Hi Jonathan, > I have implemented coloring for absolute scaling and have adjusted the > scale w.r.t. the active workout to color based on a range of 2 standard > deviations about the mean speed.
It works like a charm. To be honest, the only thing I miss is the correspondent legend embedded in the map, but I am not sure if this is possible. > Since you can only see one workout at > a time I don't think a coloring based on the total history of the > athlete would be that useful, the absolute scaling should be good enough > for that. You are right. My idea was based on legend's abscense: if I can see each time which color corresponds to which pace, I can forget about absolutes. If not I guess I would always link color to pace regardless if I run at 4 min/km or 6 min/km which can output the same (relative color) layout. > I am unsure about how it is best to use the colors. Currently for the > global it uses black-blue for walking speed and then loops through the > spectrum twice while slowly increasing the brightness. This gives a > good contrast between speeds but it might be too confusing to have it > going over the spectrum twice (or even once). Maybe it would be best to > use some common heat map style coloring? I am not aware of any standard about this, but what it comes to my mind is closer to red when I am faster and turning into 'colder' colors when I am slower. > I also added a feature where you can click on the path and it will pop > up a box showing the speed at that point, this saves having a key. Great! What about showing pace as well? This can replace adding a legend. > Currently there is no gui, you can switch between global and per workout > at line 112/113 (it is set to per workout in the patch). I think it > would be best to provide options to switch the coloring on/off (it is > significantly slower than the plain blue for large datasets, I tested it > with 26 mile walk and moving around the map is possible, but slow) and > then options to have global or per workout coloring. Step by step. I will commit this on your behalf to our svn repository. Do you have any SF account which I can grant write access? > I have attached a diff taken against the svn version of googlemaps.py. Thanks again! David > > On Thu, 2011-03-03 at 21:49 +0100, Arnd Zapletal wrote: >> David García Granda schrieb am 03.03.2011 18:17: >> >> >>From what I see on my local version, I always get tracks coloured in >> > green. I was discussing with a friend of mine something similar some >> > weeks ago and we didn't agree on how to scale colors: should we >> > collect info from the user and based on his/her history coloured >> > accordingly or just as an absolute value?. Other options? >> >> Hi all, >> >> I haven't applied the diff yet, but I always welcome such eye-candy >> features;) >> >> IMHO David's remarks about the right/individual color-mapping are important: >> Though even if the mapping is adapted to the athlete's history (her >> min/max/avg paces or speeds) the result could fail in some usecases: >> >> (e.g. I do intervals regularly so my history min/max ranges from >> snail-slow jog to 400m sprint. Not much different to an absolute scale, >> or? Same for cyclists in the mountains etc.) >> >> Maybe offer several options (as global or local settings) to the user: >> >> 1) absolute scaling >> 2) total history of athlete (per sport of course) >> 3) scale w.r.t. the active workout >> >> 3) of course means you can't compare different activities by their >> colouring. But it probably gives the best visual experience (?) >> >> cu >> Arnd >> >> PS >> matplotlib already offers legions of mappings >> http://www.scipy.org/Cookbook/Matplotlib/Show_colormaps >> >> ------------------------------------------------------------------------------ >> Free Software Download: Index, Search & Analyze Logs and other IT data in >> Real-Time with Splunk. Collect, index and harness all the fast moving IT data >> generated by your applications, servers and devices whether physical, virtual >> or in the cloud. Deliver compliance at lower cost and gain new business >> insights. http://p.sf.net/sfu/splunk-dev2dev >> _______________________________________________ >> Pytrainer-devel mailing list >> Pytrainer-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/pytrainer-devel > > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > Pytrainer-devel mailing list > Pytrainer-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pytrainer-devel > > ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
