I think it's more of a naming issue for the Breezewood example. The section between the ramps coming off the PA Pike and I-70 freeway sections should NOT be named I-70, as it isn't I-70 but rather US-30. It should have an Alt name of I-70.

https://www.waze.com/editor/?env=usa&lo ... 0,41676574

DrNeubie wrote:Interestingly, the I-19 terminus in Nogales AZ has cross traffic and surface streets, but still shows its FC as FW:

https://www.waze.com/editor/?env=usa&lo ... 461&zoom=5

In my opinion, the freeway class is wrong on these sections.

https://www.waze.com/editor/?env=usa&lo ... 9,87131224

The freeway should not start until after the last intersection.

clubjuggle wrote:
This section of road is not a gap in Interstate 70, just a gap in the expressway. Interstate 70 is federally approved to run along US-30 here and is signed as such.

You will see the overhead lane guidance signs, but you won't find the mile markers or Interstate badges.

It is not a gap in the expressway, it is a connecting highway that the interstate system uses to get from one interstate to another. (I-76 to I-70) You will not find that portion FC'd as interstate or Freeway because of the grade crossings. It is FC'd as Other Principal Arterial and as such is typed as MH.

If my understanding is correct (and I'm sure someone will correct me if I'm wrong), Waze uses the highway type more for routing purposes instead of the visual element. That's why we type service roads (roads that parallel the interstate, connecting 2 exits) as PS, even though the state might have them FC's as street. Before I became SM for Missouri, very few of the service roads along I-70 were typed correctly. Waze would never route you off the Interstate, unless there was a complete blockage. Now that the service roads are typed PS, if there is a big enough slow down to overcome the penalty for going freeway to PS and back, it will regularly route me off to the service roads.

Sign assembly at the traffic light where I-70 WB reaches the traffic light. Note that there is no "TO" placard for I-70 as there is for the PA turnpike:

Screen Shot 2016-06-09 at 11.24.48 AM.png

Overhead reassurance marker where the concurrency begins:

Screen Shot 2016-06-09 at 11.28.54 AM.png

Sign for turnpike entrance using W I-70 but "to" I-76:

Screen Shot 2016-06-09 at 11.32.29 AM.png

.

Those are lane guidance signs. The reason you see the "to" in front of the I-76 is because I-76 doesn't follow that portion of the road.

The USDOT FHA has specific guidelines that need to be met before a highway can be designated an interstate. That section does not meet those guidelines and should not be referred to as I-70. It is US-30, connecting I-70 to I-76. But then again, it's not my state and I'm just a lowly level 4 editor, so my opinion is just that, opinion.

There will always be the exceptions to the rule. The KS turnpike has a few cattle stations along it's route that would qualify as grade connectors, but it is still typed as freeway. The fact that the little section in Breezewood is typed as MH will have no impact on the routing along I-70, the reason the different highway types are used, routing.

I want to point out to my knowledge that major highways are not being pruned now but if waze ever expect to start giving routes over a thousand miles long you can be sure that they will start pruning major highway in the future.

In the Breezewood example, I assume that, because freeway and MH are in the same road type group there is no BDP.

How likely are the BDP rules to change again in the future?

In cases like this, would it generally be a good idea (and something worth putting on the wiki, though I can't imagine where exactly) to advise imposing name continuity IF APPROPRIATE?