Cropping data source to model limits

[lucdoucet_msdl]

I'm working with large GeoJSON files from a public municipal source and find it difficult to select only the elements within the boundaries of the model.

The GeoJSON files are connected data sources to Coverage Areas representing one of four categories of  polygons (road, intersection, sidewalk, islands). The Source tab has the drape option activated and the "Clip to model extent" radio box checked.

When I try to work with filters of activate the table view, all the data is "exposed" whether it is within or without of the model boundaries. Is there a way to filter out, crop or exclude all data that doesn't intersect with the model boundaries to improve the speed of working with the data?

My ultimate goal is to be able to select all the Coverage Areas corresponding to the paved surfaces and move them down 15cm/6" with a "smooth radius" of 0m to better illustrate the sidewalk borders. 

Any ideas?

Thanks,

- luc

[andrewofabley]

@lucdoucet_msdl 

If you've already defined the model extent via a shp or sdf file, then 'clip to model extent' should in theory work fine.

I often spatially query or filter data using GIS or ETL tools ahead of loading into Infraworks to avoid this (and trim down the data prior to load).

[lucdoucet_msdl]

@andrewofabley 

---

@andrewofabley wrote:

If you've already defined the model extent via a shp or sdf file, then 'clip to model extent' should in theory work fine.

---

If in theory, the clip to model extents in the data source configuration is intended to limit the imported items in the larger data source, I've tested this in the following situation:

1. Create a new empty model with a coordinate system and an SDF file to define the model extents;
2. Create a new surface by importing a point cloud and using it to generate a new surface;
3. Link a road polygon GeoJSON file using a Generice Data Source, OGR: GeoJSON;
4. Configure the GeoJSON as: TYPE = Coverage Area, Drape enabled, "Clip to model extent" enabled, Source Filter <Empty>
5. Select all Features from the Project Browser gives 60 303 results versus Selecting visible with 10 results

So the GeoJSON data outside the model extents are still selectable and included in filter results.

Adding a Source Filter at step 4 to search for a parameter (in my case, the burrough name) such as PROPRIETAIRE = 'Rosemont' does not reduce the number of coverages created (still 60 303).

---

I often spatially query or filter data using GIS or ETL tools ahead of loading into Infraworks to avoid this (and trim down the data prior to load).

---

I understand that I could use other software packages to pre-process the GeoJSON file but I would like to exhaust solutions within Infraworks to facilitate the workflow for my coworkers.

I suspect that the "clip to model extents" may not apply to all types of data sources or may refer to something other than limiting the elements imported into the InfraWorks model.

@Karsten.Saenger could you comment on what "clip to model extents" is supposed to acheive in the data source configuration window?

Thanks,

-luc

[lucdoucet_msdl · Accepted solution]

The municipal data source is also available as a SHP file format.

When testing the same procedure as below, "clip to model extents" does in fact limit the data that is imported to model extents. It seems that the GeoJSON is the problem.

-luc

[Karsten.Saenger]

Hi @lucdoucet_msdl ,

regarding to the "clip to model extents" I can only cite what is written in the help files:

Double click on a data source in the Data Sources panel and choose Clip to Model Extent from the Source tab. This will limit the extent of imported data to the already defined model extent. See To specify source and draping options for more information.

InfraWorks Help: About Coordinate Systems and Model Extents 

Regards,

Karsten.

[lucdoucet_msdl]

@Karsten.Saenger 

---

regarding to the "clip to model extents" I can only cite what is written in the help files:

Double click on a data source in the Data Sources panel and choose Clip to Model Extent from the Source tab. This will limit the extent of imported data to the already defined model extent. See To specify source and draping options for more information.

InfraWorks Help: About Coordinate Systems and Model Extents 

---

I was able to test the clipping in both GeoJSON and SHP files as the municipality providing the data had both formats. What I conclude is that the SHP did "exclude" the data outside the clipping boundary (be it the model extent or a bounding box) but the GeoJSON did not.

Can you confirm whether GeoJSON files are supposed to be clipped  when configuring the data link?

Thanks,

-luc