POST
|
Hi Doug, I have a couple of workaround suggestions for dealing with your conditionally hidden grid cell. One is to implement a ‘placeholder’ question such as a Note that is relevant when your conditional cell is not. The width of this ‘placeholder’ question will be factored in to the grid layout even when not relevant which may not suit your survey. The other suggestion may require you to re-order your cells. As you probably know, questions are automatically placed into a row if they fit. The key here would be to have your conditionally hidden cell on the end of a row and make sure that the following cell width does not fit onto the row. The ‘readonly’ field can accept an expression so perhaps that is your best bet if this is acceptable to your use case? What expression are you trying to use? I’ve attached an XLSForm with an example of each. Designing an effective Grid survey requires you to be mindful of your user devices. Could you consider using the default constraint message and then displaying the full constraint failure message as a note in a separate question? Obviously, making the constraint message shorter or the grid cell larger may also help here. The long constraint message is pushing the input box outside of the grid cell, messing up the form. The correct behaviour occurs on the second and subsequent submit attempts, ie the cell expands to accommodate the custom message and the input box. I’ll create an internal issue to investigate a fix. It would be great if you could also contact the Support team regarding this so they can assign an official bug number that you can track. If the issue is reported by other customers, it will be attached to the same bug number. This helps us understand the impact of the issue and prioritize it accordingly in our development plan. Thanks, Brett
... View more
10-06-2019
08:04 PM
|
0
|
5
|
922
|
POST
|
Hi Jing, You're not doing anything wrong! Inkscape is adding that transform function because you have your layer selected when relocating your graphics on the screen (as opposed to the <path> itself which just updates it's 'd' values). You can check this for yourself by creating a new SVG in Inkscape and draw a new path. Save your SVG without adjusting it at all - don't move, scale etc. You won't get a transform function added to the layer group. Likewise, you can draw a new path, make sure the path is selected (not the parent layer), adjust it by moving etc and you still won't have a transform function applied. I guess the key is to make sure you're not applying transforms to groups when editing your image. Brett
... View more
10-03-2019
09:55 PM
|
1
|
2
|
2015
|
POST
|
Hi Tracy, Have you seen this blog? It goes through some more detail on getting SVG files to work with Survey123. Check that your SVG file conforms to the minimum requirements listed in the blog. Often things like empty groups can catch you out. If you're still having trouble I'd be happy to take a look. Brett
... View more
09-30-2019
03:30 PM
|
0
|
3
|
2825
|
BLOG
|
Starting with Survey123 3.6, the field app now supports a new appearance of image-map. This new appearance allows Scalable Vector Graphics (SVG) files to be rendered in your survey form and provides a clickable image for both select_one and select_multiple questions. Choice list selections can now be made by simply selecting different parts of the image. The image-map appearance is currently not supported in the Survey123 web app. So what is an SVG? An SVG file is an XML-based vector image format for two-dimensional graphics, that has support for interactivity and animation. SVGs also have the ability to have raster image formats such as .png and .jpg embedded within them. The image-map appearance provides a powerful way to customise the UI of your survey without having to write a single line of code. This enables fast and intuitive data collection with the underlying user selections stored in the feature service. The 'Image-map Sample' survey, available in Survey123 Connect, shows a variety of use cases including Risk Assessment, Body Parts, USA States and Soil Texture. The animation on the right shows a Vehicle Damage Inspection survey that combines the image-map appearance with the photo watermark feature. This enables the inspection photos to be stamped with the corresponding vehicle part for easy identification later. These examples involve relatively complex shapes and highlight what is possible, but the most simple of SVG files can also provide real improvements to survey usability. The ‘big button’ experience is easily set up with a basic SVG file. Also included in the 'Image-map Sample' survey is a ‘Level of Difficulty’ example that is essentially just an SVG file containing 4 clickable <path> elements (plus some text and symbols for ease of use). Implementing the image-map appearance The following steps relate to the 'Level of Difficulty' example in the 'Image-map Sample' survey. You can follow this process using the 'difficulty.svg' file attached to this blog. 1) Add a select_one or select_multiple question to your XLSForm (more information on this step). 2) Set up your survey choice list. Each entry needs a list_name, name and label. The values in the name column are the ones that link the choices to parts of your image. list_name name label difficulty beginner Beginner difficulty intermediate Intermediate difficulty advanced Advanced difficulty expert Expert 3) Create an SVG file or assess an existing file for compatibility with Survey123. The second half of this blog goes into more detail on creating SVG images, for now just open 'difficulty.svg' (attached) in a text editor to assess it's compatibility. Ensure that your file has <path> elements with id values that match the name values in your choice list. The <path> elements with id values become the clickable areas of the image. <path
d="M 5.4998702,5.4998718 H 129.50013 V 194.50013 H 5.4998702 Z"
id="beginner" />
<path
d="M 135.48042,5.4804192 H 259.51959 V 194.51958 H 135.48042 Z"
id="intermediate" />
<path
d="M 265.48041,5.4804192 H 389.51956 V 194.51958 H 265.48041 Z"
id="advanced" />
<path
d="M 395.48041,5.4804192 H 519.51959 V 194.51958 H 395.48041 Z"
id="expert" /> Non-clickable areas are <path> elements without id values and other element types eg <rect>, <circle>, <text> etc. See below for more detailed SVG requirements and tips for using with Survey123. 4) Copy your SVG file into the media folder of your survey. The media folder is located in the survey folder (~\ArcGIS\My Survey Designs\{survey name}) which can be quickly accessed using the Files button in Survey123 Connect. If the media folder does not exist, you need to create it inside the {survey_name} folder. 5) Add image-map to the appearance column, and the name of your SVG file (include the .svg file extension) to the media::image column of your select question. type name label appearance media::image select_one difficulty difficulty Level of Difficulty image-map difficulty.svg That's all there is to it! Using SVG files in Survey123 While implementing the image-map appearance in Survey123 is simple, the contents of the SVG file itself can get confusing. SVG files can be created in a multitude of ways and each method may introduce issues when trying to use within Survey123. The remainder of this blog post will look at the most common ways of creating an SVG file and the associated tips and tricks for getting them to work in Survey123. Minimum SVG requirements for Survey123: Must contain a <path> element that has an id value. Non-<path> elements such as <rect>, <ellipse>, <circle>, <image> and <text> will not be clickable. Likewise, <path> elements without an id value will not be clickable. No empty groups. Having empty groups ie <g> </g> within your SVG makes all <path> elements become un-clickable. Can only have 1 group per nest level. You can have as many nested levels as you like, but if you have more than one group at a particular level (including the parent level), all of the <path> elements become un-clickable. SVG height and width (Viewport) must be defined. While your image will likely display properly in Survey123 without these, your clickable areas may become offset from the underlying image. Viewbox must match Viewport (if specified). You don't need to specify a 'viewBox' parameter in your <svg> element. However, if you do specify a viewBox that differs from your height and width values, your clickable areas will be offset from the underlying image. Other tips for SVG files: Transform functions. It is possible to have SVG elements with transform functions work perfectly in Survey123. However, we must understand that transforms have a cumulative effect when applied to nested elements. It is often best to avoid transform functions if possible. Number of clickable areas. Although most web browsers can render SVG files with up to 5,000 elements without any issues, these are obviously not practical for use in Survey123. Be mindful that each clickable <path> element needs to be large enough on the screen for the user to select. You'll need to consider what platforms, devices and screen sizes you're using Survey123 on, to decide on a practical limit that suits you. Downloading the perfect SVG from the web! So you’ve found the perfect SVG online and have downloaded it for use with Survey123. While the image you found online may look perfect, it needs to include the required <path> elements to be clickable in Survey123. There are numerous desktop vector graphics programs like Adobe Illustrator, Corel Draw and Inkscape as well as online SVG editors like Vectr, BoxySVG and DrawSVG. Most of these have tools that will convert different types of objects (eg <rect> or <circle>) to <path>, so perhaps your downloaded image can be easily tweaked to suit Survey123. There are online resources that have SVG files for download that are designed in a way that suits Survey123, particularly those with geography content like www.simplemaps.com and www.amcharts.com. Most SVGs you'll find online have not been designed in this way so open your file in a text editor to quickly assess the contents. Converting an existing raster image into an SVG You may have the perfect .png or .jpg raster image that you would like to use with the image-map appearance in Survey123. The image-map appearance only supports SVG files, so you will need to convert your raster to SVG first. Vector graphics programs have tools that basically trace your raster and create SVG objects which can be very effective. Alternatively, online converters such as www.pngtosvg.com or www.image.online-convert.com/convert-to-svg can help you achieve this. Results can vary, but some experimentation with the settings and thresholds can yield usable SVGs in no time. It is best if your raster image contains filled shapes with a limited range of colours. The 'Pipe Fittings' example was created using www.pngtosvg.com to first convert a .jpg to SVG. Then the unwanted light grey <path> elements were deleted using a text editor: Creating an SVG from scratch This option gives you the greatest control over your SVG file. While it is possible to write an SVG entirely in a text editor, vector graphics programs like the ones listed above are the easiest way to create an SVG from scratch. If you're completely new to digital graphics then perhaps the online SVG editors are your best bet. Otherwise, desktop programs often have a larger toolset without limitations on importing and exporting your finished SVG. Inkscape is a free and open source vector graphics editor and was used for some of the SVGs in the sample survey. The main advantage of using a vector graphics program is that you can easily embed raster images too. Embedding a photo into your SVG can be very useful, for example when the user needs to identify the selection they're making. Here is an example that includes photos of different lawn varieties: TIP: Having a raster image in the background of your SVG and drawing some simple shapes over areas you would like the user to click is often the quickest and easiest way to create your SVG for use with Survey123. The 'Stranded Oil Distribution' example was created using a .png file as the background image. Then 24 x squares were drawn as <path> elements over the top of the background image. They were given no stroke or fill properties so they are invisible, but they define the clickable areas that correspond to the underlying parts of the background image. More Information The image-map appearance type is included in the Survey123 documentation here: Select one and Select multiple. Detailed information on the SVG specification can be found here: Scalable Vector Graphics (SVG) 1.1 (Second Edition) and Scalable Vector Graphics (SVG) 2.
... View more
09-26-2019
04:05 PM
|
17
|
37
|
33237
|
POST
|
Hi Kim, Thanks for reporting this. The first 3 columns (type, name and label) are mandatory in the survey worksheet (see Documentation). Previous versions of the app may have handled this by chance (not by design) but it is strange that something has changed in v3.5. I'll look into why this has changed. Out of curiosity, what is the use case for having a hint but no label for a question? If there is an important use case we could look at the possibility of enabling this in the future through an enhancement. Brett
... View more
08-14-2019
04:04 PM
|
0
|
0
|
414
|
POST
|
Hi Vance, Just an update on this issue. We a working on a fix that will address the issue you've described here. The behaviour is occurring due to the timing of initialising a location from within the repeat. You will notice that if you move the parent geopoint while the repeated geopoint is aquiring your location, the repeat location will be immediately pulled from the parent. If that initialising isn't interrupted by moving the parent geopoint (which triggers the coord calculation), you will only get your current location as you described. A possible workaround for now is to remove the readonly from your repeat geopoint so that you are presented with a recalculate button. Recalculating the location will have the same effect as moving the parent location. Brett
... View more
07-26-2019
07:41 PM
|
0
|
0
|
2159
|
POST
|
Hi Bryce, OK – I’ve set the GRND_CVR field to be required (the repeat count for GROUNDCOVER was already set to 8). I am still not able to reproduce this issue. I get the expected behaviour when trying to advance through the Ground Cover repeat, ie each Ground Cover type is highlighted as required and each of the 8 repeat records are highlighted as required as I step through. Can you please confirm that you’re only seeing this behaviour on your Juniper devices? What do you see in in Connect or field app on your desktop / phone etc? I’m beginning to think this may be device related. Brett
... View more
07-25-2019
06:58 PM
|
0
|
0
|
1132
|
POST
|
Hi Joe, sorry for the delay. I think what you're trying to achieve is out-of-the-box functionality for feature service editor tracking. Without any configuration in Survey123 (ie no 'username' questions), the feature service will store 4 additional fields (Creator, CreationDate, Editor and EditDate). These fields are hidden by default in the Survey123 website but can be turned on with a small '+' on the right side of the Data page: In this example, I created this record from the 'survey123_publisher' account and then edited the same record with the 'bstokes_survey123' account. Subsequent edits will overwrite the Editor and EditDate data, but the Creator and CreationData data will persist. Hope this helps, Brett
... View more
07-24-2019
06:20 PM
|
0
|
2
|
533
|
POST
|
Hi Bryce, Phil has asked me to take a look at this. Does the XLSForm you supplied have the required settings removed? I’d like to address that original case if possible (where you thought there might be a bug with the required setting), rather than you needing to implement a workaround. Can you provide a copy of this XLSForm? I’ll assume this is the workaround survey as I’m not able to replicate the problem (perhaps due to it being intermittent). I’ve been testing on a Samsung Galaxy S6 running Android 6.0 with Survey123 v3.5.164. I’m just populating data at random in all nested repeats, is there a particular workflow I should be testing? What device are you using? And just to confirm, you’re also running v3.5.164 of Survey123? Thanks, Brett
... View more
07-22-2019
09:54 PM
|
0
|
3
|
1132
|
POST
|
Hi Joe, Yes you can have multiple username fields in your survey. When signed into ArcGIS Online, these fields are automatically populated with the account username. So all of your username fields will be populated with the same data, ie the current signed-in user. What error are you getting when trying to publish with Connect? Brett
... View more
07-18-2019
09:30 PM
|
0
|
5
|
533
|
POST
|
Hi Coy, This is absolutely possible in Survey123 using a custom JavaScript function. I've attached a step-by-step example taken from our Early Adopter Community and encourage you to join (if you haven't already) to check out other great samples and get ideas of what is possible. The example is performing a point in polygon query against a ArcGIS feature layer containing USA Zip codes. It returns your zip code based on your current, or chosen location. You could modify the function to query your soils layer and return any associated information to Survey123. Hope this helps, Brett
... View more
07-18-2019
09:18 PM
|
1
|
0
|
749
|
POST
|
Hi Matthew, You can now just have your users type their address into the map search box that has been set to use your organization's custom geocoder by selecting it from the drop down. This screenshot shows the default ArcGIS World Geocoding Service: This will only store the geopoint geometry in your feature layer (no address info). If you also want to store the address information in fields within your survey you can follow the same process but also include reverse geocoding of the point to populate address information into the specific fields you’ve configured in your survey. See the ‘Reverse Geocode’ sample available in Survey123 Connect. Hope this helps, Brett
... View more
07-18-2019
08:40 PM
|
0
|
0
|
2199
|
BLOG
|
Hello Parks, You can simply continue to add image questions to your XLSForm in Connect and re-publish. Since you have attachments enabled in your feature layer, this can include multiple attachments. Adding a repeat around a single image question is actually trying to add a related feature (with the name corresponding to your repeat) to your existing feature layer. Since your existing feature layer does not contain any related features you are presented with the error message. You will need to set up this relationship in order to get this working. This is most easily achieved in desktop by adding the relationship class and re-publishing your feature layer. Re-creating the survey based on your updated feature layer in Connect will read this related feature as a repeat and add this to your survey form accordingly. Just make sure that attachments are also enabled on the related feature layer. Hope this helps, Brett
... View more
07-16-2019
06:42 PM
|
1
|
0
|
4955
|
POST
|
Hello Thant Zaw Oo, You can achieve this by putting your geopoint questions within a repeat. Then just use the sum() function in your geoshape question in the calculate column to build the polygon from the points in your repeat. I suggest joining the Early Adopter Community (if you haven't already) where you can find more detailed explanations on this beta functionality. Here is an example of setting up your XLSForm: Hope this helps, Brett
... View more
07-03-2019
09:24 AM
|
3
|
3
|
2674
|
POST
|
Hi Deon, Thanks for providing all of the details for your setup. I am wondering if this is just a timing issue... At first I was able to seemingly reproduce your issue on my device (Samsung S10) while stationary. As the position bounces around I am getting momentary speed and direction readings from my internal GNSS receiver. If I don't quite coincide this when the pulldata function is triggered (either on form load or when you manually tap the GPS icon in the map widget), then I don't get the direction information into my survey. I have to ask- are you triggering the pulldata function whilst actually in motion? I found that even at walking pace, my device is constantly providing a speed / direction which is consistently being pulled correctly into my survey. Are you noticing consistent direction readings in the Location Status page, or are they momentary? Another explanation, although very unlikely, would be due to the way we handle network positions in Android devices. GPS positions are updated every second and network positions every 20 seconds. Network positions are stationary and don't have a speed or direction so if you pulled the data from @geopoint at that moment you'll never get a speed or direction value. We have a fix for this scenario in place that is currently being tested and will be in the next release of Survey123, but as I mentioned it's very doubtful to be causing your issue. Brett
... View more
06-20-2019
02:59 PM
|
0
|
0
|
467
|
Title | Kudos | Posted |
---|---|---|
3 | 04-16-2024 04:38 PM | |
3 | 01-23-2024 06:52 PM | |
4 | 08-22-2023 04:41 PM | |
1 | 07-27-2023 04:10 AM | |
2 | 02-15-2021 01:37 PM |
Online Status |
Offline
|
Date Last Visited |
Thursday
|