frabfcdXX: Bourgogne-Franche-Comte Routes Départementales

[michih]

Hi, I was wondering how you want to handle multiple routes at the same waypoint.

For example, D1, D1D, and D103 all intersect:

D1's point is D1D/D103
D1D's point is D1/D103
but D103's point is just D1, without D1D

Is this something you would want me to report in the peer review, or is it not important since the manual does not require it?

Thanks for pointing that out. I don't remember where si404 and me agreed on that. I simply dropped the child number if the parent number is already used in the label name throughout France. To avoid making the labels too complicated.

[cenlaroads]

Ok.  I'll note any I find just in case you want to add them later.

[michih]

I think that there are many. I won't add them. We would end up with wps like D999/D1234E10 for no good reason. No need to note them...

[cenlaroads]

That works for me.  I won't worry about them.

[cenlaroads]

frabfcd21 - Côte-d’Or Routes Départementales

No errors noted in data check list.  There are no unmarked NMPs.  Concurrencies look good in HDX.  I'll continue to check those as I review the routes.


Reviewing the routes through D6E:


D1:  D4J_N -> D4J_W and D4J_S -> D4J_E
D1:  D4_S -> D4_W and D4_N -> D4_E

D1A, D1B, D1C, D1D, D2, D2sav, D2A, D3, D3B, D3C - All good

D3D:  Add point at the partial interchange with D903B
D3D:  Add point at Route de Savigny.  This seems to be the only way to access D903B southbound in this area.

D4:  Maybe add a point at Chemin du Pont St. Jacques since there are few bridges across the river in this area
D4:  D36/D954 -> D954_W - the concurrency with D36 continues south of here

D4A, D4B, D4C, D4D, D4E, D4F - All good

D4G:  D4_S -> D4_W and D4_N -> D4_E

D4H:  D36_N -> D36_W and D36_S -> D36_E

D4J, D4K - All good

D4L:  Reverse the waypoint order?  It seems more north-south

D4Land - All good

D4M:  D9_E -> D9_N and D9_W -> D9_S
D4M:  Consider replacing shaping point +X16 with a point at RueRoc

D5:  D101_W -> D101_N and D101_E -> D101_S
D5:  D29_E -> D29_N and D29_W -> D29_S

D5A - All good

D5B:  The route is extending into Yonne and ending at D965 of that system; Should be truncated to the department border

D5C - All good

D5D:  Also extending into Yonne; needs to be truncated

D5E:  RueEgl appears to be an unmarked driveway for the church.  Move point to RueCit or RueCha

D5F, D6 - All good

D6die:  There is no graph connection with D901_E

D6A, D6B, D6C, D6D, D6E - All good

[michih]

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

D1:  D4J_N -> D4J_W and D4J_S -> D4J_E
D1:  D4_S -> D4_W and D4_N -> D4_E
D4G:  D4_S -> D4_W and D4_N -> D4_E
D4H:  D36_N -> D36_W and D36_S -> D36_E
D4M:  D9_E -> D9_N and D9_W -> D9_S
D5:  D101_W -> D101_N and D101_E -> D101_S
D5:  D29_E -> D29_N and D29_W -> D29_S

There is no 'signed direction'. Please explain why you think I should change them.

D4:  Maybe add a point at Chemin du Pont St. Jacques since there are few bridges across the river in this area

All are very small roads. I don't think that anyone would ever need that wp.
btw, I often tried to find matching points on routes were intersecting roads lead to. It's not a rule but my practise. That would mean, I also had to add a wp to D4J. This could to a domino effect...

D1:  D4J_N -> D4J_W and D4J_S -> D4J_ED4L:  Reverse the waypoint order?  It seems more north-south
D4Land - All good

If we see both D4L segments as one route, it's more west-east

D5B:  The route is extending into Yonne and ending at D965 of that system; Should be truncated to the department border

