If you know basic SQLite, there's almost nothing to learn. The API is 99% the same as the Android SQLite API (as of API level 15). The main difference is the packaging. Use org.spatialite.database.XYZ
instead of android.database.sqlite.XYZ
and org.spatialite.XYZ
instead of android.database.XYZ
. Same applies to the other classes - all platform SQLiteXYZ
classes have their Spatialite versions.
1) Have this in your project's build.gradle
:
allprojects {
repositories {
...
maven { url "https://jitpack.io" }
}
}
2) Add the following to your module's build.gradle
:
implementation 'com.github.sevar83:android-spatialite:<LATEST_VERSION>'
There is a very simple and useless example in the app
module. Another example is the SpatiAtlas experiment.
Works the same way as the platform SQLite. It's accessible through Java/JNI
wrappers around the Spatialite C library.
The Spatialite wrappers were derived and adapted from the platform SQLite wrappers (the standard Android SQLite API).
Simply: Spatialite = SQLite + advanced geospatial support.
Spatialite is a geospatial extension to SQLite. It is a set of few libraries written in C to extend SQLite with geometry data types and many SQL functions above geometry data. For more info: https://www.gaia-gis.it/gaia-sins/
Yes - http://www.gaia-gis.it/gaia-sins/spatialite-sql-4.4.0.html
No. It uses cursors - the suggested lightweight approach to access SQL used in the Android platform instead of the heavier JDBC.
Yes. It builds for arm64-v8a
and x86_64
. mips64
is not tested.
This library is distributed as multi-architecture AAR file. By default Gradle will produce a universal APK including the native .so libraries compiled for all supported CPU architectures. Usually that's unacceptable for large libraries like this. But that's easily fixed by using Gradle's "ABI splits" feature. The following gradle code will produce a separate APK per each architecture. The APK size is reduced few times.
android {
splits {
abi {
enable true
reset()
include "armeabi-v7a", "arm64-v8a", "x86", "x86_64"
}
}
}
}
Min SDK 16
SQLiteDatabase.loadLibs()
. Now it is automatically done.import org.spatialite.Cursor;
with import android.database.Cursor;
import org.spatialite.database.SQLite***Exception;
with import android.database.sqlite.SQLite***Exception;
UnsatisfiedLinkError: dlopen failed: library "libandroid_runtime.so" not found
should be no more. For more details: https://developer.android.com/about/versions/nougat/android-7.0-changes.html#ndk;SQLiteDatabase.loadLibs()
initialization call is not required anymore;org.spatialite.Cursor
interface. Used 'android.database.sqlite.Cursor' instead.SQLiteXyzException
classes. Their AOSP originals are used instead;The main ideas used here were borrowed from:
If you like this library, please consider...
Apache License 2.0