Private Installations Revisited

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: Unholy, bextein

Private Installations Revisited

Postby CBenson » Tue Jun 24, 2014 10:56 am

The prefferred treatement for larger private installations set forth in the wiki here is as follows:
Each entrance to the installation should be connected by a one-way split road entering and exiting the installation. The entering one-way road will include one private road segment. The exiting one-way road will be of one segment using the appropriate type of that road (usually street, primary street, or minor highway). This structure often mimics the actual lanes for such installations.


There is currently a report that a user has difficulty routing onto the NSA campus on Ft Meade. The NSA Campus is essentially a nested security zone within Ft Meade, so you need to cross two private road segments to reach the campus. Currently, the routing server more often than not times out when routing onto the NSA campus.

I asked Noam to look into this. The reply is that the timeouts are caused by the private roads. They are working on a permanent solution. In the meantime the routing team suggests making only the exit segments from private installations private and not the entry ones.

I have made this change to Ft Meade and we will see if it makes a difference.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
EmeritusChamps
EmeritusChamps
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

Re: Private Installations Revisited

Postby DwarfLord » Tue Jun 24, 2014 2:33 pm

Can you clarify that the issue is with needing to cross two non-contiguous private segments? I think that's what you mean, just want to be sure.
DwarfLord
Wiki Master
Wiki Master
 
Posts: 2459
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 1070 times
Been thanked: 1440 times

Re: Private Installations Revisited

Postby CBenson » Tue Jun 24, 2014 2:55 pm

Yes, I mean two non-contiguous private road segments.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
EmeritusChamps
EmeritusChamps
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

Re: Private Installations Revisited

Postby txemt » Wed Jun 25, 2014 5:55 pm

CBenson wrote:I asked Noam to look into this. The reply is that the timeouts are caused by the private roads. They are working on a permanent solution. In the meantime the routing team suggests making only the exit segments from private installations private and not the entry ones.

I have made this change to Ft Meade and we will see if it makes a difference.


I don't think that's going to be the reason. We tested what ya'll had set up and it worked, so there's something else going on. I'm also not a big fan of having a private road out, and a street in. I can see where Waze is coming from, but now we're restricting people from leaving the base....
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4774
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

Re: Private Installations Revisited

Postby CBenson » Wed Jun 25, 2014 6:46 pm

It does appear that there are other issues at that destination.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
EmeritusChamps
EmeritusChamps
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

Re: Private Installations Revisited

Postby txemt » Wed Jun 25, 2014 7:23 pm

For clarification purposes, please do not set up private road out at military bases throughout the country.
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4774
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

Re: Private Installations Revisited

Postby vectorspace » Wed Jun 25, 2014 11:11 pm

Txemt is correct... we tested this on real physical roads with the Private Installation WIKI guidance with a nesting level of three. I did this on Kirtland. The Base entries were with two one-way roads, the inbound being private and the outbound being regular. The two internal nested levels were with a single private segment. It worked just fine. I am quite familiar wtih Ft Meade and it should not be different.

Last time I worked with Ft Meade roads, I was told to stay away from it by another editor, by, I forget who...

I don't know why Noam would indicate there is a routing problem as this makes no sense to me. I agree with CBenson that there may be other issues at the destination. I will go look when I get a chance. As I recall someone was marking vast areas of Ft Meade as private roads. We have learned from txemt and Driving79 that this causes problems in residential areas, so it would on bases. I am considering changing the Private Installations guidance because of their work.
vectorspace
vectorspace
 
Posts: 1185
Joined: Sat Dec 17, 2011 7:05 pm
Location: Albuquerque, NM, USA
Has thanked: 173 times
Been thanked: 422 times

Re: Private Installations Revisited

Postby CBenson » Thu Jun 26, 2014 12:10 am

vectorspace wrote:As I recall someone was marking vast areas of Ft Meade as private roads.

Well that was the guidance for private areas when the current properties of private roads were introduced.
vectorspace wrote: We have learned from txemt and Driving79 that this causes problems in residential areas, so it would on bases. I am considering changing the Private Installations guidance because of their work.

Seems to me that the private road type is intended for exactly this purpose. If it causes problems, seems to me we really need to raise that with the routing staff at waze.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
EmeritusChamps
EmeritusChamps
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

Re: Private Installations Revisited

Postby txemt » Thu Jun 26, 2014 12:12 am

CBenson wrote:Seems to me that the private road type is intended for exactly this purpose. If it causes problems, seems to me we really need to raise that with the routing staff at waze.


It wasn't the private road, though in this instance. It was a node on the segment we discussed earlier today.
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4774
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

Re: Private Installations Revisited

Postby CBenson » Thu Jun 26, 2014 12:16 am

The this I referring to is marking vast areas of Ft Meade as private roads.

Seems to me that the private road type is intended for exactly the purpose of marking private areas. If marking private areas with private roads causes problems, it still seems to me that we really need to identify such problems to the waze routing staff.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
EmeritusChamps
EmeritusChamps
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

Next

Return to Waze Map Editor

Who is online

Users browsing this forum: No registered users