BLOG
|
The July 2022 update to ArcGIS Survey123 is now available. This release includes focused fixes and a handful of useful new features in the Survey123 web designer. Read on to learn what's new! Snapping in the Survey123 web app The web app now supports snapping in Map questions. With snapping enabled, the cursor will snap to all point, line, and polygon features that are visible in the web map. If you're drawing a line or polygon feature, you can also snap to the feature you’re currently drawing. The line and polygon drawing tools have also been enhanced to provide guides for constructing parallel and perpendicular line segments. Survey123 web designer improvements Question types on the Add panel are now grouped into categories, making it even easier to build a smart form on the web: The calculation builder in the web designer allows you to calculate values from other questions and properties in a form. For numeric calculations, you can now set the desired number of decimal places: Survey123 Connect enhancements Navigation in the New Survey dialog in Survey123 Connect has been improved to make the browsing of templates and samples smoother. In addition, you can now click the Information button to view the item details page for a sample or template, where you can view the item's full description, summary, and so on. We've also added a new RIPA Form Template to the community samples in Survey123 Connect. This XLSForm template was designed by Esri's Law Enforcement Solutions team. The Racial and Identity Profiling Act (RIPA) mandates that California law enforcement agencies collect and report officer-perceived identity information including race, ethnicity, gender, sexual orientation, and nationality of subjects of police stops. RIPA is used as a tool to monitor and ensure accountability and transparency among the 500+ police agencies in California. Check out the Racial and Identity Profiling Act: Data Collection with Survey123 video to learn more. We're also working on a formal process for you to submit your own survey designs for inclusion in the Survey123 Community gallery. Stay tuned to the Survey123 blog and social media channels for details! Improvements to Survey123 reports A couple of enhancements to reports in the Survey123 website should make managing report tasks easier and more efficient. On the Report panel on the Data page, a report task can be cancelled or removed; and there's also a new option to handle conflicts with existing report names. Plus, for those of you that like to automate your report tasks, the two new options above have also been added to the Survey123 Report API. For more information on these new parameters, see the Report API Reference. Image enhancements and fixes A number of minor improvements have been made for image questions in the Survey123 field app: The image preview window has been improved so you can now pan and zoom intuitively on Windows, iOS, and Android. We've fixed a bug on iOS where enabling rotation lock caused landscape photos to be saved as portrait. We've also fixed a bug where the EXIF orientation value was always stored as 1, regardless of the orientation of the camera when taking the photo. New calculation mode in XLSForm The calculationMode parameter is used in the bind::esri:parameters column to control when calculations are triggered in the Survey123 field app. In addition to the existing auto, always, and manual modes, a new whenEmpty mode can now be used to trigger a calculation only when a non-empty value is returned. This is useful for controlling calculations for read-only questions when loading existing records from the Inbox. Learn more about the calculationMode parameter here. Reordered options when closing a survey Based on user feedback, the options on the Close Survey pop-up in the Survey123 field app have been reordered to make it less likely that users will accidently close and lose survey responses. This change may initially catch out seasoned users, until they get comfortable with it. You may want to advise users of this change to ensure their data is saved as expected. Fixes and enhancements Survey123 Connect BUG-000144210 The scroll bar returns to the top after releasing the mouse-click under when browsing the 'Community' style XLSForm. BUG-000149513 Domain Names loaded from feature services are not sanitized for XLSForm rules. Survey123 field app DE-000005585 DE-000005449 BUG-000148858 The custom URL scheme does not open the form for the selected feature if the previous form is closed by clicking 'Close and lose changes'. BUG-000148047 Enabling rotation lock on iOS causes landscape photos to be saved as portrait. Survey123 website and web app BUG-000149232 Surveys created in the ArcGIS Survey123 website using non-required drop-down questions display 'Choice #' in the survey data when a null response is submitted and, when designing the survey, a default response is selected prior to filling in the response options. BUG-000150648 ArcGIS Survey123 geotrace or geoshape question intermittently does not load basemap when opening survey in a web browser. BUG-000148769 When editing a record within the ArcGIS Survey123 web form, the start time is removed from the record either from the table or the form view. Editing within the field app does not produce the same result. BUG-000144214 Setting an input mask in ArcGIS Survey123 Connect give error "hubErrCheck.inputFormatInvalid". BUG-000149623 When the same name is used for more than one report, the report item displays with the same name in the ArcGIS Online content page while the actual report has the current timestamp, in the YYYYMMDDHHMMSS format, appended to the report's name. BUG-000136143 When creating ArcGIS Survey123 reports using the Microsoft Word template, the following error message is returned, "word found unreadable content", when an annotated photo is added to the report template. ENH-000140382 Include an option in the Survey123 Report user interface to cancel an ongoing feature report export job. BUG-000149913 In ArcGIS Survey123 Connect version 3.14, when calculating from a feature layer for the relevant table, information is written to the first record, but not to another record after the first record. What's coming next Join our Survey123 Early Adopter Community to read about and test upcoming beta features. Some exciting features we're making progress with and would love to get your feedback on are as follows: CAPTCHA for web surveys: Originally planned for release in July 2022, we will likely postpone general availability until September, but you can start testing this today. Spatial calculations: Currently supported through custom JS functions, we are going to make spatial calculations available through plain XLSForm and even in the Survey123 web designer. Also available for testing now. Targeting the October update. Location sharing: Currently supported in QuickCapture and Field Maps, location sharing is also coming to Survey123! Late 2022 or early 2023. Smart assistants for the field and web apps: Machine learning for image classification and object detection. Head on over to EAC for more information.
... View more
07-28-2022
09:03 PM
|
5
|
1
|
1980
|
BLOG
|
Hi @ThomasHamill thanks for your comment. As it turns out, the Survey123 team is currently formalising a process that will allow anyone to submit one of their own surveys to be reviewed and then made publicly available in the Community samples section in Survey123 Connect. We plan to publish a blog post with further details on this process in the coming weeks, so please keep an eye on the blog. Best, Jim
... View more
06-06-2022
09:07 PM
|
1
|
0
|
3525
|
POST
|
Hi @PeterKnoop Thanks for reporting this issue. It appears to be the same as a previously reported bug concerning the behaviour of rank questions with choice filters in the Survey123 web app, BUG-000147050. If you're able to submit a bug report to Esri Support that'd be great; our support team can link your bug report to the existing one and that way we can keep you in the loop when any progress is made on it. Best, Jim
... View more
05-30-2022
04:48 PM
|
0
|
1
|
952
|
BLOG
|
Hi @MōnoSimeone thanks for your comments about the drawing tools in the web app, good suggestions. I would recommend contacting Esri Support so our Support team can open an enhancement request; similar requests can then be attached to yours, which helps us assess the demand for a feature enhancement. You'll get an official ENH number so you can track any progress on it. Best, Jim
... View more
05-26-2022
05:31 PM
|
0
|
0
|
5959
|
POST
|
Hi @Jo-Johnson Thanks for your query - in the latest (March 2022) versions of the Standard and Advanced templates, the allow_choice_duplicates column has been removed. The functionality related to this column is not supported yet and we're still working on the best way to do this, so we made the decision to remove it to avoid any confusion. For your existing surveys you can choose to keep or delete this column - either way, it will not affect your survey. For the namespaces column, you can leave the default value esri="https://esri.com/xforms" as is. As described above, this is only useful for local XLSForm conversion, which we're still working on. The default value will be required if the local conversion is going to be used; but otherwise this column is redundant. Hope this helps to clarify! Best, Jim
... View more
04-11-2022
06:50 PM
|
0
|
0
|
980
|
POST
|
Hi @Heena1 You can use the count-selected() function to count the number of choices selected by the user. For example, count-selected(${business}). For more info, see the Formulas documentation. There isn't a function for counting the total number of choices in a choice list. If the total number of choices is unlikely to change frequently, you could just hard-code this number into the summary report template. Hope this helps! Best, Jim
... View more
03-24-2022
07:33 PM
|
1
|
0
|
784
|
BLOG
|
In ArcGIS Survey123 an image question with the annotate appearance allows users to mark up an image. The image can be a photo captured with the device's camera, an existing image file, or a snapshot of a map. Similarly, an image question with the draw appearance provides a blank canvas for users to sketch on. In September and December 2021, we introduced several significant improvements to the user experience for draw and annotate questions, including better drawing tools and the ability to edit annotations. For a detailed look at these improvements, see the Updates to draw and annotate in ArcGIS Survey123 (September 2021) blog post. Survey123 ships with a default drawing tools palette that contains eight tools, including arrows, generic marker symbols, and text labels. The default palette allows users to modify the properties of the drawing tools to their liking while in the field. But what if, as a survey author, you want to make sure users draw their annotations with a specific set of tools, so that all annotations are consistent? In this blog post, we’ll explore how to create your own custom annotation tools palettes and add them to questions in a survey. Standardize image annotations for your organization Your organization might have a need to customize (or should we say, standardize) drawing tools to help make annotated images consistent and to help make image annotation in the field more efficient. For example, to ensure a particular feature is always drawn using the same line style, or that labels are always the same size and color. A few examples are shown below. A utility company might have specific symbols and line styles that relate to electrical or gas works. Similarly, an engineering organization might want certain colours and arrows to be used when marking up defects in equipment. An environmental assessment survey might require a special symbol to represent a particular type of ground cover. The February 2022 release of Survey123 allows you to create custom drawing tools palettes for the Survey123 field app, where you can configure your own line styles, add your own marker symbols, and so on. What’s more, custom palettes are applied to individual questions in your survey, meaning you can include multiple palettes in the same survey, each with a specific application. For example, in a road assessment survey, you might have an image question asking the user to indicate the where potholes are on a snapshot of a map. This question could have a custom palette that includes only two tools: specific symbols for small and large potholes. Another question in the survey might ask the user to take a photo of a guard railing that is damaged and use an orange arrow to indicate where the damage is. And so on. Note: Custom palettes for image annotation are not supported in the Survey123 web app. The process for creating a custom palette and adding it to your survey is as follows: Configure the Python environment in ArcGIS Survey123 Connect, so that you can run the conversion utility (step 4). Prepare a custom palette using the XLSPalette specification. Add the XLSPalette file and any associated files to the survey's media folder. Convert the XLSPalette to a .palette file by running the conversion utility on the Media tab in Survey123 Connect. In the XLSForm for the survey, set an image question with draw or annotate appearance to use the custom palette instead of the default palette by specifying the palette parameter in the body::esri:style column. The following sections will guide you through these steps. Configure tools in Survey123 Connect To use custom palettes in Survey123 you must first configure Python in Survey123 Connect. The reason this step comes first is because without Python, it is not possible to convert your XLSPalette file (step 4) and add it to your survey (step 5). Before you get carried away with designing drawing tools in XLSPalette, you’ll need to overcome this first hurdle! To get started: Install Python 3.7 or later. You can download Python from the Windows Store or the Python website. It is recommended to add Python as a PATH environment variable. If you have ArcGIS Pro installed, you can use its Python environment, which is installed with ArcGIS Pro by default. Install the openpyxl package. If you are using ArcGIS Pro as your Python environment openpyxl will be installed automatically. For more information, see Work with Python packages. Once your Python environment is installed, in Survey13 Connect, go to Settings and select the Tools tab. If Python was added as a PATH environment variable, Survey123 Connect should automatically detect your Python install. If it doesn’t, click the folder button next to the empty path and navigate to the folder where your Python environment is located. The default ArcGIS Pro Python installation is in: C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3 Survey123 Connect will automatically detect what Python packages are installed and let you know if you have the arcgis, openpyxl, and pyxform packages installed. This workflow requires openpyxl only. If you see a check mark next to openpyxl you can move on to the next step. If you don't see openpyxl checked, check the installed packages you have in the environment specified. Note that the openpyxl version number will vary depending on your Python environment, but any recent version should suffice. If you happen to have the pyxform package installed, you will also see the option to specify a Java Runtime Environment on the Tools tab, in addition to Terminal settings. Neither are not required for this workflow, or any other workflow in Connect at this stage – but watch this space. In the future, we hope to support additional tools that make use of Python, JRE, and Terminal. Prepare custom palette A custom palette is configured in XLSPalette, a .xlsx file that contains the worksheets that will be converted into a .palette file. The XLSPalette specification is designed specifically for creating annotation tools in Survey123. It provides a syntax that can be entered into a familiar spreadsheet, in much the same way as XLSForm is used to create a survey form. Download the Survey123 XLSPalette template to get started. Toolsets and drawing tools Each worksheet in the XLSPalette is a toolset: a group of tools in the palette. The rows in each toolset worksheet define the annotation tools that make up the toolset. Toolset worksheets can be added or removed as required. To add a new toolset worksheet, make a copy of an existing toolset worksheet to ensure the conditional formatting and data validation is preserved. Toolset worksheets that do not contain any rows besides the header row will be ignored when the XLSPalette is converted to a .palette file. There’s no limit to the number of tools you can add to a toolset, but a practical limit can be determined by your screen size. Half a dozen tools in a toolset works well. The full XLSPalette specification is described on the Reference worksheet in the XLSPalette template and in the Survey123 documentation. Data validation on the toolset worksheets will help guide you through what is required in each column. Cells that require a value are highlighted red. The cells to complete will vary depending on the type. The following example shows the XLSPalette configuration for three annotation tools on a toolset worksheet named Services&icon=wrench. The &icon= parameter in the worksheet name is used to specify the toolset icon that will appear in the Survey123 field app. Read more about toolset icons here. The drawing tool type (line, area, marker, or text) is specified in the type column. A label for the tool is provided in the label column; this label will appear in the Survey123 field app, under a preview of the tool’s style. In the tool column, the tool style is defined. For example, a line can be a straight line, or a polyline with multiple vertices. These styles are also part of the default palette. For more information on these, refer to the documentation on the default palette. The symbol column is where you set out the properties of the tool in name=value pairs, separated by ampersands. In the textSymbol column you can specify text properties such as color, size, and alignment. The syntax above includes the following: For Gas Line (Proposed), the color, width, and style properties are used to create a blue line that is five pixels wide, with a dash pattern of 4 on, 1 off. That is, solid line for a relative length of 4, followed by a space of length 1. For Work Area, the tool column is set to polygon, which allows users to draw a polygon vertex-by-vertex. The polygon has a transparent red fill and dotted outline. See more on tool colors, below. For Gas Meter, the marker is a .svg file that is stored in the survey’s media folder. The &size= property sets the marker size in pixels. The black text label is anchored to the bottom of the marker and has a cyan halo. For Notes, the syntax in the textSymbol column creates a “sticky note” text box with yellow background and black outline, with text that is aligned to the left. Here’s how the tools appear in the Survey123 field app: Tool colors Colors can be specified by HTML color name, #rrggbb, or #aarrggbb. Use #aarrggbb to specify opacity. The “aa” represents the hexadecimal value for the alpha channel, which describes the degree of transparency. This value can be equated to an opacity percentage by determining the percentage of 255, then finding the hexadecimal value of that number. For example, an opacity of 50% (that is, 50% transparent) would be 255 × 0.5 = 127.5. The hexadecimal value for 128 is 80, so standard blue with 50% transparency would be given as #800000ff. You can use the built-in Windows Calculator app in Programmer mode to get the hex value for a decimal number. Once you have configured the toolsets and drawing tools, copy the XLSPalette file (XLSX) and any image files the palette uses (for example, SVG marker symbols and toolset icons) to the media folder for your survey. The XLSPalette can now be converted into a .palette file that Survey123 can use. Convert palette In Survey123 Connect, go to the Media tab for your survey. The Media tab lists the contents of your survey's media folder. A palette button is shown alongside all .xlsx files in the media folder. Click the palette button to convert your XLSPalette. When the conversion is complete, a .palette file is added to the media folder. This file contains JSON that describes your toolsets and drawing tools in a notation that Survey123 can read. For the curious, you can open a .palette file in a text editor and check it out. The name of the .xlsx file will be the name of the .palette file, and this is the name that must be used in the palette=<palette_name> parameter in your XLSForm. To ensure your palette name can be used as a parameter, ensure your .palette file name does not contain any spaces. Update palette To update your custom palette, make the changes in the .xlsx file, save your changes, and click the button to run the conversion utility on the Media tab. This will update the existing .palette file in the media folder. The changes will be available in Survey123 Connect as soon as the form preview is updated. This process is quick and helps when designing a palette, as there can be some trial and error involved in getting the symbol settings just right. Once you’re happy with your custom palette, publish your survey to see the changes in the Survey123 field app. Add custom palette to your survey You can add as many custom palettes to your survey as you like, but only one palette can be used in each image question. To add a custom palette to your survey: Ensure the .palette file is in your survey's media folder. For an image question with draw or annotate appearance, add palette=<palette_name> in the body::esri:style column, where <palette_name> is the name of the .palette file without the extension. This parameter is case sensitive. For annotate questions, specify the image capture method in the same column, using the method parameter. The palette and method parameters must be separated by a space. For example, palette=SiteLayout method=map,camera,browse. For more on the method parameter, see the documentation on appearances. Publish your survey. Your custom palette will be used for the image question, replacing the default palette. A number of improvements introduced in the last six months means there’s now a lot you can do with annotation in the Survey123 field app. We hope you enjoy the freedom to tailor the drawing and annotation experience for your organization’s needs. Leave a comment below and let us know how these features might help your workflows!
... View more
02-23-2022
03:20 AM
|
4
|
9
|
6691
|
POST
|
Hi @LaoiseDillon The image-map appearance is not supported in the Survey123 web app. Please see documentation on image-map here and here, and also this blog post. You could raise this as an enhancement request with Esri Support, or up-vote this ArcGIS Idea and add your comments to it: Select options of image-map to work in internet br... - Esri Community Best, Jim
... View more
02-15-2022
07:07 PM
|
0
|
0
|
863
|
POST
|
Hi @kawakawa4 The total eggs calculation is not working when only one of the choices is selected for all repeats because one half of the sum is null (i.e. if one of the eggcount questions remains not relevant across all repeats, its value is null). One way around this would be to use the coalesce() function in the total calculation, which will overcome any null values (replacing null with zero). Something like: coalesce(sum(${Egg_Natural_Less200_EggCount}), 0) + coalesce(sum(${Egg_Natural_More200_EC_Total}), 0) Hope this helps. Best, Jim
... View more
02-15-2022
02:16 PM
|
1
|
1
|
574
|
POST
|
Hi @NathanialWigington Thanks for including your XLSForm. The selected() function you've used for the choice filters relies on the choice name (i.e. the value of the choice), not the choice label. Looking at the feature layer, it looks like UNITNAME corresponds to the labels in your Park_Name choice list, whereas ENTITYID looks like it corresponds to the choice names. Changing the pulldata() for the Park_Name question to reference attribute.ENTITYID instead should help. For MGTUNTIID, in the feature layer many of the values have a mix of upper- and lowercase letters, whereas in you choice list (and the MU column for the choice filter) they are all uppercase. Note that the choice names are case sensitive; so changing these to match exactly what's in the MGTUNTIID field should fix the Work_Order question. Hope this helps. Best, Jim
... View more
02-14-2022
08:31 PM
|
0
|
0
|
937
|
POST
|
Hi @LouiseHarris1 if you're using an older version of the XLSForm template, you can simply add a guidance_hint column to the survey sheet. Otherwise, you can download the latest versions of the Advanced and Standard templates from Connect (New survey dialog) and migrate your survey to the new template. You'll find some hints and best practices in this blog post - see the Migrate an existing survey to a new template section. Note guidance hints are supported in Survey123 version 3.12 and later.
... View more
02-07-2022
04:22 PM
|
1
|
0
|
1941
|
BLOG
|
Hi @DerrickWestoby Thanks for raising this. For the forthcoming 3.14 release of Survey123, the behaviour for annotate questions has been modified so that if you have more than one method specified in body::esri:style (e.g. method=camera,browse,map) you'll be presented with a pop-up when you first open the canvas that allows you to choose the desired method. For reference, this is logged as ENH-000144493. If you only have one method specified, that method will be launched when the canvas is opened. If you don't specify a method, it will default to launching the camera when the canvas is opened. If you have a default background image set, this will also appear in the pop-up as an option. Please see the Using capture methods with the annotate appearance documentation on EAC. This functionality is also available for testing in the latest beta builds. Best, Jim
... View more
02-01-2022
07:00 PM
|
2
|
0
|
6778
|
POST
|
Hi @JunFUKUDA Thanks for reporting this issue - there is a known issue in the Survey123 web app with URLs that contain curly brackets { }. This issue has been observed in the survey form itself, as well as the thank you screen. The Survey123 team is working on a resolution to this issue but no indicative timeframe at this stage. Please keep an eye out on the Survey123 blog and Early Adopter Community for release announcements. I would also encourage you to submit this issue to Esri Support so that it can be assigned a BUG number; this will allow you to track its progress. Best, Jim
... View more
01-30-2022
08:04 PM
|
0
|
1
|
352
|
POST
|
Hi @bhariadi Thanks for providing your XLSForm. Please see attached a simplified XLSForm that attempts to solve your problem using the count() function, and also by rearranging the questions slightly. One thing to note here is that I've avoided using aggregate functions (sum, count, etc.) inside the repeat that the function is aggregating. Please see the Survey123 Tricks of the Trade: Repeats blog post for some great info, as well as the documentation on repeats. Hope this useful, please let me know if this works for you. Best, Jim
... View more
01-30-2022
07:50 PM
|
1
|
1
|
1071
|
POST
|
Hi @LouiseHarris1 A couple of ideas that might be of use: If you're authoring your survey in Survey123 Connect, one option would be to use a guidance hint. Guidance hints appear under the question label, either as a 'lightbulb' icon in the Survey123 field app, or an expandable panel in the web app. See the documentation on hints for more details. Alternatively, you could use a note question inside a group that uses the compact appearance (collapsed by default) - users could expand the group if they need to read the notes. Hope this helps. Best, Jim
... View more
01-30-2022
07:24 PM
|
1
|
2
|
1961
|
Title | Kudos | Posted |
---|---|---|
1 | 06-29-2020 07:21 PM | |
1 | 08-24-2023 07:07 PM | |
2 | 08-23-2023 11:57 PM | |
1 | 11-28-2022 07:24 PM | |
2 | 08-08-2023 11:43 PM |
Online Status |
Offline
|
Date Last Visited |
4 hours ago
|