8000 InCORS network · Issue #24 · Pix4D/ntrip-catalog · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

InCORS network #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
awilken677 opened this issue May 29, 2025 · 6 comments · May be fixed by #25
Open

InCORS network #24

awilken677 opened this issue May 29, 2025 · 6 comments · May be fixed by #25

Comments

@awilken677
Copy link

Indiana's Continuously Operating Reference Network (InCORS) data.

Website: https://incors.in.gov/

Station Coordinates (RTCM ID's): This contains our reference frame information as well as our current station coordinates.

Station Coordinates and RTCM ID Numbers (NAD83 2011).pdf

Broadcast Corrections: This contains the networks available mount points.

InCORS Broadcast RTK Corrections_Products.pdf

User Agreement: This document is how to obtain a free user account for our network

user_agreement revised 2013-6-19.pdf

Connection Information: This document contains our connection instructions

Connection information.pdf

@javier-jimenez-shaw-pix4d
Copy link
Contributor

Thank you @awilken677

Due to summer vacations it may take some more time than we would like to add it. We are on it.

In summary I think the connection url is 108.59.49.226:9000 and all the mountpoints are using NAD83(2011).

As you probably know, next year (hopefully) the modernized CRS NATRF2022 will be in place. Please let us know how are you going to implement the transition as soon as you know it (for instance, having different mountpoints, using a different port, etc).

@bscholer
Copy link
Contributor
bscholer commented May 30, 2025

@awilken677 Thanks for contributing! Just to confirm, are all mountpoints using NAD83(2011)@2010?

@javier-jimenez-shaw-pix4d here is the source table pulled from 108.59.49.226:9000.

SOURCETABLE 200 OK
Server: GNSS Spider 7.9.0.386/1.0
Date: Fri, 30 May 2025 16:13:26 GMT
Content-Type: text/plain
Content-Length: 1437

STR;RTCM3_MAX;RTCM3_MAX;RTCM 3;;2;GPS+GLO;InDOT;;40.28;-86.06;1;1;Leica GNSS Spider;none;B;Y;9600;
STR;RTCM3_IMAX;RTCM3_IMAX;RTCM 3;;2;GPS+GLO;InDOT;;40.28;-86.06;1;1;Leica GNSS Spider;none;B;Y;9600;
STR;RTCM3_NEAR;RTCM3_NEAR;RTCM 3;;2;GPS+GLO;InDOT;;40.28;-86.06;1;0;Leica GNSS Spider;none;B;Y;9600;
STR;RTCM2_IMAX;RTCM2_IMAX;RTCM 2;;2;GPS;InDOT;;40.28;-86.06;1;1;Leica GNSS Spider;none;B;Y;9600;
STR;RTCM2_NEAR;RTCM2_NEAR;RTCM 2;;2;GPS;InDOT;;40.28;-86.06;1;0;Leica GNSS Spider;none;B;Y;9600;
STR;CMR_NEAR;CMR_NEAR;CMR;;2;GPS;InDOT;;40.28;-86.06;1;0;Leica GNSS Spider;none;B;Y;9600;
STR;CMRP_NEAR;CMRP_NEAR;CMR+;;2;GPS;InDOT;;40.28;-86.06;1;0;Leica GNSS Spider;none;B;Y;9600;
STR;CMRP_IMAX;CMRP_IMAX;CMR+;;2;GPS;InDOT;;40.28;-86.06;1;1;Leica GNSS Spider;none;B;Y;9600;
STR;CMRP_IMAX(GNSS);CMRP_IMAX(GNSS);CMR+;;2;GPS+GLO;InDOT;;40.28;-86.06;1;1;Leica GNSS Spider;none;B;Y;9600;
STR;CMRP_NEAR(GNSS);CMRP_NEAR(GNSS);CMR+;;2;GPS+GLO;InDOT;;40.28;-86.06;1;0;Leica GNSS Spider;none;B;Y;9600;
STR;MSM4_NEAR;MSM4_NEAR;RTCM 3;;2;GPS+GLO+GAL+BDS;InDOT;;40.28;-86.06;1;0;Leica GNSS Spider;none;B;Y;9600;
STR;MSM4_IMAX;MSM4_IMAX;RTCM 3;;2;GPS+GLO+GAL+BDS;InDOT;;40.28;-86.06;1;1;Leica GNSS Spider;none;B;Y;9600;
STR;MSM4_VRS;MSM4_VRS;RTCM 3;;2;GPS+GLO+GAL+BDS;InDOT;;40.28;-86.06;1;1;Leica GNSS Spider;none;B;Y;9600;
STR;RTCM3_VRS;RTCM3_VRS;RTCM 3;;2;GPS+GLO;InDOT;;40.28;-86.06;1;1;Leica GNSS Spider;none;B;Y;9600;
ENDSOURCETABLE

@awilken677
Copy link
Author
awilken677 commented May 30, 2025 via email

@bscholer bscholer linked a pull request May 30, 2025 that will close this issue
@hernando
Copy link

@awilken677, is it worth adding the mount points for single antenna (those on ports 7071,7072 and 7073) to the catalog?

@awilken677
Copy link
Author
awilken677 commented Jun 10, 2025 via email

@hernando
Copy link

OK, noted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
0