New answers tagged

3

It's because of the last part of the where clause: and ed."studyArea"='yes' Vince beat me to it. As soon as you include WHERE criteria like that on the table on the right side of the join it sort of implicitly becomes an inner join. Think about it: if there is no education point to intersect with the plan object then the value of ed."...


4

Fieldname <> attribute is one way to query. If there are a list you can write a query that is something like fieldname <> attribute1 AND fieldname <> attribute2, or fieldname NOT IN (attribute1, attribute2, attribute3). This will return all values in a field that are not specified as an attribute.


3

Try writing a multiple LIKE statement with the values you're trying in an IN statement. In the image below, there are 2 sets of selected features for each LIKE statement (highlighted in pink): "GEOID" like ('34013000100%') or "GEOID" like ('34013000200%')


3

I figured this out. First you need to create a new field merged_ID in the lot layer, giving a unique ID to each group of polygons to be merged. The attribute table would look like this: Then type the following query in the virtual layer creation window: select st_union(geometry), l.* from "lot" as l group by l."merged_ID"


0

just check out the project healthsites.io Healthsites.io https://healthsites.io/api/docs/ https://github.com/healthsites/healthsites/wiki To build a curated, open data commons of health facility data with OpenStreetMap Supporting objectives Our objective is to publish accessible health sites data to OpenStreetMap that is accurate and complete Accessible ...


Top 50 recent answers are included