Here is a picture of the area in 1953 (pre beltway). You can see the actual radio towers. There used to be a connector road here, so the state may have desired to keep it alive with this road.

https://dl.dropboxusercontent.com/u/274 ... _7_309.jpg (too large for inline)

In order to preserve the traffic data on brooks robinson, might we try trimming the node at the intersection with stevenson?

I might do this by using a fake roundabout to eliminate the ends of the roads at the intersection. Then, combining the nodes to rebuild the intersection, deleting the RB in the process.

This might reset the intersection, while keeping traffic data on the questionable segment.

I just checked, and I don't have heavy traffic on it right now, but who knows.

I was about to share the same article. It seems like it functions as a sort of park-n-ride. I wish there was a way to suppress traffic data on it.

Change it to a ramp?

I think a parking lot landmark actually may be more appropriate for this location.

Okay. Following my three-editor rule we have consensus on removing the railroad. I'll take it out.

Do we want to place a tiny landmark instead? I say no.

My guess is that the signal at Brooks Robinson and Stevenson Rd causes a backup on Brooks Robinson. However, I've been on this section at both ends of rush hour and didn't have any problems.

How about adding a parking lot road on either side of Brooks Robinson? Would Waze assume if someone was stopped that they must be on the parking lot road?

I agree that a landmark would be more appropriate. But I am still wondering whether a parking lot road would fix the routing issues here. If someone who has Waze running pulls off Brooks Robinson onto the parking lot road what happens?

It looks like the solution on Brooks Robinson is working. I say delete the railroad note. I can keep an eye on this segment.