Fix dask tiles regression

[ahuang11]

Closes #1431

import dask.dataframe as dd
import hvplot.dask  # noqa
import pandas as pd

data = {"x": [-9700947, -9584977], "y": [3890186, 3824923]}
df = dd.from_pandas(pd.DataFrame(data), npartitions=2)
df.hvplot.points("x", "y", tiles=True)

[hoxbro]

Failing test

[codecov]

Codecov Report

Attention: Patch coverage is 82.60870% with 4 lines in your changes missing coverage. Please review.

Project coverage is 88.93%. Comparing base (b36e3a1) to head (7ca3a78).
Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
hvplot/tests/testgeowithoutgv.py	86.66%	2 Missing ⚠️
hvplot/util.py	71.42%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1432      +/-   ##
==========================================
- Coverage   88.94%   88.93%   -0.01%     
==========================================
  Files          52       52              
  Lines        7751     7775      +24     
==========================================
+ Hits         6894     6915      +21     
- Misses        857      860       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[maximlt]

What do we recommend to users that have a dask dataset with lat/lon coordinates?

[philippjfr]

What do we recommend to users that have a dask dataset with lat/lon coordinates?

Good question, you should still be able to make it project by explicitly requesting it.

[ahuang11]

What do we recommend to users that have a dask dataset with lat/lon coordinates?

Same behavior from <0.11 releases; manually setting crs and projection; not sure if this needs to be explicitly called out though since I do mention "automatically unless..."

If coordinate values fall within lat/lon bounds, auto-projects to EPSG:3857 unless projection=False or if the data is lazily loaded (dask / ibis).

[maximlt]

What do we recommend to users that have a dask dataset with lat/lon coordinates?

Same behavior from <0.11 releases; manually setting crs and projection; not sure if this needs to be explicitly called out though since I do mention "automatically unless..."

If coordinate values fall within lat/lon bounds, auto-projects to EPSG:3857 unless projection=False or if the data is lazily loaded (dask / ibis).

But that still requires GeoViews? If so, maybe there's a way to special case crs="4326" (or some of the other allowed values) so it doesn't use GeoViews. But I'd say that's for another PR, this one was about fixing the regression and it achieved that, thanks.