Invalid Spatial Reference Issue

Permanently deleted user

January 30, 2014 08:31

Hello,

I've had some frustrations this week regarding the map's spatial reference and workflows, and I hope this helps others who are having the same problem.  

 

I had an issue with my workflow(s) in that the features returned from a Query Task was not in the correct spatial reference/projection and was therefore not displaying. I would instead recieve a notification that the results had an invalid spatial reference. I could not find information anywhere as to where to get the map's spatial reference (that is, which layer was controlling the spatial reference of the site).

It was very confusing to me as the WKT for all of my layers appeared to be the same. However, it looks as if our imagery layer was a slightly different version of the same state plane projection. I even added a new spatial reference object to the query task, but it would not resolve the issue, as the new spatial reference object was apparently still wrong.

Finally, to solve it, I added a GetMapInfo task to the workflow(s) and extracted the map's spatial reference as a Spatial Reference object. I then used that object in the out spatial reference field of the query task, to make sure that the returned results were in the correct spatial reference. It worked wonders!

 

 

0

• 

  Sebastian Mariendal Kristensen

  January 30, 2014 20:23

  What kindt of arcgis server do you use?

   

  We had problems whith ArcGISserver 10.2.1 where sevices sudently showed the full description for the spatial reference insted of the spatial reference ID number.

  We had no problem to show the services in GeoCortex, but if we used data in a workflow and returned data from a service with a full spatial reference description, then it returned a "Spatial reference don't match" error.

  The problem was that the spatial reference file names in ArcGIS 10.2.1 used spaces in the filename and in 10.2 used underscore in the filename, and the arcgis server still looked for the filename with underscores.

   

  So the solution of the problem was to remane the spatial reference filename to use underscores, reference the map agian with the new file and publish the service againg.

  Then all was back to normal and worked fine in GeoCortex.

   

   

  0
• 

  Permanently deleted user

  January 31, 2014 01:01

  We are using 10.2.1, which we just installed last week, so that may explain the sudden appearance of this issue. Thanks a lot for responding! 

  0

Please sign in to leave a comment.