mapcat wrote:Good to know they're keeping MPs down. But it's hard for me to understand how/why they can be effective at that while being ineffective at suppressing paving. FWIW, people can certainly pave while driving navigable segments too, although thankfully they don't very often.

Eventually it would be helpful to see them in the client (ONLY after some other method of leaving notes in WME becomes available). Maybe that might limit the desire for paving.

Is there any point in encouraging Waze to change their behavior?

A lot of the chronic pavers are familiar with the editor and want to "add" things. If they already see it in the editor, they are less likely to pave it. I know, it's odd because you don't see the railroads on the map, but there's no explaining human behavior.

PhantomSoul wrote:This is an unfortunate side effect of locking everything we've reviewed already. In so-called mature areas, there's very little for local noob editors to do except pave railroads (that appear to not be part of the system on the client map), add every neighborhood tree as a landmark, and map every parking stall at the local 7-Eleven or corner strip mall dry cleaner...

We can lock all we want, but short of disciplinary action for repeated vandal behavior, I don't think we can really block noobs, or anyone for that matter, from adding new things to the map.

I would much rather have them pave away railroads (which don't show up on maps), then them starting to add individuals lanes to freeways and streets. Once again, end users want a consistent experience with navigation. If it's not consistent they will drop the app immediately. Trees, landmarks, etc, are annoying but have no effect on them getting from Point A to Point B. We can clean those as we find them. If a user can't get from Point A to Point B because a new editor came along and incorrectly edited things, they will uninstall the app immediately.