|
118.
|
|
|
boundaries
|
|
|
please keep this as short as possible
|
|
|
|
grenser
|
|
Translated and reviewed by
Skippern
|
|
|
|
119.
|
|
|
Administrative Boundaries can be expressed either by tagging ways or by adding them to a relation. They should be closed-loop sequences of ways, they must not self-intersect or split and they must have a name and an admin_level.
|
|
|
|
(no translation yet)
|
|
|
|
120.
|
|
|
missing name
|
|
|
please keep this as short as possible
|
|
|
|
manglende navn
|
|
Translated and reviewed by
Skippern
|
|
|
|
121.
|
|
|
missing admin_level
|
|
|
please keep this as short as possible
|
|
|
|
manglende admin_level
|
|
Translated and reviewed by
Skippern
|
|
|
|
122.
|
|
|
not closed loop
|
|
|
please keep this as short as possible
|
|
|
|
ikke sluttet ring
|
|
Translated and reviewed by
Skippern
|
|
|
|
123.
|
|
|
splitting boundary
|
|
|
please keep this as short as possible
|
|
|
|
(no translation yet)
|
|
|
|
124.
|
|
|
admin_level too high
|
|
|
please keep this as short as possible
|
|
|
|
for høyt admin_level
|
|
Translated and reviewed by
Skippern
|
|
|
|
125.
|
|
|
restrictions
|
|
|
please keep this as short as possible
|
|
|
|
begrensninger
|
|
Translated and reviewed by
Skippern
|
|
|
|
126.
|
|
|
This check is about turn restrictions defined by relations. A turn restriction relation needs a valid type attribute, a way as 'from' member, another way as 'to' member and optionally one or more ways or nodes as via members that need to be connected to 'from' and 'to'
|
|
|
|
(no translation yet)
|
|
|
|
127.
|
|
|
missing type
|
|
|
please keep this as short as possible
|
|
|
|
manglende type
|
|
Translated and reviewed by
Skippern
|
|
|