AUSPOS - Online GPS Processing Service
Page last updated:27 October 2026
AUSPOS is an openly available online GPS data processing service provided by Geoscience Australia. It takes advantage of both the International GNSS Service (IGS) Stations Network and the IGS product range, as well as the Asia-Pacific Reference Frame Network (APREF) station data and coordinate solutions. AUSPOS works with data collected anywhere on Earth.
You can submit dual-frequency geodetic quality GPS RINEX data observed in a 'static' mode to AUSPOS, and an AUSPOS report will be emailed to you with the Geocentric Datum of Australia 2020 (GDA2020), Geocentric Datum of Australia 1994 (GDA94) and International Terrestrial Reference Frame (ITRF) coordinates.
AUSPOS Submission checklist
Before submitting your GPS RINEX file/s, please note:
- AUSPOS provides a network solution (relative positioning) using a double-difference strategy.
AUSPOS does not use the Precise Point Positioning (PPP) computation strategy.
Dual-frequency measurements from GPS L1 and L2 signals are required. Measurements from all other GNSS constellations, including Galileo (E). Beidou (C), GLONASS (R), QZSS (J), are ignored during processing. - Ensure each RINEX file submitted contains at least one hour of observations. Centimetre level position estimates are more likely to be achieved with 6+ hours of static observations.
- Ensure all RINEX files submitted in the same job contain an overlapping period of more than one hour. Otherwise, submit files individually as different jobs.
- DO NOT submit measurements for the current UTC day. Please wait until the next UTC day after 0300 (3 am) UTC time. This allows the RINEX files of reference stations to be downloaded for the current UTC day.
- DO NOT submit receiver raw binary files (for example files with extension: M00, T01, T02, DAT, SBF, TPS...).
- ONLY submit RINEX observation "O" files. DO NOT submit RINEX files with extensions: "N", "M", "G", "L", "P", "H".
- RINEX filenames should NOT contain any special characters, symbols or spaces (e.g. " * ", " _ ", " - ").
- The station name will be read from the first 4 letters of the "MARKER NAME" line in the RINEX header. An example RINEX header is below.

- Ensure the interval (INTEGER only) of measurements is equal to or bigger than ONE second. It is better to have all RINEX files with the same interval. AUSPOS will sample all RINEX files to 30 second intervals.
- DO NOT use special characters for "MARKER NAME" and "MARKER NUMBER" in the RINEX header. ONLY use numbers and/or letters from the modern English Alphabet.
- After the "END OF HEADER" line in the RINEX header, only observation data should be present (Epoch time and Measurements). Please check before submission.
- AUSPOS uses a priority list for the observations included in the RINEX file. This priority list translates to the below:
For RINEX version 2:
L1 frequency carrier phase: L1
L2 frequency carrier phase: L2
L1 frequency pseudo-range: P1 C1
L2 frequency pseudo-range: P2 C2
For RINEX version 3 and version 4:
L1 frequency carrier phase: L1W L1C L1X L1L
L2 frequency carrier phase: L2W L2C L2D L2P L2X L2S L2L
L1 frequency pseudo-range: C1W C1C C1X C1L
L2 frequency pseudo-range: C2W C2C C2D C2P C2X C2S C2L - For a RINEX v2 file, if BOTH C1 and P1 (C2 and P2) code measurements exist, P1 (P2) is given priority to be processed. In this case, please ensure all GPS satellites contain P1 (P2) measurements.
- For a RINEX v2 file, if only C1 (C2) code measurements exist, please ensure all GPS satellites contain C1 (C2) measurements.
- For RINEX v3 (and v4) files, the accepted measurements from L1 frequency are currently C1L and L1L; C1W and L1W; C1C and L1C; and C1X and L1X.
- For RINEX v3 (and v4) files, the accepted measurements from L2 frequency are currently C2P and L2P; C2W and L2W; C2C and L2C; C2D and L2D; C2X and L2X; C2L and L2L; and C2S and L2S.
- If RINEX files are Hatanaka compressed, please use the lower case "d" for the filename extension.
For each RINEX file, please ensure that there is at least one observation type for each of the two frequencies and for both carrier-phase and pseudo-range measurements.
AUSPOS submission
Frequently asked questions
Question 1.1 - What is AUSPOS - Online GPS Processing Service?
- AUSPOS is a free online GPS data processing service provided by Geoscience Australia
- AUSPOS takes advantage of both the IGS Stations Network and the IGS product range, and works with data collected anywhere on Earth
- Users submit their dual frequency geodetic quality GPS RINEX data observed in a 'static' mode to the AUSPOS GPS data processing system
- An AUSPOS report will be emailed to you (typically in less than ten minutes) containing Geocentric Datum of Australia 2020 (GDA2020), 1994 (GDA94) and International Terrestrial Reference Frame (ITRF) coordinates
Question 1.2 - Who can benefit from the service?
The service aims to assist a variety of users from the private and public sector who require coordinates in the Australian Datum (Geocentric Datum of Australia 1994/2020) and/or International Terrestrial Reference Frame (ITRF) coordinates. This includes people undertaking surveys such as:
- Reference station positioning
- Remote GPS station positioning
- Ultra-long GPS baseline positioning
- GPS connections to IGS and ARGN and APREF stations
- High accuracy vertical GPS positioning
- GPS network quality control
Question 1.3 - What do I need?
All you need to submit your data and receive your report is:
- Geodetic quality dual frequency GPS receiver observation data in RINEX format
- Access to a web browser with an Internet connection
- An email account
All the GPS data processing occurs in the AUSPOS GPS data processing server, so the type and capability of your computer is NOT important.
Question 1.4 - What do I submit?
- GPS RINEX observation data (navigation data is NOT required);
- the GPS antenna type;
- the GPS antenna height; and
- your email address.
The GPS antenna type and height can be either provided by the user or extracted from the RINEX file header using the “Scan” button once the RINEX file is uploaded. If scanning the RINEX file, ensure this information is correct in the header of the file.
Question 1.5 - How do I get the results?
The results are emailed to you when the processing is complete. Hyperlinks are also provided to download the reports and relevant result files. If you are having trouble accessing either of these, please contact us at ClientServices@ga.gov.au [with AUSPOS in the subject line].
Question 1.6 - How fast is it?
This depends on how much data you have submitted. A single site with one day of data should be completed within about ten minutes. A multiple site solution might take up to and over twenty minutes. The processing times depend upon system load.
Question 1.7 - How much does this service cost?
There is no cost.
Question 1.8 - What happens to my RINEX files?
AUSPOS will retain your RINEX files for seven days only and will then discard the data.
AUSPOS will NOT retain a copy of your data set beyond 7 days or release any submitted data sets to anyone.
Question 1.9 - Does AUSPOS process real time or kinematic data?
The service does NOT process real time, kinematic, or single frequency GPS data.
Question 1.10 - Does AUSPOS process GLONASS or Galileo data?
The service does NOT process non-GPS data, however; if GNSS data is in the RINEX file it will just be ignored.
Question 1.11 - Why do we make the service free?
AUSPOS provides the service freely to encourage consistency of all precise coordinates used by the GPS community. By making the service free, the Australian GPS community can better compete for contracts throughout the world. Feedback from Australian private sector survey firms show positive support for the service. They are competing internationally for contracts using the AUSPOS service as an important selling point. Effectively, every small survey/GPS organisation in Australia now has access to a very sophisticated GPS data processing system.
Question 2.1 - How does AUSPOS work?
All computations are undertaken using the Bernese Software. Bernese is a high precision orbit and geodetic parameter determination software . For more information see Bernese GNSS Software.
The International GNSS Service (IGS) product range is used in the computation process. Precise orbit parameters, Earth orientation parameters and coordinate solution IGS products are used.
NOTE: The IGS final orbit product is not available until approximately two weeks after the observation day. The rapid orbit product is available two days after observation, and is used if the IGS final orbit product is unavailable. If both the final and rapid orbit products are unavailable, then the IGS ultra-rapid orbit product will be used.
Once a user has submitted a RINEX file, the nearest 15 IGS and APREF stations are used as the reference stations for the processing. That data is retrieved from Geoscience Australia's GNSS Data Archive. A precise solution using a 'double difference' technique is then computed using these stations. The coordinates of the IGS stations are constrained with uncertainties of 1 mm for horizontal and 2 mm for the vertical.
Question 2.2 - How are observational errors accounted for?
The effects of observation error sources, such as receiver clocks, troposphere and ionosphere are taken into account, either through modelling, or estimation of related parameters. All the computations are undertaken according to the International Earth Rotation and Reference Systems Service (IERS) conventions.
A summary of the computation standards are provided as an appendix to all processing reports.
Question 2.3 - Does AUSPOS work with data collected anywhere on Earth?
Yes, AUSPOS is designed to work anywhere on Earth because the IGS Stations Network has global coverage. We download all IGS core station data and the APREF station data as soon as they are available in the Geoscience Australia GNSS data archive.
Question 3.1 – When was AUSPOS upgraded from version 3.0 to version 3.1, and why was this update made?
AUSPOS was upgraded to version 3.1 on 20/10/2026. The key change from version 3.0 was upgrading the underlying Bernese software from version 5.2 to version 5.4. This update was necessary because Bernese v5.2 is no longer supported.
Question 3.2 – Should I expect the same GDA2020 coordinates from AUSPOS v3.1 as from AUSPOS v3.0? Why might my GDA2020 coordinates for the same site differ between versions, and which coordinates should I use?
AUSPOS v3.1 uses Bernese v5.4, which includes several modelling improvements over the Bernese v5.2 implementation used in AUSPOS v3.0. These include the more recent FES2014b ocean tidal loading model; GPT3 and GMT3 troposphere models; Desai and Sibois (2016) high-frequency (sub-daily) polar motion model; antenna alignment to true north for reference sites; daily observation-specific signal biases; global ionosphere models; and the 7-parameter dynamic orbit model (ECOM2) for orbit integration.
Because of these changes, coordinates estimated by AUSPOS v3.1 are expected to differ from those estimated by AUSPOS v3.0. We have carried out extensive assessments to confirm that the coordinates estimated by AUSPOS v3.1 are as consistent as possible with the coordinates estimated by AUSPOS v3.0. We have confirmed that for most solutions, users should expect only small coordinate differences that fall within the 95% confidence-level positional uncertainties and are therefore statistically insignificant. However, in a small percentage of jobs, differences may exceed the reported uncertainty levels. This is mainly due to how Bernese v5.4 handles observation quality checking and outlier removal, which can remove more poor-quality observations before coordinate estimation.
In an analysis of about 2300 AUSPOS jobs submitted to the National GNSS Campaign Archive for data collected at 2468 survey marks and processed using both AUSPOS v3.0 and v3.1, more than 92% of jobs had coordinate differences smaller than their reported uncertainties. Among jobs with uncertainties below 1 cm for horizontal components and 2 cm for height, only 3% had coordinate differences greater than their uncertainties.
In a separate analysis of jobs submitted through the AUSPOS webpage, nearly 80% of jobs for sites within the GDA2020 boundaries produced coordinate differences smaller than the reported uncertainties. This increased to about 87% when considering only jobs with uncertainties below 1 cm for horizontal components and 2 cm for the vertical component.
Although exceptions can occur, coordinates are generally consistent for jobs based on high-quality data, such as long, continuous observation sessions collected under open-sky conditions.
When comparing coordinates from AUSPOS v3.0 and AUSPOS v3.1, users should consider the positional uncertainty of each AUSPOS solution at the 95% confidence level. GA recommends treating AUSPOS v3.1 solutions as preferable to the solutions that may have been previously processed by AUSPOS v3.0 because v3.1 uses the latest software and more advanced modelling. Where a user-submitted site has large reported coordinate uncertainties, nominally greater than 15 cm, the estimated coordinates should be used with extreme caution because they may not be reliable.
Question 3.3 – What was the previous version of AUSPOS, and what was the outcome of the previous upgrade?
AUSPOS was upgraded from version 2.4 to version 3.0 on 13/08/2024. Moving to AUSPOS v3.0 was an essential upgrade that aligns the AUSPOS coordinates to the most recent International Terrestrial Reference Frame (ITRF2020) and its IGS realisation (IGS20/igs20.atx). AUSPOS v3.0 and beyond use the most reliable and most up to date IGS20 products. IGS14 products (used by AUSPOS v2.4 – aligned to ITRF2014), are no longer maintained by the IGS.
As with the upgrade to version 3.1, we carried out extensive assessments to confirm that the GDA2020 coordinates from AUSPOS v3.0 were largely consistent with the coordinates from AUSPOS v2.4. The results of this analysis were published in a scientific paper in GPS Solutions. The manuscript covers details about how AUSPOS works, how v3.0 was different to v2.4, and how we verified that consistent GDA2020 coordinates would be produced by v3.0 (when compared to v2.4). A similar approach was used to assess the upgrade from v3.0 to v3.1 and ensure consistent GDA2020 coordinates are maintained.
Question 4.1 - What is a RINEX file?
RINEX is the Receiver Independent Exchange Format and is designed for easy exchange of the GNSS data. See https://files.igs.org/pub/data/format/ for format descriptions of different RINEX versions.
Question 4.2 - What type of RINEX data is accepted and useful for processing in AUSPOS?
Only RINEX Observation data files are accepted by AUSPOS, as they contain GNSS observation data that are useful for coordinate estimation. RINEX Navigation message files and Metrological data files are not accepted by AUSPOS.
Question 4.3 - What information does a RINEX observation file contain?
The most important information contained in the RINEX observation files are carrier-phase and pseudorange (code) measurements between the receiver and the GNSS satellites along with observation times. This information is processed by AUSPOS to obtain the coordinates of the site where the receiver collected data. In addition to this data, the header of the RINEX files contain information such as the RINEX file version, the antenna type and height, and the receiver type.
Question 4.4 - Why are there multiple RINEX versions?
The International GNSS Service (IGS) regularly issues new versions of the RINEX file to keep up to the speed of the needs of the GNSS community, especially as new GNSS satellites and signals are introduced. As a result, while the fundamental format of the RINEX files generally remains unchanged, there are differences between the different versions that need to be accounted for.
Question 4.5 - What RINEX versions can AUSPOS process?
AUSPOS can process RINEX observation file with V2, V3, and V4 formats.
Question 4.6 - What is different between RINEX 2, RINEX 3 and RINEX 4 observation files that may impact my use of AUSPOS?
A major difference between the RINEX 2 and RINEX 3 observation files is the length of the observation codes. While the observation codes in RINEX version 2 are two characters (e.g. L1, C1, P1), the RINEX version 3 (and version 4) use three-character observation codes to account for the different possibilities of how a specific observable was generated. See item 12 in the submission checklist. RINEX version 4 observation file has only minor differences compared to the RINEX version 3 observation file and does not impact the use of AUSPOS.
Question 4.7 - What are examples of a RINEX 2 and RINEX 3 (4) files?
Below are examples of a RINEX v2.11 and RINEX v3.05 header and beginning of the observation records:


Question 5.1 - How do I read the processing report?
The processing report is provided in Adobe PDF format.
Question 5.2 - What parts of the report should I check carefully?
It is recommended that you read the whole report thoroughly to familiarise yourself with the AUSPOS process. The important quality statistics related to your processing job are located in Sections 3-5 of the AUSPOS Report. This includes information such as the Coordinate Precision and Ambiguity Resolution.
Question 5.3 - What are the 'Derived AHD' and 'Derived Above Geoid' heights?
In the GDA section of the AUSPOS report, the user is supplied with a 'Derived AHD' height. This is a height computed using AUSGeoid2020 model. The offset between the ellipsoid and AHD is computed using Geoscience Australia's AUSGeoid2020 product and subtracted from the ellipsoidal height providing the user with a Derived AHD height. The AUSGeoid2020 model of ellipsoid to AHD separation values only extends 33 km offshore. Between 33 km and 50 km offshore, the AUSGeoid2020 ellipsoid to AHD separation values are linearly blended with Gaussian weighting with the DTU15 Mean Sea Surface model. The closer to shore, the higher the weighting of AUSGeoid2020 values. From 50 km outwards, the model is only the DTU15 Mean Sea Surface model.
In the ITRF section of the AUSPOS report, the user is supplied with a 'Derived Above Geoid' height. This is a height relative to the Earth Geopotential Model 2008 (EGM2008).
Question 5.4 - The report provides GDA and ITRF coordinates, but what about WGS84 coordinates?
ITRF and WGS84 are generally considered to be equivalent (to within 0.1 m).
Further information
Question 6.1 - Why do I have to specify the GPS antenna?
To achieve the highest quality processing results, attention needs to be paid to the type of antenna used. Using the incorrect antenna type can introduce significant bias (greater than 10 cm in the vertical component) and noise into the computed coordinates.
The actual observation point on a GPS antenna is called the electrical phase centre. The location of this phase centre is represented by a mean constant offset from the physical point on a GPS antenna, known as the Antenna Reference Point (ARP), and an additional variable offset that is dependent on the transmitting satellite's elevation.
The properties of the electrical phase centre are different for every type of antenna. Importantly, the electrical phase centre can be modelled provided you know the antenna type.
Question 6.2 - What is the antenna height?
The antenna height is the vertical distance from the ground mark to the Antenna Reference Point (ARP). The ARP is the physical point on a GPS antenna that measurements are typically reduced to. The ARP varies between antenna types. As a WARNING, the ARP is rarely the top of the Antenna Ground Plane. The ARP height should NOT be confused with slant and other instrument height measurements commonly used in GPS processing.
Question 6.3 - What type of GPS antenna do I have?
AUSPOS uses the IGS antenna naming convention. The IGS - Naming Convention Document provides more information.
Further information regarding the specifications of antennas can be found on the National Geodetic Survey (NGS) antenna calibration web site.
Question 6.4 - What happens if I choose the DEFAULT(NONE) antenna?
If you choose the DEFAULT(NONE) antenna type; no antenna phase centre model or offset is applied.
If you set the antenna height to 0.0000 m and choose an antenna type, then the position of the ARP is computed.