Phantom routes and other problems

For the past month I’ve been on a lucky streak creating trips with DeepZoom. But as of today it is no longer working well for me for these reasons:

Phantom routes. This is a new problem I have not seen before in DeepZoom. It’s a route that spontaneously goes dead and no longer works as part of the trip. It still shows up in the route list and appears on the screen but it cannot be selected for editing. Clicking on the route only takes you to the next route. In other words, the phantom route shows up on the screen but cannot be selected by clicking on it or by choosing it from the route list. The only workaround I’ve found is to just make a new route and try to ignore the phantom route. The phantom route does not go away when I quit, restart DeepZoom and reload the trip. Unfortunately, the phantom routes seem to keep occurring when I’m editing trips today. This seems to have started today as far as I can tell.
Random date changes on routes. This is another new problem for me. It happens to routes that are not being edited. The date just change, apparently at random. For example, a route set to happen on May 5, 2024 spontaneously changes to May 21, 2024. Or several years in the future. I can’t sort out what is causing this and I’ve never seen the problem before in DeepZoom.
Loss of screen positioning control. This is an old problem that seems to have gotten worse today. Say I’m editing a route, moving the endpoint on the screen. Suddenly the center of the screen becomes locked on one place on the chart and I cannot get it to scroll over to the new area of the chart. Sometimes double tapping on a new area will cause the screen to recenter but that has limited effect. One solution to this seems to be to zoom out and try to continue working but the screen stays locked at the same center as before and its difficult to get the precision I want for waypoint positioning. I usually end up having to save the trip, quit DeepZoom and try to pick it up again. This is a very frustrating intermittent problem that has been around for a while but seems to have gotten worse today.
AM/PM setting difficulties. This is an old problem that I’ve learned to live with but it is frustrating. When the clock dial comes up for setting a route starting time it is often difficult to select AM or PM. It often takes several attempts to set the time correctly. A workaround that sometimes works is to edit the AM or PM with the cursor. This is not always reliable, though. The problem seems worse near the 12 o’clock position.
Slowly drifting waypoint while editing. This is an old problem that seemed to go away for a while but is back again. It happens from time to time when I’m trying to fine tune a waypoint position. I drag the waypoint and it starts to drift away on its own very slowly. About the only thing I can do is drag to the point where I want it to go and hold my finger there for ten or fifteen seconds waiting for the waypoint to finally settle down.

I’m having these problems on both my Apple devices: my iPad Pro 12.9” first generation on iOS 16.7.7 (the latest iOS available for the device) and on my iPhone 14 Pro Max on iOS 17.4.1 (latest iOS version available for the device). I’m using the Safari web browser.

Hi Doug,

