Internal gps — pushed data, Masked gps — pulled – Juniper Systems LandMark CE User Manual
Page 71
LandMark CE User’s Manual 71
LMCE_API BOOL GetInternalGPS
Argument for Function
Function Affected
(DWORD &tic,
Unique ID
double &r_lat,
Latitude in Decimal Degree
double &r_lon,
Longitude in Decimal Degree
double &r_alt,
Elevation in meters
double &r_pdop,
GPS data
double &r_ehe,
GPS error in meters
int &quality);
2D, 3D, etc.
Internal GPS — Pushed Data
The only difference in this function compared to pulling data, is in
the protocol. Once the third part has called for data, the function
blocks the calling thread/process until LandMark CE signals when
new data are processed. There is not a three second delay after this
function is called, but the function listens for a QUIT from LandMark
CE to tell the third party program that the data are ready.
LMCE_API BOOL GetInternalGPSRT
Argument for Function
Function Affected
(DWORD &tic,
Unique ID
double &r_lat,
Latitude in Decimal Degree
double &r_lon,
Longitude in Decimal Degree
double &r_alt,
Elevation in meters
double &r_pdop,
GPS data
double &r_ehe
GPS error in meters
int &quality);
2D, 3D, etc.
Masked GPS — Pulled
The Masked GPS functions give more formatting options to the third
party application. The Get Mask GPS fi lters the GPS data according
to the preferences set in Landmark CE (refer to the Confi guration
section of LandMark CE). The protocol is the same as the Pulled
internal GPS function.
Check the GPS data (“mask_msg” argument) to see if it is masked
before using the data being received. The mask values are described
after the function defi nition.
▲
▲