QGIS change legend symbol size independent of map
I'm using QGIS 2.18. The screenshot below shows the print composer.
At the moment, the only way I can reduce the size of symbols in the print composer is to reduce the size of the symbol on the map.
In the attached, the green star symbol in the print composer legend is huge. How can I reduce the size of the green star symbol in the print composer legend, but keep the size of the green star the same on the map?
qgis symbology print-composer legend
add a comment |
I'm using QGIS 2.18. The screenshot below shows the print composer.
At the moment, the only way I can reduce the size of symbols in the print composer is to reduce the size of the symbol on the map.
In the attached, the green star symbol in the print composer legend is huge. How can I reduce the size of the green star symbol in the print composer legend, but keep the size of the green star the same on the map?
qgis symbology print-composer legend
1
I think the issue is raised from the fact that you're creating a plan, not a map. From my (brief) time in architecture, trees weren't symbolized more than they were represented as drawing objects with defined dimensions (mostly the diameter). Symbology and semiology have rules that we must adhere to that applies to abstract representations of objects. In this case you're trying to show the relative sizes of the trees and I feel creating actual objects instead of symbolizing them would work better.
– Gabriel C.
Jan 28 at 19:05
add a comment |
I'm using QGIS 2.18. The screenshot below shows the print composer.
At the moment, the only way I can reduce the size of symbols in the print composer is to reduce the size of the symbol on the map.
In the attached, the green star symbol in the print composer legend is huge. How can I reduce the size of the green star symbol in the print composer legend, but keep the size of the green star the same on the map?
qgis symbology print-composer legend
I'm using QGIS 2.18. The screenshot below shows the print composer.
At the moment, the only way I can reduce the size of symbols in the print composer is to reduce the size of the symbol on the map.
In the attached, the green star symbol in the print composer legend is huge. How can I reduce the size of the green star symbol in the print composer legend, but keep the size of the green star the same on the map?
qgis symbology print-composer legend
qgis symbology print-composer legend
asked Jan 28 at 14:54
lucianoluciano
512515
512515
1
I think the issue is raised from the fact that you're creating a plan, not a map. From my (brief) time in architecture, trees weren't symbolized more than they were represented as drawing objects with defined dimensions (mostly the diameter). Symbology and semiology have rules that we must adhere to that applies to abstract representations of objects. In this case you're trying to show the relative sizes of the trees and I feel creating actual objects instead of symbolizing them would work better.
– Gabriel C.
Jan 28 at 19:05
add a comment |
1
I think the issue is raised from the fact that you're creating a plan, not a map. From my (brief) time in architecture, trees weren't symbolized more than they were represented as drawing objects with defined dimensions (mostly the diameter). Symbology and semiology have rules that we must adhere to that applies to abstract representations of objects. In this case you're trying to show the relative sizes of the trees and I feel creating actual objects instead of symbolizing them would work better.
– Gabriel C.
Jan 28 at 19:05
1
1
I think the issue is raised from the fact that you're creating a plan, not a map. From my (brief) time in architecture, trees weren't symbolized more than they were represented as drawing objects with defined dimensions (mostly the diameter). Symbology and semiology have rules that we must adhere to that applies to abstract representations of objects. In this case you're trying to show the relative sizes of the trees and I feel creating actual objects instead of symbolizing them would work better.
– Gabriel C.
Jan 28 at 19:05
I think the issue is raised from the fact that you're creating a plan, not a map. From my (brief) time in architecture, trees weren't symbolized more than they were represented as drawing objects with defined dimensions (mostly the diameter). Symbology and semiology have rules that we must adhere to that applies to abstract representations of objects. In this case you're trying to show the relative sizes of the trees and I feel creating actual objects instead of symbolizing them would work better.
– Gabriel C.
Jan 28 at 19:05
add a comment |
1 Answer
1
active
oldest
votes
I suggest to :
Duplicate the layer (Right click on it in the layer panel and duplicate)
Give a small size to the duplicated layer
Refresh in the print composer ( you will have two "Coniferous Tree" Layers)
Uncheck the "Auto Update button", select the Bigger layer and remove it from the legend
Thanks that feels like a workaround rather than a solution. Is there not a direct solution?
– luciano
Jan 28 at 16:09
2
@luciano I'd invite you to take a look at this nice primer on legends in cartography (but it applies to statistics in general, too). The important part:Legends should ALWAYS explain symbology exactly as it looks on the map. Legend symbols should be exactly the same size, orientation, color, etc. as they appear on the map.
This is probably the main reason why it is not a feature and requires workarounds to achieve.
– Gabriel C.
Jan 28 at 18:50
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f310165%2fqgis-change-legend-symbol-size-independent-of-map%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I suggest to :
Duplicate the layer (Right click on it in the layer panel and duplicate)
Give a small size to the duplicated layer
Refresh in the print composer ( you will have two "Coniferous Tree" Layers)
Uncheck the "Auto Update button", select the Bigger layer and remove it from the legend
Thanks that feels like a workaround rather than a solution. Is there not a direct solution?
– luciano
Jan 28 at 16:09
2
@luciano I'd invite you to take a look at this nice primer on legends in cartography (but it applies to statistics in general, too). The important part:Legends should ALWAYS explain symbology exactly as it looks on the map. Legend symbols should be exactly the same size, orientation, color, etc. as they appear on the map.
This is probably the main reason why it is not a feature and requires workarounds to achieve.
– Gabriel C.
Jan 28 at 18:50
add a comment |
I suggest to :
Duplicate the layer (Right click on it in the layer panel and duplicate)
Give a small size to the duplicated layer
Refresh in the print composer ( you will have two "Coniferous Tree" Layers)
Uncheck the "Auto Update button", select the Bigger layer and remove it from the legend
Thanks that feels like a workaround rather than a solution. Is there not a direct solution?
– luciano
Jan 28 at 16:09
2
@luciano I'd invite you to take a look at this nice primer on legends in cartography (but it applies to statistics in general, too). The important part:Legends should ALWAYS explain symbology exactly as it looks on the map. Legend symbols should be exactly the same size, orientation, color, etc. as they appear on the map.
This is probably the main reason why it is not a feature and requires workarounds to achieve.
– Gabriel C.
Jan 28 at 18:50
add a comment |
I suggest to :
Duplicate the layer (Right click on it in the layer panel and duplicate)
Give a small size to the duplicated layer
Refresh in the print composer ( you will have two "Coniferous Tree" Layers)
Uncheck the "Auto Update button", select the Bigger layer and remove it from the legend
I suggest to :
Duplicate the layer (Right click on it in the layer panel and duplicate)
Give a small size to the duplicated layer
Refresh in the print composer ( you will have two "Coniferous Tree" Layers)
Uncheck the "Auto Update button", select the Bigger layer and remove it from the legend
edited Jan 28 at 15:38
answered Jan 28 at 15:31
Yannick DOUNGMOYannick DOUNGMO
466
466
Thanks that feels like a workaround rather than a solution. Is there not a direct solution?
– luciano
Jan 28 at 16:09
2
@luciano I'd invite you to take a look at this nice primer on legends in cartography (but it applies to statistics in general, too). The important part:Legends should ALWAYS explain symbology exactly as it looks on the map. Legend symbols should be exactly the same size, orientation, color, etc. as they appear on the map.
This is probably the main reason why it is not a feature and requires workarounds to achieve.
– Gabriel C.
Jan 28 at 18:50
add a comment |
Thanks that feels like a workaround rather than a solution. Is there not a direct solution?
– luciano
Jan 28 at 16:09
2
@luciano I'd invite you to take a look at this nice primer on legends in cartography (but it applies to statistics in general, too). The important part:Legends should ALWAYS explain symbology exactly as it looks on the map. Legend symbols should be exactly the same size, orientation, color, etc. as they appear on the map.
This is probably the main reason why it is not a feature and requires workarounds to achieve.
– Gabriel C.
Jan 28 at 18:50
Thanks that feels like a workaround rather than a solution. Is there not a direct solution?
– luciano
Jan 28 at 16:09
Thanks that feels like a workaround rather than a solution. Is there not a direct solution?
– luciano
Jan 28 at 16:09
2
2
@luciano I'd invite you to take a look at this nice primer on legends in cartography (but it applies to statistics in general, too). The important part:
Legends should ALWAYS explain symbology exactly as it looks on the map. Legend symbols should be exactly the same size, orientation, color, etc. as they appear on the map.
This is probably the main reason why it is not a feature and requires workarounds to achieve.– Gabriel C.
Jan 28 at 18:50
@luciano I'd invite you to take a look at this nice primer on legends in cartography (but it applies to statistics in general, too). The important part:
Legends should ALWAYS explain symbology exactly as it looks on the map. Legend symbols should be exactly the same size, orientation, color, etc. as they appear on the map.
This is probably the main reason why it is not a feature and requires workarounds to achieve.– Gabriel C.
Jan 28 at 18:50
add a comment |
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f310165%2fqgis-change-legend-symbol-size-independent-of-map%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I think the issue is raised from the fact that you're creating a plan, not a map. From my (brief) time in architecture, trees weren't symbolized more than they were represented as drawing objects with defined dimensions (mostly the diameter). Symbology and semiology have rules that we must adhere to that applies to abstract representations of objects. In this case you're trying to show the relative sizes of the trees and I feel creating actual objects instead of symbolizing them would work better.
– Gabriel C.
Jan 28 at 19:05