+ GPSMap 76Cx or CSx, which is what I have and what is apparently out of
production. The 76 and 78 models are also waterproof and floatable as
opposed to be water-resistant. All models above have a capability to
attach an external antenna which will further improve the reception. My
favorite external antenna is
http://www.gilsson.com/, since it's good and
inexpensive. I don't use it now since the receiver is good enough, but
used it all the time in the preSirf days.
We want to have the best receiver possible because the mediocre receiver
will loose reception in the mountains, under heavy tree canopy, in the river
canyons. Any receiver will work just fine on water and on an open street,
where there is an unobstructed view of the sky and thus the satellites.
Delorme, Magellan, and majority Garmin models are those mediocre
receivers...
2) Who's and what data do we want to allow to the database?
I would allow any and all data as long as it is not hand written in mapping
software, but taken in the field. We want to have all tails covered in our
database as soon as possible even if the data is outdated. We can always
improve on it later on. Just like with Wikipedia
or Amazon.com we can have reviewers comment on it and delete the
inappropriate content.
3) What are the objectives of this database?
I want to make a very important point here. This database is a
collection of hike traces, NOT a trail map. PATC cartographers will
take these hike traces and convert them into the trail layer for the GIS
database to be published on a map. For example, John Doe submitted the Old
Rag hike trace to the database. Other people submit other traces. A
cartographer takes these traces, loads them into a program like ARCGIS, edits
them and creates a layer with all the trails of the Central Section of the
Shenandoah Nat. Park for the PATC Map 10. This cartographer or a
third person makes sure that the traces are current and correct. He
adds the layers of elevation contour lines, streets, streams and mountains, etc.
and publishes the map. The objective of the database should not only be to
provide data for the cartographers for creating printed maps but also for
hikers to pick up a trace, downloaded it and hike it.
4) How would I group this database?
Pretty much by State and then the PATC Map grouping. E.g. All
the traces of the Central SNP will be in VA -> Map 10 group. Traces
that are not part of the PATC maps can be grouped by State -> County.
If the trace falls into 2 or more groups, it should be put in the one where it's
length is the longest. E.g. Harpers Ferry hike should be in MD if it
started at Weverton Cliffs. It should be in WV if it was only in the
Harpers Ferry. It should be in VA if it was mainly in Loudoun
Heights. Blockhouse Point trace should be in Maryland -> Montgomery
Co., since it's not on any PATC Map.
5) What tags should be associated with each trace?
As many as possible, and whatever can be filled, should be filled.
There should be Yes/No, Option and Fill In fields associated with the trace when
it is submitted, but only a few if any fields should be required. Here are
some of the fields that come to my mind:
*Date of the trip
*Hike/Backpack
*Loop/Out-n-Back/Tennis Racket Shape
*Names of the trails. Are any of these trails outdated?
*Bushwhack/Always on Trails. If bushwhack, how many bushwhacking
miles.
*Waterfalls (yes/no) and name if yes
*Overlooks (yes/no) and name if yes
*Special features (e.g. Columnar Junction at Compton Peak - an interesting
geological feature)
*Parking Lot coordinates and information about it.
*Comment Section: I liked this and that, I recommend this trip for this and
that.
*Warning Section: hunting season, slippery rocks, wadings, unclear
blazes.
*Contact information for the author, not to be published, but in case
cartographer needs additional details.
6) An elevation profile and statistics should be automatically created and
posted next to the trace. Statistics should include total elevation gain
and loss, max and min height at the very minimum.
7) There should be a way for people with multiple traces to submit them in
a lump, not individually. I have 100s of traces, and so do some other
people I know. We won't submit them one-by-one.
8) Not all the traces are equal. There are "Special Hikes" to
"Special" places. For each section, it would be a good idea to have traces
with lots of details and good description, which represent these special
hikes.
9) Different people use different software to work with the
traces. Most people I know and myself use Topo! Mid Atlantic and
Pennsylvania by National Geographic. Other people use Delorme's or
Garmin's software, not to mention 3d party programs including Google Earth and
GPSTrackmaker. This database should allow only the *.gpx format. I
would put a link to the free utility gpsbabel -
www.gpsbabel.org that allows to convert
from one format to another and from any format to the *.gpx. By the way,
all programs mentioned above allow to import *.gpx directly into them.
10) I wouldn't restrict the database to the PATC maintenance region.
If a person went to California or France and had a great trip, let's post it in
the NonPATC section of the database anyway.
If you have any questions about any of the above, please let me know.
Dimitri Tundra