Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on September 26, 2017, 08:43:02 am
-
Just noticed this error on the datacheck page.
mo.us040;I-64(34A);I-64(36B);I-64(34C);SHARP_ANGLE;178.65
mo.us040;I-64(36B);I-64(34C);I-64(36A);SHARP_ANGLE;179.44
Seems that the 'I-64(36B)' point is placed out of order in US-40's file and needs to be corrected to fix the multiplex with I-64.
Everything seems to be fine with I-64's file in that area.
-
This is odd because I don't have a separate point for 36B.
Both my I-64 and US 40 files go 34A, 34C, 36A, 36C. What I have as 34C should be 34B; this may be an effect of the I-64 reconstruction. But all the ramps involved for 36B/36C I have combined as a point for 36C, because there isn't a complete interchange. EB has 36B (Tower Grove) and 36C (Vandeventer) while WB has 36B (Boyle). I should, perhaps, move that point westward to be more in the middle but I don't think it should be split into two.
What I have as 34C should be 34B. But I have no idea where that other point came from.
-
I think it came from the "US-66 His ((1926-1933) Manchester)" file.
http://tm.teresco.org/hb/?units=miles&r=mo.us066hisman
-
I blame (https://github.com/TravelMapping/HighwayData/blame/master/hwy_data/MO/usaus/mo.us040.wpt) Si, having added that point in a month ago.
-
I blame (https://github.com/TravelMapping/HighwayData/blame/master/hwy_data/MO/usaus/mo.us040.wpt) Si, having added that point in a month ago.
Yep, sorry, mea culpa. I've fixed the sharp angle issue locally and that fixed file will go in. It seems I put the 36B point between 34A and 34C, rather than 36A and 36C, by mistake.
-
Wait a second. Does this mean a point was added to Missouri routes without telling me?
If this is the case, I have an issue with it.
-
Wait a second. Does this mean a point was added to Missouri routes without telling me?
I told you via multiple ways. Jim waited a good long while before pulling it in too, per my request, so that objections could be raised and changes made (which they were).
-
I don't have any PMs or e-mails about it. Could you point me to the original thread?
-
I honestly got so confused about US-40 reading through this.
-
TMK, Jeff doesn't do GitHub, and submits his updates via email to Jim.
As such, a notice on GitHub is not sufficient to inform him.
-
TMK, Jeff doesn't do GitHub, and submits his updates via email to Jim.
As such, a notice on GitHub is not sufficient to inform him.
Right. I don't mind taking the updates by email for those uncomfortable with GitHub, but maybe we should ask everyone to create an account there so they could be notified of mentions in GitHub issues and pull requests.
-
As such, a notice on GitHub is not sufficient to inform him.
There was the thread here too.
In future, I will send an email to Jeff. If the points disappear, then the points disappear: I'm not fussed - certainly my intention was never to step on toes, merely to do a tedious job so that others didn't have to.
-
I'd argue that 36C can now be folded into 36B per 1PPI.
-
I am going to look into this more. I finally found the thread being referenced, which I had not read through.
-
We all good here with this thread Jeff?
-
I don't think so. Maybe I never sent the file where I renamed 34C to 34B, because GitHub doesn't have it.
I think 36B, centered on Boyle, should remain, while 36C gets deleted. The 36B point is not quite splitting the different between the EB and WB exits with that number, but it's right over the EB-only 36C exit, so it can serve both.
This would make the eastbound order 33D, 34A, 34B, 36A, 36B, 37. Sound good?