Opened 15 years ago
Closed 15 years ago
#428 closed defect (fixed)
SQL Server Spatial Provider: Incorrect sequence to determine coordinate system data
| Reported by: | thomasknoell | Owned by: | thomasknoell |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | FDO API | Version: | 3.4.0 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description
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.
Change History (2)
comment:1 by , 15 years ago
| Status: | new → assigned |
|---|
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
The changes for this issue have been dropped into the repository on November 13th 2008.