91–100 of 113 posts
Earlier quoted context omitted.
This is exactly my point - however there is nothing clear about the intended use of this map. Former Cartographer - deriding my paying attention you abandon yours.
It shows airport data from OpenStreetMap. It's posted on a site targeted at software developers. Is it that much of a stretch to conclude it's for use by people interested in machine-readable data on airports?
Earlier quoted context omitted.
This is exactly my point - however there is nothing clear about the intended use of this map. Former Cartographer - deriding my paying attention you abandon yours.
It shows airport data from OpenStreetMap. It's posted on a site targeted at software developers. Is it that much of a stretch to conclude it's for use by people interested in machine-readable data on airports?
Is Open Street Map intended for machines to digest and spit out in say a more readable manner?
Academics vs real life = such a wide distinction.
Earlier quoted context omitted.
It's due to what appears to be a bogus error message in the response to https://openairportmap.org/api/airport/KLAX >: "remark": "runtime error: Query timed out in \"query\" at line 6 after 29 seconds." I say bogus error message because for sure that URL did not take 29 seconds to return (221ms according to Firefox). I'd guess the query is malformed and their api interprets the error as a "timeout" instead of "error"
How did you find that API link?
Earlier quoted context omitted.
It shows airport data from OpenStreetMap. It's posted on a site targeted at software developers. Is it that much of a stretch to conclude it's for use by people interested in machine-readable data on airports?
Gosh Eric, maybe something in oh say the TITLE of the webpage may give a clue as to the "intended use case". Is that a stretch to imagine? Is Open Street Map intended for machines to digest and spit out in say a more readable manner? Academics vs real life = such a wide distinction.
Thanks for the casual ad hominem. Interesting take that making practical data available for to anyone is a symptom of ivory tower delusion.
Ultimately, a person wrote a free and useful tool that can be used by anyone, and all you’ve done is deride it.
Earlier quoted context omitted.
How did you find that API link?
Open the developer tools, choose the network tab, click on "XHR" to filter down the noise, type LAX into the search box, and then watch the things that change. After it presented the error message, I looked for things named KLAX in the list, clicked on that row, clicked on the Response pane and saw that silliness