query-overpass vs overpass turbo: different resultset for the same query
See original GitHub issueHi,
when I run this query via http://overpass-turbo.eu/, I receive cca 5 ways:
[out:json];way(around:100,48.1570,17.1326)["name"]["highway"];out;
However when I run the same query from nodejs via query-overpass, I receive empty resultset.
code:
queryOverpass = require('query-overpass');
queryOverpass('[out:json];way(around:100,48.1570,17.1326)["name"]["highway"];out;', function(error, geojson){
console.log(error);
console.log(geojson);
});
result:
{ type: 'FeatureCollection', features: [] }
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
OSM Overpass API / pbogden - Observable
This notebook uses the API to extract a small amount of OSM data. Choose one of the prepackaged queries, or type of your...
Read more >Is there a way to get results for an overpass query paginated?
Let's say this result set is too big to extract in just one request to overpass. I would like to be able to...
Read more >Why are area queries in my own Overpass server returning ...
This has really nothing to do with "Overpass Turbo", as it is a web frontend rather than the database backend. I tried different...
Read more >Overpass API/Overpass QL - - OpenStreetMap Wiki
Overpass QL (short for "Overpass Query Language") is the second query language created for the Overpass API, the first being Overpass XML. Overpass...
Read more >OSM Overpass API: SQL for Geography - Medium
It stands for a “Way” and not really a “node”. This is the reason why our query is not picking it up. Spend...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@iOiurson you’re not loading the search area before using it to query amenities. You should add
area(3600007405)->.searchArea;
before the first(
in your query.Note that the double curly braces are an extension that only overpass turbo understands, so you have to export your query first (in overpass turbo: export->query->as text) to convert the stuff in
{{}}
to something that Overpass API understands.My bad, it works, it had nothing to do with the package… Thanks again !