Help
Projects and Catalogues
Projects contain your railway, while catalogues describe the components from which that railway can be built. RailKernel manages both as ordinary files so that they remain portable and easy to back up.
RailKernel project files
A RailKernel project contains the complete layout definition: placed track, geometry, accessories, feedback contacts, blocks, locomotives, trains, routes and the other information required to reopen and operate the railway. Projects are stored as XML files. XML is a readable and well-defined exchange format, but a RailKernel project is not intended to be edited manually. A small change to an identifier, reference or XML structure can make the project inconsistent or prevent RailKernel from loading it. Always make structural changes through RailKernel itself.
Local storage and RailKernel Cloud
Projects can be saved locally wherever you choose. The normal projects directory inside RailKernel Home keeps them together with the rest of your RailKernel environment. You can additionally upload a project to RailKernel Cloud as a private backup or make it downloadable for sharing and troubleshooting. Cloud storage supplements the local project; it does not remove the need to save your current work locally.
Track catalogues
A catalogue contains the articles and geometry used when drawing a layout, including connector positions, lengths, curves, turnouts and other component properties. Catalogues are also XML files and should normally be edited with the RailKernel Catalogue Editor. You may use the supplied catalogues, adapt an existing catalogue or create one for your own track system. Keep a separate backup of catalogues containing unpublished personal changes.
Automatic restoration
RailKernel synchronizes its standard catalogues. If a supplied catalogue is removed from the local catalogue directory, RailKernel downloads a fresh copy during a later start. This makes it easy to recover from an accidental deletion or discard unwanted local changes. The same principle applies to standard templates supplied and maintained by RailKernel: a missing distributed template can be restored automatically. Files that exist only as your own custom work must still be backed up by you.