Changes between Version 7 and Version 8 of rfc20_srs_axes


Ignore:
Timestamp:
Jan 10, 2008, 1:55:00 PM (17 years ago)
Author:
warmerdam
Comment:

revised - avoid x/y terms.

Legend:

Unmodified
Added
Removed
Modified
  • rfc20_srs_axes

    v7 v8  
    77== Summary ==
    88
    9 The OGRSpatialReference and OGRCoordinateTransformation classes assume that all coordinate systems use x=easting, y=northing (or in geographic terms x=longitude, y=latitude).  In practice some coordinate systems use alternate axis orientations (such as the Krovak projection), and some standards (GML, WMS 1.3, WCS 1.1) require honouring the EPSG declaration that all it's geographic coordinates refer to x as latitude and y as longitude.
     9The OGRSpatialReference and OGRCoordinateTransformation classes assume that all coordinate systems use (easting, northing) coordinate order (or in geographic terms (longitude, latitude)).  In practice some coordinate systems use alternate axis orientations (such as the Krovak projection), and some standards (GML, WMS 1.3, WCS 1.1) require honouring the EPSG declaration that all it's geographic coordinates have (latitude, longitude) coordinate ordering.
    1010
    1111This RFC attempts to extend the OGRSpatialReference, and OGRCoordinateTransformation classes to support alternate axis orientations, and to update selected drivers (GML, WMS, WCS, GMLJP2) to properly support axis ordering. 
     
    9494 * BSB, SAR_CEOS, ENVISAT, HDF4, JDEM, L1B, LAN, SRTMHGT: Like SetWellKnownGeogCS() these all include lat/long AXIS specifications in their hardcoded WGS84 coordinate systems.  These need to be removed so they will default to being interpreted as long/lat.
    9595
     96== Versions ==
     97
     98Work will be in trunk for GDAL/OGR 1.6.0 with the following exceptions which will be address in 1.5.x:
     99
     100 * Existing use of AXIS specifier will for geographic coordinate systems will be stripped from SetWellKnownGeogCS() and the various drivers with hard coded WKT strings.
     101 * Some sort of hack will need to be introduced into the GMLJP2 (and possibly WCS) code to flip EPSG authority lat/long values (details to be worked out).
     102
    96103== Questions ==
    97104