Watch the overview
About 2 minutes. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Harbour Roads Training needs to upload a road-condition export. We will prepare the file, choose the matching template, and follow processing without losing track of the original.
- 0:09Keep an unchanged source export before editing. Use a clear filename, such as training-road-condition.csv, and work on a copy when correcting data.
- 0:19Open Check templates and compare the expected columns, values and file type with your export. The template determines which checks can run.
- 0:29A comma-separated file and a semicolon-separated file can look similar in a spreadsheet. Check the actual exported text, including header names and delimiters.
- 0:38Keep road and section identifiers as text where leading zeros matter. Do not let spreadsheet formatting silently turn section 001 into section 1.
- 0:48Confirm the units, dates and coordinate fields expected by the chosen template. A file that opens successfully can still contain the wrong measurements or units.
- 0:57Open Upload a file. Choose the matching check template, attach the export, and supply the details requested on the page. Add the project where that option is available.
- 1:07Check the selected filename and template before submitting. Uploading stores the source; analysis and review are separate steps whose status must be followed.
- 1:17Large or background-processed files can show a processing status page. Keep the job reference and read its stage before deciding whether another upload is needed.
- 1:27If analysis is waiting for credit, the stored source does not need to be uploaded repeatedly. Resolve the balance, then use Run analysis or Retry analysis as instructed.
- 1:37Bulk upload handles several files, but each file still needs a suitable template and its own outcome. Review every result instead of assuming the batch succeeded together.
- 1:48Read the actual error. Correct a format problem in the source, or retry a failed analysis through its existing record when appropriate. Avoid duplicate submissions while status is uncertain.
- 1:59Pause here. Identify the template, delimiter and units for the sample export. Upload one training file and locate its processing result before attempting a batch.
Prepare one controlled example
Harbour Roads Training needs to upload a road-condition export. We will prepare the file, choose the matching template, and follow processing without losing track of the original. Keep an unchanged source export before editing. Use a clear filename, such as training-road-condition.csv, and work on a copy when correcting data. Open Check templates and compare the expected columns, values and file type with your export. The template determines which checks can run.
Example: a delimiter mistake
A comma-separated file and a semicolon-separated file can look similar in a spreadsheet. Check the actual exported text, including header names and delimiters. Keep road and section identifiers as text where leading zeros matter. Do not let spreadsheet formatting silently turn section 001 into section 1. Confirm the units, dates and coordinate fields expected by the chosen template. A file that opens successfully can still contain the wrong measurements or units.
Choose the upload route
Open Upload a file. Choose the matching check template, attach the export, and supply the details requested on the page. Add the project where that option is available. Check the selected filename and template before submitting. Uploading stores the source; analysis and review are separate steps whose status must be followed. Large or background-processed files can show a processing status page. Keep the job reference and read its stage before deciding whether another upload is needed.
Example: insufficient credit
If analysis is waiting for credit, the stored source does not need to be uploaded repeatedly. Resolve the balance, then use Run analysis or Retry analysis as instructed. Bulk upload handles several files, but each file still needs a suitable template and its own outcome. Review every result instead of assuming the batch succeeded together. Read the actual error. Correct a format problem in the source, or retry a failed analysis through its existing record when appropriate. Avoid duplicate submissions while status is uncertain.
Preserve the source before importing
Keep identifiers such as 001 as text when their leading zeroes form part of the identifier. A spreadsheet display format can show zeroes that are absent from the exported value. Inspect the saved text and compare it with the untouched source. Retain the intended units and distinguish a missing measurement from a legitimate zero.
If processing is waiting for credit, inspect the existing stored file and analysis state. Repeatedly uploading the same source can create confusing records without resolving the underlying credit requirement.
Practise and check your interpretation
Pause here. Identify the template, delimiter and units for the sample export. Upload one training file and locate its processing result before attempting a batch.
The supplied .blc examples use the TMH-18.blc template, version v5-2016, semicolons, UTF-8 and CRLF line endings. Start and end kilometre values are kilometres; ROAD_WIDTH is metres. Keep every declared column, including empty optional columns. Use the corrected file first in an authorised training account, then compare the deliberately faulty examples. Confirm the stored record and processing state before trying a bulk upload.
Use the signed-in onboarding library to record viewing progress and return to unfinished lessons. Watching the public article is useful for reference, but does not update your account’s lesson completion record.
Sources and scope
This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.