Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.
Post by Daknife
Then tell me how this station was an option for reporting gas prices. Then I adjusted the landmark to get it snapped off the roads. That made the landmark too small to appear in the client, and it disappeared from the report gas prices options for that intersection (the Chevron across the street was still listed). Then once I adjusted the landmark to get it big enough to appear in the client again, the report gas prices option was back?

I'm not claiming there is a connection, just stating exactly what I saw. The intersection is one block from my home, my attempts to report the gas prices for the station were made while fueling up at the station. The only thing that changed was the size of the landmark.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by Daknife
AndyPoms wrote:
skbun wrote:Sooo.... '[USA] Landmark Guidelines - Request for Comments' is now a locked thread with no further action mentioned, and I see no further discussion of this anywhere else in the US forums. Is the CT landmark standard now the national standard, or...?
The comments in the locked thread are still being reviewed... Final decisions will be made soon...

I apologize for the delay, but the real world (and my real job) has kinda stacked up on me...
And two months after the "Final decisions will be made soon..." comment we are still waiting for a standard, or rather we are waiting for something, anything to actually point people to. Well, other than the Utah State list I made months ago (based mostly on the CT list) when I got tired of waiting.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by Daknife
PhantomSoul wrote:I've got a number of editors landmarking rivers, lakes, and other bodies of water in my area. Should we be landmarking those or should they be asked to stop?

I thought that the Waze client uses a completely separate layer from the WME landmarks to show where there is water. Has this changed?
Last I heard the guidance was still no. With possible exception for significant bodies that do not appear in the water layer. I made one allowance in my area for a significant river (The Jordan river) running the length of the Salt lake valley to be added as it is not in the water layer.
Any other water body landmarks are deleted as soon as I see them.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by Daknife
Why did my local little church landmark disappear? Thus the need for the national standards to be finalized and published back into the wiki. Because too many landmarks clutter the map beyond usefulness. National standards that we can point the user to will help settle that question.
doctorkb wrote:One thing we're also leaving out... people can get navigation from multiple sources. They could have instructions from their friend on how to get to place X -- having the same data points (which may include "turn left at the church" or "go past the McDonald's") aids the user significantly, even if those instructions aren't read aloud or displayed in text form on the screen.
If they are asking a person for directions they won't be relying on a GPS. The GPS won't know about the red barn with the faded tobacco ad, or the Oak tree painted red white and blue, or the Smiths farm, or the church (not all churchs are easily recognized as churches and don't always show up on paper maps anyway.) Local landmark navigation? Talk to Cousin Larry. Address based GPS navigation? landmarks are not needed just turn when it tells you to turn. We rely on GPS to get away from having to ask for such directions. If you want to combine them, well when told to turn left at the little white church, and the GPS tells you to turn left and there is a little white church there, then you know it's okay to turn.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by Daknife
Wow, totally against the proposed National Standards, excessive and serves to inspire other editors to do the same to every other building they think of landmarking. I would rather suggest keep the large landmark for the entire airfield and putting a small inner landmark (that will never show on the client) for the terminals to aid in navigation to said terminals and maybe another for a General Aviation entry and one for a Cargo entry point but beyond that way too much work, way too many separate landmarks and too much data to be sent to the client (remember some people are limited in how much data they can use each month).

What purpose does it serve to map out the outline of every terminal taxi-way and runway? No waze should ever be trying to drive to those landmarks. A single large landmark for the entire airport with a couple inner guide marks to lead navigation to the passenger drop-offs, Long and short term parking and cargo/delivery points is all that is needed.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by dctdye
So just to be clear, I can go ahead and nix landmarks like these, right?

https://www.waze.com/editor/?zoom=2&lat ... rks=349361
dctdye
Posts: 166
Has thanked: 57 times
Been thanked: 13 times
Send a message
Area Manager- Tuscaloosa/Northport, AL

https://www.waze.com/wiki/images/5/5a/W ... M_only.png

Post by dctdye
I've been editing in Auburn, AL, today and there are a lot of questionable landmarks. I've already deleted some I knew where in error, but thoughts on the landmarks in and around the permalink?

https://www.waze.com/editor/?zoom=3&lat ... TTTTTTTTFT
dctdye
Posts: 166
Has thanked: 57 times
Been thanked: 13 times
Send a message
Area Manager- Tuscaloosa/Northport, AL

https://www.waze.com/wiki/images/5/5a/W ... M_only.png

Post by dctdye
Do we have a guideline on Cemeteries? I've been seeing a lot here lately.
dctdye
Posts: 166
Has thanked: 57 times
Been thanked: 13 times
Send a message
Area Manager- Tuscaloosa/Northport, AL

https://www.waze.com/wiki/images/5/5a/W ... M_only.png

Post by doctorkb
alarlo wrote:If I understand right, other than the those actual parking lots (The that's a public or paid) all other can be deleted?
Like the one next to malls, businesses or schools etc.

Is it OK delete them?

Thanks.
My rule of thumb: if it isn't named, it gets deleted (or named). I don't believe there is a need for any unnamed landmark other than parks and ponds.

Parking lots that get named: ones on a university campus, park & rides, etc.

Mall lots need to go: they are obvious. But the general consensus is that they should just be included in the mall landmark.
doctorkb
Posts: 4385
Answers: 4
Has thanked: 433 times
Been thanked: 1464 times
Send a message

Post by doctorkb
One thing we're also leaving out... people can get navigation from multiple sources. They could have instructions from their friend on how to get to place X -- having the same data points (which may include "turn left at the church" or "go past the McDonald's") aids the user significantly, even if those instructions aren't read aloud or displayed in text form on the screen.
doctorkb
Posts: 4385
Answers: 4
Has thanked: 433 times
Been thanked: 1464 times
Send a message