Contribution frustrated in Mountain View, CA

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: krankyd, Unholy

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Mon Jan 14, 2013 9:03 pm

Never mind... the same individual (whom I've never found here on the forums) seems to have deleted my work once again.

I guess I will need to re-do the parking lot outlines and then request a lock on them.
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Mon Jan 14, 2013 10:06 pm

OK, finished re-doing my work on one of the parking lots. Would one of you higher-level Wazers please lock it down? Thanks in advance!

https://www.waze.com/editor/?lon=-122.0 ... 2,70695726

EDITED well after the fact to add: There is another page to this thread. This HAS BEEN LOCKED. (No need for anyone else to feel stupid. :) )
Last edited by DaveHolzmann on Tue Jan 15, 2013 1:31 am, edited 1 time in total.
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Tue Jan 15, 2013 12:41 am

AndyPoms wrote: ... if it gets deleted again (by a level 5 editor). If it does, there may be evidence as to who did the deletion on the main roads out front (i.e. last modified will change if two segments are merged when a junction is deleted).


I think that's unlikely, as the last time they deleted my work the segments on the main roads were left separate. (I STRONGLY suspect it was another level 1 editor.)
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Tue Jan 15, 2013 1:05 am

kentsmith9 wrote:I did some basic work on your other lot https://www.waze.com/editor/?zoom=6&lat ... TTTTTTTTFT to the protected segments if you want to do some final touch up on it.


Thanks!

At this intersection https://www.waze.com/editor/?zoom=8&lat ... s=70697762 you cannot just drive across to Oak Ln. The geometry just isn't quite there. You'd either have to drive the wrong way S on Grant before getting into the L turn lane, or go around the median and risk being hit by S-bound traffic on the other side, or drivers turning R out of Oak. ;)

Regarding other segments in this lot ... as I understand the Parking Lot Wiki, it seems like one helpful thing would be to add the lanes that run parallel to ECR in order to "capture" the parking lot traffic so it's not messing with traffic speeds on ECR. It would also be helpful to add the entrance/exit directly onto ECR that's used by both the gas station and the rest of the strip-mall's customers.

One final note: while the gas station is "Coast Gas", in the app it's listed as "Houtan Petroleum". I've never heard of "Houtan" and never found any other (current) source that uses that name. (And my spouse - who's lived in this area for decades - doesn't recall it EVER being called "Houtan".) Now, it's possible that there's a Houtan Petroleum corporation behind Coast Gas. But no Wazer will find a Houtan Petroleum anywhere near that corner.
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Tue Jan 15, 2013 1:22 am

kentsmith9 wrote:I did some basic work on your other lot https://www.waze.com/editor/?zoom=6&lat ... TTTTTTTTFT to the protected segments if you want to do some final touch up on it.


Because this segment https://www.waze.com/editor/?zoom=9&lat ... s=70697758 is locked, the two adjoining segments could not be connected to it, nor have all the turns been allowed.

When that's fixed, (along with the edit mentioned above), I think this lot will be done... enough for now. (Some day, when we've got the rest of the city, county, state, etc. completed, and GPS's are accurate to within 2', we'll undoubtedly have time to get to mapping every parking space. :lol: )
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Tue Jan 15, 2013 1:35 am

Spil wrote:
shawndoc wrote:FYI, it now shows locked by me because I'm stupid. :oops:

If you're stupid, you're not the only one. Because the lock request was at the bottom of the page (and I didn't see that there was another page), I went there too ... then when I started to lock it, I saw that Shawn and Jason had both locked those segments, so I didn't bother saving my locks. I did go back in, though, and fixed some soft nodes in the parking lot -- so there are a few there with my name on them as well now. Perhaps when the guy sees locks by three different L5's, he'll start to get a clue about that lot. :lol:


No more worries. I've edited my post on the bottom of pg 2 to note that it'd been locked. Hopefully no one else falls into that trap and feel stupid. ;)

Spil wrote:EDIT: Maybe I can be helpful -- I fixed that intersection that Dave mentioned while I was typing the above. ;)


Thanks!
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Tue Jan 15, 2013 8:23 pm

Kent,
I see what you're saying about directionality within PLots. The perfectionist within me screams "NO!! That's not precisely right!!" But the pragmatist recognizes that (hopefully) people are paying more attention to the real traffic right in front of their face and less attention to their Waze when they're driving slowly through a PLot. And, while accuracy is nice, and good, and important in some situations, there are (sometimes, such as this kind of situation) higher priorities which trump technical accuracy... especially when GPS's are typically only accurate to about 25-50 feet.