Departement boundaries are tricky, and just as everything in France, highly depending on the departements' practise. I'm either gone with official coords (not available for BFC), departement signs at the boundary (often off from OSM's boundary lines), change in pavement or any marking (if GSV was available) or what's indicated on OSM/GM. I usually spent quite some time to find the best boundary locations (not for the first systems drafted (FRA-IDF) but once I got familar with the practise).
It's rare that routes extend far into the other departement like D5B but it's clearly signed at D965. Yonne does have a D5 but far away from D5B's location. Thus, I don't think that D5B is a child of Yonne's D5.

D5D:  Also extending into Yonne; needs to be truncated

I'm gone with this small marking.

D6die:  There is no graph connection with D901_E

I think it's OK since there is a short connection road b/n both. Not 1PPI: https://travelmapping.net/hb/showroute.php?r=frabfc.d000621die&lat=47.516636&lon=5.073173&zoom=17

[cenlaroads]

D1:  D4J_N -> D4J_W and D4J_S -> D4J_E
D1:  D4_S -> D4_W and D4_N -> D4_E
D4G:  D4_S -> D4_W and D4_N -> D4_E
D4H:  D36_N -> D36_W and D36_S -> D36_E
D4M:  D9_E -> D9_N and D9_W -> D9_S
D5:  D101_W -> D101_N and D101_E -> D101_S
D5:  D29_E -> D29_N and D29_W -> D29_S

There is no 'signed direction'. Please explain why you think I should change them.

I was basing it on the guidance here, where it says to use the relative position of the waypoints along the route whose file is being made.  However, looking at the link you provided, now I understand that the rules are different when identical waypoints result from multiplexes as opposed to when they result from multiple intersections without multiplexes.  I was thinking of the suffix as always identifying the waypoint.  So, disregard these suggestions


The other points you mentioned make sense.  Thanks for the clarification about departmental boundaries.  Is that small arrow commonly used to mark them?

[cenlaroads]

frabfcd21 - Côte-d’Or Routes Départementales

Edited:  Updated to include routes through D16L


D7:
D9/D16_E -> D9_E, D9/D16_W -> D9_W  -  D7 is concurrent with D16 here

D7B, D7C - All good

D8:
D8A - recenter

D8A:
D8 - recenter

D8B, D9 - All good

D9A:
D8/D954 -> D9/D954

D9B, D9C - All good

D9D:
It is signed past RueEgl at least as far as here

D9E, D9F, D9G, D9H, D9J, D9K, D9L, D9M, D10, D10B, D10C- All good

D10D:
What about replacing ImpMou with a point here?  The point is really only needed for shaping, and this is more likely to be used by regional travelers

D10E - All good

D10F:
Good, but FWIW, Google Maps and OSM both show this route extending about a mile SW from A38.  GSV is from 2013 though.  No signs are visible

D10G:
PlaEgl -> RueFon ?

D10H:
CheNoy -> RueFour or RueNanThil ?  Signs here

D10J, D10K, D10L, D11, D11A, D11B- All good

D11C:
C4 -> VC ?

D11D, D11E, D12, D12A, D12B, D13, D13A, D13C, D13D, D14 - All good

D14A:
Dra -> RueFon
Replace shaping point with RueCro ?

D14B:
GraRue -> RueLav

D14C, D14D - All good

D15:
D15C_E - reposition

D15A, D15B - All good

D15C:
Did -> RueMar or RouMol ?
D15/D906_S - reposition (see above for D15)

D15D, D15E, D15F, D15G, D15H, D15J - All good

D16 (Sombernon):
The route appears to be missing a concurrency with D6 all the way to Lamargelle, where it is signed at D901
Maybe replace shaping point X69 with a visible point at C2
D16I_S - reposition
D970/D977B_N - reposition

D16poi, D16roc - All good

D16vie:
D17F_W -> D17F_E
D17F_E -> D17F_W

D16A, D16B, D16C, D16D, D16E, D16F - All good

D16G:
It's signed farther north than RueEgl, at least to here

D16H - All good

D16I:
RueRat -> C2
RuePom -> C7
D16_S - reposition (see D16)

D16J, D16K, D16L - All good

[michih]

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

D10F:
Good, but FWIW, Google Maps and OSM both show this route extending about a mile SW from A38.  GSV is from 2013 though.  No signs are visible

It's clearly signed on 2022 GSV. Changed.

[cenlaroads]

D16 (Sombernon):
You changed the old D6 waypoint to D6_E, but it seems like it should be D6_W, or maybe just D6

Picking up at D17:

All good - D17, D17A, D17B

D17C:
D115L_E - reposition

D17D:
San -> RueCro ?

All good - D17E

D17F:
Maybe replace shaping point X18 with a point at one of the two nearby crossroads

All good - D17G, D17H, D17I, D17J, D17K, D17L, D17N

D18:
D114D - reposition
D115_Ant -> D115_E
D115D - reposition

All good - D18A, D18B, D18C

D19:
D19E - reposition
D19F - reposition

All good - D19A, D19B, D19C, D19D

D19E:
D19 - reposition (see above)

D19F:
Reverse point order
D19 - reposition (see above)

D19G:
It is signed as going north of D954 - I couldn't find where it ends though

All good - D19H, D19K, D19L

[michih]

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

D16 (Sombernon):
You changed the old D6 waypoint to D6_E, but it seems like it should be D6_W, or maybe just D6

D6_W. It's a concurrency.

D18:
D115_Ant -> D115_E

D115 is not concurrent but simply intersecting here. It was a si404 thing to use location prefixes for non-concurrencies.... I didn't like it but adopted that way in the meanwhile. Keep as-is.

D19:
D19E - reposition
D19F - reposition

I am was the one with the most accurate wp positioning. However, I had never ever reported that "inaccuracy".... "Fixed" though btw, I try to go with satellite view instead of OSM for positioning if possible.

[cenlaroads]

D20:
D31_N -> D31_S and D31_S -> D31_N

All good - D20A, D20B, D20C, D20D

D20E:
Should the name All8Mai1945 be shortened?

D20F:
D115D needs to be extended to D20F - here

All good - D20G, D20H, D21, D21A, D21B, D21C, D21D, D22, D22mon, D22A, D22B, D22C, D22D

D22E:
Reverse waypoint order

All good - D23, D23meu, D23A, D23B, D23C, D23D, D24, D24B, D24C, D25, D25A, D25B, D25C, D25D, D25E

D25F:
Maybe replace shaping point with a point at C2

All good - D25G, D25H

D26:
D114_W -> D114_S

All good - D26A, D26B, D26C, D27, D27A, D27B, D27C, D27D, D27E, D27F, D27G, D27H

D27J:
D30_E -> D30_W and D30_W -> D30_E ?

All good - D27K


Edited to add:

D28, D28cou, and D28ora:
It seems more north-south, so maybe reverse the point order?
If so, some border waypoints would be changed as well

All good - D28A, D28B, D28C

D28D:
Reverse waypoint order ?

All good - D28E, D28F, D28G, D28H, D28M

[cenlaroads]

D19:
D19E - reposition
D19F - reposition

I am was the one with the most accurate wp positioning. However, I had never ever reported that "inaccuracy".... "Fixed" though btw, I try to go with satellite view instead of OSM for positioning if possible.

I don't remember how off those were and wasn't sure how precise you wanted to be.  If you're using satellite view, I'm sure that would be more accurate   I usually try to let them go unless they are a good bit outside of the path of both routes.

[michih]

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

D20E:
Should the name All8Mai1945 be shortened?

si404 advised me to do it this way.

D19:
D19E - reposition
D19F - reposition

I am was the one with the most accurate wp positioning. However, I had never ever reported that "inaccuracy".... "Fixed" though btw, I try to go with satellite view instead of OSM for positioning if possible.

I don't remember how off those were and wasn't sure how precise you wanted to be.  If you're using satellite view, I'm sure that would be more accurate   I usually try to let them go unless they are a good bit outside of the path of both routes.

Just load these pairs into wpt editor

Code: [Select]

D19E_old http://www.openstreetmap.org/?lat=47.610098&lon=4.962725
D19E_new http://www.openstreetmap.org/?lat=47.610094&lon=4.962677

D19F_old http://www.openstreetmap.org/?lat=47.607418&lon=4.435113
D19F_new http://www.openstreetmap.org/?lat=47.607400&lon=4.435151