OK, this is a total pisser from a Debian perspective…can’t seem to get traffic generated.

Damnit, Australia, get on board with specifics! National Highways should be AU xxx and state highways should be the postal abbreviation and XXX (NSW 391 or WA 47 as possible examples).

OK, it’s been a bit of work using it for tagging, but some things I’ve noticed:

• destination and destination:lanes is far less ungainly than a simple exit_to or relations
• I’m not convinced Osmand uses this data yet. It certainly would be handy to validate things, since I’m currently working to implement this state wide as part of my lanes and relations completion project.

The turn lanes plugin should not be used at this point, as it uses the scheme that Has Lost The War™. turn:lanes is the way to go, it’s the one that has consumer and rendering usage at this point, and the easier option to wrap your head around.

I would hope you’re also contributing this data to radiocells.org (especially if there’s any wifi data inclusive).

So, am I to surmise, based on Bubble’s presence in this thread, that something’s fucky?

This seems to be a common thing with local US governments. The data is open, but often citing some really thin vineer of excuses to charge for access to the data directly from them. The primary audience tends to be realtors and land developers who generally don’t give a shit about spending the $50 to get the current official dataset.

The level of difficulty is that even though this data is digital, this might actually require driving to 77 different cities and picking up 77 CDROMs…which I’m not personally opposed to doing at all, since I could trade shifts with a coworker and start doing it on my days off (along with collecting other data using Mapillary), but the expense of doing so is prohibitive.

Except you can do that in JOSM with osm.notes.daysClosed…

Oh man, dual carriageway mapping (or the lack of it) drove me fucking bonkers when I first started editing Tulsa. The big divided boulevards now have (and have had for a couple years now) full mapping of the medians with service stubs at driveways. (U-turns are generally allowed in Tulsa, but at the time I was driving a bit of a boat, which requires a bit of extra planning; now I got a Kia and I can swing these much easier, though it does make me wish I had a U-turn signal).

I don’t really think name=* is the appropriate place for route numbers stopping at the stations.

It wouldn’t surprise me if literally half of the currently open notes are mine, right here in Oklahoma.

I’m in favor of burying the exit_to dinosaur, simply because I know of many center-lane (OR 8 from westbound U26), left (westbound I244 to southbound U75) and ambigious (U26 to Market Street; west I244 to north U75) exits that don’t fit classical definition, yet are, exits).

No, I’m against name=Exit 77. I’m in favor of ref=* on destination=* relations, however. Mostly because North American ramps often have multiple exit refs on the same ramp to start with. I can think of several in the Portland, Oregon; Vancouver, Washington; and Tulsa, Oklahoma areas without trying (and, in Vancouver’s case, minor edit wars, thanks to exit_to being hamfisted).

destination=* also fits for a LOT of awkward edge cases exit_to=* doesn’t. For example: A four-way crossroads. Would be nice to come out of a side road and get a direction like, “Turn right on OK 11, then in a quarter mile, turn left on to CR XYZ, to Ramona (via county road)”. Which would be an improvement over the current usual OSM direction of “Turn right on OK 11, then in a quarter mile, turn left to CR XYZ,” or Garmin’s equivalent, “…then turn left onto Unnamed Road.”

I really wish that there was a good way to proxy cache HTTPS. Or, heck, cache HTTPS. Most browsers won’t do it, and (obviously, duh) it can’t be transparently cached with squid. HTTPS is definitely much more bandwidth intensive than HTTP, which is still a big problem: Much of the US is still on dialup, and pretty much everywhere that isn’t Scandinavia or South Korea isn’t exactly doing much better.

Footways? Or paths? If it’s really narrow, like, two bikes can’t pass head on without someone pulling over, footway=yes is definitely appropriate (if bikes are allowed, bicycle=yes is appropriate). Are bicycles allowed? Is it wide enough for two bikes to pass head on without slowing? Then highway=path is a better fit. Are pedestrians banned or is there a painted centerline? Then highway=cycleway (and possibly foot=yes) is appropriate.

Brooklyn Roundhouse was demolished the week of my return to Oklahoma in August 2012.

That canal’s centerline could use some extra nodes. And a shoreline.

The intersection of the Equator and Prime Meridian is called “the origin.”