ResourceFrame

This chapter describes the ResourceFrame and all its elements as it is a container holding data that can be referred to from multiple other frames.

In this chapter:

• ResourceFrame
  • ResponsibilitySet
  • TypeOfValue / ValueSets
    • TypeOfNotice
    • TypeOfProductCategory
    • TypeOfService
  • Organisation / Operator / Authority
  • ServiceFacilitySet
  • SiteFacilitySet
  • VehicleType

ResourceFrame

→ Glossary definition

Purpose

Contains shared resources used / referenced in other frames - organisations (Operators), VehicleTypes, codespaces, and other common reference data.

Contained Elements

• ResponsibilitySet
• TypeOfValue / ValueSets
  • TypeOfNotice
  • TypeOfProductCategory
  • TypeOfService
• Organisation / Operator / Authority
• ServiceFacilitySet
• SiteFacilitySet

Table

Table: ResourceFrame

Sub	Element	Usage	Card	Type	Description	Note
	@id	mandatory	1..1	xsd:string	Attribute id
	@version	mandatory	1..1	xsd:string	Attribute version
	responsibilitySets	mandatory	0..1	responsibilitySetsInFrame_RelStructure	RESPONSIBILITY SETs used in frame.	RESPONSIBILITY SETs contained in RESOURCE FRAME. ResponsibilitySets are used for the cases in which the LegalEntity, the Operator and the organisation selling the tickets are different.
+	ResponsibilitySet	mandatory	1..*	ResponsibilitySet_VersionStructure	A set of responsibility roles assignments that can be associated with a DATA MANAGED OBJECT. A Child ENTITY has the same responsibilities as its parent.	Each combination of Authority and Operator needs a ResponsibilitySet.
	typesOfValue	mandatory	0..1	typesOfValueInFrame_RelStructure	VALUE SETs and TYPE OF VALUEs in frame.	Sets of TYPE OF VALUE contained in the RESOURCE FRAME.
+	ValueSet	expected	0..*	ValueSet_VersionStructure	An extensible set of code values which may be added to by user applications and is used to validate the properties of Entities.	We need a TypeOfNotice ValueSet.
++	values	expected	0..1	typesOfValue_RelStructure	Values in Set.
+++	TypeOfNotice	expected	0..*	TypeOfNotice_ValueStructure	A classification of a NOTICE according to its functional purpose.
+	ValueSet	expected	0..*	ValueSet_VersionStructure	An extensible set of code values which may be added to by user applications and is used to validate the properties of Entities.	We need a TypeOfProductCategory ValueSet
+	ValueSet	expected	0..*	ValueSet_VersionStructure	An extensible set of code values which may be added to by user applications and is used to validate the properties of Entities.	We expect a TypsOfPlace Valueset
	organisations	mandatory	0..1	organisationsInFrame_RelStructure	ORGANISATIONs in frame.	ORGANISATIONs contained in RESOURCE FRAME. Contains the relevant Operators and other Organisations. We currently face a problem that the same sboid might be reused for Operator and Authority. We will have to check, if we only define Operators, but ue them in Authority as well. TBD
+	Operator	mandatory	0..*	Operator_VersionStructure	A company providing public transport services.	We will use this organisation also in AuthorityRef. The problem is that the sboid can be used only once.
	siteFacilitySets	optional	0..1	siteFacilitySetsInFrame_RelStructure	SITE FACILITY SETs in frame . +v1.2.2	Depending on the export/import part, there will be SiteFacilitySets to be included or not.
+	SiteFacilitySet	optional	1..*	SiteFacilitySetStructure	Set of enumerated FACILITY values that are relevant to a SITE (names based on TPEG classifications, augmented with UIC etc.).
	serviceFacilitySets	optional	0..1	serviceFacilitySetsInFrame_RelStructure	SERVICE FACILITY SETs in frame . +v1.2.2	Depending on the export/import part, there will be ServiceFacilitySets to be included. If there are ServiceJourneys we expect there to be some.
+	ServiceFacilitySet	optional	1..*	ServiceFacilitySet_VersionStructure	Service FACILITY. Set of enumerated FACILITY values (Where available names are based on TPEG classifications, augmented with UIC etc.).
	vehicleTypes	optional	0..1	transportTypeRefs_RelStructure	VEHICLE TYPEs in frame.	The VehicleType here are used for generic information like lowfloor and not for formation information
