I don't think EPSG extent short names qualify as identifiers. They might
be altered between EPSG releases. Only their EPSG code is a true (ie
unmutable) identifier.
Le 21/07/2023 à 17:46, Martin Desruisseaux a écrit :
Le 19/07/2023 à 00:02, Even Rouault a écrit :
So basically the object model of osgeo::proj::metadata::Extent should
likely be extended with a shortName() getter (the corresponding
GeoAPI class that serves as the inspiration,
http://www.geoapi.org/3.0/javadoc/org.opengis.geoapi/org/opengis/metadata/extent/Extent.html,
has a single getDescription()), a C binding to get it (likely
proj_get_area_of_use_ex2()), and
AuthorityFactory::Private::createPropertiesSearchUsages() be modified
to populate it.
Alternatively if the short area name can be seen as an identifier,
then in ISO 19115 model it can be a GeographicDescription. That
description can then be included among the values returned by
Extent.getGeographicElements().
Note: EPSG defines domain of validity not only by bounding boxes or by
names, but also by polygons stored as Shapefile. The latter could be
returned by BoundingPolygon in ISO 19115 model. Said otherwise,
Extent.getGeographicElements() allows to specify an area of validity
in different ways:
* By identifier
* By bounding box
* By bounding polygon
Those 3 ways can be made available together.
Martin
_______________________________________________
PROJ mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/proj
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
PROJ mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/proj
