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 email@example.com 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.....
Retrieving data ...