topic Re: Query Problems when using query.geometry (Stumped). in ArcGIS API for Flex Questions

Query Problems when using query.geometry (Stumped).

Anonymous User — Tue, 26 Apr 2011 12:46:28 GMT

Original User: cschafer5

Hi,

I am wanting to run a Query that only displays the results within a specified polygon. I am doing this using query.geometry. I am getting the results I am looking for from most of my URLs and some return an error back to me.

I have attached pictures to show the problem.

The two pictures with arrows shows what I want to happen. In the first picture I get the hit the cap of 500 and on the second picture I click my checkbox to add the WV polygon to the query.geometry and get results only within the state.

The other two pictures show what happens with some URLs. The one not bound to the state gives me the results I expect. The second, when bound to the state using query.geometry, returns an HTTP error.

I can't figure this one out. Is there a reason I would get an error when the only additional code between the two is the added geometry?

Here are the two URLs used in the example:
1 (works):
http://publicsafetytemplates.esri.com/ArcGIS/rest/services/EMCOP/PublicSafetyFeedSample/MapServer/0

2(Gives me an Error):
http://rmgsc.cr.usgs.gov/ArcGIS/rest/services/nhss_usdata/MapServer/0

Re: Query Problems when using query.geometry (Stumped).

MehulChoksey — Tue, 26 Apr 2011 20:57:21 GMT

Could you capture and post http query request using tools like firebug/httpfox/fiddler ?

Re: Query Problems when using query.geometry (Stumped).

Anonymous User — Wed, 27 Apr 2011 14:04:47 GMT

Original User: caseybentz8

The only thing I see is that the two are using a different spatial reference. Have you tried passing the spatial reference wkid with the query?

Re: Query Problems when using query.geometry (Stumped).

CoreySchafer — Sat, 11 Dec 2021 06:47:16 GMT

I have messed around with the spatialReferences with no luck on; however, I don't have much of a background in GIS and may be doing something wrong.

Here is where I run the Query:

    var queryTask:QueryTask = new QueryTask(queryLayer);
    var query:Query = new Query();
    
    query.outFields                = queryFields.split(",");
    query.returnGeometry           = true;
    queryTask.useAMF               = false;
    
    if(borderCheckBox.selected == true){
     query.geometry = borderGeom; 
    }    
    query.where                    = rbeQuery;
    //query.where                    = "1=1";
    query.outSpatialReference      = map.spatialReference;
    
    queryTask.execute(query, new AsyncResponder(onRbeResult, onFault));

I thought perhaps my geometry may be too large, so I tried simplifying it with a GeometryService with no luck either.

I have attached some images from FireBug. I grouped them together to go along with the images I attached to my first post. Hopefully they aren't too small for you to read. Example 1 goes with the image with the arrows and Example 2 goes with the image with the water droplets.

Thanks for your Help!

Re: Query Problems when using query.geometry (Stumped).

Anonymous User — Wed, 27 Apr 2011 16:39:06 GMT

Original User: caseybentz8

I created a simple application that allows me to draw a polygon and query the service you are having trouble with, and it works as expected. I have attached the code and icons that I used for my test.

Re: Query Problems when using query.geometry (Stumped).

CoreySchafer — Sat, 11 Dec 2021 06:47:19 GMT

Thank you for your response. I have also written simple geometries which work with the service too. This makes me believe it has something to do with how I am getting the border's geometry.

