Level 3: Martinsville, NJ

Level 1 added Chimney Rock Fields PLR, need unlock for editing or connections to Chimney Rock Road please.

https://www.waze.com/editor/?env=usa&lon=-74.56051&lat=40.59467&layers=933&zoom=7&segments=32000527,80880645,80880583,80880582,80880584

Always was a PITA to find the field…glad to add it now :slight_smile:

Thanks
MW

Unlocked, please let me know when done.

Note that I don’t think you need to set up the PLR like that. Simplify. Just a line is enough. It really won’t be confusing to drivers or to Waze.

  1. It is a one way lot - This simple, or simpler? i.e. a single line two way road entering from a single point - that “solution” just seems wrong to me.
    https://www.waze.com/editor/?env=usa&lon=-74.56125&lat=40.59484&layers=935&zoom=8&segments=80957408,80880645,80957479,80957407

  2. I noticed that that Chimney Rock Road (CR-525) is marked as Bridgewater, but is entirely within Martinsville boundaries, should the length of road be edited to reflect correct town?
    link included to show range.
    https://www.waze.com/editor/?env=usa&lon=-74.55652&lat=40.59090&layers=935&zoom=3&segments=79312138,78105112,79214547,80957479,80957407,80957408,32009505,32009506,32001999,32004383,32002001

Boundary reference:
http://www.citypopulation.de/php/usa-census-newjersey.php?adm2id=34035

HOWEVER - Martinsville is unincorporated and falls within the boundaries of Bridgewater, with its own zip code (08836) vs. Bridgewater (08807).

Thoughts?
Thanks

Regarding the PLR, what’s the distance between the inbound and outbound lanes? You can use the map scale in the lower right-hand corner of WME to estimate it. Fact of the matter is if the distance is less than 50m (~150 ft), it is trivial to Waze and we can simplify the map by using a single 2-way segment.

For the city names, Bridgewater = primary city name, Martinsville = alt city name for segments where applicable. The primary city name must always, always be/reflect an incorporated municipality name, even though vast amounts of the state are currently incorrect because the base map imports were way different than the standards developed for city naming since.

Please let me know if you still need anything unlocked, as I am on Tapatalk/iPad and can’t really poke around much. :slight_smile:

Got it, logic works will correct, I believe distance isn’t more than 30 meters, I will tweak the PLR to 2 way single entrance

Makes sense.

Corrected it, 2 way PLR in place of the one way loop, chimney rock road is all Bridgewater with martinsville for alternates.

https://www.waze.com/editor/?env=usa&lon=-74.56164&lat=40.59475&layers=935&zoom=9&segments=80957407,80880645,80957408

It should be ready to relock.

It looks like you have a soft-turn enabled at node B. You can correct this by using the Q keyboard shortcut while highlighting node B only.

https://www.waze.com/editor/?env=usa&lon=-74.55982&lat=40.59456&layers=935&zoom=9&segments=80880645

It wasn’t visible to me.
Followed your instructions and resolved that (I believe).
Not sure I understand yet what a soft turn is or how it would apply to a non connected node of PLR.

While researching soft turn found the wme validator.
So at least I now have some tools to edit with.

So I believe its corrected and ready for lock

Thanks - here’s a Wiki page explaining Soft Turns - https://wiki.waze.com/wiki/Soft_and_hard_turns. It’s best practice to get in the habit or making all turns hard to avoid unnecessary routing penalties.

PS,

I don’t believe you are correct about primary names. Although it is generally true that we use incorporated names, we sometimes don’t, and take local usage into account.

Re: soft turns: if you’re already working with an existing junction or absolutely know the turns allowed vs not at a junction (besides looking at SV - it is notorious for being outdated when traffic patterns have recently changed - especially on local streets and PLR accesses), they should absolutely be confirmed by making those turns hard. However, if there’s any kind of uncertainty, it’s better to leave them as soft.

Re: Primary City Names: Has this changed or did you just start doing this because a few people felt that some unincorporated city names are more significant? Last I seen and spoke with Orbit, incorporated municipal names were to unconditionally be used in the Primary City Name field, except maybe in NYC because of the way the boroughs work and are separate counties (but we didn’t talk about that much). Unincorporated names are to be used as alternates so they will match addresses. I get that the alternate names don’t show anywhere currently, including the results of searches, but that’s a problem for Waze to address and not us in WME.

I worked with him on figuring out a local area a while back. We looked over some businesses, found that they were actually using the CDP as their local address, and therefore decided that local usage supported what happened to be a CDP instead of the municipality. I’m sorry I can’t remember the location right now. It might have been an historic district of some sort.

Phantom - I understand the premise of this, but am having trouble with the logic. We are a community first app, regarding naming Streets as defined by locals, so that should IMHO carry over to city naming. People who live in Whiting, say/search for Whiting not Manchester Twp. The same with Forked River vs Lacey(Twp), Bayville vs Berkeley, to pick 3 out of the hat. Additionally, I am trying to understand why NJ is (seemingly) the only state in Waze that officially DOES NOT include these places as primary st names - PA, MD, MI, NE, CA all use CDPs as far as Ive seen on the map and per their respective state forums/wikis. The only difference in NJ, is that it has all 4 possible incorporated places - city, borough, town, village - although that doesn’t seem to be relevant to this conversation. If CDPs are a no-go and should be entered into the “alt field”, that should be nationwide and vice-versa. If we are going by the Post Office/zip codes then the same should apply, but why do we want that for routing purposes?? Im not delivering a package, I am going to watch a football game by a friends house. Anybody living in the thousands of places like those mentioned above, would prefer to search and find the “place” where they live as opposed to the Township that delivers their mail. Especially once we get the “alt names” displayed. The only understanding I can wrap my head around is in places like CA, Los Angeles in particular, where you can have multiple CDPs in close proximity - Beverly Hills, Beverlywood and various “Beach Towns” (to name a few) where there is a greater chance of city smudging/confused Wazers. However, that doesn’t seem to be the case for most of NJ. Finally, when it comes to businesses/govt addresses, listed in these towns it would be a no-brainer to have the Primary be that city - incorporated or otherwise.

Since I have yet to come across any major or specific routing issues now that all (?) the duplicate city names have been corrected (thanks to hours of work by numerous editors), I don’t think this is such a pressing matter. A standard/understanding would be nice however.

Frankly, it’s plain and simple. They guidelines very specifically say do not use unincorporated names in the Primary City field. Whether unincorporated towns/neighborhoods or other names in the Alternate City fields display on the map or search results is not in our control as map editors.

As far as I know, nobody in any state is supposed to be entering CDPs in Primary City fields (unless of course something has changed and I missed it - in that case, I need to see a reference to a wiki article describing that). The only exception I can think of is maybe in states that have vast rural areas completely unincorporated, you may have to enter an unincorporated village’s name into the Primary City field in order to prevent errors, since you cannot have No City for a Primary City with an Alternate City. However, this does not apply to any state that is comprehensively divided into townships, like every state in the Northeast, among others.

Many unincorporated (or in some cases just plain incorrect) names exist currently on the map en masse because that was the data originally imported from the basemap. These names, as per the guidelines developed since, are technically wrong, and should be considered as smudges. We just haven’t been so quick to fix them because it doesn’t have as much of an impact on navigation as other things and there have been much bigger fish to fry so far.

I realized there is a parallel conversation in the state forum. I posted my response there as this isn’t an unlock request and seemed more appropro. :wink: