Hi, >> 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. > > I have briefly looked at the adding a legend. As far as I could see in > the google maps api V3 there isn't a standard element which would work > as a key. it could probably be added relatively easily with a div > overlaid on top of the google maps layer, but I am not sure if it is > necessary.
So far I think with the popup coming with GMaps should be enough to give users an idea of what's going on there. >> > 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 don't know of any standards either. Quickly doing a Google search > seems to give a lot of examples which go from blue to red to white. > Perhaps this would be easier to interpret. Looking at a gps trace from > cycling through a town with my current system seemed slightly confusing > to me. Maybe it's a good idea to play around on line's format (dashed, dotted, solid, etc.) to give more clarity. >> > 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. > > Adding pace would be straightforward. Great! As you and Vincent pointed out, heartrate and time might be useful. > While looking through the API I found that you can set up the little > info boxes so that only one appears at a time. I am unsure if this > would be desirable behaviour or not. On the plus side it would save > having to close a load of boxes if you look at the info at lots of > different points. On the downside it prevents people from having > multiple ones open at a time to compare, which could be more useful if > more things like pace and heartrate are added. I favour keeping the > current approach since it gives more control to the user. I agree. > Also the current implementation assumes metric units which is not good > since you can choose US units in the preferences which should be > followed. As said on previous message, step by step. > What I am currently not certain about is what units the data > from the activity.tracks distance field uses. If your gps is configured > as metric then it gives the distance in km. If this is not the case do > you know if this is still in km? I would expect miles, anyone to confirm? >> > 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 a SF account with the username quantumstatejim. Added to the project with write access to svn. Please give me a shout in case of any question ;) Regards ------------------------------------------------------------------------------ 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
