Very, very long routes, and possible solutions to loading issues
I am a photographer, and railroads are a favorite subject. I have (tediously) created routes to highlight long sections of railroad. This has lead to loading issues (as in no aspect of my map is usable) in the past, but I have been able to distribute these routes across multiple maps, and while far from ideal, it has eliminated the problem (for now...)
I have read that routes are a series of connected waypoints, and tracks, I am assuming, are in a different format (?) that is more friendly in this regard. If this is the case, would I be better served to convert my long routes to tracks? Also, if so, are there other aspects of my routes that would be sacrificed by doing this ?
Finally, is this loading issue I have experienced hardware related, or a result of my use case (abuse) of CalTopo ?
I am mostly on a 3rd Gen iPad Pro
_Jeff A
Comments
3 comments
Hi Jeff,
For all intents and purposes lines and tracks are the same thing. Tracks imported from or live tracked through the app will generally have more points and be more data intensive.
We can take a look at the maps with you, if you'd like to do this please email us at help@caltopo.com and include the map URL.
The loading issue can be device specific. iOS tends to run into problems before android or the website.
Thanks Rachel.
Will unchecking the box that controls visibility on startup have any effect?
Hi Jeff,
It may help with loading the map initially yes.
We do have a new feature called "print to mapsheet" which will be on the blog in the next week or so. This requires a desktop or team subscription but would be helpful in this case. You can create a map with just that long line on it and print it to a translucent mapsheet. Then you can overlay the mapsheet on other maps without slowing down the map in the same way a long GPX route will.
https://training.caltopo.com/all_users/mapsheets/create-sheet#printtomap
Please sign in to leave a comment.