Hi David,
One thought - and you might have already considered this, but if not, we can review something that might be causing these issues...
Before you published, did you conduct the re-project geoprocessing operation on each of your "to be published" data layers, using the geoprocessing tools in ArcGIS Pro, re-projecting from their existing CRS/projection into Web Mercator?
You likely know this, but to review this concept, inside of Pro (or ArcMap), whenever you add a layer to an existing map that is in a certain projection, there is a transformation that occurs with any layers added to the map from their CRS/projection to that of the map.
However, the data itself isn't re-projected in this operation. Re-projection requires a deliberate geoprocessing operation in order to re-project the data from it's current CRS/projection into a different CRS/projection system. Those tools are in the data management geoprocessing tools.
Sometimes, the misalignments and inability to view results after publishing, are due to these projection misfit issues. This can happen when sharing from desktop application, maps or features, where layers in the maps may be of various CRS/projections, and have been transformed on the fly, to align for viewing in the given map.
When sharing published map services or feature services, it can be problematic if certain steps are not taken ahead of time with the data itself to prepare for publishing. Usually, however, if there are mixed projections in the map or features being shared, an error is noted in the analysis ahead of publishing, when this is an issue.
For publishing to web services, what I typically do, since most layers need to work in Web Mercator, is to make a re-projected copy of my layer(s) that will be published as web services.
- I keep the originals in their original working projection, as my base data, which I will use for re-projecting to the required CRS/projection for specific purposes.
- If the data is edited, I can re-run this again if I save that geoprocessing task in a Model Builder model.
- I have found that it's also helpful to note all of this information in the layer's metadata, for later reference or for others, to understand what operations have been undertaken and the original data source's CRS/projection.
If you have covered all of these bases, then it could be something else.
In the meantime, I will see if this is an issue in any of my maps created in Map Viewer Classic, that I open up in the new Map Viewer.
With change always comes an amount of change management. The new #MapViewer has lots of cool features and is still missing some old favorite features in Map Viewer Classic, but, continuing to communicate what we need is part of the adoption process.
Hope it helps!
