You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The closed issue QGIS-Field calculator missing trees resolved that issue but left several other blank areas on my map. By using Identify Features I determined that these had multiple values in descriptiveTerm or descriptiveGroup, for example descriptiveTerm Rough Grassland, Scrub.
Using the same technique as the one that resolved the missing trees issue, I replaced "descriptiveTerm" ~ with array_contains(descriptiveTerm, and added the necessary closing bracket. For example WHEN "descriptiveTerm" ~ 'Rough Grassland' THEN 23
was replaced with WHEN array_contains(descriptiveTerm, 'Rough Grassland') THEN 23
and likewise for descriptiveGroup, in both the style_code and style_description SQL code. This has resulted in a lot fewer blank spaces on the map. I have attached my code - you will see I did not change everything, I was being cautious.
The closed issue QGIS-Field calculator missing trees resolved that issue but left several other blank areas on my map. By using Identify Features I determined that these had multiple values in descriptiveTerm or descriptiveGroup, for example descriptiveTerm Rough Grassland, Scrub.
Using the same technique as the one that resolved the missing trees issue, I replaced
"descriptiveTerm" ~
witharray_contains(descriptiveTerm,
and added the necessary closing bracket. For exampleWHEN "descriptiveTerm" ~ 'Rough Grassland' THEN 23
was replaced with
WHEN array_contains(descriptiveTerm, 'Rough Grassland') THEN 23
and likewise for descriptiveGroup, in both the style_code and style_description SQL code. This has resulted in a lot fewer blank spaces on the map. I have attached my code - you will see I did not change everything, I was being cautious.
I hope others find this useful.
topographicarea_SQL_style_code.txt
topographicarea_SQL_style_description.txt
The text was updated successfully, but these errors were encountered: