US 2013 Waze Meetup Recap

Image This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderator: delilush

Re: US 2013 Waze Meetup Recap

Postby skbun » Tue Apr 02, 2013 3:21 am

AlanOfTheBerg wrote:
  • bgodette gave examples of the Waze car position jumping north and south off of east-west running roads onto parallel roads even though the system GPS location shows the position never wavering from the main road.


Do we have any word on the status of a fix for this one? I found eight URs near this Interstate junction (and left a few, anyway), where it's clear that a person is on one road, but Waze is routing them on the other, probably bouncing back and forth as we saw in the presentation about this.

https://www.waze.com/editor/?zoom=5&lon ... TTFTTTFTTT
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 425
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: US 2013 Waze Meetup Recap

Postby razor2k » Thu Apr 18, 2013 2:38 am

ohiostmusicman wrote:So, what about things like where a fast food place is (esp. with a drive-thru). I've seen a lot of errors because people go in, around, and out. Should I map every lot that involves a drive-thru?

Part of the reason I ask is because when it comes to routing to a specific point, Waze will route you to the road closest to the point. Sometimes, those parking lot roads for a specific fast food place are closer so it tries to route you using them even though you cannot reach the actual location through a fast food restaurant drive-thru...


Waze should not be routing through parking lot or private roads to get you to your destination. Maybe Bing location pins are erroneously in a parking lot rather than the correct location. Since waze thinks that's where you're going it leads you there.

No fault of waze, but on third party providers.

Sent from my SPH-D710 using Tapatalk 2
Area Manager: Pinellas, Pasco & Hillsborough Counties FL
Phone: Samsung GS 2, Sprint, Android 4.1.2
Waze: 3.7.2

Waze FAQ...Best Map Editing Practice...Correct Server?...User Manual
razor2k
 
Posts: 696
Joined: Thu May 10, 2012 8:40 pm
Location: Saint Petersburg, FL
Has thanked: 61 times
Been thanked: 54 times

Re: US 2013 Waze Meetup Recap

Postby razor2k » Sat Mar 09, 2013 3:34 am

jhfrontz wrote:
razor2k wrote:From what I understood, parking landmarks should only be added around Malls (with their associated perimeter roads). Anything smaller (Strip malls and the like) just map in the PL roads w/o landmark. Am I right? :?


My takeaway on both points (POI/landmark-a-palooza and paving every surface capable of facilitating any form of terrestrial transportation--motorized, pedaled, pedestrian, equine, bovine, cervine, asinine,...) is that we are at status quo unless/until Waze provides tools and features to support this (namely, make parking lot roads, etc. be less prominent in the client and in WME, as well as develop a POI database/management interface that makes the drawing of landmarks moot).


Gotcha! :lol:
Area Manager: Pinellas, Pasco & Hillsborough Counties FL
Phone: Samsung GS 2, Sprint, Android 4.1.2
Waze: 3.7.2

Waze FAQ...Best Map Editing Practice...Correct Server?...User Manual
razor2k
 
Posts: 696
Joined: Thu May 10, 2012 8:40 pm
Location: Saint Petersburg, FL
Has thanked: 61 times
Been thanked: 54 times

Re: US 2013 Waze Meetup Recap

Postby razor2k » Fri Mar 08, 2013 1:25 am

AlanOfTheBerg wrote:
HavanaDay wrote:So are we suppose to draw all parking lots as landmarks now? And what did you infer he meant by driveable surfaces? Does that include all parking lot roads or still just the major roads in and out as per usual.

There was discussion about POI vs. landmark where POI is a point, not a shaded area like we have now. I am not clear whether Waze is say we should be mapping all business, etc. as landmarks or whether a different feature for POI will be coming. Someone who was paying more attention than me will need to chime in.

Every drivable surface does mean parking lots, but there was a lot of discussion around that topic and how Waze wants parking lots done. On one hand they seemed to say map the lots as roads, then they said just entrance/exit stubs and landmarks otherwise. Pretty unclear IMO. The "all drivable surfaces" comment came out of the question, "Does Waze want us to map all the forest roads, the 4-ft wide off-road, no cell-service roads used by quads and hunters, etc?" And Ehud basically said, "yes." This is why we are rearranging the road types a bit.


