OpenJUMP with SpatialLite - Revision history

Edso: /* Getting the plugin and SQLite driver */

2013-04-09T14:24:34Z

Getting the plugin and SQLite driver

Edso: /* Introduction */

2013-04-09T14:23:38Z

Introduction

Jratike80: /* Introduction */

2011-08-24T08:51:54Z

Introduction

Jratike80: /* Updating attribute values with Spatialite Reader Plugin */

2010-02-09T10:29:55Z

Updating attribute values with Spatialite Reader Plugin

Jratike80 at 10:18, 9 February 2010

2010-02-09T10:18:56Z

Jratike80 at 10:07, 9 February 2010

2010-02-09T10:07:18Z

Jratike80 at 09:43, 9 February 2010

2010-02-09T09:43:58Z

Jratike80 at 09:03, 9 February 2010

2010-02-09T09:03:09Z

Jratike80 at 08:42, 9 February 2010

2010-02-09T08:42:15Z

Jratike80 at 08:12, 9 February 2010

2010-02-09T08:12:34Z

@@ Line 151: / Line 151: @@
 === Getting the plugin and SQLite driver ===
-Go to http://sourceforge.net/projects/jump-pilot/files/p_database_plugins/p_SpatialLite_reader_plugin/1.1/spatialliteplugin1.1.zip/download and download the plugin.
+Go to https://sourceforge.net/projects/jump-pilot/files/OpenJUMP_plugins/Database%20Plugins/SpatialLite_reader_plugin/ and download the plugin.
 The readme.txt file is listing two URLs for downloading Spatialite precompiled libraries and SQLite3 JDBC driver. However, the zip file contained all the drivers needed for Windows. The plugin is using platform dependent components and for Linux and OS X users the plugin won't work as it is.

