475 Rail Route File Maintenance (005030)
This is the standard X12 005030 spec, with 1 loops and 7 segment positions, as OpenEDI JSON, an ediFabric C# template and an ediFabric Native model. To change it for a trading partner, customize it in the EDI Spec Builder.
Use the 475 spec in your code
ediFabric .NET
Add the C# template and its common files to your project, or reference the template NuGet package, and read 475 files into TS475 objects. See ediFabric .NET.
ediFabric Native
Map version 005030 to the Native model with set_map, then parse 475 files to JSON from Python, Java, C or C#. See Convert between EDI and JSON.
OpenEDI
Select Customize in Spec Builder to copy the spec under your own name, change it for your partner, and parse files against it in EdiNation, ediFabric Native or ediFabric Cloud. Read about OpenEDI.
Generate 475 classes in Python, Java, Node.js, Go, Rust or C
ediFabric Native returns each 475 as JSON, with the property names of the OpenEDI schema. To work with that JSON as typed objects, generate classes from the OpenEDI file in your language and deserialize the JSON into TS475. Serialize the objects back to JSON to build EDI with ediFabric Native. The classes keep the loops, segments, lengths and code lists, but not the EDI data formats, so validate files with ediFabric Native. Read more in Generate a class from OpenEDI.
Python: datamodel-code-generator. Node.js: openapi-typescript. Java, Go, Rust and C: OpenAPI Generator.
475 structure
Loops and segments of the standard 475, with their usage and maximum repeats.
| ID | Name | Usage | Max use |
|---|---|---|---|
| ST | Transaction Set Header | Optional | 1 |
| BGN | Beginning Segment | Mandatory | 1 |
| Loop R9 | Route Code Identification | Mandatory | 50 |
| R9 | Route Code Identification | Mandatory | 1 |
| PER | Administrative Communications Contact | Optional | 1 |
| DTM | Date/Time Reference | Mandatory | 10 |
| RDD | Route Description Detail | Optional | 5 |
| SE | Transaction Set Trailer | Optional | 1 |