FL: I-95 and US 1 Minor Considerations

[Markkos1992]

I-95: US1 should be US1_S since these routes are concurrent now.

US 1:  1. BriAve_N should be BriAve or US41_W.
2.  I think that BisBlvd should be 3rdSt since Biscayne Blvd does not continue south of here.  (also affects US 41)

[yakra]

I-95: US1 should be US1_S since these routes are concurrent now.

A similar situation to NJ US40 & NJ140.
Although for that one, you discussed the waypoint label on the route that doesn't end, and here, you discussed the label on the route that does end.

Drafting a response My thoughts on how I handle similar situations are in that thread...

In a nutshell...
I-95 doesn't split from the multiplex here, and it's debatable whether US1 does (less of a split & just one route unceremoniously ending).
I prefer what both routes would actually be intersecting at this location -- in this case, FedHwy.

[Markkos1992]

In a nutshell...
I-95 doesn't split from the multiplex here, and it's debatable whether US1 does (less of a split & just one route unceremoniously ending).
I prefer what both routes would actually be intersecting at this location -- in this case, FedHwy.

I see.  This is what you had suggested I do for PA 523.

I would go with DixHwy or BriAve based on GSV.  This makes me wonder if we should do the same for US 1.  In this scenario, either DixHwy_N, BriAve, or BriAve_S could be used (dependent on what is done with the current BriAve_N).

[yakra]

With just Brickell Ave here, that looks the more sensible of the 2.

[rickmastfan67]

With just Brickell Ave here, that looks the more sensible of the 2.

Sadly, 'BriAve' is unavailable for use in the US-1 file @ I-95, due to it being a in-use label that's hidden under 'BriAve_N'.  Best I could do there is 'BriAve_S' for US-1.

So, the following changes are as follows:
US-1:
I-95 -> BriAve_S
BriAve_N -> US41_W
BisBlvd -> 3rdSt (same change in US-41)

I-95:
US1 -> BriAve

https://github.com/TravelMapping/HighwayData/pull/6998