I've been building a new web application using GeoNames for the past few months. It's been great and gives me exactly what I need. I've been using the free version for now, but with intention for premium once we scale.
The past couple weeks I've had some weird issues, though. Was hoping it was just a blip at the time.
My API call of getting nearby postal codes is actually randomly returning different result sets with the exact same endpoint and parameters. It's causing our soft-launch to have a lot of bumps due to it. Can someone help me out here? Below is the endpoint and params being used, and attached is screenshots of when I get different results. I just sit and refresh the page and eventually it gives different results.
The endpoint isn't changing, but is there something I'm doing wrong? It seems like every so often the endpoint is changing where it's getting results from.
we are deploying new data for Canada which covers all letters of the code and not only the first part. Depending on which server is answering your request you may already get the full result.
If you only want the first letters you can add isReduced=true to your search params.
I figured the isReduced param may be a fix but when I use it I get the exact same problem. Sometimes it returns a single result and sometimes it returns the result set I expect.
I assume this is also related to the other issue where it's depending on which server is replying with the answer.
These very different results are causing some problems in our production environment. Is there an ETA of when the servers will be done loading Canada data and there won't be a 50/50 on which result set I'm getting?