Improve the feature collection by supporting snapping to existing features.
Hi Scott, do you have an idea about the release date?
Hi Scott Prindle,
More than a year since the last time I asked, so again: Do you have a timeline for this? There is so much more "post-processing" necessary when there is no snapping...
I apologize about the delay in my response. I can understand how this is important functionality, and the added steps of post-processing are not ideal. Snapping is on the roadmap to be included in a future release of the next generation of Collector (Aurora), but there is no firm date yet.
We would like to hear your feedback as Collector (Aurora) moves into beta and final release. If you haven't already, please email firstname.lastname@example.org to get access to the beta when it is released, and to get updated timelines on new functionality.
I am pretty sure that this thread answers your question about feedback. Snapping needs to be moved up as a high priority.
I agree, large user base wants it.
I'm testing Aurora but I'm not seeing any snapping capabilities. Is snapping going to be added to Aurora later or not at all?
Same here Scott.
Paragould Light Water and Cable
Sounds like it's somewhere on the list, but not particularly near the top. There are a couple of snapping threads over at https://earlyadopter.esri.com/ in the Aurora forum.
Well, it's been two years since the first suggestion. We saw this immediately upon using collector also two years ago. Come on ESRI. This is a no brainer where you are collecting geometric networks with utilities. Ours is stormdrains. and as someone posted above, a separate workflow has to be developed for Snapping routines to connect line features to point features
It really needs snapping. Big time.
....and still we wait....
Unfortunately without snapping mode the Organizations can actually choose another options, outside of ArcGIS ecossystem.
Please implement snapping for all feature types. Not having snapping is introducing more errors in our data collection projects, especially in our Sign and Pole Inventory where the workflow with Attribute Assistant depends on (near) identical geometries.
For the workflow mentioned above... if your thinking I can just do the "copy feature, different feature, same location functionality" in Collector... your wrong! Turns out, if you feature class participates in a Relationship class, that functionality is disabled in Collector. Eg... Our Sign feature class and Pole feature class each have a related table that holds "Log entries" for qualitative check ups of those physical features. So when collectors are adding new inventory (e.g. a new sign and new pole at the same location), we have a great deal of error with our workflow that must be corrected in the "back office" since field collectors can't achieve the same exact geometry when adding to different points in Collector.
If your reading this idea and vote for snapping, and you also have noticed and have been pained by the functionality I described above, please also vote for this idea as well: Collector App: Allow "Copy Feature" for features with relationships
snapping! snapping! snapping! snapping!
Would like to snap a new line feature to the end of one I just created. Very frustrating.
Surely this is vital. We desperately need snapping in collector. Come on ESRI
WOW! It still isn't done and the user conference is upon us again.
SNAP to IT ESRI !!!!
I'm looking so forward to writing auto snapping parameters to run another process just to snap together all the THOUSANDS of features our field crews have entered.
MOVE THIS UP the ABSOLUTE NECESSITY list
With the work flows we are implementing, this would be a great capability. As our field crews are now adding new water components using GPS/Collector, it would save valuable time in the review of data for integrity prior to posting to the parent geodatabase. Please make this happen!
Wondering if anyone attending the recent Esri User Conference heard anything from the developers regarding implementing snapping in Collector?
We all are waiting for this to happen!
Come on ESRI! Snap to it!
Snap! Snap! Snap!
yes, because putting a valve on an existing line with a smartphone is never going to be accurate.... requires users to go back in the office and use the desktop to finish it up. should be an easy implementation.
Creating topologically correct data is one of the most basic requirements of GIS! It really surprises me we have to fight for it so hard! Collector would be an amazing field data collector, if it allowed the creation of proper spatial data!
I agree Edith. We have been screaming this from the rooftops for almost three years now! Very frustrating.
My comment from another thread but I wanted to add my 2 cents here because this feature should be implimented.
I am surprised to hear that the snapping functionality would actually be apart of the backlog. I work for a gas utility company in Ohio and we're currently building our enterprise system to utilize the collector app. The biggest flaw for the collector app is the inability to allow field workers to snap features for mainlines and components out in the field. The snapping functionality would be a great asset especially when using the ESRI Utility and Pipeline Data Model by Tom Dewitte.
So what is more important than snapping in Collector right now? Z value? Vector tiles? Come on ESRI, those are "nice to haves", snapping is real basic editing functionality and collector is an editing tool last I checked. To give this some perspective just ask yourself: How would the value of ArcGIS desktop be affected if snapping was removed? Now if you apply that same line of thought to Collector you'll see why this is so important.
What's the hold up??? Esri, we would appreciate a reply on the status and implementation as soon as possible.
Snapping would be a great tool to have with the collector app since most major utilities spend thousands of dollars for an enterprise system. The Collector app isn't perfect but it's a great tool to have. I just wish Esri would invest some money to fix and improve existing platforms rather than creating new stuff. Even the new platforms miss the important tools we rely on everyday.
Agreed. When you spend all your development time spinning up new things, when will the bugs and missing functionality of existing products be addressed? Short answer - They won't.
I get the departure from ArcGIS Desktop development. They are focusing on Pro, which is in really, really bad shape at this point. Someone there should make some better decisions about where the development resources go. Survey 123? Nope. Totally redundant. Port the smart forms to Collector and cut 123. Storymaps? Cute. Doesn't work very well. Buggy configuration. Cut it. Add a bunch of analytical garbage to AGOL that probably isn't going to get used much? Nope.... I could go on for days. From a customer perspective, I'd rather have one or two apps that work well than 50 half-baked unstable pieces of junk that seldom get any meaningful improvements and just kind of hang around on Github, waiting for the next half-baked app to replace them. ESRI development is either off it's ADD meds or someone decided to put marketers in charge of making development decisions.
And we wait.....and wait..... and wait.....
Supposedly there is a windows 10 version of collector app that supports it in BETA????
Probably the original programmers are gone and they have to start from scratch. When you think of the enhancements to that platform over the last 4 years they have been very minimal.
I heard they go through intern programmers at ESRI like toilet paper. But I agree, some senior level manager needs to take this by the horn and GET IT DONE!!
They were talking about the intense need for this last year at the Water Utility conference in Florida in February, one year ago. We have way more mobile users accessing our county field maps this year than last and we still don't have a decent tool for this on iOS. What gives? You guys can get a program ready for an iPAD Pro (We have a new one of them too, but won't function for snapping.....
Still waiting on Snapping. Are there any updates on this? It's frustrating that ArcPad has this functionality, but Collector does not.
The short answer is never. I'm in the beta for the Aurora Project and I don't believe it has snapping capabilities. They seem to have more focus on revising the user interface than anything else for the past 4+ years lol
I guess everything has been said already. As landscape architect, Collector seems to be a decent tool to map points, e.g. for a tree survey. In contrast, it is almost impossible to create a correct topology for an area map without snapping. The snapping feature is needed immediately!
is this going to be implemented in Aurora release?
You should see the stupid stuff they are working on. No snapping..but you can login with facebook. SMH.
Nothing meaningful to add to several miles of on-point comments but I just have one question. Who on earth are the 4 people that voted down on this???
I myself voted this idea up, but to play devils advocate what if this new functionality puts a performance hit on the Collector app because there is more activity behind the scenes that needs to occur to achieve this functionality?
Hasn't there been snapping on ArcPad for like twenty years or something?
And the hardware arcpad ran on has probably 10% of the processing power of an iOS or android device so I don't think the resource issue would be a problem you also can snap with the js api so I don't see why this a huge problem.
I'm migrating an ArcPad app that has used snapping for close to 15 years. Now I find that Collector doesn't support snapping yet. I love how ESRI adds new features to products without finishing the core product first. 3D is cool and all, but we need to do our core work too.
ArcGIS Pro seems to be in the same boat, the core product is still not complete. Lookup the idea for graphics and free text in Pro. The ideas is similar to this one, "Under consideration" with no movement.
Scott Prindle Where is snapping on the roadmap? Any ideas on when snapping will be available? I'm hoping for an early Christmas present in Aurora, hint hint.
Dear Santa, all I want for Christmas is the ArcGIS Collector app with snapping. Wait, I want graphics and free text in Pro too.
Would be very useful for vegetation/habitat mapping in the field - negates the need for data cleansing afterwards.
we need this functionality for snapping lines to points in our utility systems
"Under Consideration" for 5 years. I want to make good field use products for my organization but am severely limited when I don't have the tools to do so.
I'm almost afraid to banter about the snapping anymore for fear they'll add it and then start charging for the app.
Since I have been following this thread since it's inception, and have used ArcPad in the past (even as early as 1999-2001) to accomplish what we have been asking for these past 6 years, I thought this may be helpful.
After having used the NEW collector app on iOS for the past month or so, I can say that the move to the new app does provide some great functionality and efficiency including the following: SEEING LABELS! and "SNAPPING" (of a sort.)
The labels are so nice! We have been collecting Storm Drain features for the last 5 years with collector and now being able to see some labels on our structures (indicating which ones need certain attributes added) immediately has added productivity to our workflow, as we don't have to click on every feature to see if that one has a particular attribute we desire to be present and have our field crews enter.
In regards to the snapping....the new workflow is nice and very different from the old in a way, but I feel you can get used to it in a few weeks.
Where-as the OLD Classic workflow, if I were adding a feature we would do the following:
The NEW Collector workflow uses a different logic flow that makes sure that the endpoints of lines match the structure points or match the previous structure vertex.
SO the workflow is different but you can achieve “SNAPPING” equivalents in the field with your field workers, once they adjust slightly their workflow.
This will save us the hours in the office that may be needed to accurately snap the correct features to the correct line features, etc in our current Master Maps. (ONE NOTE: our system is not yet in a Geometric Network/Utility network so these snapping features have been critical to the massive preparation needed to move our county networks to a Utility Network design, hopefully paving the way for a complete traceable drainage network in our County for the pathways to the Potomac & Patuxent Rivers and the Chesapeake Bay -our ultimate discharge point
Good info, Steve. Thanks for that. ESRI, you could've added snapping to Collector in less time than it took for Steve to type up this workaround.
I'm coming from Collector Beta for Android, here is my proposed workflow:
1. Create points in the usual fashion in collector.
2. When creating a line or polygon, add a button below "Add Point" which says something like "Use Existing Point."
3. Let the user then click an existing point, and use this point geometry for the vertex.
Please take a look at this blog for a status update,
Collector for ArcGIS (iOS) Updated
Hope this helps,
FYI: snapping is now available in Collector for ArcGIS (iOS), checkout the new blog,
What’s New in Collector for ArcGIS (January 2020)
Well done to all involved! This is an absolute game changer for us! Thank you!!!
As I'm trying to apply Collector for a Linear Referencing and Dynamic Segmentation project, I'm understanding why all the tutorial videos on the ESRI training website include commentaries from conference goers complaining about iOS having more functionality than Android. I see nothing about Snapping being available for Android, including in the most recent release from Jeff Shaner as of April 2020. What's New In Collector (April 2020)
Reading through 6 years of comments while trying to troubleshoot my project implementation, and hearing ESRI proclaim that it will "keep Android releases up with iOS and never release them out of sync again" in their conference training courses, and clearly doing the opposite, is leading me to believe that Collector is not a reliable platform for advanced data collection techniques.
I'm sorry that our lack of parity is so frustrating. Please know that it is not intentional that these platforms are out of sync. Our goal is to get to that point, but it is proving a very challenging task for us to achieve with a flagship product as advanced as Collector. I am sorry for false expectations that I and others may have set at conference events. We tend to get over-optimistic in our goals and timelines and that ends up in a lost of trust and frustration.
What we have found is that, when building native apps, Android is proving much more difficult than iOS to build for. Collector (Aurora) was a rewrite of Collector. It's a new user experience built on top of a new framework and it is our flagship, most advanced data collection app. Rebuilding an app that does all that Collector can do takes time and for long term projects its easy for the gap in time to grow.
The iOS version finished its rebuild well in advance of Android and we had to make a tough decision - should we continue building new functionality into the product that people are asking us for or do we repurpose those developers to writing Android apps. Well we did both. Looking at the adoption numbers for iOS and Android we felt we needed to continue to push ahead with iOS as well. Unfortunately this has added to the lack of parity.
The Collector (Aurora) Android release was a hard fought milestone for Collector and we are working toward closing the parity gap with the Classic version first before we tackle snapping along with a number of additional missing features. We are close to finishing that release but it too will not have snapping.
We are providing a list of functionality where we are not at parity between the two platforms to help mitigate the trial and error aspect as well:
What's new—Collector for ArcGIS | Documentation
Hopefully we can continue to earn your support and I apologize for the frustrations you are facing.
Retrieving data ...