Home » railML newsgroups » railml.common » [Ontology v0.6] IntrinsicCoordinate & GeometricCoordinate vs GeoSPARQL (Should we make IntrinsicCoordinate a subclass of gsp:Feature?)
[Ontology v0.6] IntrinsicCoordinate & GeometricCoordinate vs GeoSPARQL [message #3523] Mon, 24 March 2025 12:33 Go to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 180
Registered: February 2025
Location: Brussels
Senior Member
Should we make IntrinsicCoordinate a subclass of gsp:Feature?

The result will be that IntrinsicCoordinate will inherit the property hasGeometry and thus the ability to position using geometric coordinates. The following classes and properties will no longer be necesary:

https://ontology.railml.org/#http://ontology.railml.org/rail topomodel#hasGeometricCoordinate
(including begin/end)

https://ontology.railml.org/#http://ontology.railml.org/rail topomodel#hasGeometricCoordinate
-> replaced with hasGeometry

https://ontology.railml.org/#http://ontology.railml.org/rail topomodel#GeometricPositioningSystem
-> The definition is included in one of the datatype properties of the instance that hasGeometry refers to

https://ontology.railml.org/#http://ontology.railml.org/rail topomodel#hasGeometricCoordinate


Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [Ontology v0.6] Common & Metadata class
Next Topic: Use railML to model parts of a large network
Goto Forum:
  


Current Time: Mon Nov 09 00:31:09 GMT+1 2026