search

opengeospatial / geotiff

19 stars 9 forks source link

New Projection Methods #3

Closed tedhabermann closed 5 years ago

tedhabermann commented 9 years ago

This problem is described by Frank Warmerdam on the Refining GeoTIFF page.

Since the development of the GeoTIFF Specification, a number of projection methods and parameters have been added. These should also be reviewed, and if they seem reasonable and in somewhat well understood and common use they should be captured in the specification.

rouault commented 6 years ago

One common issue is the encoding of the WebMercator projection / EPSG:3857. See https://trac.osgeo.org/gdal/ticket/5924

rouault commented 5 years ago

As an example of this, libgeotiff has incorporated 2 new coordinate transformation codes (that is projection methods):


/* Added Feb 2005 */
ValuePair(CT_CylindricalEqualArea, 28)

/* Added May 2012 - from now on we use the EPSG */
ValuePair(CT_HotineObliqueMercatorAzimuthCenter, 9815)
EmDevys commented 5 years ago

Revised 1.1 should have fixed this by use of EPSG Projected CRS codes, proposal to close this issue.

rouault commented 5 years ago

Revised 1.1 should have fixed this by use of EPSG Projected CRS codes

That only partly fixes the issue. What about custom projected CRS that would want to use other projection methods than the one available in GeoTIFF ?

EmDevys commented 5 years ago

My wording was incomplete. should have been "by use of EPSG Projected CRS codes or by user-defined Projected CRS", also explained in Annex B. Therefore I confirm that this issue seems to be solved (IMHO)

cmheazel commented 5 years ago

Addressed in version 1.1. Closed at the GeoTIFF SWG meeting in Banff 2019