SN Coverage Supporting GNSS Correction Services

We are currently supporting full GNSS correction capabilities in the following markets.  We will continue to roll out GNSS capabilities to all hardware capable areas in the near future.  Please check this KB Article over the coming weeks for updates.

If you log into SmartNet and you see any of your constellations drop, this is not a severe issue.  This simply means the station you are connected to is either not fixed on a particular constellation or currently is not activated for that constellation.  Over the next 30-60 days this is expected and there is no need to create a support ticket.  After October 1, 2017 if you are one of the markets listed below, please let us know if you experience drops of entire constellations.

• Connecticut
• Delaware
• Eastern Massachusetts
• Eastern Pennsylvania
• Maryland
• Metro Boston
• New Jersey
• Rhode Island
• Virginia
• Washington DC

South East Markets

• Georgia
• North Carolina
• South Carolina

North Central Markets

• Iowa
• Indiana
• Metro Chicago
• Metro Minneapolis / St. Paul
• Michigan
• Minnesota
• North Dakota
• Ohio
• South Dakota
• Wisconsin

South Central Markets

• Arkansas
• Kansas
• Louisiana
• Metro Dallas/FW
• Metro Houston
• Metro Kansas City
• Metro San Antonio
• Missouri
• Oklahoma
• The Valley (TX)
• West Texas

North West Markets

• Metro Denver
• Oregon
• Utah
• Washington

South West Markets

• California
• Metro Phoenix
• Metro Tucson
• Nevada

Eastern Canada Markets

• PEI

Western Canada Markets

• L. Mainland BC

To be able to receive GNSS corrections you must use one of our RTCM 3.2 MSM Mountpoints.  There are currently three (3) RTCM 3.2 MSM Mountpoints, MSM_IMAX, MSM_NEAR & MSM_VIRS.  The Master Auxiliary Correction (MAC) is not supported by RTCM 3.2 MSM and therefore unavailable for use with full GNSS Corrections.  The standard for RTCM 3.2 MSM does not include the required message segments to support MAC at this time.

Updated July 31, 2018