Skip to main content

There are three items within our running/cycling group that have really been chafing us:

 

  1. I’m not sure how to completely describe this but I’ll give it a go - across the top of the map, a “layer” of buttons was added whereby you can “Upload GPX”, “Reverse Route”, Redo/Undo, Trash, Display Heatmaps, and Display segments, etc.

    A large number of the phantom “distance jumps”  -and- “Red Box - Sorry We Couldn’t complete...” errors are due to this layer interfering with dropping a waypoint.  Any time a waypoint is added on the top 15-20% of the map, it registers a waypoint was added but fails to formally assign it to a location as this “layer” seems to interfere.  As the mouse moves, the waypoint sticks to the cursor and causes all kinds of havoc because it can’t actually place the waypoint.  If you are re-routing, this same issue causes a secondary problem because it will also plot the “finish flag” in the same location once it finally can find a suitable location.

    Contributing to this error is #2.

    Annoyance Factor: 7 of 10 - mostly because it compounds with other issues
     
  2. Map real estate - With the top 10% lost to the “buttons”, being able to Zoom in on a run to view street names becomes increasingly cumbersome.  Additionally, if you open the “Elevation” map, you then lose another 30-35% of your map area to the elevation graph.

    This is problematic with issue #1 and plotting runs where waypoint placement may be more intimate than say a cycling route.  

    I’d love for the buttons in the top 15% be moved above or to the left nav bar and also to allow us to resize the elevation as we see fit. 

    Annoyance Factor: 3 of 10
     
  3. Segment “Finder” - I know this has been discussed before but some segments simply just will not appear on a map regardless of how much/little you filter on a location.  They are not hidden and meet recent criteria of being over 0.25 mile long - yet, will not show.  This made sense in the “old days” when you listed 10-12 segments on the right navigation.  Since this is no longer the case, it shouldn’t matter as much how many are listed simultaneously.  

    Annoyance Factor:  2 of 10

 

What browser are you using and what screen resolution do you have? In Firefox I can place waypoints near the top most buttons without problems. And zooming in to see street names works flawlessly for me.

Primarily Chrome - Resolution is irrelevant as I have the issue on several different devices from iPad/laptop/desktop (with 4 monitors).

​@Jan_Mantau I can reproduce the issue in Firefox as well - it seems more tied to dragging a point rather than simple placement in Firefox vs Chrome.  

  1. Start a new route and Plot a few points
  2. Click on the “end point” and Drag it up towards the “Heatmaps” or “Segments” buttons.  Specifically, just to the right of the “Segments” button.  
  3. At some point, the cursor will change from a “Hand” to the traditional “Arrow”
  4. Release the mouse button - you can now move the mouse and the waypoint will not place - it’ll stick to the cursor.  
  5. You have to physically click on a location to place it.

This issue has caused several errors such as:

 

phantom placement (e.g. 100+ miles away),

 

If a mid-point is dragged into this situation, it’ll locate the mid point along with the end point when you eventually click on a placement location.  Clicking “Undo” often times leads to either the dreaded “Updating Route” loop or the annoying “Red Box” error after 30+ seconds.

 

“Updating Route” issue will completely hang the session with the only resolution to reload the page and lose your existing route.

 

 

With dragging the existing points over the buttons I could reproduce that. That’s indeed annyoing if it hits you unprepared. Now that you know exactly when it occurs I guess you can simply avoid it by not dragging points to the dangerous areas.

Terms & ConditionsCookie settingsAccessibility statement