You could try sampling the unstructured grid with the polydata. But you might run into issue if the polydata points end up outside if the unstructured grid. You could blow a little bit the unstructured grid by scaling it a bit...
On Sat, Aug 4, 2018 at 10:01 AM Fastl, Thomas <[email protected]> wrote: > Hey Sebastien, > > That's correct, the 'Extract Surface' filter applied to the > UNSTRUCTURED_GRID (vtk file 1) results in more POINTS compared to the > POINTS in the POLYDATA (vtk file 2). In addition, the POINTS in POLYDATA > (vtk file 2) have some rounding error so that the location of > 'corresponding points' doesn't match exactly. > > Maybe you've already suggested the right approach: Is there a way in > ParaView to extract the nearest neighbor of all the POINTS in POLYDATA (vtk > file 2) from the UNSTRUCTURED_GRID (vtk file 1)? I could just write a csv > file of the POINTS in the POLYDATA (vtk file 2) if that'd makes the nearest > neighbor approach in ParaView more simple? Thanks. > > Best, Thomas > > ------------------------------ > *From:* Sebastien Jourdain <[email protected]> > *Sent:* Friday, August 3, 2018 9:11:54 PM > *To:* Fastl, Thomas > *Cc:* paraview > *Subject:* Re: [Paraview] Extract Point Data | Nearest Neighbor Location > > So you are saying that the ExtractSurface on the Unstructured grid won't > produce the same polydata since it will be more refined than your file2? If > that's the case, then maybe just looking for point closer could be the > solution. > > On Fri, Aug 3, 2018 at 10:56 AM Fastl, Thomas <[email protected]> > wrote: > > Hey Sebastien, > > > the UNSTRUCTURED_GRID (vtk-file 1) has around 10^8 POINTS, while the > POYDATA (vtk-file 2) has around 10^6 POINTS, i.e., the POINTS in vtk-file 2 > are a subset of the POINTS in vtk-file 1. Additionally, the POINTS in > vtk-file 2 have some rounding error so that the location of "corresponding > points" doesn't matches exactly and a nearest neighbor seems necessary. > > > Best, Thomas > > ------------------------------ > *From:* Sebastien Jourdain <[email protected]> > *Sent:* Friday, August 3, 2018 17:20 > *To:* Fastl, Thomas > *Cc:* paraview > *Subject:* Re: [Paraview] Extract Point Data | Nearest Neighbor Location > > If they are truly the "same" why don't you forget your file2 and generate > a polydata from the file1 as a file3? > > On Fri, Aug 3, 2018 at 9:41 AM Fastl, Thomas <[email protected]> > wrote: > > Dear Community, > > > I've got an UNSTRUCTURED_GRID (vtk-file 1) with POINT_DATA and want to > extract the POINT_DATA at specific POINTS. However, the POINTS are > defined in POLYDATA (vtk-file 2) and are slightly off by some rounding > error. Thus, I presume the process should look similar to: > > > 1) Find the nearest neighbors of all POINTS defined in vtk-file 2 in > vtk-file 1 > > 2) Transfer/Store the POINT_DATA of the nearest neighbors in vtk-file 1 > > > I've been searching the forum for hours, however, couldn't find a solution > to that problem. I was wondering if there's a simple solution of doing this > in Paraview? I'd really appreciate your help on this issue, thank you! > > > Best, Thomas > > _______________________________________________ > Powered by www.kitware.com > <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7Ce5763891c0f6453319f108d5f95d16fd%7C8370cf1416f34c16b83c724071654356%7C0&sdata=1tZnhbKqOJXcXbg0Tp2m8D2gjHP8MOb7HGdGUc0EgD8%3D&reserved=0> > > ParaView discussion is moving! Please visit > https://discourse.paraview.org/ > <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.paraview.org%2F&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7Ce5763891c0f6453319f108d5f95d16fd%7C8370cf1416f34c16b83c724071654356%7C0&sdata=k6yXwz%2FsmevXQOR8FGQCAscP2996kdUPrdujqiV%2Fcg0%3D&reserved=0> > for future posts. > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7Ce5763891c0f6453319f108d5f95d16fd%7C8370cf1416f34c16b83c724071654356%7C0&sdata=k3qytN9NYE%2BVh6ZE99Kd1DUbtLIdGi3VuRqo1iQIht0%3D&reserved=0> > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparaview.org%2FWiki%2FParaView&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7Ce5763891c0f6453319f108d5f95d16fd%7C8370cf1416f34c16b83c724071654356%7C0&sdata=diUlLjUJJAbNWnE%2FzjxJM7uaYq9brB8MBjq0160kVWA%3D&reserved=0> > > Search the list archives at: http://markmail.org/search/?q=ParaView > <https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3DParaView&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7Ce5763891c0f6453319f108d5f95d16fd%7C8370cf1416f34c16b83c724071654356%7C0&sdata=E0og4nleW31GkHJ0tL8nSySbRyZAqnODikkJqYSZmS8%3D&reserved=0> > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview > <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=01%7C01%7Cthomas.fastl%40kcl.ac.uk%7Ce5763891c0f6453319f108d5f95d16fd%7C8370cf1416f34c16b83c724071654356%7C0&sdata=R%2BrvA3fbK9R10O%2B4wYkwK8Qmgm64hcCa%2B7kd%2FukBI9I%3D&reserved=0> > >
_______________________________________________ Powered by www.kitware.com ParaView discussion is moving! Please visit https://discourse.paraview.org/ for future posts. Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
