Zum Hauptinhalt gehen

Search by Parcels ID Working But Doesn't Allow Zoom To

Kommentare

11 Kommentare

  • Permanently deleted user

    Hi Peter,

         Here is what is happening in the sample: the search workflow performs the query inside the workflow (on the server) but does not to include the geometry (for efficiency). The data is returned to the client using the SelectFeatures activity. Once the features are on the client, the viewer will perform another query to retrieve the geometries (since they were not provided). So that you can zoom to them, etc.

         So you may have a few problems with the modifications you have made.

        1) Make sure that the url specified in the query task in the workflow is the same as the layer defined in your site.

        2) Make sure the map server id and layer id are set correctly in the SelectFeatures activity since that is what the viewer will use to perform the query to gets the geometries.

        One of these should solve your issue. Also, you can use fiddler to check the queries that are being submitted (as long as you are running Essentials and the viewer on the same machine, you should see all the requests in Fiddler).

    Cheers,

    Christian.

     

    0
  • Permanently deleted user

    Well I double checked all my layer ids and map service ids... still not working.

    I'll just go through it a little more in-depth.

    Workflow starts up, and I've got a default value in the autocomplete box and fiddler saying something like below is being requested -

    http://<myserver>/ArcGIS/rest/services/General/GeneralFeatures2/MapServer/20/query?returnGeometry=false&spatialRel=esriSpatialRelIntersects&where=LOT_PLAN+Like+'136RP37498%25'&outFields=LOT_PLAN&f=json&

    Which seems all ok. Click the search button and the fiddler says this is called.

    http://<myserver>/ArcGIS/rest/services/General/GeneralFeatures2/MapServer/20/query?returnGeometry=true&spatialRel=esriSpatialRelIntersects&where=OBJECTID+IN+(1519874)&outSR=102100&outFields=OBJECTID&f=json&

    {"displayFieldName":"LOT_PLAN","fieldAliases":{"OBJECTID":"OBJECTID"},"fields":[{"name":"OBJECTID","type":"esriFieldTypeOID","alias":"OBJECTID"}],"features":[{"attributes":{"OBJECTID":1519874}}]}

    /customer/servlet/servlet.FileDownload?file=00P6000000e889VEAQ

    Then I click on the item above and get the below...  Note - Zoom to Feature is greyed out.   Does it matter the layer is not turned on or visible at the scale?   The selected feature appears as (1) on the correct layer.

    /customer/servlet/servlet.FileDownload?file=00P6000000e889aEAA

    0
  • Permanently deleted user

    Peter,

    Are you sure the SHAPE field (or whatever your geometry field is called) is not being excluded in the MXD?  When you view the REST endpoint for your parcels layer, do you see your geometry field listed?

    John

    0
  • Permanently deleted user

    You GOT IT, thanks!

    Something so simple.  I didn't know the geometry field was off.

    0
  • Permanently deleted user

    Hello:

    I am trying to get a search parcels by id workflow, and I am having a problem.

    The workflow seems to be working, it shows the proper results when looking at the debug window.

    However, the results show only the Object ID item from the table of attributes (see 1st screenshot below).. 

    /customer/servlet/servlet.FileDownload?file=00P6000000e88CZEAY

    When I look at the table, the Zoom to Feature and Pan to Feature Options are grayed out.  /customer/servlet/servlet.FileDownload?file=00P6000000e88CeEAI

     

    I have added the shape, shape area, and shape lenght fields; but I still have the problem.

    Can somebody help me?

     

    Thanks,

     

    J.

     

    /customer/servlet/servlet.FileDownload?file=00P6000000e88CjEAI

    0
  • Permanently deleted user

    The ObjectID issue is simple (I think).  You need to change your display field in your MXD to the field you want to display and in geocortex you may need to make sure you change the "Display Name" to the field you want.

    Can't help you on the other one...  in my case I had unticked the geometry field in the mxd and I was able to zoom to.

    Peter

    0
  • Permanently deleted user

    Make that ... I had unticked the geometry field and it wasn't zooming.. ticked it and it was able to zoom.  Pretty obvious in the end.

    0
  • Permanently deleted user

    I am also having both of the above issues. One of my layers will not zoom after selected (I checked the geometry field). I keep getting an error (see pic 1 below). I have made sure everything in my workflow is pointed to the right Map ID and Layer ID.

     I also have another query/search that zooms to the feature, but is labeling the wrong field. Its not the objectID field, but it's still wrong. I can't figure out how to fix this... (See pic 2 below). It should be labeling the Full Address field further down the list.  I have made sure my primary display field is correct and that the label field is set as well.  Does anyone have a solution to this problem? Any help would be greatly appreciated. Thanks!

    Pic 1:

    /customer/servlet/servlet.FileDownload?file=00P6000000e88CtEAI

    Pic 2:

     /customer/servlet/servlet.FileDownload?file=00P6000000e88CyEAI

    0
  • Permanently deleted user

    I got it to work! 

    I followed all the directions below.  None of them seemed to work. 

     

    What worked:

    I ended up deleting the map service (it was running from an MSD); I recreated the service right off the MXD; restarted everything, and that seems to have done the trick.

    Good luck, and thanks you all for your help.

    J.

    0
  • Permanently deleted user

    Could have been a "clearing the cache" problem?

    i.e. Making changes to the mxd without clearing the cache?

    Just a thought.   No matter how many times I fall for it, I sometimes forget the cache.

    0
  • Permanently deleted user

    I agree with Peter... I've got all my searches zooming nicely and they are not mxd's.. they've always been msd. I had an issue yesterday with one of the searches not showing the ID info as set up in the rest manager, but a new 'save site', and then clear browser cache seemed to work.

    cheers

    Gareth

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.