Assumptions:

• Data comes from five sources - Serial G-rays, Flash based G-Rays, text files and optionally from the Track Server and AGTEK Access Server (automatic upload).
• We should present tracks the same way regardless of the source. As an analogy, each capture device is like a camera in that it captures data, but just stores them differently. In the end tracks are all pictures of what happened. The device shouldn't matter to the presentation. That means:

• We'll need to apply server rules to the data that forms tracks. (George has these implemented in his AGTrac project already along with code to read the new G-Ray)

    * Gaps greater than 4 hours on the same date are separate tracks.

    * Gaps less than 1 hour across a day are in the same track (UTC days require this).

    * We check the 61st (or 121st) point for presence in a project, if not inside the projects, we put it in other.

    * We have to create a local method (catalog) of storing projects and data. I'm thinking an xml file describing the Projects and Tracks for quickly populating the window when the import window displays. This does mean more code for housekeeping of what's there but lends a level of organization to all the data that is missing now. The challenge of trackwork has always been to handle the large amount of data in a clean, organized way that conveys the results without being bogged down by the quantity. If we end up with competition, this will be a key differentiator. Other tracking applications have opted for collecting data less frequently and throw out key information rather than deal with the detail.

• AGTEK Access/Trackserver is an option set on installation like we do with Netkeys. These features of the Import window do not appear if the registry is not set to use them.
• The single method of presentation means we should formalize our directory structure on disk and mirror that on AGTEK Access (when present).
• Installation creates a Projects folder under the data directory.
• Sources like the G-Rays, text files, and the trackserver are just a read source. We read them and store the data in the Projects\ProjectName\Tracks\Days folders. In fact, after reading any of those sources (except maybe the trackserver), we should ask or have the option of removing that data from the source. Going back to the camera analogy, you read your pictures in from the flash drive. Then you remove them from the flash drive to go back to your camera and shoot more.
• We'll want to store what's in those Projects folders and display it when you first open the import window. It's essentially a localized version of what we have stored on the trackserver. In fact, we'll want to be able to synchronize what's on the local machine with what we store in AGTEK Access.
• Trackserver becomes more of a mechanism for getting automated points or data read into the system remotely from Trackreader, etc. We store the organized data locally or on AGTEK Access.