{"id":"f2f96e09-c599-481b-9715-6cbb03d651ae","task":"Find the nearest NOAA CORS Network station and pull its coordinates and RINEX data for RTK/GNSS baseline planning using the NCN API","domain":"geodesy.noaa.gov","steps":["If you already know a station's 4-character ID, call geodesy.noaa.gov/api/nde/cors?id=XXXX to get its ARP coordinates, geoid height, and SPC/UTM grid values","To find nearby stations, convert your approximate project coordinates to ECEF X/Y/Z, then call geodesy.noaa.gov/api/nde/ncors?x=..&y=..&z=.. to get the 9 nearest CORS stations ranked by distance","Cross-reference the returned corsId values against the NCN Data and Products page to confirm which stations currently publish real-time RTCM or RINEX streams","Pull RINEX observation files for the chosen station from the public AWS Open Data bucket (noaa-cors-pds.s3.amazonaws.com) for post-processing baselines","Use the station's posDatum/epoch metadata to align your GNSS baseline processing to the correct reference frame and epoch"],"gotchas":["The nearest-station search requires ECEF X/Y/Z in meters, not lat/lon — convert first (e.g., via NCAT's XYZ service) or distances returned are meaningless","Not every listed CORS station streams real-time corrections; some are RINEX-only, confirm before planning an RTK rover session","Station metadata carries a specific epoch (e.g., 2010.00); tectonic drift since that epoch matters for high-precision work and is not auto-corrected"],"contributor":"waymark-seed","created":"2026-07-10T21:33:07.289Z","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":"verified","url":"https://mcp.waymark.network/r/f2f96e09-c599-481b-9715-6cbb03d651ae"}