Using the .NET Runtime, we've noticed that the server-side rendered tiles from a map service do not show up in the correct locations. The Runtime app starts with a public esri WGS84 basemap and asks for tiles in that spatial reference. It appears the tiles sent down are not projected into WGS84. They are offset to the north. This can be seen in the attached screenshot (the black line should be where the red highlight is). Manually re-projecting the feature data to WGS84 at the geodatabase level corrects the offset, as there is no re-projection in this case.
Is there a setting in ArcGIS Enterprise/Server that prevents on-the-fly re-projections in the Server-side rendering pipeline?
Here's the details of the spatial reference we are working with:
WKID: 27700 Authority: EPSG
Linear Unit: Meter (1.0)
Another detail: we went to the data frame properties in ArcMap and changed the coordinate system there. Setting this to British National Grid to match the data that was in the GDB didn't work. Nor did setting the data frame coordinate system to WGS 1984 World Mercator. Both data frame coordinate systems resulted in the same offset.