Earlier this year, the Esri Disaster Response Program team presented a live training seminar on our lessons learned from past events. During this presentation, we covered the top ten information products that we often make when supporting our users. Those … Continue reading
On Friday, July 17th, many ArcGIS Pro users saw a small window pop up on their computer screen. It announced to them, and to the world that a new version of Pro is available to download. I often find myself … Continue reading
We will show you how you can leverage you can download maps to your device, collect and update GIS features whilst disconnected and then synchronize changes back to the office when you are connected.
UPDATE: The seminar is now available for you to view on our website. Simply log in with your Esri Global username and password and view the seminar here.
The Export Topology Errors geoprocessing tool, which is new in ArcGIS 10.1, creates feature classes from the current errors in a geodatabase topology. The resulting feature classes contain the error geometries along with attributes about the topology rule that was … Continue reading
Note: You can view this post as a video: Generalizing shared edges. In my previous post, I used Align To Shape to make the stream match the edges of the land-use polygons. As I did this, I noticed the land-use polygons … Continue reading
Note: You can view this post as a video: Aligning features by tracing. In my previous post, I used some of the new alignment tools to match edges. Just slightly west of the location I was editing before, I noticed a … Continue reading
We receive a interesting question from a user on the Water Utilities Forum. They asked if it was possible to set a date on a field only when a specific field is modified. The Attribute Assistant extension, that is part of the Water Utility Network Editing application has a rule to set a field value when a specific field is changed called FIELD_TRIGGER, but not a date. We could extent this rule to support setting values such as date or time, but maybe there is a better way to do this, holistically for all the rules. What if we changed the ON_CHANGE field to a string field, where you could specify a field or a series of fields that a rule would run only when those fields values changed. Alternatively,we could add another field to the Dynamic Value table to list those fields and leave the current schema in place. That would simplify the changes, still give you a toggle to turn the rule on and off and let you restrict ON_CHANGE rules to only when specific fields have changed. If you think this enhancement would be useful, let us know.
Note: You can view this post as a video: Aligning edges to fix gaps between polygons. In my previous post, I reshaped topology edges to make my features match newer imagery. In the same area of the map, I noticed that … Continue reading