What do you want in an electronic log book?

[indyz 1]

I'm doing an electronic skydiving logbook as part of a CS project. What fields would you want in your electronic logbook? Right now I have jump #, date, location, aircraft, container, canopy, delay, total time, maneuvers, description, and signature. It's basically just right out of my paper logbook.
[geek mode]For now I'm just writing the classes to read and write the data (XML), with a little command line demo to spew the data and let my professor key in his own entry. A complete app is outside the scope of this project. Of course, once I have those classes it wouldn't take more than a day or two to put a simple GUI on it... Looks like I might have a little summer project here.[/geek mode]
--
Brian

[gale 0]

How about altitude, speed (max and average) and then the ability to graph trends, and do seraches. (Like, when was the last time I jumped with Jane, or whatever) This might be outside the scope of you project though.
Gale
Life's not worth living if you can't feel alive

[Jumperpaula 0]

Quote

maneuvers, description...

With the growing popularity of the Skydiving League, I would think this could be marketed as a very important section.
Drop down menus showing blocks and random so the teams could Keep up easily on which moves have had significant practice,and which ones are left unpracticed.
Also, landing comments. I personally, especially on a canopy Im still learning, would like to note our landing "rating".
One other idea for a handy reminder would be reserve repack reminders on the software and auto reminders when you acheive a USPA award level.
Excellent idea for logbook software. There are lots of ways to market various versions.
Fly Your Slot !

[indyz 1]

Altitude is in the spec, it got lost in my copy 'n paste somwhere. D'oh . Max and average speed is a good idea. The point of the project is to work with data storage and retrieval (guess who got XML?), so analysis will be left out until I add a "real" user interface.
Thanks for the ideas! If I get into this like I usually get into projects (and get off of my ass and learn Swing), I should have some sort of usable demo done after finals.
--
Brian

[AndyMan 7]

I'm a geek, but I'm also somewhat pragmatic.
What problem does it solve? It seems to me the biggest pain in the ass is the physical act of pulling out the pen and writing the shit down.
So, a requirement would be integration to Jump-Track. Jump for a weekend, go home, dump your pro-track into your database.
If you don't have automated entry, ther'es just no point. I'll stick to doing it the old fashion way.
_Am
ICQ: 5578907
MSN Messenger: andrewdmetcalfe at hotmail dot com
AIM: andrewdmetcalfe
Yahoo IM: ametcalf_1999

[indyz 1]

There's no real point. I need to munge some data as part of an assigment and a log book is something I'm familiar with that happens to fit the assignment neatly. If I go further and add an interface (make it usable), it will be more of an exercise in learning Java's Swing GUI components than anything else.
--
Brian

[FallingILweenie 0]

If you don't have it "hookuptoaprotrackable", i'd have the thing do calcuations for freefall time based on the altitude and the manuevers (freeflying vs belly flying) like you do on a regular logbook.
Also, maybe opening altitude and distance to target.
I really like the reminders idea--you could expand it to include reminders for when you will get off currency (for those of us that have winters interrupt our happy jumping).
If you wanted, you could also add a feature that accesses the weather forecasts for your favorite DZs.
"Marge, it takes 2 people to lie. One to lie and one to listen."
-Homer