Skip to main content

Identify Feature Layer goes straight to result details.

Comments

9 comments

  • Permanently deleted user
    I have a similar issue with KML files hosted in Amazon. I lodged a service request to the Australian business partner, and they came to a conclusion that it's a bug. Then they escalated it to Latitude Geographic (it was 2018). I am not sure if it has been addressed in the latest version or not as I haven't upgraded my Geocortex since. However, I still have the issue in my Geocortex 4.8.2.24 and HTML5 2.9.1 versions. 
    0
  • Stefan Schweigert

    Hi Erik and Hery,

    Erik: I haven't been able to reproduce this behaviour when using both AGOL-hosted feature layers and map service layers with GVH 4.13.1. If you are able to provide a testing site for this, that would be very useful.

    Hery: I'm not able to see a filed issue that matches your description in our backlog; are you able to provide a KML file or link for testing? I would be able to check if this particular issue was fixed since then.

     

     

    Thanks, Stefan
    0
  • Erik Engstrom
    Hi Stefan,

     

    Here is one of our sites experiencing this isse:

     

    https://anrmaps.vermont.gov/websites/WetlandProjects/default.html

     

     

    Zoom to an appropriate zoom level and perform an identification on any of the mapped polygon areas in the map. When you identify, you'll notice that the results go straight to the details for the parcel polygon that was identified, and not the list of grouped results. For new(er) users, this is a little misleading, because it's not entirely evident that other features were found at that locations.
    0
  • Erik Engstrom
    Note that the Parcels are the hosted feature class in AGO. The other layers are from map services in ArcGIS Server.
    0
  • Stefan Schweigert

    Hi Erik,

    What is happening is that since the first results appear quickly and results from other layers take much longer, the viewer opens the results list from the first layer as a means to avoid having to click on the layer when not necessary, but in this case it is not desirable. There isn't currently a way to change the speed at which the state of results is checked, but a possible workaround would be to update the identify command in configuration to return back to the previous view. Please add this functionality to the Ideas section.

     

     

    Thanks, Stefan
    0
  • Permanently deleted user
    Hi Stefan,

     

    Here's an example of the KML hosted in Amazon:

     

    https://s3-ap-southeast-2.amazonaws.com/transport.wa/Tide_Packet/TideStations.kml

     

     
    0
  • Stefan Schweigert

    Hi Hery,

    I'm seeing that KML load correctly from 2.11.2 and newer versions. I can't track down a specific code change that might have fixed this but it does appear to load and be identifiable from that point onwards.

    Thanks, Stefan

    0
  • Permanently deleted user
    Hi Stefan

     

    The issue I am having is not that it doesn't load correctly nor that it can't be identified. Similar to the original post from Erik, the issue I am having is that if I turn on other layers and select an area, the result will be defaulted to the KML even if the KML is not turned on. I have to return back to the Results List in order to see if other layers are also identified.
    0
  • Stefan Schweigert

    Hi Hery,

    The KML loads very quickly for me, so it appears you are seeing the same behaviour as I mentioned previously.

     

     

    Thanks, Stefan
    0

Please sign in to leave a comment.