[qrv3w]

I agree it could be part of OSM, but keeping it up-to-date is really tricky. Piano locations are impermanent structures and information can become outdated in just a few weeks. It would take a lot of effort to keep it up-to-date and there are very few people willing to put in that effort (i.e. "few" because the union of groups of people that love public pianos and like editing OSM is small).

[dewey]

Could it be synced back to OSM so that people can submit in your nicer interface but it'll flow back into OSM? I'm honestly not super familiar how open OSM is for things like that.

[stereo]

The pianos.pub could be an osm editor that just edits pianos, based on https://wiki.openstreetmap.org/wiki/MapComplete

[ancarda]

There's lots of prior art, such as https://wheelmap.org/ -- so I imagine OSM is somewhat open to this sort of thing. Might be worth looking at how Wheelmap edits OSM. I believe it's from a generic account and edits are tagged such to make it clear it's from a member of the public.

You could also implement OAuth (sign-in with OSM) to do edits, similar to how some tools like https://maproulette.org/ work, though you'll get less contributions if you don't have an option for anonymous public edits.

[defanor]

Haven't tried it myself, but there are automated imports going on here and there, and a few wiki pages (including a code of conduct) on the topic too: https://wiki.openstreetmap.org/wiki/Automated_edits

[pabs3]

Pianos are pretty heavy and probably don't move around that much?

[zymhan]

I'll have you know I take my piano on long strolls every evening to stretch his strings

[stereo]

Don't move around that much? Classic mistake. https://www.youtube.com/watch?v=pD8I6SG_DAU

[Gigachad]

Not to mention that a lot of downstream projects using the OSM data set only update once every few weeks / months so by the time the data hits, its already old.

[PennRobotics]

Idea: list pianos as speed traps