Opened 15 years ago
Closed 14 years ago
#4236 closed enhancement (fixed)
Hide boundary=administrative by default
Reported by: | delta_foxtrot2 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: | delta_foxtrot2 |
Description
I'm not sure what the best way to handle this is, but administrative boundaries are being re-purposed and incorrectly joined and screwing up town/suburb relations as a result.
While it's something useful to use this boundary information for plotting rivers and such so not displaying them would be detrimental as well.
An example of what I mean is the town/suburb boundaries in Australia, these were previously batch imported, but due to people incorrectly joining ways they have broken these relation boundaries.
Attachments (0)
Change History (9)
comment:1 by , 15 years ago
Cc: | added |
---|
follow-up: 3 comment:2 by , 15 years ago
comment:3 by , 15 years ago
Replying to bastiK:
The current policy is to show everything there is in the database. If some ways (like boundaries) are just hidden, it would be confusing and might cause even more data corruption. A better way would be to show a warning whenever the user attempts to edit an existing boundary.
Unfortunately it isn't that simple, there is a lot of boundary ways in Australia, many follow roads and railways that don't exist in the database yet so every time you go to add a new way you can inadvertently end up editing an admin boundary.
comment:4 by , 15 years ago
I was told today that in Merkaartor you can make it show administrative boundaries as big blue dotted lines on the map in a rectangle around the extreme points in the relation, or turn it off and not be alarmed by big blue dotted lines going everywhere.
Can we get an option in JOSM to hide features on the map, such as administrative boundaries please.
comment:5 by , 15 years ago
I'm fixing boundaries yet again that have been caused by potentially inexperienced users changing things that break admin polygons, in this case postcode boundaries.
comment:7 by , 14 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
So is it possible to add a default filter to the JOSM config and have the filter panel open by default, this would make things more obvious to newbies who are the ones that need it the most, rather than those that already know about complex filtering rules.
eg.
http://wiki.openstreetmap.org/wiki/Australian_Tagging_Guidelines#Hiding_admin_boundaries_in_JOSM
comment:8 by , 14 years ago
Having filter presets is a good point. But we cannot have them enabled by default for all JOSM users.
(Best you could do is provide an "Australia-mod" plugin which, among other things like presets and styles, adds this filter default you prefer.)
comment:9 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
I'm against default filters. Users need to know what filtering means and they need to be aware what dangers result from this. Default filters will cause more harm than good.
The current policy is to show everything there is in the database. If some ways (like boundaries) are just hidden, it would be confusing and might cause even more data corruption. A better way would be to show a warning whenever the user attempts to edit an existing boundary.