I don't understand the lack of this... I have to do this manually. Is this as obvious as I think it is?

An obvious improvement that should be very easy and cheap to implement.

I am kind of surprised that TrainingPeaks does not have this especially if they have it for biking, it should then not be that hard to add Peaks for running. Honestly for me with running in mountainous terrain all the time, using peaks for pace is horrible, obviously going down hills are always going to give very fast speeds which I would never be able to do if it was flat or at least partly normal, heartbeat would be the next best, but that has it’s delays and other issues as well. So using peaks pace is no good for the terrain I run, train, and race in. It really is useless unless power is used, because power stays the same whether it is all up hill or not or all down hill or both … it truthfully tells you if it is truly a peak or not and is not subjected to a better course or not better course … it makes all courses equal and measurable. The only way that peaks would work for me if I was looking at pace is if you compare to another run that is exact course and distance. Which I do not ever do. I truly hope TrainingPeaks would consider this because I am sure I am not the only one, there is not a flat area I train in a fifty mile radius where it is flat for more than 3/4 of a mile. For example I went on a long run from my house on an out and back run of 10 miles and the elevation gain was 1,300+ feet. During that down hill part of that run I got a peak of a 5K at 22:05 minutes and I felt it was an easy exertion. By the way, the 22:05 is only a minute and a half slower than me running an all out 5K race on a flat course. But if I look at my power during that down hill 5K part it tells me that I am going at 80% of my power FTP which is exactly what it felt like, not the 100+% of my FTP that my pace peak was at. This is totally acknowledged in the world of racing … could you imagine the New York Marathon being run in the mountains and it was all down hill. The world would not recognize it as a world record because it gives a false reading of what that person could actually do in normal terrain unless all people in the world run that exact same course. The peak for that marathon according to TrainingPeaks would be easily under the 2 hour mark, which we know is not even possible yet in any legit marathon course. That is why power needs to be in Peaks in running so it honestly reports your true peaks! So what I am saying is pace Peaks flatters people who run in my type of terrain (tells someone they are faster than what they are when going down hill) or slanders them (tells someone they are slower than what they are when going up hill). I don’t think this is what TrainingPeaks wants to do for its customers - discouraging. Thus let’s get run power up and going since it is within your capability and power so Peaks can be good for all runners no matter what their terrain and not catering to those who live in “ideal” running terrain:-)