please let people find their EPSG on the web

[timmie]

Maybe a link to ​http://spatialreference.org/ could be added to the location wizard.

A extra button: "Look-Up your EPSG-code on the web". This button could link to the above mentioned address. Also a explanation why or what the EPSG-code is good for (the Mapserver docs have nice examples) would be nice. Many migrating users would never have heard of EPSG...

Experienced users will appreciate when working with other projections...

[martinl]

Replying to timmie:

Copied from grass-dev ML by Hamish:

Maybe a link to ​http://spatialreference.org/ could be added to the location wizard.

A extra button: "Look-Up your EPSG-code on the web". This button could link to the above mentioned address.

A nice idea, albeit subject to volatility of some else's website. Link the button to something we control like a page GRASS's wiki or OSGeo's wiki or grass's osgeo web pages? Then old versions don't have hardcoded deal links one day.

Also a explanation why or what the EPSG-code is good for (the Mapserver docs have nice examples) would be nice. Many migrating users would never have heard of EPSG...

mouse-over tooltip?

Experienced users will appreciate when working with other projections...

[martinl]

From grass-dev ML by Michael Barton:

I echo Hamish's sentiments below. The page is nice, but I worry about hardcoding a link to a URL that we don't control. Also, GRASS (i.e., PROJ) can only read epsg codes that are in the database that comes with GRASS. I don't know if we can depend on the web version and local versions being the same.

Re explanation of EPSG codes, we need a help manual for the location wizard. There are other aspects that need to be explained too. The new GUI is still under development and we are very grateful for any who are taking the time to test it. We also welcome any assistance--eg. Creating the html pages for location manager help. We could then add help buttons to pages.

[neteler]

For the record: ​http://www.epsg-registry.org/

[wenzeslaus]

For the record: ​http://epsg.io/

​http://epsg.io/ is much newer than ​http://spatialreference.org/ and nicer (more user friendly) than ​http://www.epsg-registry.org/. This also shows what changed and what not (old link works after 7 years but we might want to change it to something else now which we again don't know how stable it will be).

Creating a manual page on that topic with (external) links to these three websites is a good idea, I think, and links in the GUI wouldn't be so bad. We can add there more than one to increase the probability that at least one of them works.

Anyway, GUI does not prevent people from opening browser and finding one of these web pages online using their judgment, so downgrading priority to trivial.

[neteler]

GDAL offers a function for that:

Python: srs.AutoIdentifyEPSG()

(see ​http://www.gdal.org/classOGRSpatialReference.html#acb0373c83927bfd694048da6f79e33ea)

In C: OSRAutoIdentifyEPSG()

See

• ​http://gis.stackexchange.com/questions/7608/shapefile-prj-to-postgis-srid-lookup-table
• ​https://lists.osgeo.org/pipermail/gdal-dev/2014-August/039963.html
• ​https://lists.osgeo.org/pipermail/grass-dev/2015-August/075926.html

[neteler]

Milestone renamed

[Nikos Alexandris]

Relevant: ​https://lists.osgeo.org/pipermail/discuss/2016-August/016505.html

[neteler]

Ticket retargeted after milestone closed

[martinl]

All enhancement tickets should be assigned to 7.4 milestone.

[neteler]

Related update from GDAL project:

On Sat, Nov 25, 2017 at 9:02 PM, GDAL <trac@…> wrote:

> #6188: OSRAutoIdentifyEPSG does not identify EPSG 3358 (North Carolina)
> ------------------------------------------------+------------------------
>  Reporter:  Markus Neteler                      |       Owner:  warmerdam
>      Type:  enhancement                         |      Status:  closed
>  Priority:  normal                              |   Milestone:  2.3.0
> Component:  default                             |     Version:  1.11.2
>  Severity:  normal                              |  Resolution:  fixed
>  Keywords:  AutoIdentifyEPSG, GetAuthorityCode  |
> ------------------------------------------------+------------------------
> Changes (by Even Rouault):
>
>  * status:  new => closed
>  * resolution:   => fixed
>  * milestone:   => 2.3.0
>
>
> Comment:
>
>  OSRFindMatches() added in GDAL trunk should help

$ gdalsrsinfo -e 'PROJCS["Lambert Conformal Conic",
>     GEOGCS["grs80",
>         DATUM["North_American_Datum_1983",  SPHEROID["Geodetic_Reference_System_1980",6378137,298.257222101]],
>         PRIMEM["Greenwich",0],
>         UNIT["degree",0.0174532925199433]],
>     PROJECTION["Lambert_Conformal_Conic_2SP"],
>     PARAMETER["standard_parallel_1",36.16666666666666],
>     PARAMETER["standard_parallel_2",34.33333333333334],
>     PARAMETER["latitude_of_origin",33.75],
>     PARAMETER["central_meridian",-79],
>     PARAMETER["false_easting",609601.22],
>     PARAMETER["false_northing",0],
>     UNIT["Meter",1]]'
EPSG:32119

-- Ticket URL: <​https://trac.osgeo.org/gdal/ticket/6188#comment:2> GDAL <​http://trac.osgeo.org/gdal/> Geospatial Data Abstraction Library is a translator library for raster and vector geospatial data formats.

[neteler]

Ticket retargeted after milestone closed

[martinl]

Closing, please feel free to reopen if desired.