Latest Contributions by Kylie

Collector for ArcGIS 17.0.4 is now available on iOS. This release addresses a few bugs introduced with 17.0.3, including BUG-000108532 (subtype codes show instead of descriptions). ... View more

We often talk about how easy it is to collect data using Collector. But Collector participates in two major workflows: data collection (and building your own asset repository) and inspection (and knowing the state of each asset in that repository). Here I want to talk about inspections. First, let’s see how you can complete an inspection in Collector. Then I’ll talk about how the data was set up and how the map was made. Inspect a hydrant Use a Try it map in Collector to do an inspection yourself. Let’s pretend we are firefighters in Naperville, IL, and need to inspect fire hydrants. The last thing we want is to find out one isn’t functional because we need it! Open Collector and select Try it (iOS and Android) or Try Collector (Windows). You don’t need to sign in to use some sample maps and try out the UI for yourself. From the list of maps, select Hydrant Inspections. The map opens, and since I gave the app permission to use my location, the app zooms to where I am. If you’ve played with Collector before, you might notice that there isn’t a button to create a new feature! That’s OK, in this map, our inspections are going to be associated with features already there. We won’t be creating new features. Since we aren’t creating features, we need to go to where they are. Search for Naperville, IL, and you’ll see the hydrants. Or use the bookmark for the default map extent to see them. Select one of the hydrants (which one doesn’t matter) and see some information about it, including its identifier, last service date, and if it is operable. We’ll pretend that is the hydrant we are inspecting. Since we are doing an inspection, and not doing servicing or changing anything, we don’t want to change the details (attributes) of the hydrant itself. Instead, we’ll log a report. Inspections can be important over time, so we want to allow the hydrant to have multiple such reports. At the bottom of the details, there is an Inspection section with options for View and New. Select New to add your report. A form opens, prompting you for the information you’d want to report while doing your inspection. For example, if it needs paint, or draining, you can submit that information here. For this inspection, we want to be sure to include a photo of the hydrant’s current state. Take and attach a photo using the attachments button (a camera on iOS and Windows, and a paperclip on Android).   Submit your mock inspection. You are taken back to the details of the hydrant. Select View in the Inspections part of the details, and you’ll see your new inspection is associated with your hydrant. If other inspections of the same hydrant have been done, you see them as well. The data Key to the inspection workflow is how multiple inspections are all tied to a single hydrant. They can share many of the details of the hydrant, such as its identifier, location, and manufacturer. But each inspection is also important in and of itself, and the latest one shouldn’t replace the details about the one before it. To achieve this structure, the hydrants are a feature class and the inspections are a related table—since the inspections don’t have a location separate from that of the hydrants, they don’t need to be spatial. The feature class and the related table have what is known as a one-to-many relationship: one hydrant can be associated with multiple inspections. But each inspection is only associated with a single hydrant. There is a solution that gets us started. Download the Hydrant Maintenance Inspection Solution, and unzip it on your computer. That solution is built for ArcMap, and instead today we’re going to use that same data but work in ArcGIS Pro. By using the data, we’ll start with a database already populated with hydrants. If doing this for your own city, you could clear those out and start by collecting your city’s fire hydrants. Here we’re going to jump right to inspecting, though. Open ArcGIS Pro and start a new blank project. In the Contents pane, right-click Databases and select Add Database. Browse to the database you extracted from the solution, and add it to the project. In the Catalog pane, expand the HydrantMaintenanceInspections.gdb that you just added. It has three components, and hovering over each one tells a little about it: Open the properties of the components, and explore them a bit. Here are some things we’ll be able to learn: The HydrantToInspection relationship class is one-to-many. Hydrants are the origin, and the inspections are the destinations. A primary and foreign key are used to associate hydrants with inspections. Tip: To learn more about relationships and setting them up, see Relationships and ArcGIS. We want to use Collector with this data, so it needs to be available either through ArcGIS Online or ArcGIS Enterprise. To get it there, publish your data. We need to do the following to publish it: Add the hydrants layer and the inspection table to a map in ArcGIS Pro (Add a new map and drag and drop the layer and table onto it). (optional) Fix the layer’s symbology. I used “Cross 3” (double-click the existing symbol in Contents, then search for and select “Cross 3” in the Symbology pane). (optional) Add an inspection date into the HydrantMaintenanceInspection table (right-click the Hydrant Maintenance Table, select Open, and add a field). It is common to want to track when inspections were done and in this blog we’ll use the date when presenting the information in Collector. (optional) If you’d like to attach images during your inspection, enable attachments on the Hydrant Maintenance Inspection table (use the Enable Attachments tool). Share your layer as a web layer (Go to the Share ribbon and in the Share As group select Web Layer). You’ll need to be logged in to your ArcGIS organization. Make sure you leave the Layer Type set to Feature, and in Configuration, enable editing. If you want to use your map offline, enable sync as well. Publish your layer. The map Collector works with web maps. So once we have our feature class and related table available in ArcGIS Online or ArcGIS Enterprise, we need to add them to a web map. In your portal (ArcGIS Online or ArcGIS Enterprise portal), add the newly published layer to a new map. We don’t want inspectors to be changing the hydrants themselves, so disable editing on the hydrant features (click More Options for the layer and select Disable Editing). The hydrant features are how we’ll access our inspections. We’ll use most of the defaults for the hydrant pop-up, but we do want to configure it so that the inspections show with newest inspections first. Make sure you are configuring the pop-up for the hydrants (features), not the inspections (in the table), and use the Sort Options button at the bottom of the Configure Pop-up pane. If we wanted, we could further customize the pop-up in the map. Be careful: if you disable Show related data you won’t be able to add or view inspections on your hydrants. In the hydrant pop-up, the title from the inspection pop-up is used when showing the related inspections. Let’s configure the title of the inspection (table) pop-up to have some meaningful information like the inspection date and inspector. We could further customize this pop-up, as well. Doing so would customize the inspection form filled out in Collector. Save all the changes you’ve made. Open the map in Collector. The functionality of the map we just created matches that of the one we explored earlier in this blog.   Now you've used related records to capture inspection data in Collector, and even set up the data and map yourself. We stayed connected, but you could use this same map offline as well. If your company does inspections, now you can now bring those inspection workflows into Collector. ... View more

