Skip to main content
Solved

Inaccurate reverse geocoding (using HERE geocoder) >1km off


Forum|alt.badge.img

Hi all,

I'm having issues working with the Geocoder transformer.

 

I'm using the HERE geocoding service to reverse geocode : e.g. 51.9237996084706, 4.486035956925605

The result shown in the Data Inspector show:

 

51.9161, 4.4784 - which is about 1km off.

How can I fix this?

Thanks,

Ed

Best answer by nathanatsafe

Hi @edhere, @Mark2AtSafe and others,

This issue is on my radar and I just wanted to follow up a bit.

 

After some investigating, we've found that the search radius parameter (HERE documentation) accounts for the difference between the two results. Our request through the Geocoder is something like this, while something like this is needed to obtain your results.

 

In light of some overhauls to the Geocoder for 2018, it looks like we can incorporate the radius parameter going forward, and we expect to have this functionality ready sometime around 2018.1. I'll be happy to post here on any further developments, and be sure to let me know if there are any further questions or concerns about this issue.

 

Best,

 

Nathan

View original
Did this help you find an answer to your question?

10 replies

redgeographics
Celebrity
Forum|alt.badge.img+46

Could you also post the Geocoder settings?

I would imagine a specific address coming out of it rather than this general "city centre", does this happen with all coordinates you try or just this one? Could it be a limitation of the HERE geocoding service?


Forum|alt.badge.img
  • Author
  • June 30, 2017

@redgeographics

Hi, the image should be working now.

 

 

The settings I'm using:

I'm having the same issues with other sets of coordinates, the difference between input latlongs and output varies between 300m - 1000m.

When I put in the same coordinates in the HERE reverse geocoder API I do get the correct results back:

Cheers,

Ed


Forum|alt.badge.img
  • Author
  • July 4, 2017

Hi,

Are there any SAFE people able to help me out with this issue?

Thanks,

Ed


david_r
Evangelist
  • July 4, 2017

Just an idea, but you could use something like Fiddler to inspect the calls FME makes to the Bing geocoder to verify what's going on behind the scenes. That might help you see if it's a problem with FME or with Bing.


mark2atsafe
Safer
Forum|alt.badge.img+41

Hi @edhere

I'll have our developer take a look at this.

If I have it correct, you are reverse-geocoding 51.9237996084706, 4.486035956925605

Using FME+HERE it returns 51.9161, 4.4784

Using the HERE API directly returns 51.9238, 4.48604

There are limitations with HERE's reverse geocoding in that it only resolves down to the 'district' and only returns 5 decimal places of precision, but it doesn't seem to be the issue here. I'll check into it and get back to you as soon as I can.

Regards

Mark


Forum|alt.badge.img
  • Author
  • July 5, 2017
mark2atsafe wrote:

Hi @edhere

I'll have our developer take a look at this.

If I have it correct, you are reverse-geocoding 51.9237996084706, 4.486035956925605

Using FME+HERE it returns 51.9161, 4.4784

Using the HERE API directly returns 51.9238, 4.48604

There are limitations with HERE's reverse geocoding in that it only resolves down to the 'district' and only returns 5 decimal places of precision, but it doesn't seem to be the issue here. I'll check into it and get back to you as soon as I can.

Regards

Mark

Hi @Mark2AtSafe

Yes, those are the correct values mentioned.

Thanks for taking a look!

Best,

Ed


nathanatsafe
Safer
Forum|alt.badge.img+7
  • Safer
  • Best Answer
  • February 15, 2018

Hi @edhere, @Mark2AtSafe and others,

This issue is on my radar and I just wanted to follow up a bit.

 

After some investigating, we've found that the search radius parameter (HERE documentation) accounts for the difference between the two results. Our request through the Geocoder is something like this, while something like this is needed to obtain your results.

 

In light of some overhauls to the Geocoder for 2018, it looks like we can incorporate the radius parameter going forward, and we expect to have this functionality ready sometime around 2018.1. I'll be happy to post here on any further developments, and be sure to let me know if there are any further questions or concerns about this issue.

 

Best,

 

Nathan


Forum|alt.badge.img
  • Author
  • February 16, 2018
nathanatsafe wrote:

Hi @edhere, @Mark2AtSafe and others,

This issue is on my radar and I just wanted to follow up a bit.

 

After some investigating, we've found that the search radius parameter (HERE documentation) accounts for the difference between the two results. Our request through the Geocoder is something like this, while something like this is needed to obtain your results.

 

In light of some overhauls to the Geocoder for 2018, it looks like we can incorporate the radius parameter going forward, and we expect to have this functionality ready sometime around 2018.1. I'll be happy to post here on any further developments, and be sure to let me know if there are any further questions or concerns about this issue.

 

Best,

 

Nathan

Hey @NathanAtSafe,

 

 

Thanks for looking into this issue and following up.

 

Please keep me posted on this.

 

 

Best regards,

 

Ed

Forum|alt.badge.img
  • Author
  • April 20, 2018
nathanatsafe wrote:

Hi @edhere, @Mark2AtSafe and others,

This issue is on my radar and I just wanted to follow up a bit.

 

After some investigating, we've found that the search radius parameter (HERE documentation) accounts for the difference between the two results. Our request through the Geocoder is something like this, while something like this is needed to obtain your results.

 

In light of some overhauls to the Geocoder for 2018, it looks like we can incorporate the radius parameter going forward, and we expect to have this functionality ready sometime around 2018.1. I'll be happy to post here on any further developments, and be sure to let me know if there are any further questions or concerns about this issue.

 

Best,

 

Nathan

Hi @NathanAtSafe / @Mark2AtSafe

 

 

I've downloaded the 2018.1.0.0 beta and decided to go back and have a look.

 

Using the Geocoder an leaving the Radius (m) field empty results in the incorrect location.

 

With the Radius (m) field set to 20 the Geocoder returns the proper address: Meent 20 in Rotterdam.

 

 

It seems it the issue is fixed!

 

 

 

Best regards,

 

 

Eduard

 


nathanatsafe
Safer
Forum|alt.badge.img+7
edhere wrote:
Hi @NathanAtSafe / @Mark2AtSafe

 

 

I've downloaded the 2018.1.0.0 beta and decided to go back and have a look.

 

Using the Geocoder an leaving the Radius (m) field empty results in the incorrect location.

 

With the Radius (m) field set to 20 the Geocoder returns the proper address: Meent 20 in Rotterdam.

 

 

It seems it the issue is fixed!

 

 

 

Best regards,

 

 

Eduard

 

That's great news @edhere! It looks like the fix passed our quality control mid-March and it has made its way into the latest builds. Please keep us informed of any further issues you might run into with our HERE Geocoding.

 

 

Best,

 

Nathan

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings