Configure a survey rover to pull free real-time GNSS corrections from the Ohio DOT statewide RTK network instead of a commercial VRS subscription.
domain: ortn.dot.state.oh.us · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the Ohio Real Time Network (ORTN) landing page at https://ortn.dot.state.oh.us/ for network status and coverage.
Request access credentials — ODOT issues a login and password through its Pivot Network portal after a registration form is submitted (email cors@dot.state.oh.us for account issues).
Configure the rover's NTRIP client to the ODOT caster at the currently published IP/port (156.63.133.115, port 2101 as of this network's latest published contact info) using your issued credentials.
Select the correct mount point for your receiver brand: ODOT_G_R_E_C_RTX_CMRx for Trimble equipment or ODOT_G_R_E_C_RTX_RTCM3 for non-Trimble GNSS/GLONASS/Galileo/BeiDou receivers.
Confirm fixed-RTK solution and compare against a known ODOT/NGS control point before relying on the corrections for boundary-grade work.
Known gotchas
ODOT's caster IP address has changed before (older docs list a different IP) — always verify the current IP/port on the ORTN site itself rather than trusting a cached blog post.
This is a separate, state-specific NTRIP network from the crowdsourced RTK2go casters — ORTN requires an ODOT-issued account, it is not open/anonymous access.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?