Spatialite-gui

272 views
Skip to first unread message

Stephen Knox

unread,
Aug 8, 2018, 7:56:29 PM8/8/18
to spatiali...@googlegroups.com
I've built spatialite_gui on linux from the latest sources, and it runs, but I seem to be having some runtime issues.

I keep getting the error "SQLite SQL error: no such table: temp.sqlite_master" and the tables are not showing, either for new or existing dbs.

The errors in the console are

CreateVectorCoveragesTable() error: libspatialite was built by disabling Topology
and
InitSpatiaMetaDataFull() error:"(null)"

The about dialog shows:

spatialite_gui 2.1.0-beta0
a GUI-tool for SQLite / SpatiaLite

wxWidgets version 3.0.2
SpatiaLite version 5.0.0-beta0
RasterLite2 version 1.1.0-beta0
SQLite version 3.11.0
GEOS version 3.5.1-CAPI-1.9.1 r4246
PROJ.4 version Rel. 4.9.2, 08 September 2015
LIBXML2 version 2.9.3
VirtualPG version 2.0.0-RC0
PQlib (PostgreSQL client) version 10.00.04

SQLite's extensions: 'SpatiaLite', 'VirtualShape', 'VirtualDbf',
'VirtualXL', 'VirtualText', 'VirtualXPath', 'VirtualNetwork',
'RTree', 'MbrCache', 'VirtualBBox', 'VirtualFDO', 'VirtualGPKG',
'RasterLite2'

Target CPU x86_64-linux-gnu

Any clue for what is going wrong, as I am a little stuck.

Thanks

Stephen

a.fu...@lqt.it

unread,
Aug 8, 2018, 9:52:26 PM8/8/18
to spatiali...@googlegroups.com
On Thu, 9 Aug 2018 00:56:16 +0100, Stephen Knox wrote:
> CreateVectorCoveragesTable() error: libspatialite was built by
> disabling Topology
>
> Any clue for what is going wrong, as I am a little stuck.
>

Hi Stephen,

as the error message reports, you have built libspatialite
by keeping the Topology support disabled.

this is the standard default configuration when building
libspatialite, and is adopted so to fully preserve the
most liberal MPL licence.
but the GUI absolutely requires both Topology and Ground
Control Points (GCP) support, although this automatically
implies escalating to a stricter GPL licence.

solution: you just have to rebuild libspatialite after
specifying the appropriate configuration options required
by the GUI:

./configure --enable-rttopo=yes --enable-gcp=yes

note: the next BETA version of the GUI that will be released
will check in its ./configure script for a full fledged
libspatialite supporting Topology.

note #2: you have to build librttopo before attempting to
build libspatialite with Topology support enabled.
The sources of librttopo-1.1.0-RC1 are available from here:

https://git.osgeo.org/gitea/rttopo/librttopo/archive/librttopo-1.1.0-RC1.tar.gz

bye Sandro

Stephen Knox

unread,
Aug 12, 2018, 5:51:56 PM8/12/18
to spatiali...@googlegroups.com
Thanks Sandro.

This gets rid of the warnings in the console, and I now have

spatialite_gui 2.1.0-beta0

wxWidgets version 3.0.2
SpatiaLite version 5.0.0-beta0
RasterLite2 version 1.1.0-beta0
SQLite version 3.11.0
GEOS version 3.5.1-CAPI-1.9.1 r4246
PROJ.4 version Rel. 4.9.2, 08 September 2015
RTTOPO version 1.1.0-dev

LIBXML2 version 2.9.3
VirtualPG version 2.0.0-RC0
PQlib (PostgreSQL client) version 10.00.04

SQLite's extensions: 'SpatiaLite', 'VirtualShape', 'VirtualDbf',
'VirtuagetlXL', 'VirtualText', 'VirtualXPath', 'VirtualNetwork',

'RTree', 'MbrCache', 'VirtualBBox', 'VirtualFDO', 'VirtualGPKG',
'RasterLite2'

But I still can't see any tables in new or existing spatialite databases, and continue to get the "SQLite SQL error: no such table: temp.sqlite_master" error.

This is what the system version is showing (which does work)

spatialite_gui 2.0.0-devel
a GUI-tool for SQLite / SpatiaLite

wxWidgets version 3.0.2
SpatiaLite version 5.0.0-beta0
RasterLite2 version 1.1.0-beta0
SQLite version 3.11.0
GEOS version 3.5.1-CAPI-1.9.1 r4246
PROJ.4 version Rel. 4.9.2, 08 September 2015
LIBXML2 version 2.9.3

SQLite's extensions: 'SpatiaLite', 'VirtualShape', 'VirtualDbf',
'VirtualXL', 'VirtualText', 'VirtualXPath', 'VirtualNetwork',
'RTree', 'MbrCache', 'VirtualBBox', 'VirtualFDO', 'VirtualGPKG',
'RasterLite2'

is it the sqlite version that is too old?

Stephen

--
You received this message because you are subscribed to the Google Groups "SpatiaLite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spatialite-use...@googlegroups.com.
To post to this group, send email to spatiali...@googlegroups.com.
Visit this group at https://groups.google.com/group/spatialite-users.
For more options, visit https://groups.google.com/d/optout.

a.fu...@lqt.it

unread,
Aug 13, 2018, 5:11:50 PM8/13/18
to spatiali...@googlegroups.com
On Sun, 12 Aug 2018 22:51:42 +0100, Stephen Knox wrote:
> But I still can't see any tables in new or existing spatialite
> databases, and continue to get the "SQLite SQL error: no such table:
> temp.sqlite_master" error.
>
> is it the sqlite version that is too old?
>

Hi Stephen,

this issue is surely caused by an obsolete libsqlite3, but SQLite
is on its good right whilst SpatiaLite is wrong .. sorry for this.

all recent versions of SQLite are able to understand that an SQL
query referencing "temp.sqlite_master" intends to query the internal
master table reporting about all the DB objects being currently
defined into the TEMP database.
but the dcumentation is crystal clear; the standard name expected
by SQLite for referencing that special meta-table is
"sqlite_temp_master".

I've done a little testing: it effectively seems that
"sqlite_temp_master"
is correctly recognized by all versions, both olds and news.
but only the most recent versions can recognize the alternative form
"temp.sqlite_master" that is a someway tainted notation.

quick workaround: just edit the Main.cpp source.
at line 8708 you simply have to replace "temp.sqlite_master" with
"sqlite_temp_master", then save and exit.

run once again make/make install, and this time spatialite_gui
2.1.0-beta0 will surely work as expected ;-)

bye Sandro

Stephen Knox

unread,
Aug 14, 2018, 4:18:46 AM8/14/18
to SpatiaLite Users
All working,

Thanks Sandro.

Stephen
Reply all
Reply to author
Forward
0 new messages