Latest Contributions by IsmaelChivite

Digital cameras typically embed metadata at the point of capture into image files. EXIF (Exchangeable Image File Format) is the most widely adopted standard for encoding this metadata within the photos you take.  Some common data fields include the camera make and model, its serial number, the date and time of image capture, the shutter speed, the aperture, the ISO speed setting...  If a GPS is available to the camera, EXIF will also include the location from which the photo was taken and also the direction. All the above information can be critical so we added quite extensive support for EXIF data within Survey123. Preserving and capturing EXIF data with your photos. The Survey123 field app is designed to preserve and capture EXIF data whenever possible.  When a new image question is added to your survey, you can use the Survey123 app to either browse for an existing photo, or use your device's camera to capture a new one. If you browse for an existing photo, the Survey123 app will preserve any existing EXIF data in case at some point you want to download the photo from ArcGIS and extract the EXIF metadata.  This is important particularly when you use high-end cameras that write EXIF tags of your interest, or when you simply are handed a photo from someone else. If you choose to capture a new photo with the Survey123 field app, not only EXIF metadata will be populated according to the  capabilities of your device, but also a handy GPS button will be available so you can refresh the GPS coordinates from your device right when you take the photo. The reason why this is important is because the GPS in your device may not have fixed the best possible location when you shoot the photo. By using the GPS button in the Survey123's app camera widget you can help getting the best possible location into your EXIF's metadata. Looking into basic EXIF metadata tags The Survey123 website has built-in reporting capabilities that let you look at basic EXIF metadata in photos submitted. Simply go into the data tab, and expand the Individual Survey Response report for a particular record. Simply click on photos within the report to access basic EXIF metadata such as the coordinates and direction where the photo was taken, the device used to capture the photo and the date and time.   Extracting EXIF metadata using the pulldata() XLSForm function My favorite feature in Survey123 in regards with EXIF is the ability to write expressions in your XLSForm that will automatically extract EXIF tags from your photos so you can build data validation rules in your smart form and even store this EXIF tags as attributes in your features.  This means that later on you will be able to easily query your EXIF metadata within ArcGIS without any post-processing.  A classic example is extracting the GpsImgDirectiontag into an attribute, so you can later use it to rotate your symbols on a map, or the GpsLongitude and GpsLatitude tags to later map the location of the photos. Other handy tags include ImageWidth, ImageLength and ExtendedDigitalZoomRatio which give you information about the size of the image as well as the optical zoom level used (if any) when the photo was captured, and of course the ImageDateTime tag as well You can extract the EXIF tags using the pulldata() function, which we extended specifically for this purpose. The syntax is as follows: pulldata("@exif", ${image}, "GpsImgDirection")   The first parameter indicates that the pulldata() function will be used to extract EXIF metadata. The second parameter indicates the question in your XLSForm with the image. The third parameter defines the name of the EXIF tag to be extracted. There are over 300 tags in the EXIF specification, although there is no guarantee that all of them will be populated. It varies a lot depending on the device.  The table below shows the most common ones. EXIF Geotags EXIF Basic Camera  and Image Tags Extended Tags GpsVersionId GpsLatitudeRef GpsLatitude GpsLongitudeRef GpsLongitude GpsAltitudeRef GpsAltitude GpsTimeStamp GpsSatellites GpsStatus GpsMeasureMode GpsDop GpsSpeedRef GpsSpeed GpsTrackRef GpsTrack GpsImgDirection GpsMapDatum GpsDestLatitudeRef GpsDestLatitude GpsDestLongitudeRef GpsDestLongitude GpsDestBearingRef GpsDestBearing GpsDestDistanceRef GpsDestDistance GpsProcessingMethod GpsAreaInformation GpsDateStamp GpsDifferential ImageWidth ImageLength ImageBitsPerSample ImageCompression ImagePhotometricInterpretation ImageOrientation ImageSamplesPerPixel ImagePlanarConfiguration ImageYCbCrSubSampling ImageXResolution ImageYResolution ImageResolutionUnit ImageStripOffsets ImageRowsPerStrip ImageStripByteCounts ImageTransferFunction ImageWhitePoint ImagePrimaryChromaciticies ImageYCbCrCoefficients ImageYCbCrPosition ImageReferenceBlackWhite ImageDateTime ImageDescription ImageMake ImageModel ImageSoftware ImageArtist ImageCopyright ImageXPTitle ImageXPComment ImageXPAuthor ImageXPKeywords ImageXPSubject ImageRating ImageRatingPercent ImageLensSpecification ImageLensMake ImageLensModel ImageLensSerialNumber ExtendedExifVersion ExtendedFlashPixVersion ExtendedColorSpace ExtendedComponentsConfiguration ExtendedCompressedBitsPerPixel ExtendedPixelXDimension ExtendedPixelYDimension ExtendedMakerNote ExtendedUserComment ExtendedRelatedSoundFile ExtendedDateTimeOriginal ExtendedDateTimeDigitized ExtendedSubSecTime ExtendedSubSecTimeOriginal ExtendedSubSecTimeDigitized ExtendedImageUniqueId ExtendedExposureTime ExtendedFNumber ExtendedExposureProgram ExtendedSpectralSensitivity ExtendedISOSpeedRatings ExtendedOecf ExtendedShutterSpeedValue ExtendedApertureValue ExtendedBrightnessValue ExtendedExposureBiasValue ExtendedMaxApertureValue ExtendedSubjectDistance ExtendedMeteringMode ExtendedLightSource ExtendedFlash ExtendedFocalLength ExtendedSubjectArea ExtendedFlashEnergy ExtendedSpatialFrequencyResponse ExtendedFocalPlaneXResolution ExtendedFocalPlaneYResolution ExtendedFocalPlaneResolutionUnit ExtendedSubjectLocation ExtendedExposureIndex ExtendedSensingMethod ExtendedFileSource ExtendedSceneType ExtendedCfaPattern ExtendedCustomRendered ExtendedExposureMode ExtendedWhiteBalance ExtendedDigitalZoomRatio ExtendedFocalLengthIn35mmFilm ExtendedSceneCaptureType ExtendedGainControl ExtendedContrast ExtendedSaturation ExtendedSharpness ExtendedDeviceSettingDescription ExtendedSubjectDistanceRange   To get you started quickly with the use of the pulldata() function, I recommend you have a look at the EXIF XLSForm sample included with Survey123 Connect for ArcGIS. Open Survey123 Connect for ArcGIS Click on New Survey Find the EXIF survey in the Samples category Set a title to your new survey and create it The list of tags is located in the choices worksheet Limitation: pulldata("@exif") will not work if your image question uses the multiline appearance. In most cases I see the pulldata() function being used to simply persist EXIF tags from photos as attributes in your feature service, but you can also use them to build input data validation logic. For example, you can compare the location of a geopoint question in your survey with the location of a photo and prevent the user from submitting if the distance is bigger than a particular threshold. You could also display a warning if the user attempts to use a photo that was taken a long time ago etc.  This is were you get creative to get the best out of Survey123... ... View more

