Andrea: Thanks for letting me tag you in on the conversation, while I think I have a way forward, I would like to ask if I am missing an easier way of requesting the CoordinateReferenceSystem "in the original order" (when the global forceXY hint is set).
Related issue and pull request is here: - https://jira.codehaus.org/browse/GEOT-375 - https://github.com/geotools/geotools/pull/37 > FIX GEOTOOLS WMS 1.3.0 > > I was going to ask Andrea if there was a way to have our cake (global hint) > and eat it too (have WebMapServer return the correct value). > > And then reading that page I found it: > > if( forceXY == null ){ > crs = CRS.decode(srsName); > } > else if( forceXY == Boolean.TRUE ){ > crs = CRS.decode(srsName,true); > } > else if( srsName.startsWith("EPSG:") && > Boolean.getBoolean(GeoTools.FORCE_LONGITUDE_FIRST_AXIS_ORDER)){ > // how do we look up the unmodified axis order? > String explicit = srsName.replace("EPSG:", > "urn:x-ogc:def:crs:EPSG:"); > crs = CRS.decode(explicit,false); > } > else { > crs = CRS.decode(srsName,false); > } > > > Still this is a very mean change to play on GeoTools. Innocent apps that have > forceXY on may be shocked (shocked!) when WMS 1.3.0 tells them different. > Still they were unlikely to be able to talk to a WMS 1.3.0 anyways since the > data was inconsistent… > > So I can pull the trigger on this WMS fix, and should anyways. > > But we should consider when to remove this forceXY hack … anyone else run > into trouble of this nature? > ---- > Jody Garnett >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
