Latest Contributions by SSISC_FieldCrew

Thanks very much @DavidWynne, that did the trick. ... View more

Yes, the values match exactly and the capitalization also. ... View more

Thanks for the prompt reply @DanPatterson. Rather than replace the key "ABUT THE" with the value "Velvet leaf" the code keeps the field values the same. ... View more

I second this. The way the hints are currently set up, they need to be very short if a user wants to be able to read them. If the hint is too long, the rest of the hint is cut off. There is no way to read the rest of the hint. Often times the hints need to be so short (maybe 30 characters or so) that you cannot actually provide sufficient information to be useful as a hint. In this sense, the hints are futile.  In addition, the hints appear in place of the field name and the field name is no longer able to be seen. For example, a field is named "Surveyor" with the hint "Select your name". "Select your name" is what shows up in Collector. You cannot see "Surveyor". It would be preferred if the field name appeared like normal, then when a user selects the field to fill out the information, a section at the top of the drop-down option, or a pop-up, displays the field name along with the hint. It is important to be able to see both at once because, as a user becomes familiar with a form, they should not need to read the hint each time to figure out what field they are looking at.  This feature is a great addition to Collector and it would be much appreciated if this feature was fixed and made useful. Thank you!  ... View more

I second this. The way the hints are currently set up, they need to be very short if a user wants to be able to read them. If the hint is too long, the rest of the hint is cut off. There is no way to read the rest of the hint. Often times the hints need to be so short (maybe 30 characters or so) that you cannot actually provide sufficient information to be useful as a hint. In this sense, the hints are futile.  In addition, the hints appear in place of the field name and the field name is no longer able to be seen. For example, a field is named "Surveyor" with the hint "Select your name". "Select your name" is what shows up in Collector. You cannot see "Surveyor". It would be preferred if the field name appeared like normal, then when a user selects the field to fill out the information, a section at the top of the drop-down option, or a pop-up, displays the field name along with the hint. It is important to be able to see both at once because, as a user becomes familiar with a form, they should not need to read the hint each time to figure out what field they are looking at.  This feature is a great addition to Collector and it would be much appreciated if this feature was fixed and made useful. Thank you!  ... View more

Thank you so much Josh Schwartz‌. I followed the steps to use the python script and it worked perfectly. It was really quick and easy to use as well. Cheers! ... View more

I would also love to have this functionality in AGOL.  ... View more

We would also like this option. If we get a sighting from the public, we will go into Collector and add the sighting information. Our area boundary is over 5000 square kilometers. It's very frustrating when a dispatcher is adding information to the map, zoomed into the correct location, goes to add a data point and get automatically navigated back to where they are sitting at a computer. It would be ideal if the feature was off and then when you wanted to place a point, you could click a "center on me" button that would put the point where you are. ... View more

For our organization, we take a photo at every site. At the end of the field season, we then upload the photos to a provincial database. We have found a few issues with the way Collector manages photos on iOS. 1. Currently, the photos are stored in the geodatabase. It's a bit of a process to get the photos from the geodatabase so that we can save them in a folder on our computers, so that the photos can easily be uploaded to the provincial database.  2. Once the photos have been extracted from the geodatabase they then have really complicated identifiers that we need to deal with in order to figure out what photo belongs to what site. This is such a pain that we have opted to not collect photos using Collector.  A few things that would be very helpful for us include: 1. Collector saving the photos to the iOS Photo Gallery. This is how photos are saved in Android but not in iOS. 2. Having the photo names associated with date/time or even better, allowing the user to set how the name is stored using a combination of the fields. For example, the site ID and the date/time. 3. Geotagged information (GPS location, image direction) ... View more

Thanks for listening to all the feedback ESRI! Very excited for the Aurora project and I would love to be a part of the beta testing! ... View more