GGDM Entity Name and Code Updates Affect Model Paths

[UnclePoole]

One finding (expected) is that moving to the GGDM data model will affect how certain directory paths are calculated since this is based on both the FACC-like 5 letter entity code and the actual name of the entity type.

Based on the initial mapping from GGDM to CDB, a majority of the names and codes will stay the same, but not necessarily both for each feature type. For example, BUILDING is AL015 in CDB 1.1 but AL013 in GGDM.

The existing CDB standard feature dictionary should properly handle this case already - but CDB implementations may or may not be prepared to deal with such a change.

Filing here just as a reminder to include in the ER.

[PresagisHermann]

I do not foresee and issue with this. The only case where the FACC letters appears in the folder structure (aside from the filename) is for GTModels. The justification for using the 2 first letters as folder (AL015 translate to 500_GTModelGeometry\A_Culture\L_Misc_Feature) was to avoid too many files in the same folder. The actual name of the folders can change with GGDM an the objective would still be met. If GTModels are stored in a GeoPackage table, this folder structure is not required as the indexing is not limited like the filesystem.