IMPORTANT NOTE: Content in this blog post has been revised in the https://community.esri.com/groups/survey123/blog/2018/01/22/a-simple-e-mail-notification-system-for-survey123-for-arcgis-v2 blog post.  The new blog as an improved version of the content and Python script. I constantly get requests from people who want to configure an e-mail notification system on top of Survey123 for ArcGIS.  The idea is simple: notify someone via e-mail every time a new survey is submitted. There are different approaches to do this. I have seen some organizations configure ArcGIS GeoEvent Server in ArcGIS Enterprise for this purpose. It works pretty well and provides a great deal of flexibility, but not everyone has the luxury of having GeoEvent at hand. I have seen clever database triggers been written and also FME Server workflows for automating e-mail notifications. In this blog, I will describe a technique for doing this with a Python script and Windows Task Scheduler. Essentially, Windows Task Scheduler will run a Python script at a regular interval that you can define. The Python script will connect to your survey's feature service, look for any added records, and then connect to your own corporate e-mail server to send notifications accordingly. Many thanks to Mark Smith from Esri's Applications Prototype Lab who patiently worked on this Python script. While the Python script may not format the e-mail message exactly as you need, I hope that at least will give you a starting point from which you can write the exact logic that  matches your needs.  Below are step by step instructions so you can configure this Python script with your own survey. Configuring your ArcGIS Online feature layer For the script to work you need to enable an option in your survey's feature layer called 'Keep track of created and updated features' .  This is not to be confused  with Editor Tracking.  This option helps the Python script determine if any changes have been made in your feature service. Login into ArcGIS Online and open the Details page of your survey's feature layer. Switch to the Settings tab and make sure the 'Keep track of created and updated features' option is checked as shown in the screenshot below. Configuring the Python script Next we need to configure the Python script. Since you will want this script running unattended every at a regular interval, I suggest you choose a computer which will always running and connected to the internet.  Your laptop, which you may disconnect from time to time or take home is not a good choice. Choose either a desktop computer which is always on or even better a server managed by your IT department. The script requires Python 3.x to run and the 'requests' Python module installed.  If the 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 so you can install Python 3.x and then the 'requests' module. How to install Python How to install the 'requests' module Now you can download and configure the script as follows: Download the Detect Changes and Notify Python script and its associated init.json file and save them together within a folder in your computer. Edit and save the init.json file. At the very least, you will need to change the properties highlighted  in blue below.  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 anything 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 really 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. fsURL: This is the URL of your survey's feature service.  serviceuser and servicepw: The credentials of an ArcGIS Online account with access to the feature service. {     "email":         {           "recipients": ["[email protected]"],           "from": "[email protected]",           "subject": "Changes detected in your service",           "text": "You are receiving this e-mail because records have been added, updated or deleted in:\n",           "server": ["smtp.acme.com", "", "",""]         },         "service":         {           "fsURL": "https://services2.arcgis.com/fJJEXNgxjn0dpNsi/arcgis/rest/services/service_871ea76e106e4b1ab671ecc1e73c31ee/FeatureServer/",           "serviceuser": "username",           "servicepw": "password",           "fsLayerNum": 0,           "viewerURL": "http://arcgis.com/home/webmap/viewer.html",           "viewerMapLevel":19         },     "filenames":         {           "layergens": "layergens_ms.json"         } }    After saving changes to the init.json file, it is time to give the script  a quick test: Run the script once so it can capture the current state of your feature service. 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: General: Check the option to run with highest privileges and set the task to run even if you are not logged-in. 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. 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. We are working on some more flexible ways to make notifications via e-mail, SMS, voice call etc simpler with Survey123. We plan on adding some specifics about this before the end of the year in our Early Adopter Program. In the meantime, you may want to play with the approach outlined here as it may work just well for you. ... View more

