I have been working on a large impermeability study project, which I took over from a colleague from one of our US offices. The project had been prepared using an ESRI file geodatabase. Thankfully all of the creation of the various impermeable surfaces (roofs, parking, sidewalks, etc.) had been completed before I got involved. My part of the project was to merge the impermeable data with various other boundaries representing subcatchments, land use and montoring areas to create a final SHP file that had data columns for each subcatchment with area totals for each type of impermeable surface.
I decided to use Manifold’s Topology Overlay command to run through the merging of each of the different data sets. Even though this took several runs to achieve the final output required, this was so easily accomplished it didn’t enter my mind to investigate alternatives using SQL or the ArcGIS Join Data method.
The part of the project where I had a problems was with the permeable feature class in the file geodatabase – when I tried to use ArcCatalog to convert to SHP, ArcCatalog refused to complete the process, even though the progress bar shot to 100% complete, resulting in a zero object SHP file. After investigating the attribute table I determined that this was a single multi-part polygon that covered the entire study area. To resolve the issue I used the Advanced Editing Explode tool on a copy of the polygon feature class and it exported successfully. I imported the permeable SHP file into Manifold and ran the Topology Overlay command to determine the permeable area totals for each subcatchment.
All that’s left now is some QA/QC to make sure I haven’t messed up along the way, but I’m quite confident that once again the Manifold way has achieved another of the classic GIS tasks simply and without issue.
As for the ArcGIS export multi-part polygon to SHP problem lets put that in the usual ‘ESRI makes us jump through hoops’ folder.
Recent Comments