Re: [gdal-dev] EPSG 8.2 Upgrade

2013-10-03 Thread Frank Warmerdam
Patch applied in trunk... On Thu, Oct 3, 2013 at 9:06 AM, Paul Meems wrote: > Thanks Even, > > That patch works great. > Hopefully it will get implemented soon. > > > > Paul > > *Paul Meems * > Release manager, configuration manager > and forum moderator of MapWindow GIS. > www.mapwindow.org

Re: [gdal-dev] EPSG 8.2 Upgrade

2013-10-03 Thread Paul Meems
Thanks Even, That patch works great. Hopefully it will get implemented soon. Paul *Paul Meems * Release manager, configuration manager and forum moderator of MapWindow GIS. www.mapwindow.org Owner of MapWindow.nl - Support for Dutch speaking users. www.mapwindow.nl * * 2013/10/3 Even Roua

Re: [gdal-dev] EPSG 8.2 Upgrade

2013-10-03 Thread Even Rouault
Selon Paul Meems : > I'm not sure if this is the correct place to report this. If not please let > me know. > > I'm having trouble compiling the trunk version of PROJ.4 with the updated > EPSG 8.2 database definitions. > I'm running Win7 and use VS2008. > I'm getting these errors and warnings: > W

Re: [gdal-dev] EPSG 8.2 Upgrade

2013-10-03 Thread Paul Meems
I'm not sure if this is the correct place to report this. If not please let me know. I'm having trouble compiling the trunk version of PROJ.4 with the updated EPSG 8.2 database definitions. I'm running Win7 and use VS2008. I'm getting these errors and warnings: Warning 1Command line warning D

Re: [gdal-dev] EPSG 8.2 Upgrade

2013-10-02 Thread Andre Joost
Am 02.10.2013 07:46, schrieb Frank Warmerdam: Folks, I have upgraded libgeotiff, GDAL and PROJ.4 trunk's with the EPSG 8.2 database definitions. Let me know if you see problems or have questions. Not to you, but from: http://info.ogp.org.uk/geodesy/CurrentDB.html EPSG Geodetic Parameter Dat

[gdal-dev] EPSG 8.2 Upgrade

2013-10-01 Thread Frank Warmerdam
Folks, I have upgraded libgeotiff, GDAL and PROJ.4 trunk's with the EPSG 8.2 database definitions. I have come to the conclusion that the EPSG Postgresql .sql files are distributed in WIN1252 encoding, not LATIN1, and so some special characters - mostly in comments - should be translated better.