CoordinateReferenceSystem:1.1.0 PreferredUsage.Extent.Description not indexed
CC @debasisc
PreferredUsage.Extent.Description
was adding in v1.1.0 for LOCAL reference-data CoordinateReferenceSystem.
Per email from Fabien on 2022-05-25, the search API seems NOT to be indexing on description (osdu/platform/system/reference/crs-conversion-service#44 (comment 121829)).
A Usage in EPSG data model is an intersection of an Extent and Scope.
-
Ensure this property is indexed because it is more complete and less cryptic than Name (e.g., Description contains all country names where Name may say "world"; and Description may contain a list of all Counties in a US State. -
Check similar for CoordinateTransformation:1.1.0 -
Note: these data definitions also have a property called Usages
, which is an array. Often it will be an array with 1 element in EPSG Dataset. ThePreferredUsage
is an OSDU construct, it is one of theUsages
(again, in generalPreferredUsage
will be a direct copy of the onlyUsages
array element). The point of this comment is to consider/ensure thatUsages
properties do not need to be indexed butPreferredUsage.Extent.Description
(and not necessarily ..Name). AlsoPreferredUsage.Scope.Name
should be indexed. -
I believe this is known, but the data model contains a spurious (Preferred)Usages.Name
, which is a copy of the(Preferred)Usages.Extent.Name
. The reason is perhaps that apparently it gets returned by the GeoRepository API - but data modeling wise it should not be there (i.e.,Usage.Extent
has a name andUsage.Scope
has a name, but Usage does not have a name). It may be easiest to ignore this; or properly fix EpsgManifestGenerator and all loaded schemas; though it may not warrant the hassle of a schema update if only this is addressed. Maybe it can be tagged as deprecated usage to avoid people relying on it (though as said, name is only a short description).