Changes between Version 11 and Version 12 of SpatiaLite


Ignore:
Timestamp:
Jan 15, 2012, 7:24:30 AM (10 years ago)
Author:
aperi2007
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SpatiaLite

    v11 v12  
    2020$ ogr2ogr --config PG_LIST_ALL_TABLES YES --config PG_SKIP_VIEWS YES -f "SQLite" mydb.sqlite -progress PG:"dbname='mydb' \
    2121  active_schema=myschema schemas=myschema host='localhost' port='5432' user='myuser' password='mypass' " -lco LAUNDER=yes \
    22   -dsco SPATIALITE=yes -lco SPATIAL_INDEX=yes -gt 65536 -gt
     22  -dsco SPATIALITE=yes -lco SPATIAL_INDEX=yes -gt 65536
    2323}}}
    2424Some advertising: To avoid the lost of the third dimension exporting geometries you need use almost gdal 1.9.0 and spatialite library 3.0.0.[[BR]]
     
    2626of type TEXT that are also primary keys. To avoid this lost you should use the "single table" call.
    2727
     28[[BR]]
     29To load a table (mytable) (with a geometry columns named "geometry") from a Sqlite/Spatialite (mysqlite.sqlite) into a schema (myschema) of a Postgres/Postgis, using gdal 1.9.0 and spatialite 3.0.0:[[BR]]
     30
     31{{{
     32ogr2ogr --config SQLITE_LIST_ALL_TABLES YES -f "PostgreSQL" PG:"dbname='mydb' active_schema=myschema schemas=myschema host='localhost' port='5432' user='myuser' password='mypass' " -overwrite -lco SCHEMA=myschema -lco GEOMETRY_NAME=geometry -lco SPATIAL_INDEX=YES mysqlite.sqlite  mytable
     33}}}
     34