Maintaining CORS station metadata and equipment history
Station metadata connects a continuous GNSS dataset to its physical installation, equipment changes and responsible operators.
Treat metadata as measurement information
A continuously operating GNSS station produces observations over time, but the meaning of those observations depends on the installation that produced them. Metadata describes the monument, antenna, receiver, offsets, coordinates, contacts and equipment history. It is therefore part of the measurement record, not merely an administrative directory. A long archive becomes difficult to interpret if users cannot determine which physical configuration applied to a particular observation period.
Begin with the requirements of the station's intended network or service. IGS guidance provides a recognized example of structured station metadata, but the exact obligations depend on the station's role. Use the applicable format and maintain a clear local source of truth. Avoid scattering critical facts across private emails, installation photographs and controller notes without a controlled record that links them.
Continue learning CORS and network RTK: understanding the reference service
Define the station and physical reference clearly
Record a stable station identifier and describe the monument sufficiently for another qualified person to identify it. Include the relationship between the permanent mark and the antenna reference point. Offsets need a defined direction, units and measurement method. A height value without its physical endpoints can be misinterpreted later, particularly after equipment replacement or a change in mounting arrangement.
Keep photographs that show the monument, antenna attachment and surrounding environment. Date them and identify their orientation where useful. Photographs complement measurements but do not replace precise offset information. They can explain site changes, such as a new roof or nearby structure, that affect interpretation of the observation history even when the station identifier and nominal coordinates remain unchanged.
Continue learning Selecting a site for a continuously operating GNSS reference station
Record complete equipment identifiers
Use the antenna, radome and receiver identifiers expected by the adopted metadata standard and processing workflow. Preserve serial numbers where required and distinguish model information from an individual unit's identity. The antenna calibration selected in processing depends on correct identification. A shortened local nickname may be convenient for staff but insufficient for an external analyst trying to apply the appropriate model to archived observations.
Record firmware and relevant configuration history with effective times. A receiver update can change tracking or recording behavior without changing the physical monument. The importance of each change depends on the system, but an undocumented update creates uncertainty when users later investigate a discontinuity or altered data completeness. Keep the record factual and linked to the actual equipment state rather than a planned maintenance date that was never confirmed.
Continue learning Using GNSS antenna calibration information correctly
Use effective times consistently
Metadata changes should identify when the new configuration began and, where applicable, when the previous one ended. State the time system. Installation work can span a period rather than occur at one instant, so record interruptions and uncertainty honestly. A maintenance ticket creation time is not necessarily the time at which an antenna was replaced or observations resumed.
Check that the equipment history aligns with observation headers and event logs. If a receiver restart or conversion process writes stale metadata into a file, resolve the inconsistency and preserve the correction record. Users should not have to choose between two conflicting authoritative descriptions. A controlled source of truth makes it possible to propagate approved updates into downstream files and services consistently.
Continue learning Monitoring CORS continuity and data quality together
Capture changes in the surrounding site
The measurement environment can change without any equipment replacement. Nearby construction, vegetation growth, new reflective surfaces or altered access can affect station behavior. Maintain dated notes and photographs for significant changes. This helps analysts interpret quality trends and distinguishes an environmental change from a receiver problem or physical movement of the monument.
Assign responsibility for periodic site review. An operator focused on data delivery may not notice gradual changes around the antenna. A simple inspection checklist can connect maintenance visits with metadata updates. Record what was observed and whether action is required. The aim is not to document every passing object, but to preserve meaningful changes that could influence the station's long term measurement record or availability.
Continue learning CORS and network RTK: understanding the reference service
Keep contact and responsibility information current
Users and network coordinators need a reliable route to the station operator. Maintain current organizational contacts and backup responsibilities according to the applicable publication policy. Separate public operational contact information from private credentials and sensitive infrastructure details. Metadata should enable support and accountability without exposing passwords, access tokens or unnecessary personal information.
Plan for staff changes. A station should not lose its history when one engineer leaves or a maintenance contractor changes. Store the approved record in an organizational location with controlled editing and backup. Document who may approve changes and how conflicts are resolved. This turns metadata maintenance into a repeatable operational process rather than a task dependent on an individual's memory and personal files.
Continue learning Selecting a site for a continuously operating GNSS reference station
Validate the record against real files
Periodically compare the station record with a sample of delivered observation files and processing inputs. Check station identifiers, antenna names, offsets, receiver information and relevant dates. A metadata file can be internally tidy while disagreeing with what users actually receive. Automated comparisons can help identify mismatches, but important exceptions still need review against installation evidence and maintenance logs.
Do not repair discrepancies by guessing which value is most plausible. Trace the source, consult the responsible operator and document the approved correction. Preserve previous published versions where the workflow permits, so users can determine what information was available when an earlier solution was computed. This is especially important when a metadata correction affects interpretation of a long historical observation span.
Continue learning Using GNSS antenna calibration information correctly
Manage publication and downstream updates
When metadata changes, distribute the update through the network or service's supported process. Identify affected users and products where appropriate. A corrected antenna identifier in a local spreadsheet does not help analysts who continue receiving stale headers or an outdated published site log. Coordinate the update across the actual delivery chain and confirm that the authoritative record reflects the approved state.
Keep a change summary with the reason, effective time and responsible reviewer. If an earlier record was wrong, state the affected period clearly. A correction is different from a new physical installation, and users may need to reprocess data accordingly. Clear version history makes that distinction visible and reduces the risk that a future analyst mistakes a metadata repair for a real station event.
Continue learning Monitoring CORS continuity and data quality together
Preserve a history that supports interpretation
The final station archive should connect installation evidence, metadata versions, equipment changes, observation files and operational incidents. Use stable identifiers and readable formats alongside any required network submission format. Test that another staff member can locate the configuration for a selected historical date without asking the original installer to reconstruct it from memory.
Good metadata makes a continuous station useful beyond today's stream of observations. It allows users to understand discontinuities, select antenna models, reproduce processing and assess whether changes are physical or operational. Maintaining that history with the same discipline as the observation archive protects the long term value of the entire CORS installation.
Continue learning CORS and network RTK: understanding the reference service
Practical checklist
- Treat metadata as measurement information.
- Manage publication and downstream updates.
- Preserve a history that supports interpretation.
Plan your GNSS setup
Compare the EQ10 and EQ20 receiver specifications, then discuss the configuration and support your project needs.
Compare GNSS receivers
