Timeline for QGIS expression: when using overlay_nearest sometimes a feature considers itself its nearest neighbour
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2023 at 13:23 | answer | added | Taras♦ | timeline score: 3 | |
| Dec 13, 2022 at 20:28 | history | edited | Matt | CC BY-SA 4.0 |
removed unnecessary attribute field from example data table
|
| Feb 17, 2022 at 21:58 | history | became hot network question | |||
| Feb 17, 2022 at 15:04 | vote | accept | Matt | ||
| Feb 17, 2022 at 15:03 | answer | added | pigreco | timeline score: 6 | |
| Feb 17, 2022 at 15:00 | history | tweeted | twitter.com/StackGIS/status/1494325784953049101 | ||
| Feb 17, 2022 at 14:52 | comment | added | Matt |
Ah, thank you. I thought it was caused by the way I was filtering. If you want to make an answer, I can accept it. I was thinking a workaround could be to check the fid and if it matches, take the second array element instead of the first. Seems horribly hacky though.
|
|
| Feb 17, 2022 at 14:46 | comment | added | pigreco | the overlay_nearest function and others, respond badly if used with the same layer, here bug: github.com/qgis/QGIS/issues/47201 | |
| Feb 17, 2022 at 14:11 | history | edited | Matt | CC BY-SA 4.0 |
improved expression formatting
|
| Feb 17, 2022 at 14:04 | history | edited | Matt | CC BY-SA 4.0 |
improved expression formatting
|
| Feb 17, 2022 at 13:59 | history | edited | Matt | CC BY-SA 4.0 |
added 107 characters in body
|
| Feb 17, 2022 at 13:54 | history | asked | Matt | CC BY-SA 4.0 |