Profile documents

Content

 

Changelog

Date

Profile document

Change

Version

Date

Profile document

Change

Version

Jul 28, 2022

framework,
stops
network
timetable

Change requests # 35, 36, 38, 41, 42, 43, 44, 45, 46, 47(!), 48, 49

framework

  • Added PrivateCode to Vehicle, VehicleType and TrainElement

  • Added AssistanceBookingService (local service type)

  • Correction of AssistanceService

    • Change incorrectly named element/datatype AssistanceServices/AssistanceServiceEnum to AssistanceFacilityList/AssistanceFacilityListOfEnumerations as it is actually implemented

    • Added element AssistanceAvailability

    • Added element Staffing

    • Change incorrectly named element/datatype AccessibilityTools/AccessibilityToolEnum to AccessibilityToolList/AccessibilityToolListOfEnumerations as it is actually implemented in the standard

    • Removed element GuideDogsAllowed, which is not available in this dataset

  • Added PrivateCode to Organisation

  • Added ShortName as optional element for TypeOfValue

stops

  • Added Polygon and mandatory Centroid to GroupOfStopPlaces

  • Added mandatory Descriptor element (and sub-type) to TopographicPlace (required for valid NeTEx XML)

  • Removal of BookWhen - timeOfTravelOnly (this should rather be modeled as a RequestStop)

  • Deprecation of StopPlace → Weighting enum “preferredInterchange”, as it is handled equally to “recommendedInterchange” in journey planning (and GTFS only supports “recommended”)

network

  • Allow multiple Vias, with new attribute order, in DestinationDisplay

timetable

  • Deprecation of Interchange → Priority “2” (maximum interchange preference), as it is handled equally to “1” (recommended interchange) in journey planning (and GTFS only supports “recommended”)

  • Removal of BookWhen - timeOfTravelOnly (this should rather be modeled as a RequestStop on the network StopPoint)

v1.5

Jan 7, 2022

NeTEx examples catalogue
General information: NeTEx
framework,
stops
network
timetable,
fares,
sales

Change requests # 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14, 15, 16, 17, 18, 21, 22, 23, 24, 25, 26, 27, 28:

Updated example for Branding of a Network and/or Line

General information

  • Clarify paragraph "Structure of ID's" (mainly requirements for the identification element)

  • Implementation of PassingTimes during switch to and from Daylight Savings Time

framework

  • Added publication attribute to EntityInVersion

  • Added groupsOfTariffZones to SiteFrame

  • Elaborated description for use of multiple DayType-properties/PropertyOfDay to ensure compliance with NeTEx spec and XML Schema documentation

  • Added HolidayTypes and Seasons elements for PropertyOfDay

  • Added abstract data objects common for fares and sales

  • Added FareFrame and SalesTransactionFrame

  • Minor textual additions to clarify use of conditions

  • Added information on Part 3 addition Sales Transaction Frame (currently not in use) and changed references from "Norwegian" to "Nordic"

  • Simplified structure for organisation data

    • Removed Organisation → parts placeholder (for listing OrganisationParts), as this way of constructing organisation data, is neither used nor implemented technically

    • Removed OrganisationPart data object (not in use)

    • Removed Department data object (not in use)

    • Changed cardinality for Organisation → ContactDetails (previously mandatory, however, this data is unknown for some Operators thus will only be mandatory for Authority type organisations)

  • Removed SchematicMap container (not in use)

  • CheckConstraints corrections/additions

    • Adding further CheckProcess types

    • Disallowing references from CheckConstraintDelay to CheckConstraint (i.e. a CheckConstraint may have a delay, but not the other way around)

  • Release of the requirement to have DataManagedObject → responsibilitySetRef (rarely used, has never been enforced)

  • Release of the requirement to have GroupOfEntities → Name (supplementary description added to clarify when required and when optional)

  • Release of requirement to have Place → TypeOfPlaceRef (not in use, current implementations use TopographicPlaceType / StopPlaceType instead, description is updated accordingly)

  • Allow for use of ISO 639-2 (Alpha-3) three-letter language codes

  • Allow for use of ISO 3166-1 alfa-3 three-letter country codes

  • Clarification to use of coordinates and positioning tuples (default is first number latitude, second number longitude)

  • Added transport submode “unknown” for fallback use when such data is unavailable

