Difference between revisions of "Borders of RTM"
|Line 40:||Line 40:|
[[| RTM Modeling Concepts]] |[[RTM Use Cases and Application Examples]]
Revision as of 11:10, 1 April 2016
Comparison with other initiatives, norms and standards
Transmodel and RailTopoModel are both Conceptual Models dedicated to transportation, infrastructure and services. The main difference between these two models is the business and functional domain of coverage.
Transmodel is a European standard data model for public transport, designed to cover multiple transportation means (bus, tramway, trains…) in terms of interoperability, and the places where they meet each-other (e.g. stations, cities, towns, villages). The aim is to support operation, and more precisely schedule and plan journeys.
RailTopoModel has been developed for the specific needs of the railway sector, to precisely and consistently model network topology, rail infrastructure, and all railway objects and events, at any level of granularity (track, line, corridors…).
INSPIRE is a European directive which aims to create spatial data infrastructure for the European Union (EU). This will enable the sharing of environmental spatial information among public sector organisations and better facilitate public access to spatial information across Europe.
A European Spatial Data Infrastructure will assist in policy-making across boundaries. Therefore the spatial information considered under the directive is extensive and includes a great variety of topical and technical themes.
INSPIRE is based on a number of common principles:
- Data should be collected only once and kept where it can be maintained most effectively.
- It should be possible to combine seamless spatial information from different sources across Europe and share it with many users and applications.
- It should be possible for information collected at one level/scale to be shared across all levels/scales; detailed for thorough investigations, general for strategic purposes.
- Geographic information needed for good governance at all levels should be readily and transparently available.
- It should be possible to easily find what geographic information is available, how it can be used to meet a particular need, and under which conditions it can be acquired and used.
- Within INSPIRE, topology is handled in the data specification implicitly rather than explicitly, with the main reason to keep the model as simple as possible, but with the expectation that most applications will use the network data within a topological environment. There is therefore a prerequisite for “implicit topology”, where the data provided must be sufficiently clean and capable of automated topological construction within a user’s application. This concept is framed with the specific requirements, including data quality information.
RailTopoModel will ensure the minimum consistency with INSPIRE specifications, including geographical positioning and dimensions.
Main norms and standards in transportation
- IFOPT: An approved Technical Standard for location referencing in public transport.
- SIRI: The Service Interface for Real time Information covers transit communications between centres, and centre’s transit vehicles. SIRI provides traveller information on real-time transit vehicle location, predicted transit vehicle arrival/departure time, and predicted transit trip travel time.
- TransXChange: UK national XML based data standard for the interchange of bus route and timetable information between bus operators, the Vehicle and Operator Services Agency, local authorities and passenger transport executives, and others involved in the provision of passenger information.
- NeTEx: Network and Ticketing Exchange protocol for communicating timetable and fares details.
- TRIDENT: TRansport Intermodality Data sharing and Exchange NeTwork. Standard exchange data format for multimodal interoperability between RUs and service providers.
- DJPS: Exposed interface standard for distributed journey planning systems.
Transport mode borders
|Back To||Previous Chapter||Next Chapter|
|Main Page||RTM Modeling Concepts||RTM Use Cases and Application Examples|