Here at Esri, we always try to help one another out. Well the Local Government team asked if we could expand the functionality of the Attribute Assistant and make a series of construction tools to help with address data management workflows; and we obliged. We came up with some pretty cool new rules for the attribute assistant and some interesting construction tools that will be used to streamline address maintenance workflows. Even though these have been designed for managing address information, you may find them very helpful. Let’s first take a look at these new attribute assistant rules.
The first rule we needed to create was CASCADE_ATTRIBUTE. This rule will allow you to make a change to an attribute in a table or layer and push that new attribute value to every feature that contains the value. So in the address world, we have implemented a Master Street Name table. Say a road was renamed, we can go into the table, change the road name, and the rule will open up the Road Centerline layer and make that change to every road with the old name, then open up the Site Address Point Layer and update the road name as well. Pretty cool, huh?
The second rule we created was VALIDATE_ATTRIBUTE_LOOKUP. This rule will validate an attribute change against a look up table or layer. Let’s look out how you would use this in address land. If I created a new road and I want to make sure the road name matches a road in the Master Street Name table, I can set this rule up to monitor my Street Name field and check that value against the Master Street Name table. The cool thing about this rule is all I have to do is enter a piece of the road information. If it finds more than one record in the street name table, it presents a prompt, where you can select any of the matching values. How is that for data validation?
I also mentioned we are working on some new construction tools. These are still in development, but here is what we are working towards. One tool will allow the user to click a reference point, in our case, an address point that represents the location on the centerline of which the address is derived, create this point if it does not exist, then create a series of site address points with information from that reference point or the centerline underneath it. So basically, you can create a series of points all with information from source point. The second is a tool to draw a new road and split any intersecting roads and prorate their address information.
If you want to try the new rules out, as well as a few other enhancements, we have posted a beta of the tools on the forum.
Mike from the Water Team
We posted an updated version of the Editing tools today. This update has an only a few visible changes, but we did a lot of work to the plumbing of the tools. We condensed a series of duplicate functions, streamlined some of the processes and removed one of the dlls which was causing issues on non admin installs. We also did a bunch of clean up to better manage memory and improve stability.
Since we are supporting multiple config files now, we also changed the name of the config file that is being used to Loaded.config. If you have a config file you have created, let the tools create the new Loaded.config file and port your changes into it. There are a few new tags that we want to make sure you have. You will find it easier to navigate to the config file location with the Config file tool on the Infrastructure Reporting Toolbar. We also included a Bat script that will copy a config file to the appropriate location and open the folder for you.
We included a new copy of the Dynamic Value table with an updated Value Method domain. You should look at manually adding the new rules to your domain or importing the one included in the NewDyn.gdb.
I will be working on updating the docs and hope to have them all posted later this week.
For all the details, check out the change log included in the beta thread.
Mike from the Esri Water Utility Team
Hope everyone on the east coast made it through the hurricane ok. We lost power for a few days here at the Water Team headquarters in the Philadelphia area. The down time allowed us to crank out another release of the IET. We spend the time working on tools to help you move assets from proposed to in-service, in-service to abandoned, etc.
One new tool you will see came from a UC request and thought it would be a good start for this toolset. This tool allows you to reassign all connected assets to a main to a new main. Very simple, select the main that is going to be abandoned, select the new main, and all taps, laterals, valves, etc are moved over to the new main.
We also added a new rule to the Attribute Assistant – MOVE_FEATURE. This rule monitors a field and when that value of the field matches what is listed in the value info, the feature is either copied or moved to the target feature class.
Lastly we are working on a python script to move feature also. This script looks at the selected features, copy’s them to a target featureclass and sets the source features name in a field. We might look at building an ArcObjects tool to do the something similar, but expose a few more options in the configuration files. Maybe the python script can load the same config file.
Not only did we add a few new tools, but we also made a bunch of internal bug fixes and enhancements to improve the stability and functionality of the toolset.
Thanks for you feedback on the last weeks post. Please keep it coming.
If you have not noticed, we have been making a lot of improvements to the Infrastructure Editing Template or IET as some of you have been calling it. We have been working through the enhancment requests that we recieved at the UC and have released most of them through the Water Utilities Forum Beta Thread. We have one very important improvement left that we need your help on. We are looking to build a set of tools to help bring infrastructure from a proposed status to an in-service status and tools to move features from in-service to an abandon status.
Here are the tools we are thinking of so far.
1: A Geoprocessing script or model to change the status of selected features.
2: A Geoprocessing script or model to move a feature from one feature class to another and update some attributes.
3: A tool to select an existing line, select a new line and move all features to the new line(taps and laterals)
4: A tool to select two locations on a line, junctions or edges, split the line if required, run a trace between them and copy or cut each feature to a new feature class.
Would the above toolset allow you to manage the life cycle of your assets better? If not, what are we missing? Should we add any additional steps to these tools?
Please let us know through the forum entry on this topic linked below.
I wanted to thank all our Water and Wastewater users that attended this year’s User Conference. It was a fun week for us and I hope it was for you too. It is such a busy week, we did not get a chance to talk to all of you, so we wanted to solicited any feedback you had for us. Of those we did talk to, we received some great enhancement request. I listed some of them below for the editing template, but if you have any other suggestions, want to expand a topic or if we missed your request, let us know. You can post them as a comment or send us a note(ArcGISTeamWater@esri.com).
- Tool to move taps and laterals from an existing main to a new main
- Ability to add a flag or barrier then run traces from the Infrastructure Editing Toolbar
- Ability to load Multi Configuration files
- Ship the Configuration file in the documentation folder with a script to load it to the correct location
- Report of the trace results
- Sewer design tools
- Warning or deactivate the Attribute Assistant on a split
- Tool to add spin to a rotated feature
- Attribute Assistant rule to validate attribute input
- Attribute Assistant rule to not allow disconnected features to be created
- Tools to help localize the data model
- GP Models as tools to move features from Proposed to In-service, In-service to Abandon
- Intersected Line layers in profile trace
We get asked all the time, who is using the Water Utility Templates? We know of a lot of users and partners that have downloaded them, implemented them, and helped us improve them, but we do not know who and where you all are. We put together a simple ArcGIS.com map for you to provide us your location and some feedback. Let us know what you think.
Been a while since we posted anything on updates to the templates, but that’s because we’ve been busy doing some updates. A lot of good things are in the works. We’ve heard from many users that migrated their production environment over to ArcGIS 10 in the last few months and as part of that migration are deploying the templates. So their organizations are building new workflows and modifying old ones to take advantage of the templates. We’ve gotten some very useful feedback from these users and the below are some of the results of that feedback.
New fields in the Dynamic Value Table
GENERATE_ID Table – You all have asked and we listened. We are restructuring the Generate ID table to have two columns, Sequence Name and Sequence Value. Each row will represent a sequence value.
RUNORDER – This will allow to you specify the order the rules are processed. The previous extension processed the rules in the order of the fields. This caused issue when trying to chain together steps. The runorder is more of a hierarchy, so numbers can be repeated.
ON_MANUAL – Users have asked for a way to only run certain rules when I click a button. The on_change button is great, but does not allow for only manual rules. There will be a button to fire on_manual rules.
Modified Rules – We have updated a few rules, below are the changes.
These rules now have a value method that for lines you can choose to get the centroid, start or end coordinate.
C – Extract the coordinate value from the centroid
S – Extract the coordinate value from the Start
E – Extract the coordinate value from the End
JUNCTION_ROTATION – New option to list the diameter field.
New Rules – To many details to mention, but we will have detail info in the doc.
We are working on redoing the trace to allow it to be exposed to web applications better, as part of this, we are adding a secondary isolation trace function. This will temporary set all valves as inoperable, run the trace from the trace point and return the results.
We are anxiously awaiting the release of the Flex 2.3 viewer. We this release, we will update the Operational dashboard to run on this release.
Ne new version of the applications allow your customer to submit a service request as well as share information with them. Coming Soon.
Update – You can find all beta releases on the Forum – http://forums.arcgis.com/threads/20000-Beta-Versions
This week, we updated the Editing, Mobile and CIP template. There are too many changes to list here, so check out each templates release notes for a full list. I did want to highlight the new overview docs with the editing and mobile template. These documents walk through each component of the templates and discusses the configuration options for them. We also provided better comments in the configuration file. We hope this helps you configure and understand how to set up the templates with your data. We also wanted to thank you for all your great feedback. All the new functions, the bug fixes, the enhancements have been from your requests. We could not make this great toolset without you. So please, if you are having an issue, or you see an area that we could expand on, post a thread on the forum so we can discuss the enhancement request and get the communities feedback.
ArcGIS Team Water
If have not seen the recent blogs postings by the Data Reviewer team, you need to check them out. Data Reviewer is an extension to ArcGIS that provides an automated way to QA/QC your data. These blogs discuss how to configure Data Reviewer to check water and wastewater data. Also, the Data Reviewer team and the Water team will be presenting this extension in an upcoming webcast. We are finalizing the date and will have the sign up information available shortly. We will post another blog with the details once we have them. Make sure to attend if you want to see this extension in action or if you have any questions.
Data Reviewer Overview: http://www.esri.com/software/arcgis/extensions/arcgis-data-reviewer/index.html
Part 1: http://blogs.esri.com/Dev/blogs/datareviewer/archive/2011/01/06/Valency-Check-for-Water-Utilities-_2D00_-Part-1.aspx
Part 2: http://blogs.esri.com/Dev/blogs/datareviewer/archive/2011/01/18/Valency-check-for-water-_2600_-wastewater-utilities-_2D00_-Part-2.aspx
We released a beta of the mobile template today. You can access the beta through the beta thread on the water utility forums. There were a bunch of fixes, some new settings exposed and a reworked ID tool. The ID tool now allows you to select an option to look for the top most visible feature. You can also group layers, say you want to ID all water layers. This will expose a drop down on the ID panel that allows you to search for the top most visible feature in that group or select a particular layer. With this new ID tool, we also expose a factor that you can use to refine how far you search from the cursor click. If you want to test out the beta, you will need to use the cache from the release version. The beta does not include a cache of data. Let us know what you think or if you encounter any issues.
ArcGIS Team Water