Talk:Non-drivable roads lock level View history

(Added list of arguments)
(Added arguments from stelling28)
Line 12: Line 12:
* Since the introduction of phantom nodes, connecting non-drivable segments no longer creates unwanted nodes on the drivable segments
* Since the introduction of phantom nodes, connecting non-drivable segments no longer creates unwanted nodes on the drivable segments
* There are hardly any reports of errors based on this sort of routing, making a high level lock feel like overkill
* There are hardly any reports of errors based on this sort of routing, making a high level lock feel like overkill
* House numbers are a lot of work, so the more editors can do this, the better it will be
* What the best place to park/stop with a car is, requires local knowledge, of course combined with editor knowledge. But again to more editors can edit these segments, the more local knowledge is used


===Things everybody seems to agree on===
===Things everybody seems to agree on===
Complex situations should always be locked appropriately. If a segment is important for proper routing, it should be protected against mistakes of starting editors.
Complex situations should always be locked appropriately. If a segment is important for proper routing, it should be protected against mistakes of starting editors.

Revision as of 09:15, 4 June 2018

Arguments for locking at L3

  • A segment locked at L3 is seen as confirmed, as non-drivable segments are removed if they do not contribute to routing
    • In practice this only applies to the Netherlands, Belgium does not do this
  • Walking Trails have an effect on routing, so they should be locked
    • The same logic would require all regular streets to be locked at the same level, but obviously exceptions can be made
  • The logic between the categories of non-drivable segments is a bit more complicated for new editors

Arguments against locking at L3

  • Locking at level 3 will block new editors from adding missing non-drivable segments or adjusting connected local roads, causing frustrations
  • Since the introduction of phantom nodes, connecting non-drivable segments no longer creates unwanted nodes on the drivable segments
  • There are hardly any reports of errors based on this sort of routing, making a high level lock feel like overkill
  • House numbers are a lot of work, so the more editors can do this, the better it will be
  • What the best place to park/stop with a car is, requires local knowledge, of course combined with editor knowledge. But again to more editors can edit these segments, the more local knowledge is used

Things everybody seems to agree on

Complex situations should always be locked appropriately. If a segment is important for proper routing, it should be protected against mistakes of starting editors.