not dismissing your work, but I think my way is easier and a lot more in line with the norm

Map the whole parking area as amenity=parking

Thats it. 1 polygon/closed way

If I know the info, I will add capacity, operator etc

I’m not sure I see any benefit in mapping spaces to this level of detail (and I’m a lover of micromapping)

One major downside is the visual clutter it would create due to the amount of Parking icons appearing on the map

Is that not achieved by using the country boundaries (relations)?

About the only thing I use iD for is mapping turn restrictions. It makes it sooo easy.

For everything else I use josm but that’s the to say it couldn’t be improved or doesn’t have “quirks” of its own

thats some nice mapping, nice work!

“Most difficult part of OSM is the “nobody needs that” approach on tagging and talk mailing lists. Guys, just think, If somebody uses a mailing list, which is pain by itself, to ask you what is the best approach to map a thing, there is a demand for that kind of things to be mapped.”

I like your logic

ok, now one for iD ;)

Well done, fantastic and hugely useful

No, dont have linux installed or virtual machine

You lost me at command line :P

@BushmanK no we havent gotten to that stage yet.

Right now we are working on completing as much of the validation work before our next trip in Feb.

One of the goals during the in-person training will be the use of KeepRight, OSMI, Overpass etc for further improvement of the data.

This validation sprint is more focused on making sure the task requirements have been met for each tile to as high a standard as possible.

I would love to load up all the additional validation tools as part of this sprint, however I think it would be too burdensome at this stage

Going to have to check out that PT route plugin, cheers :)

leisure=picnic_site - 100 items tourism=picnic_site - 83,313 items

In other words, of 83,413 sites, 0.12% are tagged as leisure versus 99.88% tagged as tourism

I think its safe to conclude leisure is obviously incorrect

Lets not over complicate where its not needed.

If they’re tagged wrong, they should be corrected.

Nice work!

I really like this. I am going to have to play around with it during the holidays.

Awesome work

Many thanks for doing this. Its just a shame this isn’t something we could do automatically

great interview

That volume of edits is easy to do if you are doing something like realigning / enhancing previously mapped content.

I only ask because you don’t mention it, but does your script avoid merging where pieces belong to relations?

The waiver program, honestly never knew about that

I was hinting at something more along the lines of what @Vincent suggests. Something that is automatic and requires minimal oversight and maintanence during the year.

I can’t see any other method having much success and I don’t mean that as a criticism, just that if possible, the simplest solution should always be applied

@nighto, didnt realise that :)