Do you have some raw measurement data and would like to try RTKLIB before downloading and configuring it? If so, follow these instructions to get a solution emailed directly to you in just a few minutes.
RTKLIB Demo Instructions
Send an email to email@example.com that follows these rules:
- The email subject must include the words “rtklib demo”
- The base and rover data must be in attached files , either separate or zipped together and the total attachments must be less than 25 MB
- The rover files must have the letters “rov” in the file names
- The base files must have the letters “base” in the file names
- Valid file extensions are .ubx, .*nav, .obs, and .yy* where yy is the year (e.g. .17o)
- At least one navigation file from either the base or rover must be included as well as observation files from both rover and base.
- If the base observations are in a Rinex file, the approximate base position in the header must be valid and in XYZ coordinates. (This is a temporary restriction until I improve the code)
- Config values are optional and should be copied by line directly from the config file into the body of the email, one to a line (e.g. pos1-posmode = static, see more examples below)
If you’ve done everything right (and everything on my end is working properly), about five minutes after you have sent the email, you should receive a response with observation and solution plots and attached solution and config files. Here is an example response I received after sending in one of the M8T data sets from a recent post.
To specify a configuration different from the default, you can add any valid line from an RTKLIB config file to the body of the email. Here are a few sample configuration options. Copy any combination of these to the body of the email (don’t include the bold titles, only the text after the colon)
Static solution: pos1-posmode =kinematic
L1/L2 solution: pos1-frequency =l1+l2
Combined solution: pos1-soltype =combined
Elevation mask: pos1-elmask =10 # (deg)
Satellite types: pos1-navsys =15 # (1:gps+2:sbas+4:glo+8:gal+16:qzs+32:beidou)
Ambiguity resolution: pos2-armode =continuous
GLONASS ambiguity: pos2-gloarmode =on
Output format: out-solformat =llh
Base station ant type: ant2-anttype =ASH700936E