[
https://issues.apache.org/jira/browse/SIS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux resolved SIS-117.
-------------------------------------
Fix Version/s: 1.1
Assignee: Martin Desruisseaux
Resolution: Fixed
Added a {{WKTDictionary}} class. Users still have create it itself however; we
do not load automatically some {{myExtensions.wkt}} file for now.
The format has been [presented on the developer mailing
list|https://lists.apache.org/thread.html/r30aed9dbee9f9da157632fd6744a3a9c036f081326e80584eab17ee1%40%3Cdev.sis.apache.org%3E].
> Allow definition of custom CRS by properties files
> --------------------------------------------------
>
> Key: SIS-117
> URL: https://issues.apache.org/jira/browse/SIS-117
> Project: Spatial Information Systems
> Issue Type: New Feature
> Components: Referencing
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Minor
> Fix For: 1.1
>
>
> Coordinate Reference System (CRS) definitions will be provided by the EPSG
> database. However we need an easy for allowing users to provide their own
> CRS, because updating the EPSG database is uneasy. One of the easiest way is
> to provide a list of CRS as plain _key_ - _value_ pair, where the _key_ is
> the code and the _value_ is the CRS in WKT (Well Known Text) format. Such
> pairs can be provided in two ways:
> * As {{*.properties}} files
> * In the PostGIS {{spatial_refsys}} table.
> This issue is only about properties files.
> The above CRS codes are valid only in a namespace. The easiest way to specify
> the namespace would be to use the name of the properties file. So a
> {{“custom.properties”}} file might define the CRS in the {{CUSTOM}} namespace.
> One open question is where (in which directory) to put those files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
