Landmark - Best Practices US

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: Landmark - Best Practices US

Postby CBenson » Fri Feb 08, 2013 7:27 am

daknife wrote:And with one near my house I found that until the landmark was big enough to appear, the option to report gas prices for it was also not available.

This really surprises me. Many of the gas stations that waze routes me to and for which I then enter prices have no landmark at all in the landmark layer. What is the current relationship between the price database and landmark layer in the US?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2352 times

Re: Landmark - Best Practices US

Postby CBenson » Thu Aug 02, 2012 5:44 pm

mapcat wrote:In the US there is already a TOTALLY SEPARATE gas station landmark layer that has NOTHING TO DO with the gas stations that may exist as visible landmarks in WME. Please don't add (or delete) any gas stations in WME in the US.

We can't edit the real gas station layer. (Yet.)

Opps, sorry didn't get the warning that I was overposting. I do appreciate the clear answer to whether we should be adding gas station landmarks.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2352 times

Re: Landmark - Best Practices US

Postby CBenson » Thu Aug 02, 2012 5:41 pm

AndyPoms wrote:What I quoted above was from the US guidelines in the post I linked to... It seems that the landmark will allow Waze to search for the Name of the station & navigate to it, but not enable gas prices. The gas prices come from a different database...

I think that the quote is unclear at best. I guess the biggest problem is that I don't really understand how waze searches and navigates to landmarks.

For example, if I search for "The White House" under the waze tab I currently get two entries for "White House, Washington, DC" and one entry for "White House, NJ" (and a bunch of garbage related to Rutter's). Are any of these really related to the "The White House" landmark. Seems unlikely to me as the landmark has the "The" in the name.

If I search for "Sherwood Forest Golf Course" (the name of the landmark I linked to above as a erroneous default gas station), I get back a ton of results with "Golf Course" or "Sherwood Forest" in the name ranging from local to Wisconsin and Alabama, but none seem to be the actual landmark.


AndyPoms wrote:I've been adding gas station landmarks in the US because of the gas price function that is on the way & the simple fact they suppress traffic jams & problem reports of people looping through the station...

Seems dangerous to me. I don't trust waze to merge the gas stations that exist in the landmark layer with the imported list of stations with price data in a coherent efficient manner.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2352 times

Re: Landmark - Best Practices US

Postby CBenson » Thu Aug 02, 2012 4:09 pm

AndyPoms wrote:See: http://www.waze.com/forum/viewtopic.php?f=3&t=23354
Adding a new landmark of Gas station type will NOT add the station to the list. It will add it to the map, and if you enter a name, you will be able to search and navigate to it - just like any other landmark - but won't be able to update prices.

So there is no current reason to add a gas station landmark (in the US), right?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2352 times

Re: Landmark - Best Practices US

Postby CBenson » Thu Aug 02, 2012 3:54 pm

I agree that having some more guidance to get us on a consistent path would be nice, but waze needs to decide how gas stations will be handled here first.

There are many parking lots (at least on the MD side of DC) that were added by the IGN team. It seems that suppressing map problems and traffic reports from cars in parking lots was being addressed by the IGN team by putting in parking landmarks. These landmarks in my experience typcially included the buildings as well. An example is the Annapolis Mall.

The other issue is that quite a few landmarks seem to have come in with the base map. Some of these (particularly golf courses) over the course of fiddling with the landmark classifications have been given a default class. With the introduction of the gas price feature, gas stations have been made the default landmark and these landmarks now show as gas stations. This is likely the created by admin(6) gas stations that you are seeing. Example here.

I guess all I'm saying is that many of the problems here are largely traceable directly back to waze and not to the editors.

My understanding is that when routing to a gas station from the gas station category list in the US the current landmark layer is not used. In other words the imported gas station data is currently separate from the landmark layer. It also my understanding that the gas station data will be made available in WME for ongoing maintenance by the editors, but that this has not happened yet. Until we see how this is done, it seems to me that it is premature to develop best practices guidelines.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2352 times

Re: Landmark - Best Practices US

Postby bretmcvey » Mon Oct 21, 2013 2:40 pm

Reporting a Construction Zone
I'd enjoy the longterm construction zones given more consideration like the road closure feature was. Landmark names are often hidden as mentioned while in navigation mode and appending "CONST ZN" gives you a road pronounced as "CONST Z N" by TTS and not special visual treatment like how shields are added to interstates and highways.

Concept
Marking a Construction Zone vs. a Construction Event could utilize the mechanics of the "Pave" feature in Waze. Marking the zone would mean painting the road for a duration to set the area encompassed by the construction zone.

Much like the road closure feature, you could be presented with timing options in order to set a rough time for the construction zone.

In regards to the visual treatment, overlay a pattern or color or animation or even a visual icon indicating a construction zone.
Regional Coordinator - Plains Region
US Waze Champ | Country Manager: USA | State Manager: Nebraska
Image
bretmcvey
US Waze Champs
US Waze Champs
 
Posts: 400
Joined: Thu Mar 22, 2012 2:08 am
Location: Omaha, NE
Has thanked: 396 times
Been thanked: 174 times

Re: Landmark - Best Practices US

Postby bretmcvey » Thu Sep 12, 2013 12:06 am

sketch wrote:In a word, no. It'll route you to the segment nearest the destination point regardless of type. It's all the segments between you and that last one that make a difference.


Thank you, that makes sense. I've already been making a bigger push in regards to user errors related to the destination marker to correct marker placement in Google Maps, but while better than most other alternatives it is still a slower than desired process and hit-and-miss depending on what a reviewer agrees with when resetting the marker.
Regional Coordinator - Plains Region
US Waze Champ | Country Manager: USA | State Manager: Nebraska
Image
bretmcvey
US Waze Champs
US Waze Champs
 
Posts: 400
Joined: Thu Mar 22, 2012 2:08 am
Location: Omaha, NE
Has thanked: 396 times
Been thanked: 174 times

Re: Landmark - Best Practices US

Postby bretmcvey » Wed Sep 11, 2013 9:27 pm

bgodette wrote:
mapcat wrote:
bgodette wrote:Assume you had a PLot segment in front of the store, but not behind, and the pin still being closer to the residential street.

Then the customers of the business would be directed to the loading dock. Whether that's better than the residential street is debatable.

Once internal addressing is activated, and business addresses are properly edited, the need for the back driveway will go away, so why include it in the best practices now?
You don't wish the UPS/Truck driver running Waze to pollute historical data?


Wouldn't placing a segment behind as a private road type have a lower priority than the parking lot road type? Would that still keep routing more likely to the front via the parking lot segments?
Regional Coordinator - Plains Region
US Waze Champ | Country Manager: USA | State Manager: Nebraska
Image
bretmcvey
US Waze Champs
US Waze Champs
 
Posts: 400
Joined: Thu Mar 22, 2012 2:08 am
Location: Omaha, NE
Has thanked: 396 times
Been thanked: 174 times

Re: Landmark - Best Practices US

Postby bgodette » Thu Sep 12, 2013 2:45 am

mapcat wrote:
bgodette wrote:You don't wish the UPS/Truck driver running Waze to pollute historical data?

What makes you think he would be snapped to another road?
All depends on how close it is. I can guarantee such a situation exists, the unknown is how common it is (going to say not very).
ImageImage
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 117 times
Been thanked: 538 times

Re: Landmark - Best Practices US

Postby bgodette » Wed Sep 11, 2013 9:09 pm

mapcat wrote:
bgodette wrote:Assume you had a PLot segment in front of the store, but not behind, and the pin still being closer to the residential street.

Then the customers of the business would be directed to the loading dock. Whether that's better than the residential street is debatable.

Once internal addressing is activated, and business addresses are properly edited, the need for the back driveway will go away, so why include it in the best practices now?
You don't wish the UPS/Truck driver running Waze to pollute historical data?
ImageImage
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3437
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 117 times
Been thanked: 538 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users