The Spatial Reference of a service in its ArcGIS 10.3 Rest endpoint appears to list the full projection parameters whereas 10.2.2 lists only WKID.

3980
1
Jump to solution
04-30-2015 10:50 AM
SubuSwaminathan1
Occasional Contributor

Is this a documented change? I am guessing this is causing me issues in Web App Builder - resulting in Different spatial reference error?

0 Kudos
1 Solution

Accepted Solutions
SubuSwaminathan1
Occasional Contributor

BUG-000088301:When publishing a map service with Z and or M values-enabled and uses Spatial Reference 2927, the spatial reference is displayed as WKT instead of WKID in the service description.

Effect: This bug results in layers having the same underlying WKT behave like layers that have different spatial reference. So in JSAPI applications, you start having overlay issues, zoom and pan issues - any operation involving changing the extent of the map application does not work.

Workaround: We had remove M and Z values from all the concerned layers that did not need them. DBA had to recreate featureclasses in production db. MXDs had to refreshed by changing the cs to something else and then reverting to 2927 which is 'washington state plane south NAD83 Harn'. New service definition files had to be created and services republished. Cache status and related files had to be recreated.

Subu

View solution in original post

1 Reply
SubuSwaminathan1
Occasional Contributor

BUG-000088301:When publishing a map service with Z and or M values-enabled and uses Spatial Reference 2927, the spatial reference is displayed as WKT instead of WKID in the service description.

Effect: This bug results in layers having the same underlying WKT behave like layers that have different spatial reference. So in JSAPI applications, you start having overlay issues, zoom and pan issues - any operation involving changing the extent of the map application does not work.

Workaround: We had remove M and Z values from all the concerned layers that did not need them. DBA had to recreate featureclasses in production db. MXDs had to refreshed by changing the cs to something else and then reverting to 2927 which is 'washington state plane south NAD83 Harn'. New service definition files had to be created and services republished. Cache status and related files had to be recreated.

Subu