+	VehicleType	optional	0..*	VehicleType_VersionStructure	A classification of public transport vehicles according to the vehicle scheduling requirements in mode and capacity (e.g. standard bus, double-deck, …).

→ - General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<ResourceFrame id="ch:1:ResourceFrame" version="1">
  <responsibilitySets>
    <!-- RESPONSIBILITY SETs contained in RESOURCE FRAME. ResponsibilitySets are used for the cases in which the LegalEntity, the Operator and the organisation selling the tickets are different. -->
    <ResponsibilitySet id="ch:1:ResponsbilitySet-gen" version="1">
      <!-- Each combination of Authority and Operator needs a ResponsibilitySet. -->
    </ResponsibilitySet>
  </responsibilitySets>
  <typesOfValue>
    <!-- Sets of TYPE OF VALUE contained in the RESOURCE FRAME. -->
    <ValueSet id="ch:1:ValueSet:notices" version="1" nameOfClass="TypeOfNotice">
      <!-- We need a TypeOfNotice ValueSet. -->
      <values>
        <TypeOfNotice id="ch:1:TypeOfNotice:1" version="1">
          <Name lang="de">Allgemeiner Hinweis</Name>
          <PrivateCode>1</PrivateCode>
        </TypeOfNotice>
        <TypeOfNotice id="ch:1:TypeOfNotice:10" version="1">
          <Name lang="de">Angebot</Name>
          <PrivateCode>10</PrivateCode>
        </TypeOfNotice>
      </values>
    </ValueSet>
    <ValueSet id="ch:1:ValueSet:TypesOfProductCategory" version="1" nameOfClass="TypeOfProductCategory">
      <!-- We need a TypeOfProductCategory ValueSet -->
      <values>
        <TypeOfProductCategory id="ch:1:TypeOfProductCategory:TER" version="1">
          <Name lang="de">Train Express Regional
            <Text lang="it">Train Express Regional</Text>
            <Text lang="en">Train Express Regional</Text>
            <Text lang="fr">Train Express Regional</Text>
          </Name>
          <ShortName>TER</ShortName>
        </TypeOfProductCategory>
      </values>
    </ValueSet>
    <ValueSet id="ch:1:ValueSet:TypesOfPlace" version="1" nameOfClass="TypeOfPlace">
      <!-- We expect a TypsOfPlace Valueset -->
      <values>
        <TypeOfPlace id="drtCollectionPoint" version="1">
          <Name lang="de">Sammelpunkt
            <Text lang="en">Collection Point</Text>
          </Name>
        </TypeOfPlace>
        <TypeOfPlace id="regularStop" version="1">
          <Name lang="de">Reguläre Haltestelle
            <Text lang="en">Regular Stop</Text>
          </Name>
        </TypeOfPlace>
      </values>
    </ValueSet>
  </typesOfValue>
  <organisations>
    <!-- ORGANISATIONs contained in RESOURCE FRAME. Contains the relevant Operators and other Organisations. We currently face a problem that the same sboid might be reused for Operator and Authority. We will have to check, if we only define Operators, but ue them in Authority as well. TBD -->
    <Operator id="sboid" version="1">
      <!-- We will use this organisation also in AuthorityRef. The problem is that the sboid can be used only once. -->
    </Operator>
  </organisations>
  <siteFacilitySets>
    <!-- Depending on the export/import part, there will be SiteFacilitySets to be included or not. -->
    <SiteFacilitySet id="generated" version="1"/>
  </siteFacilitySets>
  <serviceFacilitySets>
    <!-- Depending on the export/import part, there will be ServiceFacilitySets to be included. If there are ServiceJourneys we expect there to be some. -->
    <ServiceFacilitySet id="generated" version="1"/>
  </serviceFacilitySets>
  <vehicleTypes>
    <!-- The VehicleType here are used for generic information like lowfloor and not for formation information -->
    <VehicleType id="tbd" version="1"/>
  </vehicleTypes>
</ResourceFrame>

→ - Template

Frame Relationships

Elements of the ResourceFrame can be referenced in other frames like SiteFrame, ServiceFrame, ServiceCalendarFrame and/or TimetableFrame.

ResponsibilitySet

→ Glossary definition

Purpose

The set of roles and organisations responsible for managing data, operations, or contractual obligations within a defined scope. We use this element to describe the different roles of the participating companies. For the most part, the company code is used to fully identify the provided services.

value of StakeholderRoleType	Description
EntityLegalOwnership	Role of the concession company holding the concession for the original service
Operation	role of the operator company responsible for providing the transport service

Table: Allowed StakeholderRoleType

Table

Each combination of Authority and Operator needs a ResponsibilitySet. EntitiyLegalOwnership ismandatory. All other roles are optional. However, we prefer to have the Operation part as well. If given Journeys are operated by a different Operator, then a different ResponsibilitySet should be referenced in the ServiceJourney from the Line.

Table: ResponsibilitySet

Sub	Element	Usage	Card	Type	Description	Note
	@id	mandatory	1..1	xsd:string	Attribute id
	@version	mandatory	1..1	xsd:string	Attribute version
	Name	mandatory	0..1	MultilingualString	Name of VALIDITY CONDITION.
+	@lang	mandatory	1..1	xsd:string	Attribute lang
	PrivateCode	expected	1..1	PrivateCodeStructure	A private code that uniquely identifies the element. May be used for inter-operating with other (legacy) systems.
	roles	mandatory	0..1	responsibilityRoleAssignments_RelStructure	Roles defined by this RESPONSIBILITY SET.
+	ResponsibilityRoleAssignment	mandatory	0..*	ResponsibilityRoleAssignment_VersionedChildStructure	Assignment of a specific RESPONSIBILITY ROLE to a specific organisation and/or subdivision.
++	StakeholderRoleType	mandatory	0..1	StakeholderRoleTypeListOfEnumerations	Stakeholder roles which this assignment assigns.	“EntityLegalOwnership” must be defined once and “Operator” should be too.
++	ResponsibleOrganisationRef	mandatory	0..1	OrganisationRefStructure	Responsible ORGANISATION.

→ - General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<ResponsibilitySet id="ch:1:ResponsbilitySet-gen" version="1">
  <!-- Each combination of Authority and Operator needs a ResponsibilitySet. EntitiyLegalOwnership ismandatory. All other roles are optional. However, we prefer to have the Operation part as well. If given Journeys are operated by a different Operator, then a different ResponsibilitySet should be referenced in the ServiceJourney from the Line. -->
  <Name lang="de">Basler Verkehrsbetriebe</Name>
  <PrivateCode>BVB</PrivateCode>
  <roles>
    <ResponsibilityRoleAssignment id="ch:1:ResponsibilityRoleAssignment:823_823:1" version="1">
      <StakeholderRoleType>EntityLegalOwnership
        <!-- "EntityLegalOwnership" must be defined once and "Operator" should be too. -->
      </StakeholderRoleType>
      <ResponsibleOrganisationRef ref="ch:1:sboid:100622" version="1"/>
    </ResponsibilityRoleAssignment>
    <ResponsibilityRoleAssignment id="ch:1:ResponsibilityRoleAssignment:823_823:2" version="1">
      <StakeholderRoleType>Operation</StakeholderRoleType>
      <ResponsibleOrganisationRef ref="ch:1:sboid:100622" version="1"/>
    </ResponsibilityRoleAssignment>
  </roles>
</ResponsibilitySet>

→ - Template

Usage Notes

Services (e.g. replacement services) can be associated with different roles. These roles can be defined inside the ResponsibilitySet element.

Only the values defined below are allowed in Switzerland for StakeholderRoleType in ResponsbilityRoleAssignment:

• Operation
• EntityLegalOwnership

We might add at some point:

• FareManagement
• Planning
• @id should be kept stable between exports.

TypeOf… / ValueSet

→ Glossary definition: TypeOf…
→ Glossary definition: ValueSet

Purpose

TypeOf… (examples: TypeOfNotice, TypeOfProductCategory, TypeOfService) are used for classification of NeTEx entities. They are listed in ValueSets as part of the ResourceFrame.

Usage Notes

We use TypeOfValue references in various Frames in objects including:

• Notice: references TypeOfNotice
• Line and ServiceJourney: references TypeOfProductCategory
• @id needs to be kept stable between exports.

TypeOfNotice

Purpose

TypeOfNotice is used within a Notice to give information, what it is about. The table below shows the TypeOfNotice we use in Switzerland.

PrivateCode	Name	Description
1	Allgemeiner Hinweis	General information text
2	Zugname	Name of the train. Is not used, as this is stored in ServiceJourney/Name.
3	Gleis-Angabe	Quay and Quay section information. Is no longer used. Is put into Quay.
10	Angebot	Most of the ServiceFacilitySet are also transmitted as Notice. On top of that we have multiple services and facilities in Switzerland that cannot be mapped to ServiceFacilitySets. This TypeOfNotice is used to deliver those special cases as Notices.
11	Region	Postauto is divided into several regions. Will be omitted. We will add a privateCodes/PrivateCode with type="rn" to the ServiceJourney or TemplateServiceJourney.

Table: Allowed TypeOfNotice in Switzerland

The following snippet is all that is defined for TypeOfNotice:

<ValueSet id="ch:1:ValueSet:notices" version="1" nameOfClass="TypeOfNotice">
  <values>
    <TypeOfNotice id="ch:1:TypeOfNotice:1" version="1">
      <Name>Allgemeiner Hinweis</Name>
      <PrivateCode>1</PrivateCode>
    </TypeOfNotice>
    <TypeOfNotice id="ch:1:TypeOfNotice:10" version="1">
      <Name>Angebot</Name>
      <PrivateCode>10</PrivateCode>
    </TypeOfNotice>
  </values>
</ValueSet>

TypeOfProductCategory

Purpose

For the ServiceJourneys exclusively provided in Switzerland, only the ProductCategories defined in the document 06 Harmonisierung Verkehrsmittel may be referenced. For ServiceJourneys provided in other countries or partially in Switzerland, there are no restrictions, provided that the category does not overlap with the ProductCategories defined for Switzerland.

Table

Table: TypeOfProductCategory

Sub	Element	Usage	Card	Type	Description	Note
	@id	mandatory	1..1	xsd:string	Attribute id
	@version	mandatory	1..1	xsd:string	Attribute version
	Name	mandatory	0..1	MultilingualString	Name of VALIDITY CONDITION.
+	@lang	mandatory	1..1	xsd:string	Attribute lang
+	Text	optional	0..*	MultilingualString
++	@lang	mandatory	1..1	xsd:string	Attribute lang
	ShortName	mandatory	0..1	MultilingualString	Short Name for TYPE OF VALUE.

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<TypeOfProductCategory id="ch:1:TypeOfProductCategory:TER" version="1">
  <alternativeTexts>
    <!-- Is done with MultilanguageString now -->
  </alternativeTexts>
  <Name lang="de">TER
    <Text lang="en">Train Express Regional</Text>
    <Text lang="it">Train Express Regional</Text>
    <Text lang="fr">Train Express Regional</Text>
  </Name>
  <ShortName>TER</ShortName>
</TypeOfProductCategory>

→ Template

TypeOfService

TypeOfService is to be found within TimetableFrame.

Organisation / Operator / Authority

→ Glossary definition: Operator
→ Glossary definition: Authority

Purpose

A legally incorporated body associated with any aspect of public transportation. Authority and Operator are Organisations. An Operator provides public transport services under contract with an Authority. We don’t use Authority.

Table

We will use this organisation also in AuthorityRef. The problem is that the SBOID can be used only once. TODO Clarify

Table: Operator

Sub	Element	Usage	Card	Type	Description	Note
	@id	mandatory	1..1	xsd:string	Attribute id
	@version	mandatory	1..1	xsd:string	Attribute version
	privateCodes	mandatory	0..1	PrivateCodesStructure	A list of private codes that uniquely identifiy the element. May be used for inter-operating with other (legacy) systems. +v2.0
+	PrivateCode	expected	0..*	PrivateCodeStructure	A private code that uniquely identifies the element. May be used for inter-operating with other (legacy) systems.	SBOID and GO (busines organisation) mandatory if they exist.
	Name	expected	0..1	MultilingualString	Name of VALIDITY CONDITION.
	ShortName	expected	0..1	MultilingualString	Short Name for TYPE OF VALUE.	there may be cases, when it can’t be set. However, when no sboid is there, then ShortName must be filled (especially for foreign operators.
	parts	optional	0..1	blockParts_RelStructure	Parts of the ORGANISATION.
++	administrativeZones	optional	0..*	administrativeZones_RelStructure	Zones managed by ORGANISATION PART.
+++	TransportAdministrativeZone	optional	0..*	TransportAdministrativeZone_VersionStructure	A ZONE relating to the management responsibilities of an ORGANISATION. For example to allocate bus stop identifiers for a region.
++++	PrivateCode	optional	1..1	PrivateCodeStructure	A private code that uniquely identifies the element. May be used for inter-operating with other (legacy) systems.

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<Operator id="ch:1:sboid:100602" version="1">
  <!-- We will use this organisation also in `AuthorityRef`. The problem is that the SBOID can be used only once. **TODO** Clarify -->
  <privateCodes>
    <PrivateCode type="GO">801
      <!-- SBOID and GO (busines organisation) mandatory if they exist. -->
    </PrivateCode>
    <PrivateCode type="sboid">ch:1:sboid:100602
      <!-- SBOID and GO (busines organisation) mandatory if they exist. -->
    </PrivateCode>
  </privateCodes>
  <Name>PostAuto AG</Name>
  <ShortName>PAG
    <!-- there may be cases, when it can't be set. However, when no sboid is there, then ShortName must be filled (especially for foreign operators. -->
  </ShortName>
  <parts>
    <OrganisationPart id="ch:1:OrganisationPart:801-5678" version="1">
      <administrativeZones>
        <TransportAdministrativeZone id="ch:1:TransportAdministrativeZone:801-5678" version="1">
          <PrivateCode>5678</PrivateCode>
        </TransportAdministrativeZone>
      </administrativeZones>
    </OrganisationPart>
  </parts>
</Operator>

→ - Template

Usage Notes

• Organisations located in Switzerland are identified by their SBOIDs (earlier GO-number ). in Switzerland. The TU-Code is to be used for operators of other countries.
• The SBOID and GO number shall always also be stored in the KeyList and in privateCodes/PrivateCode.
• OperatorRef on a Line is always the “Konzessionär”.
• If a different Operator is running a given ServiceJourney, then this is reflected in the ServiceJourney having a different OperatorRef.
• Authority and Organisation are not used.
• @id needs to be kept stable between exports.

ServiceFacilitySet

→ Glossary definition

Purpose

Set of Facility’s available for a ServiceJourney or a JourneyPart.

Table

List of ServiceFacility. Be careful: not all are supported. Consult profile. Make sure to not generate identical ServiceFacilitySets. Reuse them. Details in the mapping excel.

Table: ServiceFacilitySet

Sub	Element	Usage	Card	Type	Description	Note
	@id	mandatory	1..1	xsd:string	Attribute id
	@version	mandatory	1..1	xsd:string	Attribute version
	Extensions	expected	1..1	ExtensionsStructure	Extensions to schema. (Wrapper tag used to avoid problems with handling of optional ‘any’ by some validators).	Two elements used in HRDF for ordering facilities
+	Priority	expected	0..1	InterchangePriorityType	Priority to assign to this INTERCHANGE.
	Description	expected	0..1	MultilingualString
+	@lang	mandatory	1..1	xsd:string	Attribute lang
+	Text	optional	0..*	MultilingualString
++	@lang	mandatory	1..1	xsd:string	Attribute lang
	FareClasses	optional	0..1	FareClassListOfEnumerations	List of Fare Classes.
	MobilityFacilityList	optional	0..1	MobilityFacilityListOfEnumerations	List of MOBILITY FACILITies.
	NuisanceFacilityList	optional	0..1	NuisanceFacilityListOfEnumerations	List of NUISANCE FACILITies.
	PassengerCommsFacilityList	optional	0..1	PassengerCommsFacilityListOfEnumerations	List of PASSENGER COMMS FACILITies.
	SanitaryFacilityList	optional	0..1	SanitaryFacilityListOfEnumerations	List of SANITARY FACILITies.
	CouchetteFacilityList	optional	0..1	CouchetteFacilityListOfEnumerations	List of COUCHETTE FACILITies.
	GroupBookingFacility	optional	0..1	GroupBookingEnumeration	Classification of GROUP FACILITY type - TPEG pti23.

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<ServiceFacilitySet id="ch:1:ServiceFacilitySet:A___2" version="1">
  <!-- List of ServiceFacility. Be careful: not all are supported. Consult profile. Make sure to not generate identical ServiceFacilitySets. Reuse them. Details in the mapping excel. -->
  <Extensions>
    <!-- Two elements used in HRDF for ordering facilities -->
    <Priority>1</Priority>
    <Condition>4</Condition>
  </Extensions>
  <Description lang="de">Nur 2. Klasse
    <Text lang="en">2nd class only</Text>
    <Text lang="fr">Seulement 2e classe</Text>
    <Text lang="it">Solo 2a classe</Text>
  </Description>
  <FareClasses>secondClass</FareClasses>
  <MobilityFacilityList>stepFreeAccess lowFloor</MobilityFacilityList>
  <NuisanceFacilityList>animalsAllowed</NuisanceFacilityList>
  <PassengerCommsFacilityList>publicWifi</PassengerCommsFacilityList>
  <SanitaryFacilityList>toilet</SanitaryFacilityList>
  <CouchetteFacilityList>wheelchair</CouchetteFacilityList>
  <GroupBookingFacility>groupsAllowed</GroupBookingFacility>
</ServiceFacilitySet>

→ - Template

Usage Notes

• SKI uses the following groups to classify ServiceFacilitys:
  • Accommodation facility
  • Catering facility
  • Fare classes
  • Group booking facility
  • Luggage carriage facility
  • Mobility facility
  • Nuisance facility
  • Passenger communications facility
  • Service reservation facility
  • Ticketing facility
  • Uic train rate
• The list is from time to time revised. The values and lists from the NeTEx standard are not updated.
• This means that a given Facility (e.g. restaurant or diaper changing table) is shown in the appropriate subcategory MealFacilityList or FamilyFacilityList, and a passenger information system can show these categories in a reasonable order. The categories themselves are from type xsd:list, meaning that the values of a category are a separated list of elements.
• When transforming from HRDF to NeTEx. The Facility is often also copied as a Notice in textual form.
• The details of the usage are defined in the mapping table for NeTEX 2.0.
• See also Use case on service facilities.
• @id should be kept stable between exports.

SiteFacilitySet

→ Glossary definition

Purpose

Set of Facilitys available at a StopPlace, Quay or other site elements.

A SiteFacilitySet defines a set of facilities like sanitary facilities, ticket service, lockers etc. that can be referenced to define facilities of a site.

Table

List of SiteFacility. Be careful: not all are supported. Consult profile. Make sure to not generate identical SiteFacilitySets. Reuse them. There might be an overlap to ServiceFacilitySet, but they are used for different purposes.

Table: SiteFacilitySet

Sub	Element	Usage	Card	Type	Description	Note
	@id	mandatory	1..1	xsd:string	Attribute id
	@version	mandatory	1..1	xsd:string	Attribute version
	validityConditions	optional	1..1	validityConditions_RelStructure	VALIDITY CONDITIONs conditioning entity.
+	AvailabilityCondition	optional	0..*	AvailabilityCondition_VersionStructure	VALIDITY CONDITION stated in terms of DAY TYPES and PROPERTIES OF DAYs.
	Description	optional	0..1	MultilingualString		Description is optional
+	@lang	mandatory	1..1	xsd:string	Attribute lang
+	Text	optional	0..*	MultilingualString
++	@lang	mandatory	1..1	xsd:string	Attribute lang
	AssistanceFacilityList	optional	0..1	AssistanceFacilityListOfEnumerations	List of ASSISTANCE FACILITies.
	AccessibilityToolList	optional	0..1	AccessibilityToolListOfEnumerations	List of TYPEs of ACCESSIBILITY TOOLs.
	SanitaryFacilityList	optional	0..1	SanitaryFacilityListOfEnumerations	List of SANITARY FACILITies.
	TicketingServiceFacilityList	optional	0..1	TicketingServiceFacilityListOfEnumerations	List of TICKETING SERVICE FACILITies, e.g. purchase, collection. top up.
	EmergencyServiceList	optional	0..1	EmergencyServiceListOfEnumerations	List of EMERGENCY SERVICE FACILITies.
	LuggageLockerFacilityList	optional	0..1	LuggageLockerFacilityListOfEnumerations	List of LUGGAGE LOCKER FACILITies.
	ParkingFacilityList	optional	0..1	ParkingFacilityListOfEnumerations	List of PARKING FACILITies.

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<SiteFacilitySet id="generated" version="1">
  <!-- List of SiteFacility. Be careful: not all are supported. Consult profile. Make sure to not generate identical SiteFacilitySets. Reuse them. There might be an overlap to ServiceFacilitySet, but they are used for different purposes. -->
  <validityConditions>
    <AvailabilityCondition id="generated" version="1">
      <FromDate>2026-03-30T12:00:00</FromDate>
      <ToDate>2026-04-01T12:00:00</ToDate>
      <ValidDayBits>01</ValidDayBits>
    </AvailabilityCondition>
  </validityConditions>
  <Description lang="de">SiteFacilitySet Solothurn
    <!-- Description is optional -->
    <Text lang="en">SiteFacilitySet Solothurn</Text>
  </Description>
  <AssistanceFacilityList>personalAssistance information boardingAssistance</AssistanceFacilityList>
  <AccessibilityToolList>audioNavigator</AccessibilityToolList>
  <SanitaryFacilityList>toilet babyChange</SanitaryFacilityList>
  <TicketingServiceFacilityList>all reservations</TicketingServiceFacilityList>
  <EmergencyServiceList>police firstAid</EmergencyServiceList>
  <LuggageLockerFacilityList>lockers</LuggageLockerFacilityList>
  <ParkingFacilityList>parkAndRidePark</ParkingFacilityList>
</SiteFacilitySet>

→ - Template

Usage Notes

• Make sure to not generate identical SiteFacilitySets. Reuse them.
• We currently don’t have many SiteFacilitySet as this is not done in timetables yet. With accessibility and more information from Atlas, this may change.
• We will keep the list of relevant values updated in mapping table for NeTEX 2.0.
• There may be an overlap between SiteFacilitySet and ServiceFacilitySet. However, they reference very different things: site elements and vehicles.
• Sometimes “capabilities”/”limitations” are defined through combinations of what a stop and what a vehicle can do.
• In future also the use of Equipment and EquipmentPlace may become more important. These are then actual pieces of equipment. This also means that the Vehicle must be known and referenced.
• @id should be kept stable between exports.

VehicleType

→ Glossary definition

Purpose

A typified vehicle configuration (model or series) defining reusable characteristics such as capacity, dimensions, propulsion, and accessibility features.

Table

Used currently mainly for the relevant accessibility elements that can be expressed currently

Table: VehicleType

Sub	Element	Usage	Card	Type	Description	Note
	@id	mandatory	1..1	xsd:string	Attribute id
	@version	mandatory	1..1	xsd:string	Attribute version
	ShortName	expected	0..1	MultilingualString	Short Name for TYPE OF VALUE.	Will be defined in mapping excel
	LowFloor	optional	0..1	xsd:boolean	Low floor VEHICLES can use stop and be accessible.
	HasLiftOrRamp	optional	0..1	xsd:boolean	Whether vehicle has lift or ramp to facilitate wheelchair access.
	HasHoist	optional	0..1	xsd:boolean	Whether vehicle has hoist for wheelchair access.

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<VehicleType id="ch:1:VehicleType:NF" version="1">
  <!-- Used currently mainly for the relevant accessibility elements that can be expressed currently -->
  <ShortName>NF
    <!-- Will be defined in mapping excel -->
  </ShortName>
  <LowFloor>true</LowFloor>
  <HasLiftOrRamp>false</HasLiftOrRamp>
  <HasHoist>true</HasHoist>
</VehicleType>

→ - Template

Usage Notes

• We currently use VehicleType but not VehicleModel.
• We express accessibility partially through it.
• See more details in the mapping excel.