High-precision PPK processing without the desktop software

PPK processes recorded rover and reference observations after a mission, without requiring a live correction link in the field. Signal obstruction and phase interruptions can still prevent reliable ambiguity resolution. Preserve overlapping base data and inspect the trajectory and quality report.

• Solves a dual-frequency kinematic baseline between your rover and a single base station you provide, on GPS, GLONASS, Galileo and BeiDou as you select them per solution
• Fetches precise orbits for the observed period automatically, with no navigation file to upload and nothing to download by hand
• Reads the antenna type and height from each RINEX header and applies the IGS absolute phase-centre model automatically; a header with no antenna listed still runs, with zero offsets, and the report says so
• Switches between SHORT and LONG processing automatically at a 10 km baseline, or force SHORT, LONG or AIR yourself. There is no enforced maximum baseline, but accuracy degrades as it grows

• Upload a DJI Timestamp.MRK file, or a plain ISO-8601 timestamp list (.txt/.csv, up to 8 MB). Without one, event epochs already flagged in the rover RINEX file are used instead
• Lever-arm offsets between the antenna and the camera, read from the MRK file, are applied to every event before its position is reported
• Each event is linearly interpolated between the two bracketing trajectory epochs; one more than 2 seconds from the nearest epoch is refused rather than guessed, and unmatched events are listed with a reason
• Export camera_events.csv: sequence, time, latitude, longitude, ellipsoidal height, fixed/float quality and per-axis sigma, or download it pre-formatted for Pix4D, Agisoft Metashape or DJI Terra

• A .pos trajectory in RTKLIB-style columns: GPS time, latitude, longitude, height, fix quality (1 fixed / 2 float), satellite count and per-axis sigma
• The same trajectory as NMEA, KML and CSV
• camera_events.csv, when camera events were supplied or detected in the rover file
• A PDF report in English or Chinese, all bundled into one ZIP download

• A run fails outright only when the solved window covers fewer than 20 epochs, or less than half of the rover recording. Every other run returns a report
• The fix rate (the share of epochs whose ambiguities resolved to fixed integers) is a grade, not a pass/fail gate: 98%+ excellent, 95%+ good, 85%+ acceptable, and anything lower is graded poor
• Fix rate measures how many epochs resolved, not how accurate the trajectory is. Read it together with the coverage ratio, gaps, median ENU sigma and baseline length in the report
• The report also states which base-coordinate source was used, and includes the satellite timeline, the residual sky map and the post-fit residual RMS