Currently, this doesn't work in the Omnibox: op: historic=* and tourism=* and tourism!=hotel in "Dumaguete City" , which could've return results for tourism-related features in Dumaguete, excluding hotels.

Of course, one may opt to first move the bbox to Dumaguete and run the same query, but the "not equal" to operators are not yet supported.

• != or <> are not currently supported
• the "in ", when added to an Overpass Query, specifies a request to return results from said location.

Probably this query is not something casual users may use often, but supporting "in" is close to the search experience some users may be familiar when using Google, or Bing. See screenshots below.

On the other hand, maybe "attractions" as a preset is nice to have, since we use a variety of tags for this type of POIs in OSM, and could make it more convenient for users to look for this type of information.

Google: "tourism in Dumaguete City"

Bing: "tourism in Dumaguete City"