Select to view content in your preferred language

Create Buffer from Selected Features that does not create a portal layer

180
2
03-13-2025 11:43 AM
Status: Open
Labels (2)
CameronLacelle
Frequent Contributor

I want a way for our end users (viewers in Portal) to use our experience builder and create a buffer around a selected feature or more than one features. Currently the only way I see to make buffers is in the analysis widget but this creates portal layers and we do not want our end users creating their own portal layers at this time, especially since most of our end users are viewer roles which i don't believe the analysis widget is compatible with that role type.

The scenario is that our City planners want to search for a parcel (using the query widget), select that parcel, and then select all parcels within 100 metres of the selected parcel (i.e. use the spatial filter component of the query widget). They export the resulting parcels to create mailing lists to notify property owners from their search result.

In this scenario, our users also want to be able to export a PDF map (using the print widget) of the affected area that shows the parcel of interest, the affected parcels (within 100m), and the 100m buffer itself. So far I've been able to configure everything except for actually displaying that buffer on the map without creating a new portal layer, plus in 11.3 the analysis tool doesn't even accept selected layers as an input so the analysis tool is even less useful.

It could be its own buffer widget, an extension of the draw widget where you can draw a buffer around a selected feature (this appears to be something that can be done in the spatial filter component of the query widget where if you apply a buffer to a drawn graphic then it will show that buffer so clearly that is a possibility), or even as an extra action in the Actions menu for a widget called 'create buffer' or something like that.

This is a critical component for our staff and the fact it is not available in Experience Builder means we cannot complete and launch this application for our users, which is aimed at being a replacement of our legacy GIS viewer application that is due for replacement.

2 Comments
Jack_in_the_box

It's disappointing to see that the new program meant to replace the existing one is actually a step backward. It lacks several key tools and functionality that were available before. It feels like a basic principle of programming has been overlooked: don’t remove essential features unless you're improving or replacing them with something better. Please reconsider the direction this is going — users rely on these tools to get real work done.

CameronLacelle

@Jack_in_the_box couldn't have said it better myself. We are trying to use Experience Builder to replace our highly outdated legacy GIS Viewer for our corporation as there is risk it will go down but we keep hitting limitations with Experience Builder when trying to build a 1:1 replacement. Our legacy viewer was also built using open source software so it's disappointing that the most profitable GIS vendor seems to be lacking functionality that open source software has. Let's hope they address these necessities asap because I know others are frustrated as well. Especially with WebAppBuilder getting the axe soon.