r-tmap
Improve the break labels in tmap4
Source: https://twitter.com/profrichharris/status/1637481477242855424
Also: https://twitter.com/dev_333/status/1638426993485303808
Hi @profrichharris and @trydave (and others)
Thanks for raising this issue on Twitter
The classes are indeed 10 to <20, 20 to <30, because the underlying argument interval.closure is set to "left" by default.
The main question is: how to label these classes. I find "10 to <20" a bit odd. Do you have any suggestions? In Dutch (my native non-programming language) there is a clear distinction between "10 tot 20" (meaning "10 to (and excluding) 20") and "10 tot en met 20" (meaning "10 to and including 20").
To be clear: we are talking about continuous data. For integers, we can have 10 to 19, 20 to 29, etc.
Hi all,
Thanks for following up.
In the UK, and in maths, students are taught that you can't have classes that say, for example, 10 - 20, 20 - 30, etc. because it isn't clear which class the 20 (and 30, etc.) is in. Unfortunately, what is happening when people use tmap with continuous data and the default settings is that they are producing maps with classes that referees like me then ask them to change!
It should really be something like 10 to <20, 20 to <30, which makes clear that the 20 is in the second group, not the first. Alternatively, we could use different types of brackets, although I think this is less obvious: (10 - 20], (20 - 30]. Unfortunately, in English, 10 to 20, 20 to 30 doesn't work because it still isn't clear which the 20 is in.
It's a pretty minor thing though! Perhaps put it 'out there' to the user community on Twitter or something and see what it thinks?
@Christopher @.***>, any thoughts?
V best, and thanks again, Rich
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
From: mtennekes @.> Sent: Tuesday, April 18, 2023 8:31:41 AM To: r-tmap/tmap @.> Cc: Richard Harris @.>; Mention @.> Subject: Re: [r-tmap/tmap] Improve the break labels in tmap4 (Issue #717)
Hi @profrichharrishttps://github.com/profrichharris and @trydavehttps://github.com/trydave (and others)
Thanks for raising this issue on Twitter
The classes are indeed 10 to <20, 20 to <30, because the underlying argument interval.closure is set to "left" by default. The main question is: how to label these classes. I find "10 to <20" a bit odd. Do you have any suggestions? In Dutch (my native non-programming language) there is a clear distinction between "10 tot 20" (meaning "10 to (and excluding) 20") and "10 tot en met 20" (meaning "10 to and including 20").
To be clear: we are talking about continuous data. For integers, we can have 10 to 19, 20 to 29, etc.
— Reply to this email directly, view it on GitHubhttps://github.com/r-tmap/tmap/issues/717#issuecomment-1512592741, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJAPKOIH4JZI57AL3CCIJ3XBY7N3ANCNFSM6AAAAAAWFPZD54. You are receiving this because you were mentioned.Message ID: @.***>
Hi all - Just a couple of thoughts. One - from my mathematical background is to use the [a,b) notation - meaning the set of reals numbers from a, up to but not including b - similar notation exists for (a,b], (a,b), and [a,b]. Thus use [10,20), [20,30) etc. The problem here is that this requires the map user to be familiar with this, and I'm not sure I saw it until reading for a degree in mathematics! Perhaps an english language alternative to the Dutch suggestion is 10 to below 20, 20 to below 30 and so on?
Chris
On 18 Apr 2023, at 08:52, Richard Harris @.@.>> wrote:
Warning This email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe. Hi all,
Thanks for following up.
In the UK, and in maths, students are taught that you can't have classes that say, for example, 10 - 20, 20 - 30, etc. because it isn't clear which class the 20 (and 30, etc.) is in. Unfortunately, what is happening when people use tmap with continuous data and the default settings is that they are producing maps with classes that referees like me then ask them to change!
It should really be something like 10 to <20, 20 to <30, which makes clear that the 20 is in the second group, not the first. Alternatively, we could use different types of brackets, although I think this is less obvious: (10 - 20], (20 - 30]. Unfortunately, in English, 10 to 20, 20 to 30 doesn't work because it still isn't clear which the 20 is in.
It's a pretty minor thing though! Perhaps put it 'out there' to the user community on Twitter or something and see what it thinks?
@Christopher @.***>, any thoughts?
V best, and thanks again, Rich
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
From: mtennekes @.@.>> Sent: Tuesday, April 18, 2023 8:31:41 AM To: r-tmap/tmap @.@.>> Cc: Richard Harris @.@.>>; Mention @.@.>> Subject: Re: [r-tmap/tmap] Improve the break labels in tmap4 (Issue #717)
Hi @profrichharrishttps://github.com/profrichharris and @trydavehttps://github.com/trydave (and others)
Thanks for raising this issue on Twitter
The classes are indeed 10 to <20, 20 to <30, because the underlying argument interval.closure is set to "left" by default. The main question is: how to label these classes. I find "10 to <20" a bit odd. Do you have any suggestions? In Dutch (my native non-programming language) there is a clear distinction between "10 tot 20" (meaning "10 to (and excluding) 20") and "10 tot en met 20" (meaning "10 to and including 20").
To be clear: we are talking about continuous data. For integers, we can have 10 to 19, 20 to 29, etc.
— Reply to this email directly, view it on GitHubhttps://github.com/r-tmap/tmap/issues/717#issuecomment-1512592741, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJAPKOIH4JZI57AL3CCIJ3XBY7N3ANCNFSM6AAAAAAWFPZD54. You are receiving this because you were mentioned.Message ID: @.***>