Re: [gdal-dev] RE Python ogr GetFieldAsString problem

Steve, I believe comma as decimal separator is invalid for a XML double. Hence the GML driver only parses the value up to the comma. This could likely be improved to accept comma, but technically I believe a XML validator would reject this GML. Even > More info. > ogr2ogr --version = GDAL 1.

Re: [gdal-dev] Python ogr GetFieldAsString problem

inspq.qc.ca> writes: > > I'm trying to parse a GML and read all > the values of an attribute. > The problem is that feat.GetFieldAsString('LONG_STAT') > truncate the string to the comma > So instead of having -64,2131, > I get -64 in the output > What is the appropriate way to get the > value

[gdal-dev] RE Python ogr GetFieldAsString problem

More info. ogr2ogr --version = GDAL 1.10.1, released 2013/08/26 python --version = Python 2.7.3 I have modified my script to get the field type while feat is not None: feat_defn = layer.GetLayerDefn() field_defn = feat_defn.GetFieldDefn(feat_defn.GetFieldIndex(attribut))

[gdal-dev] Python ogr GetFieldAsString problem

I'm trying to parse a GML and read all the values of an attribute. Example -64,2131 DescribeFeatureType for this layer returns wfs_ds = ogr.Open(tmp_file.name) #tmp_file.name is the response of a WFS getFeature request layer = wfs_ds.GetLayerByName('SMDVDP_ST

Re: [gdal-dev] JP2 GML Axis Order Problem

Hi Even, I've created ticket #5960 Best Regards, Dennis On Wed, May 13, 2015 at 2:58 PM, Even Rouault wrote: > Dennis, > > Could you open a ticket in GDAL Trac about that ? > > Even > > > Hi guys, > > > > > > > > we have a Pleiades image here, the jp2

Re: [gdal-dev] JP2 GML Axis Order Problem

Dennis, Could you open a ticket in GDAL Trac about that ? Even > Hi guys, > > > > we have a Pleiades image here, the jp2 coming directly from the provider > with an GML header like this: > > > > > > > > > > gml:id="COVERAGE_DS_PHR1A_201306090940372_FR1_PX_E017N43_0315_01434"

[gdal-dev] JP2 GML Axis Order Problem

Hi guys, we have a Pleiades image here, the jp2 coming directly from the provider with an GML header like this: Ortho DS_PHR1A_201306090940372_FR1_PX_E017N43_0315_01434 coverage DS_PHR1A_201306090940372_FR1_PX_E017N43_0315_01434

Re: [gdal-dev] Regarding DPI in Geospatial PDF

Hi Jukka, I could understand from your mail that the mediabox is nothing but the image size in terms of width and height and the user unit is nothing but each pixel size. Does it mean it is the PDF readers responsibility to dynamically resample to the given parameters in Media Box and User

[gdal-dev] Signs like 'b≤3.2' not processed properly to dbf/shp files

Hello community, It seems as if signs like 'b≤3.2' were not processed properly to dbf/shp files. I create shape files from JSON file with GDAL using the statement: ds.CopyLayer(srcLayer, fileNameWithoutExtension, null); or with cpg file: ds.CopyLayer(srcLayer, fileNameWithoutExtension, ne