GitLab

Why that is used instead of the dedicated field for this information is
unknown, but that's at least the case for BVG.

Necessary now that we have multiple sources providing this information.

Needed for handling both cases during layouting.

Only SBB seems to provide this so far though.

This fixes empty entries when logging all communication.

Those slipped in here by habit and caused runtime warnings.

This fixes Theme-related regressions with the latest version.

This produces almost equal-sized coaches when interpolating based on the
SBB data.

This is needed when statically linking against KPublicTransport

This is far from perfect yet (coaches can get widely varying lengths
for example), but this starts to produce something useful for SBB Hafas
data.

Allows us to use the upstream files as-is.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This has no effect on alert messages (those are always provided in all
available languages), but it does impact locations and/or navigation
instructions. The supported languages of both sets also can differ,
the former depends on what it fed into the system while the latter
seems to be rather based on OTP/Digitransit's translation catalogs.

This is for backends not supplying positions in platform-relative
coordinates but just the section name. This has yet to be used
in the vehicle layout model.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Those failed to match automatically.

This can consume both the Transport API Repository file structure as well
as our own. The result helps with reviewing/editing coverage areas.

The station name seems to be inserted there in some cases, which confuses
the JSON parser.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This covers everything that applies without semantic conflicts, a few cases
remaining that need closer investigation.

This is a basic 1:1 conversion, with additional data from upstream merged
that doesn't conflict with our existing data. There's more that will need
manual review to properly align/merge.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

With those gone, our generic platform name normalization takes care of
the rest here.

Parsing of that yet to be implemented.