It's a network tag. The same applies to "ddot=yes", "smart=yes", or "fast=yes".

When I'm mapping these stops, I'm doing so from a moving bus, so I have to make small tags like those so I can keep up as the bus passes more stops. I then usually forget to remove them.

I'm uploading another changeset to address these tags within Downtown.

Operators. I surveyed the stops from a moving bus, so I didn't have time to make detailed notes on the stops. This was the best way I had to tell apart DDOT, SMART, and SMART FAST stops. Still, rather inattentive of me to leave them on the stops in the upload - will fix in a moment.

Followers of my profile may notice that this changeset is offset from my others by about... 600 miles or so. I'll explain in a journal on my profile.

Thanks for the catch! To be honest, those keys should never have been on those nodes in the first place. I've taken the erroneous tags off the relation members in my newest changeset (#57090144).

In the future, I may re-tag `ddot:downtown`=`yes` on stops to which their "Inbound CBD" fifty-cent fare applies (or just put that in a note). But as of now, those tags hold no meaning and should not have been there.

- Added stop_position for all stops of 275
- Added stop_position and platform to routes
- Fix the southbound 275 routing at Cherry Hill: the buses are allowed to make a direct left and actually do so

Yeah, I've used that on various routes when it removes ambiguity from other routes of the same number that don't go the same way, for example 450 SB: Pontiac => State Fair vs 450 SB: Pontiac => State Fair via Royal Oak.

... Just looked in the wiki because I thought you were wrong here.

You were right. There is no `start` or `end` key.

While I question those tags' applicability to this route in particular (`from` and `to` are the same stop), I'm going to update the rest of them to use the proper tags.

... Crap, I put the wrong source tag on the changeset. It was supposed to say DigitalGlobe Standard Imagery.