[gdal-dev] Re: Testing Geospatial PDF support

2010-10-21 Thread Even Rouault
For those interested in this saga, with the help of Brent, the issue has been solved and is now fixed in trunk. This was an issue when dealing with multiple georeferencing bounding boxes in Adobe style encoding and/or when the bounding box doesn't cover the whole page area. Le mardi 19 octobre

[gdal-dev] Re: Testing Geospatial PDF support

2010-10-19 Thread Brent Fraser
Evan, For the original PDF, gdalinfo shows: Driver: PDF/Geospatial PDF Files: my.pdf Size is 7487, 5229 Coordinate System is: PROJCS["WGS_1984_UTM_Zone_35N", GEOGCS["GCS_WGS_1984", DATUM["WGS_1984", SPHEROID["WGS_1984",6378137.0,298.257223563]], PRIMEM["Greenwich

[gdal-dev] Re: Testing Geospatial PDF support

2010-10-19 Thread Eli Adam
There are more geospatial pdfs available here: http://nationalmap.gov/ustopo/index.html - then click on 'Download Maps (Map Store)' on the left side. Then you need to place a marker, then click the marker, then hit download. I've not worked with them very much yet. Bests, Eli >>> Even Rouau

[gdal-dev] Re: Testing Geospatial PDF support

2010-10-19 Thread Even Rouault
Brent, I'm not sure what you find is wrong. What does gdalinfo returns ? The PDF driver will reproject the coordinates of the GPTS array from geographic into UTM 35N and try to build a geotransform matrix from that. The matrix may have rotating terms, so you likely need to use gdalwarp afterwar