Any plans for JPOS to handle kinematic/trajectory data?

JVan

Member
Does anybody know if there are plans to make DPOS capable of kinematic data processing? I can convert the log file to Rinex and use the Canadian PPP service, but that is extra hassle.
 

Alexey Razumovsky

Well-Known Member
JAVAD GNSS
5PLS
Does anybody know if there are plans to make DPOS capable of kinematic data processing? I can convert the log file to Rinex and use the Canadian PPP service, but that is extra hassle.
Does not matter for DPOS rather static or kinematic data to process. I posted some months ago a question about a report style for kinematic or Stop@Go. Nobody answered.
 

Shawn Billings

Shawn Billings
5PLS
I apologize. I never saw this question, Alexey.

For me, the desired format of a stop and go report would be two parts:

First Part:
  • CORS used and coordinates of those CORS stations (along with reference frame of those coordinates).
  • Number of Points in Stop and Go File/ Number of Points Fixed
  • Start Time, Date of File/Stop Time, Date of File
Second Part:
  • ASCII output, Defined by User
The ASCII output would be similar to J-Field's ASCII output options with options for:
Point Name
Point Description
Northing
Latitude
Easting
Longitude
Elevation (Ortho)
Ellipsoid Height
Number of Satellites by Constellation
Number of Epochs
Time Start
Fixed/Float/Standalone
HRMS
VRMS
DOP
Vectors (from CORS to Point)
Antenna Height/Measurement Type

For Trajectories this would not need so many options. Perhaps report the first part from above along with a DXF of the points in the trajectory, and an ASCII File for each node with the following:

Trajectory Name, Node Number in Trajectory, Latitude, Longitude, Northing, Easting, Elevation (Ortho), Ellipsoid Height, Fix/Float/Standalone, HRMS, VRMS, DOP, Antenna Height/Measurement Type.

Perhaps others can provide better ideas.

Thanks, Alexey.
 

Alexey Razumovsky

Well-Known Member
JAVAD GNSS
5PLS
I apologize. I never saw this question, Alexey.

For me, the desired format of a stop and go report would be two parts:

First Part:
  • CORS used and coordinates of those CORS stations (along with reference frame of those coordinates).
  • Number of Points in Stop and Go File/ Number of Points Fixed
  • Start Time, Date of File/Stop Time, Date of File
Second Part:
  • ASCII output, Defined by User
The ASCII output would be similar to J-Field's ASCII output options with options for:
Point Name
Point Description
Northing
Latitude
Easting
Longitude
Elevation (Ortho)
Ellipsoid Height
Number of Satellites by Constellation
Number of Epochs
Time Start
Fixed/Float/Standalone
HRMS
VRMS
DOP
Vectors (from CORS to Point)
Antenna Height/Measurement Type

For Trajectories this would not need so many options. Perhaps report the first part from above along with a DXF of the points in the trajectory, and an ASCII File for each node with the following:

Trajectory Name, Node Number in Trajectory, Latitude, Longitude, Northing, Easting, Elevation (Ortho), Ellipsoid Height, Fix/Float/Standalone, HRMS, VRMS, DOP, Antenna Height/Measurement Type.

Perhaps others can provide better ideas.

Thanks, Alexey.
So we have first iteration.
 

Shawn Billings

Shawn Billings
5PLS
Alexey,
Do you think at some time in the future, DPOS could accept a stationary static file, process this file with CORS, then process a stop and go file with the stationary file? In this way, the base for the stop and go is near to the stop and go rover receiver? Would this help achieve better results than processing directly from CORS to stop and go rover receiver?
 

Alexey Razumovsky

Well-Known Member
JAVAD GNSS
5PLS
Shawn, some time before DPOS lanching we have tested cloud service for Justin projects processing. One can configure a project (antennas, reference points and so on) with free Justin Link software. Really, it's a complicated operation. Justin Link successfully generates true project fully compatible with Justin and itself sent a project to DPOS. In this case we do not need CORS at all and get practically instant solution (on-the-fly). Unfortunatelly, it had no progress.
 
Top