Skip to main content
Solved

Geocode and OSM Timeout

  • March 18, 2019
  • 2 replies
  • 24 views

Forum|alt.badge.img

Hello,

I have been trying to determine why the Geocoder transformer (using OpenStreetMap source) keeps stalling after ~500 features have been processed. Does anyone know if there is a limit that can be processed?

Thanks

Best answer by redgeographics

In the Advanced parameters there's a timeout and a max number of concurrent requests that you can set. Also take a look at the usage policy for the Nominatim service, it could very well be that you're hitting the limits of the free service after 500 features (assuming you haven't set up your own service)

You can work around that by slowing things down (Decelerator) although the way I understand it you'd still be in violation...

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

redgeographics
Celebrity
Forum|alt.badge.img+60
  • Celebrity
  • 3702 replies
  • Best Answer
  • March 18, 2019

In the Advanced parameters there's a timeout and a max number of concurrent requests that you can set. Also take a look at the usage policy for the Nominatim service, it could very well be that you're hitting the limits of the free service after 500 features (assuming you haven't set up your own service)

You can work around that by slowing things down (Decelerator) although the way I understand it you'd still be in violation...


Forum|alt.badge.img
  • Author
  • 15 replies
  • March 18, 2019

Thank you. This helps. I had not thought of the decelerator and will try that.