Latest Contributions by DerrickWestoby

Like Ismael said, I think the recommendations you get are going to depend on the type of analysis you're trying to do.  Depending on what that is, it could be possible to see real-time updates with some arcade expressions and visualization based on that.  For instance, you could have a polygon layer that's using an arcade function to summarize S123 points collected within each polygon and symbology that reflects the count of selected points, or if a "high priority" (or whatever) point is detected within a polygon.  In general, I tend to think that "real-time updates for visualization" can be accomplished with arcade expressions for stuff like that, but "real-time updates for quantifiable summarization" would need something like what Ismael described because I want those values stored in fields, which arcade expressions in popups or visualization will not do (unless you run it manually via calculate fields)  ... View more

The default report doesn't include the parameter to restrict the size of the images.  You can download the report template from the Survey123 website and add the parameters I posted to your image question, then re-upload it and generate your report.  ... View more

Are you sure it's not the underlying imagery that's changing?  It's very possible for a building in "World Imagery" to be at a different lat/lon than "NZ Imagery (Classic)" due to inaccuracies.  Even within the exact same imagery layer, different zoom levels can draw from different imagery collections with misalignment issues or perspective distortion issues.  Example: Exact same point data and basemap, but zoom level +1   If you want to see if this is the case, try using something like the "Community" vector basemap that stuff like building footprints as lines instead of actual imagery.   If you draw a polygon using that basemap and then render it in the feature report with the exact same basemap layer, I'd expect it to be in the same spot in both ... View more

I already made a longer post, but it disappeared?   Change ${image} (or whatever) in your feature report template to something like ${image | size:0:0:660:500} ... View more

You need to restrict the size of the photos in the feature report template itself.  You probably have something like ${image} in your feature report, but need to restrict the size with something like ${image | size:0:0:660:500} See attached for the photo template that I always use in my reports.     https://doc.arcgis.com/en/survey123/browser/analyze-results/featurereporttemplates.htm Images and other attachments For image questions, sizes can be set to ensure that your reports have images of consistent size. The format for these expressions is as follows: ${image1 | size:width:height:max_width:max_height} The width and height values control the set size of your image, measured in pixels. While these values are required for the expression, providing a value of 0 will place no restriction on that dimension of your image. For example, the following expression forces the width of your image to be 300 pixels while preserving the aspect ratio of the image: ${image1 | size:300:0} The maximum height and width values limit the maximum size of an image and are optional values. The following example forces the width of the image to be 300 pixels and restricts the image height to no more than 200 pixels: ${image1 | size:300:0:0:200} Image questions can also have image details extracted and displayed in a survey response. This can be used to display the file name and size of the image as follows: ${image1 | getValue:"name"} ${image1 | getValue:"size"} ${image1 | getValue:"width"} ${image1 | getValue:"height"} The same method can be used to display EXIF data from the image, showing details of where and when a photo was taken, as follows: ${image1 | getValue:"x"} ${image1 | getValue:"y"} ${image1 | getValue:"date"} ${image1 | getValue:"time"} ${image1 | getValue:"direction"} To display the original image at its full size and quality, use the expression without any method, or use the getValue expression without any value: ${image1} or ${image1 | getValue:""} To display the original image at full quality but a set size, use the getValue and size expressions together. ${image1 | getValue:"" | size:300:0} Note: If you are setting an image's size while using any other expression parameter, size must be placed last in the expression. Dates and times are stored as strings in EXIF data, so these values cannot be formatted in a report using the format expression for date and time questions. If formatting these values is important, consider performing the EXIF extraction as part of your survey using the pulldata() function. For more information, see Images. ... View more

Sorry, I can't think of any time I've seen that behavior before. Thanks for humoring me, Gary. I'll just subscribe to this thread and see if anyone else can point out the issue.  ... View more

I can see that the initials are displaying in the middle window of the dashboard, so they're being stored with the record.    Total shot in the dark, but can you verify that the  name/label (code/label) are both being stored in all caps (IE: Make sure that your "WELL TENDER KAM" Details display isn't just displaying a "KAM" label for a code of "kam"). I've never had this issue before, so that would be my only guess.  EDIT: You could also check if that would even be a problem by constructing a URL parameter for each. Ex: https://survey123.arcgis.com/share/SURVEYID?field:well_tender=KAM https://survey123.arcgis.com/share/SURVEYID?field:well_tender=kam I'm not sure if a failed validation when using URL parameters or editing an existing record would cause the field to display as empty or as not being a valid input.  ... View more

I use Integromat instead of Microsoft Flow, but very similar.  In a few of my scenarios, I'm adding all of the repeat records for that specific submission to a Google Sheets file and then exporting to a CSV.  It should be possible to accomplish what you're after by doing something similar and then using the ArcGIS REST API to overwrite your "linked content" CSV in your AGOL account with your updated CSV. I have updated feature attributes via Integromat  in one of my scenarios, but not a linked CSV...fyi.  Also, I believe that updating the linked CSV will only automatically trigger an update that iOS field app users will see. In my experience, I need to download the linked CSV in S123 Connect and then re-publish for Android users to see the updates).  Integromat scenario for hazmat sampling:   Branch that creates Asbestos samples CSV (In this case, from a repeat layer in the survey): Create new google sheet -> Define the headers -> Move CSV (because I can't define the folder location when creating the CSV) -> Iterate through each record ->  add record as a row     In your case, I imagine that you'd want to do something like: JSON Query Collection Layer & Parse response -> Create a new CSV and populate the headers from your parsed query -> add a row for each record -> Export as CSV (With same name as your current linked CSV)-> Overwrite AGOL-Hosted CSV file.  You could probably skip the whole query & CSV setup if you just use the REST API to export the layer as a CSV file directly.    edit: This was the first time I set up a scenario to update existing features so it's a little wonky, but it works (and I couldn't get it to work via the query string options previously)   ... View more

I'm about 12% sure that I've seen this mentioned before as a known issue when trying to create feature reports with images from a feature layer that wasn't created with Survey123 publishing (I'm fuzzy on this, so don't put too much weight on it).    If you submit a NEW record via Survey123, with a NEW image attachment, will the image show up in your feature report for that specific record?  If not, you can disregard my post.     ... View more

Do you have a value in the relevant column for this question?  From the S123 Early Adopter Community:   ... View more

Thanks Philip.  I couldn't find an existing bug for it and was surprised that I couldn't find anything searching geonet either.  I'll submit a bug report right now.  ESRI Case: #02990215 Multiline Predictivetext appearance causes feature report generation to fail I'll edit in the BUG# if it gets converted to a bug.  EDIT for posterity: This was confirmed as a bug (BUG-000146779), but using "predictivetext multiline" in the appearance column (instead of "multiline predictivetext") does work. While troubleshooting, we noticed that "multiline predictivetext" will work if it's present when the survey is first published, but not if it's changed after first publishing.    Just for the sake of continuity here... This works fine, both in-app and in the feature report: The portion of the feature report that prints out this response: If I change it to multiline predictivetext and republish, the in-app behavior works as expected: New records and existing records fail to generate with this error though: And I start getting a syntax error when trying to upload an edited feature report (with appearance:multiline still set):   ... View more

Hi @BrandonArmstrong ( @Anonymous User ) - This value works fine in S123 connect and the field app behaves as expected, but my feature reports fail to generate when I make this change. The error message says something along the line of:   "appearance" cannot be found for ${comment_general | appearance:"multiline"} Is this a known bug/limitation?    ... View more

Good news, thanks @Jim-Moore ! ... View more

You really want to be flying with 70%+ overlap with SfM.   Keep in mind that this is based off the drone's altitude above ground level and an image footprint projected into the ground.  If you're flying over tall buildings, especially at low (<200ft) altitudes, the overlap in those areas is going to be insufficient.  You may have 70%/70% overlap at ground level, but 50%/50% on the building roof.  ... View more