-
Notifications
You must be signed in to change notification settings - Fork 15
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
BGDIDIC-706: update legends #4426
Conversation
1471dce
to
848e889
Compare
imo the text is to small |
For sure, but how to make in text in many lines? Is there a way to insert carriage return or other known "tricks"? |
@rebert @faselm that was exactly what my concern about the removal of the character 255 limitation was about, i think we should try to understand why the dataowner needs more than 255 character for a class or attribute name. |
Maybe the dataowner can create the legends itself, that way it can put as many characters as it wants as long as the 480px is respected.. |
or the contextual info can be added as text in the infobox... |
I think it's already the case, the legend and infobox have exactly the same texts as far as I can see.. |
These layers are strange by the way. Data for the legends are missing in the ms_class table (not sure how the legends have been created back then) and why a legend would have the same text as a infobox sounds strange to me as well.. |
No description provided.