Complete workflow for adding new ERA infrastructure elements to the railML-to-ERA conversion project. Use when implementing new element mappings from planning through testing.
Implement the ERA dual positioning model — TopologicalCoordinate (micro-topology offset) plus LinearPositioningSystemCoordinate (KilometricPost + offset) — for infrastructure elements. Use when writing or debugging any SPARQL CONSTRUCT query that positions an element on the network, or when understanding why an element is missing LRS or topology coordinates.
Implement ERA functional resources — classes such as ContactLineSystem, ETCS, TrainDetectionSystem that are NOT subclasses of InfrastructureElement and therefore carry no era:netReference. Instead they are referenced FROM tracks via properties like era:contactLineSystem, era:etcs, era:trainDetectionSystem. Use when adding a new functional resource type or debugging why a resource unexpectedly lacks netReference or geometry.
Mint correct URIs for ERA resource instances. Use when writing any BIND(IRI(...)) expression, choosing an ontology module path, or deciding whether to use the ERA namespace or a data provider namespace.
Determine spatial relationships between ERA infrastructure elements using network topology overlap matching. Use when inferring any relationship based on network position (containment, proximity, etc.) in post-processing or CONSTRUCT queries.
Compute GeoSPARQL WKT geometries for ERA network reference resources (NetPointReference, NetLinearReference, NetAreaReference) by interpolating against LinearElement LINESTRING geometries using Shapely linear referencing. Use when needing to calculate gsp:hasGeometry / gsp:asWKT triples to the graph after topology coordinates and topology is present.
Execute SPARQL queries against ERA ontology and railML source data using MCP servers. Use when querying ERA definitions, exploring railML structure, or analyzing source data for CONSTRUCT query development.
Query ERA ontology SHACL constraints to find required and important properties for infrastructure classes. Use when identifying missing properties, validating ontology compliance, or checking SHACL requirements for ERA infrastructure elements.