stops

  • Extended PurposeOfGroupingRef categories

  • Added GroupOfFareZones

  • Added FareZone (specification of TariffZone) with mandatory AuthorityRef- WiP

  • Added members (ScheduledStopPoints within) to TariffZone

  • Added Presentation data to TariffZone

  • Moved definition of TariffZone here (from network), as the SiteFrame included the containing element

  • Added PrivateCode and PublicCode for StopPlace

  • Allow for use of ISO 3166-1 alfa-3 three-letter country codes

network

  • Harmonized and clarified booking data across BookingArrangementsStructure, FlexibleLine and timetable-FlexibleServiceProperties (incl. BookingMethods “other”)

  • Specified OperatingDay - ToDate as inclusive, as documented in the specification/XSD

  • Added TimingPointStatus to ScheduledStopPoint

  • Moved SiteConnection here (from stops) and added connections container to the ServiceFrame

  • Released on requirements for FlexibleLine (removed explicit obligation "FlexibleLine must be used if one or more FlexibleStopPlace(FlexibleAreaand/orHailAndRideArea) are present in the Line.") to align better with the practical use of BookingArrangements for non-flexible lines as documented in the profile

  • Added StopUse “interchangeOnly” to StopPointInJourneyPattern

timetable

  • Harmonized and clarified booking data across FlexibleServiceProperties and network-BookingArrangementsStructure/network-FlexibleLine

  • Minor clarification to interchange feeder/consumer stops and journeys

  • Clarification to the usage of arrival/departure day offset

  • Added optional list of TrainNumber objects and references (from ServiceJourney and/or its parts, and JourneyPartCouple)

  • Added DatedServiceJourney as an optional ServiceJourney subtype for a particular OperatingDay - NB: This data type is under Nordic revision, where its core structure is currently operational but supplementary data / improvements may be introduced in the NeTEx profile at a later stage.

fares

  • Added preliminary profile document for fare/product related data (v0.8 - Work In Progress)

sales

  • Added preliminary profile document for sales/transactions/consumption related data (v0.8 - Work In Progress)

v1.4

Aug 21, 2019

stops

Change request #2: Public and private codes for StopPlaces.

stops

  • Adding PrivateCode (internal code uniquely identifying the Stop Place, usable for e.g. inter-operating with legacy systems)

  • PublicCode (a short and human-readable code uniquely identifying the Stop Place, may be used as a convenient alternative to the name or ID)

v1.4

Jun 19, 2019

stops

Change request #1: Parking – payment, spaces with recharge point, spaces for disabled users.

stops

  • Added ParkingPaymentProcess enumeration in Parking.

  • Added ParkingUserType enumeration in ParkingCapacity.

  • Added NumberOfSpacesWithRechargePoint in ParkingCapacity.

  • Updated description of TotalCapacity and RechargingAvailable in Parking for consistency with ParkingCapacity.

v1.4

Aug 30, 2018

General information: NeTEx
framework,
network
stops,
timetable

This revision includes moving Håndbok N801, all profile documents, and GitHub-examples to a new domain (Entur).

General information

  • Version reference changed to v1.3.

framework

  • Consolidated ticketing machine-modelling into TicketingEquipment. The duplicate element TicketingFacilityList was removed from the profile.

  • Consolidated sanitary equipment-modelling into SanitaryEquipment. The duplicate element SanitaryFacilityList was removed from the profile.

  • Added VehichleScheduleFrame in order to specify Blocks for a vehicle.

  • TariffZones should be handled as a part of stop places and should, therefore, be part of SiteFrame, rather than ServiceFrame.

  • Added "cityTram" as a tram submode. To be used by "Bybanen".

stops

  • Added categorisation of GroupOfStopPlaces as a pre-defined reference to PurposeOfGrouping.

  • Added new StopPlaceType "taxiStand"

