|
AditTrec
You can now get hold of a program that runs on Palm OS® handheld computers, and Pocket PCs (pocket or mobile OS) that can be fully integrated with AditSite. More information on AditTrec
Our
first foray into a direct interface to a GPS device
started when we were contacted by an existing customer, who had bought a handheld GPS, and was using it for species recording. He recorded each species as a new waypoint, and wondered if it was possible to upload this information to his PC via a serial cable, to save lots of typing.
Now, this has two elements that are just our kind of thing:
It saves re-entering data –
which isn't always a fascinating as it might be
and can also be subject to transcription errors.
There was some doubt as to feasibility. If you really want to get an
adit programmer to do something, you tell him that you have been reliably informed that it is not possible. Failing that, asking if it is possible with some doubt in your voice, works fairly well.
We had already developed a basic module for communicating with GPS devices using the NMEA standard (in collaboration with Alphabet Soup who develop software for Mountain Rescue groups), and could reliably read current position, altitude, etc, but to access waypoints, we needed to look more closely at the manufacturer’s own communications protocol.
The box in question was a Garmin GPS 12. Garmin have a proprietary protocol which is fairly well documented (definition available on the web), and within a day or two we were able to develop a small Garmin-specific module.
Waypoints have a maximum of six characters, and while this was sufficient for the user to distinguish between various species, it created a minor problem in terms of automatic data loading. For most species the short search string could be used, and where this was not unique, the user was simply prompted to select from the alternatives.
The picture shows the standard data input screen, with the uploaded waypoints.
|