topic Re: QueryTask result features set to wrong projection system in ArcGIS API for Silverlight Questions

QueryTask result features set to wrong projection system

SadanandacharB1 — Thu, 20 Nov 2014 05:09:28 GMT

Hi All,

I am getting QueryTask result features in wrong projection system,

1. Task : Migrating of Arcgis server from 10.0 to 10.2.1

2. Development: Silverlight application version 5.0

3. All original map service layers render in correct location in the Map control.

4. But after the using Query task on route event layer, the result objects are set to wrong projection system, it pans to the coast of Africa near Nigeria, when i check the WKID for result features it is set to 102100.

I have also set outSpatialReference [source from map] on query result features no use,

Any one can please help on this...

Thanks

Sadanand

Re: QueryTask result features set to wrong projection system

DominiqueBroux — Thu, 20 Nov 2014 08:26:01 GMT

You have to set the Query.OutSpatialReference before executing the query task.

There are a few query samples that demonstrate how to do it in the Silverlight interactive SDK.

If you are experiencing issues in a specific use case, please share a repro.

Thanks

/Dom

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Thu, 20 Nov 2014 13:55:57 GMT

Hi Dominique, thanks for the replay, even i had try this by setting this property like below

myQuery.OutSpatialReference = Mainpage.map.SpatialReference; but getting the same error, what could be the cause ? please help on this issue..

Thanks

Sadanand

Re: QueryTask result features set to wrong projection system

JenniferNery — Wed, 26 Nov 2014 17:33:16 GMT

Hi Sadanand,

What error message do you get from QueryTask? What SpatialReference is the service in and what is the SpatialReference of your map? Setting Query.OutSpatialReference should return features in that SpatialReference. Does the QueryResult.Features come back with the expected SpatialReference? Are you using GraphicsLayer or FeatureLayer to display these features?

Sorry I have more questions than answers. You can also try running Fiddler to see if there are any error messages from the server and if that error is being captured in the TaskFailedEventArgs when you subscribe to QueryTask.Failed event.

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Thu, 27 Nov 2014 11:58:48 GMT

Hi Jennifer,

Thanks for your replay, below are the details that I have tried.

1. Copied the Geodatabase from Oracle to Geodatabase at Oracle using ArcCatalog 10.2.1 tool copy 'Feature Class to Feature Class'. This is for the purpose of Upgrading the ArcGIS 10.0 to ArcGIS 10.2.1 [New Machine used for ArcGIS server 10.2.1]

2. Created a ArcMap file and added the below layer

2a. Roads feature layer with M values from the Oracle Geodatabase.

2b. Added attribute table called Bridges_details. [View in the same Geodatabase]

2c. Created a 'Make Route Event Layers' using the above 2 layer, this is to show the bridge points on top of road

3. All the above 3 layers are in the projection system 'WGS_1984_UTM_Zone_44N' by default.

4. In .mxd file 'Layers' projection system is set to WGS_1984_Web_Mercator_Auxiliary_Sphere WKID: 102100, this is published as Mapservices

5. When I run the Silverlight web application all published layers and a basemap are displayed in correct location.

6. I am using QueryTask to locate bridge points, and below are the details.

6a. Mainpage.map.SpatialReference is set to WKID: 102100

6b. Query.OutSpatialReference is set with Mainpage.map.SpatialReference [i.e. 102100]

6c. GraphicsLayer is used to add QueryTask results

7. But QueryResult.Features are not come back as expected, [locating in Africa near Nigeria UTM zone 30 and 31]

8. And one thing I noticed when I provide Bridges_details attribute table [RDBMS View] as a file geodatabase, the QueryResult.Features returns correctly as I expected

What could be the reason please help me, I prefer to use Bridges_details view as dynamic.

Thanks

Sadanand

Re: QueryTask result features set to wrong projection system

JenniferNery — Wed, 03 Dec 2014 20:42:21 GMT

Hi Sadanand,

Can you check the web response? You can run Fiddler while your app is making the query, it should look similar to this:

If the JSON has spatialReference that is correct (same as outSR=102100), check that QueryResult.Features SR is also the same.

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Wed, 10 Dec 2014 10:10:30 GMT

Hi Jennifer,

I have run the fiddler, Above is the screenshot of that query results , My qyeryResult.Features SR has same as JSON spatialReferene, But output is still locating on Africa, what to do?

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Wed, 10 Dec 2014 10:20:17 GMT

Hello Jennifer,

I have one more problem in arcgis 10.2.1 , If i join one oracle attribute table to one spatial table(Feature Class) using "Join and Relates" and accessed as a map service, It's projection system also changes. But when i publish only spatial table it locate's on the correct projection system. What is the problem in Joining?(in ArcGIS 10.0 same procedure is working).

Thanks

Sadanand

Re: QueryTask result features set to wrong projection system

DominiqueBroux — Wed, 10 Dec 2014 10:20:39 GMT

Hi Sadanand,

From your screenshoot, it seems you didn't set the OutSpatialReference as I suggested above.

This parameter drives the SR of the returned features and is key to fix your issue.

Once set, you should see a 'outSR' parameter in the query request sent to the server.

Dominique.

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Wed, 10 Dec 2014 11:13:28 GMT

Hello Dominique,

I Set the OutSpatialReference as you said in QueryTask, But No changes, Results locates on Africa,Here is the screenshot of the result.

queryTask.ExecuteCompleted += QueryTask_ExecuteCompleted;

queryTask.Failed += QueryTask_Failed;

Query query = new Query();

query.OutFields.Add("BRIDGE_NAME");

query.Where = "1=1";

query.OutSpatialReference = MyMap.SpatialReference;

query.ReturnGeometry = true;

queryTask.ExecuteAsync(query);

Re: QueryTask result features set to wrong projection system

DominiqueBroux — Wed, 10 Dec 2014 11:20:05 GMT

OK. Now the outSR parameter is set, unfortunately it doesn't seem to solve your issue.

Could you show us how the geometry of the returned features look like (as in Jennifer's screenshot)?

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Wed, 10 Dec 2014 12:08:40 GMT

Hello Dominique,

I have posted the screenshot of geometry of the returned features.

Re: QueryTask result features set to wrong projection system

DominiqueBroux — Wed, 10 Dec 2014 14:44:47 GMT

Humm, the issue doesn't seem to be at client side. The display is consistent with the returned geometry (x, y around 1000000 mean around Nigeria).

Maybe an issue at server side or an issue due to how you published the service.

If you try to display your published service in ArcMap, is it working well?

If you try to display your published service in Silverlight by using an ArcGISDynamicMapServiceLayer, is it working well?

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Thu, 11 Dec 2014 05:27:30 GMT

Hi Dominique thanks for your replay

1. When i display my published service in ArcMap, it is working fine,

2. and when i display same service using ArcGISDynamicMapServiceLayer in Silverlight web application it is locating correctly.

3. But when i use QueryTask on this layer the result graphics locating on Africa.

below is the screenshot of service displayed in both cases(Arcmap and ArcGISDynamicMapServiceLayer)

Please help on this issue..

Thanks

Sadanand

Re: QueryTask result features set to wrong projection system

DominiqueBroux — Thu, 11 Dec 2014 08:28:01 GMT

That beats me. It looks like a projection issue at server side but I don't get the reason.

I'll try to reproduce locally (I guess your service is not publicly accessible?).

As a workaround you might try publishing your service in 'WGS_1984_UTM_Zone_44N' instead of Web Mercator. May be the projection works in this case?

Re: QueryTask result features set to wrong projection system

sakinachafaqi — Thu, 11 Dec 2014 11:00:42 GMT

Hello

When I export metadata from arcgiscatalog I have this errors:

Error 000622: The execution failed (XslTransform) incorrect parameter

error 000840: The value does not match a file

In your opinion what's the problem.

thank you

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Thu, 11 Dec 2014 11:16:58 GMT

But we want to use Base map or Bing map as well.

Yes services are accessible to public, below are the url of these.

1. http://119.82.100.170:6080/arcgis/rest/services/Bridge_44N/MapServer

Bridge points [Make route event layer] when using 'WGS_1984_UTM_Zone_44N' and Base map QueryTask results of this layer locating on Africa [Wrong location]

2. http://119.82.100.170:6080/arcgis/rest/services/Bridges_WM/MapServer

Bridge points [Make route event layer] when using Web Mercator projection and Base map QueryTask results of this layer locating on Africa [Wrong location]

And we have also tried on some Line features i.e. Roads with using JOIN [Joining an attribute table in ArcMap]

3. http://119.82.100.170:6080/arcgis/rest/services/Roads_WM_Join/MapServer

when using Web Mercator projection and Base map QueryTask results of this layer locating wrongly

4. http://119.82.100.170:6080/arcgis/rest/services/Roads_WM_WithoutJoin/MapServer

But when we use the same Roads without using a JOIN, QueryTask results projecting correctly.

Is there any issue when Joining an attribute table ?, My Geodatabase is in Oracle 11g version 11.2.0.1, please help..

Thanks

Sadanand

Re: QueryTask result features set to wrong projection system

DominiqueBroux — Thu, 11 Dec 2014 13:55:21 GMT

Hi,

Thanks for this info.

This confirms there is something wrong at server side.

The node coordinates returned by the query REST End Point are the same whatever the out spatial reference (example with WebMercator or WGS84).

Concerning the join, it's not the same issue, the coordinates returned seem good but when too much data are requested the server returns an internal error.

Not sure if these are bugs in ArcGIS server or if it's due to the way the features have been published. You might get better answers by posting the question on the server forum..

Thanks

/Dominique

Re: QueryTask result features set to wrong projection system

SadanandacharB1 — Thu, 11 Dec 2014 14:04:32 GMT

Hi, Dominique, thanks for your support.

Sadanand

Re: QueryTask result features set to wrong projection system

ThibautDelaere1 — Wed, 25 Jan 2017 11:01:48 GMT

Was this issue ever solved? We're having the same behavior on some of our servers (ArcGIS Server 10.3.1).

Query on object id's stays in WGS84 instead of WGS84 web mercator.