GEO Model
Contents
Summary
The GEO model helps to bridge the gap between Railway based masterdata and sensor based information (e.g. GPS positioning) by providing translation and search services.
Use Cases
UC1: Relate a point to the nearest track
With the provided point the service calculates the nearest track with the OSM start and end location.
- Input: GEO coordinates of a point
- Output: OSM track, OSM start location and OSM end location of track and the distances to the given point.
UC2: Relate to RINF segments
With a provided OSM track the service search the corresponding RINF segments. This can be smaller, equal or larger than the OSM track. If it is smaller several RINF segments are provided to match the whole stretch of the OSM track.
- Input: OSM track
- Output: RINF segments
UC3: Find nearest TAF location
With a provided OSM track or RINF segment the service search the nearest TAF location to “the right” and nearest to “the left”. The TAF location must not be on the track or segment. It can be also at a certain distance to it.
- Input: OSM track or RINF segment
- Output: TAF location “left”, TAF location “right” and their distances to the given track/segment.
The service calculates whether two given locations are belonging to the same MetaGare. A MetaGare clusters several locations together which are forming a larger station, shunting yard, terminal, port.
- Input: Two TAF locations
- Output: yes/no and which MetaGare they belong to.
UC5: Shape a location
The service search the suitable OSM shape for a provided set of coordinates. The shape is a OSM polygon.
- Input: GEO coordinates of a point
- Output: Railway layer based OSM polygon which relates to this point with the distance between them
UC6: Calculate distance between two locations
Given two locations the service calculates the shortest (bee line) distance as well as the shortest track based distance between them.
- Input: two locations with their GEO coordinates or their TAF CRD ID
- Output: shortest (bee line) and shortest track distance
