|
POST
|
Hi. Thanks for reporting this. This is more likely device specific. What phone are you using? (Operating system and phone model). Thanks.
... View more
10-04-2018
05:41 AM
|
0
|
2
|
1604
|
|
POST
|
Hi, Open your survey in Survey123 Connect for ArcGIS Once you are previewing your survey, go into the Settings tab Select the Map section Choose the coordinate format for the Preview Publish your survey and download into the Survey123 field app to test The available coordinate formats are: DMS: Degrees Minutes Seconds DDM: Degrees Decimal Minutes DD: Decimal Degrees MGRS USNG UTM/UPS More info on things you can do with coordinate formats:https://community.esri.com/groups/survey123/blog/2018/07/08/working-with-usng-and-mgrs-in-survey123-for-arcgis
... View more
10-04-2018
05:37 AM
|
2
|
2
|
3199
|
|
POST
|
Hi, it is not possible for people to use Survey123 forms to look at submitted data, even if your survey is public. Survey forms are meant to help people submit data, but through a Survey123 form you cannot query or look at someone elses submitted data. The only exception is if the survey owner enables the Inbox functionality AND the end-user is using the Survey123 field app. I am not sure if that would be your case. Typically, the Inbox is only configured when you want users of the Survey123 app to look at existing data (and change it). Inbox functionality is not available in the Survey123 web app While a survey form cannot be used to look at data submitted, a malicious hacker may be able to sneak into your data using the REST API in ArcGIS, if your survey feature layers are not configured to prevent that. There is a more detailed discussion on security for public surveys in the https://community.esri.com/groups/survey123/blog/2016/11/10/getting-started-with-public-surveys post.
... View more
09-27-2018
10:08 AM
|
1
|
2
|
4517
|
|
BLOG
|
Hi Angelia. When using Web Designer to create your surveys, make sure you use the Modify Schema option in the Publish dialog. You will be able to define the name of the columns and also the choice values persisted. Note that Modify Schema options need to be setup right before you publish the survey. Try the following: In the Survey123 website, take the survey you created with Web Designer and use the Save As option to create a copy of it. Open the new survey in Web Designer and hit Publish. In the Publish Dialog you will see a Modify Schema option. Click on it and alter the field names and choice values accordingly. Publish the new survey Submit data Download in Excel format (you will no longer see choice_0, choice_1...)
... View more
09-25-2018
11:48 AM
|
1
|
0
|
11100
|
|
POST
|
Hi, I have not personally tried this myself, but here is a suggestion. First, create a locator using What3Words. Details here: Esri & what3words | what3words Then, follow instructions in https://community.esri.com/groups/survey123/blog/2018/07/06/understanding-reverse-geocoding-in-survey123-30 to call your own What3Words locator. Two warnings: 1) Reverse geocoding is only supported at the moment in the Survey123 field app. The Survey123 web app does not support it yet. 2) The pulldata operation against your What3Words locator will only work when you are connected (online) Calling Jayson Ward since I know he has been playing with this and I believe he even got it to work in the past.
... View more
09-22-2018
12:58 PM
|
0
|
1
|
1760
|
|
POST
|
Hi Eric, you initial research is correct. In a brand new survey, include a select_one question in your survey and publish it.This will create a new field of type text for your select_one question and a geodatabase domain will be assigned to it with the values in your choice list. At this point, if you open the feature layer of your survey in a web map, you will see the dropdown. To hide the select_one question from your survey, while preserving the field with its geodatabase doman, change the type of question in your XLSForm from select_one to hidden, or simply remove the question from your XLSForm. Then publish your survey again. It does not matter, if change the type to hidden or remove the question from the XLSForm, your form will not show the question and your field will be preserved (in both cases). If using a web browser to render your form, refresh the survey page. If using the Survey123 app, download the survey again to see the select_one question go in the survey. The steps described above work well in ArcGIS Online and ArcGIS Enterprise 10.4 and newer.
... View more
09-22-2018
12:51 PM
|
3
|
3
|
3850
|
|
POST
|
Please email me the form. I cannot reproduce the problem. I used a modified version of the the Nested Repeat sample to test. There could be a combination of things that produce the problem you are seeing.
... View more
09-20-2018
03:23 PM
|
0
|
0
|
1336
|
|
POST
|
Hola. Para crear nuevos surveys en Survey123, necesitas una cuenta con permisos para publicar nuevos Hosted Feature Layers. Tengo la sospecha de que probablemente estes intentando utilizar un tipo de cuenta gratuito, el cual no es compatible con la creacion de Hosted Feature Layers. Detalles aqui: FAQ: Can a user with a public account publish hosted feature services to ArcGIS Online? Si tu cuenta no es gratuita, entonces simplemente tendras que asignar un Nivel 2 (Level 2) a tu cuenta y darle permissions para la publicacion de Hosted Feature Layers.
... View more
09-18-2018
09:38 AM
|
0
|
0
|
1222
|
|
POST
|
Hi. The behavior you describe is expected. Having two separate named users making changes to the same survey is not supported. This technical limitation is rooted in how items are managed in ArcGIS. When you first copied the project, the survey folder carried over the iteminfo file which indicates who is the owner of the survey. Once signed-in Connect will hide all surveys you do not own to prevent you from overwriting surveys from others. After removing the iteminfo file, you temporarily tricked Connect, but when Connect attempts to make updates on the Form and Feature service items it fails, because ArcGIS does not allow edits in these items unless you own them. There is really no way, to my knowledge, for two different accounts to effectively collaborate with updates to the same survey.
... View more
09-18-2018
09:09 AM
|
2
|
1
|
1177
|
|
POST
|
Hi. Not directly. Survey123 works against Feature Services. Feature Services do not work against File Geodatabases. Surveys are configured against a single layer within a feature service and can work with that layer and related tables and layers. Having said this, you can schedule ETL processes (with FME or simply with some Python code) to get Survey123 data out into FGDBs.
... View more
09-15-2018
12:34 AM
|
1
|
0
|
731
|
|
BLOG
|
Whether the natural disaster is flooding, fire, earthquake, landslide, hurricane or tornado, there will be people in need and infrastructure to repair. A key question to be answered before any serious recovery efforts start is the magnitude and impact of the event; quantifying the damage. In times like these, collaboration, coordination and well-established procedures are critical. The US Federal Emergency Management Agency (FEMA) Damage Assessment Operations Manual defines Standard Operating Procedures for assessing damage and outlines information considered when evaluating requests for a Major Disaster Declaration. This 60-page manual is intended for emergency management practitioners as well as private sector and non-governmental stakeholders who have a role in assessing damage or requesting disaster assistance. FEMA has condensed the inputs that it requires by creating Preliminary Damage Assessment templates in Survey123. These templates reflect the necessary assessment details contained in the manual and are designed to quickly operationalize this information. The purpose of this blog post is to introduce these FEMA Preliminary Damage Assessment templates (“FEMA Templates”) and describe how they can be configured and optimized using Survey123 to support damage assessment efforts. A First Look at the FEMA Damage Assessment Templates The main driver for the FEMA Templates included in Survey123 is to provide State, Local and Tribal Governments with a straight-forward and efficient tool for capturing the information FEMA is looking for when evaluating requests for a Major Disaster Declaration (Robert T. Stafford Disaster Relief and Emergency Assistance Act declaration). Two templates are provided, each matching the information required by FEMA to evaluate requests for the Public Assistance (PA) and Individual Assistance (AI) FEMA Recovery Programs: FEMA Public Assistance (PA) Program: Assists with the restoration of equipment, buildings and other infrastructure damaged by the disaster. It also provides aid for the removal of debris and emergency protective measures. FEMA Individual Assistance (IA) Program: Provides assistance to support the recovery of disaster survivors who have uninsured or under-insured necessary expenses and serious needs.This may include assistance for temporary housing and housing repairs, replacement of essential personal property, etc. The templates are designed to support the delivery of PA and IA Preliminary Damage Assessment forms via both the Survey123 web and mobile apps. The Survey123 web app is ideal to support damage assessment self-reporting methods. Self-reporting is primarily conducted at the local or county level to develop initial damage information, which is later reviewed and validated. Typically, the Survey123 forms are shared publicly with affected communities via local web pages, social media, etc. Purely for demonstration purposes, you can preview unmodified examples of the PA and IA Survey123 forms from your browser through the following links: The same forms can also be used from the Survey123 field app. The Survey123 field app is better suited for field-level damage assessment methods such as Door to Door and Windshield Damage Assessments. IA and PA forms can be downloaded into the Survey123 field app for use in desktop computers, laptops, and mobile devices. Once downloaded, the forms can be used by the damage assessment teams even while disconnected from the network. To preview unmodified examples of the PA and IA forms in the Survey123 field app, you will need to first install the Survey123 app in your device. You can download it from the Google Play and iTunes Apple stores. You can also download desktop versions of the Survey123 app for Windows, Mac and Ubuntu Linux. The PA and IA PDA demonstration forms above have been published using unmodified FEMA templates included with Survey123. In practice, the templates would rarely be used without modification. I will use the rest of this blog post to describe how you can publish, configure, and optimize the templates for your own use. There are three main reasons why you will want to publish the templates into your own organization: You will want data captured with the PDA Forms to be securely stored in your own ArcGIS organization, so you can validate, triage, summarize and ultimately share damage assessment information with FEMA for evaluation. You will want to configure and optimize the FEMA templates for the particularities of specific disaster situations, geography, and the damage assessment methods and teams employed. You will want to tightly control who has access to submit damage assessment data to your organization. Publishing the IA and PA PDA Surveys Into Your Own ArcGIS Organization The FEMA PA and IA PDA survey templates are included out-of-the-box with Survey123 Connect and can be published to your own ArcGIS or ArcGIS Enterprise organization easily. Survey123 Connect is a desktop tool for designing and publishing advanced smart forms into ArcGIS. It is available for Windows, Mac and Ubuntu Linux and it is available through the Survey123 Download page. Here are basic steps to get the PDA templates published with Survey123 Connect: Open Survey123 Connect and login with an ArcGIS account with Publisher permissions. Click on New Survey Select the Community category and search for the FEMA PDA template you want to publish Set the Title of your form and click Create Survey At this point, Survey123 Connect will launch your default spreadsheet editor (typically Microsoft Office) to display the FEMA PDA template in XLSForm format. Survey123 Connect will also preview the contents of the XLSForm. To publish the template unmodified, close Microsoft Excel and click the Publish button on the left vertical bar of Survey123 Connect. Once your PDA form has been published, you can download the survey into the Survey123 field app or open it with a web browser to submit data. All damage assessments submitted will be securely hosted in your own ArcGIS organization in a Hosted Feature Layer. To preview submitted data, go into survey123.arcgis.com and login with your ArcGIS account. Your data and reports will be available under the Overview, Data and Analyze tabs. Configuring and Optimizing Ad-hoc PDA Surveys A key factor for success when deploying the PA and IA PDA survey templates provided by FEMA is to properly configure them to support the particularities of the event, the damage assessment method employed, and the target audience for the surveys. Typically the templates will be used as starting points to configure ad-hoc PDA surveys to serve the needs of a single event. In fact, the templates may be used to publish not just one, but several PDA surveys for a single event. For example, a PDA survey may be configured to support initial damage reports by the public, and a second one to support door to door damage assessments by skilled teams. You may also want to configure different PDA surveys to split damage assessments by geographic area, etc. The purpose of configuring ad-hoc PDA surveys is to optimize the damage assessments efforts in the field as much as possible, and guarantee the highest quality data. Configuring and optimizing the FEMA templates requires knowledge of the XLSForm standard specification. To learn more about using XLSForm with Survey123 Connect refer to the following materials: 3-minute XLSForm YouTube video-tutorials XLSForm essentials Survey123 documentation Here are some common techniques that you may want to employ to tailor your own FEMA PDA templates: Hiding questions and setting defaults: It can be very frustrating for field personnel to repeatedly complete sections of the form with information that is common to all the damage assessments. A good example is the Incident ID Number or the Incident Begin Date. Since you will be publishing the PDA surveys specifically for a particular event, both the Incident ID and Begin Date will be known for all Damage Assessments. For local events, location information such as the State and even the County will never vary and will be known in advance. So, why should field personnel need to worry about these recurring details? With Survey123, you can configure forms to hide these questions from the end-user and still submit the correct/complete data by setting up default values before you publish the survey. Use the hidden appearance to hide a question and set its value though the default column. Reducing choices in lists: The PDA forms include a number of lists to facilitate data entry. This includes lists such as US states and territories, US counties, event types (drought, earthquake, tornado, etc.) and many others. You can configure your PDA surveys to only show choices that make sense for your effort. For example, in assessing damage caused by flooding around the mouth of the Columbia River, you may want to limit choices in the States list to Oregon and Washington; in the Counties list to Pacific (for Washington) and Clatsop (for Oregon). From the Event Types list, you will want to remove choices such as drought, tropical storm, tropical depression and any others that do not apply to the area. You can manipulate lists using the choices worksheet of your XLSForm. Removal of questions: The FEMA provided PDA templates are exhaustive and in certain sections include detailed information that can only be completed accurately by trained staff. You may want to remove certain questions, particularly when you choose to provide access to IA PDA surveys for citizens and businesses to self-assess damage to their own property. Non-trained citizens may not know the difference between the different levels of damage to a housing unit (minor, major, destroyed…) for example. In these cases, you may want to simplify the form as much as possible and ensure only critical information is included, such as the location of the damage, photos, insurance information, type of building, etc. Questions can be removed from the XLSForm FEMA template before publishing. Cosmetic changes: The look and feel of the survey, including the color of the header, description, thumbnail, title, and other aspects can be adjusted to meet the branding guidelines of your own organization. Offline maps: Once a Survey123 form is downloaded into the Survey123 app, it can be used even if disconnected from the network. This is critical in situations where communications are interrupted due to the event itself, or when working in very remote areas that lack network signals. Now, the map included to help validate the location of a damage assessment needs to be configured to operate offline in the specific area where the damage assessments will be performed. Just for clarity, even if the map is not configured for offline use, the PDA Form will be functional. That is, even without an offline map, field teams will be able to capture the location of damage assessments by leveraging the built-in GNSS receiver in their mobile device, or an external one. Configuring an offline map provides field teams with a visual clue to validate that the location provided by their device is accurate. The map is also useful to define the location of the damage when the field team can’t physically get close to it. For example, when describing damage across a river or road or within private property. Collaboration through the Inbox: This is more of a configuration of the survey rather than an adjustment to the template, but it is a consideration worth highlighting. By enabling the Survey123 Inbox before publishing your survey, you will allow field teams to see each other’s work. That is, field teams will be able to request to see damage assessments submitted by others from the Survey123 app. This is really useful to avoid work overlaps, but also to help teams pickup on each other’s work. For example, one team may start a damage assessment and a second team may review and finish it. Securing Access to Your PDA Surveys Once your PDA surveys have been tailored to your needs and published into ArcGIS, it is important to control who is granted access. This is all easily done through the Survey123 website. Survey123 for ArcGIS supports the use of private and public forms. Private forms leverage the ArcGIS security model so your PDA survey can be privately shared with one or more groups defined in your ArcGIS organization. Access to private groups require end users to log into Survey123 before damage assessments can be submitted. When working with private surveys, all damage assessments automatically carry information about the person that originally submitted the data and the last person that changed the data. This is known as Editor Tracking and is a critical component to clearly understand who is doing what. A not so widely known feature of Survey123 is that it supports social logins. Through social logins, personnel performing damage assessments can be given a choice to use their Facebook or Gmail credentials to authenticate against ArcGIS. This is of particular importance when working with groups of volunteers, who may not remember new ArcGIS credentials assigned to them. See the Sharing your survey with members of your organization video tutorial for more details. Public forms allow any person, even without an ArcGIS account, to submit data using Survey123. This is of particular importance to support individual assessments. While public forms are supported by the Survey123 field app, the most common use of public forms is through the Survey123 web app. Links to your survey forms can be posted in social media, websites, and shared with local media. A discussion around public forms with Survey123 is available through the Getting Started with Public Surveys GeoNet blog post. You can make your surveys public and keep all your data private. To learn more about how to properly secure your data in public surveys, check https://community.esri.com/groups/survey123/blog/2020/05/11/securing-data-in-public-surveys-survey123-connect Visualizing, Analyzing and Reporting Submitted Damage Assessments The Survey123 website includes built-in visualization and reporting capabilities, which can be leveraged out of the box against all submitted damage assessments. For example: Survey overview: Describes how many damage assessments have been submitted, when, and by whom. Data: Allows you to visualize all damage assessments, as they come in, with both a map and a table view. You can also filter and look into the details of specific assessments as well as download and even print damage assessment reports following your own custom designed report templates. Analyze: Aggregates all information submitted providing a variety of maps and charts to choose from. For a quick overview of capabilities available through the Survey123 website, please refer to this video-tutorial. If you want to create hard-copy reports from your data, you can also use the Survey123 report service.In the example below, a report in PDF format has been created showing a list of addresses (obscured in the screenshot with a gray rectangle) and the categorization of damage, insurance and other information in the grid. To learn more about how to create your own report templates, check: https://community.esri.com/groups/survey123/blog/2019/07/23/understanding-survey123-feature-reports https://community.esri.com/groups/survey123/blog/2020/08/26/survey123-tricks-of-the-trade-summary-sections-in-reports
... View more
09-11-2018
03:43 PM
|
4
|
7
|
30999
|
|
BLOG
|
Hi Michael. The team has looked at this (Windows 10 and iOS with Swedish locale) and we cannot reproduce the problem. We will need more data from you to understand what is the culprit. Please send us your contact info to survey123 at esri.com so we can follow up with you. Thanks.
... View more
08-31-2018
11:38 AM
|
0
|
0
|
1065
|
|
BLOG
|
Thanks for reporting this. We are looking at reproducing this with Swedish version of IOS 11.4.1 and Windows 10.
... View more
08-31-2018
09:41 AM
|
0
|
0
|
1065
|
|
BLOG
|
We just released a minor update to Survey123 including a few high priority fixes. Here are the highlights: Survey123 Website Submit photos in public surveys where query capabilities are disabled: This is quite a critical fix for all of you working with public surveys involving sensitive data. Starting with this update, you can protect data from your public surveys by disabling queries in your survey feature layer and allow anonymous users to submit data and photos. We announced this issue as resolved for the Survey123 field app in a previous update and now this update to the Survey123 web app completes the fix so you can submit from either the Survey123 web or native apps. For more details on working with Public Surveys and disabling queries to protect your data, refer to https://community.esri.com/groups/survey123/blog/2016/11/10/getting-started-with-public-surveys The fix described above will take effect on all newly published surveys. If you already have a survey published and you are running into this issue, then you will need to republish the survey (from Connect or Web Designer as appropriate). Republishing your survey will not cause the loss of any previously captured data. In the event that any data needs to be deleted during the publishing process, then you will be warned in advance. For details on situations where republishing a survey may cause data loss refer to the Publish your survey—Survey123 for ArcGIS | ArcGIS help topic. BUG-000114225 Report generated from the Survey123 for ArcGIS website shows incorrect time. Also discussed at date/time error on report beta .This now has been fixed. Survey123 Field App (Build 3.0.149) The Survey123 Field App has been updated across all supported platforms. You can download it into your mobile device from the Google Play, Amazon and Apple app stores. Missing data in the first record of a repeat group when the survey is open from the Inbox, Draft, Sent or Outbox folders or the repeat_count XLSForm column is used: This issue has been described through BUG-000115742, BUG-000115754 as well as GeoNet threads including problem when using a repeat count limit, in survey123 mobile app only , Data Lost When Saved as Draft and Can you edit a repeat of an already submitted record? Thanks to all who helped us narrow down the issue and/or validated the fix through the Survey123 Early Adopter Program. Fixes to autocomplete appearance: The autocomplete appearance is used to provide auto-suggest (or auto-complete) capabilities to lists in Survey123. This update includes a handful of important fixes to problems you reported. For example, autocomplete now supports the use of default values, html formatting for choice labels in the list (see details athtml formating select one list) and also shows previously entered data when working with surveys open from the Inbox (referenced by Stefano Mauri at Populate select_one question with a value from asset). For completeness on the status of the autocomplete appearance, you should also know that there is still some work pending regarding calculations and autocomplete. Specifically, calculations will not trigger automatically when your survey record is open from the Inbox, Sent or Draft folders, if you choose to apply the autocomplete appearance to your select_one question (this fix is targeted for our 3.1 release in October 2018). Added error explanation when attempting to submit to a feature service that doesn't allow users to add features: This caused a headache to Carl Holt and we do not want that to happen! See the Send Error Geonet thread for details. Fixed override issues on geopoint questions: This issue is described in detail at Survey123 calculating geopoint defaults back to GPS In short, with this release, the location from your device will no longer override the value of a geopoint question if an expression is added to the XLSForm calculation column. This ensures that the geopoint value will always be set from your calculation. Strike-through fix on labels of choices: As described by Braden Burkholder, the labels of choices in dropdown lists were stroked-through in some specific conditions (select_one with minimal appearance within a repeat, with a relevant statement applied and set as required). The issue, which is described at Strikethrough on Repeat Records has been addressed in this update. Thanks Branden for finding the problem and helping us validate the fix too through the Early Adopter Program! Other Notes Survey123 Connect (Build 3.0.142) has also been update. This release of Survey123 Connect includes very minor fixes. We have not made available the source code of this update with AppStudio for ArcGIS. This update is built using AppStudio for ArcGIS version 3.1, which is still not publicly available. We will get the source code in AppStudio up to date once 3.1 is released in September 2018. A What is New historic archive is available at What's new in Survey123—Survey123 for ArcGIS | ArcGIS Our next planned release is 3.1, which is targeted for October 2018. If you would like to learn more about what is coming with the release and want to test your production surveys with it, I encourage you to sign up to our Survey123 Early Adopter Program. Key features planned for 3.1 include: Keep attention to and provide fixes to critical software defects that may get on your way. Add support for working with external GNSS receivers in the Survey123 field app, so you can not only get more accurate location data, but also be able to store all GNSS metadata from the device (FixType, VDOP, HDOP, Num of Satellites, FixTime, Horizontal Accuracy etc) Add support for Question Piping in both the Survey123 field and web apps, so you can embed within the label of a question a response to a previous question in your form.
... View more
08-30-2018
04:00 PM
|
6
|
4
|
4630
|
|
BLOG
|
Hi Rene Aubut Unfortunately not. If you want to translate Other then follow these steps: 1- Do not use 'or other' in the Type column. Simply use select_one yourlist 2- In the choices worksheet, add a 'other' choice to yourlist and use the language columns to translate 3- In the Survey worksheet add a new 'other' question and use a relevant expression to show it only when appropriate. For example: selected(${mylistquestion},'other'). Use the language columns to translate teh question as well. The 'or other' trick is only a shortcut for English.
... View more
08-27-2018
02:07 PM
|
0
|
0
|
21744
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-03-2021 09:03 AM | |
| 1 | 04-01-2022 12:48 PM | |
| 1 | 03-22-2022 08:44 AM | |
| 1 | 08-26-2021 02:43 PM | |
| 1 | 10-30-2019 10:15 PM |
| Online Status |
Offline
|
| Date Last Visited |
07-10-2026
08:41 AM
|