Re: [gdal-dev] Geospatial PDF with OGR_DATASOURCE

2012-06-05 Thread Rahkonen Jukka
Even Rouault wrote:

 
  
  I made some quick trials by combining some raster base maps and
  shapefiles and I am sure that this will be an amusing toy. But
  with the default settings the vector features are almost invisible
  on the map because of the drawing styles. I made a blind
  trial with OGR Feature Styles and wrote these two lines into a
  .ofs file for making linework a bit wider
  OFS-version 1.0
  DefaultStyle: PEN(c:#FF,w:5px)
  
  However, it did not make any difference. Perhaps OFS is not
  supported yet, or? 
 
 
 Oh, I didn't even know that those .ofs file existed, but 
 indeed I see them 
 mentionned in http://www.gdal.org/ogr/ogr_feature_style.html 
 . However, from a 
 quick look, although this seems to be implemented in 
 ogr/ogrfeaturestyle.cpp, 
 this feature isn't used by any driver.
 
  I did notice that I can change the colour
  of the features through Acrobat reader's UI, but I cannot set
  the line width. As a first aid I would suggest to use wider
  lines and bigger points as defaults.
   
 Yes, as far as I remember the current state of the code, the 
 pen width is 
 scaled with the coordinates of the geometries, so the 
 appropriate value of the 
 width depends on whether you work with projected or 
 geographic SRS, and the 
 layer spatial extent.
 
  Areas, which are drawn
  as semi-transparent with a light grey fill are OK.
 
 Even if table level styling isn't supported, the PDF writer 
 can fetch the 
 style at the feature level (not at the table level like you 
 tried). You can 
 for example try the following to attach the style to the features :
 
 ogr2ogr -f PDF poly.pdf poly.shp -sql select *, 
 'PEN(c:#FF,w:5px)' as 
 OGR_STYLE from poly

I want to combine raster and vector sources but I found
it impossible to discover how to use the -sql parameter
together with the PDF creation option -co OGR_DATASOURCE=
Fortunately it was enough to add an attribute named OGR_STYLE
into the shapefile and fill in styles as strings. Styles are 
really applied feature by feature so it is possible to set
colours and line widths individually for each feature in the
shapefile, which is pretty amusing.

I could symbolize lines and polygons with PEN and BRUSH by
using the examples from http://www.gdal.org/ogr/ogr_feature_style.html
However, I could not make SYMBOL settings to work with my
points. They appear as grey circles even if I attached some
OGR_STYLE strings to them, like
 SYMBOL(c:#00FF00,id:ogr-sym-7)

I was able to set the colours of the points by using PEN but 
altering the w: parameter did not change the size of the 
points.

-Jukka Rahkonen-

 Best regards,
 
 Even
 
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev


Re: [gdal-dev] JAXAPalsar 1.0 1.1 extended metadata reading support

2012-06-05 Thread Brent Fraser
Has there been any progress in reading AVNIR2 data?  GDAL's ceos driver 
doesn't support georeferencing...


Best Regards,
Brent Fraser


On 6/27/2011 6:56 AM, Rodolfo Bonnin wrote:

Hello Antonio,

I'll read the specs regarding JaxaPalser type, out software is reading 
those and they look well, but I didn't analyze the format in detail. 
I've also added georeferencing (Calculating the affine transform based 
on the 4 corners and assigning a coordinate system (WGS84 instead of 
ITRF97 at the moment as we are based on 1.8.0) to the JaxaPalsar driver.


For the time being, I'm writing new drivers for the PRISM and AVNIR2 
sensors, based on the current JaxaPalsar driver, as we are constrained 
in time, but I think that once I send the code, the diffing could be 
useful when writing the new unified driver. I'm ready to collaborate 
if you think another approach could more useful. The idea is to have 
PRISM and AVNIR2 support ASAP.


Regards,
Rodolfo Bonnin.

2011/6/26 Antonio Valentino antonio.valent...@tiscali.it 
mailto:antonio.valent...@tiscali.it:

 Hi Frank,

 Il 26/06/2011 13:42, Frank Warmerdam ha scritto:
 On 11-06-26 06:34 AM, Antonio Valentino wrote:
 Hi Frank,

 [...]

 Looking deeper into the ceos2 code it seems to me that the 
recipe for

 decoding ALOS-PALSAR products do not match at all specifications I can
 find at

 http://www.eorc.jaxa.jp/ALOS/en/doc/fdata/PALSAR_L10_J_ENa.zip

 Does that recipe refers to another format specification document?

 Antonio,

 I don't know.

 well, in this case I guess it is not a good idea to modify that recipe
 in any manner

 Also, regarding the ceos2 driver in general, I didn't find an obvious
 way to support CEOS products with multiple image files (like multi
 polarization PALSAR or ALOS PRISM).

 Ah, that may well have been part of Phil's rationale for handling
 multi-polarization data with custom drivers.  I don't know how hard
 it would be to do so within the existing SAR_CEOS driver.

 OK, thank you for confirming my analysis

 Possibly you could set up a multi-polarization driver based on the
 low level ceos2 code but with a somewhat different recipe mechanism?

 Yes I could try.

 A new CEOS multi-band driver could be used for ALOS (all three sensors)
 and Landsat.
 There are other sensors that could be interesting to support?
 Where can I find pointers and format spec?

 ciao

 --
 Antonio Valentino
 ___
 gdal-dev mailing list
 gdal-dev@lists.osgeo.org mailto:gdal-dev@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/gdal-dev




--
Ing. Rodolfo Bonnin
SUR Emprendimientos Tecnológicos

Perú 345  Piso 5to Oficina B (C1067AAG)
Ciudad de Buenos Aires, Argentina
Tel. +54 (11) 4342-2976/84
rodolfobon...@suremptec.com.ar mailto:rodolfobon...@suremptec.com.ar
www.suremptec.com http://www.suremptec.com



___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Geospatial PDF with OGR_DATASOURCE

2012-06-05 Thread Even Rouault
 I want to combine raster and vector sources but I found
 it impossible to discover how to use the -sql parameter
 together with the PDF creation option -co OGR_DATASOURCE=
 Fortunately it was enough to add an attribute named OGR_STYLE
 into the shapefile and fill in styles as strings.

Yes, you can't directly do that through the GDAL PDF driver, but you can for 
example use a OGR VRT as the datasource for the OGR_DATASOURCE creation 
option.

 
 I could symbolize lines and polygons with PEN and BRUSH by
 using the examples from http://www.gdal.org/ogr/ogr_feature_style.html
 However, I could not make SYMBOL settings to work with my
 points. They appear as grey circles even if I attached some
 OGR_STYLE strings to them, like
  SYMBOL(c:#00FF00,id:ogr-sym-7)
 
 I was able to set the colours of the points by using PEN but
 altering the w: parameter did not change the size of the
 points.

Yes, SYMBOL tool was not yet implemented up to now. There's now a limited 
implementation of it :

r24543 /trunk/ (3 files in 3 dirs): OGR PDF: use SYMBOL styling on point 
geometries, limited to taking into account the id (ogr-sym-0 to ogr-sym-9), c 
and s parameters

Note that the PEN, BRUSH and LABEL tool are also limited in the support of 
their parameters :
  * color, width and dash pattern for PEN
  * color for BRUSH
  * text, color, size and angle for TEXT (the text being limited to ASCII 
characters)
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev