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

Add RailwayLocation Kilometer for OperationalPoints to the mappings #19

Closed
stefanbischof opened this issue Dec 15, 2020 · 1 comment
Closed

Comments

@stefanbischof
Copy link

In the RINF XML the OperationalPoint element contains a OPRailwayLocation element with a Kilometer attribute. For example:

<OperationalPoint ValidityDateStart="2020-03-15" ValidityDateEnd="2099-12-31">
  <OPName Value="Feldkirch-Amberg" />
  <UniqueOPID Value="ATFk H1     " />
  <OPTafTapCode IsApplicable="Y" Value="AT02321" />
  <OPType Value="70" OptionalValue="passenger stop" />
  <OPGeographicLocation Longitude="+9,6216551" Latitude="47,2557051" />
  <OPRailwayLocation Kilometer="44,855" NationalIdentNum="10105" />

Currently this Kilometer location is absent from the extracted data but would be important to know.

julianrojas87 added a commit that referenced this issue Jan 28, 2021
Mappings for #19 and better URI strategy
julianrojas87 added a commit that referenced this issue Jan 28, 2021
Fix for #19 and better URI strategy
@julianrojas87
Copy link
Owner

julianrojas87 commented Jan 29, 2021

In v1.2.0 we have added new mapping rules to include the kilometer point of Operational Points. This is an example of how is this data modelled in the Knowledge Graph:

<#OP_1> a era:OperationalPoint ;
    era:lineReference <#LR_55_34.67>, <#LR_27_3.4> .

<#LR_55_34.67> a era:LineReference ;
    era:lineNationalId <#LNI_55> ;
    era:kilometer 34.67^^xsd:double .

<#LR_27_3.4> a era:LineReference ;
    era:lineNationalId <#LNI_27> ;
    era:kilometer 3.4^^xsd:double .

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

No branches or pull requests

2 participants