Forum Replies Created
-
AuthorPosts
-
Dan DamelinKeymaster
Unfortunately Google Drive does not provide you a direct link to the csv file, so CODAP can’t import using the share URL Google Drive provides.
If you could post to a server that provides public, web-accessible, direct URLs to files then what you are trying to do would work.
Other options using Google Drive:
- On a Google Sheet you can use File->Share->Publish to web. Then the URL you get from that can be given to students which, when clicked on, will initiate a download of a CSV automatically. Then this can be dragged into CODAP. It eliminates one step from them having to download manually.
- You can copy and paste data from a Google Sheet into CODAP. Give them a link to a Google Sheet. Have them select all (command-a or control-a). Then open CODAP and click the Tables button and choose “–new from clipboard–“
Hope that helps.
Dan DamelinKeymasterAndee, I’d love to hear more about these strategies.
Dan DamelinKeymasterWell, this is not ideal, but if your range for n is limited enough, you could create one table that calculates the various values for n, and then use that table as a lookup for your own n! function. (The lookup table could be closed, so it would not be visible.)
See example here:
Dan DamelinKeymasterI was blocked from uploading the geojson file so here’s a link to it:
Dan DamelinKeymasterI wanted to learn a bit about the geojson format myself, so in playing around I made a version of the file you sent with the boundaries that have thumbnails.
To make this I ended up doing some combination of formulas in excel and cutting and pasting to make the geojson file from the data that was there. Then I imported the geojson into codap, exported that and pasted the new polygon features with added thumbnail over what was there in the csv.
(Bill I tried to join after importing the geojson but could not get that to work correctly.)
Attached is the geojson file I created as well.
Dan DamelinKeymasterAlison,
Unfortunately, given the list of sensors you described, they are all wired sensors, which won’t work using our software on Chromebooks. To directly connect sensors to work in CODAP on Chromebooks you would need sensors from the Go Direct line of wireless sensors.
There is still a possibility to use Vernier’s own software (perhaps Graphical Analysis) to collect data, export it as a CSV file, and then drag it into CODAP. But that might be too cumbersome, especially for that particular activity you mentioned above.
Dan DamelinKeymasterThese links worked for me in multiple browsers, each loading the document within a few seconds. One possibility might be that the school internet filter is now preventing some access to resources being loaded by CODAP. You mentioned that several teachers are reporting this issue. Are they all in the same school? Could be that whitelisting *.concord.org could fix the issue.
Dan DamelinKeymasterThe idea of being able to draw regions on an image is intriguing, opening up the possibility for different kinds of infographics…
Dan DamelinKeymasterIt worked for me from Excel. I had to move the cursor to the border of the highlighted block of cells so I could get the “hand” cursor for dragging cells around. If I dragged into CODAP I got an imported data set.
Dan DamelinKeymasterFor a website to be visible inside CODAP it needs to use a secure connection (i.e. url starts with https). Did you try https://www.stochastik-in-der-schule.de/
Some websites also don’t allow themselves to be framed by another website. In that case there is nothing you can do short of asking the website owner to remove the code that prevents their site form displaying unless it is the top level parent.
Dan DamelinKeymasterYou might want to ask your student to submit a different link. That link is directly to the CODAP file stored directly on the student’s google drive. You likely don’t have access to that (at least through the CODAP application). If the student creates a share link using the menu to the left of the document title, then they can submit that and it should work.
Dan DamelinKeymasterOne quick solution would be to use the browser zoom to increase the size of the graph before taking a screenshot. That will keep the proportions in the graph and give you many more pixels.
Dan DamelinKeymasterI haven’t seen this for a while, but it sometimes happens when there is an update to CODAP and the local browser cache is not getting all of the most recent files. I’d suggest closing any tabs that have CODAP, clearing the browser cache and trying again. Alternately to see if it is a caching issue you can try opening the CODAP document using an incognito window.
October 15, 2020 at 4:57 pm in reply to: Problems opening CODAP documents saved on Google Drive #5972Dan DamelinKeymasterThere is an expected situation when one can’t open a CODAP doc saved to Google Drive: When one account was used to save it and another account is used to open it. We’ve seen this with some people who have work and personal google accounts, even if both accounts should have the same access to the file. If one account was used to save and another account was attempting to open, it can cause an error. Not saying that is what is happening in this case, but might be an issue for some.
Dan DamelinKeymasterTry this: if(original_attr=”little” or original_attr=”none”, “little to none”, original_attr)
-
AuthorPosts