Caching mechanisms on GPX layers

[Dirk Stöcker]

On Sat, 15 Sep 2018, Niklas B wrote:

> (maybe this time..?)
>
> Hi,
>
> I'm currently implementing an option to cut overlapping GPX tracks when
> merging them into one layer (followup of #16681
> <https://josm.openstreetmap.de/ticket/16681> "*allow multiple tracks to be
> processed and prioritized (from different sources, e.g. GPS + phone +
> Google Timeline)*", but when merging layers because this is not
> specifically related to geotagging / geoimage layers).
>
> Everything works fine, but the resulting GPX layer is not displayed
> correctly: Some lines are displayed between tracks that are not connected
> anymore (because another track was on top of it, so the underlying track
> needed to be split) and also some weird lines connecting points that were
> never connected appear - haven't figured them out yet.
>
> Before I debug that any further: What caching mechanisms are there in
> place, what do I have to reset? I'm already calling invalidate() (in
> GpxData, which calls the appropriate listeners) and tried removing the
> cached "dir" values from all of the waypoints, but it didn't help.
> The layer will however be displayed perfectly fine if it's converted to a
> data layer (and back) or saved as GPX and reloaded.
>
> Any ideas on what might be the reason for that?

Maybe your troubles come from the fact that JOSM has different settings 
for local and server based GPS data (i.e. distances for continuous track 
handling)?

Ciao
-- 
http://www.dstoecker.eu/ (PGP key available)