While we're on subject, I'd like to address the parking lot road navigation problem as well.
When you're driving around a bunch of unnamed parking lot roads, the client will grab the name of the next names road and repeat it with each instruction. Great for ramps, confusing and annoying for shopping centers.
We have two options, as I see it, both of which would need some degree of programmer intervention.Option 1: Remove the "next named road" function for parking lot road type segments.
Reprogramming the client to say just "Turn left" or "Turn right" when navigating through unnamed parking lot roads would fix the problem with no editor intervention. This would also arguably provide clearer instructions.
The problem is that we are at the mercy of the programmers here. Another potential problem is if somehow the programmers get it wrong, disabling the next-name finder on more than just parking lot roads. This would be a huge
problem. Ramps and at-grade connectors would not work at all. And that's if we get the programmers to do it at all. Option 2: Start giving parking lot roads generic names and exclude them from search.
Changing editor policy to require the inclusion of generic names for parking lots would be an easy fix that would require little to no programmer intervention. It would give instructions that are arguably even more clear than option 1: "Take a right at Parking Lot", for example.
Drawbacks are that we'd have to spend a lot of time editing, and we'd have to come up with a set of acceptable generic names and guidelines to go with them. Also, we'd have a few extraneous search results, maybe, but considering that Jason and I have hundreds of segments called "U turn" or "U-Turn" around here, it seems like it wouldn't be that big a problem:
I don't know which I prefer, but I'm leaning toward the latter. What do you think?
Sent from my iPhone using Tapatalk 2