POST
|
Thank you for your quick reply! I should have read more carefully. I change 'mode' to 'action' and upon clicking the URL, the app now opens the inbox when I click the hyperlink. Am I correct in assuming then that I need to have the inbox enabled for that survey, and that the survey response globalId I reference needs to correspond with a record matching the where clause of the inbox?
... View more
10-21-2022
09:13 AM
|
0
|
1
|
295
|
POST
|
Hello, I was wondering if the ability to use the mode URL parameter to open a copy of an existing survey record has been implemented in the field app yet? In a map authored with Map Viewer, I have polygon features and I am using an attribute expression to find the most recent inspection for each polygon feature, and then concatenate together a URL to try to open survey123 from within Field Maps Example result: arcgis-survey123://?itemID=[map item_id here]&mode=copy&globalId=517A2C24-2A78-496E-932C-EB8BA973C707 I have tried using global IDs both with and without the braces enclosing them, but no luck. There are no errors messages, but the survey just opens with no answers prefilled. I am the owner of the survey form and layer. I am testing using Survey123 on my iPhone. I do not have an Android device to test with, however our field users would be using Android devices. I would simply use URL parameters to pre-populate answers, but the form uses repeats I would like pre-populated too, so this is not an option. I'm paging @JamesTedrick to this thread because he seems to be aware of Survey123 development status.
... View more
10-21-2022
07:46 AM
|
0
|
3
|
328
|
POST
|
Hello I am having an issue where when I view data from a feature layer in ArcGIS Portal, attachments I have added to records in the feature layer via python do not appear to 'count' for the attachment count: The GUI will say there are zero 'Photos and Files' associated with the record, but when I click the 'Add' button, an existing attachment appears as expected. If I go to 'Add' and add another attachment through the GUI, this attachment count will increase to '1', despite there now being 2 attachments. I remove my secondary attachment, and the count goes back down to zero. Using the REST services, if I go to <feat server url>/1/OBJECTID/attachments. I see my one attachment: This is the Python I am using (within an FME Workbench) to attach the attachments in bulk: Basically I am using requests library to POST to <feat server url>/1/OBJECTID/addAttachment. The token and f=json are specified in the url and so are not included in the requests.post() call. import fme import fmeobjects import requests def processFeature(feature): url = feature.getAttribute('addAttachmentURL') mime_type = feature.getAttribute('mime_type') filename = feature.getAttribute('_justfilename') filenamewithpath = feature.getAttribute('_filename') files = {'attachment': (filename, open(filenamewithpath,'rb'), mime_type, {})} r = requests.post(url, files=files) feature.setAttribute("result",r.text) pass Is there something I must do after making the addAttachment call to increment the attachment count that Portal uses? ArcGIS Server version 10.71
... View more
01-21-2020
08:34 AM
|
0
|
1
|
553
|
POST
|
Hello We have a survey that may need to display one of many thousand images, depending on the asset type and asset identifier an inspector has chosen. Rather than package all of these image files with the survey and use a question of type 'image', we instead host the images on a web server at a URL that is accessible over the internet. I then pull the appropriate image URL from a csv file using pulldata, and concatenate together an HTML IMG tag in a NOTE question to display the web image in the survey at inspection time. For the most part, this worked well until recently. For some reason, when the inspector selects the asset identifier (at which point the image tag should be concatenated together), the image does not display. If they un-select the asset identifier, and then re-select it - the image then appears. I can reproduce this within Survey123 Connect x86 3.7.62 for windows, Survey123 3.6.153 for windows, and Survey123 3.7.57 for Android. I had v 3.5 on android before and it did NOT appear to behave this way - the images rendered consistently. I can share the zip of a survey that will reproduce this issue reliably, but I would need to remove some sensitive information if it is to be shared on geonet where it can be downloaded by all.
... View more
01-09-2020
12:47 PM
|
0
|
1
|
380
|
POST
|
Thanks so much for your help Melinda! I've done some testing and a variation of the process you describe works fine for me. -> Data_template.gdb contains feature datasets and source feature classses, but no network datasets -> Via FME I truncate my source feature classes in Data_template and reload them with fresh data -> Via python I: ----> copy Data_template.gdb to Data_working.gdb ----> use na.CreateNetworkDatasetFromTemplate to create the network in Data_working.gdb from my template ----> use na.BuildNetwork to build the new network It performs quite well, the entire process described above now takes less than 10 minutes.
... View more
07-31-2019
08:05 AM
|
0
|
1
|
1147
|
POST
|
Thank you for the suggestions! I'm thinking I may attempt to just recreate the network dataset using xml templates via script. I did it once and it appears to build fast the first time, so I think your theory about the dirty areas sounds correct. I do have one more question - can DeleteFeatures_management be used to delete a network dataset? If I want to recreate the same dataset from template repeatedly via script, I believe I need to delete the original dataset each time as CreateNetworkDatasetFromTemplate will not overwrite an existing network dataset with the same name as specified in the template. However, I when I try to use DeleteFeatures_management and point it my network dataset in my gdb I get an error 000732.
... View more
07-30-2019
02:51 PM
|
0
|
3
|
1147
|
POST
|
You are correct that my network dataset (and the source feature class) are in file geodatabase on a local drive. My source feature class does indeed have a spatial index so unfortunately that is not the issue. To create the network dataset, in the Catalog pane in ArcMap I right click on the Feature Dataset containing my source feature class, and choose New > Network Dataset. I then follow the wizard to choose the source features, set turns, set elevation, create attributes from evaluators, and set the driving directions name attribute. My plan is to then in a batch process truncate and re-populate the source feature class using FME, and then rebuild the network using ArcPy.
... View more
07-30-2019
12:52 PM
|
0
|
6
|
1147
|
POST
|
Hello I am working on automating a process which imports data from local and regional transit authorities, builds a network dataset, and then publishes a Network Analysis service to our ArcGIS Server to use later to solve routing problems. The process works fine, but the 'build network' step takes quite a long time (8+ hrs) and I was wondering if there are any suggestions of ways I can speed it up. Network dataset info: -Global turns only -No elevation -End point connectivity -Roughly 70000 edge features -Two network attributes added in addition to default Length attribute: one Cost, one Restriction I am using ArcMap 10.7. Building the network takes a long time both via ArcMap GUI as well as via ArcPy. Things I have tried: -changed network attributes from python to vb script -hardcoded cost and restriction values into the underlying feature class and changed the network dataset attributes to simply read those fields rather than running any script to derive them
... View more
07-30-2019
11:31 AM
|
0
|
8
|
1400
|
POST
|
Hello James and Phil We continued testing with the beta of 3.4. Some users continued to have issues with the app running out of memory and crashing. I will be revising the attachments on my original post to include a log file from June which was gathered using 3.4. I notice that 3.5 was released on Google Play last week. Does it contain additional fixes that may help with this 'out of memory' issue?
... View more
07-03-2019
02:17 PM
|
0
|
1
|
936
|
POST
|
A single field user was provided the 3.4 beta and performed testing yesterday. They did not experience the app crashing due to running out of memory. More field testing will be performed today and over the next few days by multiple users and I will be sure to report my results. Phil, I don't suppose you can share any timeline on the official release of 3.4 in the Google Play store? I'm guessing not, but we are left with a decision to make here regarding either using the beta version on a large number of devices (which some folks are nervous about) vs waiting for the official 3.4 release. Thank you for any info you can share.
... View more
05-07-2019
10:45 AM
|
0
|
5
|
936
|
POST
|
I strongly believe we are currently using S123 v 3.3.64 on all Android devices, though I would need to confirm. You are correct that I make somewhat extensive usage of pulldata and I had suspected it was this complexity that could be behind the crashing. We are using an automated nightly process to update those external csv files, and republish the survey via FME Server and Python; they are vital to the workflow. I installed the 3.4 beta on my testing device and have found it more stable and better performing, and that it has reduced failure rate to maybe 1% from the 3% I was seeing before. However, the field staff were always seeing higher failure than I was, and I plan to get the beta apk installed on some of their tablets over the next couple days to see if it resolves, or at least reduces, instances of the application crashing. To help with troubleshooting I installed a lightweight RAM monitor app that displays a screen overlay and if I repeatedly try to start the survey over and over again, the available RAM does start to creep downwards, and then when it gets to around 6% the app crashes, suggesting it is still running out of memory, but the new version seems to better manage memory when using pulldata. I will find out if the field staff are running other apps that may be RAM heavy - keeping Chrome open with many tabs open or something perhaps.
... View more
05-01-2019
11:33 AM
|
1
|
7
|
936
|
POST
|
Hello I have a group of users who are experiencing intermittent crashing (the Android 'Survey123 has stopped working' dialog) when opening a survey. Here are details on the crash: -They are using Samsung Android tablets (exact model varies, I can get more details) -Issue has occurred both in office (on WiFi) and in the field (on LTE connection) -The error only occurs for one survey -The error has been reproduced on multiple android tablet devices, suggesting it is not a single device specific problem -The survey is launched by users clicking an arcgis-survey123:// URL, specifying both the itemID and a value for a single field. -I was once able to reproduce the problem by starting the survey directly from within the Survey123 app and not via URL -They typically click this link from within Collector, but I have tested clicking the link from the AGOL webmap in the Google Chrome android app and it also will occasionally result in a crash. I believe this rules out the transition from Collector app to Survey123 app as the culprit -In my testing I have reproduced the crash on maybe 3% of survey launches. Field staff reports suggest they are seeing higher failure rates however Here are resolutions we have attempted: -Deletion and redownloading of the problematic survey via Survey123 app -In Survey123, going into Settings > Storage > Fix Database -Uninstall and reinstall of Survey123 app via Google Play store The problem may not happen again for a while but it always reoccurs eventually. Here are some things I would rather not do: -factory reset tablets -have to republish the survey Note the large log file involved me repeatedly attempting to reproduce the problem. I have included the whole log because of the information at the beginning on android version, app version etc. The other two logs I have clipped to only include logging from the attempts which actually generated an error. update: removed first and last names of inspectors from xlsx and re-attached esriinfo.zip
... View more
04-30-2019
11:37 AM
|
1
|
28
|
2967
|
POST
|
I have been testing updating itemsets.csv 'behind the scenes' (not by updating external_choices tab) and it appears it updates the choices available in the survey successfully. However, if you update itemsets.csv, the external_choices tab in the xlsx will not update to match the changes to the csv file. Further to that, if you then go and save the xlsx, causing s123 connect to regenerate the web form, itemsets.csv will be regenerated from the contents of the external_choices tab, overwriting your updated csv file. A solution is to download the survey form package, unzip it, overwrite itemsets.csv in the media folder, zip it back up, and then push it back up to AGOL / your portal without triggering a regeneration of the webform which would overwrite your freshly updated itemsets.csv file. This can be done via python, though I've found that documentation on doing something like this is minimal, which leaves a lot of trial and error. Good luck!
... View more
07-05-2018
12:32 PM
|
1
|
0
|
1083
|
POST
|
I found what appears to be the root cause I am guessing you were giving the geopoint a value when you were testing, and so could not reproduce my issue The House Num appears to only not be rendered if the geopoint widget is left to default 'no location' when the survey is submitted. So if I go thru and submit the survey instance and leave the geopoint on it's default 'no location' state, the house num (and all following values in the Location groups) will be 'fake' blank when I open the survey in the outbox. If i submit the survey with the other values all the same, but select a real location on the geopoint widget, the house num ( and all following values) will correctly render Note if I move the house num box to above the geopoint widget, it will correctly render the value when editing the survey regardless of if i left the geopoint at 'no location' at submission time. This glitch only appears to apply to fields within the same 'group' (including within subgroups) as the geopoint [I had tested adding a text field to the end of the survey after all groups and repeats are closed, and it never had this issue. Only fields within grp_loc were affected] , and only fields that appear BELOW the geopoint in the group. For now I will rearrange the text and select_one fields so they are above the geopoint
... View more
06-11-2018
10:31 AM
|
0
|
0
|
374
|
Title | Kudos | Posted |
---|---|---|
1 | 07-05-2018 12:32 PM | |
1 | 04-17-2020 12:21 PM | |
1 | 04-30-2019 11:37 AM | |
1 | 05-01-2019 11:33 AM |
Online Status |
Offline
|
Date Last Visited |
07-07-2023
09:03 PM
|