Skip to main content
  • EN

Hello,

Any idea why when I am trying to use the search enveloppe option to filter only geometry features within a specified box (see file attached) I always got: Error running translation.

 

 

Otherwise without enabling the search envelop option my workflow works fine.

Thank you in advance.

I believe the issue is, that you are reading from XML, a non spatial format.

So the search envelope has no geometries in the data source to intersect with, and will therefor not read any data.

Thank you for your answer @erik_jan !

You are right I am reading from XML but then I have access to Feature with Geometry inside.

So let me rephrase 🙂 How can I filter then those Geometry which are within a box ? Using GeometryFilter ?

Thank you again.

I think I found a way to do it by:

 

 

Using a Creator a creating a Box

 

Using a Spatial Filter and attaching my Box to the Filter input and my Feature to the Candidate input.

Thanks.

I think I found a way to do it by:

 

 

Using a Creator a creating a Box

 

Using a Spatial Filter and attaching my Box to the Filter input and my Feature to the Candidate input.

Thanks.

If you want only the inside parts, you could also use the Clipper transformer.

 

 

If you want only the inside parts, you could also use the Clipper transformer.

 

 

Not working well with SpatialFilter I tried with Clipper but I got : Error Running Translation :(

 

 

Thank you.
Not working well with SpatialFilter I tried with Clipper but I got : Error Running Translation :(

 

 

Thank you.
You might want to test for a valid geometry before feeding features to either SpatialFiler or Clipper, using a GeometryFilter.

 

Or you can set the parameter to ignore rejected features and continue:

 

 

You might want to test for a valid geometry before feeding features to either SpatialFiler or Clipper, using a GeometryFilter.

 

Or you can set the parameter to ignore rejected features and continue:

 

 

@erik_jan you are amazing!

 

 

I added a GeometryValidator before and everything is running smoothly.

 

 

A last, question though, how to remove the clipper itself from the result (the box) ?

 

 

I just want the clippee result without the clipper :)

 

 

Thanks again.
You might want to test for a valid geometry before feeding features to either SpatialFiler or Clipper, using a GeometryFilter.

 

Or you can set the parameter to ignore rejected features and continue:

 

 

The Clipper geometry should not be exported from the Clipper transformer, unless you also connected it to the Clippee port.

 

About the attributes, you can set it not to merge attributes, but only use Clippee attributes.

 

 

@erik_jan you are amazing!

 

 

I added a GeometryValidator before and everything is running smoothly.

 

 

A last, question though, how to remove the clipper itself from the result (the box) ?

 

 

I just want the clippee result without the clipper :)

 

 

Thanks again.
As u can see from the screenshot attached that the box is exported (it is not connected to the clippee port). Are the Clippee geometries altered somehow by the Clipper Geometry ?

 

 

screen-shot-2018-04-27-at-55415-pm.png

 

 

Thank u again.
You might want to test for a valid geometry before feeding features to either SpatialFiler or Clipper, using a GeometryFilter.

 

Or you can set the parameter to ignore rejected features and continue:

 

 

Is that actually the box you are seeing, or the combined boundaries of the clipped features from the clippee port?

 

 

As u can see from the screenshot attached that the box is exported (it is not connected to the clippee port). Are the Clippee geometries altered somehow by the Clipper Geometry ?

 

 

screen-shot-2018-04-27-at-55415-pm.png

 

 

Thank u again.
This is the point I don't want combined boundaries. :)

 

 

I just want all my Features which are inside a box.
You might want to test for a valid geometry before feeding features to either SpatialFiler or Clipper, using a GeometryFilter.

 

Or you can set the parameter to ignore rejected features and continue:

 

 

You can add the outside port and then test on _clipped = 'Yes' (Tester).

 

That will add the part of the clipped features that is outside the box.

 

 

This is the point I don't want combined boundaries. :)

 

 

I just want all my Features which are inside a box.
I don't think I am on the right direction...

 

 

Let's restart:

 

 

I would like to build a list of all my Features geometry which are inside a defined box (min x, min y, max x, max y) without altering their geometry/attributes.

 

 

Thank again!

 

 

I finally managed to do it with my initial idea:

- Creator + SpatialFilter

Thank you very much @erik_jan

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.