Skip navigation
All Places > GIS > Applications > Collector for ArcGIS > Blog

On Monday, March 12th, we released an update to Collector on the Windows 10 platform. Version 18.0.1 is a small, focused bug-fix update that addresses a number of issues that are affecting customers.

You can find the list of specific issues that were resolved in the What's New section of our Collector doc website.

Version 18.0.1 updates to both the iOS and Android platforms are coming soon!

Collector has documentation, but while out in the field mobile workers often need something lighter weight—something that can be printed and taken along (especially if working offline). They need a single reference sheet that helps them with common tasks and some issues.

 

We’ve always relied on admins and project leads to create these for their mobile workers (and to those of you that have shared yours with us, thank you!). While there are some project specific components, there is a lot that is common in such sheets. We’ve taken some of the common questions and tasks and compiled them into a template you can use to jumpstart creating your own cheat sheet for your mobile workers, and it is attached to this post for you to download, customize, and use.

 

This is our first draft, so we’re looking for your feedback. Is this something you’d use? What works for you in it, and what would you change? Is there something missing? Is there extra info that you don’t want to see? Leave a comment and let us know! If you’d like to share your customized version with us, please email it to Collector4ArcGIS@esri.com so that we can see how you use or plan to use this template.

Working in the field, you might be near your asset but not right at it. In Collector’s Aurora Beta you can use the compass to get right to where you need to be. The map orients itself the direction you are facing and a guideline shows the direction to the asset.

 

I recently used it to find a fire hydrant. Once I was close and looked around, the compass told me exactly which way to face to see it. In this case the hydrant was visible, but if it was obstructed I still would have found it.

 

 

Try it out:

  1. Tap an asset on the map that you want to find.
  2. Tap Overflow  on the toolbar below the asset’s details.
  3. Tap Compass .
  4. Follow the guideline to the asset you were looking for.

 

If you are not close to your asset and need to navigate streets to get there, use Directions  (also available in the asset's overflow) before you use the compass. With this Beta you can pick which navigation app you want to use for directions: Apple Maps, Google Maps, Navigator for ArcGIS – use the one that works for you.

The first beta of Collector’s Aurora project is available on iOS! All of you that expressed interest in iOS should have a TestFlight email and access to the beta. To get you started exploring the app, here are 5 things to try out with this beta:

 

  1. Open better-looking maps
    Create great looking maps in your portal and open them in Collector. Use vector basemaps, labels (including using Arcade expressions), and advanced symbology. See how they perform and look, even rotated.
  2. Use the new cross-hairs for placing your points
    When editing, the map uses a target to place the point so that your finger doesn’t get in the way of seeing where you are placing it. Use the GPS or move the map to get the cross-hairs over the location for your point.
  3. See the map and attributes together
    You can see both the map and the attributes at the same time. Slide the new panel up and down, seeing more or less of the map, as you need.
  4. Edit attributes inline
    You don’t need to leave the split view to edit your attributes, either: edit them in place.
  5. Quickly access the camera
    In one tap, get to the camera so that you can take a picture of your asset.

 

 

These are some places to start your exploration, but dig in to the app and check out all the changes we’ve made! Collect points, lines, and polygons. Use streaming, and GPS averaging. Take your maps, and the maps you’ve wanted to make, and see how they do. Keep in mind that this is the first of a series of betas, so not all the functionality you know and love in Collector today is included. In particular, you won’t find offline workflows, high accuracy GPS, or related records supported yet.

 

We are ready for your feedback. Come on over to the Early Adopter community and join the discussions.
If you haven’t signed up for the beta yet, email CollectorBeta@esri.com.

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).

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!

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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).
     
  6. Submit your mock inspection.
    You are taken back to the details of the hydrant.
  7. 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.

 

  1. Open ArcGIS Pro and start a new blank project.
  2. 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.
  3. 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:
  4. 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.
  5. 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.

 

  1. In your portal (ArcGIS Online or ArcGIS Enterprise portal), add the newly published layer to a new map.
  2. 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).
  3. 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.
  4. 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.
  5. Save all the changes you’ve made.
  6. 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.

Following the 17.0.3 release of Collector for ArcGIS on the iOS and Windows platform, we are pleased to announce the release of Collector on the Android platform this evening!

 

The Android release includes the following key features introduced late in September on the iOS and Windows platforms:

  • New 95 percent confidence interval setting
  • Managed App Configuration with ArcGIS Enterprise
  • Passing collection information through the URL scheme

 

