Made it a lazy day for the big grey. Walked almost every inch of the 12 miles and he smacked down bunches of tall green grass. Going home he was hitting a head banging 5mph at the walk then jumping into a trot and I would pull him back.
Well I am having a hell of a time with these KMZ and KML files. All EchoValley's open fine on my computer when I click on them where they are stored on my hard drive. When I paste them into this discussion using the "Upload Files" button something goes wrong in the translation. MotionBased is trouble free for me at this point.
I cannot open Kevins Loop
I can open Sonny
I cannot open T-Spur Ranch
I cannot open TL
I can open Cairo
I cannot open Fly
I cannot open any EchoValley
Anybody help out here?
the kml files are a standard tagged (xml) document. for them to be served/dispatched correctly, the web server must be configured correctly (it is not right now). I'm going to move these track-logs over to our servers so that I have control over the configuration. The .kmz files are "zipped" (same format as pkzip) which most servers are configured to serve correctly. The local binding (.kmz -> GE) is a client side thing that google earth does when you install it.
A further thing about both types of file - they both are .xml tagged files. They have structure which includes things like folders, discriptions, icons, etc. and, most importantly, coordinates. You can see an example of this by clicking on Don's .kml file. I have found that the GPS import to google earth puts "waypoints" and "paths" into a "folder" and to see the path you have to, sometimes, click on the path and "get info" or "properties" it. BUT, if you copy the path (only the path, not the folder or waypoints) and past it into your real places, it shows up just fine.) I've been making a my-places folder for the ride which contains all the paths which have been uploaded.