Key:HU:hu-go

From OpenStreetMap Wiki
Jump to: navigation, search

A Key:HU:hu-go szócikk magyarul is elérhető.


Hungary has launched a use-proportional road toll system for vans and trucks over 3.5 tons in 2013. The exact rules can be found in the law text (Nemzeti fejlesztési miniszter 25/2013. (V. 31.) számú rendelete). Appendix 1 enumerates the toll road sections. Use-proportional toll is established by a direct proportion between the fee and the section length, and by requiring a new ticket for each use (and for each direction). Contrary to the toll system for cars, there is no duration-based vignette, season ticket, or other bulk discount.

Use

The HU:hu-go namespace contains the following keys:

Key Value Element Comment Taginfo
road 82 Node Way HU:hu-go:road contains the name (“M6”) or number (“82”) of the road with respect to toll payment, coming from Appendix 1.
milestone 120 + 31 Node HU:hu-go:milestone contains the kilometre session of the toll road with regards to toll payments, in km + m format (like „120 + 31”). Leading zeros are generally not used but it may appear (like in “47 + 077” for 381u47k077m). It is typical for new bypasses that segments are not re-numbered therefore values over 1000 are present for the metre part (like “44u125k2983m”).
length 1478 Relation The value of HU:hu-go:length is the length of the section (in metres) with respect to road toll payment, assigned by the above law. This number does not necessarily match the difference between the start and the end road sessions, neither does it match the physical distance between these two points. (This is why it is not enabled for way elements.) The section length not only determines the toll to be paid but various rules of section ticket purchasing depend on it. If this key is used on relations, the relation usually refers to the ref:HU:edid key that identifies the section.

Remarks

National Toll Payment Plc issues a map of the toll sections, as an appendix to the law. This map is inaccurate in many cases, it is often obsolete, and it has completely wrong geometry or topology at some places. Due to these problems, there is no OSM way created and attached to these data.