summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
43f94e9)
GPS altitude is generally more absolutely correct than baro altitude,
so use that as the nominal pad altitude when generating a KML
file. This results in a KML file that has the flight trace start and
end closer to the ground, which is always nice.
Signed-off-by: Keith Packard <keithp@keithp.com>
PrintStream out;
int state = -1;
AltosRecord prev = null;
PrintStream out;
int state = -1;
AltosRecord prev = null;
+ double gps_start_altitude;
static final String[] kml_state_colors = {
"FF000000",
static final String[] kml_state_colors = {
"FF000000",
AltosGPS gps = record.gps;
out.printf(kml_coord_fmt,
gps.lon, gps.lat,
AltosGPS gps = record.gps;
out.printf(kml_coord_fmt,
gps.lon, gps.lat,
- record.altitude(), (double) gps.alt,
+ record.height() + gps_start_altitude, (double) gps.alt,
record.time, gps.nsat);
}
record.time, gps.nsat);
}
if (!started) {
start(record);
started = true;
if (!started) {
start(record);
started = true;
+ gps_start_altitude = gps.alt;
- if (prev != null &&
- prev.gps.second == record.gps.second &&
- prev.gps.minute == record.gps.minute &&
- prev.gps.hour == record.gps.hour)
+ if (prev != null && prev.gps_sequence == record.gps_sequence)
return;
if (record.state != state) {
state = record.state;
return;
if (record.state != state) {
state = record.state;