6.4.18 Generic Network Model
From Geostandards
6 INSPIRE
6.1 Background and Motivation
- 6.1.1 Spatial Data Infrastructures
- 6.1.2 Requirements for a European SDI
- 6.1.3 Existing foundation for a European SDI
- 6.2.1 Background and history
- 6.2.2 The five components of the Directive
- 6.2.3 Implementation, status and schedule
- 6.2.4 Groups and responsibilities within INSPIRE
- 6.2.5 INSPIRE Implementing Rules and INSPIRE Guidance Documents
- 6.2.6 European and Global initiatives in the context of INSPIRE
6.3 Technical Architecture Overview
- 6.3.1 Relationship between the different components, in particular spatial data, metadata, registers, and network services
- 6.3.2 Terminology
6.4 Interoperabilty of spatial data sets / INSPIRE data specifications
- 6.4.1 Requirements of the INSPIRE Directive
- 6.4.2 Interoperability of spatial data
- 6.4.3 INSPIRE data scope
- 6.4.4 Modelling Framework
- 6.4.5 Generic Conceptual Model
- 6.4.6 ISO 19100 series of International Standards
- 6.4.7 Rules for application schemas and feature catalogues
- 6.4.8 Identifier Management
- 6.4.9 Object referencing modelling
- 6.4.10 Coordinate referencing
- 6.4.11 Multi-lingual text and cultural adaptability
- 6.4.12 Data quality
- 6.4.13 Metadata for evaluation and use
- 6.4.14 Multiple representations
- 6.4.15 Consistency between data
- 6.4.16 Portrayal model
- 6.4.17 Conformance
- 6.4.18 Generic Network Model
- 6.4.19 Gazetteers
- 6.4.20 Encoding and data formats
- 6.4.21 INSPIRE registers
- 6.4.22 Annex I data specifications
- 6.4.23 Outlook to Annex II/III data specifications
- 6.4.24 Extensions by countries or communities
The Generic Network Model (package “Network” in the UML model) contains an application schema for networks. The types defined in the application schema provide basic capabilities that are supposed to be extended in application schemas of the relevant spatial data themes, i.e. transport networks and hydrography from the list of themes in annex I.
The main type is the network element which may be any element that is relevant for a network. In particular the following network elements are included in this network model:
- Nodes are 0-dimensional network elements that may connect links. Example: A junction in a road network.
- Links are 1-dimensional network elements. Example: A continuous segment in a road network from one junction to another.
- Areas are 2-dimensional network elements. Example: A large square in a road network.
- Network connections are network elements where it is possible to move from one network to another. Example: At a train station it is usually possible for a traveller to change from the road network to the railway network.
- Grade separated crossing are locations where two network elements intersect in a 2D projection, but where there is no physical connection of the network elements. Example: Two roads separated by a bridge.
- Aggregated links are sequences of links. Example: A route along a road network.
In application schemas that are related to networks, phenomena are often spatial referenced indirectly by a reference to a network element instead of a geometry.
For phenomena that are located along a link, their spatial reference usually applies to a part of the link only. Linear referencing may be used to describe such references. Where applicable, an offset can be provided.
The data types shown in the figure above may also be used to specify network properties in an application schema as attributes of spatial object types instead of as spatial object types in their own right.
The following figure shows an example of a network property, a speed limit, along a road. It is spatially referenced by referencing the link along which the speed limit occurs plus the start and end of the speed limit along the link (110m and 240m from the start of the link respectively).
| ← previous | Infrastructure for Spatial Information in the European Community (INSPIRE) | next → |
