You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by "Martin Desruisseaux (JIRA)" <ji...@apache.org> on 2016/05/18 00:14:12 UTC
[jira] [Updated] (SIS-128) Implement the JSR-363 javax.measure
interfaces
[ https://issues.apache.org/jira/browse/SIS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Desruisseaux updated SIS-128:
------------------------------------
Affects Version/s: 0.7
0.4
0.5
0.6
Description:
We needs an implementation of JSR-363 to be used as a replacement of JSR-275. This is needed since the JSR-275 specification attempt has been rejected. Some existing implementations exist, especially the UOMo and JScience projects, but we also have some legacy classes that we could refactor. A possible advantage of the later approach is that we have to support some rather particular Unit, like the one used in NetCDF files (e.g. "degrees_east"), which may be easier in a custom implementation.
Some useful links:
* http://www.unitsofmeasurement.org/apidocs/index.html - the interfaces that we would have to implement.
* http://www.qudt.org/ - Quantities, Units, Dimensions and Data Types in OWL and XML (ontology).
* https://code.google.com/p/unit-ontology/ - apparently the same than above.
* http://portal.opengeospatial.org/files/?artifact_id=11498 - OGC Best Practice for specifying UoM in an OGC standard.
* https://www.seegrid.csiro.au/subversion/xmml/OGC/trunk/ExampleInstances/dictionaries/units.xml - a dictionary of unit symbols related to OGC standards.
* http://unitsofmeasure.org/trac/ - UCUM, a text format for units.
* https://github.com/keilw/mco - A Java script project derived from JSR-275.
* http://wiki.eclipse.org/Science_IWG - Open Source Initiative for Scientific Development Tools.
* http://jscience.org/ - JScience, one of available implementations.
* http://www.eclipse.org/uomo/ - an other implementation.
was:
We needs an implementation of {{org.unitsofmeasurement.Unit}} to be used as a replacement of JSR-275. This is needed since the JSR-275 specification attempt has been rejected. Some existing implementations exist, especially the UOMo and JScience projects, but we also have some legacy classes that we could refactor. A possible advantage of the later approach is that we have to support some rather particular Unit, like the one used in NetCDF files (e.g. "degrees_east"), which may be easier in a custom implementation.
Some useful links:
* http://www.unitsofmeasurement.org/apidocs/index.html - the interfaces that we would have to implement.
* http://www.qudt.org/ - Quantities, Units, Dimensions and Data Types in OWL and XML (ontology).
* https://code.google.com/p/unit-ontology/ - apparently the same than above.
* http://portal.opengeospatial.org/files/?artifact_id=11498 - OGC Best Practice for specifying UoM in an OGC standard.
* https://www.seegrid.csiro.au/subversion/xmml/OGC/trunk/ExampleInstances/dictionaries/units.xml - a dictionary of unit symbols related to OGC standards.
* http://unitsofmeasure.org/trac/ - UCUM, a text format for units.
* https://github.com/keilw/mco - A Java script project derived from JSR-275.
* http://wiki.eclipse.org/Science_IWG - Open Source Initiative for Scientific Development Tools.
* http://jscience.org/ - JScience, one of available implementations.
* http://www.eclipse.org/uomo/ - an other implementation.
Summary: Implement the JSR-363 javax.measure interfaces (was: Implement the org.unitsofmeasurement interfaces)
> Implement the JSR-363 javax.measure interfaces
> ----------------------------------------------
>
> Key: SIS-128
> URL: https://issues.apache.org/jira/browse/SIS-128
> Project: Spatial Information Systems
> Issue Type: Improvement
> Components: Utilities
> Affects Versions: 0.3, 0.4, 0.5, 0.6, 0.7
> Reporter: Martin Desruisseaux
>
> We needs an implementation of JSR-363 to be used as a replacement of JSR-275. This is needed since the JSR-275 specification attempt has been rejected. Some existing implementations exist, especially the UOMo and JScience projects, but we also have some legacy classes that we could refactor. A possible advantage of the later approach is that we have to support some rather particular Unit, like the one used in NetCDF files (e.g. "degrees_east"), which may be easier in a custom implementation.
> Some useful links:
> * http://www.unitsofmeasurement.org/apidocs/index.html - the interfaces that we would have to implement.
> * http://www.qudt.org/ - Quantities, Units, Dimensions and Data Types in OWL and XML (ontology).
> * https://code.google.com/p/unit-ontology/ - apparently the same than above.
> * http://portal.opengeospatial.org/files/?artifact_id=11498 - OGC Best Practice for specifying UoM in an OGC standard.
> * https://www.seegrid.csiro.au/subversion/xmml/OGC/trunk/ExampleInstances/dictionaries/units.xml - a dictionary of unit symbols related to OGC standards.
> * http://unitsofmeasure.org/trac/ - UCUM, a text format for units.
> * https://github.com/keilw/mco - A Java script project derived from JSR-275.
> * http://wiki.eclipse.org/Science_IWG - Open Source Initiative for Scientific Development Tools.
> * http://jscience.org/ - JScience, one of available implementations.
> * http://www.eclipse.org/uomo/ - an other implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)