Grayed out location boxes
Matt Kelso
via web
I'm having a similar issue discussed in an earlier thread:
to http://support.rhizalabs.com/discussions/problems/28-unable-to-repl...
I was unable to update a dataset because the latitude and longitude boxes were grayed out. I tried to change the latitude and longitude column headers to caps, as discussed before, but that didn't do the trick this time. What's especially odd about it is that I didn't have this issue on a dataset that I updated earlier today.
I'm trying to update the following dataset:
http://data.fractracker.org/cbi/dataset/datasetPreviewPage?uuid=~01...
- pa_oil_a.csv 11.3 MB
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by higgins on 23 May, 2011 03:12 PM
Sorry for the delay Matt! I'll take a look at this today and see if I can figure out what the issue is.
Mike
Support Staff 3 Posted by higgins on 23 May, 2011 04:38 PM
The workaround for now is to name the columns "Latitude Decimal" and "Longitude Decimal" in the uploaded spreadsheet. I thought we had fixed this issue after your previous problem, but apparently the fix is not comprehensive enough. I will reopen the case internally.
Thanks for your patience, and let me know if the workaround doesn't take care of it.
Mike
4 Posted by Matt Kelso on 23 May, 2011 05:03 PM
No, the workaround didn't work. I'm pretty sure those were my original column headers.
Support Staff 5 Posted by higgins on 23 May, 2011 05:05 PM
Oh, heck. I tested it here --- can you attach the workaround file and let me see?
Thanks,
Mike
6 Posted by Matt Kelso on 23 May, 2011 05:11 PM
sure...Actually, it was probably all lower case like the rest of the columns.
Support Staff 7 Posted by higgins on 23 May, 2011 06:55 PM
Oh, wait, perhaps I am misunderstanding your problem. The way it's supposed to work is like this: when you upload a replacement, the replacement must use the same columns to define the location as the previous version of the data. So the dropdows should be greyed-out, but set to the correct attributes for you. You should be able to move on to the next screen and publish the dataset without adjusting them at all (and, in fact, the system is preventing you from adjusting them by greying them out).
I've attached a screenshot of what the screen ought to look like. Is that what it looks like, or something different? (For instance, it might say "None" in the dropdowns instead of "Latitude Decimal"...)
8 Posted by Matt Kelso on 26 May, 2011 02:00 PM
Oh, yes that's right. It did block me initially though. Now, however, I can't load anything at all, whether as a replacement or a new dataset.
Support Staff 9 Posted by higgins on 26 May, 2011 03:03 PM
Yep, we had a full disk. It's cleaned out now, so you should be good to go again. Let me know if you succeed with the replacement.
Mike
10 Posted by Matt Kelso on 26 May, 2011 03:33 PM
OK, that worked and the dataset is in the queue. Thanks for your help! Somehow though, I was just sent over 130 emails informing me that a user had made a snapshot with my dataset. This appears to be for all snapshots created by other users from February to current. Not a big deal--I just deleted them--but thought you should know.
Support Staff 11 Posted by higgins on 26 May, 2011 03:44 PM
You're not the only one. There is a mail relay problem we discovered today (and fixed) and a bunch of queued email got flushed out. It should work on a timely basis now. Sorry for the inconvenience!
Mike
higgins closed this discussion on 26 May, 2011 03:44 PM.