-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fill_colour in add_polygon not correct when stroke_colour is not defined #287
Comments
fill_colour
in add_polygon
not correct when stroke_colour
is not defined
ok, this is caused by the const polygonLayer = new deck.PolygonLayer({
...
extruded: true
...
}); When this is set to I can make this work for non-extruded polygons from within R, but I think the colouring issue lies with deck.gl. I'll make a reprex and post an issue on their github. |
It also might have to do with the lighting effects, which I haven't fully explored yet ( #174 ) mapdeck(
, style = mapdeck_style('dark')
) %>%
add_polygon(
data = sf
, fill_colour = "#ffffffff"
#, stroke_colour = "#ffffffff"
, elevation = 2000
) |
this commit should solve the imediate issue. |
Thanks for the quick action! From my side, this is solved. |
When using
add_polygon
and only definingfill_colour
the resulting colour seems not correct (should be white).However, when we also define
stroke_colour
it renders correctly (in white)I realised this behaviour when testing mapview with mapdeck for
add_pointcloud
. Given thatadd_pointcloud
does not have astroke_colour
argument, I haven't found a way to get the proper colour representation foradd_pointcloud
.The text was updated successfully, but these errors were encountered: