NEW: Multi-region user .list file entries

[michih]

A new feature is available: Multi-region user .list file entries.

The 4-field user .list file entry as described on the manual still works and will stay in place as-is. There is no need to change anything!
However, you can optionally use a 6-field user .list file entry now. It is no longer necessary to break travels at regional borders which can reduce the number of user .list file entries.

Format:

4-field user .list file entry:

Code: [Select]

Region Route Waypoint1 Waypoint2
6-field user .list file entry (new):

Code: [Select]

Region1 Route1 Waypoint1 Region2 Route2 Waypoint2
Examples:

Example for the 4-field entry:

Code: [Select]

WA I-90 WA519 WA/ID
ID I-90 0 999
MT I-90 0 999
WY I-90 0 999
SD I-90 0 999
MN I-90 0 999
WI I-90 0 999
IL I-90 0 999
IN I-90 0 999
OH I-90 0 999
PA I-90 0 999
NY I-90 0 999
MA I-90 0 MA1A
Example for the 6-field entry covering the same segments:

Code: [Select]

WA I-90 WA519 MA I-90 MA1A
Or

Example for the 4-field entry:

Code: [Select]

DEU-SH A7 DNK/DEU SH/HH
DEU-HH A7 SH/HH HH/NI
DEU-NI A7BeW HH/NI NI/HH
DEU-HH A7SiW NI/HH HH/NI
DEU-NI A7BeE HH/NI NI/HH
DEU-HH A7SiS NI/HH HH/NI
DEU-NI A7 HH/NI NI/HE
DEU-HE A7Wit NI/HE HE/NI
DEU-NI A7Han HE/NI NI/HE
DEU-HE A7 NI/HE HE/BY
DEU-BY A7 HE/BY BY/BW
DEU-BW A7 BY/BW BW/BY
DEU-BY A7Neu BW/BY BY/BW
DEU-BW A7Det BY/BW BW/BY
DEU-BY A7Fel BW/BY BY/BW
DEU-BW A7Unt BY/BW BW/BY
DEU-BY A7Hei BW/BY BY/BW
DEU-BW A7Ege BY/BW BW/BY
DEU-BY A7Kem BW/BY DEU/AUT
Example for the 6-field entry covering the same segments:

Code: [Select]

DEU-SH A7 DNK/DEU DEU-BY A7Kem DEU/AUT

The feature description will be added to the manual soon.

[yakra]

Topic moved to Instructions and Discussions until remaining out-of-order _con.csv lines are fixed.
Edit: Fixed. Topic moved back to Welcome & Notices.

[michih]

The multi-region user .list file entry (6-field entry) is described in the manual now: https://travelmapping.net/participate.php#multiregion
Again, the 4-field entry is still the common way to go and will remain in place!

Note that the ".list Tool" option is also available now. It helps generating the full .list file entry!

[Jim]

Note that the ".list Tool" option is also available now. It helps generating the full .list file entry!

For a few routes where I've added travels since the .list Tool's introduction, I've found it very useful to click the "Select Clinched Segments" button, highlight my new segments, then just paste in the segments in place of whatever I had in my .list file for the route.  No more worries about figuring out which segment I need to add/expand, or introducing typos.

I must say it was also oddly satisfying to replace my collection of I-90 lines with the single line

Code: [Select]

WA I-90 WA519 MA I-90 MA1A
I haven't bothered changing other connected routes to use 6-field entries except where I have new travels, but that one was just screaming out to be simplified.  I was still using CHM's old 0 and 999 labels for the endpoints, and I am still doing so for the majority of my long-clinched interstates..

[SSOWorld]

See my list file for I-435.  It is not completing the loop even though it has the right code.  See also issue https://github.com/TravelMapping/DataProcessing/issues/347  Cincinatti, DC, Jax, Baltimore and Charlotte will likely have this problem too.

https://travelmapping.net/hb/showroute.php?units=miles&u=master_son&r=ks.i435&cr

[yakra]

Thanks for the report; I will look into this shortly.
I'll discuss it over on the GitHub issue, to avoid bogging this topic down with technical details.