Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Hi Victor, Thanks for your reply. The marker size/rotation expression don' not actually exists, like the marker size/rotation. You can define different size/rotation expressions at the symbol level. Each symbol can have it's own variation. It's only in the particular case where the scale/rotation expressions of all symbols composing a marker preserve the aspect ratio of the symbol that it is recognized as a marker expression and displayed as such. Thanks - sounds good. As it works currently, I get a very different rendering in the map, compared to the preview in the legend ;-( Can you file a bug repport for this if it's not fixed by https://github.com/qgis/QGIS/pull/2111 ? Will do, once I tested. I have one more big problem: This mechanism - for some reasons I don't know yet - does not work on QGIS server. All the symbols that are correctly scaled on QGIS desktop are displayed small and of the same size on QGIS server (yes, I am using the latest version of QGIS server). It seems that the expressions are not evaluated on QGIS server, but just the initial standard size is used instead of the impression. See http://webgis.uster.ch/temp/qgis_server_rendering_problem_symbol_scaling.png (left QGIS desktop, right QGIS server) Can you confirm that this is the case? And if yes, can we do something about it? It would be a pity - because I always tell people they get the exact same rendering between Server and Desktop ... If confirmed, I will open a bug report. Thanks a lot for your work! Andreas ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Hi Andreas, On 02/06/2015 16:07, Andreas Neumann wrote: I found another issue with the new scaling method: For multi level point symbols we need to be able to define the scaling on the symbol level. However, when adding it on the symbol level, the same rule applies both on the parent marker and on the individual symbol level. What if one part of the symbol should be scaled differently than the other? We really need this to work on the indivual symbol levels, not on the parent marker - or at least make it optional that it scales the parent as well. The marker size/rotation expression don' not actually exists, like the marker size/rotation. You can define different size/rotation expressions at the symbol level. Each symbol can have it's own variation. It's only in the particular case where the scale/rotation expressions of all symbols composing a marker preserve the aspect ratio of the symbol that it is recognized as a marker expression and displayed as such. As it works currently, I get a very different rendering in the map, compared to the preview in the legend ;-( Can you file a bug repport for this if it's not fixed by https://github.com/qgis/QGIS/pull/2111 ? Thanks, V. Andreas On 02.06.2015 15:53, Andreas Neumann wrote: Hi, Thanks for explaining. The assistant is very nice and a welcome improvement! Thanks for investing and working on it. I had an issue that I had a size defined in 2.8.x with scaling by area which, when opened in QGIS master displayed much bigger. Once I changed that in 2.8x to scale by diameter the symbol sizes are identical in master. So there seems to be an issue with converting scale by area symbol sizes from 2.8 over to QGIS master. Should I open a bug report or is one open already? Thanks, Andreas On 01.06.2015 20:05, Régis Haubourg wrote: Hi, here are the ideas behind this work, Nyall (code reviewer) and Vincent (author) could explain implentation choices more than me (funder): - get a more consistent UI with data defined widgets, and not advanced fields. That way, size is in one place only. - offer an assistant on size varying common expression. You will find it at the bottom of the drop down widget. It computes max value from field or expression and allows normal user to do what other GIS do. - That assistant offer legend previsualisation, and generates a legend for map and composer. I wish we have a legend for any expression... - During implementation, we understood that symbol size was a multiplication factor of size varying factor. That implied that it was impossible to predict final screen size. The new implementation clears that up. - offer a size varying graduated renderer, allowing the use of classifications algorithms - offer a legend for diagrams (yes!) IMHO, we need to read previous versions correctly, but that sometimes need to read all features to retroengineer a size expression. Vincent have planned to polish that now that feature freeze is made. All that needs testing of course. I'm not totally satisfied with the assistant shortcut, hidden inside the size varying widget. If someone have a better UI idea.. Hope that helps clarifying those changes. Cheers Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5208525.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Yep, I have it too. Will file a ticket. Cheers Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5209109.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Hi, I noticed that my problem with the invalid scaling only occurs if I use layers from old QGIS versions (2.8). If I create a new layer with new symbology, this works fine. So, definitely a migration issue from old project versions, esp. if scale by area was active. Thanks, Andreas On 02.06.2015 16:07, Andreas Neumann wrote: I found another issue with the new scaling method: For multi level point symbols we need to be able to define the scaling on the symbol level. However, when adding it on the symbol level, the same rule applies both on the parent marker and on the individual symbol level. What if one part of the symbol should be scaled differently than the other? We really need this to work on the indivual symbol levels, not on the parent marker - or at least make it optional that it scales the parent as well. As it works currently, I get a very different rendering in the map, compared to the preview in the legend ;-( Andreas On 02.06.2015 15:53, Andreas Neumann wrote: Hi, Thanks for explaining. The assistant is very nice and a welcome improvement! Thanks for investing and working on it. I had an issue that I had a size defined in 2.8.x with scaling by area which, when opened in QGIS master displayed much bigger. Once I changed that in 2.8x to scale by diameter the symbol sizes are identical in master. So there seems to be an issue with converting scale by area symbol sizes from 2.8 over to QGIS master. Should I open a bug report or is one open already? Thanks, Andreas On 01.06.2015 20:05, Régis Haubourg wrote: Hi, here are the ideas behind this work, Nyall (code reviewer) and Vincent (author) could explain implentation choices more than me (funder): - get a more consistent UI with data defined widgets, and not advanced fields. That way, size is in one place only. - offer an assistant on size varying common expression. You will find it at the bottom of the drop down widget. It computes max value from field or expression and allows normal user to do what other GIS do. - That assistant offer legend previsualisation, and generates a legend for map and composer. I wish we have a legend for any expression... - During implementation, we understood that symbol size was a multiplication factor of size varying factor. That implied that it was impossible to predict final screen size. The new implementation clears that up. - offer a size varying graduated renderer, allowing the use of classifications algorithms - offer a legend for diagrams (yes!) IMHO, we need to read previous versions correctly, but that sometimes need to read all features to retroengineer a size expression. Vincent have planned to polish that now that feature freeze is made. All that needs testing of course. I'm not totally satisfied with the assistant shortcut, hidden inside the size varying widget. If someone have a better UI idea.. Hope that helps clarifying those changes. Cheers Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5208525.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Issue created here http://hub.qgis.org/issues/12876 http://hub.qgis.org/issues/12876 with sample data and project files for testing purposes. Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5209138.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
I found another issue with the new scaling method: For multi level point symbols we need to be able to define the scaling on the symbol level. However, when adding it on the symbol level, the same rule applies both on the parent marker and on the individual symbol level. What if one part of the symbol should be scaled differently than the other? We really need this to work on the indivual symbol levels, not on the parent marker - or at least make it optional that it scales the parent as well. As it works currently, I get a very different rendering in the map, compared to the preview in the legend ;-( Andreas On 02.06.2015 15:53, Andreas Neumann wrote: Hi, Thanks for explaining. The assistant is very nice and a welcome improvement! Thanks for investing and working on it. I had an issue that I had a size defined in 2.8.x with scaling by area which, when opened in QGIS master displayed much bigger. Once I changed that in 2.8x to scale by diameter the symbol sizes are identical in master. So there seems to be an issue with converting scale by area symbol sizes from 2.8 over to QGIS master. Should I open a bug report or is one open already? Thanks, Andreas On 01.06.2015 20:05, Régis Haubourg wrote: Hi, here are the ideas behind this work, Nyall (code reviewer) and Vincent (author) could explain implentation choices more than me (funder): - get a more consistent UI with data defined widgets, and not advanced fields. That way, size is in one place only. - offer an assistant on size varying common expression. You will find it at the bottom of the drop down widget. It computes max value from field or expression and allows normal user to do what other GIS do. - That assistant offer legend previsualisation, and generates a legend for map and composer. I wish we have a legend for any expression... - During implementation, we understood that symbol size was a multiplication factor of size varying factor. That implied that it was impossible to predict final screen size. The new implementation clears that up. - offer a size varying graduated renderer, allowing the use of classifications algorithms - offer a legend for diagrams (yes!) IMHO, we need to read previous versions correctly, but that sometimes need to read all features to retroengineer a size expression. Vincent have planned to polish that now that feature freeze is made. All that needs testing of course. I'm not totally satisfied with the assistant shortcut, hidden inside the size varying widget. If someone have a better UI idea.. Hope that helps clarifying those changes. Cheers Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5208525.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Hi, Thanks for explaining. The assistant is very nice and a welcome improvement! Thanks for investing and working on it. I had an issue that I had a size defined in 2.8.x with scaling by area which, when opened in QGIS master displayed much bigger. Once I changed that in 2.8x to scale by diameter the symbol sizes are identical in master. So there seems to be an issue with converting scale by area symbol sizes from 2.8 over to QGIS master. Should I open a bug report or is one open already? Thanks, Andreas On 01.06.2015 20:05, Régis Haubourg wrote: Hi, here are the ideas behind this work, Nyall (code reviewer) and Vincent (author) could explain implentation choices more than me (funder): - get a more consistent UI with data defined widgets, and not advanced fields. That way, size is in one place only. - offer an assistant on size varying common expression. You will find it at the bottom of the drop down widget. It computes max value from field or expression and allows normal user to do what other GIS do. - That assistant offer legend previsualisation, and generates a legend for map and composer. I wish we have a legend for any expression... - During implementation, we understood that symbol size was a multiplication factor of size varying factor. That implied that it was impossible to predict final screen size. The new implementation clears that up. - offer a size varying graduated renderer, allowing the use of classifications algorithms - offer a legend for diagrams (yes!) IMHO, we need to read previous versions correctly, but that sometimes need to read all features to retroengineer a size expression. Vincent have planned to polish that now that feature freeze is made. All that needs testing of course. I'm not totally satisfied with the assistant shortcut, hidden inside the size varying widget. If someone have a better UI idea.. Hope that helps clarifying those changes. Cheers Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5208525.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Hi, Regarding data-defined symbol size: I noticed that some of my old 2.8x projects display different in QGIS master - the symbols that have a data-defined size with a very simple CASE WHEN rule display much bigger in QGIS master than in the 2.8x branch. So I wonder, what exactly has changed in master regarding symbol size and why? Thanks, Andreas On 31.05.2015 15:27, Régis Haubourg wrote: HI, we are sponsoring Vincent Mora on that and I submitted the issue on Friday. He should be able to work on that in the next few days. Cheers Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5208310.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Hi, here are the ideas behind this work, Nyall (code reviewer) and Vincent (author) could explain implentation choices more than me (funder): - get a more consistent UI with data defined widgets, and not advanced fields. That way, size is in one place only. - offer an assistant on size varying common expression. You will find it at the bottom of the drop down widget. It computes max value from field or expression and allows normal user to do what other GIS do. - That assistant offer legend previsualisation, and generates a legend for map and composer. I wish we have a legend for any expression... - During implementation, we understood that symbol size was a multiplication factor of size varying factor. That implied that it was impossible to predict final screen size. The new implementation clears that up. - offer a size varying graduated renderer, allowing the use of classifications algorithms - offer a legend for diagrams (yes!) IMHO, we need to read previous versions correctly, but that sometimes need to read all features to retroengineer a size expression. Vincent have planned to polish that now that feature freeze is made. All that needs testing of course. I'm not totally satisfied with the assistant shortcut, hidden inside the size varying widget. If someone have a better UI idea.. Hope that helps clarifying those changes. Cheers Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5208525.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
Hi Régis, On Mon, Jun 1, 2015 at 8:05 PM, Régis Haubourg regis.haubo...@eau-adour-garonne.fr wrote: - offer an assistant on size varying common expression. You will find it at the bottom of the drop down widget. It computes max value from field or expression and allows normal user to do what other GIS do. - That assistant offer legend previsualisation, and generates a legend for map and composer. I just tested the assistant for the first time and it's just great! Will definitely test some more and report back. Thanks for your work on this! Best wishes, Anita ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
HI, we are sponsoring Vincent Mora on that and I submitted the issue on Friday. He should be able to work on that in the next few days. Cheers Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Data-defined-symbol-size-is-not-backwards-compatible-to-2-8-2-tp5208256p5208310.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
On Sun, May 31, 2015 at 3:27 PM, Régis Haubourg regis.haubo...@eau-adour-garonne.fr wrote: HI, we are sponsoring Vincent Mora on that and I submitted the issue on Friday. He should be able to work on that in the next few days. Thanks a lot for that Régis! Could you please share a link to the ticket, I failed at finding it. Best wishes, Anita ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data-defined symbol size is not backwards compatible to 2.8.2
On 30 May 2015 11:39 pm, Anita Graser anitagra...@gmx.at wrote: Hi, Can you confirm that data-defined symbol size styles created saved in the dev version are ignored by 2.8.2? If so, I can open a ticket. Hi Anita, It's not backwards compatible, but that's why you get a warning when saving an old project in a newer version of QGIS. We don't support backwards compatibility of projects. Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer