Recent diary entries
Please see https://plus.google.com/u/0/events/c3ohfbgso96b1ahm1li1hba5auc for more information.
Looks like software that supports Mapdust is making it more difficult to create an invalid bug, the result being the number of bugs open has been steadily declining since August. Now's a good time to start using the Mapdust plugin in JOSM so you can spot and close bugs in the areas you're editing in realtime.
This one seems odd...just noticed it in my RSS feeds. http://www.mapdust.com/detail/233220/1/viewcomm
Something tells me that 90 isn't the actual speed limit for Lake Shore Drive in Chicago.
If you're in North America, I'm going over Mapdust cleaning out obviously invalid bugs and fixing what I can as I go along trying to get Mapdust back to something actually usable for the US and CA crowds...so if folks could start following the georss feed of open bugs for their usual area, that would really help for future bugs.
OklaDOT moved I 44 again, I'm sure of it, between OK 51 and the Arkansas River. also, there's a new detour between Red Forks and the LL Tisdale Parkway ramp on the MLK Expressway...does anybody have the latest GPS traces for these two locations? If so, I'll be happy to do the edit if you can drive through the construction detours both directions.
I know there's a few folks at TriMet working on geometry and access issues, however I do have a couple friendly requests:
Don't squash "name=" without double-checking it first. Most glaring example: The Robert Baldock Freeway is not "I5 Freeway (North|South)bound." Nor is the Boone Bridge.
Don't squash "highway=" without looking. At least make an honest attempt at figuring out why something is tagged the way it is before arbitrarily changing paths to footways, cycleways to paths, etc, especially if they're already part of an lcn relation.
Don't squash "cycleway=*" without looking or ground knowledge. I've noticed several instances of opposite_lane being cleared or set lane when the lane is only on one side.
I feel vaguely mournful when I map a cemetery, particularly if it's in a very small town or if it's a very large cemetery. Oddly, though, when I read the obituaries on some of the gravestones, such as when I hiked the Memorial Park Cemetery in Tulsa, I feel a bit less bad about how things will turn out. Then again, Tulsans tend to have a lot more noble deaths than Portlanders...
Ugh, I miss Tulsa. After getting let go from my driving job for poor job performance (out of 10 runs, I had six trucks break down on me requiring a tow, four automatic transmission failures, a broken tommy lift, and a truck with bad brakes that left me navigating a runaway through city streets(!), due to poor vehicle maintenance beyond my control), I more or less went nuts and drove back to Portland. I really miss Oklahoma...
Knowing that while Sunset Highway is technically Northwest and Southwest by Portland standards (so it's not absolutely incorrect), yet, ODOT doesn't call Sunset Highway by either quadrant where no addresses front Sunset Highway, nor does any commercially available data or ODOT data set, I added "Northwest" and "Southwest" to that highway, after long suspecting Google was wholesale copying OSM based on prior, more subtle, detail edits I had made to OSM in the western Oregon and eastern Oklahoma areas (and thus, all of OSM) for months going on years. Since Google picked up the "NW/SW" gotcha on Sunset Highway, to me, this removes all doubt.
Does OSM actually enforce it's license and copyright? If so, how do we get this ball rolling? I'm /not/ going to work for Google for free if they're not going to provide attribution.
Dallas/Fort Worth area could use some serious help, as reported by data consumers.
I'm going to start adding bugs to Mapdust as I find them while on the road trucking. Given the generally good availability of aerial maps and GPS traces in the areas I'm driving in, these should be fairly easy to locate for an armchair mapper. Most of the locations will be in eastern Oklahoma, with some locations in adjacent parts of Arkansas, Missouri, Kansas and Texas. See http://www.mapdust.com/?zoom=8&lat=4164934.6421&lon=-10808329.62579&layers=B0T for current bugs in this region.
OSM is being actively consumed by truck drivers in this region, and there's a *lot* of TIGER data needing review, so your efforts will definitely be appreciated.
I'm starting to upload traces taken from driving a goods van around Oklahoma and Arkansas. Using this to compare and contrast with aerial imagery will really help some pros on the road, since I'm sharing OSM with the other drivers at my company.
...anybody need a GIS tech?
All motorways in Oregon and Vancouver, WA have been explicitly tagged bicycle=yes or bicycle=no based on Oregon state law as published by ODOT (in Oregon) or local knowledge based on signage (to the best of my knowledge in Vancouver). The following locations in this area are tagged bicycle=no:
* I 5 from I 205 in Salmon Creek to OR 217 both ways.
* I 5 from South Medford to North Medford both ways.
* US 26 from the PGE Park exit to I 405 both ways.
* US 30 from 26th Avenue to I 405 both ways.
* I 84 from I 5 to 122nd Avenue eastbound.
* I 84 from Wood Village to I 5 westbound.
* I 205 from OR 43 to WA 14 both ways.
* I 405, entire length, both ways.
The rest of I 5 in Oregon (and the southbound approach to I 205 in Washington based on several "BICYCLES MUST USE I 205" sign on I 5) is posted bicycle=yes, as is the rest of I 84, I 82, and US 26. There are no freeway portions of US 30 that permit bicycles (as the only freeway portion of US 30 is the above mentioned section). WA 14 is tagged bicycle=yes due to lack of signage and having personally used that segment by bicycle without WSP getting involved, as was a small portion of WA 500. Motorway links connecting to segments closed to bicycles were also tagged bicycle=no, whereas links that connect to open sections were tagged bicycle=yes.
I also changed a couple sections that were improperly tagged as motorway to trunk based on local knowledge (part of US 97 and part of OR 22).
In addition to the source:url for that changeset, the actual OAR (Oregon Administrative Rule) is available at http://www.oregon.gov/ODOT/HWY/BIKEPED/docs/freeway_ban.pdf
Mapdust in Oregon now only contains workable bugs, mostly in places requiring some TIGER cleanup.
I could be wrong...but I that just might be State Route 66 here...
I wonder how many people are keeping an eye on MapDust in the United States. The number of bugs has dramatically increased in the last few weeks, but it seems like I'm about the only person making any real progress (based on the number of bugs I can't reproduce or have resolved myself in the two states I'm following, relative to the number of open bugs). This is easily one of the best QA tools we have right now since we have human input (although a lot of human error) on what's getting reported.
The National Broadband Map shows where there's high speed internet coverage in the US. It uses OSM.
The remaining Missing streets, Roundabout issues, Missing speed infos, and Others on Mapdust in Oregon are ones I don't know how to fix or are going to take time to fix. I'll get to the other categories before long.