Longitude/Latitude not formatted properly (shown as Mercator values) in hover info

[prusswan]

This looks like a regression but I cannot tell if this is caused by geoviews or bokeh. Either way the example looks "wrong".

ALL software version info

(this library, plus any other relevant software, e.g. bokeh, python, notebook, OS, browser, etc) https://geoviews.org/user_guide/Working_with_Bokeh.html

Description of expected behavior and the observed behavior

geoviews: 1.8.1 bokeh: 2.1.1

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

https://geoviews.org/user_guide/Working_with_Bokeh.html

Notice that in the Plotting data example, the Longitude/Latitude values in hover info are shown in Mercator projection and scientific notation

Stack traceback and/or browser JavaScript console output

N/A

Screenshots or screencasts of the bug in action

https://geoviews.org/user_guide/Working_with_Bokeh.html

[jbednar]

I've verified that the hover info in the linked web page isn't correct, and moreover I get the same results for a variety of older versions (bokeh=2.1.1/geoviews=1.8.1, bokeh=2.2.1/geoviews=1.8.1, bokeh=1.4.0/geoviews=1.7.0), so it doesn't look like a recent regression. Not sure what's going on here...

[WesleyTheGeolien]

Not sure if this is linked but the hover data in projected graphs doesn't seem correct either, I'm not sure if the rotation is being taken into account.

In the example below it is a Orthographic projection with the central_latitude set to 90 (North Pole). Notice negative value when going up to the centre of the plot and positive values after. In reality we should be getting closer and closer to 90 the closer we get to the centre of the plot.

[philippjfr]

We have in fact never supported displaying coordinates for arbitrary projections, only for GOOGLE_MERCATOR and PlateCarree since those are the only ones we can handle client-side.