Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: michih on July 30, 2017, 04:33:17 am
-
The extension east of Saguenay is opened: http://www.lapresse.ca/le-quotidien/actualites/201707/28/01-5120336-lautoroute-de-laluminium-vers-la-baie-inauguree.php
-
Thanks, that was fast!
I'll try to figure this out this evening (I'm out of pocket most of today), including a look at the Transports Quebec website. OSM/Mapnik indicates the extension routing, but I'm not yet sure about how much of that is now open, or whether it accurately shows the tie-in to QC 170. mapcat, any thoughts?
The article indicates yet another A-70 extension is in the works, but not for a few more years.
-
I didn't see anything about this while I was drafting canqc (my only concern at the time was whether or not A-70 had been extended yet), so your guess is good as mine.
-
The extension should have a lengths of 7.6km and the interchange @ Chemin de la Grande-Anse seems to be the correct last wp for the time being.
Construction works began in April 2013.
-
The extension should have a lengths of 7.6km and the interchange @ Chemin de la Grande-Anse seems to be the correct last wp for the time being.
That sounds right. Looks like QC 170 has been or will be relocated to tie into that interchange. The Transports Quebec website indicates that some more work is underway to complete the connection to QC 170.
I'll go ahead and extend A-70 to the Grande-Anse interchange. mapcat can then relocate QC 170, to that interchange, once it is clear that has happened.
It looks, from OSM/Mapnik, like the existing connection between the east end of A-70 ad QC 170 has been or will be closed (with QC 170 realigned a little at that point away from A-70), replaced with a connection to the east at new A-70 exit 50 and a short unnamed connector road. I plan to treat the existing A-70/QC 170 connection as a closed intersection in the A-70 file, which can be tweaked later in both that file and QC 170's once the configuration of those routes at that location is clarified.
-
Sounds like a good plan. Let me know when you're ready for me to make the changes.
-
Sounds like a good plan. Let me know when you're ready for me to make the changes.
I just submitted a pull request to extend A-70. No change to QC 170. I don't think you need to update QC 170 until you can confirm that it's been moved to the new Ch. de la Grande-Anse interchange (I don't yet know its exit number).
-
Oscar, do you think the system name should be changed from "Quebec Freeways" to "Quebec Autoroutes"?
-
Oscar, do you think the system name should be changed from "Quebec Freeways" to "Quebec Autoroutes"?
Seconded. Even the English wikipedia article (https://en.wikipedia.org/wiki/Autoroutes_of_Quebec) is called Autoroutes of Quebec, not Freeways.
-
OSM was updated: http://tm.teresco.org/hb/index.php?r=qc.a070
It appears that QC-170 was realignment at the current end of A-70. OSM doesn't indicate any exit number at the current end of A-70.
@Oscar: Do you agree renaming canqca system name, see yakra's post?
-
OSM was updated: http://tm.teresco.org/hb/index.php?r=qc.a070
It appears that QC-170 was realignment at the current end of A-70. OSM doesn't indicate any exit number at the current end of A-70.
Yeah, at least at some zoom levels. Too bad there's no exit number at the new A-70/QC 170 intersection. So if I rename that point in the A-70 file as QC170, and *QC170 as *ToQC170 (which I should've done initially), some users will get credit for driving the extension unless they adjust their list files. I'm tempted to give the terminal interchange an artificial exit number for now, or leaving its name as is, to keep that from happening. But two list files will be broken, my own included, which I think is unavoidable.
In any case, mapcat can go ahead and make whatever changes he needs to make to QC 170.
@Oscar: Do you agree renaming canqca system name, see yakra's post?
I agree, but also that there's no urgency about the change, which I can't do right away.
-
I'll change "Freeways" to "Autoroutes" in systems.csv for the next update.
-
Just a followup note.
While I was up there last week, I field-checked the A-70 extension and related changes to QC 170. No need for us to do anything more there than we've already done. In particular, the interchange at A-70's new eastern end has no exit number. The eastbound lanes end at a roundabout with QC 170, with no ramps directly connecting eastbound A-70 to other roads. That's similar to the roundabout at A-73's southern end, which is likewise not treated as an exit and so gets no exit number.