Skip to main content

Snapping NOT enabled when Enable Snapping is selected

Comments

19 comments

  • Permanently deleted user
    I've noticed the same thing. I think it has something to do with how the viewer now loads the modules as you need them and for some reason fails the first time you load them (same thing happens with some workflows). If you click on "Select Snapping Layers" it should start working again.

     

    That being said, I haven't seen any responses from Latitude on this issue, so I'm wondering where they're at on this because I've seen multiple threads relating to this issue now with no responses from them.
    0
  • Stefan Schweigert

    Hi Bobby and Odiri,

    I haven't been able to reproduce the issue with snapping not being enabled once toggled. It may be that the layers that you are wanting to snap to have not been selected in the 'Select Snapping Layers' section. Also note that the module loading changes did not impact the Snapping feature.

    Thanks, Stefan

    0
  • Permanently deleted user
    Snapping has been a mixed bag for us. Some layers seem to be OK, others not. For example, I can snap to our Road base, but not the Property/Parcels layer. I'm really not sure why there is some inconsistency there. Both layers are presented the same way in the underlying map service, apart from the fact that one is line-based, the other poly. I haven't had a lot of time to dig a bit deeper unfortunately, but just giving some feedback on our experiences so far.
    0
  • Permanently deleted user
    Hey Stefan,

     

    The layers ARE selected for snapping. As soon as I hit the "Select Snapping Layers" which allows you to select your layers, the snapping suddenly works again. I don't check any new boxes or click anything else to change which features allow snapping.
    0
  • Bobby Jo Close
    Stefan,

     

    I am having the same expereince as Odiri. I have 2 layers set to be snappable by default. The halo turns on when I Enable Snapping but snapping does not occur. Snapping is enabled once I click on "Select Snapping Layers" but I don't make any changes. 
    0
  • Bobby Jo Close
    Stefan,

     

    I can send you a link to one of my development viewers so you can see this behavior.

     

    Bobby Jo
    0
  • Stefan Schweigert

    Hi Bobby Jo,

    That would be great; you can email me at: sschweigert@latitudegeo.com

    0
  • Stefan Schweigert
    I'm able to reproduce the issue with your site Bobby; only workaround currently is to disable and enable the snapping for that layer. I'll create an issue with everyone as a stakeholder.
    0
  • Bobby Jo Close
    Stefan,

     

    After upgrading Essentials 4.10.1 and HTML5 2.11.1 I am still experiencing this issue. I have 2 layers set to be snappable by default. The halo turns on when I "Enable Snapping" but snapping does not occur. Snapping is enabled once I click on "Select Snapping Layers". Is there a plan to resolve the problem?

     

    Thanks,

     

    Bobby Jo
    0
  • Ryan Kelley
    We are having this issue, or similar issue, in 4.10.1, HTML5 2.11.1. We have workflows that ActivateSnapping, but no snapping is activated. The exact same workflows work in GE 4.8.2. Once we upgraded, no go. Any update on this Stefan?
    0
  • Permanently deleted user
    FYI, this is still an unresolved bug, being tracked as BUG 21860.  The only workaround listed is mentioned above " disable and enable the snapping for that layer. "

     

    Regards,

     

    Wayne

     

     
    0
  • Permanently deleted user
    Please also add me as stakeholder, I encounter this bug since I upgraded to 4.10.1 & 2.11
    0
  • Richard Diaz
    Wayne,

     

    Please add me as a stakeholder on this issue.

     

    Cheers...Rick
    0
  • Permanently deleted user

    Done.

     

    Regards,

     

     

    Wayne

    0
  • Bobby Jo Close
    Wayne,

     

    Do you know when this BUG will be addressed? In what version?

     

    Thanks!!

     

    Bobby Jo
    0
  • Permanently deleted user

    Hi Bobbi,

     

    It is targeted for 2.12, the next viewer release, but the fix has not been implemented in the code yet.

     

    Regards,

    Wayne

    0
  • Bobby Jo Close
    Thank you!!
    0
  • Permanently deleted user
    +1 for stakeholder notification on this issue
    0
  • Emily Renkema
    Also +1, mine isn't working even after I turn enable/disable on and off
    0

Please sign in to leave a comment.