DPOS Archive

[Kelly Bellis]

Accessing DPOS reports from the
JAVAD Customer Area
using the interface available through https://app.javad.com/jca/#/dpos/report/direct/
works in retrieving those DPOS reports, but only for a short time (of unknown length) after the initial uploading and processing of the base files, but let's say, for example, you want to reprocess the older base files using the precise orbital data.

Presently, in order to reprocess them, the user has to upload the base files again in order to reprocess them; for example:

Consider this idea:
1) Save DPOS Reports (*.pdf) under folder ..\user\dpos\archive\report\process_date\pdf\
2) Save Justin Reports (*.jpr) under folder ..\user\dpos\archive\report\process_date\jpr\
3) Save base station files (*.jps) under folder ..\user\dpos\archive\jps\
4) Allow saved .jps files to be processed again

 

[Kelly Bellis]

Well, after uploading the seven files and over an hour, this:

 

[Kelly Bellis]

For unknown reasons, the DPOS system considered these (7) .jps files as being continuous, which they were not:

 

[Alexey Razumovsky]

DPOS answered: Session period exceeds 2 continuous days. Is it correct? Certainly!

 

[Kelly Bellis]

Hi Alexey,

Thank you for the reply. I think the notice just needs to read differently. Continuous means uninterrupted. My files were not continuous.

 

[Kelly Bellis]

Not only were the files not continuous, they weren't on consecutive days. The last session on the 20th of November was interrupted when I had to move the setup in order to let a big flatbed trailer vacate the premises.

 

[Kelly Bellis]

Funny story
All of this work only to see that DPOS isn't using the precise ephemeris; still using broadcast!

Just out of curiosity, why isn't the precise ephemeris being used?

 

[Alexey Razumovsky]

View attachment 7248
Not only were the files not continuous, they weren't on consecutive days. The last session on the 20th of November was interrupted when I had to move the setup in order to let a big flatbed trailer vacate the premises.

Hi Kelly, I realise that your files aren’t continuous. In the meantime DPOS session surely exceeds 2 continuous days.

 

[Alexey Razumovsky]

Funny story
All of this work only to see that DPOS isn't using the precise ephemeris; still using broadcast!

Just out of curiosity, why isn't the precise ephemeris being used?

My point is that precise ephemeris does not bring a benefit for post processing with CORS. Typical range is under 100 miles.

 

[Kelly Bellis]

My point is that precise ephemeris does not bring a benefit for post processing with CORS. Typical range is under 100 miles.

Do you mean that the CORS would need to be over 100 miles apart in order to see any benefit from precise orbital data?
And, how is benefit quantified; e.g., >1cm or <1cm

 

[Alexey Razumovsky]

Do you mean that the CORS would need to be over 100 miles apart in order to see any benefit from precise orbital data?
And, how is benefit quantified; e.g., >1cm or <1cm

I expect it less then 0.001 meter.

 

[Matt Johnson]

Just out of curiosity, why isn't the precise ephemeris being used?

Also we have found the precise ephemeris for GLONASS satellites to be unreliable and it will occasionally produce bad results.

 

[Kelly Bellis]

Also we have found the precise ephemeris for GLONASS satellites to be unreliable and it will occasionally produce bad results.

Would that be true regardless of Justin or Giodis as the computational engine?

 

[Matt Johnson]

I believe so but I encountered problems with it while using Justin in the past.