Travel Mapping
Highway Data Discussion => In-progress Highway Systems & Work => Topic started by: michih on May 23, 2020, 11:40:16 am
-
Actual status of the systems:
frabfcd21 - Côte-d’Or Routes Départementales
frabfcm21 - Dijon Métropole Routes Métropolitaines
frabfcd25 - Doubs Routes Départementales
frabfcd39 - Jura Routes Départementales
frabfcd58 - Nièvre Routes Départementales
frabfcd70 - Haute-Saône Routes Départementales
frabfcd71 - Saône-et-Loire Routes Départementales
frabfcd89 - Yonne Routes Départementales
frabfcd90 - Territoire de Belfort Routes Départementales
Legend:
Black=not yet drafted (not in HB), Red=devel, Orange=preview, Green=active
Notes to routes:
https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/FRA-BFC/frabfcd/README.md
Please report issues here!
-
frabfcd25 - Doubs Routes Départementales will be in preview with the next site update. About 480 routes with 2,000 miles.
-
frabfcd39 - Jura Routes Départementales will be in preview with the next site update. 515 routes with almost 2,000 miles.
-
frabfcd58 - Nièvre Routes Départementales will be in preview with the next site update. 312 routes with more than 2,500 miles.
-
frabfcd70 - Haute-Saône Routes Départementales will be in preview with the next site update. About 400 routes for almost 2,000 miles.
-
frabfcd90 - Territoire de Belfort Routes Départementales will be in preview with the next site update. 76 routes for 300 miles.
-
Future M route systems: https://forum.travelmapping.net/index.php?topic=2976.msg20989#msg20989
frabfcm21 - Dijon Métropole Routes Métropolitaines
-
frabfcd71 - Saône-et-Loire Routes Départementales will be partially in HB as in-development system with the next site update. Mostly trunk routes (orange on OSM).
frabfcd89 - Yonne Routes Départementales is partially in HB as in-development system. Mostly trunk routes (orange on OSM).
-
frabfcd89 - Yonne Routes Départementales will be in preview with the next site update. More than 400 routes for over 2,800 miles.
-
M123 (https://www.google.com/maps/@47.2816306,5.0174827,3a,15y,301.22h,92.03t/data=!3m6!1e1!3m4!1sGcXEIsJrRXQcSx3JYFhJHw!2e0!7i16384!8i8192), M903 (https://www.google.com/maps/@47.3598876,5.0464902,3a,16.4y,282.93h,91.37t/data=!3m6!1e1!3m4!1sAph2D8tax6x8VYk2Ap1zWg!2e0!7i16384!8i8192) and M974 (https://www.google.com/maps/@47.3598153,5.0468751,3a,15y,330.68h,96.61t/data=!3m6!1e1!3m4!1sYQLcL0i2G_QTKFFqbg8ljw!2e0!7i16384!8i8192) in Dijon are signed according to Sep / Oct 2020 GSV :) I also checked some inner city routes but those do still have black/yellow D signs or have no numbering on signs.
https://routes.fandom.com/wiki/Dijon_M%C3%A9tropole
-
frabfcd71 - Saône-et-Loire Routes Départementales will be in preview with the next site update. Almost 500 routes for over 3,000 miles.
-
frabfcm21 - Dijon Métropole Routes Métropolitaines will be in preview with the next site update. 38 routes for 85 miles.
It is a preliminary draft since Sep/Oct 2020 GSV does not yet cover the whole metropolian area and the both end locations of the routes are not clear (unlike Lille where I have a map clearly indicating the routes). See readme (https://github.com/TravelMapping/HighwayData/tree/master/hwy_data/FRA-BFC/frabfcd) for more info. I just drafted the system to know more or less the transitions to the D route system so that I can draft frabfcd21 system now - the last one of the region :)
Edit: frabfcd21 - Côte-d’Or Routes Départementales will be in devel with the next site update.
-
frabfcd21 - Côte-d’Or Routes Départementales will be in preview with the next site update. More than 570 routes for over 3,300 miles.
All system of Bourgogne-Franche-Comte are in preview now :)
-
D1, D2, D3, D4, D5, D7, D8, D9, D10, D11, D11A, D12, D13, D14, D15, D16 - fine
D17 - D130 -> HSa/TeB (as D130 is in a different system)
D18, D19, D19Bel, D20, D21, D22, D23, D23Elo, D23B, D24, D25, D26, D27, D28 - fine
D29 - D60 -> RueAer
D30 - RueGraCha -> RueChe
D31, D32, D33, D34, GES D34, D34Bre, D35, D36, D37, D38 - fine
D39 - D480 -> Dou/TeB
D39Mez, D39A, D40, D41, D42, D43, D44, D46, D47, D47B, D48, D49 - fine
D50 - add point for RueDeuxFon as leads to D26/D42
D51, D52, D53, D55, D56, D57, D58 - fine
D59 - signed as D466 (https://www.google.co.uk/maps/@47.8100712,6.8466987,3a,48.7y,139.34h,98.42t/data=!3m6!1e1!3m4!1s2pKGCxl0W-v6pSxacHcvIg!2e0!7i13312!8i6656?hl=en), with the OSM D59 signed as D59 (https://www.google.co.uk/maps/@47.8051853,6.8465821,3a,40.2y,148.83h,97.75t/data=!3m6!1e1!3m4!1scq1j0rsmKKSFepeXRZKa-Q!2e0!7i13312!8i6656?hl=en)
D60, D60A, D61, D83, D119, D171, D419, D437, D463 - fine
D465
- D59 -> D466
- Ger -> D59
D1083 - fine
-
D17 - D130 -> HSa/TeB (as D130 is in a different system)
You convinced me doing so when reviewing one of the first frad systems. I implemented it ever since. I think you argued that there is no rule for using district (i.e. departement) border names. I can try looking back if you want....
btw, I will be traveling for the next three weeks. I will be processing the reviews "afterwards".
-
D17 - D130 -> HSa/TeB (as D130 is in a different system)
You convinced me doing so when reviewing one of the first frad systems.
When there's a road of same system...
And you do the border point every other time.
btw, I will be traveling for the next three weeks. I will be processing the reviews "afterwards".
you might have a full inbox! But no worries about delays.
-
D17 - D130 -> HSa/TeB (as D130 is in a different system)
You convinced me doing so when reviewing one of the first frad systems.
When there's a road of same system...
And you do the border point every other time.
I failed finding your proposal in this thread, fraidf (https://forum.travelmapping.net/index.php?topic=3568) or frahdf (https://forum.travelmapping.net/index.php?topic=3630). Where else did we talk about departement / district border label names? I'm sure that I was told to replace Xxx/Yyy non-region border labels by the road number of the route beyond the border. Minimum when the border / wp is at a junction. Which regions out of France have systems changing at district borders? I think it's important because there are a lot of wp labels named according to this approach... Was it when talking about wp label rules?
btw, I will be traveling for the next three weeks. I will be processing the reviews "afterwards".
you might have a full inbox! But no worries about delays.
I don't worry since your peer-review-to-be-processed backlog is also still quite long ;) I'd love to have gufd (https://forum.travelmapping.net/index.php?topic=4751) done soon. It's small and the last chocolate system in rest of America.
-
I failed finding your proposal in this thread, fraidf (https://forum.travelmapping.net/index.php?topic=3568) or frahdf (https://forum.travelmapping.net/index.php?topic=3630). Where else did we talk about departement / district border label names? I'm sure that I was told to replace Xxx/Yyy non-region border labels by the road number of the route beyond the border. Minimum when the border / wp is at a junction. Which regions out of France have systems changing at district borders? I think it's important because there are a lot of wp labels named according to this approach... Was it when talking about wp label rules?
I did say this one, but it's not the route over the border:
D924
- HDF/IDF -> D929
but that's as it meets D929 (https://travelmapping.net/hb/showroute.php?units=miles&u=michih&r=frahdf.d000495&lat=49.163705&lon=2.294748&zoom=15) in that system and region. In fact it also meets D4 from that system, but not in that region.
And here, I ask you to rename a point (https://travelmapping.net/hb/showroute.php?units=miles&u=michih&r=frahdf.d016362oig&lat=50.460851&lon=3.026240&zoom=15) which you've named after the intersecting side street rather than the border. Note that I don't have you call it D54a (the departmental road in Nord), but instead the border.
D163Oig - RueFus -> PdC/Nor (no intersecting route, but the route on the continuation of this route on the other side of the border)
I believe the confusion is coming from this one:
D173 - Yvl/HdS_N -> Yvl/HdS, Yvl/HdS_E -> D907 (I know the D907 is in HdS, and the D307 ends at this point, but a border point in middle of the route is wrong)
You will, however, note that I explicitly make a comment that the route I'm asking you to label is in a different department (and system) due to the mutual assumption that this was not good labelling, but point out that it's better than the terrible alternative we start with.
Which regions out of France have systems changing at district borders?
Obviously there's the Corse/Alsace exceptions where two departments share a system because the departments don't maintain roads but the collectivity does, and a few places where one department maintains a route in another department, but the Route Departmental systems explicitly change at departmental boundaries such as these - after all that's sort of their whole schtick!
And all-but-two of the routes I've reviewed so far have used departmental boundary labels where the route ends at one (providing it doesn't meet another route of the same system at that point). Both of which are in this system - and are exceptional even within this small system - at least 10 times that number of points use the boundary labels within this system, despite that system being small.
-
I believe the confusion is coming from this one:
D173 - Yvl/HdS_N -> Yvl/HdS, Yvl/HdS_E -> D907 (I know the D907 is in HdS, and the D307 ends at this point, but a border point in middle of the route is wrong)
You will, however, note that I explicitly make a comment that the route I'm asking you to label is in a different department (and system) due to the mutual assumption that this was not good labelling, but point out that it's better than the terrible alternative we start with.
Yep, I believe you are right. But it's not at the end of the route, so totally different than D17-90's wp. :pan:
You will face similar shit in other systems. Please report it and I'll change it. Thanks.
-
https://github.com/TravelMapping/HighwayData/pull/6084
D29 - D60 -> RueAer
Nope, D60 is signed on 2018 and 2019 GSV, confirmed by OSM, GM and my beloved wikisara (https://routes.fandom.com/wiki/Route_d%C3%A9partementale_fran%C3%A7aise_D60_(90)). Extended D60 instead.
-
Further comments on frabfcd90 - Territoire de Belfort Routes Départementales before activation?
-
Looks like you've addressed my comments, and the extending the D60 shows that you've given the system a look too. So it's double thumbs up from me!
-
frabfcd90 - Territoire de Belfort Routes Départementales will be activated with the next site update.
-
frabfcm21 - Dijon Métropole Routes Métropolitaines will be in preview with the next site update. 38 routes for 85 miles.
It is a preliminary draft since Sep/Oct 2020 GSV does not yet cover the whole metropolian area and the both end locations of the routes are not clear (unlike Lille where I have a map clearly indicating the routes). See readme (https://github.com/TravelMapping/HighwayData/tree/master/hwy_data/FRA-BFC/frabfcd) for more info. I just drafted the system to know more or less the transitions to the D route system so that I can draft frabfcd21 system now - the last one of the region :)
Checked. Looks fine. Virtually no changes related to GSV coverage. I changed the D/M transition labels to the municipality since the wps are exactly at the boundaries: https://github.com/TravelMapping/HighwayData/pull/6323
frabfcd21 and frabfcm21 are also ready for peer-review now.
-
frabfcd21 - Côte-d’Or Routes Départementales
I agreed with michih to review this system.
After checking for completeness, the following routes seem to be missing (the links are to the signs in GSV). I could not find signs at each end for every route:
D5A (https://maps.app.goo.gl/vSQzV7qFHWVauGYM6) - This seems to be the sign at the other end (https://maps.app.goo.gl/MstoYLuUCPtBpVhN9)
D6A (https://maps.app.goo.gl/G7BiBPgy5442TYZG6)
D104N (https://maps.app.goo.gl/zhkUHBJLLRipj2pY6)
D119N (https://maps.app.goo.gl/t21fgN3xB6m7ebwo6)
D119R (https://maps.app.goo.gl/6DqHGGHcp7XuVkaU9)
D701 (https://maps.app.goo.gl/YRdhRqYkXfXhu5Tt9) - This is the east end. Here is the west end. (https://maps.app.goo.gl/UjVXQ8M5fY8J2Ks3A) Bypass around Mirebeau-sur-Bèze
There are some other missing routes that are unsigned in GSV, so I left them off the list. I'll continue with the rest of the peer review soon.
-
https://github.com/TravelMapping/HighwayData/pull/8355
Thanks for starting the review :)
Notes can sometimes be found in the readme (https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/FRA-BFC/frabfcd/README.md). I learned meanwhile, that wikisara is not a reliable source.
There are some other missing routes that are unsigned in GSV, so I left them off the list. I'll continue with the rest of the peer review soon.
si404 and me agreed long ago to draft all routes that are indicated on OSM + GM albeit no GSV available or no sign visible on GSV. We also draft routes that are only indicated on OSM + GSV, or GM + GSV.
-
si404 and me agreed long ago to draft all routes that are indicated on OSM + GM albeit no GSV available or no sign visible on GSV.
I think mapcat basically did the same thing for drafting Puerto Rico with the spreadsheet found online.
-
https://github.com/TravelMapping/HighwayData/pull/8355
There are some other missing routes that are unsigned in GSV, so I left them off the list. I'll continue with the rest of the peer review soon.
si404 and me agreed long ago to draft all routes that are indicated on OSM + GM albeit no GSV available or no sign visible on GSV. We also draft routes that are only indicated on OSM + GSV, or GM + GSV.
Ok, I will keep that in mind going forward. I double checked the missing routes and did not see any that would be included under those criteria. I did find a sign for D30A (https://maps.app.goo.gl/BHwFjrjP1BJxk4gr7) that I overlooked earlier though. This route is also missing.
I noticed you did not add D119N in that pull request. Was that intentional?
-
https://github.com/TravelMapping/HighwayData/pull/8355
Thanks for starting the review :)
Notes can sometimes be found in the readme (https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/FRA-BFC/frabfcd/README.md). I learned meanwhile, that wikisara is not a reliable source.
Neither are Google Maps and OSM.
-
https://github.com/TravelMapping/HighwayData/pull/8357
I did find a sign for D30A (https://maps.app.goo.gl/BHwFjrjP1BJxk4gr7) that I overlooked earlier though. This route is also missing.
I noticed you did not add D119N in that pull request. Was that intentional?
By accident ;)
Neither are Google Maps and OSM.
Yep. The chance is high when both indicate the same though.
-
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.
-
Ok. I'll note any I find just in case you want to add them later.
-
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...
-
That works for me. I won't worry about them.
-
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 (https://maps.app.goo.gl/PDSRMxqxS6WbCj1y8)
D3D: Add point at Route de Savigny (https://maps.app.goo.gl/y5jhTjfxdi1hpqmr6). 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 (https://maps.app.goo.gl/hBXxEXJnMh9m6xHu8) 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 (https://maps.app.goo.gl/JztJ1kQaeK61XACLA)
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 (https://maps.app.goo.gl/DHZoiu8f7fvWQL5i6) 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
-
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' (https://travelmapping.net/devel/manual/wayptlabels.php#split). Please explain why you think I should change them.
D4: Maybe add a point at Chemin du Pont St. Jacques (https://maps.app.goo.gl/hBXxEXJnMh9m6xHu8) 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 (https://travelmapping.net/hb/showroute.php?r=frabfc.d0005b21) but it's clearly signed at D965 (https://maps.app.goo.gl/k5QNVCJyFVcEteVe9). 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 (https://maps.app.goo.gl/qvA3pGa71ugH4e7r9).
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
-
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' (https://travelmapping.net/devel/manual/wayptlabels.php#split). Please explain why you think I should change them.
I was basing it on the guidance here (https://travelmapping.net/devel/manual/wayptlabels.php#underscore), 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?
-
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 (https://maps.app.goo.gl/SELnk4BYiDTkZAEL7)
D9E, D9F, D9G, D9H, D9J, D9K, D9L, D9M, D10, D10B, D10C- All good
D10D:
What about replacing ImpMou with a point here (https://maps.app.goo.gl/WEAtzYqJ1CGn3gta8)? 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 (https://maps.app.goo.gl/CEPRbtGMp6yfJHEP9) ?
D10H:
CheNoy -> RueFour or RueNanThil ? Signs here (https://maps.app.goo.gl/Ggk6ZgZBNTx1Jcub9)
D10J, D10K, D10L, D11, D11A, D11B- All good
D11C:
C4 -> VC (https://maps.app.goo.gl/54Ryw41ugL4sd8k17) ?
D11D, D11E, D12, D12A, D12B, D13, D13A, D13C, D13D, D14 - All good
D14A:
Dra -> RueFon (https://maps.app.goo.gl/mhReqKZtkzLmCiDt8)
Replace shaping point with RueCro (https://maps.app.goo.gl/hHhv8snjNsqT1Un19) ?
D14B:
GraRue -> RueLav (https://maps.app.goo.gl/WrTXL1Wck5oWJ2su8)
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 (https://maps.app.goo.gl/rzLnNt4EhDrXC9GF8)
Maybe replace shaping point X69 with a visible point at C2 (https://maps.app.goo.gl/cJ7nR8wRTU4VUcKK7)
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 (https://maps.app.goo.gl/TSXWgvNfDiL29Jhj6)
D16H - All good
D16I:
RueRat -> C2 (https://maps.app.goo.gl/iDbk6xs6QvdELsrF9)
RuePom -> C7 (https://maps.app.goo.gl/zFXahA7V1fhqKbUd7)
D16_S - reposition (see D16)
D16J, D16K, D16L - All good
-
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 (https://maps.app.goo.gl/vKxtvvuLJhLjskWBA) GSV (https://maps.app.goo.gl/VKP5V1ppvMKsq9uu7). Changed.
-
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 (https://maps.app.goo.gl/rnxXkMyDJjRGdoDX8) ?
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 (https://maps.app.goo.gl/vDssxU54qarGt66J9) - I couldn't find where it ends though
All good - D19H, D19K, D19L
-
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.
-
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 (https://maps.app.goo.gl/QqLp5yA5nuYDxs1Y9)
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 (https://maps.app.goo.gl/76QfKVxgMtiimzsYA)
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
-
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.
-
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 :D
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