sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Mehall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SIS-337) Package EPSG Derby DB in ​sis-epsg jar, eliminating the need for external SIS_DATA dir
Date Thu, 26 Jan 2017 20:27:24 GMT

    [ https://issues.apache.org/jira/browse/SIS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840384#comment-15840384
] 

Kevin Mehall commented on SIS-337:
----------------------------------

For our use case, we don't know which EPSG codes are going to be used ahead of time and need
the full database. We allow users to input coordinates with an arbitrary EPSG code attached.

> 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
>
> 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.3.4#6332)

Mime
View raw message