However, there is one big addition that is specific to the Android platform that has been added as well! Collector now supports integration with Trimble Catalyst. With Catalyst, Collector now has high accuracy GNSS data capture on demand. This new product from Trimble features a subscription-based software GNSS receiver that is capable of streaming centimeter accuracy to Collector when you need it.

 

CH2M and the City of Centennial joined our Collector beta program for Trimble Catalyst. Here is a blog article that discusses their success.

 

This release marks a major milestone for Collector. We are now heading full steam into the development of the next big evolution for Collector - the Aurora Project

 

Thank you,

 

Collector Team

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:

  1. 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.
  2. 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. 

 

The new row of trees

 

  1. Open Collector, and in the Settings, set Collection Style (iOS or Android) or Collection mode (Windows) to Continuous.
  2. 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.
    The first palm tree
  3. Submit the collection, and choose what information you'd like to start your new collection with.
    Continuous collect choices
    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.
  4. 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.
    New tree's attributes
  5. 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.

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: 

  1. Create a feature layer (tip: use templates!)
  2. Put your layer in a map
  3. 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.

  1. Sign in to your ArcGIS organization using either ArcGIS Online or your ArcGIS Enterprise portal. 
  2. Go to Content, and in My Content click Create and choose Feature layer to open the New Hosted Feature Layer dialog.
    Create > Feature Layer
    If you are using ArcGIS Enterprise your screen will look a bit different, but the same options are there. 
  3. Scroll to or search for the Field Notes template, and select it. Click Create in the panel.
    Create from a template
  4. For now, you just need a single point layer. Make sure Field Notes (Points) is enabled, and uncheck the other layers. Click Next.
    Select only the point layer
  5. Set the extent for your layer and click Next.
  6. 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.

  1. 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.
    Add to new map
  2. 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.
    Set a refresh interval
  3. 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.

  1. Open Collector on your device (Android, iOS, or Windows 10). 
  2. Sign in to your organization. You'll want to use the same account that made the map, as you haven't shared it yet.
  3. Browse to the map you just made and open it.
  4. Tap Collect + (or go to the Collect new panel on a tablet) and select a type of note to start your first collection. 
  5. 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. 
  6. Tap Submit (the checkmark on Android) to add your note to the layer.
  7. 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!

We are pleased to announce the release of Collector for ArcGIS v17.0.3 on the iOS and Windows platforms today. The Android platform will be following shortly with a release in October.

 

Here are the top 3 key features of this release:

1. Passing collection information through the URL scheme
When using the custom URL scheme to open Collector through another app, a website, or an email, you can now include information to start a collection. Pass information about the layer to add a feature to, as well as particular attributes and the values to assign to them. This improves integration with Workforce for ArcGIS as well as 3rd party app integration coming with CityWorks.

 

2. New 95 percent confidence interval setting

When doing data collection, Collector allows you to specify the accuracy you require to use the GPS to collect locations. By default, accuracy is calculated using RMS, however government agencies like the USFS and BLM require accuracy be calculated using a 95 percent confidence interval. We are now providing this option.

 

3. Use Managed App Configuration with ArcGIS Enterprise
Streamline your app deployment by pushing the URL of your ArcGIS Enterprise portal through your mobile device management (MDM). When your users open the app, they'll see the OAuth screen from your portal.

In addition to these new features, there are a number of bug fixes and improvements that have been made. 

 

Please refer to our What's New section of the documentation site for the full list of updates.

 

Collector Team

During an emergency event, being able to deploy field solutions that aid response and recovery efforts are not only mission critical but extremely time sensitive.

 

Debris Reporting is a configuration that supports Emergency Management organizations in collecting and monitoring debris. You can find details of this configuration on the ArcGIS for Emergency Management site

 

This blog article will illustrate, step-by-step, how you can build and deploy a debris reporting field solution with Collector for ArcGIS in minutes using a template within ArcGIS Online. 

 

Step 1: Create A Debris Reports Feature Layer

                         

We have included Debris Reporting as a template within ArcGIS Online, so when you sign into your ArcGIS organization, click on Content and then click Create Feature Layer.

 

Create Feature Layer

 

From the New Hosted Feature Layer dialog, type debris in search, click to select Debris Reports and then click Create.

 

 

The wizard will ask you a number of questions. With the Debris Reports layer selected, click Next, set the working area of your field collection work, click Next, provide a name for the feature layer like “Debris Reports” and click Done.

 

 

Step 2: Author a Debris Reporting Web Map

 

Now that you have created your Debris Reports layer, you are ready to create a web map that Collector can open. Click Add layer to new map with full editing control to author your Debris Reporting map.

 

 

