Re: [gdal-dev] sqlite dialect and MySQL spatial input

2013-10-01 Thread Jukka Rahkonen
Even Rouault even.rouault at mines-paris.org writes: I've just pushed in trunk a change to make SQLITE dialect available to all OGR drivers that have a specialized ExecuteSQL() implementation. Hi, Is this a correct interpretation: - The default SQL dialect is OGR SQL, except for databases

[gdal-dev] unable to make a valid TMS xml file

2013-10-01 Thread Jean-Roc Morreale
Hi, I'm trying to use the TMS minidriver, my xml file is based on the OSM's example and the data is an output of gdal2tiles. I've not been able to use it with gdal 1.10 : # gdalinfo D:\MyFolder\My_File.xml ERROR 4 : 'D:\MyFolder\My_File.xml' not recognized as a supported file format.

Re: [gdal-dev] Write dataset to web output

2013-10-01 Thread Guillaume Sueur
Hi Even, Sorry, I'm only noticing your reply now. My use case is weird as I am using GDAL to reproject a WMS source which doesn't offer web mercator (French Cadastral Parcels WMS) and needs some computation on the URL (city code, CRS depending on location). If I understand your solution, I

Re: [gdal-dev] Write dataset to web output

2013-10-01 Thread Jean-Claude Repetto
Le 01/10/2013 16:21, Guillaume Sueur a écrit : My use case is weird as I am using GDAL to reproject a WMS source which doesn't offer web mercator (French Cadastral Parcels WMS) and needs some computation on the URL (city code, CRS depending on location). If I understand your solution, I can't

Re: [gdal-dev] sqlite dialect and MySQL spatial input

2013-10-01 Thread Even Rouault
Le mardi 01 octobre 2013 08:58:22, Jukka Rahkonen a écrit : Even Rouault even.rouault at mines-paris.org writes: I've just pushed in trunk a change to make SQLITE dialect available to all OGR drivers that have a specialized ExecuteSQL() implementation. Hi, Is this a correct

Re: [gdal-dev] unable to make a valid TMS xml file

2013-10-01 Thread Even Rouault
Le mardi 01 octobre 2013 14:06:20, Jean-Roc Morreale a écrit : Hi, I'm trying to use the TMS minidriver, my xml file is based on the OSM's example and the data is an output of gdal2tiles. I've not been able to use it with gdal 1.10 : # gdalinfo D:\MyFolder\My_File.xml ERROR 4 :

Re: [gdal-dev] Kernel resource leak -- Windows

2013-10-01 Thread Even Rouault
Le lundi 30 septembre 2013 00:59:33, Joaquim Luis a écrit : Hi, I can make a ticket with this but before, let me just report it here. - Win 64 bits GDAL build While playing with an Intel analysis tool to chase GMT memory leaks I got two complains respecting GDAL. P1: Error: Kernel

Re: [gdal-dev] sqlite dialect and MySQL spatial input

2013-10-01 Thread Jukka Rahkonen
Even Rouault even.rouault at mines-paris.org writes: Le mardi 01 octobre 2013 08:58:22, Jukka Rahkonen a écrit : - The default SQL dialect is OGR SQL, except for databases when the default is to use the native SQL dialect of the RDBMS - The default dialect can be overridden by the

Re: [gdal-dev] Buffering geometries

2013-10-01 Thread Federico Jurio
Thank you for your advice Even, it works perfectly! i have another issue, what is the unit of dfDist from Bufferhttp://www.gdal.org/ogr/classOGRGeometry.html#ab34b27e2c8812a0fc1dccf055b11d1a2 ? On Tue, Oct 1, 2013 at 4:02 PM, Even Rouault even.roua...@mines-paris.orgwrote: Le lundi 30

Re: [gdal-dev] Buffering geometries

2013-10-01 Thread Even Rouault
Le mardi 01 octobre 2013 22:05:55, Federico Jurio a écrit : Thank you for your advice Even, it works perfectly! i have another issue, what is the unit of dfDist from Bufferhttp://www.gdal.org/ogr/classOGRGeometry.html#ab34b27e2c8812a0fc1dcc f055b11d1a2 ? The same unit as the coordinates of

Re: [gdal-dev] Buffering geometries

2013-10-01 Thread Federico Jurio
Thank you again, regards! On Tue, Oct 1, 2013 at 5:16 PM, Even Rouault even.roua...@mines-paris.orgwrote: Le mardi 01 octobre 2013 22:05:55, Federico Jurio a écrit : Thank you for your advice Even, it works perfectly! i have another issue, what is the unit of dfDist from Buffer

Re: [gdal-dev] sqlite dialect and MySQL spatial input

2013-10-01 Thread Even Rouault
Le mardi 01 octobre 2013 22:01:51, Jukka Rahkonen a écrit : Even Rouault even.rouault at mines-paris.org writes: Le mardi 01 octobre 2013 08:58:22, Jukka Rahkonen a écrit : - The default SQL dialect is OGR SQL, except for databases when the default is to use the native SQL dialect of the

Re: [gdal-dev] [EXTERNAL] Minimum user rights needed for Oracle driver

2013-10-01 Thread Smith, Michael ERDC-RDE-CRREL-NH
Jukka, Basically, you need read access to the schema.table in question. The spatial views are automatically available if a user has read access to the table. So the minimum access is GRANT SELECT on SCHEMA.TABLENAME to USERNAME; ALL_SDO_GEOM_METADATA is a view that contains metadata

Re: [gdal-dev] [EXTERNAL] Minimum user rights needed for Oracle driver

2013-10-01 Thread Smith, Michael ERDC-RDE-CRREL-NH
For write access, one needs INSERT and/or UPDATE on an existing table. For a new table, a user needs CREATE TABLE and CREATE SEQUENCE access to a Schema and some tablespace allocation for the schema, ALTER USER USERNAME QUOTA SIZE on TABLESPACE Y, or GRANT UNLIMITED TABLESPACE to USERNAME. Mike

Re: [gdal-dev] [EXTERNAL] Minimum user rights needed for Oracle driver

2013-10-01 Thread Rahkonen Jukka
Hi, What about if GDAL and Oracle can't find common understandment about SRID? I have seen that GDAL tries then to insert something into MDSYS.CS_SRS and with our user rights that fails always. I have not studied that further because that comes always from my error and adding -lco SRID helps

Re: [gdal-dev] [EXTERNAL] Minimum user rights needed for Oracle driver

2013-10-01 Thread Smith, Michael ERDC-RDE-CRREL-NH
The MDSYS.CR_SRS table has been deprecated. Its now a view and there are whole set of tables that are used for handling new spatial reference systems. User defined SRIDs should all be above 100 now. Specific info is at

[gdal-dev] EPSG 8.2 Upgrade

2013-10-01 Thread Frank Warmerdam
Folks, I have upgraded libgeotiff, GDAL and PROJ.4 trunk's with the EPSG 8.2 database definitions. I have come to the conclusion that the EPSG Postgresql .sql files are distributed in WIN1252 encoding, not LATIN1, and so some special characters - mostly in comments - should be translated