Problems with stacked road segments

Greetings. I was in a conversation with Chris (UH60SI), who is helping up at Schofield. He raises the issue of the GPS confusion near the airport viaduct between Nimitz below and H-1 above and thinks some tweaking might help.

I thought I’d raise it here, in case anyone has thoughts on this.

Not sure how it can be fixed, I hardly get GPS when driving on Nimitz

So I noticed a few things about that spot that may help. Driving on the nimitz west bound I can get GPS as long as im in the outside lane with view of the sky. I seem to have no problems with GPS on my android down there. Looking at the map the GPS Tracks show on the North side of the H1 supporting my outside lane theory. Also a look at the Eastbound side adjacent to the area show more seperation between the Nimitz path and the H1. So with all that said my opinion is to move try moving the Nimitz just a little North enough to remove the overlap in the two highways. Basic structure being the H1 inside bordered by the Nimitz on the outside with no overlap. What do yall think?

https://www.waze.com/editor/?env=usa&lon=-157.90586&lat=21.33569&layers=901&zoom=4&segments=62318488,65193275,65193276,65193593,65193594,65193783,65193788,65193789,70016958,70016959,78850513,78850514

I have a feeling that until our phone GPS’s can track within a few feet in X, Y, & Z axes, emphasis on the Z axis, there might not be a whole lot we can do. I believe that right now GPS accuracy is 15-30 feet (which, to me, is downright awesome). But I don’t think it’s anywhere near that in the Z axis. During navigation I’ve had instruction to take Nimitz Hwy exit and not taken it. Waze will continue to think I’m on Nimitz right below H1. As you know, we’ve had many UR’s for this problem. If we move the roads too far, it may impact side roads.
I’d like to get a lot more input before massive editing.

I’m inclined to agree that we need to be cautious about making changes here. Having poked around a bit on the map at the random spots where I’ve traveled lately, I know we’re not alone with this kind of viaduct GPS confusion.

It might be worth looking at what some of the editors elsewhere have to say about optimizing Waze in such areas – if it can be done. If anyone finds an interesting/relevant thread, post a link.

I’ve been getting down to 9 ft on my Galaxy S5. But GPS isn’t going to get much better than that for civilian use. Zooming in on that area looks like their is a little wiggle room for tweaking the road layout to get rid of the current overlap. But I’m new, so more input for sure. Next time I roll through there Ill run a GPS track and see what I get.

Chris, are you using juiced GPS hardware and app? or is that a standard S5 app?

Vicki, could you change the title to the thread to say something like “Problems with stacked road segments”? Maybe editors from other areas will be less inclined to skip thread.

Done. Hey, you missed your calling as a headline writer!

It my sweet “GPS Essentials” app. It pulls raw GPS data without regard to cell reception. I use it to track my flight path in new areas and during instrument procedure training.

Finally got around to posting something on this issue on the WME. The initial response, at least, suggests that moving the segments might be problematic. Take a look:

https://www.waze.com/forum/viewtopic.php?f=8&t=118407

Awesome!

It doesn’t help that waze tries to route to nimitz in the afternoon even though it may be faster on the H1. The only way to get on the H1 at this point is to drive all the way to the HOV lane, stop navigation and then search again.

So I forgot to upload those tracks I did on Nimitz. Here are the KML files.
https://drive.google.com/folder/d/0B9MfAqMgiH1wRTBtdmRyXzM2Snc/edit

Sent from my Samsung Galaxy S5 using Tapatalk