With the map open, click on the Debris Reports layer in the TOC to see the list of report types. Each of these types will be a feature type entry in Collector. Zoom into the area that you would like to start collecting debris and consider changing the basemap using the Basemap tool.

  

Set a layer refresh interval for the Debris Reports layer so that you can see new reports that come in from the use of Collector.

 

 

 Finally, you need to save your web map and share it into a group so that others can access it using Collector. Click the Save button and then enter a title, tags, summary for your map, and then click Save Map.

 

Next click the Share button and Share the map either within your organization and/or within a specific group that your responders are a member of. Note that you should be prompted to update sharing for the Debris Reports layer, click the update sharing button.

 

Step 3: Open Map and capture reports using Collector for ArcGIS

 

On your smartphone or tablet device, with Collector for ArcGIS installed from either the Apple App Store, Google Play or the Windows Store, sign into your ArcGIS organization and then search for the map you just created.

 

 

Once found, you can either tap on the map itself to open it directly and start capturing debris reports while connected or you can tap on the download button, download a map area to your device and then collect data when you are offline.

 

Tap on the map thumbnail to open the Debris Reporting map. With GPS enabled, the map will zoom to your current location and use that location for the collection of reports. Press the + button to start the capture process and then tap on the Vegetation report type.

 

 

With the Vegetation feature type chosen, Collector will automatically use your GPS position as the location of the debris report. You can then fill out the Type of Debris, Details, provide a name, set a submission date, etc. Tap the camera button to open the camera on your device and take one or many photos of the damage and then tap Done when complete.

 

 

Once you have completed the form and taken appropriate photos, you can either tap on the map button to ensure the location is correct or simply press the Submit button to send your changes back to the EOC.

 

Once submitted you will return to the map screen on your device and back in the office you will see the new debris report appear when the layer refreshes itself.

 

 

These 3 simple steps of creating a feature layer, creating a web map, and using in Collector can be completed within minutes. The solution configuration includes details for configuring an Operation View for use with Operations Dashboard for ArcGIS. Dashboards enable real-time decision making as each time a report is collected and submitted, it will appear in the Emergency Operations Center (EOC).

 

Note: In addition to using the feature templates within ArcGIS Online, you can use the Solution Deployment tool to deploy the feature layer, web map and debris reporting Dashboard.

 

Collector Team

Update: Collector's Aurora Beta is available. Already have it? Join the discussion in our Early Adopter Community

 

Collector for ArcGIS launched in the Apple App Store and Google Play in January 2013, followed by the Windows Store in December 2015.  Since its initial release Collector has evolved considerably, and as its capabilities have grown, so has its adoption and we are very thankful for your support.

 

Now the time has come for a refresh. A refresh in user experience, a refresh in technology, a refresh in field data collection workflows. So… here comes the Aurora Project.

 

Through the Aurora project, Collector is getting a number of improvements you have requested:

  • Better maps
  • Improved user experience
  • Smarter forms
  • Streamlined offline workflows
  • Enhancements to high accuracy 3D data collection

 

Most importantly, the Aurora Project brings a new foundation we will build upon to advance data collection workflows in the ArcGIS platform. Let’s take a deeper look at some of these improvements:

 

Better maps

Collector is adding support for vector basemaps (both online and offline), so that you can view crisp, high quality cartography that takes advantage of the amazing pixel density of your iPad Pro or Samsung S8+ device. Downloading vector tiles to your device will dramatically reduce the footprint of offline content on your device as well.

 

Rich symbology and smart mapping capabilities you rely on to effectively represent your spatial information and publish using ArcGIS Pro will look great in Collector.  In addition, it will support displaying labels in your map, the top idea you’ve asked for in Collector.

 

With these improved mapping capabilities, your maps will look great rotated, too!

FIMT symbology, Labeling and Heat Maps

FIMT symbology, Labeling and Heat Maps

 

Improved user experience

Significant improvements to the user experience (UX) of Collector are coming and you will see this in the very first beta release. We have spent time redesigning the collect experience so that we can streamline workflows. Some improvements include:

  1. Better layout to support your workflows – Core tools like Collect are more accessible to promote the scenarios you use every day.
     
  2. Easier capture of accurate data locations – use cross hairs that provide a “cursor-on-target” experience to precisely define location.
     

     

  3. Better use of screen real estate - let’s face it, working on a phone often leaves you wanting a bit more screen real estate.  Sometimes you want to see the map, sometimes you want to see the form, sometimes you want to see a bit of both. With our new sliding panel design, move between these views seamlessly by sliding the panel up or down to seamlessly move between map-centric and form-centric views to fit your workflow.
     

     

  4. Smarter data entry - have a lot of exciting work planned for the form, starting with the UX. Take a photo in fewer taps, capture additional media (audio, video), read information from QR and bar codes, edit in place on the form, and use a proper keyboard when editing numeric fields.

 

