I am a developer of GIS Web components, and I would greatly appreciate it if the logic that converts a MapView into a WebMap_as_JSON could be exposed in a public method. We run a custom printing service that uses the Export Web Map Task geoprocessor with extra parameters to enable the printing use cases of my Organisation.
Both the PrintViewModel.print() and the print.execute() combine building the payload and sending the request. Exposing the logic that generates the WebMap_as_JSON as a seperate method would benefit our workflow for two reasons.
- Lower code complexity: It would make it easier to edit the WebMap_as_JSON payload before sending the request to the server. Currently we have to rely on requestInterceptors to configure the payload correctly
- Easier troubleshooting: With over 1000 daily users sometimes the printjobs fail. We track these failures with dynatrace but getting the Webmap_as_JSON which is crucial for troubleshooting is cumbersome. A seperate method would make logging the json payload to dynatrace a breeze.
