[gdal-dev] Setting CS for FileGDB layers

[Jeremy Palmer]

Wow Even - thanks for the fix. Your response on this list amazes me.

I just tested creating FileGDB layers for the NZ CS's again. Most of the common ones now work using the EPSG Id :) However I still get failures on these:

2111    PROJCS  NZGD_2000_Wanganui_Circuit
2113    PROJCS  NZGD_2000_Wellington_Circuit
2114    PROJCS  NZGD_2000_Collingwood_Circuit
2125    PROJCS  NZGD_2000_Gawler_Circuit
27215  PROJCS  NZGD_1949_Nelson_Circuit
27216  PROJCS  NZGD_1949_Karamea_Circuit
27222  PROJCS  NZGD_1949_Okarito_Circuit
27227  PROJCS  NZGD_1949_Lindis_Peak_Circuit
27231  PROJCS  NZGD_1949_North_Taieri_Circuit

I checked the ArcGIS WKT definitions and they all have the correct AUTHORITY EPSG id set. Maybe a FileGDB API database issue?

Cheers
Jeremy
________________________________________
From: Even Rouault [even.rouault at mines-paris.org]
Sent: Sunday, 30 September 2012 11:57 p.m.
To: gdal-dev at lists.osgeo.org
Cc: Jeremy Palmer
Subject: Re: [gdal-dev] Setting CS for FileGDB layers

Le dimanche 30 septembre 2012 09:52:56, Jeremy Palmer a écrit :
> Hi All,
>
> When creating an Esri FileGDB layer the spatial reference system has to be
> defined using the "Esri" WKT definition. Otherwise you get an "General
> function failure" error.
>

See http://trac.osgeo.org/gdal/ticket/4838 for a fix. We can in fact use some
API from Util.h to query the ESRI SRS DB and find the expected ESRI WKT
definition from a EPSG code, or, if the EPSG code is unknown, to iterate over
the ESRI DB SRS until we find a match by comparing the SRS with
OSRSpatialRefrence::IsSame()

This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or info at linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank You.