Zhihang Yao
Zhihang Yao
The KML/COLLADA/glTF-Exporter always creates at least two COLLADA files, regardless how large is the value given in the field "_Put objects together in groups of_" (preferences -> KML/CLOLLADA/glTF-Export -> Rendering...
Currently, the XPath's function call e.g. `count` is not supported in XML query expression and the query like "_Find all buildings having at least four wall surfaces_" cannot be expressed....
Since we introduce the column `root_feature_id` (see #123) in the property table, wouldn't be better to rename `feature_id` > `parent_feature_id`? That would be more intuitive for building the "Feature hierarchy"....
The `aggregation_info` table was used for automatically generating the delete and envleope functions for citydb v4. Since we have a relatively generic database schema in v5 and introduced the table...
Since we have a very static and generic table structure for storing CityGML ADE data, the `ADE` table can be simplified by dropping some columns e.g. `db_prefix`, `xml_schemamapping_file` etc.
The current length is 256, which is not enough for storing some generic string attribute in real-world data. I'll change it to 4000 which should be OK.
Could we drop the tables “citymodel” and “cityobject_member” and store the information in the new “feature” and “property” tables?
During the CityGML import, the time attrbitue value e.g. `2022-02-01T00:00:00+05:00` will be automatically translated to the time of the database system. For example, if the database system uses UTC timezone,...
The `grid_coverage` table is never supported by our software e.g. importer/exporter. Let's drop this table for the alpha release and discuss later, if we need to readd this table for...