Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on December 29, 2020, 12:59:07 pm

Title: FL: I-95 and US 1 Minor Considerations
Post by: Markkos1992 on December 29, 2020, 12:59:07 pm
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)

Title: Re: FL: I-95 and US 1 Minor Considerations
Post by: yakra on December 29, 2020, 11:07:39 pm
I-95: US1 should be US1_S since these routes are concurrent now.
A similar situation to NJ US40 & NJ140 (https://forum.travelmapping.net/index.php?topic=4010).
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.
Title: Re: FL: I-95 and US 1 Minor Considerations
Post by: Markkos1992 on December 30, 2020, 08:26:43 am
Quote
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 (https://travelmapping.net/hb/showroute.php?units=miles&u=markkos1992&r=pa.pa523).

I would go with DixHwy or BriAve (https://www.google.com/maps/@25.7500863,-80.2063273,3a,15y,38.48h,92.62t/data=!3m6!1e1!3m4!1sAwfxbhO2KDCmytjCzHWWOQ!2e0!7i16384!8i8192) 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).
Title: Re: FL: I-95 and US 1 Minor Considerations
Post by: yakra on December 30, 2020, 09:52:04 am
With just Brickell Ave here (https://www.google.com/maps/@25.7491185,-80.2125966,3a,25.2y,79.42h,94.57t/data=!3m10!1e1!3m8!1sJPHQf7zAriftKKgyul53pw!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DJPHQf7zAriftKKgyul53pw%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D270.3969%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192!9m2!1b1!2i40), that looks the more sensible of the 2.
Title: Re: FL: I-95 and US 1 Minor Considerations
Post by: rickmastfan67 on November 17, 2023, 01:22:10 am
With just Brickell Ave here (https://www.google.com/maps/@25.7491185,-80.2125966,3a,25.2y,79.42h,94.57t/data=!3m10!1e1!3m8!1sJPHQf7zAriftKKgyul53pw!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DJPHQf7zAriftKKgyul53pw%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D270.3969%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192!9m2!1b1!2i40), 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