Importing your roster
Already track your fleet in a spreadsheet? Import it into Rail Ops instead of re-typing everything. Locomotives and cars are imported separately, since they capture different information.
Locomotives vs. cars
| Import as… | Required columns | |
|---|---|---|
| Powered engines | Locomotives | RoadName, RoadNumber, Model |
| Rolling stock | Cars | RoadName, RoadNumber, CarType |
Before you start
- Export your existing list to
.csv. - Make sure each row has, at minimum, a reporting mark, a road number, and a model (locomotives) or car type (cars).
- Don't worry about setting up railroads, car types, or models first. Anything missing gets created during the import.
Rail Ops matches rows to what's already in your roster by reporting mark + road number, so you can import the same file again after fixing it without creating duplicates.
Getting it back out
Anything you import can be exported again, either as a CSV in the same layout or as a file JMRI can read. See Exporting your roster.
Next
Bring your locomotive fleet into Rail Ops from a CSV file.
Add a locomotive by hand, track its decoder, and keep your fleet organized.
Bring your rolling stock into Rail Ops from a CSV file.
Add a car by hand, edit many at once, and keep your roster organized.
Where to go to edit, organize, and maintain your cars and locomotives.
Download your cars or locomotives as a CSV, or for JMRI.