When using the created 3D City Database as a template database for new databases, Note: the search path information is not transferred and thus has to be set again, e.g.: ALTER DATABASE new_citydb_v3 SET search_path TO citydb, citydb_pkg, public; The search path will be updated upon the next login, not within the same session. To change the reference system after setting up the 3D City Database, use the command (see Oracle version for a description of the input parameters): SELECT citydb_pkg.change_schema_srid( 32632, 'urn:ogc:def:crs,crs:EPSG::32632,crs:EPSG::4326', 1); To drop the 3D City Database with all data, execute the DROP_DB.sql script in the same way like CREATE_DB.sql. Simply dropping the schemas and in a cascading ‘citydb’ ‘citydb_pkg’ way will also do the job.
Note: When using the created 3D City Database as a template database for new databases, the search path information is not transferred and thus has to be set again, e.g.: ALTER DATABASE new_citydb_v3 SET search_path TO citydb, citydb_pkg, public; The search path will be updated upon the next login, not within the same session. To change the reference system after setting up the 3D City Database, use the command (see Oracle version for a description of the input parameters): SELECT citydb_pkg.change_schema_srid( 32632, 'urn:ogc:def:crs,crs:EPSG::32632,crs:EPSG::4326', 1); To drop the 3D City Database with all data, execute the DROP_DB.sql script in the same way like CREATE_DB.sql. Simply dropping the schemas ‘citydb’ and ‘citydb_pkg’ in a cascading way will also do the job.
3DCityDB_Documentation_v3.docx