Select to view content in your preferred language

ExB Print Widget not honoring scale

662
4
10-08-2024 01:59 PM
Labels (1)
PLadd
by
Frequent Contributor

Unless I use the zoom plus/minus tool for zooming, the scale of the map is not honored when I use the print widget.  My basemap is cached to engineering scales (i.e. 1:2400, 1:1200, 1:600 etc).  I am using state plan coordinates.  I have the scale widget showing in the map.

  • If I zoom in with the wheel, the map shows, for example, a scale of 100 ft.  But it prints at a scale of 1" = 104 ft (1:1,250).  
  • If I zoom to a selected feature (pre-set to zoom to 1:1200), the map displays correctly but again the print widget messes up the scale
  • If I zoom to a selected feature, then click the zoom out/zoom in, and then print, the scale on the print is accurate.
  • Or if I just zoom in/out with the zoom widget and then print, the scale is always correct on the printed map.

How do I control the scale properties between the map and a print so that the printed page ALWAYS shows an accurate scale?

  • I have modified the "Output spatial reference" in the Template common settings of the print widget
  • I have disabled zoom in/out with wheel

Not printing to scale is a show-stopper.

 

4 Replies
BillFox
MVP Frequent Contributor

do you see different results on different workstations with different monitors/screen resolutions?

0 Kudos
PLadd
by
Frequent Contributor

Thanks @BillFox  for the suggestion.  That’ll be an interesting bit of data to compile. 

I used different devices (laptop and PC), different browsers (Chrome, Firefox, and Edge), and different window states (maximized and normal) and here’s a summary of what I found.

The browser brand has no impact on the results – still not engineering scale in the printout.

The browser window state does change the result.  A maximized window yields a larger scale than a normal window - but it’s still not engineering scale.  Adjusting the  size of a normal window also yields different results.

The device, and thus, the window resolution/screen size changes the scale result.     The scale is smaller on the device (laptop) with the smaller screen size/resolution.  But the print scale is still inconsistent with the map scale.

I also tried adjusting the map widget in the app so that it is 3% inside the edge of the app instead of full width/height but that had no bearing on the result – it was exactly the same at 1:1,285.

Map scale and printout scale remain different.

FWIW, I am using Experience Builder Developer Edition (1.15) but the off the shelf print widget with my own print service in our Enterprise solution.  So I went to off the shelf Experience Builder (not Developer Edition) and used the off the shelf printing utility and the results are actually worse because using the zoom widget does not yield the same scale on the print shown in the map.

I'm also at ArcGIS Enterprise Portal 11.3 and ArcGIS Pro 3.2.1 to publish the print service.

I should also note that I am also using the print widget in the Web AppBuilder.  It utilizes the same in-house printing service and the map scale and printout scale are consistent.

PLadd
by
Frequent Contributor

While I await hearing back from tech support on this, I did find a small, temporary workaround. 

When configuring the print widget, expand "Template common settings", click on edit pencil for "Map printing extents" and use "Set map scale" to 1200.  This forces the map to always print a 1:1200 scale (1" and 100 ft) map. 

Then, the Advanced feature on the print widget for end-users allows them to change this default setting, if needed.  I can share with staff how to do this and most public users may not care about engineering scale but at least I don't have to be embarrassed with a scale that's, well, embarrassing (i.e. 1:2087).

0 Kudos
RyanShearerNewarkOH
Emerging Contributor

We are also having similar issues. Our basemap is cached to the AGO/Google Scales, but when we set the scale in ExB to print at, say, 600, it actually prints at 468. That isn't a tile scale or anything else that makes sense. We are using the default AGO print service for now, but we would be okay developing a custom service in the future. 

0 Kudos