Opened 21 years ago

Last modified 21 years ago

#279 closed defect (fixed)

SDTS UTM WKT has no linear UNIT node

Reported by: martin.daly@… Owned by: warmerdam
Priority: high Milestone:
Component: default Version: unspecified
Severity: normal Keywords:
Cc:

Description

Here is the WKT for an (OGR) SDTS 1:100000 transfer:

PROJCS["UTM Zone 18, Northern Hemisphere",GEOGCS["NAD27",DATUM
["North_American_Datum_1927",SPHEROID["Clarke 
1866",6378206.4,294.978698213901]],PRIMEM["Greenwich",0],UNIT
["degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER
["latitude_of_origin",0],PARAMETER["central_meridian",-75],PARAMETER
["scale_factor",0.9996],PARAMETER["false_easting",500000],PARAMETER
["false_northing",0]]

There is no linear UNIT node.  The UNIT node is mandatory in the OGC EBNF.  The 
WKT is OK after a call to SetLinearUnits.

Change History (1)

comment:1 by warmerdam, 21 years ago

Martin,

I have implemented an OGRSpatialReference.Fixup() method which sets missing
linear units and calls the previously required FixupOrdering().   The SDTS
drivers now use this method to cleanup their WKT, but I would also encourage
you to use it from your code to try and cleanup WKT issues with GDAL/OGR
produces CRSes. 

I have verified that this fixes up the missing units for SDTS data.  I also
fixed a few bugs I discovered in the core SDTS and iso8211 code.

Note: See TracTickets for help on using tickets.