on column of table Spatial index ENVELOPE CITYOBJECT on column of table Spatial index GEOMETRY SURFACE_GEOMETRY on column of table Spatial index SOLID_GEOMETRY SURFACE_GEOMETRY on column of table Normal index GMLID CITYOBJECT on column of table Normal index GMLID SURFACE_GEOMETRY on column of table Normal index GMLID APPEARANCE on column of table Normal index GMLID SURFACE_DATA The result of an index operation is reported in the console window. For instance, Figure 64 shows the result of a status query on both spatial and normal indexes. The status means that ON the corresponding index is enabled. Figure 64: Result of a status query on spatial and normal indexes. It is to Note: strongly recommended deactivate the spatial indexes before running a CityGML on a and to reactive the spatial indexes afterwards. This way import big amount of data 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 fill Note: level is high. Note that the operation cannot be aborted by the user since this could result in an inconsistent database state.
Spatial index on column ENVELOPE of table CITYOBJECT Spatial index on column GEOMETRY of table SURFACE_GEOMETRY Spatial index on column SOLID_GEOMETRY of table SURFACE_GEOMETRY Normal index on column GMLID of table CITYOBJECT Normal index on column GMLID of table SURFACE_GEOMETRY Normal index on column GMLID of table APPEARANCE Normal index on column GMLID of table SURFACE_DATA The result of an index operation is reported in the console window. For instance, Figure 64 shows the result of a status query on both spatial and normal indexes. The status ON means that the corresponding index is enabled. Figure 64: 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.