Skip to content

IGS Site Log & GeodesyML inspection, without installing software

Site log inspection runs in Stations and requires an account with Enterprise access.

Paste or upload a site log (.log or .xml) to parse all 14 standard sections, verify DOMES identifiers, inspect antenna and receiver history, and review geodetic compliance diagnostics.

Related tools

Open Stations to paste or upload an IGS site log (.log) or GeodesyML file (.xml).

Audit site logs in Stations

Parse all 14 IGS site log sections and GeodesyML schemas

  • Section 1 & 2: 4-character ID, 9-character DOMES number, monument description, CDP number, and approximate coordinates
  • Section 3 & 4: Full receiver and antenna change history with serial numbers, firmware versions, and ARP offsets
  • Section 5 to 7: Local geodetic ties, frequency standards (Rubidium, Cesium, Maser), and SLR/VLBI/DORIS collocations
  • Section 8 to 14: Meteorological sensors, local conditions, episodic events, and site log revision history
  • GeodesyML XML support: Direct parsing and validation against GeodesyML v0.4 and v0.5 schemas

Automated geodetic diagnostics and integrity audit

  • DOMES syntax verification: Enforces standard 9-character DOMES formatting and country code conventions
  • Epoch continuity check: Detects overlapping dates, missing decommission timestamps, and temporal gaps in instrumentation
  • Phase center alignment: Checks antenna radome designations against IGS naming conventions and ANTEX models
  • Coordinate consistency check: Cross-validates Cartesian XYZ against ellipsoidal latitude, longitude, and height

Seamless integration with station monitoring and network processing

Audited site log metadata links directly into PosFlow station management and Apex network adjustment, ensuring accurate phase center offsets and receiver change history for high-precision geodetic processing.

How to inspect and validate an IGS site log online

Audit GNSS station metadata and validate GeodesyML compliance in 4 easy steps.

  1. Upload or paste site log

    Upload an IGS .log text file or GeodesyML .xml file, or paste the content directly into the inspector.

  2. Parse sections and metadata

    The parser extracts 14 standard sections including DOMES identifiers, receiver models, and antenna eccentricities.

  3. Run compliance diagnostics

    The diagnostic engine verifies DOMES syntax, dates chronological order, and checks radome and coordinate integrity.

  4. Review timeline and findings

    Inspect the hardware change timeline, review warnings or errors, and export structured station metadata.

What won't produce a result

Worth checking before you upload, so a run doesn't cost you credits to tell you what your data was missing.

Incomplete or unformatted text without IGS section headers

Standard IGS Section 1 to 14 headers or GeodesyML XML root tags.

Binary proprietary station configuration files

Standard ASCII IGS site log format or GeodesyML XML text files.

Common questions

What file formats does the site log inspector accept?

The inspector accepts standard IGS ASCII 14-section site log text files (.log) and GeodesyML XML files conforming to v0.4 or v0.5 schemas.

Why is DOMES number validation important for geodetic networks?

A DOMES (Directory of MERIT Sites) number uniquely identifies a tracking monument globally. Validating DOMES syntax prevents station mix-ups during multi-session network solutions.

Does the inspector verify antenna and receiver change history?

Yes. The diagnostic engine reconstructs the chronological hardware timeline and flags missing dates, overlapping installations, or unmatched radome codes.

Related technical guides

Site log inspection runs in Stations and requires an account with Enterprise access. View plans and usage costs

Audit site logs in Stations