segmentation issue (map hover cursor does not change to campsite selector when in segmentation mode)

Mike – we’re not able to replicate this issue.

Expected behavior: when you hover close to the route line, the pointer should change from a hand (move the map on click) to a pointer finger (click to place a campsite).

If you are able to record a screenshare, email me the link, and let me know your browser, we can investigate further.

Ryan—definitely does not turn to a pointer. Also not sure if related, under route it gives me an accurate total distance, but no elevation information at all.

Safari 18.6 (Mac)

Thanks

Mike

Mike – that makes more sense now. Safari 18.6 is a bit out of date, and has undergone some pretty major upgrades since it was released (we’re now on version 26.x).

That’s not a deal-breaker, but in order for us to confirm that this is indeed a backward-compatibility issue and put the right backward-compatibility fix in place, are you able try the same route in Chrome or a newer Safari version and let us know if you continue to experience the issue?

If that fixes the issue, then I’ll know exactly how to patch it to ensure backward-compatibility.

Turns out that’s the most recent Safari I can get, based on my computer’s age. I was able to download Chrome and got it to segment camps (had to be saved before letting me segment).

However all graphs/data related to elevation are blank??? Has the correct mileage and segment lengths, nothing related to elevation.

OK, good. So for the elevation issue, please email me your GPX file, we’ll need that to diagnose that issue, which is separate.

I’ll keep this thread updated about the Safari browser issue.

KNOWN ISSUE: Route renders in Safari 18.6, but route hover hit-detection fails, so cursor never changes, and segmentation click does nothing. Chrome works. Not reproducible on Safari 26.3.1.

Update:

There are three issues of note in this thread. I’ll address them all here:

Issue #1. Route segmentation and route hover cursor change are not occurring on the map.

Reported by OP to not be working on Safari 18.6 but possibly on Chrome. We were able to replicate this behavior on a few different Safari and Chrome browser combinations, so I’m not convinced (although it is possible) that it’s exclusively an older Safari issue.

The non-browser-specific route hover problem was caused by the OP’s GPX file. This was exported by Caltopo, which has a messier “track” logic that results in large numbers of duplicate points in the GPX file that subsequently confuses TRIPS’ route hover helper (the helper sees multiple “routes/points” in the same spot, and so just kind of mentally gets tired and takes a nap).

We resolved this by creating fallback logic that tells the route hover helper to “try again if things get hard” (use a different route analysis method if needed). This encouragement seems to be working now.

Issue #2. Elevation data is missing from the route.

OP’s caltopo-exported GPX file was missing elevation data because it was exported using a non-PRO subscription. Caltopo only exports elevation data in GPX files for PRO users.

Issue #3: Safari 18.6 route hover behavior is not working, whereas it works in Chrome and later versions of Safari.

This may be related to Issue #1; it may not be. If OP tests again with a refreshed TRIPS app and #3 is resolved, then #1 is the reason, due to WebKit mapping library updates (route hover logic) that have been propagated into newer versions of Safari, in which case our route hover helper fallback logic will handle that. If Issue #3 persists, let us know, and we’ll investigate further.

marking issue as resolved.