I don't know if we'll EVER have conclusive evidence of who "our Sniper" is. But I strongly suspect it's the individual who last edited the Oak Ln segment that connects to Grant Rd. (I can't tell what s/he did to that segment that wasn't already there.)

Thanks again!

Oh, and I certainly HOPE that all this brouhaha over PLots is not the "norm". That would make this particularly un-fun and tedious!
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Tue Jan 15, 2013 10:37 pm

gettingthere wrote:Why not just use a Parking Lot Landmark if you are concerned about traffic suppression when Wazers are in the lot?


Gonna show my ignorance...

I was not aware that a PLot Landmark would have that effect. I thought it was just a "note" that that's where one would find parking. Not that it would affect traffic patterns/directions/speed. Or put another way, I didn't think Wazers would "snap" to a Landmark.

Is that what you're saying a PLot Landmark would do? Or something similar to that??

gettingthere wrote:Also, unless things have changes if the last segment that a Wazer was on was a Parking lot road traffic reports should be suppressed as long as the Wazer is not snapped to a non parking lot road segment.


Now I'm a bit more confused... are you saying that on PLot roads, directionality of traffic doesn't matter? That Waze doesn't "flag" wrong-way drivers as an automated UR? If so, that seems to fly in the face of what Kent was saying.

gettingthere wrote:Although my long standing opinion is that the client should be less snappy. If a Wazer is driving anywhere that is not mapped there should be no jams created. Should be no need for any of this mapping/landmarking of Parking Lots to avoid false traffic jams. Waze needs to focus more resources on fixing this mess without the community having to over-map.


I think I'm too new to have an educated opinion on this.

The only thing I'd say is, mapping/landmarking PLots is a good place for noobs (like myself) to start because we're not going to negatively impact "real" traffic while we do our hands-on learning. (Some of us learn only so much by reading before we get to MEGO. Getting to work and seeing how things really work (or don't) teaches people like me so much more, and often more quickly. And, if one is destined to make mistakes, it's better to make those mistakes in a PLot than on any "real" street.) If I understand you correctly, if the client was less snappy, PLot work would be even less useful/helpful.
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Fri Jan 25, 2013 6:42 pm

Back on Jan 13th
kentsmith9 wrote:There are rare instances where we set a turn restriction on a legal turn and that is generally around freeway off ramps to on ramps. This stops the routing engine from thinking that is a bypass route when the freeway is jammed.


It looks like things are heating up again with this area.

https://www.waze.com/editor/?zoom=5&lat ... rks=603861

I had started to unlock some of the PLot segments - to get back to the stated goal of not locking PLots. But, as you can see, those segments have been now deleted (again)... including some that have clearly been used recently (according to GPS tracks), both within the PLot as well as a couple of exits (to the NE). (I also find it ironic that the one complaining about PLot roads "clutter(ing) up the map" does so with a completely useless landmark that clutters up the map with a large landmark! This is the same individual who created a landmark for a panhandler.)

Yesterday there were a couple of UR complaining that Waze was routing them through the PLots. (One heading N on Grant being "routed" through the gas station on the corner. The other heading S on Grant being "routed" into and then immediately out of the PLot in the Grant Plaza.)

I could be wrong, but I strongly suspect it's not that Waze is "routing" them through the lots, but rather, they're snapping to the lots and then being re-routed out when they start moving again.

There are three possible solutions that I can think of:

1) Split Grant Rd.
Arguments in favor:
a) it fits more of the criteria for splitting a road than not: gap at 100m, median requires U-turns
b) it would "spread" Grant Rd so that those on the road would be closer to the Waze "road" than the Waze PLot roads - reducing miss-tracks into the PLots - when they're in the middle or slow lanes.
c) it would improve the usefulness for pretty much ALL users - both those who are seeking to drive past the gas station and shopping center, as well as those who are heading for the gas station or shopping center - and would be better served by door to door directions.

Arguments against:
a) It's a bunch of work - that very well may not be appreciated.
b) It adds some complexity (which while there IRL, is currently not there in Waze' World).
c) It doesn't fit ALL of the criteria for splitting a road: it's not a highway or freeway, while there is the gap in GPS tracks at 100m the median is less than 5m wide, there are some cross-road breaks in the median barrier-wall, Google HAS mapped it as a split road - so we shouldn't ;) .

2) Set real and/or proposed/sensible turn restrictions to stop "the routing engine from thinking that is a bypass route when the (roads are) jammed".
Arguments in favor:
a) would fix the "routing" problem - if that really is the problem
b) would be a relatively simple fix to implement

