Re: [GRASS-user] SQLite connection - error
Hi Espen, the regular SQLite tables driver does not support geometry storage in SQLite databases. If you want to connect to a spatially enabled SQlite3 database, use v.in.ogr instead. Cheers, Ben - Original Message - Hi! I have tried to read the documentation and the mailing list for how to connect to a SQLite database. So far I have done this: 1. db.connect driver=sqlite database='/home/espen/db.sqlite' 2. Created a new vector map called test 3. v.db.connect map=test table=GSHHS_f_L2 -o key=PK_UID However I get this warning: WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported The table GSHHS_f_L2 is now part of vector map test and may be deleted or overwritten by GRASS modules And running v.info map=test show that the layer does not have any objects ++ | Layer: test | | Mapset: PERMANENT | | Location: newLocation | | Database: /home/espen/Dokumenter/grassdata | | Title: | | Map scale: 1:1 | | Map format: native | | Name of creator: espen | | Organization: | | Source date: Wed Jun 23 08:55:30 2010 | || | Type of Map: vector (level: 2) | || | Number of points: 0 Number of areas: 0 | | Number of lines: 0 Number of islands: 0 | | Number of boundaries: 0 Number of faces: 0 | | Number of centroids: 0 Number of kernels: 0 | || | Map is 3D: No | | Number of dblinks: 1 | || | Projection: Lat/Lon | | N: 0 S: 0 | | E: 0 W: 0 | || | Digitization threshold: 0 | | Comments: | || ++ Could anybody explain to me what the warning means, and why I cannot access the features? The only thing i can guess is that I can only use version 1 of SQLite? However, I am not familiar with the different versions of SQLite. Kind regards, Espen Isaksen ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user -- Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] SQLite connection - error
My understading from this page is that it is not possible to compile OGR with Grass write support? http://gdal.org/ogr/ogr_formats.html Am I wrong? This might indicate that write support is possible: http://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Espen 2010/6/24 Benjamin Ducke benjamin.du...@oxfordarch.co.uk: You could try compiling GDAL with GRASS support and using ogr2ogr directly to convert from the external format to GRASS. Ben - Original Message - Thanks Achim and Ben for your quick answers! I never even thought about that(a bit embarrassing really :-) ) I suppose that means I am back to the horribly slow import through v.in.ogr. Practically impossible for me to import a 100 mb shapefile. If anybody has suggestions for good performance, please go ahead and tell me. Espen 2010/6/24 Achim Kisseler achim.kisse...@jupiter.uni-freiburg.de: This is because SQLite is not SpatiaLite (SQLite with spatial extension). GRASS does not support SpatiaLite as far as I know. If you just want to use the Data from Spatiallite, you can export the tables as shape-files or csv and import these to GRASS. Hope it helps a bit, Achim Espen Isaksen schrieb: Hi! I have tried to read the documentation and the mailing list for how to connect to a SQLite database. So far I have done this: 1. db.connect driver=sqlite database='/home/espen/db.sqlite' 2. Created a new vector map called test 3. v.db.connect map=test table=GSHHS_f_L2 -o key=PK_UID However I get this warning: WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported The table GSHHS_f_L2 is now part of vector map test and may be deleted or overwritten by GRASS modules And running v.info map=test show that the layer does not have any objects ++ | Layer: test | | Mapset: PERMANENT | | Location: newLocation | | Database: /home/espen/Dokumenter/grassdata | | Title: | | Map scale: 1:1 | | Map format: native | | Name of creator: espen | | Organization: | | Source date: Wed Jun 23 08:55:30 2010 | || | Type of Map: vector (level: 2) | | | | Number of points: 0 Number of areas: 0 | | Number of lines: 0 Number of islands: 0 | | Number of boundaries: 0 Number of faces: 0 | | Number of centroids: 0 Number of kernels: 0 | | | | Map is 3D: No | | Number of dblinks: 1 | | | | Projection: Lat/Lon | | N: 0 S: 0 | | E: 0 W: 0 | | | | Digitization threshold: 0 | | Comments: | | | ++ Could anybody explain to me what the warning means, and why I cannot access the features? The only thing i can guess is that I can only use version 1 of SQLite? However, I am not familiar with the different versions of SQLite. Kind regards, Espen Isaksen ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user -- Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] SQLite connection - error
On Thu, Jun 24, 2010 at 10:35 AM, Espen Isaksen espen.isak...@gmail.com wrote: Thanks Achim and Ben for your quick answers! I never even thought about that(a bit embarrassing really :-) ) I suppose that means I am back to the horribly slow import through v.in.ogr. Practically impossible for me to import a 100 mb shapefile. If anybody has suggestions for good performance, please go ahead and tell me. You could try grass 7, see [1] Really big shapefiles like GADM v1 (gadm1.shp is 913 MB) will take at least 1 hour, though. Alternatively, get v.in.gshhs from grass-addons [2], get the original GSHHS data [3] and import those with v.in.gshhs Markus M [1] http://grass.osgeo.org/wiki/GRASS_7_ideas_collection#Radim.27s_TODO_list [2] http://grass.osgeo.org/wiki/GRASS_AddOns#v.in.gshhs [3] ftp://ftp.soest.hawaii.edu/pwessel/gshhs/gshhs_2.0.tbz 2010/6/24 Achim Kisseler achim.kisse...@jupiter.uni-freiburg.de: This is because SQLite is not SpatiaLite (SQLite with spatial extension). GRASS does not support SpatiaLite as far as I know. If you just want to use the Data from Spatiallite, you can export the tables as shape-files or csv and import these to GRASS. Hope it helps a bit, Achim Espen Isaksen schrieb: Hi! I have tried to read the documentation and the mailing list for how to connect to a SQLite database. So far I have done this: 1. db.connect driver=sqlite database='/home/espen/db.sqlite' 2. Created a new vector map called test 3. v.db.connect map=test table=GSHHS_f_L2 -o key=PK_UID However I get this warning: WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported The table GSHHS_f_L2 is now part of vector map test and may be deleted or overwritten by GRASS modules And running v.info map=test show that the layer does not have any objects ++ | Layer: test | | Mapset: PERMANENT | | Location: newLocation | | Database: /home/espen/Dokumenter/grassdata | | Title: | | Map scale: 1:1 | | Map format: native | | Name of creator: espen | | Organization: | | Source date: Wed Jun 23 08:55:30 2010 | || | Type of Map: vector (level: 2) | | | | Number of points: 0 Number of areas: 0 | | Number of lines: 0 Number of islands: 0 | | Number of boundaries: 0 Number of faces: 0 | | Number of centroids: 0 Number of kernels: 0 | | | | Map is 3D: No | | Number of dblinks: 1 | | | | Projection: Lat/Lon | | N: 0 S: 0 | | E: 0 W: 0 | | | | Digitization threshold: 0 | | Comments: | | | ++ Could anybody explain to me what the warning means, and why I cannot access the features? The only thing i can guess is that I can only use version 1 of SQLite? However, I am not familiar with the different versions of SQLite. Kind regards, Espen Isaksen ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] SQLite connection - error
Ok, so that means that grass 7 should be better at importing ogr vector formats then right? My 100 mb file has now been running for more than 24 hours and not done yet. My GSHHS data was really just a test, I need to import other large shapefiles as well. But thanks for the tip :-) Espen 2010/6/24 Markus Metz markus.metz.gisw...@googlemail.com: On Thu, Jun 24, 2010 at 10:35 AM, Espen Isaksen espen.isak...@gmail.com wrote: Thanks Achim and Ben for your quick answers! I never even thought about that(a bit embarrassing really :-) ) I suppose that means I am back to the horribly slow import through v.in.ogr. Practically impossible for me to import a 100 mb shapefile. If anybody has suggestions for good performance, please go ahead and tell me. You could try grass 7, see [1] Really big shapefiles like GADM v1 (gadm1.shp is 913 MB) will take at least 1 hour, though. Alternatively, get v.in.gshhs from grass-addons [2], get the original GSHHS data [3] and import those with v.in.gshhs Markus M [1] http://grass.osgeo.org/wiki/GRASS_7_ideas_collection#Radim.27s_TODO_list [2] http://grass.osgeo.org/wiki/GRASS_AddOns#v.in.gshhs [3] ftp://ftp.soest.hawaii.edu/pwessel/gshhs/gshhs_2.0.tbz 2010/6/24 Achim Kisseler achim.kisse...@jupiter.uni-freiburg.de: This is because SQLite is not SpatiaLite (SQLite with spatial extension). GRASS does not support SpatiaLite as far as I know. If you just want to use the Data from Spatiallite, you can export the tables as shape-files or csv and import these to GRASS. Hope it helps a bit, Achim Espen Isaksen schrieb: Hi! I have tried to read the documentation and the mailing list for how to connect to a SQLite database. So far I have done this: 1. db.connect driver=sqlite database='/home/espen/db.sqlite' 2. Created a new vector map called test 3. v.db.connect map=test table=GSHHS_f_L2 -o key=PK_UID However I get this warning: WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported The table GSHHS_f_L2 is now part of vector map test and may be deleted or overwritten by GRASS modules And running v.info map=test show that the layer does not have any objects ++ | Layer: test | | Mapset: PERMANENT | | Location: newLocation | | Database: /home/espen/Dokumenter/grassdata | | Title: | | Map scale: 1:1 | | Map format: native | | Name of creator: espen | | Organization: | | Source date: Wed Jun 23 08:55:30 2010 | || | Type of Map: vector (level: 2) | | | | Number of points: 0 Number of areas: 0 | | Number of lines: 0 Number of islands: 0 | | Number of boundaries: 0 Number of faces: 0 | | Number of centroids: 0 Number of kernels: 0 | | | | Map is 3D: No | | Number of dblinks: 1 | | | | Projection: Lat/Lon | | N: 0 S: 0 | | E: 0 W: 0 | | | | Digitization threshold: 0 | | Comments: | | | ++ Could anybody explain to me what the warning means, and why I cannot access the features? The only thing i can guess is that I can only use version 1 of SQLite? However, I am not familiar with the different versions of SQLite. Kind regards, Espen Isaksen ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] SQLite connection - error
No, unfortunately you are right. This is not an option for you. There is some severe inefficiency in the way v.in.ogr handles attribute and geometry data during import, which makes the whole process slow. Unfortunately, no one has yet stepped forward to re-design the logics (as far as I am aware). Ben - Espen Isaksen espen.isak...@gmail.com wrote: My understading from this page is that it is not possible to compile OGR with Grass write support? http://gdal.org/ogr/ogr_formats.html Am I wrong? This might indicate that write support is possible: http://grass.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin Espen 2010/6/24 Benjamin Ducke benjamin.du...@oxfordarch.co.uk: You could try compiling GDAL with GRASS support and using ogr2ogr directly to convert from the external format to GRASS. Ben - Original Message - Thanks Achim and Ben for your quick answers! I never even thought about that(a bit embarrassing really :-) ) I suppose that means I am back to the horribly slow import through v.in.ogr. Practically impossible for me to import a 100 mb shapefile. If anybody has suggestions for good performance, please go ahead and tell me. Espen 2010/6/24 Achim Kisseler achim.kisse...@jupiter.uni-freiburg.de: This is because SQLite is not SpatiaLite (SQLite with spatial extension). GRASS does not support SpatiaLite as far as I know. If you just want to use the Data from Spatiallite, you can export the tables as shape-files or csv and import these to GRASS. Hope it helps a bit, Achim Espen Isaksen schrieb: Hi! I have tried to read the documentation and the mailing list for how to connect to a SQLite database. So far I have done this: 1. db.connect driver=sqlite database='/home/espen/db.sqlite' 2. Created a new vector map called test 3. v.db.connect map=test table=GSHHS_f_L2 -o key=PK_UID However I get this warning: WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: unable to parse decltype: POLYGON WARNING: SQLite driver: column 'Geometry', SQLite type 2 is not supported The table GSHHS_f_L2 is now part of vector map test and may be deleted or overwritten by GRASS modules And running v.info map=test show that the layer does not have any objects ++ | Layer: test | | Mapset: PERMANENT | | Location: newLocation | | Database: /home/espen/Dokumenter/grassdata | | Title: | | Map scale: 1:1 | | Map format: native | | Name of creator: espen | | Organization: | | Source date: Wed Jun 23 08:55:30 2010 | || | Type of Map: vector (level: 2) | | | | Number of points: 0 Number of areas: 0 | | Number of lines: 0 Number of islands: 0 | | Number of boundaries: 0 Number of faces: 0 | | Number of centroids: 0 Number of kernels: 0 | | | | Map is 3D: No | | Number of dblinks: 1 | | | | Projection: Lat/Lon | | N: 0 S: 0 | | E: 0 W: 0 | | | | Digitization threshold: 0 | | Comments: | | | ++ Could anybody explain to me what the warning means, and why I cannot access the features? The only thing i can guess is that I can only use version 1 of SQLite? However, I am not familiar with the different versions of SQLite. Kind regards, Espen Isaksen ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user -- Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user -- Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.
