[fdo-trac] #428: SQL Server Spatial Provider: Incorrect sequence to determine coordinate system data

[FDO]

#428: SQL Server Spatial Provider: Incorrect sequence to determine coordinate
system data
----------------------------+-----------------------------------------------
   Reporter:  thomasknoell  |       Owner:  thomasknoell
       Type:  defect        |      Status:  new         
   Priority:  major         |   Milestone:              
  Component:  FDO API       |     Version:  3.4.0       
   Severity:  3             |    Keywords:              
External_id:                |  
----------------------------+-----------------------------------------------
 In the current version, the SQL Server Spatial provider first consults the
 SQL Server 2008 coordinate system library to determine the coordinate
 system for a given EPSG code and then - if the information could not be
 found in the library - the extended coordinate system file. However, since
 the extended coordinate system file - if present - is intended to allow a
 user to overwrite predefined definitions, it needs to be consulted first.
 Only if there is no entry for the defined EPSG code in the extended
 coordinate system file should the SQL Server 2008 coordinate system
 library be consulted.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/428>
FDO <http://fdo.osgeo.org/>
Feature Data Objects