I can use a workflow computation to update an Item, taking it’s point geometry then buffering this into a circle based on a radius and editing the Item to insert this large circle into another attribute. This attribute then get’s passed into a report as a Data Source and used as a parameter in an AQS query.
Is there a way to shorten this whole process so that the AQS Data Source does the buffering, thereby negating the need for a holding attribute?
Hey Chris,
The above sounds like we could try and do something a little nicer here for the experience. A suggestion would be we look to extend AQS functionality with a new “Buffer” node that would allow you to “buffer” a geometry by a number of metres defined at query time. e.g.
{
"type": "Query",
"properties": {
"collectionCode": "Live",
"dodiCode": "designInterfaces_assets"
},
"children": [
{
"type": "GeomWithin",
"children": [
{
"type": "Attribute",
"properties": {
"attributeCode": "attributes_itemsGeometry"
}
},
{
"type": "BufferGeometry",
"properties": {
"distance": 50 // 50m
},
"children": [
{
"type": "Geometry",
"properties": {
"value": {
"type": "Point",
"coordinates": [-1.528451, 52.291276]
}
}
}
]
}
]
}
]
}
This way you could use an AQS parameter (the existing point geometry) without having to compute and store the “Buffered Geometry”.
If this sounds useful then I suggest opening an idea for it so our product team can track it. Great stuff though 