(should mention that there are TONS of nuances that don't fit into tweets.)
Two main issues with the proposal that don't make it a perfect one:
- It's too wordy, nobody would read it, despite the core idea is very simple (stop nodes).
- It challenges the current tram stop mapping (and nothing else).
The new PT schema should've been perfect in 2018 to be approved, and now it should be double-perfect, otherwise it won't pass any discussion. Everybody in OSM has their own opinion on PT mapping.
Keeping an up-to-date rendering database means relying on worldwide replication streams from osm.org or per-country streams from @geofabrik . But what if I want my own extract area?
In 2014 I dug into osm2pgsql's "slim" tables, and wrote a script to trim the data outside a given polygon:
https://github.com/Zverik/regional
I use it for my "veloroad" tile server, but not sure if it works: the database grows pretty fast. Maybe it's just because people are mapping more than ten years ago.