Re: [Qgis-user] columns in spatialite

For different reasons I'm not fan or either geopackage and spatialite... Btw, you can reduce the size of the spatialite if you create it only with CR's of your data (and much Custer to create). A spatiallite with all CRS is 4mb... With a single crs is some k but with all spatial operators indside.

Re: [Qgis-user] columns in spatialite

On 11/13/2015 01:51 AM, Matthias Kuhn wrote: On 11/12/2015 07:25 PM, Alex M wrote: SQLite stores the geometries differently than Spatialite. http://www.gdal.org/drv_sqlite.html FORMAT=WKB/WKT/SPATIALITE Biggest side effect I can think

Re: [Qgis-user] columns in spatialite

This thread drifted off into some very interesting discussions of data exchange formats. But going back to the original problem - new columns, added in SL do not appear in QGIS: Sandro Furieri posted on the spatialite-users forum a pretty full explanation of

Re: [Qgis-user] columns in spatialite

On 11/12/2015 07:25 PM, Alex M wrote: > SQLite stores the geometries differently than Spatialite. > http://www.gdal.org/drv_sqlite.html > FORMAT=WKB/WKT/SPATIALITE > > Biggest side effect I can think of is that you can't use the spatialite > query mechanisms on WKB/WKT without converting. Which

Re: [Qgis-user] columns in spatialite

On 12/11/2015 14:10, Paulo van Breugel wrote: On Thu, Nov 12, 2015 at 1:05 PM, Bernd Vogelgesang wrote: Am 12.11.2015, 08:01 Uhr, schrieb Paolo Cavallini

Re: [Qgis-user] columns in spatialite

On Thu, Nov 12, 2015 at 1:05 PM, Bernd Vogelgesang wrote: > Am 12.11.2015, 08:01 Uhr, schrieb Paolo Cavallini : > > Il 12/11/2015 00:31, Bernd Vogelgesang ha scritto: >> >> So, to answer to Paolo's question about what is missing in DBManager: >>>

Re: [Qgis-user] columns in spatialite

Am 12.11.2015, 08:01 Uhr, schrieb Paolo Cavallini : Il 12/11/2015 00:31, Bernd Vogelgesang ha scritto: So, to answer to Paolo's question about what is missing in DBManager: Actually nothing in my case, cause I really do not want to use it at all. I just would like to be

Re: [Qgis-user] columns in spatialite

The main issues with spatialite are IMO: It's based on sqlite so deleting columns and renaming columns is not supported by design. We could offer some hacks to bypass this (annoying restriction) from the UI - there is a risk of side effects though. Another property of it is, that it's already

Re: [Qgis-user] columns in spatialite

I believe the main difference between SpatiaLite and Geopackage is that a SpatiaLite database contains a lot of query functionality and additional data (e.g. a big list of CRS) - while Geopackage does not When you checked filesizes for shp: did you only look at the shp, or also include dbf,

Re: [Qgis-user] columns in spatialite

On Thu, Nov 12, 2015 at 1:30 PM, Matthias Kuhn wrote: > The main issues with spatialite are IMO: It's based on sqlite so > deleting columns and renaming columns is not supported by design. We > could offer some hacks to bypass this (annoying restriction) from the UI > -

Re: [Qgis-user] columns in spatialite

Hi, I would prefer if we could concentrate on Geopackage. Geopackage is now an OGC format and should be (at least in theory) better supported in other (proprietary) GIS than SpatiaLite. Andreas On 2015-11-12 13:30, Matthias Kuhn wrote: > The main issues with spatialite are IMO: It's

Re: [Qgis-user] columns in spatialite

On Thu, Nov 12, 2015 at 3:48 PM, Neumann, Andreas wrote: > I believe the main difference between SpatiaLite and Geopackage is that a > SpatiaLite database contains a lot of query functionality and additional > data (e.g. a big list of CRS) - while Geopackage does not > That

Re: [Qgis-user] columns in spatialite

SQLite stores the geometries differently than Spatialite. http://www.gdal.org/drv_sqlite.html FORMAT=WKB/WKT/SPATIALITE Biggest side effect I can think of is that you can't use the spatialite query mechanisms on WKB/WKT without converting. Which includes spatial indexes (not sure anything in QGIS

Re: [Qgis-user] columns in spatialite

It works - mostly. I've had a few problems reading spatialite in ArcGIS 10.2.2 as of late - which may be to the fact I'm still on 10.2.2. My last attempt at moving a database from PostGIS to Spatialite and into ArcGIS ended up with ArcGIS crashing a lot - BUT - it could read the data. Randy

Re: [Qgis-user] columns in spatialite

I understand that the real spatialite format is not really knowed. The test you report is a read only test on the spatialite-gui. But the spatialite-gui is a all-version readable software. This mean that it is capable to read and understand EVERY VERSION of the spatialite format. Also the

Re: [Qgis-user] columns in spatialite

