Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tilemill .mbtiles problem #3

Closed
moovida opened this issue Sep 8, 2013 · 3 comments
Closed

Tilemill .mbtiles problem #3

moovida opened this issue Sep 8, 2013 · 3 comments

Comments

@moovida
Copy link
Member

moovida commented Sep 8, 2013

Reported by alessandro.battisti, Aug 28, 2013

I can't load a Tilemill .mbtiles (sard2.mbtiles) as basemap in Geopaparazzi 3.6.2, my log: http://www.pasteall.org/45206

I can load it only if I modify it with these sql commands (sard3.mbtiles):

create table android_metadata (locale text);
insert into android_metadata values ('en_US');

I'm using TileMill 0.10.1, Ubuntu 12.04 64 bit, Alcatel OT-997D, Android 4.0.4.

Data: http://ge.tt/1T6YJer?c

Error log:

08-28 09:56:25.471 I/SqliteDatabaseCpp(26615): sqlite returned: error code = 1, msg = no such table: android_metadata, db=/mnt/sdcard/geopaparazzi/geopaparazzi.db
08-28 09:56:25.471 E/SqliteDatabaseCpp(26615): SELECT locale FROM android_metadata failed
08-28 09:56:25.479 E/SQLiteDatabase(26615): Failed to open the database. closing it.
08-28 09:56:25.479 E/SQLiteDatabase(26615): android.database.sqlite.SQLiteException: no such table: android_metadata
08-28 09:56:25.479 E/SQLiteDatabase(26615): at android.database.sqlite.SQLiteDatabase.native_setLocale(Native Method)
08-28 09:56:25.479 E/SQLiteDatabase(26615): at android.database.sqlite.SQLiteDatabase.setLocale(SQLiteDatabase.java:2075)
08-28 09:56:25.479 E/SQLiteDatabase(26615): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:1014)
08-28 09:56:25.479 E/SQLiteDatabase(26615): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:986)
08-28 09:56:25.479 E/SQLiteDatabase(26615): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:962)
08-28 09:56:25.479 E/SQLiteDatabase(26615): at eu.geopaparazzi.spatialite.database.spatial.core.mbtiles.MBTilesDroidSpitter.open(MBTilesDroidSpitter.java:31)
08-28 09:56:25.479 E/SQLiteDatabase(26615): at eu.geopaparazzi.spatialite.database.spatial.core.MbtilesDatabaseHandler.getSpatialRasterTables(MbtilesDatabaseHandler.java:69)
08-28 09:56:25.479 E/SQLiteDatabase(26615): at eu.geopaparazzi.spatialite.database.spatial.SpatialDatabasesManager.getSpatialRasterTables(SpatialDatabasesManager.java:109)
08-28 09:56:25.479 E/SQLiteDatabase(26615): at eu.hydrologis.geopaparazzi.GeoPaparazziActivity.onCreate(GeoPaparazziActivity.java:158)

@moovida
Copy link
Member Author

moovida commented Sep 8, 2013

As also Luca commented on the old issue tracker, I also tested both databases and they both do work for me.
It looks like the android_metadata table is created by the android sqlite api automagically and in some cases (yours for example) it doesn't, for some reason.

@moovida
Copy link
Member Author

moovida commented Sep 29, 2013

since there has been no feedback on this and I can't reproduce it, I will close it.
If there are news feel free to re-open it.

@moovida moovida closed this as completed Sep 29, 2013
@mj10777
Copy link
Contributor

mj10777 commented Nov 30, 2013

This may be an issue with sqlite.SQLiteDatabase

  • sqlite_db.setLocale(Locale.getDefault());
    -- created this table

Non-android systems do not create such a useless table.
Maybe sqlite.SQLiteDatabase demands this when opening

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants