Le jeudi 01 mars 2012 11:43:59, Rahkonen Jukka a écrit : > Hi, > > EPSG:3067 works for me too.
I meant EPSG:32635 sorry. But now, I've downloaded your http://latuviitta.org/documents/GDAL_OGC_32635.pdf sample and it is properly recognized by TerraGo toolbar and the coordinates reported are consistant with gdalinfo output.... And I can see the Document - Page 1 - Map Frame 1 structure. > The toolbar is installed yesterday from > TerraGo. I am just an end user and I cannot do any difficult things like > compiling. I tried to edit the EPSG:32635 description with hex editor and > changed "/" into "N". No effect, TerraGo tool bar does not find the > coordinates. > > With EPSG:32635 GeoPDF file properties does not show any document tree > structure. It is just "Document". With EPSG:3067 it is Document - Page 1 - > Map Frame 1. Perhaps there is something that truncates the metadata? > > -Jukka Rahkonen- > > Een Rouault wrote: > > Selon Rahkonen Jukka <[email protected]>: > > > > Nice to see early testers of geospatial PDF writing support ! > > > > I'm currently behind a corporate firewall that prevents > > access to your samples, > > but I did a quick test similar to yours and EPSG:3067 seems > > to work fine with > > Terrago Toolbar (v5.7.70). However I suspect that the > > presence of the unescaped > > slash (/) in the Description string might be the cause of the > > issue (if you have > > a different version of the toolbar). I've not verified if it > > is allowed or not > > by the PDF spec, but poppler doesn't seem to have issue with it. > > > > So perhaps you could try the following patch that will encode > > strings with > > slashes into hexadecimal UTF16 sequences : > > > > Index: pdfobject.cpp > > =================================================================== > > --- pdfobject.cpp (revision 24040) > > +++ pdfobject.cpp (working copy) > > @@ -63,7 +63,7 @@ > > > > for(i=0;(ch = pabyData[i]) != '?';i++) > > { > > > > if (ch < 32 || ch > 127 || > > > > - ch == '(' || ch == ')' || > > + ch == '(' || ch == ')' || ch == '/' || > > > > ch == '\' || ch == '%' || ch == '#') > > break; > > > > } > > > > > > Hi, > > > > > > I had a quick test by converting one GeoTIFF into > > > > georeferenced PDF files > > > > > with different parameters and opening results with Acrobat > > > > Reader and TerraGo > > > > > toolbar. > > > > > > For TerraGo the metadata must be in OGC_BP style and ISO > > > > style metadata must > > > > > not exist (option BOTH does not work). What is odd is that > > > > TerraGo toolbar > > > > > finds coordinates if I run gdal_translate with -a_srs > > > epsg:3067 but not if I run it with -a_srs epsg:32635. > > > There seems to something different in the PDF headers, here > > > > are short > > > > > captures > > > from the beginnings of the files > > > > > > EPSG:32635 which is not understood by TerraGo toolbar > > > > > > %PDF-1.6 > > > %<bh:ff><bh:ff><bh:ff><bh:ff> > > > 7 0 obj > > > << /CTM [ (0.5487347256) 0 0 (0.5487347256) (3409989.640548643) > > > (6956053.279989699) ] /Description (WGS 84 / UTM zone 35N) /Neatline > > > > > > EPSG:3067 which is OK for TerraGo > > > > > > %PDF-1.6 > > > %<bh:ff><bh:ff><bh:ff><bh:ff> > > > 7 0 obj > > > << /CTM [ (0.5487347256) 0 0 (0.5487347256) (3409989.640548643) > > > (6956053.279989699) ] /Description > > > > <FEFF0045005400520053003800390020002F00200054004D0033003500460 > > 049004E00280045002C004E0029> > > > > > /Neatline > > > > > > Images are available here > > > http://latuviitta.org/documents/GDAL_OGC_32635.pdf > > > http://latuviitta.org/documents/GDAL_OGC_3067.pdf > > > > > > -Jukka Rahkonen- > > > > > > -Jukka Rahkonen-_______________________________________________ > > > gdal-dev mailing list > > > [email protected] > > > http://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
