Our water/wastewater (municipal) utility does not share infrastructure information by making services/apps public.
However, we regularly share area-specific subsets (copies) of GN data with engineering consulting firms and other stakeholders. Occasionally, we share system-wide copies of the water or wastewater GN data. When we share, we always provide a standard set of shapefiles and feature classes in a file geodatabase.
How are your organizations handling infrastructure data deliveries using the Utility Network schema? (FileGDB with layer files to support symbols/rendering? other?).
I believe the more hierarchical schema of the UN - built around symbolizing with subtype group layers - asset group/asset type, etc. will be more challenging for users than a simple feature class of water system valves, for example. UN v7, with a 64 bit ObjectID may be an issue for shapefile deliveries for some.
Any thoughts/advice appreciated. Thanks.
Solved! Go to Solution.
We do offer some tools that might help you export the subtype based UN layers. Would any of these help you?
We do offer some tools that might help you export the subtype based UN layers. Would any of these help you?
Thank you, Mike
We were leaning towards making something like the SubtypesToClasses tool. Good to see it already exists.
It does interject an intermediate step of creating the feature classes. We can use those resulting FCs as the data source for our Shapefile and FGDB deliveries, since those will need to export from a selected set.
We'll just need to periodically run the SubtypesToClasses tool.