& I-395 "2" that I mentioned in my previous post?
For I-395, I think changing 2B to just 2 may be fine as long as the graph connections stay.
That should be easy enough till we know what they are planning on doing for the reconfiguration there. Done in my local files.
fl.fl540: Old9FootRd -> ...probably Old9FRd
I don't think the '9' would count as a word. Could we go with 'Old9FtRd' maybe? We honestly should have a rule where we could have a few words that can be abbreviated in labels that aren't 'road types'. 'Foot' would be a natural candidate for something like that.
For I-95 at 12B, should there be a graph connection with US 441, FL 9, and FL 826 here?
One of the most annoying interchange setups for sure in the state.
I might be able to get one for all of the routes @ 12B. Then add an extra shaping point on I-95 between 12B & 12C to prevent a false multiplex with US-441 & FL-9.
Ok, here's how I changed this area up:
I-95:12A http://www.openstreetmap.org/?lat=25.921146&lon=-80.210752
+X001A(I95) http://www.openstreetmap.org/?lat=25.924531&lon=-80.209851
12B http://www.openstreetmap.org/?lat=25.926873&lon=-80.207282
+X001B(I95) http://www.openstreetmap.org/?lat=25.928593&lon=-80.205833
12C http://www.openstreetmap.org/?lat=25.930829&lon=-80.204937
And recentered the following labels in each file to match the '12B' coordinates listed above to enable the graph connections for all (@ 12B) without any other changes to their files:
- FL-9: FL826
- FL-826: I-95(12B)
- US-441: FL826
Sound good to you before I submit those changes?