Added the <trkseg> tag to the GPX Files (Other) format. This seems to be required by the Velox application that can be used on Android devices. It's a standard tag, so please let me know if it causes any problems for anyone who has been using this file format up to this point.
This one is a little complicated, but I'll explain it. I have added a new popup dialog box that appears when the route gets much longer than the user requests.
The scenario I was dealing with is this one. The user requests a route of, say, 10 miles, and RouteLoops makes one. Then the user starts to drag the route around, gets a little carried away, and ends up making a route that they really like, which is, let's say, 25 miles long. If they try to do anything with this route (like Permalink it), RouteLoops will decide that the route is much too long, and it will just generate a new 10 mile route. This can be really annoying if the user has spent a lot of time hand crafting the route.
So, although this is really not what RouteLoops is meant for (that is, for hand-crafted routes) I wanted to support that use case. So now, if RouteLoops spots a really long route, it gives you the option of updating your desired route length and keeping the long route. You can accept or reject that option. If you reject, RouteLoops behaves like it always has. If you accept, RouteLoops updates your requested route length and lets you keep the long route.
I added a new feature to allow RouteLoops to read in a preexisting GPS file (like a .gpx or .tcx formatted file). The reason is that I have some routes on my GPS device that I wanted to tune a bit, but I didn't want to have to create them from scratch on RouteLoops.
This new feature lets you import an existing route into RouteLoops. Once you have it there, you can edit it by dragging the route, changing the average speed, etc. and then you can put it back onto the GPS device.
I'd love to know if anyone uses this and if there is any feedback.
> I added a button that allows you turn off (and back on) the "autocleaning" feature. If you turn it off, RouteLoops won't attempt to remove little spurs and things from your route.
> I made it so that if you mouse over one of the waypoints, RouteLoops will ask you if you want to delete that point. Why, you ask? Well, I was using RouteLoops on an iPad and I realized that there is no way to right-click on an iPad. Up until now, you had to right-click near the point to remove it. So now even an iPad user can remove a waypoint if desired.
> The site now uses a location service (W3C location) to identify where you are when you launch RouteLoops. A little flag will show up, if that lookup is successful.
I added some new features into the RouteLoops application. They include:
> I added some pages formatted for mobile devices. If you hit it from an iPhone or Android phone it should prompt you to go to a mobile page. Give it a shot.
> I have been thinking about how to generate routes based on a preference for climbing hills, so I added, as a start, the ability to "profile" a route. It uses the USGS database for elevation data, so it only works in the US for now, but you can try it out. It attempts to provide a rating of the ride in terms of total climbing, and local "steepness".
> French and Japanese pages are there, too, for anyone interested. See the language links at the top.
Some RL additions:
(1) A simple way to share routes. You can upload your favorite routes to the server, and they will be visible to others. RouteLoops can also adapt those routes to start from your desired location.
(2) Turned on the Google weather layer