View Full Version : Splitting IGC file with multiple flights
Mike Schumann
August 20th 08, 01:15 AM
I have a single IGC file that has two flights on it (I landed, and the
flight recorder continued recording while I was on the ground and thru the
completion of my second flight).
Is there anyway to split this IGC file, so I have a separate file for each
flight? Having both flights is very confusing, both in See-You, as well as
in my OLC posting, as the route display shows both flights together.
Thanks,
--
Mike Schumann
** Posted from http://www.teranews.com **
noel.wade
August 20th 08, 04:05 AM
Mike -
When you upload an IGC file to the OLC, there's an option for "more
precise" start and end timing. Couldn't you just use that to move the
"start bar / start time" to the beginning of your second flight so
that only the second flight is counted for that OLC claim (I'd suggest
moving the "end bar / end time" of the first flight, but if you've
already claimed it I don't think you can change it).
Take care,
--Noel
ContestID67
August 20th 08, 06:54 AM
On Aug 20, 8:15*am, "Mike Schumann" <mike-nos...@traditions-
nospam.com> wrote:
> Is there anyway to split this IGC file, so I have a separate file for each flight? *
The short answer is "Yes" but it isn't particularly easy. I had the
same problem. There were three of us were flying together and it
looks cool in SeeYou to have all three flights playing at the same
time. The issue was one person had two flights in the file and I only
wanted the flight with me. I think it was a Volkslogger.
Anyway, you need to first make a copy of the original file. NEVER
touch the original file. NEVER rename the original file. Open the
copy with a text editor. Now comes the fun part which is figuring out
where to make the split. Scroll down until you find all the lines
that start with a B (B records). These have the following format.
Example: B0001053611636N11546579WA0361703530000
The first 6 characters follow the B are the UTC time in HHMMSS format,
so the UTC time is [000105], 00 hours, 01 minute, 05 seconds.
The next 8 characters represent the latitude [3611636N in your
example]
The next 9 characters the longitude [11546579W in your example]
1 character for fix valid flag, A valid, V warning [A - data valid
here]
next 5 characters represent the pressure altitude [03617 meters here]
next 5 characters the GPS altitude [03530 meters here]
Originally, the B record ended with a final 3 characters representing
"fix accuracy" field [000 here]. More recently, depending on the I
record, additional data may be appended, for example engine noise
level.
The simplest way I have found to figure out where to make the cut, is
to look at the altitude (the 5 characters after the A). When this
number stops changing (by more than a few meters) you are on the
ground and are "taxi-ing". Delete all the A records following this
point (assumes the first flight is the one to keep). Do not delete
anything but A records. Note that this file will fail a security test
and cannot be used for badges, records, etc. That is why you should
always keep the original file unchanged.
Good luck.
Mike Schumann
August 20th 08, 02:16 PM
I did that, but OLC still shows the trace for both flights combined, not
just the segment for each flight, which is very confusing. Neither of these
flights was very long, so the points don't matter to me. I mainly wanted to
record the flights on-line, so I could send a link to my passengers as a
memento of their 1st glider flights.
Mike Schumann
"noel.wade" > wrote in message
...
> Mike -
>
> When you upload an IGC file to the OLC, there's an option for "more
> precise" start and end timing. Couldn't you just use that to move the
> "start bar / start time" to the beginning of your second flight so
> that only the second flight is counted for that OLC claim (I'd suggest
> moving the "end bar / end time" of the first flight, but if you've
> already claimed it I don't think you can change it).
>
> Take care,
>
> --Noel
>
** Posted from http://www.teranews.com **
vBulletin® v3.6.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.