Content

Displaying brand or altered operator information

Branding expands the presentation possibilities at all levels of the time table data. At the top level (Authority/Operator), Branding can override which company information presented to the customer. Please note that the proper way to override Authority is with additionalNetwork.

Modelling for alternative operator information

Authority for lines operated under contract from a county should be the county or its designated organization. Line lines delivered by the county on behalf of other operators, should (normally) have its own Authority within the codespace. In practice, this means that the customer is informed which Authority is responsible for the route, as well as for example ticketing (note that customer service/contact information is obtained from CustomerServiceContactDetails for the lines' Operator).

...

Additional information on Network or Line

Branding is a generic NeTEx element which can be applied to elements in the NeTEx structure for adding or overriding name and URL. In the Nordic profile, the usage is limited to adding additional names and URL to the Network and Line elements.

• Branding per Network

  • Used when certain lines in the dataset have a common denominator, i.e. Network.

  • Examples of this can be a cluster of city buses, a string of Lines which form a coherent service, or a sales related brand name.

  • The Network may have a different URL from the authority.

• Branding per Line

  • Used when a Line has a commonly used or publicly marketed name which a customer may relate to in addition to the Lines' publicCode.

  • An example of this can be e.g. "Bergensbanen" for railway service journeys between Oslo and Bergen.

  • The Line may have a different URL from the authority.

Modelling of added information

The Branding elements may be added to the commons file of the dataset (for reduced redundancy) and is referred to from Network or Line with the use of a BrandingRef.

...

...

Please note that the concept of GroupOfLines is not a part of the hierarchy and does necessarily have to include the same lines as the Network.

Link

The entire XML sample file is files are located in the GitHub repository: 

• https://github.com/entur/profile-norway-examples/blob/master/netex/submodels/submodel-Branding-Line.xml

• https://github.com/entur/profile-norway-examples/blob/master/netex/submodels/submodel-Branding-Network.xml

Elements

ValueSet

Each instance of Branding is defined under ResourceFrame (as a TypeOfValue), specified with at a minimum the with Name value. 

<typesOfValue>
	<Branding version="1" id="SOFUNI:Branding:1">
		<Name>Firda Billag<<Name>Lavprisekspressen</Name>
		<Url>https://www.firda-billag.no/<lavprisekspressen.no</Url>
	</Branding>
	<Branding version="1" id="SOFVYB:Branding:21">
		<Name>Nettbuss Sogndal<<Name>Bus4You</Name>
		<Url>https://www.nettbussvy.nose</</Url>
	</Branding>
</typesOfValue>

...

The reference element BrandingRef must be specified for the object where a name, (and if applicable, other fields) is to be replaced.

Branding on a Line

(simplified example)

<Line version="1" id="SOFUNI:Line:1">
	<BrandingRef version="1" ref="SOFUNI:Branding:1"/>
	<Name>Sogndal-Kaupanger kai<<Name>Oslo-Kristiansand-Stavanger</Name>
	<TransportMode>bus</TransportMode>
	<TransportSubmode>
		<BusSubmode>localBus</BusSubmode>
	</TransportSubmode>
</Line>

Branding on a

...

Network

(simplified example)

<ServiceJourney<Network version="1" id="SOFVYB:ServiceJourneyNetwork:1"> 
	<BrandingRef version="1" ref="SOFVYB:Branding:21"/>
	<Name>Sogndal-Kaupanger kai</Name>
	<TransportMode>bus</TransportMode>
	<TransportSubmode>
		<BusSubmode>localBus</BusSubmode>
	</TransportSubmode>
</ServiceJourney><Name>Vy Buss AB</Name>
</Network>