JAVAD Data Collector (JDC)

Nate The Surveyor

Nate The Surveyor

Well-Known Member
Thank you John. Does this mean that this new data collector, will be able to be used with the LS, and LS+?
Curious minds need to know..... :)
Nate
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
JAVAD GNSS
The new data does not work with the LS or LS+. The LS and LS+ have built in data collectors so why would you want to add another external data collector?
 
John Rosco

John Rosco

Active Member
JAVAD GNSS
Nate The Surveyor said:
Thank you John. Does this mean that this new data collector, will be able to be used with the LS, and LS+?
Curious minds need to know..... :)
Nate
Click to expand...
Hello Nate, the Javad Data Collector (like to original Javad Mobile Tools) application is only to be used with the Javad Smart Antenna units (T-1M+, T-3NR, or T-3) . . .
JDC is a simple 'survey point data collection' utility.
 
John Rosco

John Rosco

Active Member
JAVAD GNSS
JDC v1.0.8 Available Now- see https://www.javad.com/product/javad-data-collector/

Release Notes
  • Datasheet
    Datasheet
    Download
  • User Manual
    User Manual
    Download
 
JAVAD Support

JAVAD Support

Active Member
Staff member
5PLS
JAVAD GNSS
Project Coordinate System and Geoid selection in JDC.

The Coordinate System field allows the user to select the preferred coordinate system for the job.
The search bar can be used to find the coordinate system for use. Start typing the state, region, county or zone to auto-display these filtered coordinate systems.
For example, typing “California” will display the filtered results for California coordinate systems as shown in the figure below. The search results are scrollable.
Click on the required coordinate system to select it for the survey project.

1762967122047.png

The Geoid field allows the user to select the preferred vertical reference system for the job.
The search bar can be used to find the preferred Geoid for use.
For example, in the USA, type “NAVD88” to display the available vertical reference systems for NAVD88 as shown below.
Then select "NAVD88 Height (ftUS)

1762967211917.png
Note: EPSG:6360 NAVD88 height (ftUS) is GEIOD18 (Conus) orthometric height elevation model that is valid for North America and SPCS

For reference see - https://www.ngs.noaa.gov/GEOID/GEOID18/#:~:text=Hybrid geoid models are used to convert NAD83
 
Last edited:
John Rosco

John Rosco

Active Member
JAVAD GNSS
Since the JAVAD Data Collector (JDC) Android application is designed for easy setup and operation for repeatable connection and configuration of JAVAD Smart Antennas, to obtain reliable and accurate GNSS observations requires the use of an accurate a reliable RTK RTCM3.2 correction service to the GNSS 'rover'.

Using JDC and an internet connection, RTK RTCM3.2 corrections can be obtained from 'any' NTRIP 'base' Caster service or a JAVAD configured 'base' receiver.
- see https://support.javad.com/index.php?threads/ntrip-caster.6260/#post-56467
 
avoidthelloyd

avoidthelloyd

Active Member
After spending many hours in JDC out in the field, while they are working on JDC, why not go ahead and make some significant improvements (if you will not make J-Field available on mobile devices):
  • The export format needs more options. Text and CSV are okay, but the data fields are still not importable into cad without manual formatting. This is unacceptable.
    • The point name field should NEVER be prefixed with “Point_”
    • The number should NEVER have preceding 000’s
    • Simple 1, 2, 3,… C1, C2…
    • It should have the option to turn off the header in the export - we want direct to CAD export options
  • We need to be able to sort the point numbers by time and search them for descriptions
  • We need to be able to change the coordinate system and datum in the project settings
  • We need to be able to change the raw data of points, like rod heights, etc.
  • We need better background maps (aerials)
  • We LOVE our J-Field 4-engine status screen and signal programming!
  • The exported data MUST match the screen data
  • For the DESCRIPTION, the most recent one should be defaulted in the field.
    • ALSO a RECENT LIST of the last 8 or so should be available without retyping the ENTIRE thing again. This made work so slow!
  • Guys, y’all have SPOILED us with DPOS! We must have this ability on JDC.
  • RTPK?
I know it's marketed as SIMPLE... well, it's TOO simple for a land surveyor right now. HELP!

Is there ANY way to get a mobile version of J-Field????????? Please?????????
 
JAVAD Support

JAVAD Support

Active Member
Staff member
5PLS
JAVAD GNSS
avoidthelloyd said:
  • Guys, y’all have SPOILED us with DPOS! We must have this ability on JDC.
Click to expand...
JDC simply collects and records Coordinate System measurements and does not save (in the Android memory) RAW .jps data.
To be able to post-process .jps data, the user needs to enable internal log-file recording in the Javad GNSS receiver internal memory.
Then 'download' the .jps data log-file from the Javad GNSS receiver internal memory to post-process via DPOS or OPUS etc...
 
John Rosco

John Rosco

Active Member
JAVAD GNSS
JAVAD Support said:
JDC simply collects and records Coordinate System measurements and does not save (in the Android memory) RAW .jps data.
To be able to post-process .jps data, the user needs to enable internal log-file recording in the Javad GNSS receiver internal memory.
Then 'download' the .jps data log-file from the Javad GNSS receiver internal memory to post-process via DPOS or OPUS etc...
Click to expand...
JDC simply collects ‘base/rover’ RTK measurement solutions in the define coordinate system (NEU)

If the user needs to post-process any ‘rover’ .jps log-files, they need to:-
  1. Have JDC configure the ‘rover’ to record .jps "Rover Standalone" data to the receiver’s internal memory (for a shot);
  2. Then after the survey session, use NetView to download the .jps data-log-file to the users local computer;
  3. Then submit the .jps log-file to DPOS to be post processed via JCA or convert to RINEX for OPUS or CSRS etc... post-processing.
Note: Of course the ‘rover’ log-file session needs to be recorded for many minutes as the DPOS processing will not be relative to any static-base data . . .
 
You must log in or register to reply here.
Top