Survey123 for ArcGIS ... | GeoNet [PDF]

All Places > Survey123 for ArcGIS > Blog

Survey123 for ArcGIS

1 2 3 …

98 posts

Paper Airplane Day Release (2.8) Posted by ichivite-esristaff

May 25, 2018

Previous Next

Do you know the difference between a dart and a glider? Well you should, because you will want to make good use of all those paper forms you no longer need. Get ready for National Paper Airplane Day , which is coming up on May 26! What goes through your mind while folding a piece of paper to make an airplane? What do you feel when it escapes your fingers gliding away? Paper airplanes are truly amazing. Take a moment to enjoy them, if possible with good company.



We split our 2.8 update in two. Just a few days ago we released the Survey123 field app with a critical fix for all of you using the app with public surveys. We also included a couple of additional bug fixes. For more details refer to the Minor update to the Survey123 Field App Available (2.8) blog post. Today, we are making available an update to our Survey123 website. It comes with some bug fixes, but also brings a few interesting new features. Here are the highlights:

Survey123 Web Designer Enhancements Survey123 Web Designer lets you visually build your own surveys, right from your web browser. In this update, we have added features particularly useful for those of you who plan to publish surveys for exclusive use from web browsers (Web Forms). New Single Choice Grid questions: Survey123 web designer now includes a new type of question called Single Choice Grid. This question type lets you to arrange a set of single choice questions in a table. The only condition is that all single choice questions in the table use of the same choice list. There are multiple scenarios where Single Choice Grids are useful. A classic one is checklists, like the one presented below for a Fire Safety inspection.

Single Choice Grids will help you compact questions within your forms allowing users to enter data more easily. As you add Single Choice Grid questions into your form, keep in mind the following: Horizontal real estate is going to be limited, so keep the number of choices in your lists and labels short. You cannot set rules against the Single Choice Grid or any of the individual questions in it. If you choose to flag the grid as required, then all rows (questions) within the grid must contain an answer. Single Choice Grids are only supported in Web Forms (in our Survey123 Web App). The Survey123 Field app does not currently handle this type of question. Custom Thank You Notes: Thank You notes are presented right after a survey is submitted from a Web Form (from the Survey123 Web App). It is good practice to control the text presented in this dialog. This is of course the right place to thank respondents for taking time to complete your survey, but also a great place to acknowledge sponsors of your project or direct respondents to your website, next actions etc. Starting with this update, we added a rich text editor widget so you can better control the look and feel of your Thank You notes. You can add links, images, define the size and color of text and more.

From within Web Designer you will be able to preview your Thank You note and also control if a link should be included to allow respondents to submit the survey again. Geosearch for Geopoint questions at design time: Through the new geosearch widget included in geopoint questions, you can now more easily set the initial extent and zoom level of your map. This is particularly relevant for online surveys where people will submit data through a Web Form. When your survey is open from a web browser, you cannot assume that the map will be centered automatically at the user's location, because often location services are disabled in browsers for privacy reasons. With this new geosearch widget there is really no excuse for you to leave an initial map extent that is not relevant to your project!

Note: The geosearch widget uses the default locator configured in your ArcGIS Online organization

.

Survey Collaborate Tab Through the Collaborate tab in the Survey123 website, you control who can submit data to your surveys, and who can view their results. Restrict Viewer Access: Through the Viewer category in the Collaborate tab, you define which Groups within your ArcGIS organization can visualize the results of your survey. We have added a new option that lets you control if access to the survey results is restricted to survey entries submitted by the logged-in user, or all results in the survey.

As the owner of a survey, this option gives you tighter control over what data can people see in your surveys. Here is a scenario where this new option will be handy: Pretend that you have published a survey for a group of Building Inspectors. Through Collaborate/Submitter you have already granted them access to your survey, so all Building Inspectors are happily submitting their work to you. Next, you would also like Building Inspectors to have access to their own submitted data through the Survey123 website. Through Collaborate/Viewer you will next grant the Inspectors Group with access to the results of the survey, but since you do not want inspectors to see someone else's work, you will grant visibility to 'Only their own submitted records'. At that moment, inspectors can log into the Survey123 website and access their own records. For example, they can use the Data tab in the Survey123 website to export all their inspection data into Excel, generate high quality printable reports of their inspection records or even look at trends across their own inspections through the Analyze tab. Administrators of the ArcGIS organization and owners of the survey will always have access to all records. Shortened survey URL links (ArcGIS Online only): If working against ArcGIS Online, the next time you share a survey URL with someone or include it into a website or e-mail, you will note that the Survey123 website will shorten them for you. The animation below shows the difference between the shortened and original URLs.

We feel like shortened URLs are easier for most people, but if you are a nostalgic, purist or you simply want the original URL, all you need to do is to copy the shortened URL into a web browser and navigate to it. You will see that the shortened URL is simply a shortcut that gets redirected to the source (and long) URL of your survey.

Survey Analyze and Data Tabs Photo Galleries in the Analyze report: Up until now, Image and Signature questions in your survey were not included in the Analyze report. Starting with this update, photo galleries will be used to display data submitted into Image and Signature questions.

The new galleries will let you more quickly scan large collections of photos submitted to your survey and if needed, by clicking on them, get more details on the photo itself. Sort surveys by date in the Data tab table: The Data tab shows your survey results as a map and a table. Some of you suggested that data in the table should show the newest surveys on top by default. We think this is a good idea too, so rows are now sorted by the Edit Date column, in descending order. If you would like to sort using a different column, all you need to do is to click on the column header and set your sorting preference. Barcode question support in Individual Response reports (Data tab): The individual response report shown when you select a record from the survey table now supports Barcode questions as well, which are treated similarly to Text questions.

Survey Gallery Launch Connect directly from the survey gallery: You can now easily launch Survey123 Connect from the survey gallery to make updates and re-publish your Connect surveys. This option will only work if you have Survey123 Connect 2.7 or newer. I trust you will have Connect in its latest release. Right? You would actually not believe how many people out there are still running 1.x versions of Connect!



Major Bug Fixes and Enhancements Survey123 Web Form (aka Survey123 Web App): BUG-000108086 Field values are missing in questions within repeats (Web Form) BUG-000109787 Pulldata caculations within a repeat do not update note questions if the survey is open from a web browser. BUG-000108785 The message "Surveys published by Survey123 Connect for ArcGIS are currently not supported" appears when attempting to open a survey published with Connect from a web browser, if the hosting portal is configured with Integrated Windows Authentication. Survey123 website: BUG-000113180 Unable to share a survey with a group when the user is a group manager of that group in ArcGIS Online and the group setting 'who can contribute' is set to 'Only group owner and managers' BUG-000113270 With Portal 10.5.1 configured with IWA, surveys published using Survey123 Connect do not show data for users in https://survey123.arcgis.com BUG-000113054 The data tab of the survey123.arcgis.com website does not have appropriate logic to prevent attempting to export data that comes directly from ArcGIS Server BUG-000107294 Incorrect German translation of "Please input a number less than xx". BUG-000113741 When deleting a survey that is created from an existing feature service in Portal for ArcGIS, the behavior is different between Survey123 Connect for ArcGIS and the Survey123 for ArcGIS website Static content in the Survey123 web site is delivered leveraging Content Delivery Network Services to reduce loading times. This will be particularly noticeable outside the United States. Survey123 field app and Connect: Regression on Public Surveys: Our 2.7 release introduced an issue that prevented the use of Public Surveys if no user was logged into the Survey123 field app. This is now addressed, allowing the use of Public Surveys in the field app even if there is no user logged-in. Thanks to all of you who promptly reported this problem and helped diagnose it through this GeoNet Group. I am having problems with some users getting "unpacking errors" while opening a survey. What causes this? Problem with public survey Check for offline conditions on Windows: This update includes a fix that enhances Survey123's ability to detect if your device is connected or not, when working on Windows. We have observed some reports of Survey123 on Windows not detecting offline conditions when working on very specific network configurations. The offline check is much better now. BUG-000107663 Features do not display in webmap after submission by the field app: Some of you have reported that ArcGIS Online Web Maps with a refresh interval set , were not automatically showing new features added from the Survey123 field app. The problem was caused by a combination of issues in both ArcGIS Online feature services and the Survey123 field app. All problems are solved now! An Archive of What's new in Survey123—Survey123 for ArcGIS | ArcGIS is available in our product help documentation.

Beyond 2.8 Our next major release will be 3.0, which we envision shipping around July 2018. If needed, we may squeeze in 2.9 as a maintenance release with critical fixes. Here is what we are planning for our next updates: Custom Form Reports: Our Leveraging Custom Form Report Templates in Survey123 for ArcGIS blog post anticipated this feature, which is currently available to all of you in Beta. We are working hard to move this feature into general release and incorporate into it bulk report capabilities. Support for nested repeats: This feature is available for testing already through our Early Adopter Program This will be part of our 3.0 release in July.

and allows you to author surveys that have repeats within repeats.

Enhanced support for external GNSS receivers: At the moment, you can use external GNSS receivers with Survey123, but only in a limited way. For example, you cannot extract key metadata from the receiver such as VDOP, HDOP, Number of Satellites or the Fix Type... With the 3.0 update our intent is to extend the pulldata() function so you can also extract this important metadata and store it along with the features you capture. We also plan to provide support for RTK corrections. We are working towards having this feature available for testing in our Early Adopter Program around June around July, but will not be part of 3.0. Webhook integration: An earlier post Sneak Peek: Survey123 and Webhooks (Integromat) described this work in more detail. Available for testing today through the Early Adopter Program. Planned for our 3.0 release. GeoSearch in the Survey123 field app map widget: Check out this video in our Early Adopter Program

for details. Available for testing now and planned to be part of 3.0.

Support for Web Maps, Vector Tiles and Mobile Map Packages: This is a big deal as it will make maps for geopoint questions much better looking, useful and lightweight. Looking at having this available for testing around June. Postponed until later in 2018. Pages: While Pages are not officially supported yet, we continue working on improving this feature. Starting with 2.7 you will notice that the page navigation has been vastly improved, although there are multiple areas that still need more work before we can call it 'ready'. If you are into pages, do not hesitate providing your feedback via the Beta forum in our Early Adopter Program . Portal support: As of version 3.0 of Survey123 for ArcGIS, we will no longer support working against version 10.3.1 or older of Portal for ArcGIS. iOS support: Following Apple's announcement regarding end of support for 32 bit devices starting with iOS 11, our 3.0 release will also drop support for 32 bit devices. Having said this, we understand that many of you still have not, or don't plan to upgrade your Apple devices in the short term. Therefore we will make available a 32bit compatible version of Survey123 in the Apple store for a period of time to assist you with your transition. We will be naming this 32-bit compatible version of the app, Survey123 Classic and it will include only 2.8 functionality. Android support: The minimum version of the Android operating system with Survey123 3.0 will be 4.4. The Classic flavor of Survey123 will support Android back to 4.1, but will only include 2.8 functionality. A lot in the plate as you can see for 3.0. Our focus however it is not going to deviate from listening carefully to all your feedback through this GeoNet Group, so keep your questions and suggestions coming! Comments: 0

46 Views

Permalink



Tags: survey123

Survey123 for ArcGIS at the Esri UC 2018 Posted by ichivite-esristaff

May 23, 2018

