This morning, I upgraded the servers. The new setup has twice the RAM and twice the CPU speed.
Recently in Cyclogz Category
I am pleased to announce that Cyclogz can automatically geotag your ride pictures. Here is how it works.
- Before getting started, make sure that your camera is set to the local time.
- Upload your pictures to Flickr™. Cyclogz will only look for public images, so make sure to share your ride pictures with the public.
- After uploading your ride log to Cyclogz, click on the &Setup Photos" link. This will open up a new window.
- Enter your Flickr ID to get Cyclogz search your ride pictures. You can go to sites like idGettr to know your Flickr ID.
- Follow the rest of the instructions on that window to associate the photos you want with the ride.
That's it. Cyclogz will then geotag your photos, and generate a slide show!
At this time, Cyclogz will not save the geotag data back to Flickr.
I am pleased to announce that Cyclogz now supports personal ride diaries today. Apart from showing the logs chronologically, this diary lets you see vital statistics on a monthly basis so that you can train better.
This is just the initial version. Please check it out. If you have suggestions, please email.
Happy riding.
As you may have noticed, Cyclogz does not ask for any user inputs like titles, places, descriptions etc at the time of uploading logs. Why? That is just to keep the uploading process as fast possible. But what if you do want to edit some details? You can do so leisurely. To try it out, login, and visit the page of the activity you want to edit. For instance, take this page:http://www.cyclogz.com/activity/42.The page displays hints like the ones shown in the screen shot below:
You will notice similar hints for the blog URL and ride notes. To edit, just click on the text above (i.e. "San Ramon Loop"):
Enter the title you wish to have for the ride, and hit save. That's it.You can do the same for ride notes and few others as well.
At Cyclogz.com, there was a problem sending emails to signed up users. It should be back up now. Sorry for the inconvenience.