Are you running version 3.14.55? Also is DeepZoom installed on your home screen, or running just as a web page?
Phantom Routes. Can you please confirm you haven't inadvertently turned off Enable selected route on the routes tab? If you press All: Enable on the Routes tab does the problem go away?
Random date change on routes. Please confirm you don't have Ripple departure date changes to all later routes enabled.
I've also seen this on 3 occasions over many, many, many hours of use, but also haven't figured out what sequence triggers the issue. Definite bug which is super hard to replicate, and I'm guessing is in the Mapbox Draw library, perhaps https://github.com/mapbox/mapbox-gl-draw/issues/1117. I've hit soooooo many bugs in this library :(
Interesting. I never use the clock dial (frankly, I'd forgotten it exists), preferring instead to use the departure hour horizontal slider. I'm assuming the issue only happens with the clock dial, yes? Now that I'm playing with the clock dial, I see what you mean... A definite bug.
You're saying, your finger or mouse is not touching the waypoint and it spontaneously moves??? Or are you touching the screen and it's jumping around unexpectedly?

It would be great if you could include a link to a trip which exhibits these symptoms.

Jay,Thank you for getting back to me. I'm having more success today. I've been using the 3.14.55 version of DeepZoom and I always run it as a progressive web app on either my iPhone or iPad Pro. I usually leave enable set to all on so I'll have to play with that next time a phantom route pops up. Unfortunately, I deleted the trips with the phantom routes and I have not been able to replicate the problem today. I think the route time changes may have been caused by leaving the ripple on. Will keep that off from now on. Lately, I've been making trips by drawing the whole thing out as one route and then snipping at the break points and adjusting the route settings for the resulting parts. I may go back to building trips route by route instead. The problem with the chart display locking on one position happens all the time when I'm trying to edit a route. I can gradually coax it to recenter in a jerky fashion by double tapping at the edge of the screen I want to move to. Not as ideal as simply dragging to pan the screen. This is probably the most frustrating thing for me right now since it requires so much effort. Makes it very hard to edit routes. I haven't used the time slider in the route window because it seems to be limited to 15 minute increments. I'll try to use that more, though. From my experience, the problem with the drifting waypoint has been in DeepZoom since the trip feature was added. It happens like this. When I'm editing the course of a route I'll drag an end point or other waypoint to a new position. Once my finger gets to that new spot I lift my finger off the screen and wait until the waypoint and connected route parts finish drifting around. Most of the time the waypoint will end up where I lifted my finger but not always. I've found that sometimes I need to drag to the new position and hold my fingertip down on the new position then wait for the waypoint and route legs to gradually float their way there. Sometimes I'll see two sets of waypoints and route lines when I'm doing this and the extras will disappear when the waypoint has reached the intended position. Other times a route line may fracture while the waypoint floats along, the broken lines reforming into a single line when the action is over. Doug @. Apr 12, 2024, at 10:33 PM, Jay Borseth @.> wrote: Hi Doug,

Are you running version 3.14.55? Also is DeepZoom installed on your home screen, or running just as a web page? Phantom Routes. Can you please confirm you haven't inadvertently turned off Enable selected route on the routes tab? If you press All: Enable on the Routes tab does the problem go away? Random date change on routes. Please confirm you don't have Ripple departure date changes to all later routes enabled. I've also seen this on 3 occasions over many, many, many hours of use, but also haven't figured out what sequence triggers the issue. Definite bug which is super hard to replicate, and I'm guessing is in the Mapbox Draw library, perhaps mapbox/mapbox-gl-draw#1117. I've hit soooooo many bugs in this library :( Interesting. I never use the clock dial (frankly, I'd forgotten it exists), preferring instead to use the departure hour horizontal slider. I'm assuming the issue only happens with the clock dial, yes? Now that I'm playing with the clock dial, I see what you mean... A definite bug. You're saying, your finger or mouse is not touching the waypoint and it spontaneously moves??? Or are you touching the screen and it's jumping around unexpectedly?

It would be great if you could include a link to a trip which exhibits these symptoms.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I've fixed item #4 in v3.14.57. This was a bad bug and may have influenced other things like the date changes you referenced in #2. In addition, I added support for a 24 hour clock, and the ability to set the departure time for all routes at once if you check the apply to all routes checkbox (below, center).

I'm still unclear what's happening with your issue #5. Is it anything like the video in this link: https://github.com/mapbox/mapbox-gl-draw/issues/1031

Jay,Many, many thanks for your excellent and continuing work on DeepZoom! The other day I tried importing a Garmin GPX track into DeepZoom and the replay was fantastic!! I imported it right after a sea kayaking trip in the Deception Pass area and the results were amazing. It was awesome to watch the actual progress of the trip along with the changing currents and tide. I wasn’t expecting this but the weather information appeared to have been preserved as well and matched up perfectly to what I recall from our time on the water. Blown away! I’m not sure how long DeepZoom holds on to past weather data but that was amazing. Now I have a complete record of my trip!Another great discovery was that I could bring in all my old tracks from my old Garmin eTrex and view them all at once in a single “trip.” I’m not sure how that happened from a single GPX file. I exported it from the old BaseCamp program on my old PC and apparently all the trips got combined in that single GPX. It was such a beast of a file the new Garmin Explore app. I thought I might lose the opportunity to bring those trips forward and was pleased to find DeepZoom could do it! Amazing nostalgic result! Now I can see all those old trips and leverage that information for future ones!I continue to rack up trips in my DeepZoom catalog. Along the way I’m still experiencing the occasional problem I call the “lazy waypoint phenomenon.” Specifically, when editing a route the waypoint I’m trying to move does not respond instantly but wanders about very slowly before finally landing where I want it to go. Sometimes this lag is accompanied by the temporary disappearance waypoint and/or fragmentation or disappearance of adjacent route segments. I’ve attached a link to a video that shows this combination of problems. In the video I’m trying to edit an existing route after relocating the Z end point, then deleting waypoints to get the route to conform to a new shape. The video shows the slow motion of the waypoints I’m trying to move, as well as the occasional disappearance of route segments, and the difficulty I sometimes encounter getting a waypoint to go where I want it to. Toward the end of the video you can see the fight I had with a waypoint that did not want to go where I wanted it to. I’m using a first generation iPad Pro on iOS 16.7.7 and an iPhone 14 Pro Max on iOS 17.4.1. I use DeepZoom 3.14.61 as a Progressive Web App on both devices. This is an old problem for me with DeepZoom. I thought it had gone away for a while after the big pi day update but its still pops up from time to time. Quitting DeepZoom and restarting does not seem to help.Here’s that video link: https://www.dropbox.com/scl/fi/4t8y8hgq4kbtu5okdodik/DZ-route-editing-quirks.MP4?rlkey=2qqjul0wu3xibq53gus9lc1xl&dl=0Doug @. Apr 13, 2024, at 23:49, Jay Borseth @.> wrote: I've fixed item #4 in v3.14.57. This was a bad bug and may have influenced other things like the date changes you referenced in #2. In addition, I added support for a 24 hour clock, and the ability to set the departure time for all routes at once if you check the apply to all routes checkbox (below, center). image.png (view on web) I'm still unclear what's happening with your issue #5. Is it anything like the video in this link: mapbox/mapbox-gl-draw#1031

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Hi Doug, sorry for the delay responding.

Does the lag when dragging route points happen identically on the iPad and the iPhone?

Are you a web or Apple developer and is it possible you have logging turned on? https://www.lifewire.com/activate-the-debug-console-in-safari-445798

I'm flummoxed about this. Earlier there was a bug that had these exact symptoms, but it's really hard to diagnose your issue without a console log, (this is assuming the lag is due to a flurry of exceptions which would be logged).

Jay

jaybo / deepzoom-blog

Phantom routes and other problems #41