Yes we should implement a cheat in QGIS (core) to handle this issue. Other SQLite GUIs do this. Spatialite GUI and SQLite Manager (Firefox plugin). The basic process: 1. Make a new table the way you actually want it. 2. SQL INSERT records from Old to New (Mapping old columns to new if name

Re: [Qgis-user] columns in spatialite

Sure you can clarify there. I have tested spatialite in ArcGIS 10.2+ http://blog.geomusings.com/2013/08/07/spatialite-and-arcgis-10-dot-2/ http://www.northrivergeographic.com/archives/spatialite-arcgis-qgis Enjoy, Alex On 11/12/2015 08:57 AM, Andrea Peri wrote: > As the better ML for ask for

Re: [Qgis-user] columns in spatialite

The spatialite db contains spatial reference tables of projections. Thats where those MB come from. As Andrea pointed out the full answer of what else is in those MB would be on the Spatialite mailing list. -Alex On 11/12/2015 08:49 AM, Andrea Peri wrote: > You need study better the spatialite

Re: [Qgis-user] columns in spatialite

Le jeudi 12 novembre 2015 18:02:59, Alex M a écrit : > The spatialite db contains spatial reference tables of projections. > Thats where those MB come from. I confirm. Spatialite by defaults populates the spatial_ref_sys table with all the EPSG catalog (but you can actually remove all the ones

Re: [Qgis-user] columns in spatialite

Am 12.11.2015, 16:17 Uhr, schrieb Paulo van Breugel : On Thu, Nov 12, 2015 at 3:48 PM, Neumann, Andreas wrote: I believe the main difference between SpatiaLite and Geopackage is that a SpatiaLite database contains a lot of query

Re: [Qgis-user] columns in spatialite

The better ML where ask for any difference between the spatialite and the geopackega is the spatialite ML, where there are user skilled on spatialite use.rather than the QGIS ML where there are few user skilled in the spatialite use. So you could ask to them. Regards, A. 2015-11-12 17:49

Re: [Qgis-user] columns in spatialite

On 11/12/2015 04:12 AM, Micha Silver wrote: > On 12/11/2015 14:10, Paulo van Breugel wrote: >> >> >> On Thu, Nov 12, 2015 at 1:05 PM, Bernd Vogelgesang >> <bernd.vogelges...@gmx.de> wrote: >> >> Am 12.11.2015, 08:01 Uhr, schrieb Paolo Cavallini >>

Re: [Qgis-user] columns in spatialite

You are correct. In my mind the workflow is get GeoPackage -> up convert to Spatialite -> do work -> Convert to GeoPackage to give to other people. This is actually the same workflow that's been pushed in other software too. Get exchange format, import to internal best database format, do work,

Re: [Qgis-user] columns in spatialite

You need study better the spatialite formats. :) Also the shapefile format and also the geopackage format. So you will be able to understand why spatialite is 4mb and other not. :)) A. 2015-11-12 17:34 GMT+01:00 Bernd Vogelgesang : > Am 12.11.2015, 16:17 Uhr, schrieb

Re: [Qgis-user] columns in spatialite

Le jeudi 12 novembre 2015 19:25:20, Alex M a écrit : > SQLite stores the geometries differently than Spatialite. > http://www.gdal.org/drv_sqlite.html > FORMAivT=WKB/WKT/SPATIALITE > > Biggest side effect I can think of is that you can't use the spatialite > query mechanisms on WKB/WKT without

Re: [Qgis-user] columns in spatialite

Il 12/11/2015 00:31, Bernd Vogelgesang ha scritto: > So, to answer to Paolo's question about what is missing in DBManager: > Actually nothing in my case, cause I really do not want to use it at > all. I just would like to be able to act with spatialite layers as I am > able to do with ESRI

Re: [Qgis-user] columns in spatialite

Am 11.11.2015, 21:55 Uhr, schrieb X Of : Am 11.11.2015 um 07:59 schrieb Micha Silver: Unfortunately I easily forget how sql works, so doing "easy" stuff becomes very time consuming and frustrating. I think this is a usual problem for us non-regular SQL-users (for any

Re: [Qgis-user] columns in spatialite

Hi, You could probably try the last "master" QGIS and processing, as René-Luc (rldhont) added a couple of days ago the ability to save scripts and algs result layers into a spatialite database. Combined with the tool "Refactor" ( visible in the Processing toolbox), and using your initial

Re: [Qgis-user] columns in spatialite

Am 10.11.2015, 16:00 Uhr, schrieb kimaidou : Hi, You could probably try the last "master" QGIS and processing, as René-Luc (rldhont) added a couple of days ago the ability to save >scripts and algs result layers into a spatialite database. Combined with the tool

Re: [Qgis-user] columns in spatialite

Il 11/11/2015 00:16, Bernd Vogelgesang ha scritto: > 2015-11-10 15:42 GMT+01:00 Bernd Vogelgesang > >: > > Hi Micha, > > yeah, working with spatialite dbs "seriously" is still quite > uncomfortable. >

Re: [Qgis-user] columns in spatialite

The need for improved spatialite plugins aside, I still think that the QGIS provider for SL should pick up *all* attribute columns, even those after the geometry column. On 11/10/2015 04:42 PM, Bernd Vogelgesang wrote: Hi

Re: [Qgis-user] columns in spatialite

Hi, You are probably hitting issue 8923. This is more of a spatialite issue than a QGIS issue. But there is a workaround for it, see here: https://hub.qgis.org/issues/8923#note-5 Best regards Matthias On 11/10/2015 03:26 PM, Micha Silver wrote: > I have found that QGIS cannot "see" any

Re: [Qgis-user] columns in spatialite

Hi Micha, yeah, working with spatialite dbs "seriously" is still quite uncomfortable. When I try, I mostly have to use all available means to get the work done: DBManager, QSpatialite, SpatialiteGUI. Unfortunately I easily forget how sql works, so doing "easy" stuff becomes very time