Looks an odd editor bug, but several of these bus stop names have numbers randomly inserted in. I removed them in changeset/34255087. I’ve never ridden TANK before, so let me know if this is some strange convention they have. :-)

That's a good point that I hadn't considered, although OSM's landuse tag isn't intended to strictly match zoning in every case. (We also don't tend to subdivide landuse areas according to legal subdivisions like you'd find on a tax assessor's map.) I did go ahead and tag the building as an event venue; the area surrounding it still feels primarily like a recreational area, so I went with leisure=park. That said, I've only been there once (last Sunday), so maybe I'm jumping to conclusions from that one visit.

The Drees Pavilion overlook area definitely isn’t landuse=commercial. That tag is meant for office parks…

Hi, it looks like you accidentally commandeered the Tempe point of interest (POI) for the SkipperBud’s boat shop. :-) I cleaned things up in <changeset/34236043>. In the future, please create a separate POI when you want to add something to the map. If you need help while using the editor, press H to display some instructions. Feel free to contact me if you need more help.

After tagging enough “empty” VTA bus stops in San José (with a shelter or bench and a Bus Stop sign that lists no routes), I’ve come around to the idea that the magnificent new streetcar shelters should be tagged as real stops that don’t yet belong to any route relations.

changeset/33995382 corrects track information in and out of Millbrae station.

No worries, I’ve been known to get ahead of myself too, and it’s clear you had good intentions. :-) At this point, maybe the best course of action is to send a message to the [email protected] mailing list. (Or post a diary entry.) Explain the change you made and the reasoning above, and offer to help change individual POIs back if for some reason any exceptions should have been made. That should help to get the word out and offer people an opportunity to agree or disagree.

Can you point to consensus about amenity=fitness_center being incorrect (despite the preference for UK spelling)? osm.wiki/Gym_/_Fitness_centre is very ambivalent on this point, and until this changeset, amenity=fitness_center was one of the more popular options. A public awareness campaign should’ve taken place ahead of this change.

Thanks for adding this information – I had no idea it used to be a landfill. I changed some of the tags on this POI to be consistent w/ how historic features are often tagged. In iD, you can see them under “All tags” in the sidebar. Please let me know if you have any questions.

It is strange. I visited exactly a year ago; at the time, there were electronic signs to alert drivers to the change, and the local newspaper was full of questions about whether the increased flow was worth the confusion. MoDOT built the country’s first divergent diamond interchange up I-44 in Springfield, and I guess they’re confident that it works.

I sketched in the new interchange from (one-year-old) memory in changeset/33190964. Please feel free to correct it if it doesn’t match what you observed.

Or rather: osm.wiki/Ohio/Route_relations

I tried my best to transcribe a bilingual sign I took a photo of while passing by. The Amharic name is a little more detailed than the Engilsh name. It transliterates roughly to “Debre Genet St. Mary Beta-Christian Ethiopian Orthodox Tewahedo Church in San Jose”.

`name:en` is for English. I went with `alt_name` because these expanded names are what people would tend to search for in a geocoder like Nominatim.

Good idea, though not everyone has easy access to Greek characters on their keyboards. I wonder if the Greek characters are better suited for `short_name`.

Also, Φ is phi, Τ is tau, and Θ is theta. In changeset/30993287, I took the Greek characters currently in `name` and expanded them in `alt_name`, assuming that you got the names wrong originally. But if you had the names right originally, then they should be ΔΘΔ and ΠΚΘ.

Awesome, thanks for taking the time to do that.

I figured that OSM-based public transit routers would have no way of knowing that the stops have no service yet. The poor hapless users would be waiting far longer than the standard Metro wait…

For context, I was getting a bit fed up with the many under-construction and proposed BART and Muni stops that were tagged as being complete:

changeset/30491130

I’m definitely open to more specific tagging, though. `railway=fingers_crossed` ;-)

OSM classifies population centers based on population and prominence, regardless of legal status. That way software based on OSM don’t have to worry about every country’s definition of a city when labeling cities a certain way. So as a suburb to another city and as a place with under 100,000 residents, Springdale is tagged place=town, not place=city. Please see <place=city> for more information.

Bing aerial imagery in this area is a bit outdated (dating to summer 2010). The Mapbox Satellite layer is more up-to-date at zoom levels 13–17 in Ohio, drawing from NAIP 2013 imagery. You can see the mast’s shadow in that layer.

http://mvexel.dev.openstreetmap.org/bing/

FYI, man_made=mast is the more appropriate tag for radio/broadcast/cell towers. man_made=tower is for things like watchtowers, and it doesn’t get a special icon on most maps.