When you email a binary file, it is also converted to text prior to
transfer, and converted back to binary on the other end.

You are probably correct that the OLC programmers don't want to spend
additional effort on the non-standard and now obsolete CAI binary
format, especially since they have already spent considerable effort on
the current compromise solution. Since the relative number of GPS-NAV
loggers will keep declining, this is probably a wise allocation of
limited resources. They should focus their efforts on future growth
opportunities.

I don't think you are correct about the ease of implementing a binary
FTP transfer. But, if you want to volunteer to implement this, and
prove me wrong, I can put you in touch with the right people.

jcarlyle wrote:
Doug,

I'm not a web expert, but this assertion seems incorrect. Certainly you
can e-mail a binary cai file and it will still be valid upon receipt.
It can also be sent via FTP, and I guarantee that this process would
result in a valid binary file. And a FTP transfer could be easily built
into the OLC submission process if OLC chose to do so.

Sounds to me like OLC programmers simply don't want to go to the effort
of figuring out how to handle cai files, and so are putting what should
be their problem on all of us Cambridge users.

-John

Doug Haluza wrote:
Actually, it is not possible for OLC to process the CAI binary because
it cannot be uploaded via the web form. The HTTP transfer used to
upload the IGC files will not accept the non ANSI characters in the
Cambridge CAI binary file. This is why the binary data needs to be
converted and appended to the IGC file as text.