I have a *.tif in Pro that I'm publishing to AGOL as a tile. It's not behaving. The CRS of my map in Pro is one thing, so as I share to AGOL I make sure to configure the tiling scheme to ArcGIS Online / Bing Maps / Google Maps. This has been my workflow for all the others.
The REST Endpoint of the published tile layer tells me the CRS is 102100, which is the same as the AGOL basemap. So, why does the tile layer land at 0,0 in the webmap? I've deleted it and republished over and over thinking it might be a glitch, but to no avail.
How the CRS looks on the Map Service endpoint:
Spatial Reference:
102100
PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Mercator_Auxiliary_Sphere"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],PARAMETER["Auxiliary_Sphere_Type",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",3857]]
How it looks when you click the Layers endpoint:
"spatialReference" : {
"wkid" : 102100,
"latestWkid" : 3857,
"xyTolerance" : 0.001,
"zTolerance" : 0.001,
"mTolerance" : 0.001,
"falseX" : -20037700,
"falseY" : -30241100,
"xyUnits" : 10000,
"falseZ" : -100000,
"zUnits" : 10000,
"falseM" : -100000,
"mUnits" : 10000
}