Post Reply

[Page Update] Places

Post by CBenson
Before the wazeopeadia project resulted in the USA wazeopedia, there were many (IMO) good proposals that went nowhere as global consensus was sought. Can we now implement these suggestions in the USA wazeopeadia?

For example, there was this discussion about Area-Point Combinations and Naming. The only non-US voice in that thread questioned whether this should be global guidance and the proposal was left waiting for other countries to weigh in. Is there a reason not to now move that discussion to this forum and make the changes to the Places page in the USA wazeopedia?
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by CBenson
Its a bit hard to tell if what is solely USA related. I'd be happy to merge the prior topic here if appropriate.

The original discussion was raised to revise the guidance on "combined naming for area-point combinations to explain the idea more clearly, provide examples and to have it mirror actual practice more closely. Much of this was considered in conjunction with our efforts to standardize names of retail chains."

The Proposed Update was created at that time with respect to the existing global places pages.

Does anyone have any suggestions or objections with regard to revising this guidance as proposed for the US?
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by CBenson
I'm hearing no objections to updating the US wiki, to correspond to the Proposed Update.
CBenson
EmeritusChamps
EmeritusChamps
Posts: 10330
Has thanked: 646 times
Been thanked: 1844 times
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902

Post by abc1357
How do we want to handle hours of a location (e.g. fast food) that has different lobby hours from drive-thru hours. Do we put the longer one in (typically drive thru)? What do we do with the lobby hours - ignore them?
abc1357
State Manager
State Manager
Posts: 600
Answers: 1
Has thanked: 244 times
Been thanked: 202 times

Post by CitizenTraffic
#4 Can not be converted to a place point or place area

Should be: Cannot be converted to a place point or place area

On a different note, calling them Residential Place Points, seems to go against the grain of the described usage. First, you compare them to HNs. Next, you say they can be used for businesses. This only leads to confusion about usage vs description. Even the title is misleading.

Perhaps something definable is appropriate since it only provides address search capability, like Incognito Place Point (IPP), where the definition is: "with one's identity concealed", https://www.merriam-webster.com/dictionary/incognito.

It literally says what it does, can be used for residential or business, and eliminates any discussion about needing to use something else. It can also go hand-in-hand with PP, APs, and HNs.

That's my 2¢ worth.
CitizenTraffic
Posts: 78
Has thanked: 98 times
Been thanked: 22 times

Post by Inactive user -1643015044-
I agree and support the thought process that any category that does not have guidance should be point. As we know new categories from time to time get added and by having that guidance will help provide guidance for future state until further discussions occur.
Inactive user -1643015044-
PartnerCoordinator
PartnerCoordinator
Posts: 1023
Has thanked: 406 times
Been thanked: 459 times
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Post by Inactive user -1643015044-
Places - Description
With the YEXT imports the topic of place descriptions has been coming up more frequently and a topic of conversation today in the wazeopedia_usa channel. I was hoping to gauge the community on best practices of using the description field and maybe even some guidance for editors as the current info on the wiki lacking.
Place Wiki
Do not use the description field for notes to other editors. This field is visible in the Waze app and should only contain details pertinent to the place itself.


Question 1:
To start at the most simple question and for the purpose of this starting question, lets pretend that YEXT imports didnt exist. What should we as editors be putting in this field?
It is unique as almost everything else we enter is factual: phone number, website, services, external providers, categories, etc. And yet here we can enter almost anything we choose. We see guidance from time to time of factual info to include: pharmacy hours for a convenience store, line info for a train station, post office details, charging cable types for EV charging station, which all of these is again factual information.

However from time to time we see people add about us information from a company website, or worse copying from google place info. Obviously copying from yelp or google is against our sources policy, however a companies website appears to enter into a grey area. I personally feel about us, advertisement slogans, or other descriptions run into a grey area that we should avoid. We may not be following their corporate policies on utilization of their copyrighted/trademarked IP. And in the end it makes our places more advertisements than destinations.

What would be best guidance here?
-Only use factual information in this field that is not subject to dispute, opinion, or copyright/trademark?

Question 2:

This is where things get more complicated, as I dont think we as editors should be adding place descriptions, however the YEXT imports were ultimately a paid advertisement with included descriptions. It is further complicated by the fact that these descriptions can exceed the character limit we in WME are given for the description field. What is our best practice for handling these descriptions?

Overall I am inclined to leave them, a company paid for them and we should respect that. However when we get into situations where their places dont meet our PNH or other guidance standards it quickly becomes more complicated. Adding as an example, pharmacy hours is often impossible without deleting the description due to character limits.
Should we reduce the length of their description or remove all together and add our PNH/Guidance descriptor?
-I believe it is an all or nothing situation, where we can not start the habit of modifying their content. If we need to add something to the description per guidance/standards we should clear any other description out.

Question 3:
What to do with existing descriptions? The decisions to add a description is one thing, but what do we do with ones that we suspect may not be from an YEXT or other advertisement import? The ability to see the history of a place can quickly be confusing if it was merged, or without the proper script. How can we verify with and without script support? This one is probably the most challenging question as we discussed today answers to this from leadership could change on a week to week basis. However in keeping with the concept of retention we should always stride to preserve data unless we have clear evidence that it is not appropriate.

I think that state/regional leadership should still be consulted however I know that is something that could be subject to debate and I ask for your thoughts on this one and all the previous questions.

The YEXT imports provide a complicated example of a place which as has been many times discussed do not meet our standards, how much of it is ok and how much should be adjusted? How do we provide guidance to our editors that recognizes the exception that they might be?
Inactive user -1643015044-
PartnerCoordinator
PartnerCoordinator
Posts: 1023
Has thanked: 406 times
Been thanked: 459 times
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Post by Inactive user -1643015044-
jm6087 wrote:
DL's old proposal, plus additions recommended since, wrote: Users see the Description field only when viewing details for a Place. Its contents are not searchable.

Descriptions must be limited to brief, easily verifiable facts that:
  • help drivers locate, identify, or reach a destination;
  • help them park for a destination if potentially confusing;
  • confirm the destination being offered is what the user wanted;
  • highlight possibly unexpected restrictions, such as a park that doesn't allow dogs;
  • qualify the destination's details; or
  • differentiate the hours or other details of any sub-destinations, such as a pharmacy within a larger store.
Descriptions are not for reviews, opinions, or redundant, obvious, or offhand comments, nor are they for educational discussions of history or significance. To offer such information, set the Place's website field to the destination's official website.

If a description appears to have been added by a Waze-approved third party, you may leave it as is aside from any necessary corrections to facts or grammar. You may shorten or remove an existing description in order to include any of the essential information listed above, and you may edit descriptions that seem excessively opinionated in order to improve neutrality, but please respect the standing of advertisers who may have paid Waze to add the Place and its description. Consult local leadership if in doubt.
I think I like it
I second that
Inactive user -1643015044-
PartnerCoordinator
PartnerCoordinator
Posts: 1023
Has thanked: 406 times
Been thanked: 459 times
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Inactive user -1643015044-
PartnerCoordinator
PartnerCoordinator
Posts: 1023
Has thanked: 406 times
Been thanked: 459 times
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Post by abc1357
subs5 wrote: Another method is to have two entries Surface stations (Area), Underground Stations/Stops (Point)
There is no need for a note then and might be clearer to the first time reader.
I prefer this approach.
abc1357
State Manager
State Manager
Posts: 600
Answers: 1
Has thanked: 244 times
Been thanked: 202 times