FL 909 & 922

[yakra]

FL922: FL915/909 may more appropriately be plain FL915, if FL909 (North Miami Beach) terminates a wee bit north on FL915 as shown in the HB.

The FL FL922 *FL909_S point added here resulted in a couple NMPs not yet maked FP:

Code: [Select]

fl.fl909nmi End (25.88995,-80.187702) NMP fl.fl922 *FL909_S (25.89022,-80.187503)
fl.fl922 *FL909_S (25.89022,-80.187503) NMP fl.fl909nmi End (25.88995,-80.187702)


[rickmastfan67]

FL922: FL915/909 may more appropriately be plain FL915, if FL909 (North Miami Beach) terminates a wee bit north on FL915 as shown in the HB.

With the way the intersection is configured, and signed, it's just best to leave the label as-is.
https://maps.app.goo.gl/g9sR81YafH8ZRyqE8

The FL FL922 *FL909_S point added here resulted in a couple NMPs not yet maked FP:

Code: [Select]

fl.fl909nmi End (25.88995,-80.187702) NMP fl.fl922 *FL909_S (25.89022,-80.187503)
fl.fl922 *FL909_S (25.89022,-80.187503) NMP fl.fl909nmi End (25.88995,-80.187702)


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

[yakra]

is and is not!
is and is not!

I believe the HB should be kept consistent with itself (in terms of routing vs labels) when practicable.
This may be a case of a DOT omitting TO plates for brevity/"clarity".

[rickmastfan67]

is because of the direct connection.

[Markkos1992]

is because of the direct connection.

Yeah I am with you on this one.