Just plain weird
I have two polygon layers in a map service. I use Query Tasks with Return Geometry=True , and Select Features into a named collection. I then DisplayResultsTable for the named collection.
One of the layers works as expected - you click a row in the table and the map centers and zooms to the selected feature. For the other layer, in the same Results Table , the map does not recognize the selected feature. I can click a feature in the map and get a map tip, but the Results Table doesn't seem to have the geometry. The two layers look identical in the database (i.e. SRID, Geometry Type, etc.).
I've recreated the service, recreated the data on a different database and recreated the service, created a completely new service with just the one layer. Nothing I do seems to make the features in this one layer selectable from the Results Table .
Has anyone else experienced this issue? Can anyone suggest something else I can try to get the features in the layer to work like other features in the Results Table ?
This is just plain weird.
-
Sean
All you have done seem to be correct.
This is what I would like to investigate.
1) configure [REST]/web.config to set the proxy so that your fiddler can catch the server side (Query Task) for which you can find from http://support.geocortex.com/configure-essentials-to-use-a-proxy-server
2) open fiddler to test your workflow to check if your query task really returns the Geometry in the output.
Or simply use your AGS mapser vice - Layer - Query REST endpoint to check your query returns Geometry or not first.
If the query task does not return Geometry (I am sure it does not contain geometry) since you wrote that Identify on clicking map does not zoom to the feature), please open your .mxd to see that you may UNCHECK on Shape of the layer which does not return Geometry.
I saw it few times for few other projects.
Munhwan
0 -
AHA! Mystery Solved.
It was Colonel Mustard, in the Library, with an unchecked SHAPE column in the mxd!
Thanks, Munwhan!
0
Please sign in to leave a comment.
Comments
2 comments