Lat/Long Precision Issue

[4one4]

Is there a precision limit on a lat/long query? I'm passing in coordinates for Missoula, MT, but it seems like the precision is getting truncated and I'm getting weather returned for Clinton, MT (which is about 15 miles down the road).

So for example: query=46.872146,-113.9939982
I would expect that to provide weather for Missoula, but the JSON returned shows that the query is, "Lat 46.87 and Lon -113.99". The truncation of the coordinates is causing inaccuracy in the city returned.

[gmcmicken]

I think it's worse than just a truncating problem..

For example I am passing: "48.48,-123.31" which is Victoria (Saanich), BC, Canada. But the response I'm getting is very far away.

"name":"Old Town",
"country":"United States of America",
"region":"Washington",
"lat":"48.151",
"lon":"-123.150"

[gmcmicken]

from their support:

Aleksa (apilayer)
Jan 29, 2021, 11:59 GMT+1

Hi Graham,

Thanks for the message - that's a bug on our end, we are working on fixing it.
For now, querying by lat / long will give you a rough location.

Best regards,
Aleksa
Customer Service

[twwilliams]

We have been seeing the same problem with low-precision responses from the API.

[jmemaxwell]

I too am experiencing incorrect results based on Lat/Lng values.

In my example, I am searching with Lat/Lng values for Dallas, TX and the results I am getting back are for Fruitvale, TX. That is over 1 hour away? Weather reporting stations are guaranteed to be in Dallas, TX - so why it is returning a location over an hour away is surely a bug.

Input:
Dallas, TX
32.776
-96.797

Result:
Fruitvale, TX
32.707
-96.769

The temperature difference is currently 8 degrees different, cloudy in Dallas, and Sunny in Fruitvale! We require the weather to be accurate for our customers and clients - especially for a paid service. Please resolve this asap!

[jessupjs]

Thanks for starting this tread - we are also concerned about the input / output results. Does the returned lat and lon represent the query or the closest weather station?

Many thanks!

[jmemaxwell]

From what I can tell, this is just a botched geocode result. I have attempted to enter in direct Lat/Lng values for known weather reporting stations and they are all inaccurate.

Some input from WeatherStack would be appreciated on this... ETA on when it will be fixed? This issue was opened 20 days ago and no resolution yet from a paid service?

[gmcmicken]

I suggest everyone here make a support ticket with this issue so they know people are affected. They do not monitor GitHub it seems.

[jmemaxwell]

I switched over to attempt to use the query - but again, pretty poor results.

St. Louis, MO, USA -> returns St. Louis Senegal
Quebec City, QC, CA -> returns Clarke City (7.5 hours away)

Different variations on those queries return the same results.

They boast 75k companies using their service, but I find that hard to believe based on the results we are seeing. We are also paying for their Professional Level API.