Basic—Provides comprehensive mapping and analysis tools with simple editing and geoprocessing. Standard—Includes advanced editing capabilities for shapefiles and geodatabases in addition to the full functionality of ArcGIS for Desktop Basic. It builds on the functionality of Standard with advanced geoprocessing. It also includes legacy applications for ArcInfo Workstation. Maps, data, symbology, map layers, custom tools and interfaces, reports, metadata, and so on, can be accessed interchangeably in all three products.
This means that you benefit from using a single architecture, minimizing the need to learn and deploy several different architectures. New capabilities can be added to all seats through a series of ArcGIS for Desktop extensions from Esri and other organizations. You can develop extensions and custom tools using Visual Studio. ArcObjects is a framework that lets you create domain-specific components from other components.
The ArcObjects components collaborate to serve every data management and map presentation function common to most GIS applications. This means all properties of the features being compared will be checked, including such things as spatial reference, field properties, attributes, and geometry. However, you may choose a different compare type to check only specific properties of the features being compared. The Ignore Options provides the flexibility to omit properties such as measure attributes, z attributes, point ID attributes, and extension properties.
Two feature classes may be identical, yet one has measures and z coordinates and the other does not. You can choose to ignore these properties. For example, the features of two annotation feature classes can be identical but the feature classes may have different extension properties, such as different symbols in the symbol collection and different editing behavior.
To minimize error, the value you choose for the compare tolerance should be as small as possible. If zero is entered for the XY Tolerance, an exact match is performed. The units are the same as those of the Input Base Features. If zero is entered for the M Tolerance and Z Tolerance, an exact match is performed. If the spatial references are different, a miscompare will be reported. If the coordinate system is different for either input, the features will miscompare.
This tool does not do projection on the fly. The Omit Fields parameter is a list of fields that are not included in the field count comparison—their field definitions and tabular values are ignored. Attribute tolerances can only be specified for numeric field types.
This file is a comma-delimited text file which can be viewed and used as a table in ArcGIS.
Is It Really that Easy? Is it Really that Easy? Transcript Part I: Hi, welcome to the webinar. Is it Really That Easy? Jeff is a product manager in our applications group. Thanks Christa, yeah no problem. So David Totman is going to actually get us started. You all know David. Thank you, Christa. So yeah, just a real quick intro here just to kind of reflecting on the year. So, Christa? Sure, David. And then right into the next one, Christa. Sure, so our second polling question is: So this webinar is going to be awesome!
Back to you David. Okay, thanks Christa. So yes, this is great. Hopefully have a little bit of fun here at the end of the year. As people could finally see how easy it was to go disconnected — to download your data to the phone or whatever — and go just collect your data and then synchronize [it back at the office].
So that really just opened up the door and allowed people to do exactly what they wanted — like hydrant inspections, things of that nature. And then really, as Christa [said when she] opened the session here, we had Le-Ax [Water] on and talked about the high accuracy. So we really we just had a ton of conversations. Part II: So we talk about going from easy to hard, and then going from points to high accuracy.
You finally made this thing that all of us can use. So you can definitely go offline. For high accuracy, if you have really good photography sometimes you get pretty accurate with you with your thumb or stylus. It really has been transforming utilities. I think we finally kind of knocked it out of the park with this one: So anyway, probably enough of that.
I want to turn this over to Jeff and let him get started. Thanks David. It has been a pretty busy year for us, and thank you for having me in this webinar today. So what I wanted to do is first kind of set the agenda with a few slides. Christa and everyone here today did a webinar with them recently, and you can go and watch that webinar to see his experiences as well.
You guys want me to do that in a demo? Part III: Getting Started: And then we need to give the organization a name. Because of our entitlement program, every account does. All right, so we have our organization name. You can see, as I filled it out, underneath its building a URL, and telling you whether or not that actual short name is available. The next step is to setup browser language, or, sorry a language for the for the organization — a default language.
Also, a region. And, that becomes the transport protocol for your use throughout the platform with it, so we can add a contact link if you want. There we are. You can continue, or you can go get them out. You can edit the settings, so you can change some of those things we just did. But you can write members of the organization, so we can add users.
They could be your field testers that you want to add. And you can manage them directly from here, and give those licenses to certain named users. That could be public, meaning that other users inside of your organization can look for it, see it and ask to join it.
And you can control the access of who can update information in that group, too. So if you want to just lock it down so that only you can add content and be a contributor, you could do that. So what we did was we went to the trial login page and the free trial page, and we entered in our username, email address, and our industry. Then we followed a bunch of stuff. Part V: One is to find a sponsor. Really try to bring them up to wanting to be the sponsor for you.
Take baby steps and learn from those successes and failures. So just a few quick tips there. Next thing I wanted to talk about that in the steps that we did — I went too fast — was that we signed up from the email. We created the administrator username and password.
There are a bunch of different ways that you can do that. But you can go and change that within your organization. It has some ramifications if you do, but what I would say set it up first. So in your organization, you can invite members. And linked into this slide is how you can go and understand the different methods of inviting members.
So if you want to do that instead of manually creating users or loading them from a text file, you can do that. Part VI: The way that you organize content is through groups.
Items are shared using groups. That has home screen banners that you can use. It has the icon, like the field data collection group icon that I used, and much more inside of it. So I encourage you to go and download that model organization as well. It has a lot of really valuable content inside of it. Level 2 is what, today, is a named user.
You can create new users using that level 1 role. If you want some tips, create a dedicated group for field data collection — all the users that you have in the field, like your sponsor, and others. Part VII: And it saves it into a folder. That layer is the foundation for all of the data types that you can collect in the field that are specific to water violations.
I can create new folders. I just want to point that out now this is that new item that we created. It sees a water violations. First, you see that well clearly it has a thumbnail that you could modify if you want. And like I mentioned earlier, the model organization has a bunch of icons if you want to spruce that up. Also you get to the layers within.
There happens to be one layer here: By default, this template has them already enabled for us. A good one as a rule of thumb, especially if you share in a group where you let anybody access it, is preventing it from being deleted. So you can protect it by deleting that or by preventing that web layer from being deleted.
Part VIII: Check by default. You can also keep track of who created in last updated features. So you have this audit trail on your features based upon who the editor was.
Then you can actually control the type of editing.