Search results

Hey Harold, share the files. I will try to help.

I found it. Tap 'Coord.Sys'.(2nd page of main screen) Tap '+' , 'North America', 'United States(USA), 2nd tab,'SPCS(NAD83 2011),3 tab, 'NAD83(2011) / Georgia West' . Return to 'Coord.Sys' page. Tap button on upper right corner. Tap 'Export'.

I recreated GA_West.jcs with Justin 3. New jcs contains geoid. It seems Justin Link is a bit obsolete. It uses old GeoData.

I did jcs with Justin Link. I am not confident where jcs should be in TLS. Maybe Shawn knows?

Hello Wes, The only way to make DPOS report in user defined CS is an import of suitable *.jcs file (app.javad.com >> GeoData >> Import). Before sending jps file check in a box "Private coordinate system". "NAD83(2011) / Georgia West" should appear in a drop down menu. J-Field and...

Hi Kelly, no way to update or edit URL in regular Justin. In the meantime we provide this opportunity in developer version.

Justin Lite is a discontinued product. No free software that can accept precise orbital data.

It's unlikely that DPOS functionality will be expended

DPOS processing server uses data uploaded on DPOS data repository - CORS observations and broadcast ephemeris. We don't plan to upload precise ephemeris.

Justin/DPOS engine uses 12 degrees cut off elevation mask. We found its the best setup.

Hi Kelly, latest and stable jps2rin is still available at http://www.javad.com/jgnss/products/software/jps2rin.html jps4rin is beta version suitable for RINEX v.4.x. In the meantime with --opus option it would convert to OPUS friendly RINEX.

PPP deals 3-4 cm (ITRF 2014) accuracy on 3-4 hours observation

The residuals on picture above show the same values as DPOS report. They are small. In the meantime both occupations at one point do not agree well. So an errors in postprocessing have systematic nature varying in time. Systematic impact (meteo, sat's constellation) can't be eliminated in...

It depends. Distance to CORS, PDOP and set of GNSS signals on the base side are main factors. I would recommend 1 minute per 1 km if GPS+GLO only.

I tied points 90055 and 90064 to 3 CORS manually in Justin. Every set of solutions pointed at separated receiver location (see picture below) Looks like you have moved receiver between sessions. In the meantime 90055 session is 13 minutes only. So you might neglect a solution for 90055.

Hi Ken, What was TL+ id number?

Hi Mark, DPOS provides an adjusted solution tied to multiple CORS. RTPK provides a solution tied to local base. So radially impact would be eliminated in DPOS after adjustment.

To check position radial dependency 2 CORS (MAWM, WES2) were used for post processing Local base is on the bottom. Points 1-6 are in the center of picture. Below are RTK and RTPK solutions. Purple dots are RTK epoch solution. Orange vectors are RTPK. RTK is a bit shifted towards North. I...

Mark, send us ~15 minutes static file if the case remains. It would help to investigate the issue.

Production DPOS is on