...in which line of code it is read? Can you hint this point?
It is part of the server side print task which automatically reads it from the service metadata. I'm not familiar enough with the server side print task, but the important part to understand is that it is not on the client/browser/API side.
Assuming you are using the 3.0 PrintWidget and ArcGIS Server printing...
The PrintingTools service included with ArcGIS for Server references a preconfigured folder with eight map layouts. If you want to use your own layouts, you can publish your own service for printing web maps. You configure this service to reference your own map layouts.
bjorn: Thanks for your response. The reference you provided is about the layout. My Q's are related to some information displayed in the printed map, rather than related to layout.
The reference you provided is about the layout. My Q's are related to some information displayed in the printed map, rather than related to layout.
Hi Shaning, Maybe I'm still misunderstanding it, but the main thing being sent from the print widget to the print task on the server is just the list of layers to print and the extent. No widgets, scale bar etc.
So to answer your three questions: 1) The North Arrow cannot be added and included from the web clients when using the standard print service. You would have to create your own print layout in ArcMap. 2) The ruler by the Coordinates cannot be included from the web clients when using the standard print service. You would have to create your own print layout in ArcMap. 3) The source text cannot be customized from the web clients. It is automatically retrieved from the map service "Copyright Text", see for example bottom of http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer
Thanks for your response. Even though the source (basemap) text can't be customized, in which line of code it is read? Can you hint this point? Thanks.
...in which line of code it is read? Can you hint this point?
It is part of the server side print task which automatically reads it from the service metadata. I'm not familiar enough with the server side print task, but the important part to understand is that it is not on the client/browser/API side.
