API location returns weird data
First, I should say that having an API at all is a huge task – a big thanks for making this accessible!
I'm trying to query networks from a particular location (in this case New York City) but am getting weird results: networks from all over the USA and even some from Japan and Europe.
I looked up the bounding box using the API to get the latrange and lonrange values and used those, but I also tried manually putting in the location values, all with the same result. This isn't erroneous data either: the city, state, region, and trilat/trilong are all off from what was requested.
Any help would be most appreciated!
I'm trying to query networks from a particular location (in this case New York City) but am getting weird results: networks from all over the USA and even some from Japan and Europe.
I looked up the bounding box using the API to get the latrange and lonrange values and used those, but I also tried manually putting in the location values, all with the same result. This isn't erroneous data either: the city, state, region, and trilat/trilong are all off from what was requested.
Any help would be most appreciated!
Oops! Late-night programming bozo move. I misread the "longrange" as "lonrange" (since latitude is "latrange"). Works now!
hah!
we chose a lot of those parameter names a decade and a half ago, kinda wish we'd used lonrange instead of longrange for consistency's sake!
we chose a lot of those parameter names a decade and a half ago, kinda wish we'd used lonrange instead of longrange for consistency's sake!
Who is online
Users browsing this forum: No registered users and 0 guests