AnsweredAssumed Answered

QueryParameters ReturnGeometry Not Honored

Question asked by chad.yoder@nwg on Oct 17, 2017
Latest reply on Oct 19, 2017 by PMaske-esristaff

Like • Show 0 Likes0
Comment • 7

I have a feature service that contains polygons. When I execute a query using QueryFeaturesAsync with QueryParameters that sets the ReturnGeometry = false I get an error: "Error performing query operation".

If I do the same query using the REST API, I get the same error, unless I switch the query to not return geometries.

We tracked this down because only certain queries will cause this issue. We think it has something to do with the shapes (maybe the # of vertices or true curves), but have not nailed it down yet.

The issue though is that even for the queries that work, the return features still have the geometries, although the flag was set the false. This makes me think the flag is not being honored.

Anyone else see this issue?

No one else has this question

Outcomes

PMaske-esristaff

Oct 19, 2017 8:55 AM

Hello Chad,

Two questions: What version on Quartz are you using?

Are you using Manual Cache and using PopulateFromServiceAsync() to populate the data?

--Preeti

Actions

chad.yoder@nwg @ PMaske-esristaff on Oct 19, 2017 9:02 AM

v100.1

Not using PopulateFromServiceAsync(), using QueryFeaturesAsync on the feature table.

I can try that approach and let you know if you'd like.

Actions

PMaske-esristaff

@ chad.yoder@nwg on Oct 19, 2017 9:05 AM

Ya, sure, try that

Actions

chad.yoder@nwg @ PMaske-esristaff on Oct 19, 2017 9:37 AM

Pretti, that worked, and no geometry was returned. I'll just have to code to handle online/offline a bit differently.

I did notice the results returned almost immediately using this approach vs. just calling QueryFeaturesAsync(). Is that expected? Is the the most efficient way to query an online service?

Thanks.

Actions

PMaske-esristaff

@ chad.yoder@nwg on Oct 19, 2017 9:44 AM

>"The issue though is that even for the queries that work, the return features still have the geometries, although the flag was set the false. This makes me think the flag is not being honored."

This should not happen, I will look into it.

>I did notice the results returned almost immediately using this approach vs. just calling QueryFeaturesAsync(). Is that expected? Is the the most efficient way to query an online service?

Well, that also should not happen, the response time should be same. Although with ManualCache, subsequent layer operations will be little faster as there is no http traffic to fetch the more data.

Is it possible to share the service end point? Also share the code snippet that didn't work. I will give a closer look and let you know.

Actions

chad.yoder@nwg @ PMaske-esristaff on Oct 19, 2017 9:57 AM

Can I email you directly with this information?

Actions

PMaske-esristaff

@ chad.yoder@nwg on Oct 19, 2017 10:10 AM

Sure, email me at pmaske@esri.com

Actions

7 Replies

PMaske-esristaff Oct 19, 2017 8:55 AM
Mark Correct
Correct Answer
Hello Chad,

Two questions: What version on Quartz are you using?
Are you using Manual Cache and using PopulateFromServiceAsync() to populate the data?

--Preeti
Like • Show 0 Likes0
Actions
- chad.yoder@nwg @ PMaske-esristaff on Oct 19, 2017 9:02 AM
  Mark Correct
  Correct Answer
  v100.1
  
  Not using PopulateFromServiceAsync(), using QueryFeaturesAsync on the feature table.
  
  I can try that approach and let you know if you'd like.
  Like • Show 0 Likes0
  Actions
  - PMaske-esristaff @ chad.yoder@nwg on Oct 19, 2017 9:05 AM
    Mark Correct
    Correct Answer
    Ya, sure, try that
    Like • Show 0 Likes0
    Actions
    - chad.yoder@nwg @ PMaske-esristaff on Oct 19, 2017 9:37 AM
      Mark Correct
      Correct Answer
      Pretti, that worked, and no geometry was returned. I'll just have to code to handle online/offline a bit differently.
      
      I did notice the results returned almost immediately using this approach vs. just calling QueryFeaturesAsync(). Is that expected? Is the the most efficient way to query an online service?
      
      Thanks.
      Like • Show 0 Likes0
      Actions
      - PMaske-esristaff @ chad.yoder@nwg on Oct 19, 2017 9:44 AM
        Mark Correct
        Correct Answer
        >"The issue though is that even for the queries that work, the return features still have the geometries, although the flag was set the false. This makes me think the flag is not being honored."
        
        This should not happen, I will look into it.
        
        >I did notice the results returned almost immediately using this approach vs. just calling QueryFeaturesAsync(). Is that expected? Is the the most efficient way to query an online service?
        
        Well, that also should not happen, the response time should be same. Although with ManualCache, subsequent layer operations will be little faster as there is no http traffic to fetch the more data.
        
        Is it possible to share the service end point? Also share the code snippet that didn't work. I will give a closer look and let you know.
        Like • Show 0 Likes0
        Actions
        chad.yoder@nwg @ PMaske-esristaff on Oct 19, 2017 9:57 AM
        Mark Correct
        Correct Answer
        Can I email you directly with this information?
        Like • Show 0 Likes0
        Actions
        PMaske-esristaff @ chad.yoder@nwg on Oct 19, 2017 10:10 AM
        Mark Correct
        Correct Answer
        Sure, email me at pmaske@esri.com
        Like • Show 0 Likes0
        Actions

GeoNet

The Esri Community

QueryParameters ReturnGeometry Not Honored

Outcomes

Related Content

Recommended Content

Incoming Links