Many CRS Definitions don't have useful range specifications

[Norm Olsen]

There are more than 4,000 CRS definitions in the coordsys.asc file which do not have a geographic useful range specified.

[Norm Olsen]

A 'ConsoleUtility' named csAddEpsgExtents was written which will add geographic extents to the coordsys.asc file in a manner which will enable reasonable 'diff' action to see what was done.

This new utility used three sources to apply geographic extents to the definitions in the coordsys.asc file: EPSG 7.09, a coordsys.asc file maintained by the author of CS-MAP prior to Open Source submission, and a simple algorithm which applies easily to UTM zones.

In the process, definitions in the "LEGACY" group were not altered. The result of executing this process is summarized:

• 6617 definitions in the coordsys.asc file
• 1764 were LEGACY definitions, no fix attempted
• 702 Geographic extents already in place, no change attempted
• 2235 Fixed with an extent extracted from EPSG 7.09
• 830 Fixed with a pre-open source Mentor definition
• 109 Fixed with standard UTM extent definition based on zone
• 977 Remain without a geographic extent specification, may need manual tweaking.

NOTE: that in the CS-MAP context, these extents are considered to be useful ranges, and not the designed range of useage. Thus, CS-MAP extents tend to be more liberal than EPSG extents. Thus the csAddEpsgExtents application increased the size of the EPSG extents by about 25% (12.5% in each direction). The expansion of geographic system definitions was limited to a maximum of 2 degrees.