Forum Replies Created
-
Posts
-
I’m revisiting this post now because I have a dataset in CODAP where having an auto detected URL data type, as well as an image data type, would be really nice. See here: https://bit.ly/AIfeederDataMA . The column/attribute name is “link to screenshot.” I could see also an attribute for the screenshot itself. I’m not sure how this would work in table form, but I could see it in case card view. Perhaps the image of the screenshot could be put at the top or bottom of the card, something like the attached image below that I quickly mocked up.
I realized it would likely be more helpful to have these formulas use more generic attribute names (“Day,” “Month,” “Year” and “Date”) so you could copy/paste the formulas into other CODAP documents without potentially having to change anything in the formulas. So I updated this demo document accordingly. See here.
I realized it might be useful to see the formulas for more generic attribute names, so here goes:If you have 3 columns/attributed titled “Day”, “Month”, and “Year”, use this formula (make sure month is indicated as a number like 12, NOT “December”, and for Year, give 4 digits, for example 2024, NOT 24):
Day+if(Month> 1, 31, 0) +if(Month> 2, 28, 0) +if(Month> 3, 31, 0) +if(Month> 4, 30, 0) +if(Month> 5, 31, 0) +if(Month> 6, 30, 0) +if(Month> 7, 31, 0) +if(Month> 8, 31, 0) +if(Month> 9, 31, 0) +if(Month> 10, 31, 0) +if(Month> 11, 30, 0) +if(frac(Year/ 4) = 0 &Year> -47 & frac(Month/ 100) != 0 or frac(Month/ 400) = 0, 1, 0)If you have 1 column of date attribute type titled “Date”, use this formula:dayOfMonth(Date) +if(month(Date) > 1, 31, 0) +if(month(Date) > 2, 28, 0) +if(month(Date) > 3, 31,0) +if(month(Date) > 4, 30, 0) +if(month(Date) > 5, 31, 0) +if(month(Date) > 6, 30, 0) +if(month(Date) > 7, 31, 0) +if(month(Date) > 8, 31, 0) +if(month(Date) > 9, 31, 0) +if(month(Date) > 10, 31, 0) +if(month(Date) > 11, 30, 0) +if(year(Date) < -46, 0,if(frac(year(Date) / 400) = 0, 1,if(frac(year(Date) / 100) = 0, 0,if(frac(year(Date) / 4) = 0, 1, 0))))Here’s a new CODAP link to use (in the previous one, I forgot to take daylight saving time into account): https://codap.concord.org/app/static/dg/en/cert/index.html#shared=https%3A%2F%2Fcfm-shared.concord.org%2FKwvW902nIkhhp2yjUTzF%2Ffile.json
In certain circumstances, one could maybe just use a graph with parent visibility toggles to keep track of the subset you are looking at. Another option could be using the StoryBuilder plugin to track/write notes documenting the filtering processing. Or one could write a description of the filtering process in a text box. Although these are not automatically generated histories.
One thought/idea: would it be possible to have parent visibility toggles (or something like them) work on tables in CODAP too, in addition to graphs? (also what about maps? I thought they worked on maps but apparently not). It strikes me that this these toggles are kind of like the check boxes you can use for filtering a table in Excel (and consult later to see exactly what you are/are not seeing in the table). If there were parent visibility toggles (or something like them) for tables in CODAP, it would be pretty quick/easy to determine what has been filtered out.
There is a CODAP/NetLogo integration guide here. I’m not sure if you have looked at it already or if it might help with the issue you are encountering–maybe someone else with more experience with embedding NetLogo in CODAP could chime in here too?
There is quite a lot of info now on the getting started with maps page that may be of help as well: https://codap.concord.org/help/basics/maps
For latitude and longitude attributes, they must be named latitude and longitude (or lat, lon, or long) for the map to display properly.
We recently made a video tutorial that may be helpful to you, if you are looking to add boundaries to the map that are not already in CODAP: https://www.youtube.com/watch?v=3VHTb9giboE
Also, if you can’t find a GeoJSON with the boundaries you want by googling, you can create one yourself for regions you select here: https://support.planet.com/hc/en-us/articles/360016337117-Creating-a-GeoJSON-file
If you are curious about how to do this yourself, I recently made a video tutorial on how to get boundaries that are not included by default in CODAP onto maps in CODAP: https://www.youtube.com/watch?v=3VHTb9giboE
Another thing that is not in this video is you can create your own GeoJSON file if you can’t find a pre-existing one you want by searching online, drawing your own custom boundaries, and then importing that GeoJSON file into CODAP. Here is a site I used with guidance that helped me create my own GeoJSON boundaries for two small islands off the coast of Maine that I then imported into CODAP: https://support.planet.com/hc/en-us/articles/360016337117-Creating-a-GeoJSON-file
Just played around with this some more. If I upload a CSV with a date in the format such as “June 19, 2010” as shown below, and do not specify that the attribute type as date in CODAP, I can make a graph that displays the date properly. Also, I can sort the data in chronological order and then add connecting lines that appear properly to a graph with date on the X axis and another attribute on the Y axis, all without specifying date data type for the date attribute (see second image below). So there are workarounds, it seems.
Attachments:
Thank you Bill! A somewhat related question I am now wondering about is how numeric data displays in the table/on the graph. It seems if you specify numeric, commas will be added to the numbers at 10,000 and above in the table and on the graph, but there would be no easy way to have a number below 10,000 display as, say “5,000”–is that correct? Thanks again.
