Author Topic: updates.csv: non-root data in the root column  (Read 5907 times)

0 Members and 1 Guest are viewing this topic.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4450
  • Last Login:January 01, 2025, 09:44:22 pm
  • I like C++
updates.csv: non-root data in the root column
« on: February 14, 2022, 05:30:29 pm »
ut.ut085 (West Jordan)
" (West Jordan)" was probably intended to be in the Route rather than Root column. Though oddly, there's only one UT85 in the HB now, without a City, and updates.csv doesn't mention I don't see another one being deleted and folded into a main UT85 route.
Edit: Ah. Found it: 2019-03-30;(USA) Utah;UT 194;ut.ut194;New route number for former discontiguous section of UT 85 in Lehi

autsisrab -> ita.autsisrab

il/il057 -> il.il057

gbna (here & here) and mnem ("Re-entered"?") don't produce a valid link to a single route in the HB. These fields could be left blank, but these entries may be better suited for systemupdates.csv instead.
« Last Edit: February 14, 2022, 05:50:07 pm by yakra »
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1027
  • Last Login:Yesterday at 04:36:10 pm
Re: updates.csv: non-root data in the root column
« Reply #1 on: February 14, 2022, 05:51:22 pm »
ut.ut085 (West Jordan)
" (West Jordan)" was probably intended to be in the Route rather than Root column. Though oddly, there's only one UT85 in the HB now, without a City, and updates.csv doesn't mention another one being deleted and folded into a main UT85 route.

There is no mention of that because that didn't happen. There is, however, this:
Quote
2019-03-30;(USA) Utah;UT 194;ut.ut194;New route number for former discontiguous section of UT 85 in Lehi

You're right about "(West Jordan)" being in the wrong column though, that's an oopsie and lemme fix that. Gonna keep the reference to West Jordan since there were two UT85 segments at the time of that update.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3318
  • Last Login:Yesterday at 11:31:00 pm
Re: updates.csv: non-root data in the root column
« Reply #2 on: August 16, 2023, 03:51:56 pm »
autsisrab -> ita.autsisrab

gbna (here & here) and mnem ("Re-entered"?") don't produce a valid link to a single route in the HB. These fields could be left blank, but these entries may be better suited for systemupdates.csv instead.

I am guessing si404 more or less never saw this thread or forgot about it.

il/il057 -> il.il057

I fixed this one.  Also I-72 should have been I-172 in the original updates entry.

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

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4903
  • Last Login:Yesterday at 02:48:34 pm
Re: updates.csv: non-root data in the root column
« Reply #3 on: December 22, 2024, 06:36:12 am »
gbna (here & here) and mnem ("Re-entered"?") don't produce a valid link to a single route in the HB. These fields could be left blank, but these entries may be better suited for systemupdates.csv instead.

I think we should just remove the system name from the route field of these 2016/18 update entries and then finally close this thread. I'll remove them later this month if @si404 does not beat me.

I think the thread can be closed then?

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4450
  • Last Login:January 01, 2025, 09:44:22 pm
  • I like C++
Re: updates.csv: non-root data in the root column
« Reply #4 on: December 22, 2024, 08:18:19 pm »
Any thoughts on moving the entries to systemupdates.csv?
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4903
  • Last Login:Yesterday at 02:48:34 pm
Re: updates.csv: non-root data in the root column
« Reply #5 on: December 25, 2024, 02:53:11 am »
Quote
2019-10-31;France;fraa;France Autoroutes;re-entered
2019-10-31;France;fran;France Routes Nationales;re-entered
2019-10-31;(France) Corsica;fracort;Corsica Routes Territoriales;re-entered
2018-01-05;Montenegro;mnem;Montenegro Magistralni Put;re-entered
2017-10-06;Germany;deua;German Autobahnen;re-entered
2017-10-06;Germany;deub;Germany Bundesstraßen;re-entered
2017-10-06;(Germany) Bavaria;deubyst;Bavaria Staatsstraßen;re-entered
2017-10-06;(Germany) Hesse;deuhel;Hesse Landesstraßen;re-entered
2017-10-06;Germany;eure;UNECE International 'E' Roads (Germany);re-entered
2017-10-06;Germany;eursf;Europe Select Named Freeways (Germany);re-entered
2017-10-06;Spain;espa;Spain Autopista / Autovia;re-entered
2017-10-06;Spain;espn;Spain Carretera Nacionales;re-entered
2017-10-06;Spain;eure;UNECE International 'E' Roads (Spain);re-entered
2017-10-06;Spain;eursf;Europe Select Named Freeways (Spain);re-entered

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4903
  • Last Login:Yesterday at 02:48:34 pm
Re: updates.csv: non-root data in the root column
« Reply #6 on: December 29, 2024, 03:32:54 pm »
gbna (here & here) and mnem ("Re-entered"?") don't produce a valid link to a single route in the HB. These fields could be left blank, but these entries may be better suited for systemupdates.csv instead.

@yakra, your links point to a commit from 2022. It's not the latest version of updates.csv :pan: The fields are already blank. The invalid links are gone. Marking solved.