Wall-mounted maps have "You are here" bubbles, and our phones use a dot on the map to show current location. But those are clearly not determined the same way: a wall-mounted map always has the same location, while your phone moves about with you. And how your location is determined varies between devices and even app to app on a single device. To best understand the location information presented for mobile workers in Workforce (both our own as a mobile worker, those of other mobile workers, and those of our mobile workers when a dispatcher) we need to understand how location is determined in Workforce. First, let's understand what the dispatcher is seeing. The location presented for each mobile worker is simply the location the mobile worker's device is passing to Workforce. Once we understand how the mobile device is handling the mobile worker's location, we'll also know how the location the dispatcher is seeing is determined. The only catch is that the location isn't updated for dispatchers continuously; instead, the mobile worker's device updates the mobile worker's current location every minute. This is the location displayed in the web app. When a mobile worker sees the location of another mobile worker in the same project, their view of that other mobile worker's location aligns with that the dispatcher sees. While they are receiving the same information from the project, it might not exactly match the dispatcher's view. In addition to the offset introduced by mobile workers updating their location with the Workforce project every minute, the mobile worker reading the location is also only checking for updated locations every minute, so the position seen can be up to 2 minutes old. Now let's look at the mobile worker and their device, as that is the key to all the locations. Workforce uses the location provided by the device's location services. What exactly that means depends on the device and its setup, but what we need to know is that location services determine position information from various sources, such as GPS, cellular, Wi-Fi, and Bluetooth networks. Here is a bit more detail into location services: The location reported on the mobile device depends on the information available to the device. If your device doesn't have GPS, it uses a combination of cellular and wireless signals to determine your location. If your device also doesn't have GPS or cellular service, wireless signals are used. GPS generally provides the most accurate locations, after that Wi-Fi, then cellular. A more accurate location means that its margin of error is less. Your position might be identical, but if you know you have 10 meter accuracy, you know you are likely within 10 meters of the location shown. If you have 30 meter accuracy, you know you are likely within 30 meters of the position shown. In Workforce, the blue circle around your position indicates the accuracy. In the image below, Workforce believes you are between the tree and the other mobile worker (green pin). However, you might be closer to the green dot, or you might be with the other mobile worker. But it is pretty sure you are inside the bigger blue circle. On Android, you can choose a mode for your location (High accuracy, Battery saving, Device only). This changes what is used to calculate location. High accuracy (the default) uses GPS, Wi-Fi, cellular, and other available sensors through Google's Location service to get the highest-accuracy location. Battery saving doesn't use GPS, using only Wi-Fi and cellular through Google's Location service, saving battery. Device only uses only GPS, turning off Google's Location service. Changing this value affects the location you see in the app. One last thing to understand about location services on iOS: they never provide an accuracy less than 5 meters. Even if you are using an external GPS with sub-meter accuracy, Workforce uses location services and while the position used could be more accurate, the accuracy reported will still be 5 meters, at best. You might notice this if you look at the historical tracks of where mobile workers have been. A mobile worker will see their position updated continuously. However, as mentioned earlier, they don't update the Workforce project with the same frequency. The project is updated every minute. Additionally, if the mobile worker sets their status to On Break or Not Working, their location is not updated to the project at all until they return to Working. And if the mobile worker didn't set their status to On Break or Not Working before shutting down Workforce, the location the project has for them might be outdated and show them still working. Got it, you might think. But then you open Collector, and see that your location has better accuracy than you are seeing in Workforce! What is going on here? Well, it actually isn't too complicated: Collector doesn't always use the device's location services, bypassing it for the information coming straight from the location sensor (such as an external GPS). Location services are limited in the accuracy that they'll report, even if the device is getting a better accuracy from the location sensor. Because accuracy is critical in data collection, Collector uses the most accurate information available. Workforce, on the other hand, doesn't have the same requirements, so uses the most easily accessed information. Now you should understand how Workforce determines the location of mobile workers, what factors contribute to its accuracy, why it might vary between members of the same project, and why it might vary when using other apps. Now when you see worker location and it doesn't seem they are in the right place, yet the workers insist they are, you'll be able to figure out what it is you are actually seeing and how, if necessary to your project, to improve that information. ... View more

