LogiAI Input Specs
LogiAI CVRP Input Specs
Use this guide to prepare the CSV accepted by the LogiAI CVRP upload flow. The workspace accepts the flat first-row-is-depot shape shown here, and exported scenario CSVs can also be re-imported.
Overview
Use this guide to prepare valid input files for this workspace. Review the required files, exact column names, example rows, and common formatting rules before uploading.
Required files
1
Optional files
0
Spec sections
1
Upload section
Routing CSV
Upload one CSV with the depot first and each customer stop after it. Fleet, objective, and solver settings stay in the workspace controls rather than the file.
Required file
routing-scenario.csv
Single-file routing scenario input. The first row is treated as the depot and remaining rows become stops.
Requirements
Required columns
stop_idnamelatlondemandservice_time
Optional columns
tw_starttw_end
Row identity
- Required row identity: stop_id.
- The first row is the depot; remaining stop_id values must be unique.
Approved aliases
- stop_id: depot_id or id
- name: label
- service_time: service_minutes
- tw_start: window_start
- tw_end: window_end
Shape requirements
- Flat CSV uploads use the first data row as the depot.
- Sectioned # depot / # stops exports can also be re-imported.
Format limitations
- Time windows use numeric minutes from scenario start; HH:MM time windows are not supported in this CSV contract.
Unsupported currently
- HH:MM time-window values are not supported yet.
Value rules and examples
- The first row becomes the depot when you upload the flat CSV shape.
- lat and lon must be valid geographic coordinates.
- demand and service_time are numeric minutes/units and must be non-negative.
- HH:MM time windows are not part of the current CVRP CSV contract.
- When you provide tw_start and tw_end, tw_end must be at or after tw_start.
Example CSV table
| stop_id | name | lat | lon | demand | service_time | tw_start | tw_end |
|---|---|---|---|---|---|---|---|
| DEPOT | Central Depot | 45.5017 | -73.5673 | 0 | 0 | ||
| C1 | Customer 1 | 45.545 | -73.62 | 3 | 10 | 540 | 660 |
Common mistakes
- Using invalid latitude or longitude values.
- Uploading duplicate stop ids.
- Assuming fleet settings belong in the CSV instead of the Configure step.
Quick rules
- The first row is treated as the depot in the flat CSV shape.
- Stop ids should stay unique.
- Time windows are optional, but when provided they must end after they start.
Navigate
Keep the right guide close by
Pair this upload guide with the product page for workflow context or the resources hub for related public material.
Navigate
Keep the right input guide close
Return to the input-spec library for another upload contract, or go back to the resource hub for quickstarts, how-to guides, and use cases.