[gdal-dev] GeoPDF offsets from actual location after gdalwarp

[Even Rouault]

Le mercredi 18 novembre 2015 19:42:30, Gane R a écrit :
> Here is link to a GeoPDF (
> https://drive.google.com/file/d/0B4shTM1bPS5TMmk2OWxuTGJpY1k/view?usp=shari
> ng) this has a mile offset from the current location,
> on GDAL gdal-2.0.1 when gdalwarp warps the PDF (poppler driver) to GeoTIF
> 
> Here is gdalinfo for the file
> 
> Driver: PDF/Geospatial PDF
> Files: AssembledMaps.pdf
> Size is 3673, 2044
> Coordinate System is:
> PROJCS["UTM Zone 15, Northern Hemisphere",
>     GEOGCS["NAD83",
>         DATUM["North_American_Datum_1983",
>             SPHEROID["GRS 1980",6378137,298.257222101,
>                 AUTHORITY["EPSG","7019"]],
>             TOWGS84[0,0,0,0,0,0,0],
>             AUTHORITY["EPSG","6269"]],
>         PRIMEM["Greenwich",0,
>             AUTHORITY["EPSG","8901"]],
>         UNIT["degree",0.0174532925199433,
>             AUTHORITY["EPSG","9108"]],
>         AUTHORITY["EPSG","4269"]],
>     PROJECTION["Transverse_Mercator"],
>     PARAMETER["latitude_of_origin",0],
>     PARAMETER["central_meridian",-93],
>     PARAMETER["scale_factor",0.9996],
>     PARAMETER["false_easting",500000],
>     PARAMETER["false_northing",0],
>     UNIT["Meter",1]]
> GeoTransform =
>   494482.9934340139, 1.9797610687878, -0.4578063200329283
>   3519200.148697479, -0.4578063200329283, -1.9797610687878
> Metadata:
>   NEATLINE=POLYGON ((491222.64246014197
> 3515690.1233778466,492158.60528832977 35
> 19737.6489099222,499430.68065023294 3518056.0308031105,498494.71782204515
> 351400
> 8.5052710348,491222.64246014197 3515690.1233778466))
> Corner Coordinates:
> Upper Left  (  494482.993, 3519200.149) ( 93d 3'29.84"W, 31d48'30.24"N)
> Lower Left  (  493547.237, 3515153.517) ( 93d 4' 5.33"W, 31d46'18.79"N)
> Upper Right (  501754.656, 3517518.626) ( 92d58'53.27"W, 31d47'35.67"N)
> Lower Right (  500818.900, 3513471.994) ( 92d59'28.87"W, 31d45'24.24"N)
> Center      (  497650.947, 3516336.072) ( 93d 1'29.32"W, 31d46'57.26"N)
> Band 1 Block=3673x1 Type=Byte, ColorInterp=Red
> Band 2 Block=3673x1 Type=Byte, ColorInterp=Green
> Band 3 Block=3673x1 Type=Byte, ColorInterp=Blue
> 
> Does the scale_factor has something on this will gdal_translate -unscale
> will help or there is some problem in handling this specific file or
> projection parameters

No, not related at all. 

Fixed in trunk by r31638  "PDF: make OGC BP registration work with media box 
where min_x != 0 (in non-rotated case)"

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com