[pct-l] Data Book Mileposts--database

[losthiker at sisqtel.net (Deems)]

Comparing the previous and new data books we see that the trail has grown by
seven miles between
editions, and it might grow again when OR/WA is revised.     This creates
problems with our
ingrained habit of naming points by the distance from the Mexican border.
^^^^^^^^^^^^^^^^^^
I agree that this could be a problem for years to come, using the mileage
point to identify a unique landmark point on the PCT. If the mileage
changes, then the landmark point is renamed indiscriminately. A different
proposal that would work is to give each landmark in the current BenGo book
it's own unique identifier that is independent of the mileage. Possibly
using the Section it lies in, and a cumulative number identifier. Oracle
databases use unique identities to track discrete data points. An identifier
such as A22 for the Lake Morena road crossing. It's the 22nd item in the
book in section A, and lies at milepoint 20.2  If new points are inserted,
then add a decimal point for each new insertion.  Such as A22.1 would be the
first insert between Lake Morena and Ridgetop. If a section is removed, such
as will happen with the Tejon Ranch addition, then a new identifier will be
used. The main thing is that each point in the BenGo PCT Mileage book should
have a unique identifier (that is never repeated!)  in addition to the
mileage (which changes), and the map label description. Linking it to PCT
Guidebook section could help, unless Wilderness Press changes the section
names and trail described, as will occur with the Tejon Ranch addition. A
database person out there could have fun with the PCT information database,
and possibly unspaghetti the inevitable changes to come as the trail
evolves, and write the next PCT mileage databook.