Can the QuickOSM QGIS plugin be used with Overpass QL (rather than xml)?

Question

The QuickOSM plugin for QGIS can support users with the generation of new Overpass queries (for beginners on Overpass like me). It does this using the xml query language. I'd like to also be able to use this plugin with the alternative Overpass QL format. So far I've failed to do this despite having working queries on Overpass-turbo.

Can the plugin support the alternate language. Could I see a couple of queries - written for the plugin specifically - which work so I can base new queries on this?

The main reason for asking is that the answers I've been getting as I learn to use Overpass tend to be in Overpass QL.

Answer 1

Yes, QuickOSM can execute an OQL query.

Even if QuickOSM generates XML and the OQL is not colored, QuickOSM forwards the query to Overpass so it should work.

I tried to run the query from the other post:

[out:json][timeout:90];
rel["route"="bicycle"](51.4177274438, 0.259382751254,51.553418261,0.0539556851102);
way(r);
way._["surface"="paved"];
out geom;

I got the error :

The order must be node-way-relation. Check the print statement.

For your information, in your query, you are using:

[out:json]

OGR can't read JSON, so QuickOSM will change on-the-fly to

[out:xml]

Most of the time, it doesn't matter. But in the XML format, you should notice 3 categories : node, way and relation. Only nodes contain geographic informations. So ways relies on nodes. Relations relies on ways and nodes. In the JSON format, the way has its own geometry.

To fix your problem, you can't request only ways in your query. You need to add a recurse down statement to fetch nodes which are part of ways:

[out:json][timeout:90];
rel["route"="bicycle"](51.4177274438, 0.259382751254,51.553418261,0.0539556851102);
way(r);
way._["surface"="paved"];
(._;>;);
out geom;

Answer 2

I tried with the Overpass Turbo Wizzard output for amenity=bench on an extent of 6.50876 to 6.56241 East and 51.3721 to 51.3915 North:

/*
This has been generated by the overpass-turbo wizard.
The original search was:
“amenity=bench”
*/
[out:json][timeout:25];
// gather results
(
  // query part for: “amenity=bench”
  node["amenity"="bench"]({{bbox}});
  way["amenity"="bench"]({{bbox}});
  relation["amenity"="bench"]({{bbox}});
);
// print results
out body;
>;
out skel qt;

which results in

Successful query, but no result.

Running Generate query results in:

“amenity=bench”
*/
[out:json][timeout:25];
// gather results
(
  // query part for: “amenity=bench”
  node["amenity"="bench"](51.3720747317,6.50876494726,51.3915180471,6.50876494726);
  way["amenity"="bench"](51.3720747317,6.50876494726,51.3915180471,6.50876494726);
  relation["amenity"="bench"](51.3720747317,6.50876494726,51.3915180471,6.50876494726);
);
// print results
out body;
>;
out skel qt;

which the plugin does not like at all: Bad request OverpassAPI

Quick Query in the plugin with amenity=bench returns values, as well as going back to Overpass Turbo via the icon in the plugin.

So I think it is NOT working (at least not in an easy way) with the current plugin version 1.3.4.