Skip to main content

I created a spatial ETL tool that essentially exports GIS features from an enterprise GIS to individual DWGs by fanning out on a attribute. The attribute is associated with a specific site id. Additionally, I leverage the joiner, test filter, and reprojector transformers to reproject the individual fan outs into the appropriate projected coordinate system. These associations are defined in a list, hence the use of the joiner and test filter. This works well, but some sites need to be combined. So, my thinking was to leverage a feature class that contained envelopes to define the output extents and the data output associated with these extents by intersecting the envelope feature class. Is this possible?

Hi,

You can use the FeatureReader in combination with a spatial feature (your bounding box) as a trigger to intersect with the underlying database.

So instead of using a regular reader, you create the output extents as spatial features which are used by the FeatureReader.

Hope this helps,

Itay


Hi,

You can use the FeatureReader in combination with a spatial feature (your bounding box) as a trigger to intersect with the underlying database.

So instead of using a regular reader, you create the output extents as spatial features which are used by the FeatureReader.

Hope this helps,

Itay

Thank you. That seems to work, but I need the output grouped by the polygons in the feature class (envelope). When I follow your method, my output is a single .dwg. I want a .dwg per envelope.


Thank you. That seems to work, but I need the output grouped by the polygons in the feature class (envelope). When I follow your method, my output is a single .dwg. I want a .dwg per envelope.

You can set the envelop attributes to be made available after the FeatureReader ( see the parameters of the transformer) this way you can use the fan out option based on the envelop attributes.

 

 


Hi,

You can use the FeatureReader in combination with a spatial feature (your bounding box) as a trigger to intersect with the underlying database.

So instead of using a regular reader, you create the output extents as spatial features which are used by the FeatureReader.

Hope this helps,

Itay

Awesome, that worked. Thank you!


Reply