Smarter Forms

Forms are improving more than just the UX: you’ll find they honor the modern capabilities of the ArcGIS platform.

 

Collector is founded on the principles of the web map. Layers that you collect data into follow the guidelines set by feature layers you author and feature services you publish. The dictionary of feature types are based upon feature templates you create, and the forms experience is driven by popups you configure from the information model you create. But within that popup, support for validation of required fields, Arcade expressions, and attribute rules will be added.

 

Arcade Expressions are particularly exciting, as they will drive a smarter forms experience when editing in Collector, in web apps, and in ArcGIS Pro. Conditional logic, enrichment of data, inheritance of values from other features, grouping, and ordering of attributes will all come with this update.

 

Streamlined Offline Workflows

Collector works anywhere, anytime you need it. Maps can be downloaded to your device and you can synchronize changes when you gain connectivity. This release brings a simplified download experience, improved management of offline map areas, and the ability to keep working when you drift in and out of connectivity.

 

Within your ArcGIS organization, you will be able to plan ahead: prepare the areas to go offline, store them in your content, and share them throughout your organization. Mobile workers simply select the map areas they need and download them to their devices.

We are simplifying the interactive download experience as well as managing local content on the device. One key aspect is how you work with basemaps. In addition to packaged tile map services, Collector will support packaged mobile maps built with ArcGIS Pro and vector tiles. In the app, you’ll be able to download and manage a collection of offline basemaps.

 

Enhancements to High Accuracy 3D Data Collection

As part of this project, Collector is adding support for direct capture of 3D data. In addition, vertical datum transformations will allow you to transform elevations on the fly, eliminating office workflows usually required to achieve accurate elevations.   

 

Collector - Aurora Project Schedule

The Aurora development project is underway and the first beta of Collector’s new dawn will be this fall! We will release a series of betas, bringing new capabilities with each update. To participate in the beta, please email collectorbeta@esri.com and then join our Early Adopter Program.  Your feedback throughout the beta is important to us – we want to hear from you!

 

Our current target for release is Q3 of 2018 for the iOS platform and Q4 for the Android platform. We have not set a release date for the Windows platform yet. We know Collector is an essential part of your mobile workflows, and our goal is to make the transition easy for you. Starting with the beta releases, Collector as you know it today and this significant update will happily live side-by-side on your device.

 

Collector Team

Collector released a very minor bug fix update today to support relief efforts with Tropical Storm Harvey. This update resolves a specific issue (BUG-000107667). Please reference our documentation site for any additional details.

This fix is for the iOS platform only. We will have a v17.0.3 release coming soon on all platforms with enhanced support for app integration, Trimble Catalyst support on the Android platform and more.

On June 5th, we released a new version of Collector that is now available in the iTunes App Store, Google Play, Amazon App Store and the Windows Store.

This is a minor update but adds some strategic new enhancements that will improve the way you work with high accuracy GPS receivers, manage attachments, work with basemaps and use Collector in a connected environment.

GPS Averaging –  can be used to improve the precision of your high-accuracy collection workflows. You can capture a number of positions and create a location from the average of those positions.

Rename Media Attachments -  now you can provide a meaningful name to the photos that you take around a feature. This is one of the most requested enhancements.

SD card support (Android) -  you can use the SD card to store and manage basemaps for easier, faster deployment of data.

Continuous Collect Improvements -  now supporting feature types that contain relationship classes.

Layer Refresh Support -  if your feature layers have a layer refresh interval set, Collector will honor the refresh setting. This is valuable when working with maps in a connected state as the graphics of a feature are cached when on the device and this will force a query/update.

In addition to these updates, we have several additional bug fixes and minor stability improvements. Please refer to our documentation website for more information.

The Collector Team

During a recent EGUG Birds of a Feather webcast, Kurt Towler from Sulfer Springs Valley Electric Cooperative (SSVEC), presented on how they used Collector for ArcGIS with Eos Positioning GNSS receivers to inspect 7,640 locations, capture over 34,000 asset records in just 32 days. That's 235 collections per day! Paired to the Eos Arrow receiver, their median accuracy was 4.6 cm, dramatically improving the accuracy and currency of their data.

 

The webinar was recorded and uploaded to YouTube. You can view it here: