AUSPOS - Trouble Shooting
- Question 6.1 - What if something goes wrong?
- Question 6.2 - I hit the submit button after mistyping my email address?
- Question 6.3 - What are the limits to how much data I can submit?
- Question 6.4 - Is my data too old?
- Question 6.5 - What do I do if the processing terminates?
- Question 6.6 - The processing system doesn't seem to be working?
- Question 6.7 - After submitting, I just get a blank page?
- Question 6.8 - AUSPOS Error - What should I do?
- Question 6.9 - AUSPOS Error - RINEX file does not conform to RINEX format standard?
- Question 6.10 - AUSPOS Error - RINEX file name or path contains spaces
- Question 6.11 - AUSPOS Error - Not L1 or L2 data?
- Question 6.12 - AUSPOS Error - The requested processing date span is too long?
- Question 6.13 - AUSPOS Error - No IGS data available?
- Question 6.14 - AUSPOS Error - Submitted data has not been observed on consecutive days?
- Question 6.15 - AUSPOS Error - Site has data on the same day (UT) in more than one RINEX file?
- Question 6.16 - AUSPOS Error - Submitted near real time data
- Question 6.17 - AUSPOS Error - AUSPOS has detected an error while trying to create the processing report. It appears AUSPOS was unable to calculate a solution for one of your submitted file(s).
If you receive an error and can’t resolve it using the error message or information in the FAQ’s, please contact us on firstname.lastname@example.org.
That's OK - take note of your job number, and after a few minutes, have a look in ftp://ftp.ga.gov.au/geodesy-outgoing/apps/auspos/#####.pdf (where ##### = your job number) - your processing report is also copied here.
Up to seven RINEX files can be submitted simultaneously. Each submitted RINEX file can contain up to seven days of data. A user can make as many submissions as they want.
If you submit multiple sites together then they must be in the same approximate part of the world (closer than 5000km).
We are currently only processing data that has been observed after the 1st of January 1998.
The AUSPOS software will stop the processing job under the following circumstances:
- A RINEX file fails the format check process
- More than seven days of data are submitted in the one processing job
- The first four characters / numbers from the submitted files are the same
- More than one RINEX file is submitted in the same job and the sites are greater than 5000km apart
Please read the error message carefully and try to fix the problem yourself. If that fails, please email us at email@example.com. If you notify us of a problem, please quote the job number.
As with all technology from time to time there may be problems. Also, occasionally we need to undertake maintenance on our system. If you think our system is down (we may not know), please feel free to let us know at firstname.lastname@example.org.
Sometimes after a user submits their data files, a blank window opens and nothing seems to happen. This normally isn’t a problem and after the data is uploaded to AUSPOS, the window starts sending useful information about the processing job back to the user. However, if the file is big and/or your Internet connection is slow, this can take a while.
First, try to solve the problem yourself using the AUSPOS FAQ’s. If you are not successful, you can email us at email@example.com
Sometimes RINEX files can be corrupted, or perhaps the software used to create the RINEX file is not working correctly. If your RINEX file isn’t valid, then a message will be emailed to you. The best way to fix these errors is to review your RINEX file (the line number is generally given in the error message).
You can always check your RINEX file against the RINEX Format Document .
Any space in your RINEX file name or path will cause AUSPOS to fail. Please rename your file, without spaces, and resubmit it.
One of the first checks AUSPOS makes is to see that the user file has both L1 and L2 carrier phase and code data. AUSPOS was designed to process only dual frequency data. A common user error is to accidentally submit the RINEX navigation file instead of the RINEX observation file.
AUSPOS will determine the start and the end of an observation session in all the submitted files. If the data span exceeds seven days, an error is generated and the user will be asked to break up their data set and resubmit in smaller batches. This feature was implemented to prevent massive processing jobs dominating the service.
For most IGS stations and the APREF network, data is not available until several hours after the end of the UT day. This means that there is the potential that data that has been collected in the last 24 hours will not be able to be processed. The best solution is to wait and try again later.
AUSPOS will process all the user data and the required IGS/APREF data between the start and end times. However, to prevent users from submitting data that has been observed at different times, a consecutive day test is applied, i.e. user data must have been observed on the same day or in a non-broken set of consecutive days. This test prevents any complications during the transformation of the coordinates to GDA94 by ensuring that any tectonic motion between the start and the end of the session is negligible.
AUSPOS uses the first four characters of the RINEX filename to set the site name. AUSPOS also combines the solution from multiple files/sites into a combined weighted mean solution. To protect users who name all their RINEX files the same, regardless of their location i.e. 'base100a.02o' and 'base100b.02o', a ‘same site on the same day’ test is applied. If the site is actually the same, then the RINEX files should be combined - if they are actually different - then one of the files should be renamed.
AUSPOS cannot process near real time data and it needs several hours after end of a UT day to allow reference data to become available.
Question 6.17 - AUSPOS Error - AUSPOS has detected an error while trying to create the processing report. It appears AUSPOS was unable to calculate a solution for one of your submitted file(s).
Code observations in one of your files contain too much noise to estimate the approximate coordinates for that site. If you have more than one file, you may submit them separately.
Topic contact: firstname.lastname@example.org Last updated: May 8, 2013