Here we are once again, so close to the Esri User Conference ! Below is a list of the many places where you will be able to learn more about Survey123 for ArcGIS while in San Diego. The Esri Events App: If you are coming to San Diego, I recommend that you download the Esri Events app. It will help you create your own schedule and keep track of last minute changes to sessions. You can download the app from the Apple and Google Play stores. Technical Sessions: Technical Sessions are one UC's favorites. Always well attended, Tech Sessions run for about 60 minutes and cover technical aspects of Esri products. We always try to keep a good chunk of time at the end for a live question & answer section. Tech Sessions start on Tuesday morning and run until Friday. They all take place in the second floor of the San Diego Convention Center (also known as SDCC). Survey123: An introduction : This session covers the basics of the Survey123 website, including designing smart forms with Web Designer, publishing and sharing surveys, generating high quality reports for submitted data and other capabilities available through the Survey123 website. The session will end with a sneak peak of smart form capabilities going beyond what is possible through Web Designer. I recommend attending this session even if you are already familiar with Survey123, because there are many new things that have been added to the Survey123 website in the past few months. Philip Wilson, Brandon Armstrong and Derek Law will be presenting this session, and there is always tons to learn from them! Tuesday, July 10 10:00 am - 11:00 am SDCC - Ballroom 06 D Tuesday, July 10 1:00 pm - 2:00 pm SDCC - Room 32 A/B Wednesday, July 11 4:00 pm - 5:00 pm SDCC - Ballroom 06 F Survey123 for ArcGIS: Creating Smart Forms Using XLSForms and Survey123 Connect : Join this session for an introduction to designing smart forms following the XLSForm specification with Survey123 Connect. With Connect and XLSForms you can create the most sophisticated smart forms for the Survey123 native or web apps. If you want to become a Survey123 Ninja you really need to make it to this session. James Tedrick and Jonathan Hasthorpe will take care of this one. Wednesday, July 11 2:30 pm - 3:30 pm SDCC - Room 09 Survey123 for ArcGIS: Advanced Topics : This session will introduce advanced workflows with Survey123 including editing existing features and designing surveys on top of existing feature layers, workflow automation with Survey123 and web hooks, working with external sensors in Survey123 and other exciting features. There will be lots of live demos and time for live questions. Ismael Chivite, Elvin Slavik and James Tedrick will present this session. Thursday, July 12 2:30 pm - 3:30 pmSDCC - Room 05 A ArcGIS Apps for the Field: An Introduction : In this session we will describe how all ArcGIS mobile apps work together. A great place to learn how Survey123 works along with Workforce for ArcGIS, Navigator for ArcGIS, Collector and even Operations Dashboard for ArcGIS. Scheduled presenters include Chris Lesueur, Ismael Chivite and Jeff Shaner. Friday.Tuesday, July 10 10:00 am - 11:00 amSDCC - Ballroom 06 C Wednesday, July 11 1:00 pm - 2:00 pmSDCC - Room 31 C Friday, July 13 9:00 am - 10:00 amSDCC - Ballroom 06 F ArcGIS Apps for the Field: Working Together : A more technical perspective on making ArcGIS apps work together. Custom URL Scheme's described. Wednesday, July 11 10:00 am - 11:00 am SDCC - Room 08 Survey123 User Group Meeting We are happy to announce that this year we will have our own Survey123 User Group Meeting . It runs on Tuesday at lunch time from 11:30 AM to 12:30 PM, but no lunch is provided. This is for the ones with a strong Survey123 spirit! Our User Group will be a great opportunity to meet other Survey123 Ninjas. This is fundamentally about connecting with other people and the team. We will have a couple of 7-minute lighting talks to warm-up and then the rest of the time is for group discussion and networking. Survey123 User Group Meeting: Tuesday 10, 11:30 AM - 12:30 PM SDCC - Ballroom 06 D

Demo Theaters You can think of Demo Theaters as mini-Tech Sessions. They are shorter, always focused on very specific workflows and run in a small setting were questions can be handled throughout the presentation. The Demo Theaters take place in Expo area (first floor), close to the Product Islands. Improving Utility Field Workflows in ArcGIS (by Claire Price) Tuesday, July 10 11:15 am - 12:00 pm SDCC - Demo Theater 14 Survey123 for ArcGIS: Extending the App (by Elvin Slavik and Erwin Sorekianto) Wednesday, July 11 10:00 am - 10:45 am SDCC - Demo Theater 09 Damage Assessment Using Survey123 for ArcGIS (by Jess Neuner) Wednesday, July 11 11:15 am - 12:00 pm SDCC - Demo Theater 17 Survey123 for ArcGIS: Printing Survey Records (by Calvin Jung and Brandon Armstrong) Wednesday, July 11 11:15 am - 12:00 pm SDCC - Demo Theater 09 Understand the Resiliency of your Community Using ArcGIS Apps Wednesday, July 11 12:15 pm - 1:00 pm SDCC - Demo Theater 16 Invasive Pest Surveys in ArcGIS (by Aziza Parveen) Wednesday, July 11 1:15 pm - 2:00 pm SDCC - Demo Theater 14 Public Safety Field Data Collection: Best Practices (by Fern Ferner) Wednesday, July 11 2:30 pm - 3:15 pm SDCC - Demo Theater 11 Troubleshoot Like an Esri Support Pro: ArcGIS Apps and GPS/GNSS Connections (by Collin Lawrence and Kiersten Hudson) Thursday, July 12 10:00 am - 10:45 am SDCC - Demo Theater 04 User Presentations User Presentations are a great way to learn the details of how Survey123 is applied to specific workflows. A good opportunity to learn directly from users like you! Using GIS to Prepare for a National Level Radiological/Nuclear Response



Sunday, July 8 Hilton - 9:10 am - 9:30 am Sapphire Ballroom B/C/D/F/G/H GIS Supporting Data Driven Homelessness Solutions Tuesday, July 10 1:00 pm - 2:00 pm SDCC - Room 29 A Improving Human Services Through GIS Tuesday, July 10 1:00 pm - 2:00 pm SDCC - Room 29 A Public Transit GIS in the Field; A Tale of Two Apps Tuesday, July 10 1:00 pm - 2:00 pm SDCC - Room 24 C Lessons from Hurricane Harvey Response Tuesday, July 10 2:30 pm - 3:30 pm SDCC - Room 28 B ArcGIS Enterprise for the Muckleshoot Indian Tribe Tuesday, July 10 2:30 pm - 3:30pm SDCC - Room 24 A Mobile Applications in Stormwater Wednesday, July 11 1:00 pm - 2:00 pm SDCC - Room 26 A Citizen Scientists Using Survey123 to Collect Lake Quality Data Thursday, July 12 8:30 am - 9:30 am SDCC - Room 26 A Utilizing Survey123 and ArcGIS Online to Improve Damage Assessment Thursday, July 12 8:30 am - 9:30 am SDCC - Room 28 B GIS and the Eclipse: A New Tool for Emergency Management Thursday, July 12 8:30 am - 9:30 am SDCC - Room 29 B Expo The Expo area is opens Tuesday and closes on Thursday afternoon. It is located in the first floor in the San Diego Convention Center (SDCC) and features different areas including Partner Exhibits, Esri Industry Neighborhoods, GIS Product Areas and Customer Care booths. Product Areas (Islands) at the Expo: You will always find someone from the Survey123 team in there. This is the place to go when you want to have a one on one conversation to address specific ideas or issues you may have. We often refer to the Product Areas as Islands. The Survey123 team will have a station under a big sign that says 'Apps'. It will be a big sign... you will see it. Partner & Sponsor Exhibits: The Survey123 software is only a third of the story. There are two good reasons to visit the Esri Partner and Sponsor Exhibits. The first one is that many of them are now experts building smart forms with Survey123 and know the tricks of the trade when implementing solutions. Swing by their booth and ask them about their own experience. The second one is that through the Partner Exhibits you will find many hardware vendors that can teach you the benefits of using their offerings with Survey123. Think Laser Measurement Solutions, GNSS receivers, ruggerized devices and much more. Just to name a few: EOS Positioning Systems GIS Inc Leica

, booth 1019

, booth 719 , booth 517

Microsoft

, booth 2227

SSP Innovatons

, booth 619

Bad Elf LLC , booth 2330 Blue Raster LLC , booth 2408 Frontier Precision Inc GeoDecisions

, booth 2027

, booth 609

GPS-it ltd

, booth 708

Handheld

, booth 530

ikeGPS , booth 2231 Juniper Systems

, booth 1815

Vestra Resources

, booth 2314

International Association of Fire Chiefs NAPSG Foundation

, booth P1 (Public Safety Kiosk)

, booth P3 (Public Safety Kiosk)

Customer Care and Esri Tech Support: Our Esri Customer Care and Technical Support teams will be represented in the Expo. You can also swing by their stands with your Survey123 technical questions. Esri Industry Neighborhoods: Everything from Public Safety to Defense, Local Government, Utilities and more. The Industry Neighborhoods are a good place when you want to connect with people that understands how to put Survey123 in the context of your own workflows. Ask for a demonstration of Survey123 focused on your problem or for examples of organizations using Survey123 in your industry. Esri Education Summit The Esri Education Summit

takes place between July 7-10 at the Marriott Marquis & Marina Hotel. You will need to register separately

Using Survey123 for Citizen Science and Crowdsourcing Initiatives

for this one!

(by Ismael Chivite)

Saturday, July 07 10:00am - 11:00am Marriott - Point Loma Mobile Field Data Collection with Survey123

(By Joseph Kerski)

Sunday, July 08 2:30 pm - 3:30 pm Marriott - Cardiff From Story Maps to Survey123: GIS in K-12 Education

(by Michael Jabot)

Sunday, July 8 8:30am - 9:30am Marriot Newport Beach Introducing Web-based GIS using Survey123 and ArcGIS Online

(by Dan Farkas)

Sunday, July 8 Hilton - 10:00 am - 11:00 am Marriot Coronado Pre-Conference Seminars By now, many Pre-Conference Seminars are sold-out, but I thought I would include info about this for those of you who are planning to come next year. You need to hurry before all seats are taken. Survey123 will be highlighted in the Field Operations and ArcGIS PreConference seminar: Field Operations and ArcGIS A full day hands-on seminar covering the complete suite of ArcGIS apps: Workforce, Navigator, Survey123, Collector and Operations Dashboard. Sunday, July 08 8:30 am - 5:00 pm

Comments: 0

105 Views

Permalink



Tags: survey123, uc 2018, esri uc 2018

Minor update to the Survey123 Field App Available (2.8) Posted by ichivite-esristaff

May 15, 2018

A minor update to the Survey123 field app has been made available in the Apple, Google Play and Amazon or desktop computer, the setups are also available for Windows, Mac and Linux .

app stores. If you happen to use the Survey123 field app on your laptop

The build number for the Survey123 field app and Connect is now 2.8 This release includes a handful of critical fixes: Regression on Public Surveys: Our 2.7 release introduced an issue that prevented the use of Public Surveys if no user was logged into the Survey123 field app. This is now addressed, allowing the use of Public Surveys in the field app even if there is no user logged-in. Thanks to all of you who promptly reported this problem and helped diagnose it through this GeoNet Group. I am having problems with some users getting "unpacking errors" while opening a survey. What causes this? Problem with public survey Check for offline conditions on Windows: This update includes a fix that enhances Survey123's ability to detect if your device is connected or not, when working on Windows. We have observed some reports of Survey123 on Windows not detecting offline/online conditions when working on very specific network configurations. The offline/online check is much better now. BUG-000107663 Features do not display in webmap after submission by the field app: Some of you have reported that ArcGIS Online Web Maps with a refresh interval set , were not automatically showing new features added from the Survey123 field app. The problem was caused by a combination of issues in both ArcGIS Online feature services and the Survey123 field app. All problems are solved now! We plan on updating the Survey123 website in the next couple of weeks, bringing a handful of enhancements and fixes. Stay tuned. Comments: 10

658 Views

Permalink



Tags: hot fix, survey123

How to create buttons to invoke survey123 from workforce or collector Posted by rogermesengeotec May 14, 2018 There is a way to invoke #Survey123 with the fields fill. With the URL. if you want to know more about how to configure the URL is better to check the following link ( click here). In the blog Ismael Chivite explain deeply how to use the url. This blog is more about how to transform the link in a button to show a better graphic interface to the user. Basically when you have the link with the url of the form and you are setting the pop-up you can configure a "kind of button", with the following #html code. Orden de Trabajo

this code shows up the following button in collector or workforce. Depending of the pop up that you set.

As you can see is a better interface that a link for the user. I you need more information just let me know in the comments. Comments: 3

206 Views

Permalink



Tags: collector, surver123, customurl