I am a bit new to this, so perhaps the way I am getting the geometry is either wrong or harder than it needs to be. Currently, there is a Feature Layer which only has one feature which is the polygon I want to be my geometry. So this is how I am populating the geometry I want to use in the separate query that I am having troubles with.

   private function loadWVBorderGeometry():void{
    if(borderGeom == null){     
     var queryTask:QueryTask = new QueryTask(borderURL);
     var query:Query = new Query();
     query.where = "1=1";
     query.returnGeometry = true;
     query.outFields = ["Shape"];
     query.outSpatialReference = map.spatialReference;
     queryTask.execute(query, new AsyncResponder(borderResult, borderFault));
     function borderResult(featureSet:FeatureSet, token:Object = null):void{
      borderGeom = featureSet.features[0].geometry;
      borderGeom.spatialReference = map.spatialReference;
     }
     function borderFault(info:Object, token:Object = null):void{
      Alert.show("Border not loaded");
     } 
   }

I then use that borderGeom as the query.geometry in the code I had presented earlier. Is this the best practice when all I want is the geometry from the Feature Layer? It's all I can think of that can be the problem.

Re: Query Problems when using query.geometry (Stumped).

Anonymous User — Thu, 28 Apr 2011 12:51:46 GMT

Original User: caseybentz8

What is borderGeom declared as?

Re: Query Problems when using query.geometry (Stumped).

CoreySchafer — Thu, 28 Apr 2011 13:17:50 GMT

a global variable as:

private var borderGeom:Geometry;

Re: Query Problems when using query.geometry (Stumped).

Anonymous User — Sat, 11 Dec 2021 06:47:23 GMT

Original User: caseybentz8

I have run out of ideas. I can get it to work using the code below.


protected
 function myMap_loadHandler(event:MapEvent):void


[LEFT]{
var queryTask2:QueryTask = new QueryTask("http://sampleserver1.arcgisonline.com/ArcGIS/rest/services/Demographics/ESRI_Census_USA/MapServer/5");
var query2:Query = new Query();
query2.where = "STATE_NAME ='West Virginia'";
query2.returnGeometry = true;
query2.outFields = ["Shape"];
query2.outSpatialReference = myMap.spatialReference;
queryTask2.execute(query2, new AsyncResponder(borderResult, borderFault));
function borderResult(featureSet:FeatureSet, token:Object = null):void{
borderGeom = featureSet.features[0].geometry;
borderGeom.spatialReference = myMap.spatialReference;
stateLayer.add(featureSet.features[0]);
query.geometry = borderGeom;
queryTask.execute(query);
}
function borderFault(info:Object, token:Object = null):void{
Alert.show("Border not loaded");
} 
[/LEFT]
}


<esri:QueryTask
 id="queryTask"
concurrency="last"
executeComplete="onQueryExecuteComplete(event)"
showBusyCursor="true"
url="http://publicsafetytemplates.esri.com/ArcGIS/rest/services/EMCOP/PublicSafetyFeedSample/MapServer/0"
useAMF="false"/>




<esri:Query id="query"
outSpatialReference="{myMap.spatialReference}"


returnGeometry="true"/>



private
 function onQueryExecuteComplete(event:QueryEvent):void



{

var symbol:SimpleMarkerSymbol = new SimpleMarkerSymbol(SimpleMarkerSymbol.STYLE_SQUARE, 8, 0xFFFF00, 0.5);
symbol.outline = new SimpleLineSymbol();

var fset:FeatureSet = event.featureSet;
for each (var graphic:Graphic in fset.features)
{
graphic.symbol = symbol;
myGraphicsLayer.add(graphic);
}


}

Re: Query Problems when using query.geometry (Stumped).

CoreySchafer — Tue, 10 May 2011 18:08:37 GMT

I can get that URL to work with the current code I have. The one I am getting an error with and can't figure out why is http://rmgsc.cr.usgs.gov/ArcGIS/rest/services/nhss_usdata/MapServer/0

My only guess is that maybe it is a spatial issue, but I am newer to GIS so I'm not 100%.

I've still been trying different approached with no luck...still stumped as to why it works when the geometry isn't applied, but I get the error when the only change made to the query is the border...
I have changed my code to fetch the border geometry the same way you did (query2.where = "STATE NAME....). It seems to run faster than what I had before with a simpler geometry returned. Still no luck when I use that geometry either though.

BTW thank you so much for your help...

Re: Query Problems when using query.geometry (Stumped).

Anonymous User — Tue, 10 May 2011 19:42:29 GMT

Original User: watson_j

Not sure if this is related, but I am noticing that sometimes either the Flex API or the Viewer (at 2.3.1) is making an invalid URL when hitting REST services on my server. It is asking for ".../mapserver/..." instead of ".../MapServer/..." as it should.

Might want to focus on the URLs being sent back/forth to your server to make sure they are not mal-forming the "MapServer" mixed-case to "mapserver" lower-case.

Re: Query Problems when using query.geometry (Stumped).

CaseyBentz — Wed, 11 May 2011 16:05:54 GMT

So, now that I am querying the proper service. I now get the same error as you. The fault content shows that it is an invalid url. I am not sure what the xml style comment is all about.

The specified URL cannot be found

It is really weird, when I go back to attempting to draw a polygon to query that layer, I get some mixed results. I can draw a simple rectangle and get a proper result every time. I can draw a point to point style polygon with up to 36 vertices and it will work. When I try 37 or more it fails everytime. I can also draw a very small free hand polygon and it works, I am assuimg that it has less the 37 vertices. It seems like there is something up with rmgsc.cr.usgs.gov's ArcGIS Server.

Re: Query Problems when using query.geometry (Stumped).

Anonymous User — Wed, 11 May 2011 16:14:00 GMT

Original User: caseybentz8

You could try this method, add a where tag to your query. It appears that the STANAME always ends with the state abbreviation. I then commented out the query.geometry = borderGeom line, and it brings back 118 features.

<esri:Query
[LEFT]id="query"

outSpatialReference="{myMap.spatialReference}"
where="STANAME LIKE '%WV'"

returnGeometry="true"/>

[/LEFT]