Reverse Geocoder

Permanently deleted user

15. April 2016 14:13

Hi all,

 

I am trying to set up a reverse geocoder in the Map Context Menu (right-click). I am running the HTML5 2.6 viewer in Essentials 4.6.

 

My geocoding service is set as the 'Default Reverse Geocoder' in the site and I have the option to 'Show Reverse Geocoder' enabled in the viewer.

 

All I get is 'No address found' when I right-click on the map. My geocoding service works great from the global search, as well as a reverse geocoder in ArcMap.

 

Any Suggestions?

 

Thanks

0

• 

  Nico Burgerhart

  15. April 2016 15:01

  It's possible you are clicking on a location where no address are available.

   

  Check with the developer tools of your browser which request is done.

   

  You should find a reverseGeocode request like e.g. http://services.arcgisonline.nl/arcgis/rest/services/Geocoder_BAG_RD/GeocodeServer/reverseGeocode?location={%22x%22%3A169931.01541767822%2C%22y%22%3A519758.1529608207%2C%22spatialReference%22%3A{%22wkid%22%3A28992}}&distance=1000&f=json Copy/paste the URL in your browser and check the results.

  0
• 

  Permanently deleted user

  15. April 2016 15:34

  I noticed the same thing after installing the final release version today.

   

  There was an identified bug in the 2.6 beta that I found but unfortunately the beta forum is closed so I no longer have access to the bug tracking number.

   

  From what I recall, the viewer is expecting to always see a MATCH_ADDR property returned in the reverse geocode response.

   

  None of our locator services do this (v9.3.1, 10.05, 10.2.2).  I was told that they were going to change the code to look for either the address or location object (can't recall which) instead since those are always returned with a successful reverse geocode.  It appears that perhaps this was not fixed in the 2.6.0 release which is disappointing but perhaps it will be included in the maintenance release in May.

  0
• 

  Permanently deleted user

  15. April 2016 15:38

  Hi Nico, 

   

  Thanks for that.

   

  I checked out the developer tools in Chrome and it didn't fix this problem, but I noticed another error and fixed it. So much appreciated.

   

  Dave

  0
• 

  Permanently deleted user

  15. April 2016 15:39

  Hi Peter, 

   

  That would make sense for us as well. Thanks for the info.

   

  Here's hoping they have a fix for the May maintenance.

   

  Dave

  0
• 

  Permanently deleted user

  15. April 2016 16:45

  Hi Dave -

   

  As Peter discussed in his post above, the original logic for the map context menu's address field was originally populated from the MATCH_ADDR field returned in the reverse geocoder's response for the identified location.

   

  Peter's service was returning a valid response with valid address information but no MATCH_ADDR field.  Accordingly, the "No Address Found" message was used to populate the map context menu's address field rather than valid address information.

   

  For 2.6.1, this logic has been changed.  If a MATCH_ADDR field is present, then that information will be directed to the map context menu.  Otherwise, the elements of a valid response's address object are parsed and directed to the map context menu.

   

  We regret that this code change could not be included in GVH 2.6, but we are excited that it will be included in the first maintenance release (GVH 2.6.1).

   

  Regards,

   

  Steve Chapman

  0
• 

  Permanently deleted user

  15. April 2016 17:00

  For everyone's reference, the issue number was GVH-10076.

   

  Regards,

   

  Steve Chapman

  0
• 

  Permanently deleted user

  15. April 2016 22:14

  Thanks Steve

   

  Looking forward to the fix

   

  Dave

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.