Layers not showing on printed map
Greetings,
I am running essentials 4.6.3 and html5 2.7.1.
Certain layers in my site turn on at a 1:2000 scale.
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000Cke5&feoid=Body&refid=0EM600000001TAr" _/_img_
When I print, the layers that show at 1:2000 do not show on the print.
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000Cke5&feoid=Body&refid=0EM600000001TB1" _/_img_
In the print settings box I ensure I select MAP SCALE 1:2000.
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000Cke5&feoid=Body&refid=0EM600000001TAw"_/_img_
I also get the same behaviour from the silverlight viewer, but if I change the scale to 1:1999 in the silverlight viewer everything works.
Am I missing something? Or is this a BUG?
Many Thanks
0
-
Hi Craig,
I think the issue here is that when you print the map, Essentials sends a request to your ArcGIS service using the your selected map extent . When ArcGIS Server calculates the scale for this extent, it might be a little bit off from the scale you chose.
You can use a tool like Fiddler to look at the requests that are sent to ArcGIS Server and see how far it is off (and potentually make adjustments to your print scales as a workaround)
Here's an example:
I printed using these settings:
_img_ alt="Print Settings in HTML5 Viewer" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrFd&feoid=Body&refid=0EM60000000UjUP" _/_img_
Here's the request that was sent to export my basemap (found using Fiddler):
https://services.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer/export?bbox=-11773480.8310879%2c6065401.56943112%2c-11771560.3545932%2c6066906.42041582&bboxSR=102100&size=804%2c630&dpi=96&format=png&transparent=true&layers=show%3a0&imageSR=102100&_ts=636295112513884570&f=image
If you change the f=image at the end to f=pjson and load that url in a browser, you can see that the calculated scale for the extent that was used is 9027.9593550656082.
We do have a bug for this and I'll add you on as a stakeholder.
Hope that helps,
Amanda0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar