In response to the large number of questions on this topic on the Wolfram Community, on StackExchange, and through Wolfram Technical Support, we have published a support article describing these changes, and their rationale, at

https://support.wolfram.com/50417

I agree with Szabolcs. The last two releases have broken the same code for me. The first time it was due to changes in FITS image import. This time it’s changes to rasterization. I am trying to do real work and need more attention paid to quality assurance.

Thanks, Szabolcs. Makes perfect sense. And I agree about the automatic resolution. Things just work . . .until they don't.

I understand what you are doing, I am doing the same thing and adapting to this chance was annoying ...

You can set $ImageResolution = 72 at the beginning of the session.

Alternatively, you can make all rasterization explicit, and set ImageResolution -> 72. This is some trouble because I also used to do things like Binarize@Graphics[Disk[],...] instead of using Rasterize explicitly.

I have not refactored all my code for this, but I was thinking of using something similar to the following:

rast[im_?ImageQ][gr_Graphics] :=
 Module[{w, h},
  {w, h} = ImageDimensions[im];
  Rasterize[
   Style[
    Show[gr, PlotRange -> {{0, w}, {0, h}}, ImageSize -> {w, h}],
    Antialiasing -> False
    ],
   "Image",
   ImageResolution -> 72
   ]
  ]

Then if we have an image image = RandomImage[{0.9, 1}, {100, 100}], we can rasterize corresponding masks as mask = rast[image][Graphics[Disk[{50, 50}, 50]]].

I am curious how others handle this.

I understand what you are doing, I am doing the same thing and adapting to this chance was annoying ...

You can set $ImageResolution = 72 at the beginning of the session.

Alternatively, you can make all rasterization explicit, and set ImageResolution -> 72. This is some trouble because I also used to do things like Binarize@Graphics[Disk[],...] instead of using Rasterize explicitly.

I have not refactored all my code for this, but I was thinking of using something similar to the following:

rast[im_?ImageQ][gr_Graphics] :=
 Module[{w, h},
  {w, h} = ImageDimensions[im];
  Rasterize[
   Style[
    Show[gr, PlotRange -> {{0, w}, {0, h}}, ImageSize -> {w, h}],
    Antialiasing -> False
    ],
   "Image",
   ImageResolution -> 72
   ]
  ]

Then if we have an image im = RandomImage[{0.9, 1}, {100, 100}], we can rasterize corresponding masks as mask = rast[image][Graphics[Disk[{50, 50}, 50]]].

I am curious how others handle this.

Thank you, @Szabolcs. I clearly did not understand how image dimensions relate to graphics in this case. Let me ask, please, if there is a good way to do what I am trying accomplish. I want to extract the data from a target image which corresponds to pixels identified by a convenient to construct mask having the same dimensions as the target image data. In the method which is broken (and perhaps it only worked accidentally), I try to construct the mask by generating an image using graphics primitives. I then use that mask to extract data from the target image. In this case I find the positions of all pixels having value 1, and use that list of positions with Extract to extract the data.

This worked before because my use of Graphics did generate an image of the needed dimensions. But that appears to have been an accident. It there a way to design an image with specific dimensions. For example, an image which would have ImageData dimensions 2048x2048 with a filled disk centered at {1000,1000} with a disk radius of 500, All dimensions being in pixels of ImageData. I can picture ways to do this with direct calculations for the value of each element in an array, but that is not as convenient as working with graphics primitives.

Best regards, David