Lets turn back the clock to a NAD27/EPSG:4267 data set:
https://tnris.org/data-catalog/entry/original-texas-land-survey/ (1 MB / CC0 data)
When this data is published via GeoServer and displayed in an WGS84/EPSG:4326 map the results do not quite line up (see attached screen snaps).
We expect this will require both:
an ellipse shift between clark66 and a wgs84
and a datum shift between NAD27 and NAD83
We assume one of the systems is going through NAD27 → NAD83 and doing a small small transform to WGS84, while we assume the other system is just doing the ellipse shift.
GeoServer 2.9.x (configured with user_projections with conus.los and conus.las grid-shift files )
Shall we close as won't fix, or maybe create a request for enhancement? The work to have more dynamic choice of transformation paths is not going to be trivial, especially in terms of making it perform in an acceptable way
It has been addressed with a documentation fix for now (an additional
On Sat, Jul 9, 2016 at 4:46 AM Andrea Aime [Administrator] (JIRA) <
If we are content with the documentation fix this can be closed, if you want to consider the approach with loading them all up and choosing the "best" we can leave it open.
Closing, as this really boils down to a request for improvement. Usual process: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Mass closing all resolved issues not modified in the last 4 weeks