Innhold

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), Brandin Branding can override which company information is displayed presented to the customer. This should not be used to separate routesper Authority - then additionalNetwork must be usedPlease note that the proper way to override Authority is with additionalNetwork.

Modeling for alternative operator information

All routes owned by the county municipality shall have the county municipality or the current administrative company as the Authority. Line data that is only Authority for lines operated under contract from a county should be the county, or its designated organization. Line lines delivered by the county miunicipality on behalf of other operators, has should (normally) have its own Authority within the data set's Codespace. This means in practice codespace. In practice this means that the customer is informed that the which Authority is responsible for the route, as well as for example . management and ticketing (note that customer service/contact information regardless of this is obtained from CustomerServiceContactDetails for the current lines' Operator).

If on some routes you want to display a different coimpanu information than what is stated in the Authority, you must use Branding. This is added by the following model:In some cases it might be prudent to slighty- or completely alter the contact and ownership information of a Line. Branding can theoretically be added to all levels of the Line structure, but Norwegian circumstances only require Branding application on Network, Line and Operator.

By default, a Line points to an Authority (via Network) and an Operator. By also pointing to a  adding Branding one can indicate that another information should be used insteadoverride Authority or Operator information. 

Link

The entire XML sample file is located on in the project's GitHub repository under : https://github.com/entur/profile-norway-examples/blob/master/netex/submodels/submodel-Branding.xml

Elements

ValueSet

Each Branding must be defined under Each instance of Branding is defined under ResourceFrame (as aTypeOfValue), with the specifying at a minimum the Name to be overruled value. 

<typesOfValue>
	<Branding version="1" id="SOF:Branding:1">
		<Name>Firda Billag</Name>
		<Url>https://www.firda-billag.no/</Url>
	</Branding>
	<Branding version="1" id="SOF:Branding:2">
		<Name>Nettbuss Sogndal</Name>
		<Url>https://www.nettbuss.no/</Url>
	</Branding>
</typesOfValue>

...

The referance element BrandingRef must be entered specified for the object where the "brand name" name, (and if applicable, other fields) is to be overruledreplaced.

Branding

...

on a Line

(forenklet eksempelsimplified example)

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

Branding

...

on a ServiceJourney

(simpliefied simplified example)

<ServiceJourney version="1" id="SOF:ServiceJourney:1"> 
	<BrandingRef version="1" ref="SOF:Branding:2"/>
	<Name>Sogndal-Kaupanger kai</Name>
	<TransportMode>bus</TransportMode>
	<TransportSubmode>
		<BusSubmode>localBus</BusSubmode>
	</TransportSubmode>
</ServiceJourney>

...