Sometimes the most difficult part of writing a blog is coming up with a good title. I am not sure I quite got the right one this time, but since I have your attention I will describe now in more length a common problem that I see people having in Survey123, and some approaches to it. The 'Ticket Number' problem:  The use of Survey123 for ArcGIS to submit incidents, requests or workorders is quite common. In these cases, it is very likely that you will want to uniquely identify every survey submitted, so it can then be tracked throughout its complete life cycle: from the moment the survey is submitted, to when it is reviewed, assigned, rejected and/or completed. I will generically refer to this as the 'Ticket Number' problem.  Say for example you create a survey to help handle the whole life cycle of a 311 call, from the moment you receive a call from a citizen, to the moment it is, validated, prioritized, assigned, acted upon and closed.  To follow along the 311 request, you need to have a unique 'Ticket Number' so all parties involved can find the right information about the event. Ideally, this Ticket Number should be somewhat user friendly. There is not an obvious way in Survey123 to create such 'Ticket Numbers', at least not at first sight.  Lets look at some options. Auto increment fields (and ObjectIDs): In common database jargon, some people solve the problem with what is known as Auto Increment fields. Through an Auto Increment field, a database is able to assign a new and unique identifier (typically a number) to every new record added into a table.  This works well, because it does not matter from where you add a new record: when it gets to the database it will be assigned a new identifier... a new 'Ticket Number'. In ArcGIS, every record submitted to a feature service automatically gets a 'Ticket Number' through an attribute called ObjectID.  Every record submitted to ArcGIS, from Survey123 or any other app, will have its own unique ObjectID. Now, there are a handful of consideratons to keep in mind with ObjectIDs:   ObjetIDs are managed automatically by ArcGIS and as such, you can never change them.  ObjectIDs only get created when the record has been submitted to the feature service.  This is a problem when the life cycle of the event starts even before there is a chance to add a record into the feature service. Think for example that a city employee wants to use Survey123 to record an infraction of the city's code.   The person receiving the ticket must know what the Ticket Number is even if it has not yet been officially recorded (submitted) into the City's database (feature service).  If the city employee happens to be working on a remote area with no connectivity, there will be no chances of waiting for ArcGIS to give back a Ticket Number...  ObjectID fields are created new every time you create a new table, so there is really no way you can reuse old ObjectIds from a back-up table, or when you append records from one table to another.  The ObjectID or Auto Incrementing field approach give the most user friendly Ticket Number, but the necessity to be connected and the fact that it is completely managed by the database rule this option out in some scenarios. UUIDs: A Universally Unique Identifier (UUID) is, as its name  indicates, a universally unique identifier.   They are also known as GUIDs.   Unlike auto increment fields and ArcGIS's ObjectIDs, UUIDs can be created even if disconnected. That is, you do not need to wait for a record to be added to a master table before you can get a unique identifier. In Survey123, you can use the uuid() function within the calculation column of your XLSForm to create a UUID. A UUID looks something like this: e9858c60-84fe-49c6-b792-ac8cf0cc0cfd UUIDs are not pretty to look at, and from a practical perspective, impossible to remember. This is the reason why they do not quite fit the bill for the 'Ticket Number' problem either.  I wanted to bring this up anyways, because in some cases where you need a unique identifier, even if it is not human friendly, the use of the uuid() function could be handy. Purely for completeness, you should also know that ArcGIS feature services support the notion of GlobalID and GUID fields where UUIDs can be stored. In the case of GlobalID fields, the UUIDs are created automatically by ArcGIS when the feature is created in the feature layer, and guaranteed to be unique across all records in the table. If working with  GUID fields, UUIDs can be assigned and edited at will and no uniqueness is required. That is, you can calculate and set a GUID value using the uuid() XLSForm function. Hand-made Ticket Numbers: As long as you understand certain limitations, it is possible to create more human friendly 'Ticket Numbers' using functions supported in Survey123. It would be great if we had some sort of magic auto-incrementing function that would give us unique numbers sequentially.  This would allow us to start with an easy number like 0000 and then increase it to 0001, 0002.... easy to remember! Unfortunately, this is not that easy when working disconnected because there is no way for an offline device to know what is the next sequential number available.  Even if we were able to create sequential numbers within a device, we cannot guarantee that other devices will not create the same sequential numbers. Since time is always moving forward, a first approach is to use the current time, say down to the second, to generate a number. This can be accomplished by using the format-date() function, which is described in a previous post on Dates and Time in Survey123. Type Label Calculation text Ticket Number format-date(now(), '%y-%m-%d %H:%M:%S') The above will generate a number similar to this: 17-09-26 13:22:23 where the first two characters are the year, the next two the month, then the day, hour, minute and second.  If you look carefully at the expression within the format-date() function I have added some dashes and spaces a separators, but you can get rid of them if you like. Using the current time is certainly going to give us a unique number for the device you are on, but this does not mean that it will be unique across all devices capturing data. First of all, there may be people creating new survey at exactly the same second.  If working across multiple time zones, the chances of coincident numbers increase. Not everything is lost, because you can augment your Ticket Number with some additional data to reduce the changes of creating duplicates. You can for example use the username of the currently logged in user. This can be achieved by using the function property('username'). This would leave your Ticket Number expression as: Type Label Calculation text Ticket Number concat(format-date(now(), '%y-%m-%d %H:%M:%S'),property('username')) Obviously, using the logged-in username is only possible if your survey is secured. This approach will not work with public surveys where users can submit data anonymously. Depending on your particular scenario, you may be able to use a combination of one or more other attributes in your survey that would make your Ticket Number meaningful and unique. Technically, a handmade Ticket Number is not guaranteed to be unique although in practice, if you build it correctly, it will do the job just fine. When working with hand-made Ticket-Numbers or with the uuid() function, you also need to consider certain workflows that could get on your way. Hand-made ticket numbers and uuid() are defined through an expression in the calculation column of a survey. Calculations will execute when your form loads for the first time and will populate the Ticket Number accordingly. Once the Ticket Number is set, it will not be calculated again unless the calculated value is altered or removed. This is all good and consistent with how calculations should behave, except if a user decides to create a copy of an existing survey from the Sent folder. In that case, the Ticket Number will not be recalculated  so you will end up with a duplicate. Using the Sent box settings in Survey123 Connect, you can prevent this from happening by disabling the Sent folder for your survey. Similarly, you will want to decide if you want to make the Ticket Number be a read-only field or not. If users are given the ability to override a Ticket Number manually, you can no longer guarantee uniqueness.  You can easily flag the readonly XLSForm column of your question to 'yes' if  you want to make your Ticket Number question read-only. I hope that the above gives you some food for thought, even if you did not find a solution as you would have imagined it first. ... View more

