Feature Requests item #3610218, was opened at 2013-04-07 02:15 Message generated for change (Comment added) made by jratike80 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=679909&aid=3610218&group_id=118054
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: File/Data IO Group: None Status: Open Resolution: None Priority: 6 Private: No Submitted By: michael michaud (michaudm) Assigned to: michael michaud (michaudm) Summary: Add WMS 1.3.0 Initial Comment: Note : I've started refactoring Parser to implement different versions as sublclasses (target : OJ 1.7) ---------------------------------------------------------------------- >Comment By: Jukka Rahkonen (jratike80) Date: 2013-04-07 04:04 Message: This is good plan because there are nowadays servers which support only version 1.3.0. First thing to change is simple, what is SRS up till WMS version 1.1.1 is called as CRS in WMS 1.3.0. The harder part is the BBOX axis order problem. Earlier versions of WMS use always axis order Easting-Northing but in WMS 1.3.0 the official axis order of the coordinate reference system should be honoured. It means that every WMS client should know all the projections of the world and know it they are presenting coordinatesn in latitude-longitude/Northign-Easting order as longitude-latitude/Easting-Northing. Because OpenJUMP does not have any native support for projections the handling of axis order comes tricky. A simple way to handle WMS 1.3.0 axis orders would be to re-use the workaround used in MapServer. There is a source ccde file wile which is listing all the EPSG-codes which are using the reversed axis order https://github.com/mapserver/mapserver/blob/master/mapaxisorder.csv Using this text file would leave two problems: - the list may have errors or it may be incomplete and because it is a workaround it is not guaranteed that the list will be maintained in the future - not all WMS 1.3.0 servers are handling the axis order correctly for each and every CRS My suggestion is to use the MapServer text file as a basis for automatic handling of axis order but also give users a possibility to override the automatic selection as "Force lat-lon/N-E" or "Force lon-lat/E-N", This way it should be possible to read data from any WMS 1.3.0 server with OpenJUMP in any projection, even unknown by code and even if the server is misconfigured. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=679909&aid=3610218&group_id=118054 ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
