Closed nikita03565 closed 3 years ago
Hi @nikita03565 ,
Yes that's exactly the idea of issue 51. I am ok with limiting the number of shapes, even to 1 for a given layer.
One question regarding implementation: if I understood well, the shape is stored in local storage, right? What happens if we try to apply this new shape filtering on different layers? We will always have the same selected shape? (not saying this is bad, just making sure I understand)
Hi @nikita03565 ,
Yes that's exactly the idea of issue 51. I am ok with limiting the number of shapes, even to 1 for a given layer.
One question regarding implementation: if I understood well, the shape is stored in local storage, right? What happens if we try to apply this new shape filtering on different layers? We will always have the same selected shape? (not saying this is bad, just making sure I understand)
yea, the shape will be applied to all layers
closes #51 Not sure that this is what was meant in the issue but i needed this for my purposes so here we are
Added super basic geoman support: drawing and removing of rectangles in order to limit nodes/relationships in queries like so
minLat < node.lat < maxLat and minLon < node.lon < maxLon
. This helps when there are so many objects so app starts freezing. But this doesn't work great, I tried it with 4 rectangles and my neo4j crashed with out of memory error and it only had ~1800 nodes and ~1800 relationships :thinking: Perhaps I can allow only 1 or 2 rectangles and add editing/moving support, it won't be difficult