-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Print Support and server side issues printing WMTS and TMS layers #5292
Comments
@offtherailz @tdipisa in general:
brokenUrlPlaceholder: 'data:png,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNkYAAAAAYAAjCB0C8AAAAASUVORK5CYII=' About TMS: the attached request is wrong. This is one that works: The main differences are:
|
About WMTS, the attached request works fine with the transparent brokenUrlPlaceholder I mentioned in my previous comment |
@offtherailz @tdipisa let me know if this is enough to solve your issues, or need anything more / else |
@mbarto thank you so much for the investigation, it is really useful. I think it is enough for the moment, @offtherailz should be able to replicate according to your feedback and check the TMS code for a fix. |
@ElenaGallo and @mbarto : |
Blocked because to be tested it needs to merge #5189 |
…it#5972) * geosolutions-it#5292: Fixed opacity issues in printing * Unified opacity exract system in printutils
@offtherailz please remember to update the revision in c125 project for this |
Description
We need to provide support for Printing for:
WMTS:
http://gs-stable.geo-solutions.it/geoserver/wmts
https://www.basemap.at/wmts/1.0.0/WMTSCapabilities.xml
)TMS :
allowedProviders: "ALL"
)https://nls-{s}.tileserver.com/nls/{z}/{x}/{y}.jpg
and advancedOptions:Server side issues
next comments concerns some issues on back-end that has been fixed acting on the request and on the print
config.yml
.If you find the issue on WMTS, we need to update config.yml on the related project.
See this issue "Other useful information":
#5189 (comment)
And expecially the linked comment: https://github.com/geosolutions-it/austrocontrol-C125/issues/144#issuecomment-620455864
We need to investigate if these 2 issues are cause by:
Therefore plan a solution to mitigate this problem
Copy of the original comments issues :
For the WMTS layer to mapfish print specification, setting opacity to 1, hides the other layer background, in this case, WMS. I have attached the POST call with the spec sent for WMTS.
Is it due to some problems with the spec request?
Ex: http://localhost:8081/?debug=true#/viewer/openlayers/23534
POST Request (Spec)
POST_WMTS.txt
Screenshot:


Opacity - 0.45
Opacity - 1
TMS:
For TMS, I have encountered the below issue.
Mapfish print specification for TMS
POST-SPEC
POST_TMS.txt
Ex: http://localhost:8081/?debug=true#/viewer/openlayers/24413
After conversion, the mapfish prints the tile with white background in place of the TMS layer,
I have tried with three sample TMS services, but the results are same.
https://public.sig.rennesmetropole.fr/geowebcache/service/tms/1.0.0
https://osm.geobretagne.fr/gwc01/service/tms/1.0.0
http://gs-stable.geo-solutions.it/geoserver/gwc/service/tms/1.0.0
Screenshot

Note: Since the service appends the serviceVersion to the path, so I tried removing the service version in baseURL while sending spec but the result is still the same.
The text was updated successfully, but these errors were encountered: