[
https://issues.apache.org/jira/browse/SIS-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380781#comment-16380781
]
Martin Desruisseaux commented on SIS-350:
-----------------------------------------
Hello Umesh, and welcome!
Yes, there is remaining work to be done. A partial port to Android has been
done by Dinush during Google Summer of Code 2017 and is available there:
https://github.com/dinush/sis/commits/Android26
This work has not yet been merged to Apache SIS development branches however.
The reason is that the database accesses have been rewritten for using SQLite.
The use of SQLite is fine, but the replacement of every JDBC usage by
SQLite-specific API usage will make difficult to maintain this branch. A more
convenient solution for us would have been to use or create a "SQLite - JDBC"
bridge. If we could use SQLite through JDBC, it would allow us to have minimal
amount of changes on the development branch.
If you are interested in continuing this work, you are welcome! The next step
would be to look at Dinush commits and prepare a document that describe the
current state and why more work is needed. Note however we don't know yet if we
can have more than one student on Apache SIS this summer, so it would be safer
to prepare proposal for different projects in case.
> Port Apache SIS to Android
> --------------------------
>
> Key: SIS-350
> URL: https://issues.apache.org/jira/browse/SIS-350
> Project: Spatial Information Systems
> Issue Type: Task
> Components: Features, Metadata, Referencing, Storage, Utilities
> Reporter: Martin Desruisseaux
> Priority: Major
> Labels: gsoc2017, mentor
>
> Create an Apache SIS branch for Android. This will require the following work:
> * Simulate the JAXB framework if possible, or remove SIS usage of JAXB on the
> Android branch. JAXB is extensively used in the metadata modules, but some
> usages are found also in other modules.
> * Remove Java2D dependency. This work has already been anticipated by keeping
> Java2D dependency in separated classes or packages. When a replacement is
> available on the Android platform, the Java2D type should be substituted by
> the replacement. This should include in particular
> {{java.awt.geom.AffineTransform}}.
> * Get a JDBC implementation for SQLite. If needed, write code that adapt
> on-the-fly the SQL statements used for the creation of EPSG dataset to SQL
> statements compatible with SQLite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
