Regression: RangeXY now provides incorrect longitude x_range

[TheoMathurin]

ALL software version info

I think only hv and gv versions are relevant

geoviews 1.13.0
holoviews 1.19.1

Description of expected behavior and the observed behavior

Potentially a serious regression that breaks a lot of things in my apps.

Assuming a Plate Carree crs, longitudes returned by hv.streams.RangeXY were always given between -180 et 180.

They are now given in the (0, 360) interval when they are both in the western hemisphere.

Complete, minimal, self-contained example code that reproduces the issue

import panel as pn
import holoviews as hv
import geoviews as gv


def print_xrange(x_range, y_range):
    text.object = f'x_range: {x_range}'


coastline = gv.feature.coastline
xy_range = hv.streams.RangeXY(source=coastline)
xy_range.add_subscriber(print_xrange)
text = pn.pane.Str('')

pn.Column(coastline, text).servable()

Stack traceback and/or browser JavaScript console output

No errors

Screenshots or screencasts of the bug in action

Capture.video.du.2024-10-04.16-29-54.mp4

[hoxbro]

Do you know if it is HoloViews or Geoviews release which broke it?

Maybe #722 is the culprit.

[TheoMathurin]

Thanks for the quick response.

I happened to update both at the same time but will investigate.

[hoxbro]

Easier to downgrade holoviews first.

[hoxbro]

Can you comment out these lines:

geoviews/geoviews/plotting/bokeh/callbacks.py

Lines 99 to 102 in 256394b

	if plot._unwrap_lons and -180 <= x0 < 0 or -180 <= x1 < 0:
	x0, x1 = x0 + 360, x1 + 360
	if x0 > x1:
	x0, x1 = x1, x0

[TheoMathurin]

I won't have the opportunity to try before Monday, but looks promising

[TheoMathurin]

Removing these lines does solve the problem!

As an aside, I tried with holoviews 1.18.3 and geoviews 1.13.0 but by default it installed panel 1.5.2 which is not compatible with 1.18.3 it seems:

  File "/home/mathurin/miniconda3/envs/test-range/lib/python3.12/site-packages/holoviews/core/util.py", line 1634, in resolve_dependent_value
    from panel.depends import param_value_if_widget
ImportError: cannot import name 'param_value_if_widget' from 'panel.depends'

[TheoMathurin]

@hoxbro @ahuang11

I don't know how to move forward on this one. I guess the solution is not to remove the lines mentioned above, since the changes brought by #722 had a purpose of their own.

Currently everything relying on RangeXY in PlateCarree CRS is going to be affected, including datashader range updates.

[ahuang11]

@TheoMathurin can you try #756 and see if that fixes your issues?

#756 (comment)