nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Add "limit number of results" to the Near Me widget

DavidEgginton

When configuring the Near Me widget in Experience Builder it would be useful to be able to limit the number of results, just as you could in Web AppBuilder's Near Me widget. I would hope this could be implemented in one of two ways.

Firstly, to not have the strict requirement to search by a distance. An option to simply return the X closest features (including an approximate distance) to my specified location would be really useful.

Otherwise, a change to the 'Closet Feature' Analysis Type whereby you can specify how many closet features you would like returned. There is laughably already a toggle to display 'Feature count -- Show number of features returned' even though it is only capable of returning 1 feature. This analysis type is currently incredibly limited in it's actual usefulness and has an extremely limited scope of use.

I know there are already ways to achieve this results limiting effect by linking the Near Me widget to the Query widget or the List widget for example, but these are more of a workaround due to this missing functionality rather than a preferable option.

Trouver plus de publications taguées avec

ArcGIS Online

Widget

Status: Ouvrir

Réponses

AzizaParveen1

Hi @DavidEgginton ,

We have plan to add an option to return the true closest feature (without buffer) to a specified location and we are currently working towards adding the server side functionality . At the current moment, we calculate distance at the client side which can be performance heavy when there are large number of features in the layer.

In Near Me Proximity returns more than one results, we will see if we can add option there as well to return X number of features without any specified search distance.

I will update this thread once we make progress on this issue.

Thank you for sharing your idea with us.

Aziza

DavidEgginton

Thank you @AzizaParveen1 , that all sounds very promising!

AzizaParveen1

Hi @DavidEgginton ,

For your use case/workflow, will it work if we just provide 2 configuration options

1) A toggle to allow Near me to return closest features without search distance

2) A toggle to limit returned results, when enabled will show a text box to input number of desired results.

or you need the same settings to show up at runtime so end user can control whether they want closest and/or proximity to find features without buffer?

DavidEgginton

Hi @AzizaParveen1 ,

Yes, having both of those configuration options would be ideal.

It would be good for option 1 to have the same text box you mention in option 2 too so you can input the number of desired results.

Additionally, it's important that you can include (toggle) an approximate distance for each of these options.

Lastly, including the same settings to show up at runtime so that end users can control it is a really good idea, and whilst it wouldn't be required for our case/workflow, I think that would be a welcome addition for some users.

Rejoindre la conversation

Connectez-vous pour publier, suivre du contenu, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.