Arguments against:
a) while possibly fitting the spirit of the "law", it certainly wouldn't fit the letter
b) wouldn't do anything about fixing erroneous snapping to PLot, which could in turn create even MORE problems in that the Wazers who are blindly following Waze and paying no attention to the road in front of them would have no idea how to get themselves out of those PLots. :lol:

3) delete all PLot roads, add PLot Landmarks, and say to hell with the whole thing
Arguments in favor:
a) less work than #1
b) may solve the erroneous traffic reports from people in the PLots
c) simplifies the map, reducing drag on Waze server(s)

Arguments against:
a) eliminates door-to-door directions - even as a possibility later, when addresses are working again.
b) more work than #2

According to you who are FAR more experienced than I, which of those (or possibly a 4th, even better) solutions would you recommend?

I think it may be important to keep in mind that at various times of the day almost every day, this intersection gets EXCEEDINGLY congested.
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

Re: Contribution frustrated in Mountain View, CA

Postby DaveHolzmann » Sat Feb 02, 2013 6:22 pm

Continuing to get URs for this area.

Many of them along the lines of today's "helpful" details: "Moronic editors" and "Street name wrong" (on a PLot road).

I'm convinced the problem is that, while having the PLots mapped does, in fact suppress erroneous traffic info, and does, in fact, help direct traffic to the businesses, the fact that Grant Rd. is mapped with a non-split road makes real traffic snap to the nearest PLot road all too often.

As drivers approach El Camino heading NE on Grant Rd., the road expands to 5 lanes. This means, the Grant Rd segment is 4 lanes away from the slow/right turn lane traffic, while the PLot road in the gas station (where drivers stop to fill up) is the equivalent of 2 lanes away.

https://www.waze.com/editor/?zoom=7&lat ... 6,70695383

Also here to a much lesser degree:
https://www.waze.com/editor/?zoom=7&lat ... 0,70695591

Of COURSE Waze will snap to the PLot road in that situation. It's significantly closer to the GPS tracks.



I'm equally convinced (now that I've thought about it, and observed Waze and Wazers behaviors) that the best solution is to split Grant Rd. through this entire section:

https://www.waze.com/editor/?zoom=4&lat ... 6,70695383

As I noted before, it will have these advantages:
DaveHolzmann wrote:1) Split Grant Rd.
Arguments in favor:
a) it fits more of the criteria for splitting a road than not: gap at 100m, median requires U-turns
b) it would "spread" Grant Rd so that those on the road would be closer to the Waze "road" than the Waze PLot roads - reducing miss-tracks into the PLots - when they're in the middle or slow lanes.
c) it would improve the usefulness for pretty much ALL users - both those who are seeking to drive past the gas station and shopping center, as well as those who are heading for the gas station or shopping center - and would be better served by door to door directions.

Arguments against:
a) It's a bunch of work - that very well may not be appreciated.
b) It adds some complexity (which while there IRL, is currently not there in Waze' World).
c) It doesn't fit ALL of the criteria for splitting a road: it's not a highway or freeway, while there is the gap in GPS tracks at 100m the median is less than 5m wide, there are some cross-road breaks in the median barrier-wall

DaveHolzmann wrote:I think it may be important to keep in mind that at various times of the day almost every day, this intersection gets EXCEEDINGLY congested.


One more argument in favor:
d) It will allow Waze to "allow" or even suggest U-Turns - which are frequently necessary.

Regarding the arguments against...
a) Editing is "work" - and I'm learning that no matter what we do, it very well may not be appreciated. Appreciation or lack thereof comes with the territory.
b) While it adds complexity to Waze, it will (I'm convinced) simplify the function of Waze for Wazers in this area. A certain amount of complexity is required in order to work properly.
c) The benefits outweigh the (minor) discrepancies between the technically "correct" criteria, and the practical need for splitting the road. I've seen quite a few other situations where roads are split when they're not highways, have far LESS split in the GPS tracks, just as narrow medians, and at least as many cross-road breaks.

The challenge for me is, I don't have a high-enough level for unlocking, editing, and re-locking that stretch of road.
Area Manager: Silicon Valley (South SF/SJ Bay Area)
Image
Using Waze on HTC One
DaveHolzmann
 
Posts: 105
Joined: Wed Dec 19, 2012 9:38 pm
Has thanked: 37 times
Been thanked: 3 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: Google [Bot], Google Feedfetcher, irowiki, NickS22, s18slider, wgodwin