on columns of table Normal index GMLID, GMLID_CODESPACE SURFACE_GEOMETRY on columns of table Normal index GMLID, GMLID_CODESPACE APPEARANCE on column of table Normal index THEME APPEARANCE on columns of table Normal index GMLID, GMLID_CODESPACE SURFACE_DATA on columns of table Normal index GMLID, GMLID_CODESPACE ADDRESS The result of an index operation is reported in the console window as shown below. For instance, Figure 65 shows the result of a status query on both spatial and normal indexes. The status means that the corresponding index is enabled. ON Figure 65: Result of a status query on spatial and normal indexes. It is to Note: strongly recommended deactivate the spatial indexes before running a on a and to reactive the spatial indexes CityGML import big amount of data afterwards. This way the import will typically be a lot faster than with spatial indexes enabled. The situation may be different if only a small dataset is to be imported. Deactivating normal indexes should however never be required. Activating and deactivating indexes can take a long time, especially if the database Note: fill level is high. Note that the operation cannot be aborted by the user since this could result in an inconsistent database state.
Normal index on columns GMLID, GMLID_CODESPACE of table SURFACE_GEOMETRY Normal index on columns GMLID, GMLID_CODESPACE of table APPEARANCE Normal index on column THEME of table APPEARANCE Normal index on columns GMLID, GMLID_CODESPACE of table SURFACE_DATA Normal index on columns GMLID, GMLID_CODESPACE of table ADDRESS The result of an index operation is reported in the console window as shown below. For instance, Figure 65 shows the result of a status query on both spatial and normal indexes. The status ON means that the corresponding index is enabled. Figure 65: Result of a status query on spatial and normal indexes. Note: It is strongly recommended to deactivate the spatial indexes before running a CityGML import on a big amount of data and to reactive the spatial indexes afterwards. This way the import will typically be a lot faster than with spatial indexes enabled. The situation may be different if only a small dataset is to be imported. Deactivating normal indexes should however never be required. Note: Activating and deactivating indexes can take a long time, especially if the database fill level is high. Note that the operation cannot be aborted by the user since this could result in an inconsistent database state.
3DCityDB_Documentation_v3.3.docx