-
Notifications
You must be signed in to change notification settings - Fork 25
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
Impossible to print with all the customized scales #585
Comments
@landryb , @jusabatier Do you have the same behaviour with the last release ? |
Here it appear to work, in our conf we set :
Not related, but we have A3 format selected by default on print plugin opening. |
Yes we have the same.
But the issue is just for the scales between 1:4000 and 1:100 however they are in the config.yml (I personally think that there are too many of them but it was a request from the product owner):
@tdipisa, is there a limited number of scales to use, now ?
|
I can try to do a PR to add it in https://github.com/georchestra/mapstore2-georchestra/blob/master/configs/localConfig.json, if you want. |
@tdipisa To give you more information, in the mapstore logs , I see
|
that'd be welcome so that one knows its possible.. but dont forget to also PR https://github.com/georchestra/datadir/blob/master/mapstore/configs/localConfig.json |
im not sure this error messages is related to the scaling issue you see when printing (after all its just a warning), but it seems the existing config.yaml isnt accepted by the backend. |
Yes you're right @landryb , it is not linked because I have the same message with a "good" PDF. So It 's difficult for me to track the scaling issue becaus e I don't see anything in the console's browser neither in Mapstore logs.
I don't remember but I think, I am using a copy of the mapfishapp config.yaml |
@catmorales I don't think the rotation parameter can be used inside the config.yaml used by MS. It is supported by the print lib used by MS but it is not currently supported by the frontend application: it is not sent in the body of the print request, therefore I think this error is normal. |
Dear @catmorales, I've checked and the rotation parameter is effectively present both in the body of the create.json request (always set to 0) and in the default config.yaml of MS. I'm sorry about that, my fault. |
News : reducing the number of scales, it works (less than 23 scales) ! |
Ok thank you, when do you think the small bug will be fixed ? |
Since this issue is linked in the list of things for MS4, last time I've commented I've put also an estimate there for the fix. |
So, if I understand well, you will fix it with issue #582 |
#582 is another task @catmorales, the issue is this one and estimated are at row 38 of the shared document. Anyway, since it seems you have found a way to workaround the original topic involving annotation reported at row 38, you can maybe create a new issue describing that problem and put it in the shared document so that we can finally estimate it too. |
Print layer with visibility limits applied #585
@tdipisa Thank you very much for the correction. |
@catmorales the stable branch has been already updated 2w ago with this fix. We have in plan to release v2022.02.02-geOrchestra shortly. As par of this we will publish the updated docker image. I will keep you posted on the progress. |
@catmorales the new release is available here. |
Thanks a lot @tdipisa. We will test it asa. |
Describe the bug
Print maps at specific scales (between 1:4000 and 1:100) don't work.
It is a regression.
We didn't change the config.yaml parameter and with the last release, printing on specific scales don't work
To Reproduce
Steps to reproduce the behavior:
Preview is ok, Print --> pdf is bad scale is not the good one
Expected behavior
Print the map at the scale selected in the list
Desktop (please complete the following information):
MapStore2-geOrchestra :2022.02.xx(b08b95fc)
MapStore2 :2022.02.xx(15c07932)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: