EveryDoor: Stop snapping of new address nodes to the 'nearest' building

Went on an address mapping survey and like the previous time all me new address nodes were snapping to the nearest building. In Italy you put the node where the shield is, an address does not go on a building area. Most very often the address shield is the driveway or garden entrance gate. No matter the distance and no matter what precision observed, not even adding the tags to say the address is at the barrier=gate, the address nodes snapped to the nearest building outline upon uploading. In some cases the wrong building at that. Any way to kick this bad Everydoor habit? (google and it’s AI proved once more utterly useless.)
thx

1 Like

Which button do you use? Door or building? The door one I think tries to snap them to a building, the building one doesn’t (if I remember correctly).

I tried to replicate this, but couldn’t… Used both Door and Building buttons on the House screen…

Analyzing on return, entrance=gate, entrance=door, entrance=yes would kick them to a building and if it could not, it would add a fixme note as well, On home coming had to correct the bunch.

When in ‘house’ mode it’s irritating anyway that an address would open up on the flats panel instead of house, but maybe as beginner my entry point with that tool is wrong.

Currently in EveryDoor you cannot influence the snapping of nodes to lines Snapping points to the lines should be switchable · Issue #541 · Zverik/every_door · GitHub

That’s expected. The wiki page for the entrance key says:

The entrance node should be placed on the building/area’s way (i.e. its outline).

1 Like

Thanks for all the input.

  1. With EveryDoor, don’t use ‘entrance’. You get unwanted like gates plomped onto building walls, overzealous snapping while assuming the mapper is grossly misplacing the address when in fact it’s placed where fences, hedges, gates are still to be mapped. QA like Osmose would have highlighted those anyway, the ‘fixme’ planted on a dozen because it was deemed ‘too far’ overdone.

  2. Two years after the ticket, don’t expect it to ever be given options to not snap, all or individual.

Next run before the end of the month, at least if the weather holds.

cheers

PS Might try Vespucci since recently installed on the mobile, but loitering to map details and looking conspicuous is not appreciated here… at least 3x ‘what you’re doing here?’ The guy at 33 would keep watching me until I left.

Well, the map rotation reset button was made three years later Button showing the map is rotated, that returns north-up on tap · Issue #409 · Zverik/every_door · GitHub

Create a separate ticket. I don’t really understand why it’s necessary to snap address nodes to buildings at all.

As promised meself, did another address survey run, EXCEPT, this time used Vespucci. Quite different and likeable… hit the locator icon to position the screen, downloaded fresh data, hit the big + (plus) right bottom and chose to ‘add tagged node’, hit screen in right position where civic number shield is, hit the magic ‘42’ icon and start filling in the address fields… housenumber, streetname (it fills in the remainder while typing), city and postcode (looked up on the fly), switch to detail tab if needing to add more tags, tick the ‘V’ left top to save. No snapping. It was 65km, > 1KKcal, 446 vertical up to get there for the main purpose… to confirm that the streetname change applied done by a mapper basing on a CCBY40 licensed site, ANNCSU, incompatible with OSM Odbl, and wrong to boot. 10 addresses added… 1 per 6.5km. The correct name is ‘still’ on the bus stop too, and conversing with the old resident at the very top @ 225a on the dead end road, same old same old streetname,




A few more addresses to map from the geolocated photographic evidence, so it will be 13 when done, and the beauty is, only need to change the housenumber with each new address as Vespucci remembers what it was the previous time \o/.

1 Like