Re: [gdal-dev] GDAL/OGR 1.11.0 Beta1 ready

2014-04-05 Thread Even Rouault
Le dimanche 06 avril 2014 02:36:16, David Tran a écrit : > Hi to everybody again > > Hope you all enjoy gdal 1.11.0beta1. > > What was the big bang between v1.9.2 and >=1.1x.y? The big-bang lol ? no, I guess a tiny change that cause a compilation failure... > > 1.10.1 > make[1]: *** [cpl_xml_

Re: [gdal-dev] GDAL/OGR 1.11.0 Beta1 ready

2014-04-05 Thread David Tran
Hi to everybody again Hope you all enjoy gdal 1.11.0beta1. What was the big bang between v1.9.2 and >=1.1x.y? Because my MinGW installtion doesn't compile Gdal since version 1.10.0 at all. Only Gdal 1.9.2 with MinGW (www.mingw.org) was (configure, make, make install) fine. I tested the binari

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Martin Landa
Hi, 2014-04-05 23:50 GMT+02:00 Even Rouault : [...] >> Hum, this isn't yet possible, but I can try to see if I can add support >> for > >> that. > > Done. See http://trac.osgeo.org/gdal/changeset/27132 thanks a lot! Martin ___ gdal-dev mailing list gd

[gdal-dev] Vagrant developement environment

2014-04-05 Thread Even Rouault
Hi, Strongly inspired from MapServer vagrant set-up, itself strongly inspired from PDAL one, I've committed in trunk a Vagrantfile and the necessary scripts to setup a Vagrant development environment for GDAL. See http://trac.osgeo.org/gdal/wiki/Vagrant Even -- Geospatial professional servic

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Even Rouault
> > Is there any way how to set names also for geometry tags? Similar to > > properties, eg. > > > > > > > > myname > > tagname > > > > > > > > I would like to name them without 'geometry|' part... > > Hum, this isn't yet possible, but I can try to see if I can ad

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Even Rouault
Le samedi 05 avril 2014 22:53:20, Martin Landa a écrit : > Hi, > > 2014-04-05 22:38 GMT+02:00 Even Rouault : > > [...] > > > Hum, this isn't yet possible, but I can try to see if I can add support > > for that. > > thanks! > > > This is really wanted. The SRS is a property of a geometry column

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Martin Landa
Hi, 2014-04-05 22:38 GMT+02:00 Even Rouault : [...] > Hum, this isn't yet possible, but I can try to see if I can add support for > that. thanks! > This is really wanted. The SRS is a property of a geometry column. There are > cases where 2 geometry columns could have a different SRS. Sure, b

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Even Rouault
Le samedi 05 avril 2014 22:24:14, Martin Landa a écrit : > Hi Even, > > 2014-04-05 22:10 GMT+02:00 Even Rouault : > > there is another issue which I would like to solve. > > The layers contain multiple geometries (MultiPoint and MultiPolygon), > the relevant tags are > > > > > > >

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Martin Landa
Hi Even, 2014-04-05 22:10 GMT+02:00 Even Rouault : there is another issue which I would like to solve. The layers contain multiple geometries (MultiPoint and MultiPolygon), the relevant tags are In related GFS I have defined: cities cities|city urn:ogc:def:c

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Even Rouault
Martin, > > I will prepare such patch tomorrow. Good > > ah, this seems to be much more better solution! It seems to work, I > will do more tests later tomorrow. Try to run the autotest/ogr/ogr_gml_read.py tests to check that it doesn't cause regressions. And it would be good if you could ad

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Martin Landa
Hi Even, 2014-04-05 13:17 GMT+02:00 Even Rouault : > gmlregistry.diff looks fine, but it would be good to document elementValue in > drv_gml.html I will prepare such patch tomorrow. > All in all, I think that the more simpler solution would be to drop that patch > and rather modify the call to S

Re: [gdal-dev] Considerations around WFS layer and ArcGIS REST API Connector Plugin

2014-04-05 Thread xavier lhomme
Beginning with 10.1 the ArcGIS REST API introduces the maxRecordCount property for MapServer and FeatureServer. See http://sampleserver5.arcgisonline.com/arcgis/rest/services/CommercialDamageAssessment/FeatureServer?f=pjson The value can be change when publishing the service. If you want to obt

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Even Rouault
Martin, gmlregistry.diff looks fine, but it would be good to document elementValue in drv_gml.html As far as gmlhandler.diff is concerned, serveral issues : - naming convention : "CPLString pszFilteredElementName" should be "CPLString osFilteredElementName" - if ( pszElementName[m_poReader->Get

Re: [gdal-dev] GML / NAS code redundancy

2014-04-05 Thread Martin Landa
Dear Even, 2014-03-19 11:17 GMT+01:00 Even Rouault : > Just for Martin's enlightment, the GML driver manages to recognize several > layers in that case since the RekisteriyksikonTietoja is the top feature > present in the first bytes of the file, and the other feature types are sub > feature type

[gdal-dev] Considerations around WFS layer and ArcGIS REST API Connector Plugin

2014-04-05 Thread Stefan Keller
Hi Devs, Tobias and I are working on the "ArcGIS REST API Connector Plugin" which reads WFS- and WMTS-alike services (called Feature Service and Map Service) from ArcGIS Online or ArcGIS Server 10.x. Let's call this a connection of type "ArcGIS Layer", which creates a vector layer (in memory). 1.

Re: [gdal-dev] Strange reset OGR_INTERLEAVED_READING when using Python bindings to read OSM PBF file

2014-04-05 Thread Even Rouault
Le mercredi 02 avril 2014 21:45:23, Dražen Odobašić a écrit : > On 02.04.2014 21:38, Even Rouault wrote: > >> I had no issues when reading large PBF files using this method. For the > >> large files, without OSM_USE_CUSTOM_INDEXING=NO I got lots of "Cannot > >> read node ..." error messages, and I'

[gdal-dev] OGR SQLAnywhere driver

2014-04-05 Thread DeHaan, Dave
Hello, I recently mentioned on gdal-dev that we would like to contribute an OGR driver for SAP SQL Anywhere. I have opened ticket 5430 http://trac.osgeo.org/gdal/ticket/5430 to track this. A patch file is attached to the ticket. My apologies for not getting this uploaded before the 1.11.0