A finding the IONEX reader reports without refusing the file.

Most concern a header record that summarizes or describes the maps. The values read do not depend on such a record: every map carries its own epoch and bands, so the file reads the same with or without it.

tag names the finding and decides which of the other fields are set:

• :missing_record - label
• :version_record_not_first - line
• :epoch_mismatch - label, line, declared_epoch, maps_epoch
• :map_count_mismatch - line, declared_count, tec_maps, all_maps
• :not_a_number_value - kind, map_number, line, lat_deg, lon_deg
• :interval_mismatch - line, declared_s, map_number, spacing_s
• :exponent_carried_into_map - kind, map_number, line, exponent, set_by_line
• :unhandled - a finding the core reports that this binding predates. Only message is set, and it is the core's own text; no other tag stands in for it.

kind is the band the finding concerns: :tec, :rms or :height for the names the core uses, and the core's own string for any other.

message is the core's formatted text for the finding, carried beside the fields rather than instead of them.

A record the reader passes over raises no finding here. It is counted instead, and read with Sidereon.GNSS.Ionosphere.skipped_records/1 or from a Sidereon.GNSS.Ionosphere.ParseResult, so an empty warning list does not by itself say that nothing was left out.