Log 2015121202

For the record... Dayton of Montgomery County (Wikipedia article) with a population of 141, 527 is  the largest city on the North Country Trail (4,500mi long) and the Sea-to-Sea Route (7,800 miles) as of the date of this log.  However, it is not the largest city on the Buckeye Trail.  That distinction belongs to Cincinnati of Hamilton County.  And I don't know enough about the American Discovery Trail, but from what I hear, it's routed through Chicago, Illinois and that's probably it.  When I declare these, I do not count greater metro areas (just the cities themselves)

------------------------------------------------------------------------------------------------------------

Pictured here is the modified track for the Troy Section (North Country Trail concurrent) on Google Earth that I made from from the BTA GIS/ GPS Data Depository.  The remainder of this log is about digital mile markers.

In this picture, I backspaced the track from it's terminator until I met a predetermined intersection that I made a placemark for.  With it's properties dialogue up and it being set to "measurement," you can see that the track is now reading at 48 miles.  If the whole miles were in the single digits, Google Earth would display something like "9.48 miles."  But all mileages 10 and above only read in the tenths (and not in the hundredths).  And when backing down a track, in this case it would go something like "48.1, 48 then 48.0."  Personally, I don't like this.

So, I switched the dialogue box to read in "inches" instead.  As you can see here, it reads the track's length as being "3,046,742 inches." There are 63,360 inches in a mile.  So, when using a calculator, dividing 3,046,742 by 63,360, it comes out to "48.0862058081."  Personally, rounding to the ten thousandths (48.0862) is good enough for me... that's all I really need.

In this picture, I closed the Properties dialogue for the track and then opened the one for the placemark.  As you can see, it's still unnamed.

Here, I named the placemark with the track's mileage based upon a division in inches, pressed OK and now I can move further uptrail.

I use inches for two reasons.  For one is that I don't like those mileage readings that come without a decimal place.  And two, I'll do this if two or more placemarks look like they'll occur in the same tenth of a mile (or it just looks like its going to be close).