Easy run with Ted in the morning. Dropped him off at 6.5, then went on for more. Decided to do a short tempo to feel the waters. Ran 1.25 in 6:42 from the DI bridge to the railroad bridge on the trail. It is a slight down, about 0.5 %, but it does roll. Heart rate eventually climbed to 159. Legs felt strong, I felt I was getting a lot of power in my stride.
Ran with the kids in the evening. Got the GMap plotting feature in the course tool to the point where I could make it public. Check it out. Lots of little and not so little things are still lacking, but at least you do not have to go to GMap Pedometer and do the GPX dance to upload your course. One step at a time we'll get there.
The new feature helped me discover an interesting problem in Google Maps. There appears to be a shift or a small discrepancy between what you see, and the coordinates Google Maps API gives you. Here is my evidence for it - I clicked around the parking lot where the Provo River Trail intersects the Geneva road to get an idea of what the actual elevation of it is. I figured, I am getting averages of 30 meter squares from the US Geo service. Well, the parking lot is big enough, and it is nearly perfectly flat, you should not be getting any variation more than 1 foot or so. Well, the elevation data I am getting shows there is a 10 foot deep hollow right in the middle of the parking lot, which matches the width of the adjacent Provo River. When you click on the Provo River, there is no drop in the elevation, and it actually happens to be above the hollow of the parking lot. I am still not quite sure what to do about it. Paul, any ideas?
I do have a friend who is a runner who works for Provo City, and does survey measurements. Maybe I should have him stop by and get the actual coordinates of some easily identifiable point in that parking lot, then file a bug reports to Google Maps.