[PROJ] Area of usage (short) name

[Javier Jimenez Shaw]

Ups, I realized that I answered to the wrong email. Sorry
My email about "Incheon height" should be the answer to "CRS aliases"
thread. Unfortunate copy and paste on the wrong place.

On Sat, 22 Jul 2023 at 16:20, Javier Jimenez Shaw <j1 at jimenezshaw.com>
wrote:

> My use case is (I want to think) simpler.
>
> Search for "incheon height" in epsg.org:
> https://epsg.org/search/by-name?sessionkey=syx74l2mwn&searchedTerms=incheon+height
> You can see "KVD1964 height", that was called before (just a few days ago)
> "Incheon height" (now under Naming System "EPSG alias").
> If PROJ is my access to EPSG db, I would like to be able to perform that
> search somehow. I do not mind if I have to iterate (once) the whole
> catalogue to create a map.
>
> Javier
>
> On Sat, 22 Jul 2023, 10:35 Martin Desruisseaux, <
> martin.desruisseaux at geomatys.com> wrote:
>
>> Le 21/07/2023 à 18:48, Even Rouault a écrit :
>> >
>> > 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.
>> >
>> True, but this is true for CRS name as well, and nevertheless ISO 19111
>> defines the type of those names as MD_Identifier. I agree that this is a
>> bit surprising. A possible rational is that MD_Identifier contains a
>> `version` attribute. so while the identifier code alone is ambiguous and
>> unstable, the (code, version) or (namespace, code, version) tuples are
>> more stable.
>>
>>      Martin
>>
>>
>> _______________________________________________
>> PROJ mailing list
>> PROJ at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/proj
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20230723/14bff63c/attachment.htm>