Open MarcSkovMadsen opened 3 years ago
The solution is to drop the tiles which restrict access. Its not that this wasn't documented, it's that the tile provider changed their policy.
It's getting pretty bad, dropping Carto, Stamen, and Wikipedia is a pretty big loss.
Looks like Carto/Stamen break only when using https, so maybe there is a fix for those.
In some sense it's a sign of success, with map usage on the web growing beyond the capability of individual map providers to handle the bandwidth. I'm not sure what the solution is; our own projects' usage is probably nowhere near high enough to be of concern, and so we could consider offering some mirror that always allows access from our projects, but it's hard to justify paying for that ourselves for an open-source project, same as for the map providers.
I am trying to deploy an app based on Panel, HoloViews and GeoViews. See https://github.com/MarcSkovMadsen/load-forecasts/blob/main/app_code.py to binder. But the Tile does not display.
@philippjfr explains me this is not Panel, HoloViews or Bokehs fault. It's the Tile provider which restricts access. https://github.com/holoviz/panel/issues/2078
This is simply confusing for a "simple" user like me not used to working with geo data.
Furthermore the HoloViews Tiles documentation does not mention that the Tiles cannot be used in production. Furthermore the Tiles documentation looks like it is full of error to a "simple" user like me. This lowers the confidence in HoloViews.
Solution
Improve documentation by explaining the problem and providing a solution if possible.