network

  • Clarification on how to structure booking information for FlexibleLines. Some previously mandatory elements are no longer so.

  • Removed redundant option advanceOnly for BookWhen (on FlexibleLine, BookingArrangementsStructure and FlexibleServiceProperties)

  • Moved FlexibleServiceProperties to Timetable (used only in TimetableFrame)

  • Clarification on the usage of Line  Presentation

  • Changed cardinality for Line → Monitored and Line → AccessibilityAssessment (previously mandatory elements are no longer so. The reason for this is that most data providers will not be able to provide meaningful information for it)

  • Changed cardinality for ServiceLink → projections (previously mandatory elements are no longer so. The reason for this is that ServiceLinks technically have geographic positionings for parts of the way)

  • Remove unused objects associated with flexible transport (FlexibleRoute, FlexibleLinkProperties, FlexiblePointProperties) since these should be modelled using the general objects (Route, ServiceLink, ScheduledStopPoint).

  • Added optional field PrivateCode for JourneyPattern.

timetable

  • Specified use of Priority for Interchange (specified as weighting, not sequential order).

  • Removed optional fields Planned and Advertised for Interchange, since this will be implicit for specified interchanges.

  • Clarification on required attributes ID and VERSION for TimetabledPassingTime (has previously not been validated due to an unhandled discrepancy of the main NeTEx XML-Schema)

  • Clarification that referred ServiceJourney has to exist in the PublicationDelivery.

  • Added possible value ServiceJourney → ServiceAlteration "replaced" for usage in replacement transport.

  • The concept SpecialService removed from the profile (not in use). For "special" departures, use normal ServiceJourney and add FlexibleServiceProperties when relevant.

  • Added DeadRun to make the modelling of trips without passengers possible.

  • Clarification that interchanges across datasets should only be defined for the receiving/departing Line at the interchange.

v1.3

Mar 7, 2018

General information: NeTEx
framework,
network
stops,
timetable

Full export (appendix Håndbok N801)

v1.2

Mar 6, 2018

General information: NeTEx
framework, network
timetable  

General information

  • Updated version references (NeTEx XSD v1.08 and Norwegian profiles v1.2)

framework

  • Removed references to default values for optional fields (they are not optional, and should be handled explicitly).

  • New and clearer description for fields in OrganisationPart.

  • It is now required that ContactStructure has at least Email, Phone or Url

    • For CustomerServiceContactDetails, the field Url is now required.

  • Listed allowed enumerations for DayType → PropertyOfDay → DayOfWeek and DayType → PropertyOfDay → WeeksOfMonth

  • It is no longer required to include the Distance field for LinkSequence.

  • Added optional field AlternativeTexts to support translations of Notice texts.

  • Added the NameType "Label" for AlternativeName.

  • Formalised the requirement for using TimeZone for local time in Locale (was already the de facto standard), and removed the optional fields TimeZoneOffset and SummerTimeZoneOffset which won't be used.

stops

  • Updated version number.

network

  • Specified usage of ForAlighting and ForBoarding on first- and last stop in StopPointInJourneyPattern.

  • Added optional field Distance for ServiceLink (can be used to monitor vehicles via in real-time).

  • Added optional field ShortName for Line (can be used for alternative names).

  • Changed cardinality for Line  PublicCode (a previously required element is no longer required since not all lines have an actual PublicCode).

timetable

  • Removed references to default values for optional fields (they are not optional, and should be handled explicitly).

  • Added PrivateCode as an optional field on VehicleJourney for external- or dataset-specific ID's (such as train- or trip numbers).

v1.2

Sep 13, 2017

General information: NeTEx
framework,
network
stops,
timetable

Full export (appendix Håndbok N801)

v1.1

Sep 12, 2017 

General information: NeTEx
framework,
stops,
network
timetable

All profile documents:

  • Consolidation of links.

General information:

  • Clarification regarding the use of versions.

  • Clarification regarding ID formatting.

  • Revised list of definitions according to changes of profile documents (added new-/removed outdated objects)

  • Clarification on how a common objects file must be used.

