Unable to replace a dataset
Matt Kelso
via web
Hello,
I'm having some issues trying to replace an existing dataset. I downloaded the original from http://data.fractracker.org/cbi/dataset/datasetPreviewPage?uuid=~01...
Then I added 30 records or so, took care to make sure that the columns lined up, and got an error saying that there were 32 data columns and it was expecting 30. In fact, my last two columns were duplicate lat long data that I copied to match the rest of the dataset (which again came straight from fractracker.org). Any ideas on this one?
- pa_marce.csv 1.4 MB
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by higgins on 04 Oct, 2010 10:41 PM
Try removing those two final columns and see if that works better. I think fractracker added those, so they weren't in the "original" and that might be confusing it.
(Technical details: The system tries to make sure that replacement data doesn't differ in schema from the original data, but the export function doesn't necessarily preserve the data exactly as it was originally supplied because every data format is converted to an internal representation that lets us manage the differences between shapefiles, CSV files, KML, etc. That means there can be some changes if you upload a dataset and then immediately download it, even if you download it in the same format as you uploaded it.)
Let me know if that helps.
Thanks,
Mike
3 Posted by Matt Kelso on 06 Oct, 2010 01:04 PM
Yes, that was part of the problem. Now that I've gotten around to trying it again though, there is another issue. The dataset uploaded, but when I get to step three of "Describe your dataset" I am unable to select geographic data because the three dropdown boxes are all grayed out. How can I activate those?
Thanks again,
Matt
Support Staff 4 Posted by Alison Alvarez on 06 Oct, 2010 01:16 PM
Just to clarify, did you upload that dataset as new, or as a replacement of your last dataset?
5 Posted by Matt Kelso on 06 Oct, 2010 01:29 PM
It was as a replacement. I thought that perhaps it would have remembered that, but it wouldn't let me go on to step 4 of the metadata section without selecting the latitude and longitude, which I was of course unable to do.
Support Staff 6 Posted by Alison Alvarez on 06 Oct, 2010 02:41 PM
Hm, that doesn't sound right. We will have a staff member look into it.
Support Staff 7 Posted by higgins on 06 Oct, 2010 02:50 PM
Yeah, I agree with Alison. It's supposed to remember your "select geographic data" settings from the previous version and re-use them. (That's why the selection box is greyed out --- so you don't mess up the settings.) But it sounds like the greying out part is working, but the remembering part has failed for some reason. We will try to reproduce on our staging server and investigate.
So I'm clear, the process you followed was:
Create a dataset initially from a CSV, selecting latitude and longitude columns in the CSV.
Download that dataset and add additional rows.
Upload the new dataset as a replacement, expecting it to go through, but instead you are trapped at the "select geographic data" step.
8 Posted by Matt Kelso on 06 Oct, 2010 03:05 PM
That is exactly right.
Support Staff 9 Posted by higgins on 06 Oct, 2010 04:28 PM
I'm having trouble reproducing the problem internally. I took your dataset, uploaded it to our staging server (selecting two attributes for latitude longitude --- latitudede and longituded), then downloaded it, deleted the last two columns, and added a row. I uploaded again as a replacement for the previous dataset and was able to go all the way through the process.
I'm attaching a screenshot of what my "Select Geographic Data" step looks like. I take it yours looks different? What browser are you using?
10 Posted by Matt Kelso on 06 Oct, 2010 05:02 PM
Hmm, it didn't work for me in Chrome or Firefox. Would updating the metadata along the way play a role? I've given a screenshot that looks the same, but with the error message.
Support Staff 11 Posted by higgins on 06 Oct, 2010 05:40 PM
All right, I think I've isolated the problem. The original uploaded dataset had capitalized column names (like LATITUDEDE and LONGITUDED). Fractracker is converting the attribute names to lower-case for internal storage (and so they are lower-case when the file is downloaded). But, the piece of the system that remembers the original geographic data settings is NOT converting to lower-case.
So, the workaround is to rename the "latitudede" column to "LATITUDEDE" and the "longituded" column to "LONGITUDED".
I'll file bug in our internal issue tracker to fix this problem in a future release.
Meanwhile, let me know if that solves the immediate problem for you.
12 Posted by Matt Kelso on 07 Oct, 2010 01:10 PM
It did not work. I also tried to change all of the labels to caps, and that didn't help either. I get the same error message as before.
Support Staff 13 Posted by higgins on 07 Oct, 2010 01:31 PM
Can you attach the file with the changed capitalization that you tried to use?
14 Posted by Matt Kelso on 07 Oct, 2010 05:20 PM
OK, I got it to work. Originally when I had tried to capitalize the field names, I thought I was supposed to try it in fractracker itself, but when I updated the .csv it worked fine. Thanks.
Support Staff 15 Posted by higgins on 07 Oct, 2010 05:45 PM
Awesome! I've put this issue on the buglist, so in a future release you won't have this problem anymore.
higgins closed this discussion on 07 Oct, 2010 05:45 PM.