On Fri, Sep 2, 2016 at 8:59 AM, Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> Hi,
>
>
>
> It might be good if at least the developers would find information from
> the native data sources. In case of EPSG data I believe that it is then
> http://epsg-registry.org and for
Hi,
It might be good if at least the developers would find information from the
native data sources. In case of EPSG data I believe that it is then
http://epsg-registry.org and for this projection
http://epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::32661
What Google finds is usually
By the way, the EPSG database seems to also have the E,N oriented variant,
it's under a different code:
https://epsg.io/5041
Cheers
Andrea
On Thu, Sep 1, 2016 at 6:46 PM, Andrea Aime
wrote:
> On Thu, Sep 1, 2016 at 6:15 PM, Bessette-Halsema, Dominique E <
>
On Thu, Sep 1, 2016 at 6:15 PM, Bessette-Halsema, Dominique E <
dominique.besse...@gdit.com> wrote:
> Hi
>
>
>
> I’m using GeoServer 2.9 and I’m seeing that the output axes for EPSG:32661
> is Northing-Easting. The bug https://osgeo-org.atlassian.
> net/browse/GEOS-6354 documents that the axis
Hi
I'm using GeoServer 2.9 and I'm seeing that the output axes for EPSG:32661 is
Northing-Easting. The bug https://osgeo-org.atlassian.net/browse/GEOS-6354
documents that the axis is swapped and says that EPSG:32661 does not follow the
standard. This bug report was closed under 2.5 but I'm