Skip to main content
Solved

Auto-creating a bounding box for GDB readers

  • December 9, 2015
  • 2 replies
  • 20 views

chriswilson
Enthusiast
Forum|alt.badge.img+21

Other than manually specifying coordinates to define a GDB reader's bounding box within workbench, is there a way to use (for example) a polygon to define the bounding box prior to reading so that a workspace can do this automatically and dynamically? I have project areas all across Christchurch, NZ and being able to do this would be very helpful in only reading in select portions of a massive city-wide dataset.

Thanks,

Chris

Best answer by erik_jan

You could just read the project areas and then use those as triggers for a FeatureReader to read the data from the GDB using the project areas as areas of interest. Doing this will allow you to read only the features you need from the GDB.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

erik_jan
Contributor
Forum|alt.badge.img+23
  • Contributor
  • Best Answer
  • December 9, 2015

You could just read the project areas and then use those as triggers for a FeatureReader to read the data from the GDB using the project areas as areas of interest. Doing this will allow you to read only the features you need from the GDB.


chriswilson
Enthusiast
Forum|alt.badge.img+21
  • Author
  • Enthusiast
  • December 9, 2015

Great, thanks Erik!