Print Template bug with basemap
Hi there,
Bug 1: I have a basemap that can zoom to 1:750. When I print, the dialog box shows "current scale 1:750" I hit ok, the map prints at 1:749, meaning my basemap goes blank on the print.
Bug 2: I have "Current extent" set as the default map scale option in manager, but the print dialog shows "Current scale" instead of current extent.
Anyone else have this issue? Can someone from latitude test? I have had to create a workflow as a workaround.
The basemap is a public service. https://mapping.ssc.nsw.gov.au/ArcGIS/rest/services/draftlep/LZN/MapServer
example: first not showing current extent, then second rounding down the scale in the print, the map is blank just left of where the legend is:
/customer/servlet/servlet.FileDownload?file=00P6000000elu83EAA /customer/servlet/servlet.FileDownload?file=00P6000000em1XAEAY
-
Mark, did you ever get this sorted out? I'm experiencing the same thing.
0 -
Hi Mark,
I was able to reproduce Bug #1and filed it under GVH-6529. Bug #2 has already been identified under issue GVH-4765. I've attached you as a stakeholder on both items.
Thanks for giving us all the details required.
Matt: Let me know which of the two (or both) I can attach you onto as a stakeholder.
-Kevin
0 -
Thanks Kevin. Its great that latitude staff are so active in these forums.
0 -
Kevin,
you can add me to both of those.
I don't get current extent as my default and when I print to current scale, the output is different.
Am not the only one with this problem: (https://support.geocortex.com/SupportForums/Thread.aspx?thread=57441&mid=2&pageid=0&ItemID=9&pagenumber=1#post164591) http://support.geocortex.com/SupportForums/Thread.aspx?thread=57441&mid=2&pageid=0&ItemID=9&pagenumber=1#post164591
0 -
Hi,
I am also having the same issue where the scale shows up as one lower than the minimum scale level (ex. 399 instead of 400) and the cache layers disappear. Is there a workaround for this that anyone has found?
- Greg0 -
Hi,
I'm checking this now on essentials 4.4.2 and the html5 viewer 2.5.1 and the problem still occurs for me. Is this still an open bug? resolved? or is there a workaround for this?0 -
Hello,
I have Bug1 exactly as described. I'm so glad I found this so quickly. I couldn't find an easy solution. I'm converting from Web Mercator to the local scale so I thought it might be something to do with that. Looks like it's not resolved yet.
Lara0 -
There is a workaround which can be used in the meantime. If you set a scale in the print template to be the maps minimum scale, users can select this when printing all the way zoomed in. The viewer then appends a scale override along with the extent. This way the scale is not calculated on the extent and the basemap will be visible. 0 -
Kevin,
Could you please provide more details about your suggested fix. I haven't touched our print templates in probably 2 years so I am rusty. Are you setting something in Essentials or on the print template itself?
Thanks,
Carmen0 -
+1 please 0 -
In the meantime, is there a way to remove "Current Scale - 1:x" from the list of options in the print dialog box? I am looking in the code for this but can't locate it, or alternatly can we set the default in the code in the area I list below? If we can remove that option, or set the default to be "Current Extent" then the workarounds listed above will work great. Any ideas? Thank you!
{
"moduleName": "Printing",
"moduleType": "geocortex.essentialsHtmlViewer.mapping.modules.printing.PrintingModule",
"configuration": {},
"views": [
{
"id": "PrintingView",
"viewModelId": "PrintingViewModel",
"type": "geocortex.essentialsHtmlViewer.mapping.modules.printing.PrintingView",
"markup": "Mapping/modules/Printing/PrintingView.html",
"region": "ModalWindowRegion",
"visible": false,
"iconUri": "Resources/Images/Icons/Toolbar/print-24.png",
"title": "@language-print-map",
"configuration": {
--anything here that might work?--}
}0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
11 Kommentare