Holoviews combined with geoviews.tile_sources causes axis scale error
I'm trying to combine a geoviews.tile_sources layer with a datashade layer. Both layers individually result in the correct axis (see image), but when combined (using *) the scale becomes distorted.
import numpy as np
import pandas as pd
import holoviews as hv
from geoviews.tile_sources import EsriImagery
from holoviews.operation.datashader import datashade
hv.extension('bokeh')
lats = np.random.uniform(51.111, 51.222, 10000)
longs = np.random.uniform(1.31, 1.33, 10000)
df = pd.DataFrame({"latitude": lats, "longitude": longs})
points = hv.Points(df, ['longitude', 'latitude'])
shader = datashade(points)
EsriImagery * shader
However, both of the individual plots are correct:
shader + EsriImagery
python bokeh holoviews datashader geoviews
asked Nov 15 '18 at 18:38
wabwab
340212
add a comment |
I'm trying to combine a geoviews.tile_sources layer with a datashade layer. Both layers individually result in the correct axis (see image), but when combined (using *) the scale becomes distorted.
import numpy as np
import pandas as pd
import holoviews as hv
from geoviews.tile_sources import EsriImagery
from holoviews.operation.datashader import datashade
hv.extension('bokeh')
lats = np.random.uniform(51.111, 51.222, 10000)
longs = np.random.uniform(1.31, 1.33, 10000)
df = pd.DataFrame({"latitude": lats, "longitude": longs})
points = hv.Points(df, ['longitude', 'latitude'])
shader = datashade(points)
EsriImagery * shader
However, both of the individual plots are correct:
shader + EsriImagery
python bokeh holoviews datashader geoviews
asked Nov 15 '18 at 18:38
wabwab
340212
add a comment |
I'm trying to combine a geoviews.tile_sources layer with a datashade layer. Both layers individually result in the correct axis (see image), but when combined (using *) the scale becomes distorted.
import numpy as np
import pandas as pd
import holoviews as hv
from geoviews.tile_sources import EsriImagery
from holoviews.operation.datashader import datashade
hv.extension('bokeh')
lats = np.random.uniform(51.111, 51.222, 10000)
longs = np.random.uniform(1.31, 1.33, 10000)
df = pd.DataFrame({"latitude": lats, "longitude": longs})
points = hv.Points(df, ['longitude', 'latitude'])
shader = datashade(points)
EsriImagery * shader
However, both of the individual plots are correct:
shader + EsriImagery
python bokeh holoviews datashader geoviews
asked Nov 15 '18 at 18:38
wabwab
340212
I'm trying to combine a geoviews.tile_sources layer with a datashade layer. Both layers individually result in the correct axis (see image), but when combined (using *) the scale becomes distorted.
import numpy as np
import pandas as pd
import holoviews as hv
from geoviews.tile_sources import EsriImagery
from holoviews.operation.datashader import datashade
hv.extension('bokeh')
lats = np.random.uniform(51.111, 51.222, 10000)
longs = np.random.uniform(1.31, 1.33, 10000)
df = pd.DataFrame({"latitude": lats, "longitude": longs})
points = hv.Points(df, ['longitude', 'latitude'])
shader = datashade(points)
EsriImagery * shader
However, both of the individual plots are correct:
shader + EsriImagery
python bokeh holoviews datashader geoviews
python bokeh holoviews datashader geoviews
asked Nov 15 '18 at 18:38
wabwab
340212
asked Nov 15 '18 at 18:38
wabwab
340212
asked Nov 15 '18 at 18:38
wabwab
340212
asked Nov 15 '18 at 18:38
wabwab
340212
asked Nov 15 '18 at 18:38
wabwab
340212
340212
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
HoloViews elements do no know anything about the coordinate system of your data, while tile sources are defined in a Mercator coordinate system. Therefore when you overlay hv.Points on top of a tile source it assumes your coordinates are already in Mercator coordinates. In order to overlay data situated in different coordinates systems you should therefore use the GeoViews elements, e.g. in your case gv.Points, as described in this user guide. This will ensure that your points are interpreted correctly as lat/lon pairs and can be automatically projected into the same coordinate system as the tile source.
answered Nov 15 '18 at 19:08
philippjfrphilippjfr
1,997611
add a comment |
You're trying to combine a HoloViews object in PlateCarree coordinates with a GeoViews object in Web Mercator coordinates, which differ by a factor of a few million. You can fix it by changing hv.Points() to gv.Points(), which will be a GeoViews object in PlateCaree coordinates that GeoViews will project into the same coordinate system as the tile layer when it's displayed. You can also consider using gv.project_points() to do the projection a single time at the start, rather than the default of re-projecting it each time it's displayed.
answered Nov 15 '18 at 19:12
James A. BednarJames A. Bednar
88635
D'oh! Philipp answered before I hit post...
– James A. Bednar
Nov 15 '18 at 19:13
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325947%2fholoviews-combined-with-geoviews-tile-sources-causes-axis-scale-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
HoloViews elements do no know anything about the coordinate system of your data, while tile sources are defined in a Mercator coordinate system. Therefore when you overlay hv.Points on top of a tile source it assumes your coordinates are already in Mercator coordinates. In order to overlay data situated in different coordinates systems you should therefore use the GeoViews elements, e.g. in your case gv.Points, as described in this user guide. This will ensure that your points are interpreted correctly as lat/lon pairs and can be automatically projected into the same coordinate system as the tile source.
answered Nov 15 '18 at 19:08
philippjfrphilippjfr
1,997611
add a comment |
HoloViews elements do no know anything about the coordinate system of your data, while tile sources are defined in a Mercator coordinate system. Therefore when you overlay hv.Points on top of a tile source it assumes your coordinates are already in Mercator coordinates. In order to overlay data situated in different coordinates systems you should therefore use the GeoViews elements, e.g. in your case gv.Points, as described in this user guide. This will ensure that your points are interpreted correctly as lat/lon pairs and can be automatically projected into the same coordinate system as the tile source.
answered Nov 15 '18 at 19:08
philippjfrphilippjfr
1,997611
add a comment |
HoloViews elements do no know anything about the coordinate system of your data, while tile sources are defined in a Mercator coordinate system. Therefore when you overlay hv.Points on top of a tile source it assumes your coordinates are already in Mercator coordinates. In order to overlay data situated in different coordinates systems you should therefore use the GeoViews elements, e.g. in your case gv.Points, as described in this user guide. This will ensure that your points are interpreted correctly as lat/lon pairs and can be automatically projected into the same coordinate system as the tile source.
answered Nov 15 '18 at 19:08
philippjfrphilippjfr
1,997611
HoloViews elements do no know anything about the coordinate system of your data, while tile sources are defined in a Mercator coordinate system. Therefore when you overlay hv.Points on top of a tile source it assumes your coordinates are already in Mercator coordinates. In order to overlay data situated in different coordinates systems you should therefore use the GeoViews elements, e.g. in your case gv.Points, as described in this user guide. This will ensure that your points are interpreted correctly as lat/lon pairs and can be automatically projected into the same coordinate system as the tile source.
answered Nov 15 '18 at 19:08
philippjfrphilippjfr
1,997611
answered Nov 15 '18 at 19:08
philippjfrphilippjfr
1,997611
answered Nov 15 '18 at 19:08
philippjfrphilippjfr
1,997611
answered Nov 15 '18 at 19:08
philippjfrphilippjfr
1,997611
1,997611
add a comment |
add a comment |
You're trying to combine a HoloViews object in PlateCarree coordinates with a GeoViews object in Web Mercator coordinates, which differ by a factor of a few million. You can fix it by changing hv.Points() to gv.Points(), which will be a GeoViews object in PlateCaree coordinates that GeoViews will project into the same coordinate system as the tile layer when it's displayed. You can also consider using gv.project_points() to do the projection a single time at the start, rather than the default of re-projecting it each time it's displayed.
answered Nov 15 '18 at 19:12
James A. BednarJames A. Bednar
88635
D'oh! Philipp answered before I hit post...
– James A. Bednar
Nov 15 '18 at 19:13
add a comment |
You're trying to combine a HoloViews object in PlateCarree coordinates with a GeoViews object in Web Mercator coordinates, which differ by a factor of a few million. You can fix it by changing hv.Points() to gv.Points(), which will be a GeoViews object in PlateCaree coordinates that GeoViews will project into the same coordinate system as the tile layer when it's displayed. You can also consider using gv.project_points() to do the projection a single time at the start, rather than the default of re-projecting it each time it's displayed.
answered Nov 15 '18 at 19:12
James A. BednarJames A. Bednar
88635
D'oh! Philipp answered before I hit post...
– James A. Bednar
Nov 15 '18 at 19:13
add a comment |
You're trying to combine a HoloViews object in PlateCarree coordinates with a GeoViews object in Web Mercator coordinates, which differ by a factor of a few million. You can fix it by changing hv.Points() to gv.Points(), which will be a GeoViews object in PlateCaree coordinates that GeoViews will project into the same coordinate system as the tile layer when it's displayed. You can also consider using gv.project_points() to do the projection a single time at the start, rather than the default of re-projecting it each time it's displayed.
answered Nov 15 '18 at 19:12
James A. BednarJames A. Bednar
88635
You're trying to combine a HoloViews object in PlateCarree coordinates with a GeoViews object in Web Mercator coordinates, which differ by a factor of a few million. You can fix it by changing hv.Points() to gv.Points(), which will be a GeoViews object in PlateCaree coordinates that GeoViews will project into the same coordinate system as the tile layer when it's displayed. You can also consider using gv.project_points() to do the projection a single time at the start, rather than the default of re-projecting it each time it's displayed.
answered Nov 15 '18 at 19:12
James A. BednarJames A. Bednar
88635
answered Nov 15 '18 at 19:12
James A. BednarJames A. Bednar
88635
answered Nov 15 '18 at 19:12
James A. BednarJames A. Bednar
88635
answered Nov 15 '18 at 19:12
James A. BednarJames A. Bednar
88635
88635
D'oh! Philipp answered before I hit post...
– James A. Bednar
Nov 15 '18 at 19:13
add a comment |
D'oh! Philipp answered before I hit post...
– James A. Bednar
Nov 15 '18 at 19:13
D'oh! Philipp answered before I hit post...
– James A. Bednar
Nov 15 '18 at 19:13
D'oh! Philipp answered before I hit post...
– James A. Bednar
Nov 15 '18 at 19:13
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325947%2fholoviews-combined-with-geoviews-tile-sources-causes-axis-scale-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
