A few things about your initial .list file that I'll mention here instead of in a direct email in case they'll be useful to other new users going forward.
- Any lines in your file that aren't meant to be clinched highway segment entries will generate error messages in your log file (which you will be able to see on site once your first .list is processed this afternoon). They do no harm otherwise, so you're welcome to leave those in if the log messages don't bother you.
- All lines intended to match highway segments should have exactly 4 fields, separated by spaces. Many of yours are good, like:
NC I-95 1 66
However, for some routes, you will need to look up the correct abbrevations (we call them the "list names"). So your line:
NC I-74 (Mount Airy) 1 10
Would be just
NC I-74 1 10
since that segment is considered the primary I-74 segment by TM.
Whereas your line:
NC I-74 (Pembroke) 7 9
would be
NC I-74Pem 7 9
The correct "list name" codes can be found on each highway's entry in the TM Highway Browser. Your business routes and future interstates will need similar fixes.
- Also for many (all?) of your entries, you have invalid labels. The labels for the interstates are exit numbers. You can find the actual labels we use also on the highway browser for each route. You can get to the Highway Browser from any page on the main site through the "Highway Browser" link at the top and then going to the system then the highway.
I'll include the file you sent (converted to plain text) in the next site update, so you'll have an entry and you can start to see your log files. I run site updates almost every day, so you're welcome to send in updates any time.
- If you want to see lots of examples of list files, you can see everyone's in our GitHub repository:
https://github.com/TravelMapping/UserData/tree/master/list_filesHope this helps. You'll get the hang of it soon enough I'm sure.