MapView.Extent is wrong on spatial reference change

MaxMax2

Code for test:

<SPAN class="keyword token">var</SPAN> sr <SPAN class="operator token">=</SPAN> mapView<SPAN class="punctuation token">.</SPAN>Map<SPAN class="punctuation token">.</SPAN>SpatialReference<SPAN class="punctuation token">;</SPAN>
<SPAN class="keyword token">var</SPAN> extent <SPAN class="operator token">=</SPAN> mapView<SPAN class="punctuation token">.</SPAN>Extent<SPAN class="punctuation token">;</SPAN>‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Steps to reproduce the problem:

1. Create new project. Variables now will have values:

2. Add layer with WGS84 spatial reference and zoom to full extent (the issue will be without zooming too). Now execute the code above:

We see that spatial reference now is WGS84, but extent coordinates doesn't correspond to WGS84. Max extent for this sr must be -180 -90 180 90 in degrees, but the values from screenshot are obviously wrong.

More than that I can't project extent to WGS84, because it's already in WGS84, so coordinates still the same!

TestGdb.gdb.zip

RHB2.jpg

Stefan_Thorn_13-1652309055087.png

CharlesMacleod

Max, the issue to me looks like you are not specifying a cell size. The resulting cell size of the raster is 10600614 which matches the dimension of the raster. I do not know the significance of that number (i.e. why is it used as the default cell size). However, if I do specify a cell size explicitly (eg "90" or "180" ) then the extent of the layer is correct (as, in, it is a proper extent).

As the cell size, in this case because of the projection being used, is in decimal degrees and the WGS projection is wider than it is tall, I assume that the maximum possible cell size will be "180" while still retaining a "real" spatial extent.

For example, using your same settings and a cell size of 180: