POST
|
I also have the same problem. Why I hesitate to adopt the new Collector. Seems kaputt and half baked.
... View more
07-04-2021
06:14 AM
|
0
|
2
|
3120
|
POST
|
Hello. I'm experiencing a bizarre issue with data pushed into an existing AGOL feature service from Survey123. I have a survey form that feeds field data into an extant feature service layer in AGOL (in this case, field tracts). The new data is clearly present in the attribute table, but they cannot be visualized using either a filter or regular layer properties. For instance in the screenshot included, I tested for content in the field COLL21 (if 1, we collected the tract). Even though the test entry shows in the properties legend and in the attribute table, it will not be visualized on the map, as if it does not exist. Likewise, if I filter for that value under layer properties, nothing shows. On the other hand, any data present in the fields as part of the original feature service creation can be visualized and filtered fine. I am hoping someone who has also worked in AGOL/Survey123 integration has a solution... Many thanks for any tips UPDATE: I think this is partly caused by the fact that Survey123 was pushing data into a duplicate NEW record (unassociated with the relevant geometry/polygon) rather than passing the data into the existing one. How to pass the form data properly to the existing feature service fields? All the fields between the feature service and the form match (in both title and type) and under settings I have specified the location of the feature service using the format below (evidently this part works as the data does get pushed in the service as seen in the screenshot below). Do I need some formula under settings to pass the contents of a field into its equivalent of the feature service? So ideally I'd like to put the Survey123 data into existing records/polygon features of an existing feature service. https://www.arcgis.com/sharing/rest/content/items/layerID
... View more
07-04-2021
02:04 AM
|
0
|
1
|
1057
|
POST
|
Hi all. Just came back from fieldwork having used survey123 successfully. I did have this one issue I couldn't figure out. The project was situated in Greece but the form entries kept getting a wrong date and time (the preceding day, presumably default EST). The tablets where Survey123 was operating from had the correct (local, i.e. Greek timezone) and were offline most of the time (wifi enabled only). The creationdate field correctly captured the correct date. But the field where a date was entered by collectors (using the correct field type in XLS) systematically outputted a day later. Can exclude human error as the error was systematic and across board. I noticed the same issue on my 5g connected cell where I downloaded the same form so it's not specific to the tablets or the wifi or whatever. I was trying to see if Survey123 Connect has a setting somewhere for these forms for timezone that potentially overrides device and network settings. None to be found. Any clues why this was happening? It meant tons of manual edits and QC daily. Thanks
... View more
08-12-2019
08:10 AM
|
0
|
2
|
565
|
POST
|
Many thanks for your quick reply. So I specified 0 as shapefile (since I want the lines inside the polygons of that shapefile; also tried feature layer), 1 also as a feature class, 3 and 4 as linear units. 10 m interval, 0 buffer. I then created a new layer to receive the polylines (since the tool doesn't seem to give the option to create a new layer but prompts choosing an existing one). I also made sure the output matches my coordinate system. The script runs and runs forever and I end up stopping it. Thoughts?
... View more
07-04-2019
01:11 PM
|
0
|
0
|
2530
|
POST
|
Hi I am trying to run this tool but haven't experimented with this before. Could you please explain how you get there to see the UI shown in the original page referenced above? I have created a new toolbox and added the script from a text file. Then what? I see the window below and am unsure how to set the parameters I need. I have a feature layer with polygons loaded I want filled with wells at 5 m intervals. Edge buffer isn't needed. Thanks.
... View more
07-04-2019
08:46 AM
|
0
|
3
|
2530
|
POST
|
Also I dont see the option to update all items or own items in the creation interface
... View more
06-18-2019
03:23 PM
|
0
|
1
|
4447
|
POST
|
I am having the same issue as admin and creator of my group. "To do that we require a more intentional sharing workflow that is done from the item owner’s content page" is irrelevant for the issue raised since the problem occurs even for item owners. Why isn't the admin and owner the material not able to see a group under access and update but able to see it through access? And yes when it was created members were given the ability to add content. Very odd.
... View more
06-18-2019
03:20 PM
|
1
|
2
|
5331
|
POST
|
FYI I have successfully applied callback using this code in the custom popup of the layer. &callback=arcgis-collector://?itemID=XXXXX (where itemID is the name of the specific webmap you're using). I have added this to a list of other parameters that pass extant data in the feature service I'm using into the associated survey form and it works fine.
... View more
06-17-2019
08:34 AM
|
2
|
4
|
766
|
POST
|
Also, once in the survey there seems to be no easy way of going back to Collector unless one hits the back button repeatedly. But I have now also built a call back code in the popup to speed that up a bit. Still not ideal if you're dealing with hundreds of polygon edits/survey adds in a day.
... View more
06-17-2019
07:44 AM
|
1
|
4
|
4870
|
POST
|
Of course, I have uploaded the survey to an existing service. But that's not my problem -the issue was how to pass data already in some fields into the survey form to avoid redundant typing, and how to integrate the survey with Collector which shows you the specific polygons that are being added with attribute data. Very clumsy solution, but it works. ESRI needs to streamline this.
... View more
06-17-2019
07:42 AM
|
1
|
5
|
4870
|
POST
|
Hi all. I am having a similar issue. I created a survey using an existing feature service in AGOL through Survey123 Connect. The feature service has polygons (agricultural tracts) and fields that describe various attributes. That process went fine and the survey looks great. Using these instructions (Uhttps://community.esri.com/groups/survey123/blog/2016/07/30/understanding-survey123s-custom-url-scheme I added a custom attribute display url to the layer in AGOL to call up the survey form in Collector. Because I want the survey form to have the area and tract ID prepopulated I added the relevant fields too: arcgis-survey123://?itemID=69c04a817b534bddb2eeef3d0f7c2832&field:Tract area={Area__m2_}&field:Tract ID={Code} Basically I'd like to see this behavior: user goes to Collector, clicks on a polygon in the tract layer, and the link to the survey opens up with the name of that specific tract showing in the tract ID field of the survey and its area prepopulated. What am I doing wrong? While the survey is correctly linked in the Collector app when I edit the layer, the fields do not prepopulate. I did a test data entry and the survey simply creates a new entry. I have enabled inbox btw. Thanks! UPDATE: okay, figured it out. So for those poor bastards who are doing this from scratch (like me), if you have an existing AGOL layer you want to connect to a new survey, here are the steps: 1. Make sure the layer is properly shared with the same group as the survey. Make sure your fields are finalized before the next step. Make sure the layer has sync and full edit abilities selected (and attachments enabled if you plan to have an attachment field in the survey). (If you enable the attachments first then do allow the edit/sync you may have to disable the attachments and enable again for some reason). 2. Create the survey (best to do this in Survey123 Connect). Make sure the survey uses exactly the same names and types of ESRI data as the layer on AGOL (check the schema in Survey123 Connect to be sure). 3. Publish the survey to the existing feature layer. This can be updated after you publish it from Survey123 Connect (make the needed changes and republish to the same layer). 4. Next, go to AGOL and open the map that contains the feature layer. From Content, highlight the layer in question and select Configure popups. 5. Select Custom Attribute Display. Click on the green Configure button and select the link icon. 6. Go to survey123.arcgis.com and select the by now published survey. Select Collaborate in the green ribbon, then from Link below select Open the survey directly in the app. Click that link next to the sentence (Learn more about this option) and copy survey link e.g. arcgis-survey123://?itemID=69c04a817b534bddb2eeef3d0f7c2832 7. Go back to AGOL and the Custom Attribute Display interface. In the URL field add the link above. 8. If you want some fields prepopulated from the AGOL layer, add the relevant fields with ampersands right after the survey link. E.g. arcgis-survey123://?itemID=69c04a817b534bddb2eeef3d0f7c2832&field:Tracts={Tracts}&field:Area={Area}&field:Code={Code} Note that in the formula above the field names without brackets must correspond exactly (including any capitalization) with the survey field names where the information is to be autofilled and the field names with brackets must correspond exactly with the fields of the AGOL layer from where the autocomplete data is to be pulled. I still can't stand how complicated all of this needs to be. ESRI, come on! This is key functionality, it shouldn't be this obscure to figure out. How about some better documentation? How about a push option to connect to an AGOL layer straight from the Survey123 app? Been a long, long day.
... View more
06-08-2019
09:31 PM
|
5
|
1
|
4870
|
POST
|
Yes, this worked me for in the end. HOWEVER, in order to even see the option to post a shp zip as hosted service on AGOL one must have been granted publisher or admin status by an organization. I struggled with crazy-making app behavior for a whole day before I realized this (this will also unlock all sorts of analytical functionality on the map itself; plus you can make a map downloadable). Once turned into an admin, I could see this option. Here is the right workflow to do this: 1. I can't emphasize enough you need to become a publisher or admin in the organization. User will not do. See: Publish hosted feature layers—ArcGIS Online Help | ArcGIS 2. Create a new web map in My Content. Don't add anything to this yet. 3. Post the zipfile(s) containing the shapefile files as admin in My Content. 4. In My Content, edit each service file so that they are editable. 5. Go to the web map and add the now editable layers. Important note: I found out Collector will not fetch a web map if only some of the layers are editable -even if one isn't, the map won't show. This is why ALL layer components added must be editable. This is crucial but nowhere disclosed. 6. Go back to My Content, select the web map and the layers and share them with a group, if appropriate. You need to do this in My Content because only there (as opposed to individual layer or map sharing) is there the option to specify access and edit capabilities for participants (as opposed to just access). Note: sharing with a group implies you have already created that group and invited members prior. Note the following doesn't apply to AGOL. Publishing feature services—Documentation | ArcGIS for Server What's weird though, for 10 days before I was forced to troubleshoot this (my maps stopped showing in Collector suddenly), I had been able to post shapefiles normally (i.e. not as hosted services but as simple uploads) with user privileges and these showed in Collector fine.
... View more
06-11-2016
02:40 AM
|
2
|
0
|
1104
|
Title | Kudos | Posted |
---|---|---|
1 | 06-17-2019 07:44 AM | |
1 | 06-17-2019 07:42 AM | |
5 | 06-08-2019 09:31 PM | |
2 | 06-11-2016 02:40 AM | |
1 | 06-18-2019 03:20 PM |
Online Status |
Offline
|
Date Last Visited |
06-20-2023
04:55 PM
|