Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle measurement transformations #18

Open
DiegoVinasco opened this issue May 25, 2022 · 1 comment
Open

How to handle measurement transformations #18

DiegoVinasco opened this issue May 25, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@DiegoVinasco
Copy link
Contributor

Measurements in GML are a datatype+attribute composed of a value and a unit of measure (uom)

Shapechange proposes transforming these to the <http://shapechange.net/resources/ont/base#Measure> datatype which is a string containing both the value and the uom separated by a space. Although this solves the problem (a simpletype+attribute is transformed into a owl datatype), semantic data is lost when the decimal is transformed into a string.

Alternative:
Transform GML measure to the http://def.isotc211.org/iso19103/2005/UnitsOfMeasure#Measure or the http://def.isotc211.org/iso19103/2015/MeasureTypes#Measure class which can have value and uom datatype properties

@DiegoVinasco DiegoVinasco self-assigned this May 25, 2022
@DiegoVinasco DiegoVinasco added the enhancement New feature or request label May 25, 2022
@DiegoVinasco
Copy link
Contributor Author

these classes can be treated as an exception and the XML-to-OWL transformer can take them into account during #28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant