Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Geopackage support #180
Looking back, I think the issue was related to database indexing. There is a project which converts raster tiles in geopackage into osmdroid format (see the wiki/related projects). Including the NGA package with an example in osmdroid is feasible, however vector data probably wont' be supportable (at least easily)…
On Wed, Jan 4, 2017 at 1:56 PM, legrostdg ***@***.***> wrote: It would be cool to support geopackage directly in osmdroid: it is a standard and is supported by gdal, which permits conversion from a lot of formats. Maybe the performance of geopackage-android has improved during the last year? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#180 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4kGY8fbjJk8HqQf_l8dFvkJxX7LAgjks5rO-t7gaJpZM4GWhey> .
i think the reason why it wasn't originally merged has the version at the time had a lot of dependencies on google libraries, which i don't like and it sort makes understanding the licensing, complicated.
i also wanted to just included it with the samples osmdroid app, however the minsdk is 8 for osmdroid. the NGA stuff enforces a minsdk of 14. Enforcing that for the sample app would significantly reduce our test coverage unfortunately but it may be worth it. Maybe we can split up the sample app somehow to have a version for travis with a low minsdk but publish to the play store a version with everything in it.
@spyhunter99 unfortunately I reported this as the user, not as a coder, as I don't speak java... I would be happy to assist if it could be coded in haskell or python!
I think this worth increasing the minsdk but you are the one who decides :-).
Thanks a lot for taking time on this issue!