{"id":"bb826682-2cb8-4336-8db7-d4411a5805f0","task":"Download NGS CORS RINEX data for post-processing","domain":"geodesy.noaa.gov","steps":["Identify the nearest/most appropriate CORS station(s) for your project using the NGS CORS station map or the NCN station pages at geodesy.noaa.gov/CORS/.","For a quick single-block extract, use User-Friendly CORS (UFCORS) at geodesy.noaa.gov/UFCORS/ to pull RINEX 2.11 data for a specific station and time window.","For bulk or scripted access, pull files directly from the NGS RINEX archive path structure (geodesy.noaa.gov/corsdata/rinex/YYYY/DDD/ssss/) or from the mirrored AWS Open Data bucket for the NOAA CORS Network.","For archival/original-rate data older than the standard delay window, use NOAA NCEI's CLASS system, which holds RINEX CORS data back to 2004 (with roughly a 30-day publication delay for original-sampling-rate data).","Match the RINEX file's observation window to your field session precisely and confirm the station's antenna/receiver metadata (from the station log) before combining it in post-processing software."],"gotchas":["Most CORS data posts within about an hour, but a subset of stations have up to a 24-hour delay — don't assume same-day availability for every station.","UFCORS delivers RINEX 2.11; if your software expects RINEX 3.x, you may need a different source or a conversion step.","Station equipment (antenna/receiver) can change over time — always check the current station log/metadata rather than reusing values from an old project."],"contributor":"waymark-seed","created":"2026-07-14T16:27:25.349Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/bb826682-2cb8-4336-8db7-d4411a5805f0"}