framework:

  • Changed cardinality for Point Location. Previously required elements are no longer required when the geographic position can be derived from projection or links to another locational object.

  • Changed incorrect cardinality for Zone < GroupOfPoints < GroupOfEntities < DataManagedObject. The implementation (NeTEx-XSD) only allows 0 or 1 of gml:Polygon (not 0 to many) for Zone.

  • Added equipment type "sign": GeneralSign < SignEquipment < PlaceEquipment < Equipment < DataManagedObject

    • There are explicit demands for modelling stop place signs.

  • Changed recommended modelling of walk paths to independent pathLinks, instead of NavigationPaths consisting of pathLinks, for objects which support this, since NavigationPath can be derived from them.

  • Removed redundant and optional field AllAreasWheelchair for PathLink/PathJunction. The information can be derived from AccessibilityAssessment → MobilityImpairedAccess → WheelchairAccess (required value).

  • Added placeEquipments (equipmentPlaces minus specified Location) for Site.

  • Added localServices under Site

  • Changed the abstract type WaitingEquipment to the correct SiteEquipment data type WaitingRoomEquipment (inherits from WaitingEquipment)

  • Adjusted requirements of data fields for Organisation (specifically incl. Authority/Operator)

  • Added fields for a possibly explicit PrivateContactDetails for Organisation.

  • Adjusted AlternativeName:

    • Lang and NameType are now required.

    • NameType "other" no longer valid value.

    • Removed optional fields TypeOfName, ShortName, QualifierName and Abbreviation.

  • Added OperatingPeriodRef as a possible reference in DayTypeAssignment.

  • Added PrivateCode as an optional field for Equipment in order to handle non-public ID's/codes.

  • Adjusted translations for TransportMode "cableway" and "funicular".

  • Clarification of data format for language, language code, and currency.

  • Added the TransportMode "coach" in order to separate long-distance buses from local-/regional buses.

  • Added the TransportMode "taxi" (with TaxiSubmode)

  • Added notices and noticeAssignments for TimetableFrame.

  • Added groupsOfStopPlaces for SiteFrame.

  • Added versionRef attribute which can be used for external objects in a specific version.

  • Added optional additionalNetworks (which allows multiple Networks and subsequently multiple Authorities) for SiteFrame.

  • Notices

    • Removed the field TypeOfNoticeRef.

    • Made the field Text required (notice must have content).

    • Made PublicCode optional.

stops:

  • Replaced optional field PlaceCode with optional PublicCode for Quay.

  • Added optional element TransferDuration for PathLink.

  • Added optional element ParkingVehicleType for Parking.

  • Changed all previously required data fields for Parking to optional.

  • Removed redundant value covered for Parking → ParkingLayout. The concept is instead modelled by defining Parking → Covered as covered or indoors (general value for SiteElement)

  • Added optional element PublicUse for objects of the type SiteElement.

  • Added PrivateCode as an optional field for Quay.

  • Clarification of data format for land- and area code.

  • Added GroupOfStopPlaces.

  • Added "country", "region", "interregion" and "municipality" as allowed values for TopgraphicPlaceType.

network:

  • Adjusted errors in organisation references for Network, related to AuthorityRef.

  • Added required connection between Line and Authority.

  • Clarification in Presentation, and removed redundant fields ColourName and TextColourName.

  • Clarification for the minimum required DestinationDisplayRef for first StopPointInJourneyPattern, and all subsequent stops where DestinationDisplay changes.

  • Removed redundant data type Connection.

  • Changed Name to required element for Network and GroupOfLines.

  • Adjusted data structure for Interchange.

    • Removed the redundant field for transfer time.

    • Added field for Planned and Advertised.

    • Added field for MaximumWaitTime.

  • Adjusted requirements for StopAssignment types to reflect technical schema validation.

  • Changed TransportSubmode to required.

  • Removed field PublicCode for DestinationDisplay.

  • Removed noticeAssignment from Line, StopPointInJourneyPattern and TimingPointInJourneyPattern. Should be located with notices directly in ServiceFrame.

  • Added optional field RequestMethod for StopPointInJourneyPattern.

  • Added optional dataset BookingArrangements for StopPointInJourneyPattern.

  • Added optional field felt ExternalLineRef for Line.

timetable:

  • Added optional fields ArrivalDayOffset/DepartureDayOffset for TimetabledPassingTime.

  • Changed time-specification for arrival/departure to required. Cardinality for PassingTimes (per VehicleJourney/ServiceJourney) is specified according to this.

  • Changed TransportMode and TransportSubmode to required.

  • Clarified usage of calendar objects in a ServiceCalendar vs. free-standing.

  • Changed fields FromDate and ToDate to required when using ServiceCalendar.

  • Removed noticeAssignment fra Journey and Interchange. as it is more relevant to place notices directly under TimetableFrame.

  • Added optional field ExternalVehicleJourneyRef for Journey.

v1.1

Apr 15, 2020 

framework,
stops,
network,
timetable

Initial export (appendix Håndbok N801)

v1.0