F25: preserving native instrument context

Native F25 validation is now available

The live platform now parses native comma-delimited F25 records by record identifier and validates their surrounding context. Keep the original order: unit and setup information, station data and subsequent drop records are related evidence. A native F25 file and a tabular FWD export are not interchangeable merely because both describe deflection tests.

The video was recorded before this parser was deployed. Its catalogue-only limitation is historical, not the current feature description. Review actual native parsing and validation findings in the present result. The parser does not certify calibration or engineering capacity, and unsupported or missing evidence must remain explicit.

Keep units, stations and drops together

An F twenty-five file is not simply another rectangular survey spreadsheet. It contains instrument context, station information and repeated drop records. Preserve that structure in the original evidence.

The catalogue describes unit and history records, sensor information and test setup. A numerical reading means little if its force, distance or deflection unit has been misunderstood.

Station records connect location and time to subsequent drops. Moving a drop into another station can change its engineering meaning even when the individual numbers remain unchanged.

Use the result from the current processing run

Open the current file result and read structural findings with their line and record context. Keep the original native export alongside any derived table so that station attribution, units and drop order can be reconstructed. A converted file should document how information was mapped and which original fields were omitted.

Do not assume the tabular F W D schema and native F twenty-five records are interchangeable. Use the ingestion route supported by your deployment, and confirm the actual processing result before relying on coverage.

Keep the untouched instrument file alongside any derived export and document the conversion. Review station, units and drop attribution from source evidence. A successful upload must never stand in for checks that were not performed.

How to use the earlier video

The earlier film remains useful for understanding why a native instrument file needs context. Its statement that a descriptive catalogue entry does not establish a native parser was correct for the version being described; it must not be used to infer that the current deployed platform lacks native F25 parsing.

Use the current selected definition and recorded findings as evidence of coverage. Successful transfer, numeric field acceptance and instrument calibration are separate questions. A parser can identify structural or contextual problems without certifying the physical test setup or pavement capacity.

Sources and scope

This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.