[
https://issues.apache.org/jira/browse/SIS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux resolved SIS-337.
-------------------------------------
Resolution: Fixed
New Maven module ready as of SVN revision 1811256. The new module is
{{org.apache.sis:non-free:sis-embedded-data}}. It does not have "epsg" in its
name because future versions will probably contains other resources than EPSG.
Note that this module is 3 times bigger than {{sis-epsg}} (3.4 Mb compared to
1.1 Mb), even if it currently contains only the EPSG data. In addition of being
more compact, {{sis-epsg}} is also more portable since it can be used with
PostgreSQL and HSQL.
If the {{SIS_DATA}} environment variable is defined and the referenced
directory exists, then the environment variable will have precedence over the
{{sis-embedded-data}} module. So this module is a convenience for avoiding the
need to define {{SIS_DATA}} and avoiding the need to write anything on user
machine, but user has the possibility to override.
> Package EPSG Derby DB in sis-epsg jar, eliminating the need for external
> SIS_DATA dir
> --------------------------------------------------------------------------------------
>
> Key: SIS-337
> URL: https://issues.apache.org/jira/browse/SIS-337
> Project: Spatial Information Systems
> Issue Type: Wish
> Components: Referencing
> Affects Versions: 0.7
> Reporter: Kevin Mehall
> Assignee: Martin Desruisseaux
> Fix For: 0.8
>
>
> Since [Derby
> supports|https://db.apache.org/derby/docs/10.7/devguide/cdevdeploy11201.html]
> read-only databases in .jar files, is there a reason that the
> `org.apache.sis.non-free:sis-epsg` package includes SQL source to create an
> external database, rather than the database itself?
> It would make deployment much easier if there were no need for a SIS_DATA
> directory and environment variable, and adding the dependency were the only
> thing necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
