moving-bits

I could start working on the technical aspects of this issue, but this would only make sense if someone implements a new drawable. @ztNFny Would you be willing to create...

> If such new type is introduced, would I still be able to use one of the other types for such a calculated waypoint? > > Because I would not...

> That would actually match, what is also used for a "non joker" calculated waypoint as marking in the waypoint list. Therefore I think it would be consistent to reuse...

> The challenge with this issue is IMHO not so much the introduction of a new waypoint type (this is actually very easy) but to come up with a good...

based on material.io:calculate: (as shown above) |regular icon|dot icon| |---|---| |||

> hm, I find that one way too busy in the marker. Also transparency in the icon color is not nice. But I'd suggest you commit whatever you have in...

> @moving-bits keep in mind that at least now there's no relationship between "origin waypoint" and "generated waypoints" kept in db or elsewhere. I know, that's why I suggest to...

https://www.geocaching.com/plan/api/gpx/list/BMxxx returns a DNF when called via browser (even when being logged in) - maybe API change?

> All list-stuff was switched to a new API on weekend Thanks for the new link > The "add to bookmarks" stuff is likely broken as well - can't test...

> Could you check the other list code as well? > > e.g. to add a list I used to call POST [geocaching.com/plan/api/lists](https://www.geocaching.com/plan/api/lists), now POST [geocaching.com/api/live/v1/lists](https://www.geocaching.com/api/live/v1/lists) same for GET/DELETE [geocaching.com/plan/api/lists/BMxxx](https://www.geocaching.com/plan/api/lists/BMxxx)...