Reverse geocoding fails if the location of a point is greater than 50 meters in distance.
上次发布: December 28, 2021ArcGIS GIS Server
漏洞 ID 编号
BUG-000143278
已提交
September 28, 2021
上次修改时间
June 5, 2024
适用范围
ArcGIS GIS Server
找到的版本
10.7.1
操作系统
Windows OS
操作系统版本
10.0
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
This issue will not be addressed because the reverseGeocode operation is working as expected based on the default search tolerances defined in the hierarchy table (https://developers.arcgis.com/rest/geocode/api-reference/geocoding-reverse-geocode.htm#GUID-FC97069F-310B-44A8-9DD1-8EC188170831) and the data used to build the locator referenced in the bug. When a single featuretypes value is included, then a search tolerance of 500 meters is used and only the input feature type is searched for. More details about choosing specific reverse geocode outputs can be found here, https://developers.arcgis.com/rest/services-reference/enterprise/reverse-geocode.htm#ESRI_SECTION1_8D8C3482DF394FD183CBCBC1DC360A16.
Since the request included more than one feature type, no match results are expected because there were no valid StreetAddress, PointAddress, or StreetInt features within the default search tolerances (StreetInt=10m; PointAddress =50m, StreetAddress(near)=3m; StreetAddress(distant)=100m). When the reverse geocode request includes PointAddress and StreetAddress featureTypes no matches are returned because there are no valid features within 50 or 100 meters of the input location. The street segment FRA26614 intersects the 100m tolerance for a StreetAddress match, but house number range and street name elements are 0 or null. If these attributes were populated then a StreetAddress match would be returned. If featureTypes includes a single value, then a search tolerance of 500 meters is used and only the input feature type is searched for. This is the reason they get results when including only one feature type in their request.