FME World Tour 2016 - Developing Custom Transformers to Simplify a Sanitary Sewer Geometric Network
•Download as PPTX, PDF•
0 likes•68 views
Central San has progressively upgraded it's GIS platforms over the past decade, and FME has been integral to those efforts. As part of the most recent platform shift, we needed to migrate our existing sanitary sewer features into the Esri Local Government Information Model and improve their integration with other connected systems. This presentation shows how we developed custom transformers to simplify our model of sewer pipes and their associated attributes.
Recommended
Recommended
More Related Content
Similar to FME World Tour 2016 - Developing Custom Transformers to Simplify a Sanitary Sewer Geometric Network
Similar to FME World Tour 2016 - Developing Custom Transformers to Simplify a Sanitary Sewer Geometric Network (20)
Recently uploaded
Recently uploaded (20)
FME World Tour 2016 - Developing Custom Transformers to Simplify a Sanitary Sewer Geometric Network
- 1. Developing Custom Transformers to Simplify a Sanitary Sewer Geometric Network Carl Von Stetten CCCSD
- 2. About Me GIS Analyst, CCCSD Carl Von Stetten
- 3. Last Year on the FME World Tour…
- 4. Our Goal GIS will serve as the authority of record for the inventory of District infrastructure assets.
- 5. Our Problem GIS sewer main features were not always 1:1 with physical pipes, sometimes they were n:1.
- 7. Historical Context… • From 1970’s thru mid-1990’s, infrastructure maps produced by manual drafting • Annotation overload!
- 8. …More Historical Context… • 1996 MGE deployed – similar hardcopy format, just maintained with different tools • Sewer mains with attribute changes stored as “minisegs” # Main ID Length Diam. Material Job 1 75D1 M 70.5 75D1 80 131 6 VC X1558 2 75D1 80 75D1 81 114 8 CI X1558 3 75D1 81 75D1 82 18 8 CI X1558 4 75D1 82 75D1 83 100 8 CI X1558 5 75D1 83 75D1 84 18 8 CI X1558 6 75D1 84 75D1 M70 75 6 VC X1558
- 9. …Almost Caught Up… • 2005-06 GeoMedia deployed – somewhat refined hardcopy format, new tools and custom code • Automated process to calculate “majorsegs” from “minisegs” # Majorseg Main ID 1 75D1 M 70.5 75D1 M 70 75D1 M 70.5 75D1 80 2 75D1 M 70.5 75D1 M 70 75D1 80 75D1 81 3 75D1 M 70.5 75D1 M 70 75D1 81 75D1 82 4 75D1 M 70.5 75D1 M 70 75D1 82 75D1 83 5 75D1 M 70.5 75D1 M 70 75D1 83 75D1 84 6 75D1 M 70.5 75D1 M 70 75D1 84 75D1 M70
- 10. So Where Are We? • “minisegs” solved the problem of tracking the attribute changes over the length of a sewer main • “majorsegs” solved the problem of linking to external databases (CMMS, CCTV, hydraulic modeling, etc.) • But… still can’t reliably link back to GIS from the external databases 1:1 • Which single GIS feature represents the whole pipe?
- 11. Time to Rethink Things How can we consolidate the “minisegs” into single features without losing any information?
- 12. What do we do with “miniseg” data? Pipe attribute changes tracked by “minisegs” Need to track spatially? New solution Pipe material Yes Copy “miniseg” to ssAttributeChangeLine FC Liner material/method Yes Copy “miniseg” to ssAttributeChangeLine FC Diameter Yes Add reducer fitting in ssFitting FC – make it a defining structure Slope (grade breaks, vertical curves) Yes Move mid-pipe elevation changes to ssElevationPoint FC, retain start/end invert elevations on pipe Job number(s) No Move to a related JobLinks table Encasement Yes Copy “miniseg” to ssCasing FC, remove encasement attributes from pipe
- 13. What do we do with “miniseg” data? A few leftover details: • When consolidated pipe has multiple materials set the MATERIAL attribute to “Varies” • Same for multiple liner materials/methods (LINERMATERIAL/LINERMETHOD) • If the “minisegs” can be consolidated at all before copying to ssAttributeChangeLine, do so • Can consolidate job and slope changes if material or liner doesn’t change between adjacent “minisegs” • Sum the total length of the consolidated pipes and consolidated ssAttributeChangeLines
- 14. How do we accomplish this? • With FME of course! (duh!) • Using the LineJoiner transformer • Using a reuseable Custom Transfomer
- 15. Let’s see this in FME…
- 17. MiniSeg Consolidation to Whole Pipes
- 18. MiniSeg Consolidation to ssAttributeChangeLine
- 20. MiniSegJoiner User Parameters Define inside Custom Transformer Set attributes on each placement
- 21. Move Job info to a Relate
- 23. JobHandler User Parameters Define inside Custom Transformer Set attributes on each placement
- 24. Custom Transformers rock!!! • Keeps workbench DRY (don’t repeat yourself) • Configureable behavior (through user parameters) • Encapsulate your task logic
- 25. Thank you! Carl Von Stetten Email: cvonstetten@centralsan.org Web: http://centralsan.org http://about.me/cfvonner Twitter: @cfvonner Slack: @cfvonner http://gisdevs.slack.com signup: http://bit.ly/1HxiNv1
Editor's Notes
- Last year talked about how we were using FME to migrate all of our GeoMedia-based GIS data into the Local Government Information Model in ArcGIS This talk is about how FME helped us solve one particular pain point in that migration
- Third GIS platform to be used at District Previous ones driven largely by paper map book production 1st, web GIS 2nd Opportunity to shed as much historical baggage as possible and put web 1st Streamline GIS maintenance and enhance user experience
- In other words, we had more GIS sewer main features than we had physical pipes What does that even mean?
- Draw on the screen!!!
- All the colored sections of pipe are part of the same pipe: M70.5 to M70 Each represents some different characteristic Note the dimension symbols to identify where the changes occurred… hard to reproduce on web maps
- Still had 6 GIS features that represented portions of the pipe But now there is an attribute column “majorseg” that defines the whole pipe Note the X symbols denoting where the changes occurred
- Here’s our opportunity to start fresh
- ssAttributeChangeLine and ssElevationPoint feature classes and JobLinks table are custom ssFitting and ssCasing are part of delivered LGIM
- Consolidate as much as we possibly can to keep things as simple as possible
- `
- Some statistics: 6 Readers (12 Feature Types) 2 Writers (36 Feature Types) 175 Transformers in main workspace (not counting inside custom transfomers) The two areas with red outlines are what we are going to focus on
- TestFilter divides up categories of sewer main features based on attribute values MiniSegJoiner custom transformers (green=custom embedded transformer in workbench) SequenceGenerator custom transformer (aqua=linked custom transformer sharable with other workbenches)
- Same MiniSegJoiner transformer used here – why???
- Walk through logic Highlight the Mode switch which bypasses some of the transformers
- The crazy TestFilter here helps make sense of the various contextual uses of our 3 job number columns