Forum Replies Created
-
Posts
-
Something like this: https://codap.concord.org/app/#shared=44494 ?
It groups the years as subgroups of states. I made it using the Attribute Stacker plugin: https://concord-consortium.github.io/codap-data-interactives//AttributeStacker/index.html .
Regards,
Jonathan
Hi Anna,
Thank you for your excellent description of this issue. It is clearly a bug. I have filed a bug report (https://www.pivotaltracker.com/story/show/158236735). I hope we can have a fix, soon.
Jonathan
Hi Cristían,
Thank you for reporting this. The video is especially helpful. I am sorry you are having this difficulty with CODAP, though.
I can’t say I understand what is going on. When I try the same thing here, with either the English or Spanish version, I see a proper image in the Draw Tool. We will keep trying, though.
I noticed one interesting thing from the video, though. The draw tool borders, when it opened, was not sized to fit the drawing canvas. That is an indication that the Draw Tool plugin was not able to communicate with CODAP. Normally, when the Draw Tool or any other CODAP plugin starts, it tells CODAP how big a window to make. I could not see from the video what the exact URL was. This may provide a clue as to why CODAP was unable to communicate. If you would be so kind as to provide the exact URL, this could be very helpful.
Thanks,
Jonathan Sandoe
Hi Joachim,
There is a CODAP plugin to facilitate simple Web Scraping, the awkwardly named “Drop HTML Table” plugin. You drag the plugin into your CODAP document. In another browser page, select the table that you want to scrape and copy it. (Control-C on windows, Command-C on macs) Then, paste it into the designated window in the plugin. You should see the contents of any table that the plugin could find. You can pick the ones you want and import into CODAP.
The plugin may or may not be able to identify tabular data in the HTML fragment that you paste. This depends on the structure of the HTML in the original page. Sometimes the structure doesn’t match any of the patterns that the plugin recognizes.
Jonathan
Hi Cristián,
I have not been able to reproduce the bug in any of the browsers I have available to me. However, I have a potential fix. Would you be so kind as to go to this version of CODAP and try to capture an image? If you can, please let us know if you still see the error. My hypothesis is that you will not, but the image in the draw tool may not look like the original.
Thanks,
Jonathan
Hi Cristián,
The problem looks like it is a consequence of Chrome tightening its security policy. The particular circumstance referred to in the link you referenced is not applicable to CODAP, but something similar must be in play.
The problem seems to have arisen with Chrome version 64. You said you were on the latest version of Chrome. Just to confirm, what is the version number reported by the “About Google Chrome” menu item?
Thanks,
Jonathan
Hi Max,
I suspect the problem is one of character encoding. CODAP expects CSV files to have an encoding of UTF-8. This is a standard encoding and will work for many cases. It is likely that your CSV file was encoded with a different character encoding.
If you created the CSV file from some other data source then the tool you used to create the file may give you the ability to specify the encoding. If you only have the CSV file, there are tools available to convert the files, depending on your computer type. On Macs, for example there is a command line tool called “iconv”.
Jonathan
Hi Cristián,
We are aware of many of the issues with date formatting in CODAP. We will address them when we can, but I can’t say how soon this will be. I apologize for this.
We do support the international standard date format for date input (ISO 8601, https://en.wikipedia.org/wiki/ISO_8601), but unfortunately the output in the case table will be formatted for the en-US locale.
A question: there is a similar issue with decimal separators. CODAP expects periods as decimal separators, many countries use commas. Is that an issue for your use of CODAP?
Jonathan
Hi Donna,
I took a look at the Foobot API (http://api.foobot.io/apidoc/index.html). It looks pretty straightforward, although its not clear through the documentation how to get an API key if you don’t have an account nor how to get an account if you don’t have a device. Conceptually, though, the API is close to a lot of other cloud APIs that work well with CODAP. To give you a sense of this, here is a CODAP document that accesses periodically the USGS database of recent earthquakes of magnitude 2.5 or more: https://codap.concord.org/app/#shared=36160 . Although it is a quite different subject matter, it is, with respect to being “live”, similar to the application you have in mind, as I understand it.
Jonathan
Interesting!
So, if I understand, the idea would be to pull into CODAP current or recent data for the family’s sensor periodically. Is that right? This is doable by creating a CODAP plugin. If you have Javascript skills or have someone available with Javascript skills, this is not difficult. Here are a couple of documents to get started: https://github.com/concord-consortium/codap/wiki/Getting-Started-With-CODAP-Plugins, and https://github.com/concord-consortium/codap/wiki/CODAP-Data-Interactive-Plugin-API.
Jonathan
I am curious what sensors are involved (e.g. manufacturer and type) and how they connect to the computer (e.g. USB, bluetooth, …). With the Excel lessons, do the sensors directly interface to Excel or do they, for example, write to a CSV file? In all likelihood integrating with CODAP is going to involve a plugin. There may be one already available, though.
(my previous post came out somewhat garbled for some reason. What follows is a cleaned up version.)
I am sorry you are having difficulty installing the CODAP development environment on your computer. Its a little difficult for me to understand what may have caused this failure. Had you run “npm install” prior to running “npm run build:bundle”. The install instructions recommend installing cygwin or a shell with similar functionality on Windows systems. This may help. Also, you may wish to try running “yarn” instead of “npm install” since it is more precise on versioning. To install “yarn”, run “npm install -g yarn”.
We do not see the issue you are seeing when we execute the install procedure on our Windows machines, here. What version of Windows are you using?
I am interested what type of development work you are contemplating involving CODAP. Many interesting things can be done by writing a CODAP plugin. You can integrate new data sources or create new data visualizations this way. Developing a plugin does not require setting up a full CODAP development environment. You can download the current version of CODAP from https://codap.concord.org/releases/zips and install it on a local web server. Documents on the CODAP wiki (https://github.com/concord-consortium/codap/wiki) can help you get started. In particular, the API document (https://github.com/concord-consortium/codap/wiki/CODAP-Data-Interactive-Plugin-API) and this tutorial: https://github.com/concord-consortium/codap/wiki/Getting-Started-With-CODAP-Plugins.
Thanks for your interest.
Hello Max,
<div style=”color: #222222; font-family: arial, sans-serif; font-size: 12.8px;”>I am sorry you are having difficulty installing the CODAP development environment on your computer. Its a little difficult for me to understand what may have caused this failure. Had you run “npm install” prior to running “npm run build:bundle”. The install instructions recommend installing cygwin or a shell with similar functionality on Windows systems. This may help. Also, you may wish to try running “yarn” instead of “npm install” since it is more precise on versioning. To install “yarn”, run “npm install -g yarn”.</div>
<div style=”color: #222222; font-family: arial, sans-serif; font-size: 12.8px;”></div>
<div style=”color: #222222; font-family: arial, sans-serif; font-size: 12.8px;”>We do not see the issue you are seeing when we execute the install procedure on our Windows machines, here. What version of Windows are you using?</div>
<div style=”color: #222222; font-family: arial, sans-serif; font-size: 12.8px;”></div>
<div style=”color: #222222; font-family: arial, sans-serif; font-size: 12.8px;”>I am interested what type of development work you are contemplating involving CODAP. Many interesting things can be done by writing a CODAP plugin. You can integrate new data sources or create new data visualizations this way. Developing a plugin does not require setting up a full CODAP development environment. You can download the current version of CODAP from https://codap.concord.org/<wbr />releases/zips and install it on a local web server. Documents on the CODAP wiki (https://github.com/concord-<wbr />consortium/codap/wiki) can help you get started. In particular, the API document (https://github.com/concord-<wbr />consortium/codap/wiki/CODAP-<wbr />Data-Interactive-Plugin-API) and this tutorial: https://github.com/<wbr />concord-consortium/codap/wiki/<wbr />Getting-Started-With-CODAP-<wbr />Plugins.</div>
<div style=”color: #222222; font-family: arial, sans-serif; font-size: 12.8px;”></div>
<div style=”color: #222222; font-family: arial, sans-serif; font-size: 12.8px;”>Thanks for your interest.</div>
<div class=”yj6qo ajU” style=”cursor: pointer; outline: none; padding: 10px 0px; width: 22px; margin: 2px 0px 0px; color: #222222; font-family: arial, sans-serif; font-size: 12.8px;”></div>Hi Michelle,
Thanks for the post. Currently, CODAP doesn’t support Connecting Lines for attributes on the right-hand side of the graph. I think the fall-back would be to create a second graph with the same x axis, but the right-hand y-axis attribute on the left. Not ideal, but at least you could compare the shapes of the two y-attributes.
Out of curiosity, would you say that the need for connecting lines for right-axis attributes was a common one? Should it be higher on our to-do list?
Jonathan
