I'm trying to create a validation routine that tells me what points are not in their expected polygon.
I have two tables with an areaid common to both- one has point geometry (building b) and the other has polygons (area a). something along the lines of the following badly phrased pseudocode!
select * from building where building point does not exist in area and a.areaid = b.areaid
All help appreciated! Thanks in advance
Best answer by david_r
You can e.g. use a PointOnAreaOverlayer with a GroupBy on areaid. On the Points output, connect a Tester and check for _overlaps = 0.
You can e.g. use a PointOnAreaOverlayer with a GroupBy on areaid. On the Points output, connect a Tester and check for _overlaps = 0.
+50If you use a PointOnAreaOverlayer that's set to group by the areaid and then a Tester or TestFilter to filter out the points with _overlaps = 0 you'll get all the points that are not within an area with the same areaid.
Thanks for the quick response folks! I've tried that but it's not working - they all seem to have 'passed' and there's no area attribution on the point! I've had a look at the data, I've looked at projections, included an areabuilder to make sure I wasn't passing a line - is there anything else that I need to look at?
I've got a vertexcreator directly before the PointOnAreaOverlayer if that makes a difference
(I'd love to post the existing work bench with some data but it's licensed!)
+50Thanks for the quick response folks! I've tried that but it's not working - they all seem to have 'passed' and there's no area attribution on the point! I've had a look at the data, I've looked at projections, included an areabuilder to make sure I wasn't passing a line - is there anything else that I need to look at?
I've got a vertexcreator directly before the PointOnAreaOverlayer if that makes a difference
(I'd love to post the existing work bench with some data but it's licensed!)
Hmmm...
If we can't see the workspace or data that's going to make it a bit difficult, but there's a few things you can check:
I'm a bit unclear about what you mean when you say "there's no area attribution on the point", my assumption is that before the PointOnAreaOverlayer they do (because otherwise there is no way to connect them to the areas)
Thanks for the quick response folks! I've tried that but it's not working - they all seem to have 'passed' and there's no area attribution on the point! I've had a look at the data, I've looked at projections, included an areabuilder to make sure I wasn't passing a line - is there anything else that I need to look at?
I've got a vertexcreator directly before the PointOnAreaOverlayer if that makes a difference
(I'd love to post the existing work bench with some data but it's licensed!)
First thing to check is that the attribute "areaid" that is used for the Group By exists with the exact same name (case sensitive!) on both the point and area dataset.
Hmmm...
If we can't see the workspace or data that's going to make it a bit difficult, but there's a few things you can check:
I'm a bit unclear about what you mean when you say "there's no area attribution on the point", my assumption is that before the PointOnAreaOverlayer they do (because otherwise there is no way to connect them to the areas)
Thank you! that cracked it - it was the areaid and an '_'.
A small thing, big headache! Thanks for your help!
First thing to check is that the attribute "areaid" that is used for the Group By exists with the exact same name (case sensitive!) on both the point and area dataset.
That's it! Thank you!
+50Hmmm...
If we can't see the workspace or data that's going to make it a bit difficult, but there's a few things you can check:
I'm a bit unclear about what you mean when you say "there's no area attribution on the point", my assumption is that before the PointOnAreaOverlayer they do (because otherwise there is no way to connect them to the areas)
You're welcome!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
