I could be wrong and in this case, it might be fine. However, it has been my experience that it is preferred to have a generic building, with a detailed POI Node. ... It is simple matter to upgrade a POI, by surrounding it with a generic building. It works well for buildings containing multiple POI nodes. Some editors, like OSMand, will only allow editing POI nodes. Google seems to be doing well with the generic building and detailed POI technique. Etc.

I know better. It is "right OF way", not "right-a-way". Not enough coffee.

Thanks for joining the fun and mapping Evergreen Cycles. Just so you know, only the house number, street and occasionally an addr:unit need to be tagged.

"Tags such as Key:addr:country, Key:addr:city, Key:addr:postcode are often redundant as features inside administrative boundaries (when mapped) "inherit" their attributes..." -- osm.wiki/Addresses

That would probably be, because the two ways were not connected. I've just corrected this. changeset/44713128

Not sure the best way to tag this. So far, three different tagging schemes have not made the name show up, only the house number.

Wish I had more time.

What would REALLY be nice, is if CATA would take the task on. I wonder if OSM has an easy way for public transportation administrators to maintain their routes.

Mind me asking where you got the data for the bus stops and routes? Did you have to gather it manually? I keep thinking there must be a way to pull stop information from CATA's HiWire web application (http://tp.cata.org/hiwire). CATA must have given this same data to Google, for their maps. With stop times even.

I like the way the competitors are doing it. Generic building with a POI point.

Should this be a point at the front door, on a generic building?

Why would this minor change appear, in the history, to affect a large portion of the world?