@@ Line 2: / Line 2: @@
 There are two plugins that allow to use SpatiaLite with OpenJUMP:
 * the [http://sourceforge.net/projects/jumpdbqplugin/files/ JUMP DB Query Plugin]
-* a separate Spatialite Reader Plugin available [http://sourceforge.net/projects/jump-pilot/files/p_database_plugins/p_SpatialLite_reader_plugin/SpatialitePlugin.zip/download here] Note! Does not work properly with OpenJUMP 1.4. Use version 1.3 instead.
+* a separate Spatialite Reader Plugin available [https://sourceforge.net/projects/jump-pilot/files/OpenJUMP_plugins/Database%20Plugins/SpatialLite_reader_plugin/ in OJ plugins files section].
 == Using SpatiaLite with DB Query Plugin ==

@@ Line 2: / Line 2: @@
 There are two plugins that allow to use SpatiaLite with OpenJUMP:
 * the [http://sourceforge.net/projects/jumpdbqplugin/files/ JUMP DB Query Plugin]
-* a separate Spatialite Reader Plugin available [http://sourceforge.net/projects/jump-pilot/files/p_database_plugins/p_SpatialLite_reader_plugin/SpatialitePlugin.zip/download here]
+* a separate Spatialite Reader Plugin available [http://sourceforge.net/projects/jump-pilot/files/p_database_plugins/p_SpatialLite_reader_plugin/SpatialitePlugin.zip/download here] Note! Does not work properly with OpenJUMP 1.4. Use version 1.3 instead.
 == Using SpatiaLite with DB Query Plugin ==

@@ Line 198: / Line 198: @@
 === Updating attribute values with Spatialite Reader Plugin ===
-It is not possible to update Spatialite features which are read into OpenJUMP. However, because of the SQL window of the plugin everything that is possible to do with Spatialite SQL can be done through the plugin as well. For example, updating the "roads" layer by changing all maxpeed=0 values into null (empty) values goes easily. Error message "No ResultSet was produced" indicates only that nothing was selected from the database.
+It is not possible to update Spatialite features which are read into OpenJUMP. However, the SQL window of the plugin connects directly to SpatiaLite database and thus everything that can be done with Spatialite SQL is doable through the plugin as well. For example, updating the "roads" layer by changing all maxpeed=0 values into null (empty) values goes easily. Error message "No ResultSet was produced" indicates only that nothing was selected from the database. A new query SELECT * FROM roads will show that the values were really updated.
 [[File:Spatialitereader_10.png]]

@@ Line 4: / Line 4: @@
 * a separate Spatialite Reader Plugin available [http://sourceforge.net/projects/jump-pilot/files/p_database_plugins/p_SpatialLite_reader_plugin/SpatialitePlugin.zip/download here]
-== Using SpatialLite with DB Query Plugin ==
+== Using SpatiaLite with DB Query Plugin ==
 this has been written by Jukka:
@@ Line 138: / Line 138: @@
   SELECT * from TABLE LIMIT 1000
-== Using SpatialLite with Spatialite Reader Plugin (under construction)==
+== Using SpatiaLite with Spatialite Reader Plugin ==
 === Installing and using JUMP Spatialite Reader Plugin with Spatialite databases ===

@@ Line 78: / Line 78: @@
 [[File:Dbqyery_image006.png]]
-Feed in the table name to be used in the database, projection of the data and character encoding (with Geofabrik shapefile the correct setting is probably UTF-8 but there were some import problems when using if).
+Feed in the table name to be used in the database, projection of the data and character encoding (with Geofabrik shapefile the correct setting is probably UTF-8 but there were some import problems when using it).
 [[File:Dbqyery_image007.png]]
@@ Line 102: / Line 102: @@
 [[File:Dbqyery_image012.png]]
-The result of the query. Maximum speed of zero feels so odd that we will return to this later.
+The result of the query.
 [[File:Dbqyery_image013.png]]
@@ Line 110: / Line 110: @@
 [[File:Dbqyery_image014.png]]
-The result of the query above.
+The result of the query above. Maximum speed of 0 km/h may feel odd. We will return to this later.
 [[File:Dbqyery_image015.png]]

← Older revision		Revision as of 09:03, 9 February 2010
Line 195:		Line 195:

	[[File:Spatialitereader_09.png]]		[[File:Spatialitereader_09.png]]
		+
		+	=== Updating attribute values with Spatialite Reader Plugin ===
		+
		+	It is not possible to update Spatialite features which are read into OpenJUMP. However, because of the SQL window of the plugin everything that is possible to do with Spatialite SQL can be done through the plugin as well. For example, updating the "roads" layer by changing all maxpeed=0 values into null (empty) values goes easily. Error message "No ResultSet was produced" indicates only that nothing was selected from the database.
		+
		+	[[File:Spatialitereader_10.png]]

← Older revision		Revision as of 08:42, 9 February 2010
Line 161:		Line 161:

	The next examples are using the same Spatialite database as the previous tests with DB Query Plugin. The database is just renamed to "spatialitereader_test.sqlite"		The next examples are using the same Spatialite database as the previous tests with DB Query Plugin. The database is just renamed to "spatialitereader_test.sqlite"
		+
		+	[[File:Spatialitereader_01.png]]
		+
		+	Start via menu with Select Layer - Import Spatialite Layer
		+
		+	[[File:Spatialitereader_02.png]]
		+
		+	Press the only active button "+" and search the Spatialite database file.
		+
		+	[[File:Spatialitereader_03.png]]
		+
		+	The whole database structure comes visible.
		+
		+	[[File:Spatialitereader_04.png]]
		+
		+	By double clicking the layer title "roads" the SELECT clause is created automatically. You can also write is directly to the text box. The second button "SQL >" makes the query and lists results in the form without transferring them into OpenJUMP map yet.
		+
		+	[[File:Spatialitereader_05.png]]
		+
		+	After pressing the third button the query results, including geometries, are sent to OpenJUMP.
		+
		+	[[File:Spatialitereader_06.png]]
		+
		+	With the Spatialite reader plugin you can reach all the Spatialite functions through a menu. Menu items have tooltip help entries and double click tranfers a prototype text into query window. This query will return the road geometries in WGS84 UTM zone 33 projection (EPSG:32633).
		+
		+	[[File:Spatialitereader_07.png]]
		+
		+	Berlin roads reprojected from the native EPSG:4326 into EPSG:32633 by Spatialite. Note: This is possible only if the "spatial_ref_sys" table contains definitions for both the input and output projections. All the databases created with Spatialite-GUI tool have definitions for 3519 different projections.
		+
		+	[[File:Spatialitereader_08.png]]
		+
		+	This is not a Spatialite tutorial, but these two screenshots should give some idea about what kind of operations can be done inside Spatialite and visualised with OpenJUMP
		+
		+	[[File:Spatialitereader_09.png]]

← Older revision		Revision as of 08:12, 9 February 2010
Line 139:		Line 139:

	== Using SpatialLite with Spatialite Reader Plugin (under construction)==		== Using SpatialLite with Spatialite Reader Plugin (under construction)==
		+
		+	=== Installing and using JUMP Spatialite Reader Plugin with Spatialite databases ===
		+
		+	Tested with:
		+	* Windows XP
		+	* Java 1.6.0_ 06
		+	* OpenJUMP 1.3.1
		+	* Spatialite Reader Plugin version 1.1
		+
		+	=== Getting the plugin and SQLite driver ===
		+
		+	Go to http://sourceforge.net/projects/jump-pilot/files/p_database_plugins/p_SpatialLite_reader_plugin/1.1/spatialliteplugin1.1.zip/download and download the plugin.
		+
		+	The readme.txt file is listing two URLs for downloading Spatialite precompiled libraries and SQLite3 JDBC driver. However, the zip file contained all the drivers needed for Windows. The plugin is using platform dependent components and for Linux and OS X users the plugin won't work as it is.
		+
		+	=== Installation ===
		+
		+	Windows users can just unzip the spatialliteplugin1.1.zip into bin\ext folder of OpenJUMP and the plugin is ready for use. After successful installation there is a new menu item: Layer - Import Spatialite Layer.
		+
		+	=== Using Spatialite Reader Plugin ===
		+
		+	The next examples are using the same Spatialite database as the previous tests with DB Query Plugin. The database is just renamed to "spatialitereader_test.sqlite"