Closed michihdeu closed 4 years ago
I think just make it clear that the current way to specify still works and will continue to work. The new format is strictly a convenience for mapping travels across boundaries.
Modify .list file structure - future link: a) By travel b) By system c) By region (likely use of 4-field entries only)
https://github.com/TravelMapping/DataProcessing/issues/58#issuecomment-636434986
Current version:
Many users break up list files into chunks by region or highway type to make it easier to read or manage.
Version on next update:
Many users break up list files into chunks by system, region or individual travel to make it easier to read or manage. We recommend sorting by system to keep the .list file small.
Omit or region
on purpose in the last sentence to be future-proof for enabling 6-field entries.
Future version:
Many users break up list files into chunks by system, region or individual travel to make it easier to read or manage. We recommend sorting by system to enable using the multi-region .list file option and to keep the .list file small.
I'd just state it as this, and not "recommend" anything:
TM users organize their list files in different ways to make them easier to read and manage. Some prefer to organize by system, region, or individual travel. The order doesn't matter to the TM system, so do whatever works best for you.
If there are no objections, I'll change it tomorrow to:
Many users break up list files into chunks by system, region or individual travel to make it easier to read or manage.
I think using the new showroute list entry tool should be mentioned in the manual once that version's up on the main site.
To be added when https://github.com/TravelMapping/DataProcessing/issues/58 is live.
Not under
First steps with email submission
but underAdvanced features
. However,More examples of how to break down your travels
describes the actual multi-region handling and must be changed too. Maybe splitting the chapter into two chaptersMulti-region segments
andBeltways
.t.b.d.