Jack Dangermond credits Ralph Nader with being the person who inspired the creation of GIS Day. He considered GIS Day a good initiative for people to learn about geography and the uses of GIS. He wanted GIS Day to be a grassroots effort and open to everyone to participate. GIS Day was first held in November 1999 by the National Geographic Society, Association of American Geographers (AAG) and Esri. It is celebrated since then the third week of November, coinciding with National Geographic Society's Geography Awareness Week. Our 2.5 release includes updates to the Survey123 website, Survey123 Connect for ArcGIS and the Survey123 field app across all supported platforms. Make sure you refresh your browser cache and get the latest Connect and field app from the Survey123 download page. Survey123 website Remember to clear you  web browser cache to make sure you get the greatest and latest from this update: Chrome Internet Explorer Firefox Survey Publishing Enhancements (Modify Schema) With Survey123 web designer, you can visually create surveys right from your web browser.  Our vision with web designer is to provide the simplest experience possible for building powerful smart forms.  Survey123 web designer, in fact, does a lot for you under the covers including automatically building a fully functional ArcGIS feature service where data from your survey will get persisted.  Up until this release, you could not control the exact characteristics of the fields in your feature service. This is not typically an issue except when you want to download the data to Microsoft Excel, CSV or other formats like Shapefiles. Starting with this release, we added an option in the Publish Survey dialog that lets you modify the schema of your survey's feature service.  You can control the exact name that will be given to fields, define the values to be stored when using choice lists and even the maximum length of text fields. Please note that you will not be able to change  the schema of fields that already exist in your feature service.  For  example, when you publish your survey for the first time, you will be able to modify the schema for all questions in your survey. However, if you publish the same survey again, you will only be able to modify the schema for new questions in your survey. Delete a survey while preserving the data Starting with this release, the Delete Survey dialog in the Survey123 website includes a handy option that will let you optionally preserve all data you captured.   If you choose to delete all collected data, your survey will be removed along with its feature service.  If you choose this option, you may want to first make a backup copy of your data first.  Changes to the Data tab The Data tab in the Survey123 website lets you explore all collected data using a map, a table and an individual response format. We made a handful of changes: A new refresh button lets you more easily update the map and table to get the latest data from your survey. You can now more easily drag the table view over the map to split the screen in between the two views. The Individual Response view includes a new settings dialog from which you can control the size of photos retrieved into your report. Click on photos in the Individual Response reports to open a detailed view which will let you also see EXIF metadata, if available, including location, direction, camera and size. Other enhancements and fixes in the Survey123 website A new keyboard shortcut for saving your work in web designer has been enabled: Ctrl+S (Cmd+S in Mac). Multiple fixes allow the Analyze and Individual Response reports to better handle surveys with Groups and Repeats. Survey123 Field App and Connect Enhancements Disable the Sent box in the Survey123 field app Through a new survey-level setting in Survey123 Connect for ArcGIS you can now disable the Sent box in the Survey123 field app. This setting has been requested by a handful of organizations who, for security reasons, want to ensure that data already submitted to ArcGIS is completely erased from the device.  Disabling the Sent boxis also handy if you want to prevent users from copying previously sent surveys to create new ones.   If you already have published a survey and you want to apply this setting, field users will need to delete their local copy of their survey first, and then download the survey again.  Simply refreshing the survey from the Download page will not take effect, unless the Sent box in the device is already empty. For more info, check this help topic. Extract Exif metadata from photos using the pulldata() function The pulldata() XLSForm function has been extended so you can extract Exif metadata from photos.  This allows you to store the Exif metadata as attributes of your features, making it possible to use this information easily once stored in ArcGIS. Information such as the date-time and location where the photo was taken are stored as Exif metadata. You can also retrieve information about the camera used to take the photo, its dimensions etc   The syntax for extracting Exif data is as follows: pulldata("@exif", ${image}, "gpslatitude") The first parameter indicates that the pulldata() function will be used to extract Exif metadata. The second parameter indicates the question in your XLSForm with the image. The third parameter defines the name of the Exif metadata to be extracted. Depending on the camera used to take the photo, Exif metadata can include more than 100 tags. For a detailed list of common tags available, look at the Exif XLSForm included in Survey123 Connect for ArcGIS: Open Survey123 Connect for ArcGIS Click on New Survey Find the Exif survey in the Samples category Set a title to your new survey and create it The list of tags is located in the choices worksheet Survey123 Connect publishing enhancements Survey123 Connect will no longer overwrite your survey feature service when attempting to add new questions to an already published survey.  A new dialog will prompt you to confirm that new fields should be added to your feature service. A side effect of this enhancement may cause you some confusion when attempting to re-publish surveys with notes in your XLSForm.   If the Publish dialog indicates that new fields will be added for your note questions, simply go back to your XLSForm and remove the value of your note question in the name field of the survey worksheet.  Notes should not include a name! You can learn more about notes in https://community.esri.com/groups/survey123/blog/2017/11/14/understanding-notes-in-survey123  New XLSForm Community Surveys and Samples in Survey123 Connect The Create New Survey dialog in Survey123 Connect for ArcGIS includes many functional XLSForms in the Community and Samples categories.  You can use these surveys as a starting point to your own. This update includes new XLSForms: Exif (Sample): Included in the Samples category, illustrates how to use the pulldata() function to extract EXIF metadata from photos in your survey. Smart Sketching (Sample): This sample illustrates how to use the draw and annotate appearances on image questions to enable smart sketching on an empty canvas, a photo or a predefined image. Spike (Sample): This functionality is in Beta and shows how to integrate Survey123 with Spike. More information at Video Link : 4237  Cardenal Amarillo (Community): A simple survey used to capture observations of Gubernatrix cristatain Argentina. This survey is a good example of how to include questions in your survey to record audio. It also shows how to include audio files in your survey so they can be played from your device. Pesticide use Log (Community): A survey for helping private pesticide applicators record the location and weather conditions where pesticide is applied. Other Survey123 Field App and Connect Enhancements and fixes A slider control in the camera widget now lets you apply optical zoom to take detailed photos. Read-only questions are now supported in the Survey123 field app Inbox. BUG-000107126: Disallow the ability to bypass certificate verification warnings in Survey123 for ArcGIS field app. BUG-000108290: Unable to collect geopoint locations on Android devices using a Trimble GNSS bluetooth receiver when configuring the device with a mock location and GPS-only enabled. BUG-000100273:  Importing data from Survey123 for ArcGIS into a geodatabase in Oracle returns an error "The Field is a keyword in the destination DBMS (cannot rename).[rowid]. BUG-000108893: Using Survey123 for ArcGIS field app, if a survey is taken while Offline, then the device is switched to Online, pending surveys in the Outbox will fail to send with Code 0. ENH-000100907: Provide documentation for silent and/or unattended installation for Survey123 Connect for ArcGIS. ENH-000104929: Support Single Sign On (SSO) experience for Survey123 Connect when using SAML-based Identity Provider (ADFS). Clearing and recalculating a dateTime question that uses the now() function now updates the value to the current date and time instead of the date and time from when the form was first loaded. The source code of both Survey123 Connect and the Survey123 field app have been updated in AppStudio for ArcGIS. ... View more