Relation:preferredEntry

A preferredEntry relation is meant to hint routing applications as for the way to get to the destination address if the access is not free, or the publicly accessible highway closest to the address is not a convenient end of route (e.g. routing ends on one side of a building and there is a big parking on the other side, but accessible from another side of a quarter).

Algorithm for a routing app to use such a relation:

1. for a destination address find all the preferredEntry relations it belongs to
2. for every preferredEntry relation found, find all the entries of desired type e.g. vehicle when routing for a vehicle
3. if the result is exactly one object with coordinates, route through or to this entry point

NOTE: It may be assumed that when the app user goes through this entry point, they have got access to highways marked private from entry point to destination address.

Tags

Key	Value	Description
type	preferredEntry	(mandatory)

Members

Object type	Role	Recurrence	Description
	address	One or more	Any object that may be found by a street address
	vehicle	Zero or one	An entry point for vehicles
	foot	Zero or one	An entry point for pedestrians
	hgv	Zero or one	An entry point for heavy goods vehicles
	emergency	Zero or one	An entry point for emargency vehicles

Only use hgv or emergency roles if the entry point is different than vehicle or vehicle does not exist. It is on the routing engine's side to decide what kinds of entry point it will search for.
Any other value used for access restrictions (like bicycle or horse) may be used if there is a special entry point for them.

See also

• Relation:provides_feature
• Proposal:Associated Entrance