Landmark - Best Practices US

[ img ] 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: MapSir

Re: Re: Landmark - Best Practices US

Postby mapcat » Sun Sep 23, 2012 3:04 am

shawndoc wrote:
jasonh300 wrote:A gas station landmark will suppress reports there, and would be more correct than a parking lot. However, it was mentioned a week or two ago not to add any gas stations until we got to some point with the gas prices functionality. I'm not sure if that's correct or still the case.


Was that from Waze? I would think it would be okay to add them if you are doing it to suppress traffic and error reports.

We don't know how the gas stations in the hidden layer and the ones in the landmarks layer affect each other (if at all). It may be that the ones in the hidden layer actually suppress reports, and if so, it would be a waste of time to add them to the landmarks layer. We don't know if they intend to merge the two layers at some time. If they do, we'll have duplicates to delete. Since we don't have answers, because no one answers our questions, I err on the side of doing less work.
mapcat
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 196 times

Re: Re: Landmark - Best Practices US

Postby HandofMadness » Sat Sep 22, 2012 11:18 pm

jasonh300 wrote:A gas station landmark will suppress reports there, and would be more correct than a parking lot. However, it was mentioned a week or two ago not to add any gas stations until we got to some point with the gas prices functionality. I'm not sure if that's correct or still the case.


Was that from Waze? I would think it would be okay to add them if you are doing it to suppress traffic and error reports.
HandofMadness
Area Manager
Area Manager
 
Posts: 1802
Joined: Mon Apr 16, 2012 7:44 am
Location: Californialand, USA
Has thanked: 18 times
Been thanked: 375 times

Re: Landmark - Best Practices US

Postby sketch » Tue Oct 29, 2013 3:47 pm

PhantomSoul wrote:Two things:

1. I thought the CONST ZN suffix was only for segments totally disconnected from the road network during construction but expected to be reconnected at some point in the future. We do this instead of deleting them to avoid losing the road metric data they've collected, and the CONST ZN serves as note to anyone reviewing the map for disconnected segments as to why it's there and disconnected. So I'm not sure what the fuss about TTS trying to read CONST ZN is about.

As far as I'm aware, this is not the case; at least, this is not how it's been used around here.

Either way, I'm pretty sure it predates TTS.

IMO it would be better to replace it with "(Under Construction)" if anything. Waze inserts a pause at the open parenthesis and would pronounce it properly; also, it looks better.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5912
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1418 times
Been thanked: 1936 times

Re: Landmark - Best Practices US

Postby orbitc » Fri Oct 25, 2013 6:06 pm

PhantomSoul wrote:Two things:

1. I thought the CONST ZN suffix was only for segments totally disconnected from the road network during construction but expected to be reconnected at some point in the future. We do this instead of deleting them to avoid losing the road metric data they've collected, and the CONST ZN serves as note to anyone reviewing the map for disconnected segments as to why it's there and disconnected. So I'm not sure what the fuss about TTS trying to read CONST ZN is about.

2. As I understand it, there is no reliable predictability, at least within the context of WME, for which landmarks will appear, when, and for how long, or whether a particular landmark's name is displayed in any of the Waze clients. Rather they are rendered (or hidden) as a function of zoom level and other higher priority things drawn on the map around it, like other roads, their names, city names, the navigation line and its bubble names, etc. As such, denoting construction zones with landmarks does not really add any kind of reliable value to the Waze clients, but it does add extra noise to the landmarks database.

I would think that we should have a way to identify long-term construction zones in a broader sense than just temporarily re-configuring sections of roads. If fed to the Waze clients correctly, it could provider the driver with valuable information about constructions zones up ahead and maybe even a warning to keep an eye out since the map may be slightly outdated there. However, because of the way landmarks are rendered, I do not think that landmarks will adequately meet this objective.


+1

Unless, there is dedicated color in that LM indicating the Construction Zone like Orange perhaps, it wouldn't work due to the inconsistencies PhontomSoul mentioned above. (to give credit to the rightful party...color was suggested by mapcat from an earlier post, if I'm not mistaken)
orbitc
Master Raider
Master Raider
 
