MnCORS GNSS Network Frequently Asked Questions
- Does the system provide both real time GNSS corrections and the ability to access Rinex data for post processing?
- Where do I find the Rinex data?
- Do I need to pay a subscription fee to use the system?
- Do I need a dual frequency GNSS receiver to access the system?
- How do I access the system for real time corrections?
- We have two GNSS rovers in our office. Can we use both rovers with a single login?
- My company has multiple customers/rovers. What is the easiest way to register them?
- Do I need a specific brand of GNSS equipment to access the system?
- What vertical datum and what horizontal datum and adjustment does the MnDOT CORS Network use?
- Will the real time coordinate values delivered from the CORS match the values of the HARN stations in my area?
- Is a calibration necessary?
- My rover is able to use Glonass and Galileo satellites. Does the MnDOT CORS Network support the Glonass and Galileo constellations?
- Are there any plans to add stations in the areas of northern Minnesota that do not appear to have good local coverage?
- How far can I work outside of the existing network of GNSS base stations?
- Should I expect downtime due to network failures?
- Which cellular provider is the best?
- Does MnDOT own and maintain all of the GNSS equipment/sites in the network?
FAQ last updated on 10/13/2021
1. Does the system provide both real time GNSS corrections and the ability to access Rinex data for post processing?
Yes.
Top of Page
2. Where do I find the Rinex data?
15 second - 24 hour RINEX, 1 second - 1 hour RINEX or 5 second - 1 hour T02 files can be download from ftp://ftp.olmweb.dot.state.mn.us. With the removal of support for ftp file access in modern web browsers (Chrome, Edge, ...), you will need to use Internet Explorer or, preferably, an ftp client application (such as FileZilla).
Top of Page
3. Do I need to pay a subscription fee to use the system?
No.
Top of Page
4. Do I need a dual frequency GNSS receiver to access the system?
Not necessarily. If your survey demands accuracy in the range of 2-3 cm, you will need a dual frequency receiver. However, if your accuracy requirements will allow up to 1 meter of error, a single frequency receiver will suffice. Please contact your local dealer to check the compatibility of your particular equipment with the system.
Top of Page
5. How do I access the system for real time corrections?
You will need to subscribe to the service on the MnDOT CORS GNSS Network website. Choose the 'MnCORS Data Access and User Management Website' link and then click on Register. After the registration has been completed and submitted a confirmation message that includes your login information will be sent to you by e-mail. Your subscription will remain active as long as you use it at least a few seconds a year. Accounts not accessed for a one year period may be deactivated.
If you have not received a response from a MnCORS Administrator within 3 working days, please contact Nathan Anderson.
Top of Page
6. We have two GNSS rovers in our office. Can we use both rovers with a single login?
Not at the same time. The username/password you were issued will allow access to only one rover at any given time. It is possible to use the same username/password combination with more than one rover if used during different time periods, but it is easiest just to request a login for each rover that will use the system.
Top of Page
7. My company has multiple customers/rovers. What is the easiest way to register them?
You can:
A. Register all rovers individually. This requires that each user has a unique e-mail address. Each username will consist of the first name and last initial. All users who register in this manner will be notified by e-mail about any upcoming changes to the system or any expected outages. This registration also allows MnCORS web access. (Most people register using this method.)
Or...
B. You can send a list of preferred usernames and passwords for your rovers to a MnCORS Administrator at [email protected]. If you do it like this, at least one person in the organization will need to register as suggested in example "A" above. All additional registrations would reside under that "primary user." If you like, the passwords can be the same. None of these users will have web access or receive network informational messages. Those functions would be the responsibility of the primary user.
8. Do I need a specific brand of GNSS equipment to access the system?
No, the software will work with most, if not all GNSS receivers. At this time the GNSS network delivers GNSS data in 5 different formats: RTCM 2.3 (older), RTCM 3.1 (newer), RTCM 3.2 (newest), CMR+ (older), and CMRx (newer). Keep in mind that newer GNSS equipment will be using more satellites and because newer message types are more compact, using the most recent version that your equipment supports will increase the likelihood of an uninterrupted data stream. It is always best to ask your equipment dealer which correction message is the most efficient for your equipment.
The Radio Technical Commission for Maritime Services (RTCM) is an international standards organization. This message type is understood by most if not all GNSS receivers and is generally recommended by equipment dealers other than Trimble.
Compact Measurement Record (CMR) is a correction protocol proprietary to Trimble™. This message type is generally recommended by Trimble dealers as the best choice for Trimble equipment.
9. What vertical datum and what horizontal datum and adjustment does the MnDOT CORS Network use?
Strictly speaking, the MnDOT CORS network is not constrained to a vertical datum. It only facilitates the accurate determination of ellipsoid heights. To produce an orthometric height, an appropriate Geoid separation must be calculated by software within the roving GNSS receiver and subsequently applied to the ellipsoid height. This separation can be determined either by performing a calibration to local control, or by using a standard Geoid model. See Question 11 for calibration recommendations).
The datum and GNSS correction message type used in your application will be determined by the mount point you choose. *A discussion of datums and adjustments follows the mountpoint table. At this time there are 15 available mountpoints:
Mountpoint |
Data Format |
Adjustment |
Geoid Model |
| CMRx_NAD83(1996) | CMRx | 1996 | Geoid03 |
| CMR_Plus_NAD83(1996) | CMR+ | ||
| RTCM_32_NAD83(1996) | RTCM 3.2 | ||
| RTCM_31_NAD83(1996) | RTCM 3.1 | ||
| CMR_Plus_NAD83(2007) | CMR+ | 2007 | Geoid09 |
| RTCM_31_NAD83(2007) | RTCM 3.1 | ||
| CMRx_NAD83(2011) | CMRx | 2011 | Geoid18 |
| CMR_Plus_NAD83(2011) | CMR+ | ||
| RTCM_32_NAD83(2011) | RTCM 3.2 | ||
| RTCM_31_NAD83(2011) | RTCM 3.1 | ||
| RTCM_23_NAD83(2011) | RTCM 2.3 | ||
| AGCMRX | CMRx | ||
| AGCMRP | CMR+ | ||
| AGRTCM32 | RTCM 3.2 | ||
| AGRTCM31 | RTCM 3.1 |
Top of Page
*A discussion of datums and adjustments.
The NAD83(2011) mountpoints will provide corrections consistent with the NGS's recently released NAD83(2011) (Epoch 2010.00) adjustment. This nationwide adjustment was constrained to active NGS certified GNSS CORS stations, 55 of which are a part of the MnCORS network. See https://geodesy.noaa.gov/web/surveys/NA2011/ for further details. It is highly recommended that anyone interested in determining NAVD88 elevations from NAD83(2011) ellipsoid heights, should utilize the latest geoid model, Geoid18 https://geodesy.noaa.gov/GEOID/GEOID18/. Initial testing has indicated that the combination of NAD83(2011) and Geoid18 could potentially produce results more consistent with published NAVD88 values than previous adjustment/geoid model combinations.
The AGXXXX entries are NAD83(2011) mountpoints that were recently added in an effort to accommodate users with equipment, most commonly tailored to the agricultural industry, that does not provide a means to enter special characters. The corrections provided should be identical to that of the corresponding standard 2011 mountpoints.
With the NAD83(1996) mountpoints, we are attempting to provide corrections that will more closely agree with the "HARN" values published for passive control marks throughout the state. Within the Trimble Pivot software that runs our systems, all stations must be positioned in a single NAD83 adjustment; in our case NAD83(2011). In order to produce 1996 and 2007 corrections, a local transformation is applied to shift the "Virtual Reference Station" location established for each RTK session by approximately the difference between the published NAD83(2011) value and the published value for the select adjustment at the nearest CORS station.
The primary limitation of this translation model is that the differences between the three adjustments at the CORS stations are generally smaller than what is observed at the passive control marks. This is probably to be anticipated since, to varying degrees, multiple CORS stations were used as (nearly) fixed control in all of the adjustments. In an effort to provide a better real-world model, we have created a state-wide 8,000 station grid using coordinates extracted from the MnDOT Geodetic database from stations that have a published 1996, 2007 and 2011 coordinate value. The Pivot software applies a Delaunay triangulation to translate the 2011 position to either 1996 or 2007 based on the values in this grid.
Top of Page
10. Will the real-time coordinate values delivered from the CORS match the values of the HARN stations in my area?
Horizontally - Over the last several years, the MnDOT Geodetic Unit has been routinely collecting NAD83(1996), NAD83(2007) and more recently and NAD83(2011) RTK positions on survey monuments throughout the state as part of their recovery and monumentation process. Over approximately 15,000 measurements, both adjustments have produced results that agree with published values within 4cm about 90% of the time. We would expect better results when using the 2011 mountpoints. One distinction however, is that there are a lot more outliers when comparing real-time NAD83(1996) results with published values. We are hopeful that the newly implemented NAD83(1996) mountpoints will provide slightly more accurate and consistent results.
Vertically - For ellipsoidal heights, NAD83(2007) values display a consistent bias of approximately -2cm when compared to the values produced in static GNSS surveys. For NAD83(1996), the bias is about -4cm. NAVD88 elevations computed from ellipsoid heights tend to display this same bias.
If matching with local control is important for your project, calibration (see Question 11) can help resolve the discrepancies between the real-time and published values.
Top of Page
11. Is a calibration necessary?
Usually it is best if you want your survey to fit the local control as close as possible. Although it is difficult to make a blanket statement that covers the entire state, we will say "generally" a one-point vertical calibration is sufficient. Please remember that this can only be determined to any degree of certainty by actually measuring trusted control monuments in your area and examining the differences.
If you think about it, a calibration is exactly what you do every time you set up a portable base station. By default, when you set up the base station over a new monument you are in effect localizing the coordinates.
Note: Trimble Recommendations
With Pre-Defined Coordinate System (ie. County Coordinates):
- Horizontal calibration should be only one point. More could alter the system.
- Vertical calibration should be either one point or more than three points with the geoid model.
Without a Pre-Defined Coordinate System:
- Horizontal calibration should use three or more points.
- Vertical calibration should be either one point or more than three points with the geoid model.
12. My rover is able to use Glonass and Galileo satellites. Does the MnDOT CORS Network support the Glonass and Galileo constellations?
Yes.
Top of Page
13. Are there any plans to add stations in the areas of northern Minnesota that do not appear to have good local coverage?
We need a reliable internet connection in order to move data from a CORS site to our network processors in St. Paul. Finding such sites in these areas has proven difficult, if not impossible. As internet connectivity improves and we are able to identify locations for new base stations, we will continue to improve coverage in these areas. If you are aware of locations that would fit our needs, please send us a note at [email protected].
Top of Page
14. How far can I work outside of the existing network of GNSS base stations?
As a rule of thumb we say you are pretty safe up to around 10 miles outside of the network. You will receive corrections considerably further out than that, but common sense says you should be more diligent in checking control in order to stay within the tolerances your survey requires.
Top of Page
15. Should I expect downtime due to network failures?
Although we make every effort to keep the network running 24/7, it is possible you may experience some infrequent outages.
16. Which cellular provider is the best?
That is hard to say. Essentially you should look for a plan that will allow you to use your phone as a modem and in turn move data to and from the RTK server over the internet. In the metro area most if not all carriers provide this service. Out state you may encounter a more limited number of choices. Your best bet is to contact your local GNSS equipment dealer for recommendations about plans and phones compatible with your equipment and have coverage in your area.
Remember that GNSS coverage in your area does not necessarily equal cell phone coverage in your area. You need both for this system to operate as it is intended.
Top of Page
17. Does MnDOT own and maintain all of the GNSS equipment/sites in the network?
No, we have a number of partners from both the public and private sector who participate in the network by either providing equipment or hosting sites with the necessary communications.
Top of Page