@ShanaBritt thanks for the reply! And sorry, because my previous post wasn't clear. The situation is this: we have a web app that residents can use to request service from our city. They specify the location of the service request by dropping a pin on a map. Dropping a pin triggers a reverse geocode to get the "closest" address. The geocode service we call uses a locator with three reference layers: address points, street centerlines, and park polygons. Park polygons are included as the POI type because we want any pin dropped within the park to be tied to the official park address. That works as expected. However, we have a few edge cases where residents drop pins outside the park, but the reverse geocode call still returns the park address. We think that's because the parks in the edge cases are very small, and their centroid is less than 25 meters from the perimeter of the park, which is the search tolerance for the POI centroid feature type. Hopefully that makes more sense. Is there a way to avoid returns from the park polygon centroids when pins are dropped outside the parks?
