Mapping - Field order

[stufraser1]

Does the order of fields in a mapping file matter?
With an eye on being able to provide 'industry default' mapping files, ideally we would easily draw attention to fields and values which differ from the 'default' developed collaboratively and agreed by e.g. the Exposure Transformation techincal working group. Could we put the adjusted fields at the top of the file, for example?

[stufraser1]

In transform: Order of fields transformed does not matter - BUT the order of fields in output csv file will reflect the order of fields in mapping file - so the mapping file order should be dictated by any required ordering of fields in model input.

In types: Order of input fields does not matter.

reverse/forward: These can be placed in any order, as long as the full block is present (including types: and transform:)

input_format/output_format: These can be placed in any order and before or after other blocks, as long as they are outside the forward/reverse blocks.

[stufraser1]

add this to the mapping files section in docs

[stufraser1]

Workshop 30 March 22: Participant feedback supports standard ordering of fields:

"order of fields does matter in Touchstone files - not critical but would help in manual validation to see fields in order. >> Default mapping files should have correct order of fields."

[stufraser1]

Documented at https://oasislmf.github.io/OpenDataTransform/components/setup/mapping-files.html