Query Widget/Public Notice Widget

[mkauth_wardgetz]

Hi all. I have followed this 'tutorial' https://www.youtube.com/watch?v=8C9DNPupK2k to configure my Experience Builder query widget.  While it works, the results appear to be wrong. 
I have the spatial relationship set to intersect with a 300 foot buffer. However, the selected parcels go beyond 300 feet from the selected parcel.

Why are my results going beyond 300 feet?

In this screenshot you can see my inputs to the query widget and the measurement (aprox 300ft)

This is the result with the measurement showing parcels that intersected going beyond 300 ft.

[TianWen]

Thanks for the post! I want to clarify that the buffer extends outward from the edges of the feature's boundary by the designated distance, rather than from the center. Additionally, given the intersect relationship rule being used, the feature will be returned as long as any part of it is contained within the buffer area.

[mkauth_wardgetz]

I agree with you @TianWen . While my measurement I provided does start at the center of the polygon, the returned results are still well beyond 300 feet. I checked my results against the Public Notification app (I'm trying to replicate that functionality in ExB) and the results seem to be correct.

[TianWen]

Would it be possible to provide a sample app or dataset?

[mkauth_wardgetz]

Hi @TianWen Try this link, https://wgaportal.wga-llp.com/portal/apps/experiencebuilder/experience/?id=1bff044926884522bb9f0c285...

[TianWen]

Would you also publicly share the data? Thanks!

[mkauth_wardgetz]

Sorry about that. I think it was a setting in the widget. Try this link, https://wgaportal.wga-llp.com/portal/apps/experiencebuilder/experience/?id=1bff044926884522bb9f0c285...

And here is a link to the data I am using - https://services1.arcgis.com/PRoAPGnMSUqvTrzq/arcgis/rest/services/Tax_Parcel_Public_View/FeatureSer...

[TianWen]

Thank you for providing the sample data. We have identified an issue with the spatial reference transformation process in this case and are working to address it promptly. In the meantime, the spatial query should function properly with the drawn graphic approach, serving as a temporary workaround. We apologize for any inconvenience this may cause.