When using Collector to do data collection in the field, there are workflows that require you to collect similar things one after the other. There are two common workflows where I see this: Collecting many things of the same type, but in different locations. For example, you might be walking down the street collecting all the light posts, or through a field and collecting all the orange trees that were just planted. You might be collecting all the addresses or pipe segments in a new housing development. Collecting multiple things that are all in the same place, but have different qualities.  For example, a pole and a transformer that is on it. Whatever it is you might be collecting, you don't want to have to tap Collect new and type the same attributes each time. That is time-consuming and leaves room for human error. And you don't have to: set the Collection Style setting to Continuous and each collection you complete will initiate a new collection. You'll get to choose if attributes, location, both, or neither from your previous collection are brought into your new collection, saving you from providing the same information over and over. Let's try it out. You can use any map, but for this post, I'm collecting palm trees for the City of Redlands. In a newly developed area of town, palm trees are being planted lining the road. They are the same type of tree, the same height, and planted on the same date. These fall under the first type of workflow: I have a lot of things with similar attributes, each at a different location.  Open Collector, and in the Settings, set Collection Style (iOS or Android) or Collection mode (Windows) to Continuous. Open the map, choose a feature type, and provide the details about it. For my note, I pick California Palm, provide species information, set the planting date to today, and provide a height and diameter. I also took and attached a photo of the tree. Submit the collection, and choose what information you'd like to start your new collection with. Since I'm going to continue at the next tree, which has the same size and planting date, I picked Like the last one, at my location, copying attributes but using my new location. My new collection starts, and I can see the attribute values I provided before, along with my new location on the map. I don't see the photo I took, but that is expected and appreciated as I'll take a new photo of this tree. Update any attributes that you need to, and add any attachments. I take a new photo and make sure my other information is all in place. Submit the second feature. I now have two trees with detailed information on my map, and Collector is prompting me for the next. While this is a pretty simple example, think about all the data you have for your organization where the attributes are similar, or the geometry's shape repeats. Try out Continuous collection to get your job done faster and with less human error. Some things to keep in mind: Attachments and related records are not copied, as those are usually unique to the feature they were collected with. If your data uses related records, this setting only applies to collecting parent feature types (for example, light poles) but not the children (for example, the lights associated with each pole). When collecting child features, you won't be prompted to start your new collection. If you are recording GPS metadata for your points, and you duplicate the location (either with Like the last one or At the same location) the GPS metadata is also copied. If you are recording GPS metadata for your points, and you use a new location (either with Like the last one, at my location or New feature) the GPS metadata is captured as part of capturing the new location. If you are adding a feature similar to one already on your map, not similar to the one you just collected, check out Copying the feature. This gives similar options that will save you time and reduce errors. Continuous collect used to be restricted in maps containing features that participated in relationships. That restriction was removed in June 2017 as part of version 17.0.1. ... View more

