You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cross posting CartoDB/carto.js#2237 , which appears to be a Windshaft feature request and not a carto.js feature request. Here is the original issue for context:
Context
A customer would like to apply a shape filter (circle, polygon) to a dataview. The customer believes that we can extend bounding box filtering to irregular polygons and circles. See their comments here:
the problem I’m facing is to apply a shape filter (circle, polygon) to a dataview. I’m aware you can change the sql on the source, but this affects how the layer is displayed. We need to have the layer unmodified on screen, then the user draws a shape, and some data from a dataview is returned based on that shape, without affecting the source. I opened this question on SO:
There is a way to achieve this through the dataviews?
Checking the carto 4.1.12-1, the line 19290 is where the code for boundingbox is declared. Probably will not be a huge enterprise to extend this to accept an array on lat/lngs. It is possible for your team to add this poly support? Or at least someone can guide me a little bit, so I can write the code to support the polygons? This is something very important for us. Later in the future a support for a circle would be great too.
Support Issue and Zendesk tickets for more context
CartoDB/support#2202
The text was updated successfully, but these errors were encountered:
Cross posting CartoDB/carto.js#2237 , which appears to be a Windshaft feature request and not a carto.js feature request. Here is the original issue for context:
Context
A customer would like to apply a shape filter (circle, polygon) to a dataview. The customer believes that we can extend bounding box filtering to irregular polygons and circles. See their comments here:
Support Issue and Zendesk tickets for more context
CartoDB/support#2202
The text was updated successfully, but these errors were encountered: