Hello! I'm looking for help on several aspects of a feature report. I'm a complete newb to feature reports. I built the survey from scratch using Survey123 Connect and I have learned a lot so far! The end goal of this project is to streamline data management and reduce overall time spent by switching to survey123 with a feature report. The form is designed to collect basic data at one geopoint and include to four photos per geopoint. The feature report is generated from a number of selected points at a given property and I've been using the "merge continous" output setting.
I've been able to get pretty close to the desired output but am spinning my wheels searching for useful help articles at this point. There are three sections to the report- see attached pdf for example of descriptions below.
Map
Photopoint Coordinates
aka these are the feature report output goals 🙂
Photopoint map example from existing document. This map is manually created by staff at this time
Photopoint images and description. The photopoint images and captions are manually created by staff at this time. The text box below describes how the information corresponds to the form design. The attached XLS form has the rows highlighted in same colors.
Solved! Go to Solution.
Hmm.
I've not tried to call on orderByFields that way. There is a chance it isn't supported since that looks properly formatted.
Same deal for drawingInfo. I haven't tried that variable yet since it isn't something I would typically need. However, what you have in your tests are the same things I would have tried. Given that you tried so many variations and you are seeing those different outputs, I think that it may be worth it if you contacted Esri support so you could jump on a call and have them look in-person.
Map
Photopoint Coordinates
When working with photos, don't forget to add getValue:"". E.g., ${project_photo | getValue:"" | size:0:0:400:300}
This ensures the photo is printed in a higher quality. Without that parameter, photos can be super grainy.
Thanks @abureaux !! I'm so.so.so close to having this done and am very grateful. I'm still stuck on two things:
First, I can't get the summary map of all points in the report to look right. I've been playing around with a ton of permutations based on the info below (source link).
By default, a map question will display using a default map symbol, regardless of symbology set in the feature layer. You can use thedrawingInfo method to extract and use the drawing information stored in a specific feature layer, including the symbol, label, and transparency used. You can specify this information either from the current layer or from a specific feature layer through a provided URL.
${location | drawingInfo:"currentLayer"}
${location | drawingInfo:"https://.../FeatureServer/0"}
I've attached a word doc trying to track the trial and error outcomes. It's a bit messy but it all ends up that I can't seem to get the desired symbology output (box style point with label of "pointnum").
Second, the "dot notation" worked beautifully and allowed me to edit the caption text. It's *perfect*! I tried using it to achieve the desired photo point sorting in a couple ways without success. Am I trying to do something that isn't possible syntax-wise?
${#images | orderByFields:"Baseline_Collector.pointnum ASC"}${Baseline_Collector.pointnum}${image_alpha | getValue:""}) ${ Baseline_Collector. image_text}. ${image_text2} facing ${photo | getValue:"direction" | round:0} degrees
${#images}${Baseline_Collector.pointnum | orderByFields:"Baseline_Collector.pointnum ASC"}${image_alpha | getValue:""}) ${ Baseline_Collector. image_text}. ${image_text2} facing ${photo | getValue:"direction" | round:0} degrees
Hmm.
I've not tried to call on orderByFields that way. There is a chance it isn't supported since that looks properly formatted.
Same deal for drawingInfo. I haven't tried that variable yet since it isn't something I would typically need. However, what you have in your tests are the same things I would have tried. Given that you tried so many variations and you are seeing those different outputs, I think that it may be worth it if you contacted Esri support so you could jump on a call and have them look in-person.