To explore Collector, the "Try it" maps (available before you sign in) are a great starting point. They let you jump right into the app and see what it can do. But the next question is always "How can I get my own data in the app?" Users starting on their data from scratch should take a look at the ArcGIS Online and ArcGIS Enterprise templates. This blog answers their question, showing how to use the templates and, in five minutes, be out in the field with your own data in the app. It takes three steps:  Create a feature layer (tip: use templates!) Put your layer in a map Open the map in Collector and get to work  First, create a feature layer While there are multiple ways to create a feature layer, using the Feature Layer templates available in ArcGIS Online and ArcGIS Enterprise is a great way to quickly create a layer in your ArcGIS organization. While a variety of templates are available (and worth exploring!) in this blog you'll use the Field Notes template. Sign in to your ArcGIS organization using either ArcGIS Online or your ArcGIS Enterprise portal.  Go to Content, and in My Content click Create and choose Feature layer to open the New Hosted Feature Layer dialog. If you are using ArcGIS Enterprise your screen will look a bit different, but the same options are there.  Scroll to or search for the Field Notes template, and select it. Click Create in the panel. For now, you just need a single point layer. Make sure Field Notes (Points) is enabled, and uncheck the other layers. Click Next. Set the extent for your layer and click Next. Provide a title, like Field Notes. You might need to include your initials in the name to get a unique layer name. Click Done to create your layer and see its item page. Second, put your layer in a map Now that you have a layer for the data you collect, put it in a map that you'll open with Collector. Go to the item page of your layer, if you aren't already viewing it. Click the drop-down next to Open in Map Viewer and click Add to new map. Because you are collecting data into the layer and will want to see it on your screen, you'll want the layer to update on the map regularly. Hover over your layer, click the More Options ellipses, hover over Refresh Interval, and provide an interval of 0.1 minutes. Save the map. You'll need to give it a name (like Field Notes) and tags. Third, open the map in Collector and get to work Now that you've made the layer and the map, open the app and get to work. Open Collector on your device (Android, iOS, or Windows 10).  Sign in to your organization. You'll want to use the same account that made the map, as you haven't shared it yet. Browse to the map you just made and open it. Tap Collect + (or go to the Collect new panel on a tablet) and select a type of note to start your first collection.  Your GPS will be used to add the point, or you can use the map to set a different location. Provide a name for your note, and any other information you'd like to fill out in the form.  Tap Submit (the checkmark on Android) to add your note to the layer. Go back to your web browser and look at the map you made. Within a couple seconds, you'll see your note appear on the map. In three steps you've created a feature layer, made a map, and brought your data into Collector, where you can collect the data that matters to you. Although we didn't try it here, you can add attachments to your data, and even work offline. While you might need to collect field notes, there are templates that provide the data structure for a number of industry-specific projects, too. Go take a look at them, and see what data your organization could bring into their GIS. Have a suggestion for another template? Let me know! ... View more