Creating a field with the duration time generated automatically Posted by rogermesengeotec May 4, 2018 In this case I been working in one survey for a local government in Costa Rica. They need the total time that the user spend doing the survey. So I Create a start and end type of fields(important: do not use the default values of now() ) Those kind of fields automatically generate the values. The time Start create the same value of the #now(), but the end is fill at the end of the #survey. Check the image. After create the start and end field you create the #calculation field with the following #formula /* round(int(${Hora_Fin} - ${Hora_Inicio}) div (1000*60),0) */



This field is going to update automatically. Enjoy creating forms and tell me if it works for your form. Comments: 0

133 Views

Permalink



Tags: time, survey123, start, formulas, end, auto-update, time type, autofield

Extending Survey123, Part 1: White Labeling Posted by Jayson_Ward-esristaff

Apr 29, 2018

For this blog post, and the subsequent blog post on extending Survey123's functionality, I've created a user story for a fictitious municipality called the City of Cilantro that will help guide the customization process. Also, a public repo with the customized app is available at Github: Cilantro Surveys

I. User Story The City of Cilantro needs a custom version of Survey123 that will be used by various city departments to conduct public and private surveys. The city currently has three customization needs: 1. The app needs to be branded to match the organization. [Not extending core functionality] 2. The city needs the ability to print the time and location onto new photos taken with some surveys. [Extending core functionality] 3. Some surveys used in the field will include the scanning of barcodes as the only action required of the survey. The application will need to automatically submit the survey after the barcode is successfully scanned and then open a new survey immediately upon successfully submitting the previous survey. [Extending core functionality]

This blog post will address the first customization need. Updating the user interface (UI) to match an organization's branding doesn't affect or amend the application's core functionality and requires no coding experience (there is one caveat to this currently which is noted in section III.4). Let's first look at the asset's needed to create the custom look and feel before downloading the template.

II. Assets & Information Needed a. App Name The app should have a distinct name. It should not be called Survey123. For the City of Cilantro, 'Cilantro Surveys' was chosen as it referenced the city's name and also kept the name simple and succinct.

Cilantro Surveys

b. Branding Color The Survey123 application has one main color used throughout the UI that 'brands' the look and feel. Survey123's branding is built around a hue of green, and can be seen throughout the UI of the application as well as the website and associated marketing materials. When customizing Survey123, it is highly recommended that a different color be used in order to help distinguish the app from Esri's production version of Survey123. The color should ideally match the branding guidelines and needs of the organization that is customizing the app. The City of Cilantro uses a brown hue in their logo, so that same hue of #543e36 will be used in the custom app.

#543e36

c. App Icon The app icon is what the user will see in the device's user interface and will be touched or clicked to open the app. 512 × 512 (pixels) .png file

d. Launch Screen Image Overlay The launch screen overlay is a graphic that will appear above a colored background when the app is launched into the device's memory. 768 × 768 (pixels) .png file Should include transparency or the background color should match the color set for the background color in the app's settings. In this example the image includes white graphics on a transparent background. The background color is set to #543e36 in app's settings.

e. App Thumbnail [for ArcGIS only] The app thumbnail is used to help distinguish the app in ArcGIS galleries. It is used throughout the web and AppStudio to visually reference the application item. 200 × 133 (pixels) .jpg or .png file

f. Company / Organization Logo [optional] The company / organization logo is an optional asset. If included, it will appear on the app's About view. It can additionally be set to open a custom url to an external website. Height should be a maximum of 200px. The width will be automatically adjusted to preserve the image's aspect ratio and fit the logo into horizontal space on the About view. .png or .jpg file

g. Custom Font [optional] The Survey123 template allows for the use of a TrueType font family in the customized application. .ttf (TrueType) files supported. Ensure that the font is licensed or has a license that allows it to be distributed with the app. For the Cilantro Surveys app, we are using the Raleway font family available from Google Fonts, which has an Open Font License.

III. Steps to UI Customization Now that I've outlined the assets and information needed to create a custom version of Survey123, the next step is to download the template and get started. I'll go through this step by step and reference the assets and information listed above along the way.

1. Download the template 1. Open AppStudio for ArcGIS . You don't have to log into your ArcGIS organizational account in order to download the template, but it is a best practice. 2. Click "New App" 3. Click the "Enterprise" tab in the New App dialog 4. Select Survey123 (Template), enter the title of the app ("Cilantro Surveys" in this example) and click "Create" 5. The new app template will download and appear in the AppStudio gallery.

2. [Optional] Create the fonts folder and add the font files This step is only required if you are using a custom font family. 1. Right-click the gallery card for the app in AppStudio and select Open in folder. 2. Open the "Controls" folder 3. If the folder doesn't contain a "fonts" folder, create one. 4. Copy all of your .ttf files into that folder. In this example we'll be copying the Raleway fonts to the folder.

3. Update the app's settings and assets Now comes the most significant step where the assets and settings for the app are updated. 1. Make sure the gallery item for the downloaded template is selected and then open Settings for the app. This can be down by right-clicking on the gallery item and clicking Settings from the menu, or using the side menu. 2. Details Tab 1. First update the app's details under the Details tab. 2. Click the thumbnail and replace it with the app thumbnail created for the app (See section II.e) 3. Update the app's summary, description and access use and constraints to reflect the new app. The description will appear in the app's About view. 3. Survey123 Tab General Tab Text color: The text color used in all non-title text in the app. I'll leave this set to the default value of #4c4c4c. Background color: This will set the background color displayed in the gallery and the survey info views. I'll leave this set to the default of #efeeef. Title bar text color: This sets the foreground (text) and icon colors for the top bar in the gallery and survey info views. I'll leave this set to the default of #ffffff. Because the branding and background color for Cilantro Surveys is dark, the white text will contrast well against it. Title bar background color: The background color used in the app's title bars. For Cilantro Surveys I am using the branding color of #543e36 (see section II.b). Font Family: This is where the name of the custom font is entered. For Cilantro Surveys I am using the Raleway font family. Note: The text entered here would be the same text entered for the css font-family property if the font were being used on the web (e.g. font-family: 'Raleway';) Other Properties backgroundTextureImage: This property is no longer used. companyLogo: The company logo that appears on the app's About page (see section II.f). companyUrl: URL opened via the company logo on the About page. formBackgroundColor: The default background color used for forms in the app. startBackgroundColor: The background color of the opening splash screen. For Cilantro Surveys I am using the branding color of #543e36 (see section II.b). startForegroundColor: The foreground color of the opening splash screen. startOverlayImage: The image that appears on the opening splash screen. For Cilantro Surveys I'll set this to our company logo as well (see setion II.f). 4. Resources Tab App Icon I'll set this to the icon created with the assets (see section II.c) Launch Image Overlay image: I'll set this to the launch image created with the assets (see section II.d). Background Image: I won't use this property with the customized app. Background color: I am using the branding color of #543e36 (see section II.b).

4. Fix small bug in code [only for templates based on version 2.7 or less] Survey123 templates based on version 2.7 of the app or less have a small bug in the code that needs to be fixed in order for the branding color to be reflected on the survey view. To fix the bug do the following: 1. Open the app codebase in Qt Creator. This can be done by right-clicking on the app card in AppStudio and selecting "Edit in Qt Creator" or by highlighting the app in the AppStudio gallery and clicking the "Edit" button in the side panel. 2. Open the following file by using the file browser in the left panel of Qt Creator: template > SurveyView.qml 3. Within the style property of the XForm component in SurveyView (approximately line 501), add the following 2 properties below the line: fontFamily:app.fontFamily titleBackgroundColor: app.titleBarBackgroundColor titleTextColor: app.titleBarTextColor 4. You can view the code in the Cilantro Survey's public repo at CilantroSurveys/SurveyView.qml 5. Save the file and close Qt Creator.

5. Upload the app Upload the app to ArcGIS online. This will allow you to register a client id for the app so that it can use OAuth for login authentication, as well as provide access to CloudMake.

6. Register the client id in order to use OAuth In order for users to be able to log in to your app with their ArcGIS Online or Portal credentials, a client id must be registered for the app. If the app is located on ArcGIS Online, registering the client id is an easy process*. 1. Open Settings for the app (see Step 3.1 above). 2. Click the Advanced button on the bottom bar next to Apply. 3. Under ArcGIS Client ID click the "Register" button (You must be logged in to ArcGIS Online). 4. Settings will register the app with ArcGIS and return a client id that will appear in the text field. 5. Once the client id is returned and visible, click "Apply". 6. That's all *Note: If the app needs to authenticate to a Portal for ArcGIS, you will need to follow instructions similar to those outlined in this article the article).

