Search Results

In order to merge all features into one, you should do: ogr2ogr output.shp input.shp -dialect sqlite -sql "SELECT ST_Union(geometry) AS geometry FROM input" where geometry is the special field used … in order to represent the geometry of the features in SQLite SQL dialect and input in the SQL statement is the input layer name. …

Using GDAL >= 1.10.0 compiled with SQLite and SpatiaLite, you can: Given a specific search radius (e.g. 5), calculate the buffers around your points: ogr2ogr buffers.shp points.shp -dialect sqlite -sql … "SELECT ST_Buffer(geometry,5) from points" Calculate the clusters: ogr2ogr clusters.shp buffers.shp -dialect sqlite -sql "SELECT ST_Union(geometry) from buffers" -explodecollections Wrap points.shp …

So it should be: ogr2ogr nodateline\new_polygons.shp org_polygon.shp -dialect sqlite -sql "SELECT ShiftCoords(geometry, 360, 0), * FROM org_polygon WHERE X(geometry)<0" However, X(geometry) is not suitable …

If infile* are SpatiaLite datasources and intable* the table names, try with: ogr2ogr -f sqlite -dsco SPATIALITE=YES " !outfile!.sqlite !infile1! -nln !outfile! … -dialect sqlite -sql "SELECT ST_Intersection(A.geometry, B.geometry) AS geometry, A.name, B.name FROM !infile2!.!intable2! A, !infile3!.!intable3! …

Source: http://www.gdal.org/ogr/ogr_sql_sqlite.html So you need to build GDAL (>= 1.10) against SQLite (>= 3.6) and SpatiaLite (>= 3.0) in order to use the -dialect SQLite option. … In order to understand which versions of SQLite and (eventually) SpatiaLite you are using, simply execute: ogrinfo foo.shp -dialect sqlite -sql "select sqlite_version()" ogrinfo foo.shp -dialect sqlite …

</OGRVRTLayer> <OGRVRTLayer name="overlap"> <SrcDataSource>overlap.shp</SrcDataSource> </OGRVRTLayer> </OGRVRTDataSource> Then you can execute: ogr2ogr output.shp test.vrt -dialect sqlite …