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

2013-10-03 Thread aborruso
Ciao Jukka, Rahkonen Jukka wrote > It could be good to mention that since GDAL version r26506 in trunk and > with > the future GDAL releases beginning from 1.11 (or 2.0) users do not need to > do this in a tricky way with VRT but it is enough to just use -dialect > SQLITE. People will find your b

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

2013-10-03 Thread Jukka Rahkonen
aborruso gmail.com> writes: > > Hi Even, Jukka, GDAL developers, > I have written a blog post (in Italian), about this MySQL/GDAL/Sqlite > experience: http://goo.gl/YvRqo2 > > It is another way to say thank you. Ciao, It could be good to mention that since GDAL version r26506 in trunk and wi

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

2013-10-02 Thread aborruso
Hi Even, Jukka, GDAL developers, I have written a blog post (in Italian), about this MySQL/GDAL/Sqlite experience: http://goo.gl/YvRqo2 It is another way to say thank you. Best regards, a -- View this message in context: http://osgeo-org.1560.x6.nabble.com/sqlite-dialect-and-MySQL-spatial-in

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

2013-10-02 Thread aborruso
Hi Even, Even Rouault wrote > Wouldn't Area() as described in > http://dev.mysql.com/doc/refman/5.0/en/geometry-property- > functions.html#function_area do the job ? you are right, but I have used Area() in my post to make a simple example. I'm talking about functions like "Contains". In MySQL

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

2013-10-02 Thread Even Rouault
Le mercredi 02 octobre 2013 10:13:23, aborruso a écrit : > Hi, > firts of all thank you for your work. It is always very nice to see how a > great open source community works. > > > Even Rouault wrote > > > Using SQLITE dialect with a RDBMS driver is kind of unusual use case > > (which was the t

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

2013-10-02 Thread aborruso
Hi, firts of all thank you for your work. It is always very nice to see how a great open source community works. Even Rouault wrote > Using SQLITE dialect with a RDBMS driver is kind of unusual use case > (which was the thing that was finxed with r26506). I want to add a detail, but I do not kno

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 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 RDBM

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

2013-10-01 Thread Jukka Rahkonen
Even Rouault 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 -dial

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 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 interp

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

2013-09-30 Thread Jukka Rahkonen
Even Rouault 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 when the

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

2013-09-30 Thread Even Rouault
Le lundi 30 septembre 2013 19:22:21, aborruso a écrit : > Hi Jukka, > thank you. > > > Rahkonen Jukka wrote > > > I wonder where in the documentation would be the best place to mention > > this over-override trick. > > Probably in this moments it would be necessary to insert it in both pages >

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

2013-09-30 Thread aborruso
Hi Jukka, thank you. Rahkonen Jukka wrote > I wonder where in the documentation would be the best place to mention > this over-override trick. Probably in this moments it would be necessary to insert it in both pages you mentioned. Best regards, Andrea -- View this message in context: http

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

2013-09-30 Thread Jukka Rahkonen
aborruso gmail.com> writes: > > Only to add that if I try to read the same MySQL input using OGR Virtual > Format, the ST_Area function works properly. > > Thank you Hi, http://www.gdal.org/ogr/ogr_sql.html says: "All OGR drivers for database systems: MySQL, PostgreSQL and PostGIS (PG), Oracl

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

2013-09-30 Thread aborruso
Only to add that if I try to read the same MySQL input using OGR Virtual Format, the ST_Area function works properly. Thank you -- View this message in context: http://osgeo-org.1560.x6.nabble.com/sqlite-dialect-and-MySQL-spatial-input-tp5080909p5080911.html Sent from the GDAL - Dev mailing li

[gdal-dev] sqlite dialect and MySQL spatial input

2013-09-30 Thread aborruso
Hi all, I'm using sqlite dialect with shapefile input. An example is: ogrinfo poligoni_input.shp -dialect sqlite -sql "SELECT ST_Area(geometry) AS Area FROM poligoni_input" It works and it's a great feature. I have some problems with MySQL spatial input. I use this syntax: ogrinfo MYSQL:"mydb,us