Attribute Rules were introduced to the GIS community in January 2019 with the release of ArcGIS Pro 2.3 and ArcGIS Enterprise 10.7. The focus was and still is improving data quality and reducing erroneous data entry. While Geodatabase Domains do this through pick lists and validation through range domains, there is nothing stopping an editor from picking the wrong value. Also, many DOT's attach information onto their asset inventory such as the county, District, Maintenance Region, and other administrative boundaries. Many DOT's even do this through post-processing.
What if there was a way to do this in real-time while an Editor is creating a new feature or even moving an existing feature or updating its attributes. I present to you Attribute Rules. The Attribute rules are designed to support 3 types of workflows.
Automatic population of attributes.
Perform QA checks on existing features.
Constrain Invalid Edits.
They are applied to your data residing in an Enterprise Geodatabase and are just another complex behavior like domains and subtypes. They support two workflows which include evaluation at edit operations using immediate calculations to populate an attribute dynamically or they can be used as a constraint to specify permissible values. The second workflow they support is evaluation of data by a validation service allowing the user to apply them to a batch calculation to populate attributes and validation to validate existing data.
Attribute Rules allow you to make the data smart, so the editor doesn't have to necessarily know where they are when they are editing a bridge. As long as they create the bridge point, Attribute Rules can, for example, intersect the bridge point with a county and pull out the county name and insert it into the county name field on the bridge layer. So as long as you know what the authoritative data sources using arcade expressions you can make your data smart.
The best part in all of this is that wherever you make edits, in Pro, Web App Builder, Event Editor, Survey123, Collector or any other app that supports editing, the database will always honor your attribute rules and apply them no matter the client making the edit.
Here is a video I put together to illustrate how it works. Over the next few months, I'll update this blog with videos on Constraints and Validation Rules. To sweeten the pot I've also attached all of the arcade expressions I used in the video to give you a head start on your own efforts to implement Attribute Rules. Also here is a nice article in the help and a deeper dive video than mine on Attribute Rules from the 2019 Developer Summit.
I conjunction with today's Winter Operations Webinar, I went ahead and pre-recordedall of the demos so you can watch the demos we didn't have time to show today or rewatch videos again to pick up on items you may have missed.
I'm pretty excited to show the integration of Survey123 with Spike by Ike GPS. This paring enables you to turn your iPhone or Android phone into a laser range finder with Spike. Integration with Survey123 allows me to capture, GPS coordinates, distance to target, area, length and a few other measurements. It enables me to capture data 6' up to 324' away which means I can stand at one end of a football field and capture GPS coordinates of an asset at the other end. I think, sign inventory, culverts, drains, ADA curb ramps, crash cushions, concrete walls, control fence, and bridges are ideal candidates for an inventory or inspection with Survey123. While concrete walls and control fencing are usually modeled as linear features, Survey123 could capture related tables with locations where fences or walls need to be repaired. While this is in Beta you can sign up for the as a beta tester and start working with it today which I'm sure Ismael Chivite and his team would love to get as much feedback as they can.
My video editing prowess was certainly challenged today, as a result I'm uploading the videos as 4 separate videos. I was also able to make use of the iOS screen recording capability which was cool. If you have questions please don't hesitate to reach out... thanks.
Good morning, here is the last video in the series on ditributed collaboration and 511. This workflow is still a prototype and has some scalability testing to go through after the new year. I want to at least make you all aware of what we are working on and show you how 511 workflows could be enhanced to take data directly from the enterprise and pushed into the Transportation 511 solution or even the Waze Connected Citizens Program. Enjoy
By the hair of my chinny chin chin... here is the Tuesday video I promised. In this video, I show how distributed collaboration can be used to support mobile workflows in ArcGIS Online. Hosted feature services living in ArcGIS Online can participate in collaboration where the data captured is written down to Portal for ArcGIS. The data can then live in the relational data store or it can be exported out and appended to an enterprise Geodatabase. To keep the Lego theme going, I use Survey123 and its ability to support existing features and related tables. It makes for a complex workflow, and it tests my patience. You'll see in the video when I go out to Pro to see the attached image, it is not there but what I forgot about was the fact that I'm waiting on a full resolution picture to make its way from ArcGIS Online to the Portal. Of course, it shows up as soon as I stop recording. Anyways, I hope you enjoy and please send questions my way if you think of any.
Hope the holiday season is treating everyone well. As we get ready to turn the page on 2017 and prepare for the soon to be released ArcGIS 10.6 and the December release of ArcGIS Online (12/6). I'm planning to release a series of videos this week on technology that exists today that I think can have a major impact on how DOT's utilize the ArcGIS Platform. I've chosen workflows that are relatively easy to set up and use Keith King's famous Lego block analogy. If Keith has come to your DOT this year you know what I'm talking about. For those of you who don't know. It goes like this, Esri’s apps (Collector, Web App Builder, Survey 123, Solutions, ArcGIS Pro etc.) work great by themselves and depending on the app, they are very simple to use. Legos are very simple, come in all different shapes and sizes and can be interconnected to form complex objects. Just like Legos, our apps can be interconnected and can be used to build complex workflows. The videos I share this week will be based on that premise. I'll take concepts of the platform and applications to support my explanation and build complex workflows.
Today's video shows how Distributed Collaboration can be used to share data from ArcGIS Enterprise (Portal for ArcGIS) to ArcGIS Online for use with ArcGIS Hub sharing to an Open Data Site. Enjoy!
I've had several discussions with DOT's from around the U.S. about the growing interest in the use of drones. Drones have a significant advantage over traditional aerial photography and LiDAR capture in that they are inexpensive, generally easy to fly and they can come equipped with a camera and LiDAR sensor. We are seeing drones used to capture change detection along construction projects, culvert inspections, and bridge inspections. Other emerging use cases include damage assement, land/rock slide geo-technical inspections, visibility analysis, and rail crossing inspections. Drone to Map for ArcGIS supports the uses of drones and allows users to analyze and store the data captured from a drone directly into ArcGIS Online or ArcGIS Enterprise as web services. Drone to Map for ArcGIS can produce to types of web services. Integrated Mesh Scene Layer and Point Cloud Scene Layer. Point Cloud Scene Layers allow the viewer to look through objects like tunnels and culverts. If your LiDAR vendor is actively collecting data using mobile, terrestrial or aerial LiDAR, be sure to request that they deliver the data with RGB point symbiology attributes. Many LiDAR vendors are not doing this but are starting to, this allows the point cloud to be displayed using true color, making the point cloud look more realistic. Density of the points matters as does resolution of the sensor.
To help understand what is possible, I put together a video of data captured by Guenter Doeffel, Marketing at SynerGIS Infomationsysteme Wien in Germany, here is a link to the web scene he published. You need to allow the data to download and cache into the browser, once that happens it renders very quickly.
Here is a video I put together showing the Web Scene embedded in a story map
If you spend enough time in ArcGIS Online building web applications for your organization, you'll likely have the need to include Esri Premium Services like Live Traffic, especially if your organization is a State Department of Transportation. While Live Traffic does not cost credits, it does require a named user to log in, and access the premium content. You of course know this because when you launched the application you tirelessly spent all that time configuring you hit the snag where the app requires the user to sign in. So how are you supposed to deploy a public app with traffic cameras, weather and live traffic if your app requires a login?
You could provide an access token that you embed in your application but that requires you customize or develop an application which means you have to host it. In addition, this creates a security risk, because your token could be hijacked and used without you ever knowing.
An easier solution is to create a proxy service configuration for the premium service of your choice. A proxy service allows you to encode and manage your credentials inside a service URL. In addition proxy services support rate limiting. This allows you to make the Esri World Geocoding Service available to an end user for batch Geocoding or other operations which do consume credits. However it protects you because you can specify the rate at which addresses can be batch geocoded preventing runaway usage while allowing the public the access they need.
Register your application by choosing Register New Application
Provide the Application Details
Click on the Authentication Tab
Scroll down to the Service Proxies area.
Select the service you wish to proxy and enter a rate limit for the number of requests you want to allow over a given period.
Copy the newly created proxy URL and add it to the webmap that your application is consuming. Remove the original service if it exists and save the webmap.
Log out of all web sessions using you ArcGIS Online credentials or use Incognito Mode on your browser to test that your app opens without challenging you for credentials. (This is a quick trick to allow you to open the browser with a cleared browser cache.) ! !
Open your web application and bask in the glory of your app opening withPremium Services that don't prompt your public users for an ArcGIS Online Username and Password.