Re: [gdal-dev] Parllelization slows down single gdal_calc process in python

2016-03-02 Thread Flippmoke
On my phone so can explain fully, but there are several blockers in GDAL Library that prevent multi threading from being effective. Try using different processes if it is completely required. Blake Thompson > On Mar 2, 2016, at 5:44 PM, Lorenzo Bottaccioli > wrote: > > Hi, > I'm trying to pa

[gdal-dev] Parllelization slows down single gdal_calc process in python

2016-03-02 Thread Lorenzo Bottaccioli
Hi, I'm trying to parallelize a code for raster calculation with Gdal_calc.py, but i have relay bad results. I need to perform several raster operation like FILE_out=FILA_a*k1+FILE_b*k2. This is the code I'm usign: import pandas as pdimport osimport timefrom multiprocessing import Pool df = pd.r

Re: [gdal-dev] WMS Driver defaulting to version 1.1.1

2016-03-02 Thread Jukka Rahkonen
Passmore, James H. bgs.ac.uk> writes: > > I agree with all those that think that a request like > http://myservice/ows?service=WMS&request=GetCapabilities&; should return the highest supported > version of WMS on that server (currently 1.3.0 but in the near? future 1.4.0 and then 2.0.0...). Th

[gdal-dev] Request for assignment to defect

2016-03-02 Thread Tanuj Kumar
Hello, I would like to work on the defect listed under #6388 ( Get rid of the remaining hard coded pi constants) https://trac.osgeo.org/gdal/ticket/6388 Also, if we're to remove the hard coded pi constants, shouldn't we also remove the ln2 constants, as that too is defined under math.h? Thank yo

Re: [gdal-dev] WMS Driver defaulting to version 1.1.1

2016-03-02 Thread Passmore, James H.
I agree with all those that think that a request like http://myservice/ows?service=WMS&request=GetCapabilities&; should return the highest supported version of WMS on that server (currently 1.3.0 but in the near? future 1.4.0 and then 2.0.0...). This is the expected behaviour according the to

[gdal-dev] Fwd: [OSGeo-Discuss] GSoC 2016: call for mentors

2016-03-02 Thread Even Rouault
FYI -- Message transmis -- Sujet : [OSGeo-Discuss] GSoC 2016: call for mentors Date : mercredi 02 mars 2016, 18:03:31 De : Margherita Di Leo À : "OSGeo-SoC" , OSGeo Discussions Dear All, Following the acceptance of OSGeo as mentor org also this year, we are now recruiting m

Re: [gdal-dev] WMS Driver defaulting to version 1.1.1

2016-03-02 Thread Damian Dixon
I would concur with Ian and Jeff. My experience of WMS servers is that those that say that they are 1.3.0 are miss-configured or are just not following the standard well enough. Not all of the WMS 1.3.0 servers are at fault but enough that it is safer and less time consuming to default to 1.1.0.

Re: [gdal-dev] MapInfo and number format limits

2016-03-02 Thread Even Rouault
Le samedi 13 février 2016 13:58:59, Jukka Rahkonen a écrit : > Hi, > > This question > http://gis.stackexchange.com/questions/180627/qgis-ogr-shp-to-tab-export-cr > ashing-mapinfo-due-to-number-format-issues and a referred forum topic > https://groups.google.com/forum/#!topic/mapinfo-l/sO-wcp9bnuQ

Re: [gdal-dev] WMS Driver defaulting to version 1.1.1

2016-03-02 Thread Timothy Astle
To be clear, I personally don't have a problem with 1.1.1. My concern is about version negotiation as a WMS client. I've seen users omit the version and then when something doesn't behave as expected, they manually (in a web browser) make a request as follows: http://www.example.com?request=

Re: [gdal-dev] WMS Driver defaulting to version 1.1.1

2016-03-02 Thread Michael Smith
Completely concur with Jeff. Everyone avoids 1.3.0 if they can help it. 1.1.1 is the de-facto standard version. Mike Michael Smith US Army Corps Remote Sensing GIS/Center michael.sm...@usace.army.mil -Original Message- From: gdal-dev on behalf of Jeff McKenna Date: Wednesday,

Re: [gdal-dev] WMS Driver defaulting to version 1.1.1

2016-03-02 Thread Jeff McKenna
Hi Tim, I can tell you just by use alone, the 1.1.1 standard is most prevalent. In the MapServer world, it is 1.1.1 that dominates. I also find, having been at this a long time now, that the 1.1.1 specification is most likely to be supported, if WMS is supported at all, by other mapping eng

Re: [gdal-dev] WMS Driver defaulting to version 1.1.1

2016-03-02 Thread Ian Turton
There are lots of reasons to stick with 1.1.0 and few reasons to move to 1.3 so I would guess anyone who knows they want 1.3 will want to specify it to be sure while naive users will be less suprised at getting a 1.0.0 version back if they haven't thought about it. Ian On 2 March 2016 at 13:58, T

[gdal-dev] WMS Driver defaulting to version 1.1.1

2016-03-02 Thread Timothy Astle
Does anyone know why the WMS Driver defaults to version 1.1.1 instead of 1.3.0 by default? Does anyone have any objections with this changing to 1.3.0? It seems like 1.3.0 would fall more into line with the specifications content negotiation. https://github.com/OSGeo/gdal/blob/trunk/gdal/frm

[gdal-dev] OCI loses decimal result

2016-03-02 Thread SIMON Nicolas
Dear GDAL developer, I run this command (GDAL 2.0.2, released 2016/01/26) ogr2ogr -f "ESRI Shapefile" Test2.shp OCI:user/pwd@instance -sql "SELECT RID, ROUND(sdo_geom.sdo_area (s.geom, 0.01) / 1,4) SURF_HA, s.GEOM FROM SIG_SOCS s WHERE RID IN (7778067,8644604)" And I get W