<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Include search distance option when performing spatial joins in Data Pipelines Ideas</title>
    <link>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idi-p/1405601</link>
    <description>&lt;P&gt;I'm attempting to do a spatial join and unfortunately the 2 input datasets have different spatial references. This means that the 2nd is transformed to match the first. The data should align, but the transformation means there are slight differences. These differences are resulting in features joining that should not when using the "intersects" or "contains" options. In ArcGIS Pro, i frequently add a negative search distance to reduce the chance of overlaps around the edges, but this is not possible (yet) in Data Pipelines.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I even tried the "Near geodesic" option with a negative distance (5 metres) but that results in an error when run/previewed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LindsayRaabe_FPCWA_0-1712215206436.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/99984i78B432F921AA2135/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LindsayRaabe_FPCWA_0-1712215206436.png" alt="LindsayRaabe_FPCWA_0-1712215206436.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;In the screenshot below, you can see the incorrectly join areas circled. The blue hatch indicates what should have been joined - the solid yellow areas have only joined based on the slightest overlap/touch at the boundaries.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LindsayRaabe_FPCWA_3-1712215593437.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/99985i3EF26729E0CD21A4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LindsayRaabe_FPCWA_3-1712215593437.png" alt="LindsayRaabe_FPCWA_3-1712215593437.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I even tried to include a projection step prior to the spatial join to remove the slight shift, but it made no discernable difference.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 04 Apr 2024 07:28:19 GMT</pubDate>
    <dc:creator>LindsayRaabe_FPCWA</dc:creator>
    <dc:date>2024-04-04T07:28:19Z</dc:date>
    <item>
      <title>Include search distance option when performing spatial joins</title>
      <link>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idi-p/1405601</link>
      <description>&lt;P&gt;I'm attempting to do a spatial join and unfortunately the 2 input datasets have different spatial references. This means that the 2nd is transformed to match the first. The data should align, but the transformation means there are slight differences. These differences are resulting in features joining that should not when using the "intersects" or "contains" options. In ArcGIS Pro, i frequently add a negative search distance to reduce the chance of overlaps around the edges, but this is not possible (yet) in Data Pipelines.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I even tried the "Near geodesic" option with a negative distance (5 metres) but that results in an error when run/previewed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LindsayRaabe_FPCWA_0-1712215206436.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/99984i78B432F921AA2135/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LindsayRaabe_FPCWA_0-1712215206436.png" alt="LindsayRaabe_FPCWA_0-1712215206436.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;In the screenshot below, you can see the incorrectly join areas circled. The blue hatch indicates what should have been joined - the solid yellow areas have only joined based on the slightest overlap/touch at the boundaries.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LindsayRaabe_FPCWA_3-1712215593437.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/99985i3EF26729E0CD21A4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LindsayRaabe_FPCWA_3-1712215593437.png" alt="LindsayRaabe_FPCWA_3-1712215593437.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I even tried to include a projection step prior to the spatial join to remove the slight shift, but it made no discernable difference.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2024 07:28:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idi-p/1405601</guid>
      <dc:creator>LindsayRaabe_FPCWA</dc:creator>
      <dc:date>2024-04-04T07:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: Include search distance option when performing spatial joins</title>
      <link>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idc-p/1405758#M35</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/148829"&gt;@LindsayRaabe_FPCWA&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;Thanks for reaching out and sharing your idea.&lt;/P&gt;&lt;P&gt;Data Pipelines does not currently have plans to support a negative search distance.&lt;BR /&gt;&lt;BR /&gt;Is the data you're joining public or sharable (even if it's just the geometries and no attributes)? This is an interesting use case and we'd like to investigate options. If it's sharable, please feel free to send it along to me directly at &lt;A href="mailto:bscott@esri.com" target="_blank"&gt;bscott@esri.com&lt;/A&gt; and we will take a look.&lt;BR /&gt;&lt;BR /&gt;And just to confirm, when you run the exact same join in Pro (Intersect with all the same spatial references and no search radius), are the results the same as what you're seeing in Data Pipelines?&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;Bethany&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2024 14:51:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idc-p/1405758#M35</guid>
      <dc:creator>BethanyScott</dc:creator>
      <dc:date>2024-04-04T14:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: Include search distance option when performing spatial joins</title>
      <link>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idc-p/1406154#M37</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/350186"&gt;@BethanyScott&lt;/a&gt;&amp;nbsp;It's not publicly shareable data , though I can share to a test group and add you - I just need your argis online username. I tried bethanyscott but it said that account had insufficient privileges?&lt;/P&gt;&lt;P&gt;I've just done a quick test in Pro using Model Builder then adding the output to a map. The below screenshots show the results of doing a Spatial Join...&amp;nbsp;&lt;/P&gt;&lt;P&gt;...using "Contains":&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LindsayRaabe_FPCWA_0-1712276597082.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/100155i20C37A31B93BD830/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LindsayRaabe_FPCWA_0-1712276597082.png" alt="LindsayRaabe_FPCWA_0-1712276597082.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;...using Intersect:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LindsayRaabe_FPCWA_1-1712276665618.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/100156i3D1BDA5C2472A534/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LindsayRaabe_FPCWA_1-1712276665618.png" alt="LindsayRaabe_FPCWA_1-1712276665618.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Both the above worked well, but only included the intersecting features in the output dataset. So I've run it again with "Add Spatial Join" to create a temporary join with all Target features retained. This yielded a similar results as Pipelines (though some areas were left of and others were returned instead).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LindsayRaabe_FPCWA_2-1712277450176.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/100157iA8170D43D2EB0D3D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="LindsayRaabe_FPCWA_2-1712277450176.png" alt="LindsayRaabe_FPCWA_2-1712277450176.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2024 00:38:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idc-p/1406154#M37</guid>
      <dc:creator>LindsayRaabe_FPCWA</dc:creator>
      <dc:date>2024-04-05T00:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: Include search distance option when performing spatial joins</title>
      <link>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idc-p/1406267#M39</link>
      <description>&lt;P&gt;Thank you, these results are helpful. I've sent you a direct message with details for how to share the data with me.&lt;BR /&gt;&lt;BR /&gt;Best,&lt;/P&gt;&lt;P&gt;Bethany&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2024 11:33:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-pipelines-ideas/include-search-distance-option-when-performing/idc-p/1406267#M39</guid>
      <dc:creator>BethanyScott</dc:creator>
      <dc:date>2024-04-05T11:33:50Z</dc:date>
    </item>
  </channel>
</rss>

