Create Feature speed of input/clicking

Permanently deleted user

11 April 2017 05:34

Hi there,

 

I've been tinkering with the 'Create Feature' Edit tool  in the HTML5 viewer (2.6.x) and it seems to be extremely slow when compared to the equivalent function in the silverlight viewer (GVS). 

 

We have a large number of editors around the State that need responsive editing tools and unfortunately this tool is a massive regression and it's losing confidence before it's even out the door!!

 

I've had a play with other Esri based applications that use the JS API, and they too are very slow when compared to the GVS, so I gather it may not be a Geocortex related issue???

 

If this is the case, is there anything we can do to help speed up the editing experience? Esri Web AppBuilder has a Freehand drawing tool in it's editing suite which is not a bad option - not ideal, but at least it's quicker. There is also the Auto-complete tool which could help with finishing off edits but I assume there are no plans for Latitude to include these tool options in any upcoming release from what I'm seeing in the Road Ahead webinars.

 

Given this, can these two tools be written into the Geocortex UI a custom tools??

 

any help or ideas appreciated

 

cheers

 

Gareth

0

• 

  Permanently deleted user

  18 April 2017 01:01

  We've had our local distributor support guys look into this also, and they've come back with some interesting results.. They've measured the requests to the server for both the GVS and the GVH for the same basic edit shape

   

  Hi Gareth,

   

  I did a check with a simple four sided polygon and got the attached result.

   

  In summary…

   

  Viewer Size Time Requests

   

  Silverlight 234 0.3 2

   

  HTML5 3962 7.2 84

   

  So there does seem to be a big difference in Size Time and Number of Requests.

   

  I will raise this finding with the senior support team for progression or comment.

   

  Thanks for bringing this to our attention and we will do all we can to get a result for you.

   

  Is anyone else experiencing this behaviour with editing in the HTML5 client?

   

  cheers

   

  GF

   

   

  0
• 

  Permanently deleted user

  18 April 2017 21:51

  Hi Gareth,

   

  I believe you are seeing the results of WCAG requests, the accessibility option for the HTML5 viewer.  When you click on the map the WCAG option will want to announce the location and it will do a query to obtain data.  Normally the query should be very quick and you wouldn't notice a delay.  If the query is slow, due to the server responding slowly, you may notice a slow response.  You can confirm this theory by disabling WCAG in Essentials Manager, on the Accessibility page when editing the viewer.

   

  To look into this issue further I would obtain one of the queries that the viewer is sending out and run the same query in a browser window, independent of the viewer.  The response should be less than a second.  If you are seeing longer delays I would investigate as to why the ArcGIS server response time is slow.

   

  Regards,

   

  Wayne Richard

   

  Latitude Geographics Group Ltd.

   

  Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

   

  Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com 

   

  Developers of Geocortex web-based mapping software | www.geocortex.com

   

  An Esri Platinum Business Partner

   

   

  0
• 

  Permanently deleted user

  18 April 2017 23:51

  Wayne,

   

  Thanks for replying but I've disabled the WCAG and it makes no difference. It's not really to do with requests travelling back and forth from what I can gather. It's more to do with the speed of the browser accepting the clicking of a new vertice.

   

  You can simply test this by adding in a new feature really slowly, one click every second, and in this case there are no requests being sent. If you try to click too quickly - all hell breaks loose and you get a bunch of requests being sent.

   

  It should be easy enouh to replicate this behaviour (I hope). Our local dstributors have on their own site which is positive I guess :)

   

  They've escalated it to you guys for comment.

   

  thanks again

   

  GF

  0
• 

  Permanently deleted user

  25 April 2017 22:34

  Hi Gareth,

   

  I see what you mean about the fast clicking, in my tests I also only experienced multiple requests when fast clicking.  I also noticed the requests were due to a very slight map pan.  When drawing points for a polygon it's possible to click, hold and drag the map to change the extent.  I believe the requests you and I are seeing are due to the slight map pan when clicking too fast.  If I click fast but carefully do not hold down the mouse button too long, I do not see any panning nor any requests.  The pan was very very slight.

   

  As I said previously, it sounds like your queries were taking too long as well, making this behaviour appear to be much worse.

   

  Regards,

   

  Wayne

  0

Du måste logga in om du vill lämna en kommentar.