DPOS report returns "unknown error"

[oajioka]

I uploaded a .jps file to the DPOS web service and after processing the report shows only "unknown error".

We had the LS set up in a challenging location on a corner monument and left it there for most of the day as we continued to search for evidence. When we returned to the LS it had exited phase 1 and had 15 epochs in ~22,000 seconds with confidence 10.

Back at the office we ran the project through DPOS with "base-rover processing + base-cors processing + rover-cors processing" enabled. The point in question (#6000) did not receive a rover-cors solution.

We'd like to understand why we can't get a rover-cors solution for this point.

Below is a dropbox link to the project .zip

20200002_GPS2-200710 09_22_18.zip

Shared with Dropbox

www.dropbox.com

 

[Alexey Razumovsky]

This point has 1 epoch data intersection with nearest (>30 km away) CORS that provides 30 sec rate observations. For the case "Unknown error" means "No solution".

 

[oajioka]

Hi, thanks for the reply.

I took the .jps file for point #6000 and converted it to RINEX and uploaded to OPUS.

Here you can see that only 8% of observations are being used. Also the peak-to-peak errors are quite high.

Converting to anything other than RINEX 2.10 caused the OPUS upload to fail because the file size was too big. Any ideas on how to get around this?

 

[Alexey Razumovsky]

DPOS provides accurate solution for point 6000, isn’t it?

 

[oajioka]

Yes, the base-rover processed coordinate for #6000 looks okay.

The issue we are having is that we didn't get a verified shot on this point despite letting it sit there for several hours, and we would like to get some kind of independent check on it.

We thought it would be possible to get a rover-CORS solution for this point since it had a nice long duration.

Uploading our observable file to OPUS gave us a coordinate that is different by many feet, but it appears that the OPUS solution is not very accurate.

 

[Alexey Razumovsky]

I wouldn't recommend to occupy point in canopy more than 6 minutes. Best check is multiple occupation. Be aware that CORS provide 30 seconds data so there's no way to tie points like this to CORS.