Posts: 5862
Joined: Mon Jun 25, 2012 1:51 pm
Location: USA
Has thanked: 2227 times
Been thanked: 4873 times

Re: Landmark - Best Practices US

Postby PhantomSoul » Fri Oct 25, 2013 5:51 pm

Two things:

1. I thought the CONST ZN suffix was only for segments totally disconnected from the road network during construction but expected to be reconnected at some point in the future. We do this instead of deleting them to avoid losing the road metric data they've collected, and the CONST ZN serves as note to anyone reviewing the map for disconnected segments as to why it's there and disconnected. So I'm not sure what the fuss about TTS trying to read CONST ZN is about.

2. As I understand it, there is no reliable predictability, at least within the context of WME, for which landmarks will appear, when, and for how long, or whether a particular landmark's name is displayed in any of the Waze clients. Rather they are rendered (or hidden) as a function of zoom level and other higher priority things drawn on the map around it, like other roads, their names, city names, the navigation line and its bubble names, etc. As such, denoting construction zones with landmarks does not really add any kind of reliable value to the Waze clients, but it does add extra noise to the landmarks database.

I would think that we should have a way to identify long-term construction zones in a broader sense than just temporarily re-configuring sections of roads. If fed to the Waze clients correctly, it could provider the driver with valuable information about constructions zones up ahead and maybe even a warning to keep an eye out since the map may be slightly outdated there. However, because of the way landmarks are rendered, I do not think that landmarks will adequately meet this objective.
PhantomSoul
US Waze Champs
US Waze Champs
 
Posts: 1660
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 300 times
Been thanked: 498 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.
bretmcvey
US Waze Champs
US Waze Champs
 
Posts: 347
Joined: Thu Mar 22, 2012 2:08 am
Location: Omaha, NE
Has thanked: 241 times
Been thanked: 122 times

Re: Landmark - Best Practices US

Postby WeeeZer14 » Mon Oct 21, 2013 2:12 pm

I'm late to the party but my 2 cents:
I'd love for some way to flag long term construction zones. The idea running around in my head that I like the most would be road segment based and then it just pops little traffic cones/pylons/barrels on the map display along the length. No warning or alert generated (although maybe that can be an option).
WeeeZer14
 
Posts: 3761
Joined: Sun Apr 11, 2010 3:27 pm
Location: Knoxville, TN, USA
Has thanked: 46 times
Been thanked: 315 times

Re: Landmark - Best Practices US

Postby mapcat » Mon Oct 14, 2013 9:33 pm

MGODLEW wrote:I tried experimenting with this & kinda like the results.

I saw some of your handiwork on a few recent trips thru PA and agree that it's helpful. Unfortunately for long stretches sometimes only a blank rectangle shows on the screen, and so there's no way of knowing exactly what's going on.

If we could have a special landmark for this, perhaps one that shows as orange in the client and always displayed the text whenever part of the landmark was on the screen, I'd support that.
mapcat
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 196 times

Re: Landmark - Best Practices US

Postby MGODLEW » Sun Oct 06, 2013 7:39 pm

I think I heard things about being able to flag a road as a construction zone in waze in the near future but in the mean time I would like to propose use of the landmark type of "Other" over top the entire length of the road of Long Term construction zones while also flagging the road name CONST ZN. In the name of the landmark, keep it short & sweet. For example: (I-80 E & W Single Lane Restrictions) or (Road Closed: Bridge Replacement), then in the comments field put the estimated complete date & and any links to reference. I tried experimenting with this & kinda like the results. Wondering what the communities thoughts are? I think it would benefit editors by letting them know why the a road maybe detached/closed or why normally a 1 way road is now a 2 way road. Plus, in the client it shows the actually start & end of the construction zone while simply adding CONST ZN doesn't appear until you are actually driving well into the construction zone. Road Closure To McKees Rocks example.

[ img ]
MGODLEW
US Waze Champs
US Waze Champs
 
Posts: 2004
Joined: Tue Dec 20, 2011 6:39 pm
Location: Pennsylvania
Has thanked: 778 times
Been thanked: 691 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).
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3416
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 108 times
Been thanked: 507 times

Next

Return to United States

Who is online

Users browsing this forum: No registered users