-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathstandards.yaml
More file actions
195 lines (183 loc) · 7.21 KB
/
Copy pathstandards.yaml
File metadata and controls
195 lines (183 loc) · 7.21 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
datex-ii:
title: DATEX II
longTitle: European Standard for Traffic and Travel Information Exchange - CEN/TS 16157
icon: 🚦
description: European standard for traffic and travel information exchange
domain: Road traffic and travel information
purpose: Standard for exchanging road and traffic data such as incidents, roadworks, and traffic status between road authorities and service providers.
format_technology: XML, UML, RDF (via DATEX II RDF profile)
maintainer_origin: CEN (EN 16157)
related_standards:
- isodis-14819
- mobilitydcat-ap
- rdf
status: EU standard (CEN)
link: https://docs.datex2.eu/
netex:
title: NeTEx
longTitle: Network Timetable Exchange
icon: 🚇
description: Network Timetable Exchange - public transport network data
domain: Public transport (scheduled data)
purpose: Data exchange standard for sharing public transport schedules, routes, stops, and fare information, based on the TransModel conceptual model.
format_technology: XML (CEN schema)
maintainer_origin: CEN (EN 16614)
related_standards:
- transmodel
- siri
- mobilitydcat-ap
status: EU standard (CEN)
link: https://transmodel-cen.eu/
siri:
title: SIRI
longTitle: Service Interface for Real-time Information
icon: 📡
description: Service Interface for Real-time Information - live transit data
domain: Public transport (real-time information)
purpose: Defines interfaces for exchanging live operational data like vehicle positions, departures, and service alerts between systems.
format_technology: XML (SOAP-based web services)
maintainer_origin: CEN (EN 15531)
related_standards:
- transmodel
- netex
status: EU standard (CEN)
link: https://transmodel-cen.eu/
mobilitydcat-ap:
title: mobilityDCAT-AP
longTitle: Mobility Data Catalog Application Profile
icon: 🏷️
description: Mobility Data Catalog Application Profile - metadata standard
domain: Transport and mobility data catalogues
purpose: Profile of DCAT-AP tailored for describing datasets and APIs in National Access Points (NAPs) for mobility data.
format_technology: RDF, DCAT vocabulary
maintainer_origin: European Commission / EU ITS Directive framework
related_standards:
- dcat-ap
- datex-ii
- netex
- gtfs
status: EU specification (ITS Directive)
link: https://w3id.org/mobilitydcat-ap/
dcat-ap:
title: DCAT-AP
longTitle: Data Catalog Vocabulary Application Profile for Europe
icon: 📋
description: Data Catalog Application Profile - EU open data metadata
domain: Open data and metadata cataloguing
purpose: Common model for describing datasets, APIs, and catalogues to enable interoperability among European open data portals.
format_technology: RDF, W3C DCAT vocabulary
maintainer_origin: European Commission / W3C
related_standards:
- mobilitydcat-ap
- rdf
status: EU profile of W3C standard
link: https://op.europa.eu/en/web/eu-vocabularies/dcat-ap
isodis-14819:
title: ISO/DIS 14819
longTitle: Intelligent transport systems — Traffic and travel information messages via traffic message coding
icon: 📍
description: ALERT-C location referencing standard
domain: Road traffic and navigation systems
purpose: Defines the RDS-TMC message sets for broadcasting traffic and travel information to in-vehicle systems.
format_technology: Binary (RDS-TMC), XML/JSON (TPEG extensions)
maintainer_origin: ISO/TC 204
related_standards:
- rds-tmc
status: ISO standard (global)
link: https://www.iso.org/standard/76781.html
rds-tmc:
title: RDS-TMC
longTitle: Radio Data System – Traffic Message Channel
icon: 📻
description: Radio Data System - Traffic Message Channel
domain: Road traffic information broadcasting
purpose: Encodes traffic messages into FM radio broadcasts to deliver real-time traffic updates to navigation systems.
format_technology: Binary over FM RDS
maintainer_origin: ISO / CEN / broadcasters
related_standards:
- isodis-14819
status: Mature ISO/CEN standard
link: https://www.iso.org/standard/76781.html
gtfs:
title: GTFS
longTitle: General Transit Feed Specification
icon: 🚌
description: General Transit Feed Specification
domain: Public transport (static data)
purpose: Open format for publishing scheduled public transport data including routes, stops, and timetables.
format_technology: CSV (zipped feed)
maintainer_origin: Originally Google; now MobilityData community
related_standards:
- gtfs-realtime
- mobilitydcat-ap
status: Widely adopted global community standard
link: https://gtfs.org/
gtfs-realtime:
title: GTFS Realtime
longTitle: Real-time transit updates extension for GTFS
icon: ⚡
description: Real-time transit updates extension for GTFS
domain: Public transport (real-time data)
purpose: Real-time extension of GTFS providing live updates on vehicle positions, trip progress, and service alerts.
format_technology: Protocol Buffers (protobuf)
maintainer_origin: MobilityData community
related_standards:
- gtfs
status: Community specification (MobilityData)
link: https://gtfs.org/documentation/realtime/reference/
gbfs:
title: GBFS
longTitle: General Bikeshare Feed Specification
icon: 🚲
description: General Bikeshare Feed Specification - standard for shared mobility systems
domain: Micromobility and shared mobility
purpose: Defines a standard format for sharing real-time data about shared vehicles (bikes, scooters, etc.).
format_technology: JSON (REST API)
maintainer_origin: MobilityData community
related_standards:
- mobilitydcat-ap
- gtfs
status: Community specification (MobilityData)
link: https://gbfs.org/
transmodel:
title: TransModel
longTitle: European Reference Data Model for Public Transport
icon: 🗺️
description: European reference data model for public transport
domain: Public transport conceptual modelling
purpose: Conceptual data model describing the structure and relationships of public transport information (network, timetables, operations).
format_technology: UML conceptual model
maintainer_origin: CEN (EN 12896)
related_standards:
- netex
- siri
status: EU standard (CEN)
link: https://transmodel-cen.eu/
rdf:
title: RDF
longTitle: Resource Description Framework
icon: 🔗
description: Resource Description Framework - W3C standard for linked data and semantic web
domain: Semantic web and linked data
purpose: Framework for representing and linking structured data across the web, foundational to DCAT and mobilityDCAT-AP.
format_technology: RDF/XML, Turtle, JSON-LD
maintainer_origin: W3C
related_standards:
- dcat-ap
- mobilitydcat-ap
status: W3C core standard
link: https://www.w3.org/RDF/
osm:
title: OSM
longTitle: OpenStreetMap
icon: 🌍
description: OpenStreetMap - collaborative open-source mapping data
domain: Geospatial and transport mapping
purpose: Collaborative open geodata project providing maps, networks, and location references widely used in transport applications.
format_technology: XML, PBF (binary), APIs
maintainer_origin: OpenStreetMap Foundation / global community
related_standards:
- gtfs
- datex-ii
status: Global open dataset / de facto reference
link: https://www.openstreetmap.org/