(substitute your app's name for Survey123 in

7. Test and Build app Now the only thing left to do is build the app. Before doing that, most of the changes made in the previous steps can be previewed in AppRun or AppStudio Player. To open the app in AppRun either double-click the app card in the AppStudio gallery or click "Run" in the AppStudio side panel. For more information on AppStudio Player, see: Guided tour—AppStudio for ArcGIS | ArcGIS

Building the app via CloudMake or Local Make is beyond the scope of this blog post. However, please note that in order to build the app for various platforms appropriate developer certificates and provisioning profiles are required. That's all there is for white label branding Survey123. However, if you want to finesse the app's look and feel even further, feel free to jump into the code Comments: 0

522 Views

.

Permalink

International Mine Awareness Day (2.7) Posted by ichivite-esristaff

Apr 3, 2018

On 8 December 2005, the General Assembly declared that 4 April of each year shall be observed as the International Day for Mine Awareness and Assistance in Mine Action . It called for continued efforts by States, with the assistance of the United Nations and relevant organizations, to foster the establishment and development of national mine-action capacities in countries where mines and explosive remnants of war constitute a serious threat to the safety, health and lives of the civilian population, or an impediment to social and economic development at the national and local levels.

The Geneva International Centre for Humanitarian Demining has leveraged Survey123 for ArcGIS over the last year and a half to capture the location of reported explosive devices, record hazardous areas and interview and support victims and survivors. We devote this update to GICHD and to all organizations committed to make a difference for those who suffer the long lasting consequences of war. To learn more about GIHCD and their work with Survey123, watch this video:



Next, lets describe the highlights for this update:

Web Designer Enhancements Starting with this release, you can add signature questions into your surveys, right from Web Designer. Signature questions are supported in both Web Forms as well as the Survey123 field app and present to the end user a simple black-over-white signature pad. Signatures are stored as attachments, like other images. Rules: Rules in Web Designer allow you to define simple conditional statements to control the visibility of questions in your form. Using rules, you can dramatically simplify your forms, ensuring that users are only presented questions relevant to them. To define a rule, you need to first select a question of type Single Choice, Dropdown, Likert or Rating. At that point, the Set Rule option will be enabled so you can define what questions will be shown when a particular choice or rating is selected. Up until this update, rules were only supported in Web Designer for single choice questions.

Autocomplete: You can now enable autocomplete on questions of type dropdown. This is particularly useful when working with long choice lists. Compact choice lists: A new 'horizontal compact' appearance has been added to single and multiple choice questions. Use this appearance if you want the choices to be arranged horizontally, but preserving as much space as possible.

Date questions: Date questions have been enhanced in Web Designer so you can control if the calendar control should let users define a complete date (Year, Month and Day), or simply the year or the year and the month. Bug fixes and other enhancements: ENH-000111156: Add support for pulldata() in geopoints in the Survey123 Web Form BUG-000111357: Clicking the collaborate option for a survey in the Survey123.arcgis.com website returns an error, "Survey does not exists or is inaccessible" when labels are kept empty in the corresponding survey form. BUG-000111377: Trying to publish a form using the Survey123 site containing multiple choices, with a choice containing more than 32 characters, fails to publish the survey and results in the error, "Unable to publish the survey. Length >32" BUG-000111206: hide-input appearance does not work when taking the survey in the web app Multiple issues addressed when using Web Forms in IE11 Web Browser.

Survey123 Field App and Connect Version 2.7 of the Survey123 field app and Connect does not come with major new functionality, but it is loaded with many fixes and enhancements. Lets start with a selection of critical fixes: BUG-000096762: Feature Services published from Survey123 Connect for ArcGIS do not define a "Display Field" in the feature layer rest endpoint. This bug prevented surveys published from Survey123 Connect from working within Collector for ArcGIS Android. It also caused table preview issues in some versions of Portal for ArcGIS. BUG-000108943 Required values for integer, decimal, geopoint, and DateTime questions in a Repeat section can be submitted blank. Also raised by Johan Ekenstedt in GeoNet: Required geopoints in repeats doesn´t work BUG-000110669: This bug caused the form not to center the screen on empty required questions after validation, making it difficult for end users to identify which required questions had been left empty. Also raised in GeoNet: Survey123 2.0 Change Question BUG-000109967: Offline maps not available in the Inbox, Sent and Outbox. Now fixed in this release. Also raised in GeoNet:

How to use TPK on Inbox map?

BUG-000108975: When previewing a survey in Survey123 Connect for ArcGIS, validating the input for the first selection in a cascading select will not function as desired. Fixed! BUG-000110311 In iOS operating system, copying sent data to a new survey and deleting an attachment results in the attachment missing from subsequent copy from sent. Addressed. BUG-000106661 Updating a sent survey that is connected to a feature service from the ArcGIS Server that is federated with Portal (not hosted) will result in the following error: Unable to Complete Operation. Error code 400. Fixed. Fix-Heather Follis: This fix accommodates cases where the Sent box could not display submission error messages. More details at: They stay in outbox with red exclamation and no errors. Fix-John Walls: A fix to address situations where certain surveys would cause Survey123 Connect to crash.More details here: Survey Thanks John for reporting.

Our completed surveys are not sending.

Survey123 Connect Crashing When Opening

Fix-Chris Shuck: With this fix, a survey can include multiple expressions extracting EXIF metadata from images. More details at app

Pulldata function on multiple photos freezes the

Fix-Eric Page: With this fix, the Inbox now properly displays and sorts Inbox records based on submission time, when the Inbox makes use of a query. and Filtering Fix-David Rebot: Great find by David: Default values were not being applied if the autocomplete appearance was in use. Addressed in this release. interfering with Defaulting Date/Time fields Fix-Shane Clark: This one was an oldie that we had to accommodate. Input masks now no longer make your questions required.

Survey123 Inbox Sorting

ISSUE with Autocomplete

body::esri:inputMask should not require input

Shane: your finding was a good one too... And here a list of the most relevant enhancements in the Survey123 field app and Connect: Enhancements to annotate appearance: We introduced requests:

smart sketching in our 2.4 release and many of you are leveraging it today. In this update we incorporate two popular

1. Allow end users to sketch on top of existing images from the photo gallery 2. Allow end users to rotate images before sketching Optionally disable Web Form generation in Connect: A new option has been added in the Publish dialog in Connect so you can disable the Web Form generation. This is handy when you have lists with many thousands of choices in your XLSForm. UTC offset property: ArcGIS Hosted Feature Services store date and time information in UTC. This causes issues in some applications (like ArcMap) that are not UTC-aware, when people work across multiple time-zones. To compensate for this, we have extended the pulldata function so you can store the UTC-Offset of the device from which the data is being submitted as a GIS attribute. The syntax is as follows: pulldata("@property", 'utcoffset'). Calculate select_ones: Last but not least, you can now calculate values in select_one questions. That is, you can trigger a selection on a select_one question from a calculation. There have been multiple threads on this in GeoNet including: Criteria / Calculation Based Select_One Auto-Population , Pre-populate Select One/Select Multiple fields from CSV , Auto-Populate Select One Question Based on a Previous Select One Question and default depending on previous answer Go to the top of a repeat on new record: Did you ever feel like you were stuck at the bottom of a repeat when adding a new record? Did you ever feel like you wanted to be taken back to the top? Well... 2.7 does it now for you! group. , Have a new repeat scroll to top.

Thanks to all of your feedback on this one too:

Have a new repeat scroll to top ,

Adding record in repeat stays at bottom of

If you are a developer building your own version of Survey123, you can also now download the latest code from AppStudio for ArcGIS.

Beyond 2.7 Looking at next steps beyond 2.7, we have already a handful of projects that have made sufficient progress as to be shared in a near-term road map. Our next major release will be 3.0, which we envision shipping around July 2018. If needed, we may squeeze 2.8 and 2.9 as maintenance releases with critical fixes, but 3.0 in July will be the update with the most relevant new features, of which I want to highlight: Custom Form Reports: Our Leveraging Custom Form Report Templates in Survey123 for ArcGIS blog post anticipated this feature, which is currently available to all of you in Beta. We are working hard to move this feature into general release and incorporate into it bulk report capabilities. Support for nested repeats: This feature is available for testing already through our Early Adopter Program

and allow you to author surveys that have repeats within repeats.

Enhanced support for external GNSS receivers: At the moment, you can use external GNSS receivers with Survey123, but only in a limited way. For example, you cannot extract key metadata from the receiver such as VDOP, HDOP, Number of Satellites or the Fix Type... With the 3.0 update our intent is to extend the pulldata() function so you can also extract this important metadata and store it along with the features you capture. We also plan to provide support for RTK corrections. We are working towards having this feature available for testing in our Early Adopter Program around June. Webhook integration: An earlier post Adopter Program.

Sneak Peek: Survey123 and Webhooks (Integromat) described this work in more detail. Available for testing today through the Early

GeoSearch in the Survey123 field app map widget: Check out this video in our Early Adopter Program

for details. Available for testing now.

Support for Web Maps, Vector Tiles and Mobile Map Packages: This is a big deal as it will make maps for geopoint questions much better looking, useful and lightweight. Looking at having this available for testing around June. Pages: While Pages are not officially supported yet, we continue working on improving this feature. Starting with 2.7 you will notice that the page navigation has been vastly improved, although there are multiple areas that still need more work before we can call it 'ready'. If you are into pages, do not hesitate providing your feedback via the Beta forum in our Early Adopter Program . A lot in the plate as you can see for 3.0. Our focus however it is not going to deviate from listening carefully to all your feedback through this GeoNet Group, so keep your questions and suggestions coming! There are many other ideas in our backlog including survey pages, support for polygons and lines, on-premises setup of all components of Survey123 and many other enhancements which remain as high priority in our list, but will see the light after the 3.0 release. 1637 Views

Comments: 12

Permalink



Tags: mobile, survey, signature, geoform, survey123, websurvey

Using App links to Launch Survey123 from Explorer for ArcGIS Posted by mbockenhauer-esristaff

Mar 29, 2018

In this article we will learn how to launch Survey123 from Explorer for ArcGIS and pass attribute information from the Explorer map to the survey. For this example we will use a map of Shenandoah National Park that that will allow hikers to provide trail information for their current location by launching a survey.

Here is a video that shows the scenario:



In this exercise we will use an offline map for Shenandoah National Park. We will create a Survey for Survey123 that will allow map users (park visitors) to submit trail reports. If you are brand new to using ArcGIS Pro, I would recommend working through the Using ArcGIS Pro to make an offline map blog https://community.esri.com/community/gis/applications/arcgis-pro/blog/2018/01/20/use-arcgis-pro-21-to-make-an-offline-map, which walks through each step in creating an offline map.

We will start by creating a Survey. For this step you will need an Esri user account. In a web-browser visit https://survey123.arcgis.com/ and sign in.

Click “Create a New Survey”

For this Survey we will get started using the Web Designer.

Enter name, tag, summary and provide a thumbnail for your survey… then click create.

Use Survey123 to build your survey. For this survey we want hikers to provide trail information, so we will set up the Survey with some common trail issues that we want to know about, as well description, photo, location, and observation time. If you are new to working with Survey123 web designer, check out this video https://survey123.arcgis.com/videos/

Once we have completed the questions for our survey, click the Publish button.

In our example we will be passing some attribute information from the map to our Survey. To make this an easier setup process click Modify schema.

It is good practice to set the name column in the schema, rather than using the defaults. It makes the service easier to use for other purposes.

When finished renaming fields, click Publish to create the survey service. Next click Collaborate, check Everyone (Public) and click Save. Now, anyone hiking the trail with the survey will be able to provide information.

Copy the Survey ID number from the survey link and save it for later.

Now we will work on updating an offline park map to use the survey. Open this Map Package in ArcGIS Pro http://www.arcgis.com/home/item.html?id=c48742ecdc784623ac15fde1e2455a72



In this map we will update the ShenandoahNP_Trail layer pop-ups to allow user to launch the Survey we just created. Right Click on the ShenandoahNP_Trail to Configure Pop-ups and Click the pencil to modify the Text pop-up.

The pop-up is already defined to show the Trail Name and Length of the trail. Add “Report Trail Status” use your mouse to highlight the text and click the hyperlink button.

We will add an AppLink to Launch Survey123 and pass a couple trail feature attributes to the survey. For this step you will need the field names and survey ID for the survey you created. You will use the them to create an app link URL like this one: arcgis-survey123://?itemID=4560a3c533eb41fcb79fa3ec473babc8 &field:TRAILNAME ={TRAIL_NAME}&field:MAINTENANCE ={MAINT_BY}

The ID and fieldname defined in the survey are in bold, the fields in our feature data are in curly brackets. Type the App link in for the URL and click Apply.

*Pro 2.1 and later required.

Next click the back arrow on the Configure Pop-up pane.



Now we will test the pop-up and App link in ArcGIS Pro. To test the link to the survey, if you do not have Survey123 for Windows installed you can get it here https://doc.arcgis.com/en/survey123/download/ Zoom in the map and click on a trail to see the pop-up.

Click on the “Report Trail Status” link. Survey123 opens the Trail Report Survey and the trail name and maintenance attributes are automatically filled out.



*more information about Survey123 URL scheme https://community.esri.com/groups/survey123/blog/2016/07/30/understanding-survey123s-custom-url-scheme With a working pop-up, all we need to do is share our map with Explorer for ArcGIS users. Use the Create Mobile Map Package tool to create an offline map. The Publisher extension allows you to ‘Enable Anonymous Use’, check the box to allow the public to use the map and click run. To enable for Anonymous use your ArcGIS Pro user account will need to be provisioned with the Publisher license.



Use the Share Package tool to share your map.



Maps that are Enabled for Anonymous use and shared with Everybody can be opened by every and any Explorer for ArcGIS user. Explorer users can simply search for the map in the Explorer app to use it. Our intention is to provide an offline map and offline survey that park visitors can use while hiking in the park. The users also need the app Explorer for ArcGIS and Survey123. They need to get all of this while connected to the internet. In a park scenario we might make a website for a user to download the content from, or print out a map or poster, that lets users know that this content is available, and how to make use of it. We can even create QRcodes to make getting the content easy.

Creating QR codes and App links Once you have shared the map, find it on ArcGIS online and view the map details to get the item ID.



Copy the item ID to your clipboard and create the following applink. (more information about Explorer app links can be found here https://github.com/Esri/explorer-integration ) arcgis-explorer://?itemID=6ca5f9cfea0c47b2969ee9750693301f You can use this as a link on your website, and Explorer users browsing your site on their device can simply click the link to download and open the map. Open the map in Explorer

You can also make it easy for people to get your map using a QR Code. Just use the applink to generate a QR Code, add it to your website or print it for poster display.

Of course, users will also need Explore for ArcGIS and Survey123. You can create Links and QRcodes for those too. For IOS Explorer for ArcGIS Appstore link for a webpage.

Explore Appstore QRcode



Survey123 IOS Weblink
" class="download-link" style="margin:.375rem 0">
src="d ata:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAIgAAAAoCAYAAAAlprK8AAAACXBIWXMAAA7

EAAAOxAGVKw4bAAAAB3RJTUUH4gEQFiAX9N0QoQAAAAd0RVh0QXV0aG9yAKmuzEgAAAAMdEVYdERlc2NyaXB0a W9uABMJISMAAAAKdEVYdENvcHlyaWdodACsD8w6AAAADnRFWHRDcmVhdGlvbiB0aW1lADX3DwkAAAAJdEVYdFN vZnR3YXJlAF1w/zoAAAALdEVYdERpc2NsYWltZXIAt8C0jwAAAAh0RVh0V2FybmluZwDAG +aHAAAAB3RFWHRTb3VyY2UA9f +D6wAAAAh0RVh0Q29tbWVudAD2zJa/AAAABnRFWHRUaXRsZQCo7tInAAAJaUlEQVR4nO1cvY7TShT +AggoEDtUexGIOECDQFrzBDuR6DM0W9CseQK8lBSsI0RLjHiAeJ8gyRPYkZAoM9tSkMlSsU1mC4QEQucWe2eun Ti7SZz9uZd80kiOfXLmzPjMzPlLSkQEANjb26MvX75gf38fv3//xhJ/Fi5duoS//voLd +/exa1bt0r2ARHh48eP9PbtW7p//z5dvnyZACzbH9auXLlCDx8+pPfv39OnT5+IiEBEwGAwoNevX5+5gMt2Ptq 1a9fo3bt39PXrVyIiII5jWl1dPXPBlu38tEePHlGSJEREuNDv9/Ht2zcssYTB58+fsb +/DwC48P379zMWZ4nzhp8/f +LHjx8AgAun1akQAq1WC67rFuLjOE5hHtPg5cuXWF1dLcTD8zw4jrMYgXLAOQfn/MT4A6egIIwxxHGMVqsFIUQ hXpxzSCkRhiGklIjjGIyxBUmaxZs3bwrzWLSCMMYyCvG/UJB2u20HMRgMIKUsxE9KCc45XNfF7u4uoiiyzxzHQ a1Wy+ww6Qk09xlj9ppzDsdxsL6+fuTL5JxjfX09c8913dzvGfmOwig/I5PhmQfP89BoNMaeCyHG +jN8ii6gE1UQz/Myg0m/zEUgDEPUajUAhxOSJAkeP36MKIrgeZ7t03VdCCHQ6/XAGIPnefZ5HMeIoghPnz5Fki S5/UgpIYTA1tYW4jgGAMunWq1CSmlfRJIk8H0fnudNVJI8fq7rIo5j +L6Pra2t3LlyXRc3btxAtVq190w/SZLY/nzfRxAEqFarE8c0NT58+HBi7lK73SaDKIoK8+OcU5Ik9rPjOHTorI OiKKIgCAgACSGo1+sRAArDkHzfpyiKqN1ukxCCkiQh13UJABERcc4JACml7P3v37/T6uoqcc5JSmn71FpbGs45 bW9vU7/fJ845OY5DWmtLK6W0vNNjyOPHOSellKXp9/vHjj8IAjvmMAzttVKKGo2Glc3IO0vb2dk5dHPn0qopwR jDYDBAvV63K3aREEKg0+nYvrTWAACtNUqlw2ixOeIcx0EYhvY676hTSuVuyYZv +loIAd/3sbOzg8FgMCbDUZhEo5Sy17PaLmmejDF0u110u108f/48w3dWXJr7mymkz1OlFHZ2dux94HCwL168gO M40FpDKYVOpzPVZI5iZWUFtVoNnHM8ffrU9hFFEYIgQK/XQ6PRQLvdBnC45RujNkkSRFFkn00DKSVc18WLFy8A HL4IYwcREdbW1rC2tmZpAWB7exta69yXPMpPKWX5HQetNVzXBef8yKMjiiJsbm4iDEPcuHFjrnk2KKQgruui1W qNTUQYhmi321BKTbS0tdYIwxD1en3q/oxiPX78GJ1OB1tbW/ZZu92G1hrVahX1ej2jBEZBACAIgszuUa/X7QqL oshev3r1ysrpOA5834fWOqOQAFCpVDKr1HVd +L6PwWAA3/fHVu8kfkopy1MplTsvUkr4vm8VJK0k6WtjA1Wr1UK7B4D5bRDOOS0Cvu +fWUh52U7IBmGModVqzfPVDA4ODopb2UucKOZSEN/3FxKgMoGvJc4v5lKQRXgkOzs7S+X4D2BmBWGMoVwuF +54Fk8iD0IIxHGMOI5PxIWeBY7joNlsot/vg4gwHA7RarVOPAx+GphZQRaVKCviegGHu5jxkIzLeBZwXRe9Xg +e56FUKqHb7eLg4CA37+Q4TuF81KljVi9mUd7LaIRxlsYYIyIiKSVprYmIiDF2Jta +iRaPRopHo5dm3tKR0PPc5vZiFmU3FMlymlWYJIk9qqZZmdMk5WalHY2LGMwzT4wxrK +vT51kc103Vz4TuFxIJnmeOMgikJdrmLaZVSuEIM/ziIio3W6P0QVBYHerdF6IiCiO48yuY2g9z6MoijK0vV5v 4g4lpSQisnmQvPZP+d4YzHPGGDUajbHnzWYzV0YhhJUx3a/neTQcDjM8Go1GoR1kLgWZNOBZ0Ww2Z +7bHC8mKWY +E40fM2ZCh8Mhaa1tcsscS3EcT6Q1ya882nTzfd/2H8dx7tGZVjqlVCbJllZ4KSV5nkee51nFa7VaYzL2+/0MP XCYoDT3OOc2KUg0XzCykIKkJ6UoWq0WOY4zdd9mx0if +WaCzWSNTigRZWwC13XtfSHEkbSMMasko/wnzUccx1PbIOa +1jqj4CZTTfSvvZaWcVQWpdREHvPs1oUiqUVd1DSEEDO5g4Y2LcNxdki3283YBFJKmwUe9cpGabXWlv +kMz0MQ1QqFdTrdRwcHIBzjjiOp/L4jMwml2Rg8k7pMRuMFkq5rotyuYx +v4+1tTVrx5hwRBFbZC4FSWdsi2IwGMxUSGQmtNVqgf75cU +z2QQA1Gq1qSO8RgmmeYkm4XWUIiulEAQBHMdBt9sFYwyNRuNY3qb/vKTaJBlHQwRmzKZwKN1G +5kVc2dzgyDA5ubmvF +3CMNwalohBFZWVnKVyvM8lMtlCCGmUjizqqbxNswLmCYzqrWG7/vo9XpT7YxSyoklhkbGaWNGu7u78H1/Yj/z YG4FMSnp7e3teVlgd3d3ZgUBDrfjIAgyzxzHwebmZq6CrKysjPFKp9nTyIsSm36nnWSjUKaQ6CiY/mu12tiYjI zHJTQNj3K5DCll4SBkBkVLDo2lPCu01jMZpwCssZhXQmes +OFwmGukGnePMUbNZnPMMEzTGu9qEm26tdtt2tzctDKZckciojAMx4xRY3QaXowxUkplZARgvZ48GfOCbcazjO M4M6+u684VRCzkxaQbYyxXSaSUlCRJrkustZ45kmoUIF3zOUmBRj0T8wKOkiFNa/ikaQ3PdEt7GqNIkmTsxYzK kVYe02c6jpGufz1OQSa9B6KjYzTHKUjhkkNTFeV5HoQQtqwvvXWbCnDOOZRSCMNw5konrXWm +isPvu/bssY0lFK2hpQxBinlmIxpWt/3La +88aRpK5WK/f2LqXVNR3jTMNVmo2UOpiLdzBFweIxGUZQZizlq8mQx5Yimyt0YrGkvbC6cZFX7WbejVlwR2j +hnUpV +xL/fSwVZIkjcen69etnLcOJ4agzuwjt/x2XL1/G1atXDz8kSUI3b9488zNv2c5Pe/Dgwb9/IFOpVLCxsYEllg CAUqmEZ8+e4d69ewCAS3fu3CltbGzQxYsX0el0sLe3h1+/fp2xmEucNq5evYq7d +9iY2MDT548we3bt0sAUKLU32Cav6Na/g3mnwfzN5iVSsUqBwD8DVjVshHYbwlqAAAAAElFTkSuQmCC" style="vertical-align:middle; height:40px;">

Survey123 Appstore QRcode



For Android Explorer for ArcGIS is in Beta, see this webpage to join the beta - https://blogs.esri.com/esri/arcgis/2017/06/15/android-beta-of-explorer-for-arcgis-is-now-available/ Survey123 Google Play web link
" class="download-link" style="margin:.375rem 0">
src="https://play.google.com/intl/en_us/badges/images/generic/en_badge_web_generic.png

" style="vertical-align:middle; height:58px;">

Google Play QRcode



A map could printed with all of the QR codes in a location that has internet access, allowing people to get everything they need on their device before going out into the field or offline.

Comments: 1

539 Views

Permalink



Tags: explorer, attributes, integration, survey123, integrate, applink, pass

Using Spike® with Survey123 for ArcGIS Posted by ichivite-esristaff

Mar 6, 2018

In this blog post I will describe how you can integrate Survey123 with Spike. Spike is a laser-based measurement solution by Esri partner ikeGPS. What makes Spike unique is that it allows you to easily measure the dimensions of remote objects, such as areas and lengths, all from a photo. Say, for example, while doing a property inspection you need to calculate the height of a balcony, or the size of a garage door. Rather than using a ladder and measuring tape, you can simply take a photo of the building, and then calculate dimensions by drawing on top of the photo. You can similarly use Spike to calculate the size of road signs, billboards, the height of attachments in an electricity pole etc. Starting with release 2.6.9, you can embed Spike questions within Survey123 and automatically bring all measurements from Spike into your form: Tap on a Spike question, snap a photo, measure on it… and your measurements will get persisted in ArcGIS along with the rest of the survey data. The integration of Survey123 with Spike is exciting news, because it has the potential to boost the productivity of certain data capture workflows tremendously. Let’s now learn about it in more detail.

About Spike® The Spike laser: The most visible aspect of Spike is the laser instrument. It is an eye safe Class-1 laser , designed to measure distances in a range between 2 and 200 meters with an accuracy of 5 centimeters. The laser is designed to be attached to your smartphone or tablet and paired using a Bluetooth connection. Spike units have a retail price of $499 and are sold online and through a network of resellers . The Spike app: Once the laser is paired, the Spike app uses the camera on your smartphone or tablet so you can take a photo of your object of interest. Using the distance to the photographed object captured by the laser, the Spike app can accurately calculate lengths and areas as you draw lines and polygons over the photo. The Spike app is available for iOS and Android operating systems and is certified for use against a wide collection of smartphones and tablets . Getting familiar with Spike: Spike is straight-forward to use, but knowing a handful of tips and good practice in the field is key to get the best out of it. The best reference to take your first steps is the Spike User Manual . Spike can be operated through two main modes: New Photo Measurement: When working in New Photo Measurement mode, you take a single photo, and then derive all measurements from it. While the main purpose of Photo Measurement is to extract lengths and areas from photographed objects, you can also obtain other useful measurements such as the distance to the object and even the location of the photographed object (more on this later). New Point-to-Point: In this mode you can calculate the distance and elevation difference between two objects by taking a separate photo of each object. Since we have currently only integrated the New Photo Measurement mode in Survey123, I will not expand on Point-to-Point mode. We will consider adding support for Pointto-Point mode in the future. New Photo Measurement: The most typical use of Spike is measuring a length or an area from a photo. When used correctly and in ideal conditions, you can expect a measurement with an accuracy of 1%. For example, if you measure the height of an object to be 10 meters, you can expect the accuracy to be around 10 centimeters. Let’s describe next what used correctly and ideal conditions means: Measurements against a flat surface: You should only perform measurements on flat surfaces, such as a wall or a sign. The specific shape you want to measure should be on a rectangular plane. This is because you will need to define the plane in the photo before you can measure anything. Face your target front-on: For the most accurate measurements, you should take your photo while facing your target perpendicularly. That is, you need to be right in front of the plane on which you will do your measurements. If you need to take your photo at an angle, the expected accuracy of the measurements will be reduced progressively as you get further from being perpendicular.

Ideal target range: The ideal working range of the laser is between 6 and 100 meters, although technically you can push the limits and measure objects between 2 and 200 meters away. Center your target: You also want to make sure that the object you want to measure is right in the center of the camera bulls eye, because the laser always calculates distances through the bulls eye. Draw accurately: Once you have taken the photo, you will want to make sure you accurately draw your lines and areas for measurement. The Spike app has a handy magnifying window that will help you with that task. If your photo is taken following all the tips above, but you do not take pride in carefully drawing the exact shapes you want to measure… the measurement will not be as accurate as it could be. So far all of this may sound a little bit intimidating, but once you have the Spike device in your hand things are much simpler. Not just simpler, but also fun. Next you can see Brandon having a good time while ‘spiking’ outside Esri.

From our own experience, the Photo Measurement mode works best with man-made structures: walls, signs, billboards, doors, straight poles, streetlights etc. Measuring the height of trees, rocks etc is much more challenging because you often do not have a good plane to reference your measurements. Like with any tool out there, it takes a bit of practice to fully understand when Spike is the right tool for the job. Spike can greatly boost the productivity of field workers and save valuable time. For hard to reach objects, Spike can also make it possible to perform measurements that could not be done otherwise.

Integrating Survey123 with Spike (Photo Measurements) Starting with Survey123 version 2.6, you can incorporate Spike functionality into your form. This allows you to streamline the use of Spike within your data collection workflows. For example, if you have a survey to help map the presence of graffiti in the city, you will want to capture many things including the location, typology (Tag, Throw-up, Blockbuster…), surface, photo and size. Spike can help you capture the size accurately, so you can estimate the cost of removal. Adding Spike questions into a survey: You can add Spike questions to a survey using Survey123 Connect for ArcGIS. In your XLSForm, add a question of type image, and then set the appearance to either spike-full-measure or spike: Spike-full-measure: This appearance sets the Spike app in New Photo Measurement mode as described in the previous section. When using this appearance, you will be able to get the measured lengths and areas, into your form. Spike: With this appearance, Survey123 will launch the Spike app so you can simply aim at your object of interest and snap a photo of it. The spike appearance is useful when you simply want to get the distance to the photographed object and its estimated location. When using the spike-full-measure and spike appearances, Survey123 will let users easily launch the Spike app from within the form. Once the photo has been taken and measurements added, Spike will return back to Survey123, so all measurements of interest can be extracted and stored in the survey. The measure object with Spike help topic describes step by step how Survey123 and Spike work together. Spike photos will be stored as an attachment automatically. This is a great feature because photos will become a verifiable record persisted with your data. Photos will show how accurately the measurement was made in the field, and if needed, the photo itself could be used in the back-office to make additional measurements.

The use of Spike within Survey123 is only available to logged-in users. Spike questions can be used while online or offline, but you must be logged-in. Extracting Spike measurements with pulldata(): Spike uses EXIF photo headers to store information such as the location from which the photo was taken, the direction, distance and measurements made in the Spike app. In a previous blog we explored how to extract EXIF metadata from an image in Survey123 using the pulldata() function. This same technique can be used to extract Spike metadata. The Spike metadata in the EXIF of the image is split between standard EXIF tags and custom information stored in the ImageDescription tag. The following table describes standard tags populated by Spike: EXIF tag

Description

gpsdestlongitude

The estimated X coordinate of the photographed object

gpsdestlatitude

The estimated Y coordinate of the photographed object

gpsdestcoordinate

The XY coordinate pair of the photographed object

gpstimestamp

The time when the photo was taken

gpsdatestamp

The date when the photo was taken

gpsdestdistance

The distance between the photographed object and your device

imageDescription

A JSON string including measurements captured by the Spike app

This expression will extract the distance in meters between the photographed object and the device: pulldata("@exif", ${spike}, "gpsdestdistance") In order to extract photo-measurements from Spike, your pulldata() function will need to first get the ImageDescription EXIF tag, and then parse the returning JSON string to extract the specific dimensions you are looking for. For example, the following expression assumes the first measurement made in Spike was of type length, and gets its value in meters: pulldata("@json", pulldata("@exif", ${spike }, "ImageDescription"), "Spike.objects[1].dimensions") The next expression assumes the first measurement made was of type area and extracts its value in square meters: pulldata("@json", pulldata("@exif", ${spike_full}, "ImageDescription"), "Spike.objects[1].area")

Spike returns many other properties through the ImageDescription EXIF tag including: the pitch, roll and direction of your device when the photo was taken, the unique identifier of the specific Spike laser unit that captured the distance measurement etc. The Spike section of the Media help topic describes in detail the contents of the JSON object stored in the ImageDescription. Another way to explore the contents of the ImageDescription tag is to simply add a text question to your form and have it populated with the contents of the ImageDescription tag through a calculation. When you do this, it is important that you set the esriFieldLength column of your text question to 1000 characters. The ImageDescription JSON string can be quite big. A great starting point to experiment with all the things you can do with XLSForms and Spike is our Spike sample. I strongly recommend that you have a look at it: 1. Open Survey123 Connect for ArcGIS 2. Click on Create New Survey 3. Search for the Spike survey in the Samples category 4. Publish it and test from your smartphone 5. Look into the XLS file to learn all the techniques used in the sample.

Integrating Survey123 with Spike (Estimate Locations) While the heart of what Spike excels at is helping you measuring dimensions over photos, you can also use Survey123 to roughly estimate the location of remote objects. For example, you can map the location of a building without stepping out of your car, or the location of a streetlight across the street. Before we go into the details of estimating the location of remote objects, I want to emphasize that Spike is not a high accuracy surveying device. It can measure accurately distances to objects, but when estimating the location of remote objects there are several sources of error that will come into play outside of what Spike is designed to do. To define the location of a remote object, Spike relies on the following: The location of your own phone or tablet: This is the first source of error. A typical smartphone is not going to give you a highly accurate location for your phone. Your location accuracy may vary depending on many factors and if your location is off, the estimated location of the remote object will be off too. To correct this problem, you can connect an external GNSS receiver to your own phone or tablet via Bluetooth. If used correctly, external GNSS receivers will improve the source location used by Spike in its calculations. The distance to the remote object: This is going to be very accurate as long as you keep yourself within the working range of Spike (2 to 200 meters) and you aim at the remote object using the bull’s eye in the Spike app. Measuring distances to objects is what Spike is designed to do, and does it very well. The azimuth to the remote object as measured from your own device location: The azimuth is another important source of error. The azimuth is obtained from the compass in your own smartphone or tablet. The compass in your smartphone must be calibrated before use by Spike. It is critical that you follow steps in this compass calibration videotutorial before you estimate remote locations. Even with your compass calibrated, it is normal to get deviations of a few degrees, which will increase the error as the distance to the remote object increases. The gpsdestlongitude and gpsdestlatitude properties will be populated with both the spike and spike-full-measure appearances.If you do not plan to capture any length or area measurements and all you want is the location of the photographed object, then the best is to use the spike appearance. To extract the estimated latitude and longitude of the photographed object, you will use the pulldata() function within a calculation. For example, the following expression will extract the latitude: pulldata("@exif", ${spike}, "gpsdestlatitude") You can store the latitude and longitude as attributes in your survey, and then create an XY Event Layer with them in ArcGIS Pro

or other tools.

While it should be possible for you to calculate a geopoint question with the latitude and longitude values extracted from the Spike photo, there is currently a known limitation in Survey123 preventing the successful calculation when applied. This is in our backlog and we will work towards resolving the problem as soon as possible. As stated before, it is best that you exercise Spike in the field in all its capabilities. To fully understand its potential and limitations you must experience it in the field in real working conditions. 1319 Views

Comments: 15

Permalink



Tags: photo, rangefinder, exif, survey123, disto, laser, spike

Sneak Peek: Survey123 and Webhooks (Integromat) Posted by ichivite-esristaff

Mar 5, 2018

We are happy to announce that Survey123 will introduce support for Webhooks shortly. If you are not familiar with webhooks, think that you will be able to integrate Survey123 workflows with Micosoft 365, Google Sheets, Box, Evernote, GMail, SMS (Simple Message System), Apple Push Notifications, Salesforce and hundreds of cloud services more! What is a Webhook? The concept of a Webhook is simple. A WebHook is an HTTP/s callback: an HTTP/s POST that occurs when something happens; a simple event-notification via HTTP/s POST. The beauty of webhooks is that they are a commonly accepted pattern by many applications out there, so a whole ecosystem of different providers allows you to work with webhooks and automate processes involving things such as Microsoft 365, Evernote, Google Sheets, SalesForce...and now Survey123. What can I do with Webhooks and Survey123? As you will find soon, many different things, but I will give you a simple scenario: Imagine you want to send an email to someone when a high priority incident is reported through a particular Survey123 form. Imagine too, that if the incident is low priority then you want the incident to be logged in a Google Sheets spreadsheet. By configuring a webhook with Survey123, you can trigger a flow that orchestrates Gmail and Google Sheets to do what I just described. The flow could look something like this:

The flow above was built using Integromat. Integromat is a cloud application that helps you visually orchestrate different cloud services. Integromat supports initiating these flows, or scenarios as they call them, with a webhook triggered by Survey123. How can I do this myself? I am slow typing, so I recorded a step by step video so you can get a hang of it. You will be able to do this by using the Early Adopter version of Survey123 .



Do I need to use Integromat? Not necessarily. Integromat is one of many possible solutions for using webhooks and Survey123. Other solutions include Zapier , Microsoft Flow , Tray.io , IFTT etc. You can in fact trigger a webhook that calls your own custom developed web service, an ArcGIS geoprocessing service, an FME service etc... Does Esri plan to have connectors for Zapier, Microsoft Flow etc? Very likely, but we are still working out what is the specific set of connectors we will create. We want to use this Early Adopter Program to figure out which connectors you would like. For now, you can use the generic webhook connector! To what Survey123 event can I associate a webhook? For now, only to the submit operation in a form (Web Form or Survey123 field app). If you have use cases for other triggers, let us know. Are there any restrictions to the use of webhooks using Survey123? Yes: Webhooks will only be triggered if the end-user is logged in into the Survey123 field app or Survey123 Web Form. Survey123 webhooks will not be triggered if the form is shared publicly and the user submitting the form is not logged-in. When is this functionality planned to be made available? We are targeting version 3.0, which will release around July 2018. Our Survey123 Early Adopter Program now lets you experiment with this feature. We are looking for your feedback through the Early Adopter Program! 2474 Views

Comments: 18

Permalink



Tags: soa, integration, survey123, ifttt, zapier, microsoft flow, webhook, integromat, orchestration

Great Wall Release (2.6) Posted by ichivite-esristaff

Jan 23, 2018

This update to Survey123 is in tribute to our Esri Beijing R&D Center, which leads the vision and development of the Survey123 website and Web Forms. Survey123 for ArcGIS is developed by a small (but passionate ) team spreading over Redlands (USA), Melbourne (Australia) and Beijing (China). Coinciding with GIS Day , on November 15 2017, our Beijing friends put together a field exercise at the Mutianyu section of the Great Wall. We headed up, capturing data with Survey123 all the way to Tower 26. It was an unforgettable experience!

The Great Wall of China spans over more than 10,000 (5,000km). It is certainly one of the most impressive architectural feats in history.

Better Web Forms The significance of this release is the introduction of a much improved support for Web Forms. Web Forms let you capture data with the surveys you design in Survey123, from web browsers. Web Forms are handy because they run well on desktop and mobile devices, not requiring the end user to download anything extra in order to capture data. Web Forms can also be easily shared through a simple link in an e-mail, they can be embedded within a web site or shared via social media. We see more and more people authoring smart forms with Survey123 for use within a web browser. Typical use cases include campaigns to gather data from the general public, citizen science projects but also forms for routine work within the enterprise. You can open any survey you have published from a web browser by simply using the links provided in the Collaborate tab of the Survey123 web site.

The above will not take you by surprise, because we have supported Web Forms since June 2016. So what is new? Web Forms authored from Survey123 web designer are faster: If you use the web designer to create your own surveys, you will find a noticeable boost in performance. This counts, because particularly for public surveys people expect an instantaneous response when loading the survey. We have reduced significantly the total size of the surveys. The more lightweight your survey, the less time it takes to download into your web browser. Most importantly, surveys have been improved so the browser can start rendering the questions before the full survey is downloaded. This reduces the perceived startup time significantly. In our own testing, surveys with over 50 questions that used to take 11 seconds to load in the web browser, now only need 2.5 seconds. This performance boost will only take effect with surveys that you publish with version 2.6. That is, starting today... If you already have published your survey and you want to take advantage of the performance improvements in this release, simply go into the web designer and re-publish your survey. If you already have published surveys with web designer and want to take advantage of the performance improvements in this release, simply go into web designer and republish your survey. General release for Web Forms authored from Survey123 Connect: If you follow Survey123 development closely, you will know that until this release we supported surveys from Connect on the web as a Beta feature. As of this release, it is not Beta anymore! A lot of work went into fixing critical issues and improving the user experience so you can author surveys in Connect, and then have people use them from a web browser. While there are still some known limitations, we feel confident that Web Forms now are solid to support the more common advanced features that Survey123 Connect offers. This includes additional question types not currently available in web designer, as well as your own custom logic for user-input validation, conditional statements, repeats, groups etc Not everything that is possible in Survey123 Connect will work in a Web Form, but most will. The following table provides a quick reference to help you identify which XLSForm features are not supported in Survey123 Web Forms. XLSForm features not supported in Survey123 Web Forms Question types

All XLSForm question types supported in Connect are supported except barcode.

Appearances

All appearances supported except weeks...)

Other XLSForm Columns

body::esri:inputMask and bind::saveIncomplete are not supported.

XLSForm expressions

spike and

spike-full-measure supported (more on these appearances in a couple of

pulldata() function is not supported. can't set the background image in questions of type image with the annotate appearance property() function is not supported (although you can use the email and username question types to achieve the same)

Please also note that the look and feel of Web Forms may differ (although no drastically) from the way the survey is rendered in the Survey123 field app. Overall, the experience will be similar, but we have made conscious decisions to optimize data capture in the web versus the native app. Web Forms in this release also come with refinements in the user experience of various question types, particularly questions to capture locations, images/photos and single and multiple choice questions as well as many, many software defects fixed. The release of this new Web Form engine involved a pretty big undertaking so we are really excited about you finally having access to it.

Enhanced Report Print Templates (Beta) As you may already know, Survey123 includes a handy built-in reporting engine that allows you to define the look and feel of reports using templates built with Microsoft Word. Once the template is associated with your survey, you can easily create high quality printable documents using data submitted to Survey123. This work was first introduced through Tega's blog post Leveraging Custom Form Report Templates in Survey123. The report service is at the moment exposed as a Beta feature and we continue evolving it with your feedback. In this release we have simplified and expanded the syntax used in Microsoft Word document templates as follows: Images: Up until 2.6, you could include images in your Microsoft Word template using the keyword ${%image1}, where image1 would be the name of the question in your survey with the image. As of this release, you no longer need to prefix the question name with the percent sign %. That is, ${image1} will do! This makes things easier for all of us. Most importantly, you can also specify the exact size of the image in your document. For example, you can set the width of your image in the final report to 300 pixels by using ${image1 | size:300:0}. You can specify both the width and the height, but if you leave the height set to 0, we will ensure that the aspect ratio is preserved. That is, we will guarantee that the image in your document has the width you specify, and then we will set the height accordingly to preserve the aspect ratio of the original photo. You can also now retrieve metadata from your images and include it as part of your report. Here is the syntax: ${image1 | getValue:"x"} and ${image1 | getValue:"y"} will give you the X,Y coordinates from which the photo was taken. ${image1 | getValue:"date"} and ${image1 | getValue:"time"} will extract the date and time when the photo was taken. ${image1 | getValue:"name"} returns the name of the file. Many thanks to

Peters, Amy and all who voted for

Include photo coordinates on reports from Survey123

Maps: Simplified grammar so you can simply say ${Location} instead of ${%Location}. Many of you have requested the means to define not only the scale and size of the map, but also the Web Map to be used. This now can be achieved through the mapSettings optional parameter as follows: ${Location | mapSettings:webmapID:mapScale}. For example: ${Location | mapSettings:ffb2f300ceeb417e9b384f52b60ce4e4:10000 | size:600:400} will include in your report a map centered at the geometry found in the Location question (this is expected to be a geopoint question), using a Web Map with ID ffb2f300ceeb417e9b384f52b60ce4e4, at a scale of 10000 and with a size of 600 pixels in width and 400 pixels in height. If you do not remember the name of the geopoint question in your survey, you can also use the keyword $shape. For example: ${Location | mapSettings:ffb2f300ceeb417e9b384f52b60ce4e4:10000 | size:600:400} is equivalent to ${shape | mapSettings:ffb2f300ceeb417e9b384f52b60ce4e4:10000 | size:600:400} Multiple choices: With this new release you can decide how to include in your report the information contained in multiple-choice questions. For example, if you use ${multichoice1}, your Word document will include all selected choices in a single-line and separated by commas. If you choose to use ${multichoice1 | appearance:"bullets"}, then your Microsoft Word document will output the user selection as a bulleted list. All the above new grammar is in addition to everything supported so far and described in the Print Individual Responses help topic used before, so if you have already uploaded your own report templates, they will continue to work as usual. We will continue listening to your feedback regarding this beta feature and evolve it accordingly.

. It is also in addition to the old-style grammar you

Survey123 web site The Survey123 website includes some additional fixes and enhancements. I want to highlight a number of them: BUG-000109826 In Individual response window on Survey123 for ArcGIS website, leading zero is dropped for a selected record if the survey form contains values with leading zero in label column. BUG-000109752 When using Survey123 for ArcGIS web app, users are unable to scroll through the 'Thank You' screen if the message after submitting a survey does not fit within the web browser display BUG-000108470 Individual Response fields appear blank for a selected record in the Data tab of the Survey123 for ArcGIS (survey123.arcgis.com) website if the submission contains a leading zero BUG-000107912 Survey results exported to PDF from survey123.arcgis.com show the tags if html was used to style the survey with multiple selections ENH-000104866 Provide URL parameters to apply to fields for web surveys from Survey 123 online BUG-000110685: Date values do not get submitted from Web Forms published from Connect in Safari and IE11 browser BUG-000109871: HTML tags added to choices tab in XLSForm are displayed in Survey123 website

Survey123 Field App and Survey123 Connect for ArcGIS The Survey123 field app and Connect have been updated to version 2.6. You can download the field app from the Apple, Google Play and Amazon app stores. As usual, you can also download the desktop version of the app and Connect from our Downloads Page . This is a minor release including a few fixes and minor enhancements: BUG-000106527 / DE-000002011: Date & Time cannot take selected values. A usability fix for the Date and Time controls. BUG-000103945 / DE-000001638: Android Photo Gallery. You can now browse for photos in Android devices using a nice photo gallery. BUG-000109192: Save survey in Draft option is not working when the survey form is created with repeat_count value. BUG-000107386: Hints cut off all text after a less than symbol '<' in Survey123 for ArcGIS field app. BUG-000105455: Home button on the Inbox (and Drafts) map overview ignores the custom home location. Eliminated conditions that caused the field app to occasionally crash after a new survey download. Clearing the Inbox and Sent folders in one survey will no longer clear Inbox and Sent folders in other surveys downloaded in the device. "time" type calculations not refreshing Improvements to the camera flash on Android devices. Improved zoom capabilities in the barcode scanner. For more details on What is New in this release as well as all previous updates, refer to our What's New Help Topic 2006 Views

Comments: 35

Permalink



.

Tags: survey123

A simple e-mail notification system for Survey123 for ArcGIS v2 Posted by ichivite-esristaff

Jan 22, 2018

Back in November 2016, I published a blog post describing how to automate e-mail notifications against a Survey123 project. The idea was simple: A Python script that would trigger an email every time a new survey is submitted. By scheduling the script to run unattended at certain time intervals, one could easily put together a simple e-mail notification system. I want now to revisit this topic and share a new Python script, which takes care of some limitations of the first version. Specifically, the new script: 1. Works against ArcGIS Enterprise in addition to ArcGIS Online 2. Can be configured to either send one email for every newly added survey, or alternatively send one email for all new records added since the script was last launched. While the Python script can be used as is, I really share it as a starting point from which you can write the exact logic that matches your needs. You may for example tweak the script to: Format the e-mail notification following specific branding guidelines. Extend the notification logic so the recipient of the email varies depending on data submitted. Below are step by step instructions so you can configure this Python script with your own survey.

Preparing your computer to run the Python script Technically, you can host the script in any computer that is able to run Python 3.x, however, you will want to select the host carefully. You will want the script to run regularly and unattended, so you want to pick a computer that will reliably running 24x7 and constantly connected to your network. In addition to Python 3.x, the script requires the 'requests' Python module installed. If your computer already has ArcGIS Pro installed, you already have Python 3.x and the 'requests' module installed. However, ArcGIS Pro is not required to run this script. How to install Python How to install the 'requests

' module



Preparing your feature service The Python script works against your survey's feature service. The script requires that your feature service has Editor Tracking enabled. By default, all feature services created by Survey123 have Editor Tracking enabled, so there is really nothing that you need to do extra. If your survey is configured to work against a service from ArcGIS Server, then you will want to make sure Editor Tracking is enabled, and if not, enable it manually. If you do not enable Editor Tracking, the script will generate an error text file indicating that Editor Tracking needs to be enabled and will stop execution.

Downloading and configuring the Python script Now you can download and configure the script as follows: 1. Download the Detect Changes and Notify Python script v2

and its associated init.json file and save them together within a folder in your computer.

2. Edit and save the init.json file. At the very least, you will need to change the properties highlighted in blue below. { "email":{ "recipients":[" [email protected]"], "from":" [email protected]", "subject":"New features has been added to your service", "text":"Hi Team,\n\nYou are receiving this e-mail because features have been added in:\n", "server":["smtp.acme.com", "", "", ""], "onemailflag":1 }, "service":{ "portalURL":"https://www.arcgis.com ", "fsURL":"https://services2.arcgis.com/fJJEXNgxjn0dpNsi/arcgis/rest/services/service_20dc5e3eab3f4efab8fde88f6027911b/FeatureServer "fsLayerNum":0, "serviceuser":"yourusername", "servicepw":"yourpassword", "fieldstoreport":["*"], "viewerMapLevel":19 }, "filenames":{ "lasteditfile":"lastedit.json" } }

",

recipients: This is the e-mail that will be receiving notifications. You can create an email alias if you want several people to receive the email. from: This is the e-mail of the person/organization that is sending the e-mail. You can also set it to a DoNotReply email address. server: This setting refers to your email server connection properties which are defined as a comma separated list of strings. The first parameter is the host of your email server which can be specified by hostname or IP address. It will look something like smtp.yourCompany.com for example or smtp.gmail.com The second parameter is optional and defines the port where the SMTP server is listening. Common ports are 25 and 587 but it could really be any other port depending on how your mail server is configured. The third and fourth parameters are also optional and are used to set a user and password to access your email server. To properly get the email server connection properties, you will want to contact your IT department and describe what you are trying to achieve as many email servers are configured with strict security policies that will prevent the script from successfully connecting and using your corporate e-mail server. Folks in your IT department should know how to give you the right hostname and port for your email server. Handing over the source code of the Python script may be of help too. If you want to configure this script using your Gmail, You will need to configure your Gmail account with 2-step verification , and then setup a Gmail App password . Once you have done that, use your complete Gmail e-mail address as the user (third parameter) and the App password for the fourth parameter. When using Gmail you do not need to specify a port number, so simply type "" in the second parameter. onemailflag: If you leave this parameter as 1, then an e-mail will be sent summarizing all records added since the Python script executed for the last time. If you switch the value to 0, then the script will trigger one e-mail for every record added. portalURL: You only need to change this setting if working against ArcGIS Enteprise. You will want here the full https location of your portal including the Web Adaptor. fsURL: This is the URL of your survey's feature service, which could be running in ArcGIS Online or ArcGIS Enterprise. fsLayerNum: This is the index of the layer in the feature service that you want to monitor. If you want to check for changes in the main layer of your survey, leave it to 0. If you want to check for changes in the layer of a repeat, change the index accordingly. serviceuser and servicepw: The ArcGIS credentials of a user with access to the feature service. After saving changes to the init.json file, it is time to give the script a quick test: 1. Run the script once so it can capture the current state of your feature service. 2. Submit one record to your feature service and run the script again. If any errors occur during execution, an error text file will be created in the same folder where you saved the Python script.

Scheduling the script The Windows operating system includes a simple utility called Task Scheduler. It is quite easy to setup. Once you have determined when the script will be triggered for the first time, you can repeat its execution at regular intervals. For example, every 5 minutes. Obviously, the computer where you setup the task will need to be running all the time, although you can configure the task to run regardless of who is logged in. The configuration of tasks in the scheduler is pretty much self-explanatory, but here are some specific instructions that can save you some back and forth: 1. General: Check the option to run with highest privileges and set the task to run even if you are not logged-in. 2. Trigger: If you want to quickly test your task, you can simply select your task in the gallery and then hit Run in the Selected Item panel on the right. When configuring the task for real, I suggest you select the startup trigger and that you also configure the task to run indefinitely every five or ten minutes or so. 3. Actions: You will need to be particularly careful with this one. The Program/Script setting needs to point to the Python executable (Python.exe). If using your own copy of Python, refer to the installation directory of Python where you will find Python.exe If using Python from ArcGIS Pro, it will be under the Pro installation directory. For example: "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\python.exe" You also need to indicate the location of your DetectChanges.py Python script as an argument. Do not forget to include the .py extension in the path. If the path to your DetectChanges.py file includes spaces, then you need to enclose the path with quotes. Lastly, set the 'Start in' property so it points to the directory in which you are storing the DetectChanges.py file.



Beyond the basics The technique described in this blog post is a bit rudimentary, but it may do its job reasonably in some simple scenarios. You can manipulate the Python script to properly format the email message to be sent, and also to apply some logic to determine if a n email needs to be sent, and to who. Since you are in 'Python land' already, you can get creative and import the arcpy.mapping module to do all sort of sophisticated things in the script. You can for example take the incoming feature added into your feature service and do a straight (buffer) or network distance (closest facility) search to determine who will be notified.

Differences between the original script and this one There are a handful of differences between the original Python script published in November 2017 and this one. For the most part, they are the same, but here are the key changes: The most important difference is how changes in the feature layer are found. In the November 201 script the script exercises a new API introduced in ArcGIS Online to detect changes. This new API only works in ArcGIS Online (not in Enteprise) and it had to be enabled manually on the survey's feature service. The latest version of the script, described in this post, uses Editor Tracking. Editor Tracking is enabled by default in every feature service created by Survey123 for ArcGIS. Editor Tracking is compatible with ArcGIS Online feature services and also with ArcGIS Server feature services back to 10.1. One email per feature or one per execution: The other key difference is that in our November 201 version, it was not possible to easily configure the script to aggregate all changes in a single email. With this version, you can use the 'onemailflag' parameter in the init file to decide if you want to send one email per added record, or one email per execution of the script. If you are already using the November 201 version of the script and want to switch to this one, I recommend that you copy the Python script and the new init file into a separate folder. The init file is different, so pay attention to the new parameters introduced. 4425 Views

Comments: 35

Permalink



Tags: email, notification, survey123, e-mail

Calculating distances between multiple Geo-Points in a survey with the Haversine Formula Posted by dlengtonesri-southafrica-esridist

Jan 10, 2018



This blog post provides a solution for:

Capturing multiple locations per survey

Calculating straight-line distances between a base location point in the survey and other repeating locations captured Consider the scenario where your survey must assist in the administration of new liquor licence applications and the law stipulates: New liquor premises must be located at least five hundred meters (500m) away from schools, places of worship, recreation facilities, rehabilitation or retreat centers, residential areas and public institutions. For this requirement Survey123 can be a valuable tool and in this blog post I will show you how you can enable this functionality in a Survey123 form: Step 1: Create a new survey with Survey123 Connect Step 2: Create a geopoint field in the main survey which will be used to capture the location of the new licence premises (the base point or new_licence_location field in the survey below) Step 3: Create a repeat section to capture the occurrences of nearby schools, places of worship etc. Each with a premise type and a geopoint (the nearby_location field in the survey below) Your survey design should look similar to this:

Step 4: Now, split both the coordinates sets into their x,y pairs and convert them to radians:

Do the same for the nearby_location geopoint field:

Step 5: Use the X, Y (lat,long) pairs to perform the distance calculation (in meters) with the Haversine formula: acos(sin(${gps_lat_end})*sin(${gps_lat}) + cos(${gps_lat_end})*cos(${gps_lat})*cos(${gps_long}-${gps_long_end}) ) * 6371000 After making some cosmetic enhancements (and adding the 500m stipulation) your survey should look like this:

The user can add multiple locations (Nearby Premises) at will in the repeat section and each will have it's own distance calculation to the base point (New Licence Location).

The Survey123 Excel Design file is attached to this blog. Feel free to use and adapt as you require! 742 Views

Comments: 7

Permalink



Tags: distance, haversine

Survey123 Progress / Increment Bar without AppStudio Posted by dlengtonesri-southafrica-esridist

Jan 9, 2018

A customized but "Out-of-the-Box" Progress / Increment bar for Survey123 For a recent survey that I designed I wanted to give the user visible feedback of a risk factor calculation. Have a look at the video below to see how striking the end result is:

Let's break the Progress / Increment Bar down into it's capabilities:

A color ramp to visualize the score (similar to the score distress bar)



A progress / increment indicator (nnnnnnn )

Expand and contract the bar according to the score How was the end result achieved? Let's look at the three components needed to make this work:

1. Color Ramp The color ramp changes from green to red according to the score entered, which runs from 0 to 10 in this case. We could sit down and pretend to be graphic artists and create a color ramp from scratch, or we can use one of the handy websites which creates beautiful color ramps for us! Let's head to RGB Gradient Generator or any RGB gradient generator of your choosing. Now choose your start color and your end color for your ramp (in my case green to red) and choose the number of steps required (in this case 11, which corresponds with our allowable score values):

Next you need to choose a generated gradient and copy the gradient indexes and corresponding hex values to Notepad++ in order to create a CSV file which will act as a color value lookup which is based on the score calculated:

Now we have a handy way to color the bar according to the score calculated. To retrieve the color for each score, we simply have to use the pulldata() function of Survey123: ${color} = pulldata('ColorLookup', 'hexvalue', 'colorvalue', string(int(${score}))) In order to use this hex color we need to use some html magic:

2. Progress Indicator The progress indicator is actually a string of HTML Unicode characters (UTF-8). Let's go shop for a pair of Unicode characters to use for the progress bar at UTF-8 Geometric Shapes You can play around with the various character options but in essence you need a pair of Unicode characters; one to show up as "filled" and colored in, and one that seems to be "empty": nnnnnnn I found it useful to add the character pair strings to a CSV file since it abstracts the solution:

In the CSV file I simply Copied & Pasted each character 10 times to make two strings that are each 10 characters long. Item 1 in the CSV then represents the filled in section of the progress bar (e.g. 10/10 nnnnnnnnnn) and Item 2 represents the "empty" part of the progress bar (e.g 0/10 We now have two strings of 10 characters each and we can access them in our survey with the pulldata() function: ${barString} = pulldata('CharStringLookup', 'textvalue', 'item', '1') ${emptyString} = pulldata('CharStringLookup', 'textvalue', 'item', '2')

).

3. Expanding and Contracting the Bar Now we can color our progress bar and we can visually differentiate between the "filled" in part and the "empty" part of the progress bar by using our Unicode character pair. All that is left is to cut our strings to size (according to the score e.g. 1/10) and combine and color it according to the color ramp already calculated. Our score in the survey can run from 0 to 10 so the progress bar should mimic that by filling up from 0 to 10. We can achieve this by using the SubStr(,,) function on each of our character strings. When the filled in part expands, the empty part should contract, so there is an inverse relation between their lengths. Using two substring functions we can easily cut our two strings to size: substr(${barString},0,${scorelength}) substr(${emptyString},0,${scoreinvertlength}) Now all we need to do is to set the color of the filled in section to our ramp color and then concatenate the strings together with the concat() function: concat('', substr(${barString},0,${scorelength}), '', substr(${emptyString},0,${scoreinvertlength}), '
', string(${score}), ' / ' ,${scoremax}) The second font color setting colors the empty part of the progress bar in black for a nice contrast in colors.

The source files can be found here: AGOL Resource

Thank you for reading this Blog! As always, feel free to use and adapt as needed! 704 Views

Comments: 2

Permalink

Use Arcade to Improve Survey123 Other Answers in Pop Ups Posted by cconnollyesriuk-esridist

Dec 18, 2017

Survey123 is an incredible app from Esri that makes it really easy to configure data capture surveys. I've previously looked at how to implement a custom Other field and how to make survey results easier to analyse, or symbolise, when a survey includes the Other functionality. These methods use configuration options in the Survey123 Connect for ArcGIS desktop application. Supposing you’ve created your survey using the web designer, or perhaps you are happy with your existing surveys and don’t want to change them? In this blog I explore how to work with results that include the Other functionality, after the survey has been published. If you're not aware, the Other functionality allows users to enter an Other value as an answer to a multiple choice question if the answer they need is not in the list. This has been implemented for the question What is the property type?:

This functionality is awesome, but the Other value that a user inputs is assigned to a new field in the attribute table. This means the answers for one question are spread over two fields:

Arcade can help us with this! Arcade is a cross-platform expression language for ArcGIS and, since June 2017 , we can use Arcade in web map pop ups. So we can manipulate the contents of pop ups and, in this instance, display the correct entry for the question What is the property type? This blog assumes you have published a survey using the Survey123 Web Designer or Connect , with at least one Single Choice (web designer) or select_one (Connect) question with Other enabled. You can do this using the standard method or the alternative method I shared before. Using Arcade with Other 1) Add the Survey123 data to a web map 2) Navigate to the Configure Pop Up pane > under Attribute Expressions click Add 3) Specify a name for the Attribute Expression 4) Now we need to form the expression. In simple terms, if the answer to a question is ‘other’, then ignore it and give us the alternate answer supplied instead. In Arcade, this translates into: IIf($feature.fieldname == "other", $feature.fieldname_other, DomainName($feature,"fieldname")) For the question in this example; ‘What is the property type’ is the field alias and ‘PropertyType’ is the field name so the expression looks like: IIf($feature.PropertyType == "other", $feature.PropertyType_other, DomainName($feature,"PropertyType"))

Click Test to ensure the expression works correctly. When you’re happy, click OK to close the window. Note: Arcade expressions are case sensitive, 'other' might be 'Other' or another phrase depending on your survey question. 5) In the Configure Pop Up pane, choose A list of field attributes for the Displayoption > click Configure Attributes. The Attribute Expression created in the previous step will appear at the bottom of the list. Enable this attribute, reorder and turn off the two fields it is replacing:

Click OK to close the Configure Pop Up pane 6. Click on a feature to see the results!

Tips You can find the field names from the Globals section in the Attribute Expression window If you are referencing a field’s domain in the expression, you need to use the domain code and not the name. You can find this in the Attribute Expression window by clicking on the little pencil beside the field name under Globals. If you created your survey using the Survey123 Web Designer, please note that the field names usually are field_0, field_0_other, field_1 etc. Under Globals, fields that have domains include extra information:



If you use the Code then domain codes will be returned in the pop up, whereas if you use DomainName($feature,”PropertyType”) the domain names will be returned instead and will look better. Attribute Expressions can also be used in Custom Attribute Displays too, have a go! Using Arcade in this way means no changes are made to the information at a database level but how the information is relayed to end users is improved! Note, if you need some help setting up a Survey123 survey, check out the help videos and pages . This post was originally shared on the Esri UK blog: GeoXchange — Esri UK . It's also a valuable source for posts on other ArcGIS topics by other Esri employees, check it out!

895 Views

Comments: 5

Permalink



Tags: arcgis online, survey123

1 2 3 …

Home | Top of page | Help

Previous Next

We use cookies to support your experience on our site. For details on which cookies we use and why, read our Esri cookie disclosure and Privacy Statement This website uses cookies to ensure you get the best experience on our website. For more information on cookies, please read our Privacy Policy.

Manage Cookies Settings

Accept Cookies

Accept & Continue

Decline & Close