Timeline for Syntax for "fields to keep" of Intersection tool in graphical modeler
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 1, 2020 at 12:00 | history | tweeted | twitter.com/StackGIS/status/1267425687503331328 | ||
| Sep 2, 2018 at 11:50 | vote | accept | L.Blanc | ||
| Sep 2, 2018 at 11:47 | history | edited | underdark | CC BY-SA 4.0 |
Removed tag prefix from question title as per Jeff Atwood style preference
|
| Sep 2, 2018 at 0:10 | comment | added | L.Blanc | Hi @csk, thanks for your help! I tried your suggestion with the vector field input. I really would appreciate this solution because the model would become more userfriendly by this for other people. Unfortunately i also don't get it done with this. I have tried a lot now with vector-field-inputs in the modeler field calculator as well as in the modeler intersection tool. But in general, adressing a vector-input field as a varialbe seems to be tricky in the modeler. | |
| Sep 1, 2018 at 22:50 | answer | added | ndawson | timeline score: 7 | |
| Sep 1, 2018 at 22:47 | comment | added | csk |
If you define a Vector Field input, you can select that field from the drop down menu. I have two field inputs designed, field1 and field2. When I type field1, field2, it allows me to click OK without giving me an error. I haven't fully tested that the tool runs as expected, though.
|
|
| Sep 1, 2018 at 18:42 | comment | added | L.Blanc |
Yeah i tried this version ['attribute1', 'attribute2',...] before. It doesn't work for me. I also tried your suggested workaround with the drop field(s) algorithm, but there i get the same problem. I don't get the syntax right for more than one attribute field. With just one field, it works without brackets and without any quotation marks, just the name of the attribute in the input line. But with more than one field, it doesn't work with or without marks or brackets. Or do i have to define the fields-to-keep in the intersection or drop-process by an additional input-variable?
|
|
| Sep 1, 2018 at 17:35 | comment | added | csk |
Did you try ['attribute1', 'attribute2', ...]? If that doesn't work, here's a workaround: run intersection with the default setting of "keep all fields." Add a step to your model, remove unwanted fields with the drop field(s) algorithm.
|
|
| S Sep 1, 2018 at 16:21 | history | edited | L.Blanc | CC BY-SA 4.0 |
correction of spellings,grammatical error fixed, improved formatting
|
| S Sep 1, 2018 at 16:21 | history | suggested | Maxima | CC BY-SA 4.0 |
correction of spellings,grammatical error fixed, improved formatting
|
| Sep 1, 2018 at 14:46 | review | Suggested edits | |||
| S Sep 1, 2018 at 16:21 | |||||
| Sep 1, 2018 at 14:45 | review | First posts | |||
| Sep 1, 2018 at 17:29 | |||||
| Sep 1, 2018 at 14:41 | history | asked | L.Blanc | CC BY-SA 4.0 |