Latest Contributions by HélèneTouyéras

‎06-21-2018

Good afternoon, Is it possible to use some smart syntax in Survey123 report templates to avoid attachment piling up on top of each-other? My survey has its "image" field within a repeat, so people can take several pictures of the feature they are surveying, for instance to show the different issues on the same feature. I downloaded the report template and reused the part about the attachment without modification: ${#attachments} ${attached_item | size:250:0} ${/attachments} When creating the report for a feature with several attachements, all the attachments are ported in the report, but they are all placed on top of each other. EDIT: the above syntax will place each picture on its own line, it is okay. I realize I did wrong when actually using: ${#attachments} ${attached_item | size:250:0} ${/attachments} I was wondering if there is a way to iterate through the attachments, so that I place the first one found on the first page, and all attachements (to make it simpler) at the end of the document, that is, all of them side by side or each on its line, but not on top of each other. Any help greatly appreciated!! Hélène.

‎05-04-2018

I found a workaround on GIS Stackexchange. There is an interaction between versions of Python (32 bits or 64 bits) and arcpy tools. My simplistic python snippet is working if I call it with 32-bits python, and not with 64-bits python.

‎05-04-2018

I have the exact same issue after "exporting as a python snippet" the results of a metadata conversion tool. The GUI tool works well and outputs a valid result (metadata XML file), but the python snippet only comes out with the error code 00816. In other words, the same on-the-shelf tool works when called from the GUI, and not from Python (using the same arguments). This is not a case of upgrading versions. Or downgrading - I observe the issue in ArcGIS 10.5.1, but the process was working in previous versions (10.0, 10.4 proved OK here and used regularly). There seems to be a disconnexion between the GUI and arcpy - can this be? Has anyone observed the same?

‎04-20-2018

Thanks Mike, I had a look and found the Edit menu in ArcMap - I'll wait for this week's field survey campaign to be over to backup the data and modify it. Many thanks for your help!!

‎04-20-2018

Thanks for the fast reply James! I took a closer look at my two surveys after reading your comment - the domains that do not show aliases have two different sources: Fields with a "choice-filter" dependency Fields with a "select_multiple" question I have modified my screenshot above to reflect this. I also checked the behavior when porting the data into a report: the "select_mulitple" question appear in the report with the alias value - even though the alias is not visible in the feeature service table. the fileds with a "choice-filter" dependency appear in the report with the coded value only.

‎04-19-2018

I have created survey templates with Survey123Connect for ArcGIS (v.3.0.14), with extensive use of "select_one" fields. The domains are mostly defined in the "Choices" worksheet, and sometimes in the "external_choices" worksheet. In the Field App, Survey123 for ArcGIS, all domains aliases always display OK. Some of those aliases do not display when I view the Feature Service, whether ArcGIS Online or the Survey123 website, or in ArcMap: the field shows the coded value only. I cannot find why some of the domains "work" (show the alias) and why some don't. All coded values are short, and created in the Survey123Connect Excel worksheet (short values, mostly textual for client's needs, mostly frrom the "choices" worksheet and some from the "external_choices"). Do you know what causes this inconsistent behaviour, and how I can modify my survey design to consistently disply domain aliases? Below a series of screen shots showing the same fields in Survey123 for Arcgis, and in ArcGIS Online, with the corresponding source Excel cells.

‎04-19-2018

After several days of fieldwork, our crew is happy with Survey123 ease of use. They nevertheless made a few mistakes, and some bulk correction is necessary. I loaded the feature service in ArcMap (10.4.1), but the service is not editable (see below). I am logged in AGOL with the same credentials as used to design the survey, and am able to edit the data in AGOL... very puzzling! Are all Survey123 feature service impossible to edit in ArcMap, and if not, what is triggering this behaviour? (ArcGIS Desktop version? Feature service structure/content?, other?)... help!!

‎04-11-2018

Hi James, and thanks for your reply! Our users are currently using textual values (N,S, E,W, NE, NW, SE, SW) - they are not geographers, and would not be able to interpret numeric values (so if the widget was developed with numeric values, we would try to fill a dependant field with textual values.)

‎04-06-2018

Brilliant - many thanks for the adequate and very fast response!

‎04-06-2018

Apologies if this is very basic..My survey formular contains a "% mortality" filed. I would like to constrain users to entering values beween 0 and 100. I have looked here, and here, but could not derive a working solution from either page. Any ideas? Many thanks!!

‎04-06-2018

Would it be possible to add a "aspect" widget, to record whether a feature is facing north/east/west/south or intermediate directions? We are thinking of the image of a compass, and radio-buttons at each direction and intermediate direction. Formatting of the aspect value could then cater for displaying numeric or text values. Our use case is in tree surveying, to record whether a tree is bent/leaning in one direction, and tree buttress direction (if present)

‎04-06-2018

I have the same need. The Distress widget is brilliant as extremely visual ; being able to customize it would make it more powerful and widespread. The colors used by default have implicit meaning (green: good ; red: bad / grren : low ; red: strong, etc), which is not always a good match with the numbers associated to them (by default: red: large value). I would like to use a version of Distress that is low value = red = bad/low and high value = good = green. The use case is to register tree helath state or damage asseessment. The likert widget matches the need, but is much less visual and therefore less powerful.

‎04-06-2018

I would also like to reverse the color ramp, to make a visual slider from 0/bad/red to 10/good/green. I am testing version 3.0.014 and this functionality is not available. Thank you.

‎04-05-2018

Different country, exact same problem here, at the French Forestry Commission. Please, please, please, give us tools/parameters to specify proxy settings and be able to use Survey123Connect & Survey123 from "government-issued-proxy-protected" hardware.

‎04-05-2018

Welcome to our Feedback Community

Online Status	Offline
Date Last Visited	‎03-01-2024 12:53 PM

My Ideas

Latest Contributions by HélèneTouyéras

Survey123 Report: placing attachments side by side (or each on a different line)?

Re: ERROR 000816: The tool is not valid.

Re: ERROR 000816: The tool is not valid.

Re: Edit Survey123 data in ArcMap?

Re: Survey123: domains are inconsistently displayed

Survey123: domains are inconsistently displayed

Edit Survey123 data in ArcMap?

Re: Survey123: Feature Aspect

Re: Survey123: constraint on percentage field?

Survey123: constraint on percentage field?

Survey123: Feature Aspect

Re: User customizable version of the distress appearance

Re: Change 'Distress' Color Ramp?

Re: Proxy Settings for Survey123 & Survey123Connect

Re: Sneak Peek: Survey123 and Webhooks (Integromat)

Re: tab through data entry on Survey123 form on PC

Smart Editor cannot fully edit multipoint feature ...

Re: Smart Editor cannot fully edit multipoint feat...

Re: Survey Description- Hyperlinks

Re: Allow to Launch Survey123 Native Client from E...