2.1 User Data Format Specification
wuulong edited this page Jul 4, 2015
·
1 revision
Follow data format specification to delivery the sensor data is very important for later on data processing.
The rule must be followed and invalid data will be filter out if it make problems.
V 0.1
Initial draft version
SensorData=[|FieldName=FieldValue]+
FieldValue=[FieldSubValue,]+
Sensors/SensorName
LASS-AnyNameYouPrefer
System will apply LASS prefix filter in the future. The wrong devices ID will not get service.
We use Grove sensor name as our rule, remove space. The detail list as below.
Refer http://www.seeedstudio.com/wiki/Grove_System
The definition will be different in different sensor.
Should have common rule, but it should be list the data format in each sensor definition.
Welcome to suggest new sensor format, or just use it. We will try to capture it in the data log and become new sensor format.
/* Refer to http://www.gpsinformation.org/dale/nmea.htm#GGA
* Sample data: $GPGGA,123519,4807.038,N,01131.000,E,1,08,0.9,545.4,M,46.9,M,,*47
* Where:
* GGA Global Positioning System Fix Data
* 123519 Fix taken at 12:35:19 UTC
* 4807.038,N Latitude 48 deg 07.038' N
* 01131.000,E Longitude 11 deg 31.000' E
* 1 Fix quality: 0 = invalid
* 1 = GPS fix (SPS)
* 2 = DGPS fix
* 3 = PPS fix
* 4 = Real Time Kinematic
* 5 = Float RTK
* 6 = estimated (dead reckoning) (2.3 feature)
* 7 = Manual input mode
* 8 = Simulation mode
* 08 Number of satellites being tracked
* 0.9 Horizontal dilution of position
* 545.4,M Altitude, Meters, above mean sea level
* 46.9,M Height of geoid (mean sea level) above WGS84
* ellipsoid
* (empty field) time in seconds since last DGPS update
* (empty field) DGPS station ID number
* *47 the checksum data, always begins with *
*/
#Example log Sensors/SoundSensor |device_id=LASD-example|time=20645|device=LinkItONE|values=0|gps=$GPGGA,235959.000,2448.0338,N,12059.5733,E,0,0,,160.1,M,15.0,M,,*4F