简洁公司运作流程模板： 自来水行业的系统管理工程GIS in Water Utility Management.ppt

Here is an example of our map book. Hundreds of 24 X 36 pages. Whats not obvious is that each of these pages used to be its own idividual coverage. This was do not so much to facilitate map books but because technology at the time could not effectively handle a dataset of our entire system. As GIS and water modeling software evolved the need to convert our GIS data into a single data set and feed it into the model be came apparent. * As we went down this path what also became apparent was the while the GIS data was good for printing map books it was lacking in GIS connectivity. When you zoomed into the datasets you would discover that the lines and points were not actually connected. We have all zoomed in to far on a dataset an seen this. * Water won’t really flow in a system like this. In order to make the GIS and Model work together we had to make the linework connect. We also had to connect all the datasets together across the network. So we could have something more like this: * As we went though the steps to get to this we discovered many steps and checks that needed to happen before it was ready to be a water model. Some of these we only had to fix once like connecting water mains. Some however had to be checked each time the water model was to be updated. * * In the end we had an intermediate Geodatabase that would review all the possible errors to make sure the data that went into the model was correct. This database has over 64 tables, 200 queries, and hundreds of lines of custom code. It takes 5 iterations to complete. Needless to say the process was anything but quick and painless. * The decision to convert from coverages to one complete Geodatabases and update our water model was aggreed upon. * We also decided to develop a system that could be used by all our business units. By partnering with our other business units we were able to purchase an SDE database with added features such as multiple editors. This also took a lot longer to col