bgodette wrote:Except of course when it's suffering from the GPS->Car on map translation table bug that's been present ever since 3.0, and is still in the current betas.gettingthere wrote:I agree that it sounds very unlikely that Wazers driving on the main road, on a route are being snapped to the Parking Lot roads. The Waze application has a very strong snap-to-route.
DaveHolzmann wrote:As for Phyllis Ave. split... mea culpa. That was a (brief) venture I took to try to go beyond the parking lot. It was accepted before I learned the guidelines for not splitting a road. (I had figured, since there was a serious barrier between the two lanes of traffic, it made sense to split it, and clarify where/why side streets/drives would/wouldn't be able to make certain turns. I had not read the Wiki about split roads, and had failed to consider the lack of accuracy of GPS tracking. At this point, it seems like it would be more work to un-split it. And, unless there are any URs that I made errors in allowed/disallowed turns, I wonder if it should be changed.
DaveHolzmann wrote:The restrictions near the entrance/exit were ones I intentionally "added" - because I've found MOST of the time, even though those turns are technically allowed, the drivers who try to make them create traffic jams, either by physically blocking others or by scaring other drivers who aren't expecting them to jump out in front of them as they're just getting into the lot or trying to catch the signal out of the lot. I suppose you could say, they're restrictions the I think SHOULD be there.
AndyPoms wrote:I'm really hoping for a PM/forum post from the user asking why it's locked and I'll refer them to this thread and to talk to you.
Users browsing this forum: KC-Guardrail