Skip to content
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

Deckgl ViewPort on Polygon Layer didnt Update when Filter Set #9463

Closed
drunkenmyno opened this issue Apr 3, 2020 · 1 comment
Closed

Deckgl ViewPort on Polygon Layer didnt Update when Filter Set #9463

drunkenmyno opened this issue Apr 3, 2020 · 1 comment
Labels
inactive Inactive for >= 30 days

Comments

@drunkenmyno
Copy link

A clear and concise description of what the bug is.

Expected results

When a Table is set as Filter for a Polygon Layer.

A Filter is set and the Viewport didnt update.

Error happened

Could not fit viewport Error: @math.gl/web-mercator: assertion failed.

because the Coordiantes are Zero then. after

if (formData.autozoom) {
viewport = fitViewport(viewport, {
width,
height,
points: features.flatMap(getPointsFromPolygon)
});
}

Polygon.js

Actual results

Viewport zooms out to stanrdard 6.85236157047845, 31.222656842808707

How to reproduce the bug

Create a GeoJSON Layer with More then 2 Polygons set a Filter on it.
The Viewport did not update to the Polygon

Environment

  • superset version: latest
  • python version: 3.6.4
  • node.js version: 13
  • npm version: latest

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

  • [x ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • [ x] I have reproduced the issue with at least the latest released version of superset.
  • [x ] I have checked the issue tracker for the same issue and I haven't found one similar.
@drunkenmyno drunkenmyno changed the title ViewPort on Polygon Layer didnt Update when Filter Set Deckgl ViewPort on Polygon Layer didnt Update when Filter Set Apr 3, 2020
@stale
Copy link

stale bot commented Jun 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

1 participant