-
Notifications
You must be signed in to change notification settings - Fork 5
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
Figure idea: visual variables #12
Comments
That's a great idea! I thought about another column 4. rasters, but this is essentially the same as column 3. Those 3 or 4 should cover all bases. There will be a couple of empty table cells: 2.3, 3,3, and 3.4. |
Awesome. Could you try to make it happen? PS: For now, I decided to treat width as size (you can find how I explain that in the book), but I am open to discussion if you want to use width as a different category. |
I will:-) Yes, I agree that width is treated as size. An interesting note is that the non-contiguous cartogram can be regarded as symbols rather than polygons, where the shape corresponds to feature (with a 1:1 mapping provided that no two features have a similar shape) and the size to a numeric data variable. |
I've added the figure. I had to do some tricks to get the legends wide enough. Probably, tmap could benefit from that as well. Great progress on chapter 5, btw. |
The figure is awesome - thanks @mtennekes |
Hi @mtennekes - I totally forgot about rasters for this figure. Should we add them to the right side of the figure or just change the column name "Polygons" to "Polygons/Rasters"? |
I have an idea for a figure explaining visual variables. It could be a grid with three columns and four rows:
Each example could be directly taken from a tmap plots' legends. For more details - visit the Visual Variables section in chapter 5. What do you think about it, @mtennekes ?
The text was updated successfully, but these errors were encountered: