<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<blockquote type="cite">
<div class="msgHead" style="color: rgb(0, 0, 0); font-family:
helvetica, arial, sans-serif; font-size: 14px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-thickness: initial; text-decoration-style:
initial; text-decoration-color: initial;">
<p class="darkgray font13" style="font-size: 13px; color:
rgb(102, 102, 102);"><span class="sender pipe"
style="margin-right: 0.5em; border-right: 1px solid rgb(221,
221, 221); padding-right: 0.8em;"><a
href="https://www.mail-archive.com/search?l=qgis-user@lists.osgeo.org&q=from:%22Simon+Dietmann%22"
rel="nofollow" style="color: rgb(102, 102, 102);
text-decoration: none;"><span itemprop="author"
itemscope="" itemtype="http://schema.org/Person"><span
itemprop="name">Simon Dietmann</span></span></a></span><span> </span><span
class="date"><a
href="https://www.mail-archive.com/search?l=qgis-user@lists.osgeo.org&q=date:20220131"
rel="nofollow" style="color: rgb(102, 102, 102);
text-decoration: none;">Mon, 31 Jan 2022 00:07:19 -0800</a></span></p>
</div>
<div itemprop="articleBody" class="msgBody" style="color: rgb(0,
0, 0); font-family: helvetica, arial, sans-serif; font-size:
14px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-thickness:
initial; text-decoration-style: initial; text-decoration-color:
initial;">
<pre style="font-family: courier, "courier new", monospace; font-size: 1em; white-space: pre-wrap; overflow-wrap: break-word; margin: 0px;">the reason für all the ‘1’ values is obviously that the algorithm seeking for
the nearest points always finds the original point itself. When I first used
the expression that I had suggested as a solution for your problem, this didn´t
happen and the original point wasn´t taken into accont, but when I later tried
it with another point layer, I got the same result as you with ‘1’ for every
point feature.
</pre>
</div>
</blockquote>
<br>
Hi Simon,<br>
as I've written in a previous message, I think a bug occurs when the
overlay_nearest function is used with a Shapefile layer, while the
bug doesn't occur with a Memory or GeoPackage or Spatialite layer.<br>
<br>
Could you please try this:<br>
<br>
- create a new scratch (Memory) point layer<br>
- add a single point to the memory layer<br>
- use the expression overlay_nearest(@layer,$geometry) in the field
calculator for such layer: the preview will show [] (i.e. no nearest
geometry returned)<br>
<br>
- export the memory layer with a single point to a Shapefile layer<br>
- import the Shapefile layer with a single point<br>
- use the expression overlay_nearest(@layer,$geometry) in the field
calculator for such layer: the preview will show [ <span style="
font-style:italic;"><geometry: Point></span> ] (i.e. the
expression incorrectly returns the very some point as the nearest
point)<br>
<br>
- export the memory layer with a single point to a GeoPackage or a
Spatialite layer<br>
- import the GeoPackage or a Spatialite layer with a single point<br>
- use the expression overlay_nearest(@layer,$geometry) in the field
calculator for such layer: the preview will show [] (i.e. no nearest
geometry returned)<br>
<br>
Best regards.<br>
<br>
Andrea Giudiceandrea<br>
</body>
</html>