From what I understood, parking landmarks should only be added around Malls (with their associated perimeter roads). Anything smaller (Strip malls and the like) just map in the PL roads w/o landmark. Am I right? :?
Area Manager: Pinellas, Pasco & Hillsborough Counties FL
Phone: Samsung GS 2, Sprint, Android 4.1.2
Waze: 3.7.2

Waze FAQ...Best Map Editing Practice...Correct Server?...User Manual
razor2k
 
Posts: 696
Joined: Thu May 10, 2012 8:40 pm
Location: Saint Petersburg, FL
Has thanked: 61 times
Been thanked: 54 times

Re: US 2013 Waze Meetup Recap

Postby PhantomSoul » Tue Apr 09, 2013 2:43 pm

I've been mapping small parking lots only when there's a problem pin, and adding only the segments needed to solve the problem pin. Otherwise, smaller parking lots can easily get cluttered with segments crisscrossing all over the place at distances most cell phone location/GPS systems cannot distinguish.

For larger parking lots that clearly show distinct thoroughfares at least 50 m (150 ft) apart, I've been mapping the entrances/exits from nearby roads, the roadway along the perimeter of the building, the drive-able perimeter of the parking lot, and any obvious thoroughfares that connect the two perimeters based on looking at the aerials.

The important thing is to not map every single lane with parking stalls. They are often too close together for Waze to be able to distinguish which row you're actually in, probably confusing Waze as to where you are actually driving.
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1711
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 318 times
Been thanked: 526 times

Re: US 2013 Waze Meetup Recap

Postby phantomblack » Wed Mar 06, 2013 11:21 pm

AlanOfTheBerg wrote:Every drivable surface does mean parking lots, but there was a lot of discussion around that topic and how Waze wants parking lots done. On one hand they seemed to say map the lots as roads, then they said just entrance/exit stubs and landmarks otherwise. Pretty unclear IMO.

I agree I think we could use some clarification on this. Until I understand better I guess it is business as usual leave parking to the newer editors or add the bare minimum to keep frequent requests at bay.
Wisconsin-based US Country Manager
phantomblack
 
Posts: 114
Joined: Thu Nov 17, 2011 9:17 pm
Location: Wisconsin
Has thanked: 5 times
Been thanked: 5 times

Re: US 2013 Waze Meetup Recap

Postby Olestas » Thu Mar 07, 2013 11:15 am

Rename US "Dirt/4x4" road type to "Unpaved" for clarity.
Create new US "4x4/Offroad" road type as Waze wants all paths of vehicle traffic, no matter how remote or how its used, to be mapped.


Will you do the same for INTL server?
Will you also change the way waze navigates through these types of roads?
Will you add option to avoid 4x4/Offroad type and/or Unpaved type separately?
Olestas
Coordinators
Coordinators
 
Posts: 6024
Joined: Wed Mar 09, 2011 7:08 pm
Location: Latvia
Has thanked: 3060 times
Been thanked: 2210 times

Re: US 2013 Waze Meetup Recap

Postby OhioStMusicMan » Sat Apr 20, 2013 4:54 pm

kentsmith9 wrote:
ohiostmusicman wrote:This is the issue I have. The most recent encounter I had was here. I was on my way to Clark for gas and someone had put in a parking lot road at the Wendy's just to the NW. Even though the address in Waze via gas lookup was correct, the location pin was closer to the Wendy's parking lot road than Apollo Dr and it wanted me to enter the Wendy's parking lot to finish my trip. I know the area enough to know that wouldn't work (insert hilarious joke about Wendy's food and gas here). I deleted the Wendy's road because of this.

I believe the problem you experienced was the current Lat/Long address information for the station from Bing was closer to Wendy's. Once Waze is using the internal address information that problem could be solved without deleting roads. :shock:


Except the gas station info was Waze's...now, of course we (or just I maybe) don't know exactly where it came from, but that is not something that can be fixed with Bing. I've done my share of fixing locations with Bing when the location is wrong. As far as I know, going to Bing to fix it wouldn't fix problems with Waze's gas lookup. The only reason I took out the road in Wendy's is that it was resulting in incorrect routing and would every time. Personally, I would have it route me (and others) to the correct location at the expense of having a road for a drive-thru. The only other fix would be to try and map the gas station in some way.

This brings me back to my original question - should we be trying now to put in something for every single small lot? If not, then there will be plenty of times where users get routed incorrectly. What good is a GPS service if it routes users incorrectly?

As an aside, I wonder, now that we can edit gas station info in the US, if the address info put in will be used to provide routing. If not, what's the point of putting it in there if it won't be used?
Travis
Waze 4.28.9.900
iPhone 7 (VZW) - iOS 10.3.3
iMac 21.5" & MacBook Pro 15" - macOS Sierra (10.12.6)
Area Manager: Bakersfield, CA
State Manager: Ohio

ImageImageImageImage
OhioStMusicMan
Waze Mentor
Waze Mentor
 
Posts: 154
Joined: Wed Apr 11, 2012 11:05 pm
Location: Toledo, OH
Has thanked: 60 times
Been thanked: 63 times

Re: US 2013 Waze Meetup Recap

Postby OhioStMusicMan » Fri Apr 19, 2013 2:44 pm

jhfrontz wrote:
razor2k wrote:
ohiostmusicman wrote:Part of the reason I ask is because when it comes to routing to a specific point, Waze will route you to the road closest to the point. Sometimes, those parking lot roads for a specific fast food place are closer so it tries to route you using them even though you cannot reach the actual location through a fast food restaurant drive-thru...


Waze should not be routing through parking lot or private roads to get you to your destination.


Right, it won't route through (meaning "into and back out from") the parking lot/private roads. However, if the parking lot or private road ends up being closer to the destination's pin than the actual entrance/access to the destination, the driver will be routed into the parking lot to get the driver closer to the apparent location of the adjacent business (or apartment).


This is the issue I have. The most recent encounter I had was here. I was on my way to Clark for gas and someone had put in a parking lot road at the Wendy's just to the NW. Even though the address in Waze via gas lookup was correct, the location pin was closer to the Wendy's parking lot road than Apollo Dr and it wanted me to enter the Wendy's parking lot to finish my trip. I know the area enough to know that wouldn't work (insert hilarious joke about Wendy's food and gas here). I deleted the Wendy's road because of this.

This goes back to my original question of should we be putting in these roads for, say, every fast food place, small parking lot, etc.? I know I've seen tons of error pins because cars go in and out and there's no road there. I've been inclined not put any road in specifically of issues such as this. However, if the goal is to map every drivable path, then this could cause an issue.
Travis
Waze 4.28.9.900
iPhone 7 (VZW) - iOS 10.3.3
iMac 21.5" & MacBook Pro 15" - macOS Sierra (10.12.6)
Area Manager: Bakersfield, CA
State Manager: Ohio

ImageImageImageImage
OhioStMusicMan
Waze Mentor
Waze Mentor
 
Posts: 154
Joined: Wed Apr 11, 2012 11:05 pm
Location: Toledo, OH
Has thanked: 60 times
Been thanked: 63 times

Re: US 2013 Waze Meetup Recap

Postby OhioStMusicMan » Thu Apr 18, 2013 2:14 am

So, what about things like where a fast food place is (esp. with a drive-thru). I've seen a lot of errors because people go in, around, and out. Should I map every lot that involves a drive-thru?

Part of the reason I ask is because when it comes to routing to a specific point, Waze will route you to the road closest to the point. Sometimes, those parking lot roads for a specific fast food place are closer so it tries to route you using them even though you cannot reach the actual location through a fast food restaurant drive-thru...
Travis
Waze 4.28.9.900
iPhone 7 (VZW) - iOS 10.3.3
iMac 21.5" & MacBook Pro 15" - macOS Sierra (10.12.6)
Area Manager: Bakersfield, CA
State Manager: Ohio

ImageImageImageImage
OhioStMusicMan
Waze Mentor
Waze Mentor
 
Posts: 154
Joined: Wed Apr 11, 2012 11:05 pm
Location: Toledo, OH
Has thanked: 60 times
Been thanked: 63 times

Next

Return to United States

Who is online

Users browsing this forum: No registered users