I'm about to set up a survey of sorts in Indonesia and need some advice on
managing data in Aggregate.
The survey will involve collecting data on deforestation on an ongoing
basis, including GPS locations and images (it's quite a simple set up in
that sense). I'm having a few teething problems relating to storing and
exporting data in and from Aggregate.
The first issue is that I can't work out how to export submissions in a way
that retains images. For example, exporting as a CSV file creates a link to
the image in Aggregate. Equally, when I publish KML files the image remains
in Aggregate. This means that if I delete submissions the image no longer
exists, and CSV files and KML files will link to nothing. Is there a way,
or does anyone have any suggestions, of ways to download the image in a way
that it remains connected to the submissions?
Is it, alternatively, the case that the submissions should remain in
Aggregate as long as I want/need to use them? I can see that this might
make sense with a survey with a defined end and number of submissions. But
in this case the number of submissions can't accurately be predicted and
the survey is continuous.
The second issue relates to filtering submissions. Is there a way to filter
submissions by date, or alternatively, to order submissions within
Aggregate? At the moment dates appear in the following format: Fri Dec 28
00:00:00 UTC 2012. I can't figure out how to filter based on that format.
There are probably very obvious answers to these questions, but I'm quite
new to this. Thoroughly enjoying it nonetheless and excited by the
opportunities.
As far as filtering by date or ordering, I don't think you can.
Regardless, I find it's usually easier to stream data to Google
Spreadsheets or Fusion Tables and work on the data there.
Hope that helps,
Yaw
···
On Fri, Nov 23, 2012 at 5:53 AM, Tom Johnson wrote:
> Hi there,
>
> I'm about to set up a survey of sorts in Indonesia and need some advice on
> managing data in Aggregate.
>
> The survey will involve collecting data on deforestation on an ongoing
> basis, including GPS locations and images (it's quite a simple set up in
> that sense). I'm having a few teething problems relating to storing and
> exporting data in and from Aggregate.
>
> The first issue is that I can't work out how to export submissions in a way
> that retains images. For example, exporting as a CSV file creates a link to
> the image in Aggregate. Equally, when I publish KML files the image remains
> in Aggregate. This means that if I delete submissions the image no longer
> exists, and CSV files and KML files will link to nothing. Is there a way, or
> does anyone have any suggestions, of ways to download the image in a way
> that it remains connected to the submissions?
>
> Is it, alternatively, the case that the submissions should remain in
> Aggregate as long as I want/need to use them? I can see that this might make
> sense with a survey with a defined end and number of submissions. But in
> this case the number of submissions can't accurately be predicted and the
> survey is continuous.
>
> The second issue relates to filtering submissions. Is there a way to filter
> submissions by date, or alternatively, to order submissions within
> Aggregate? At the moment dates appear in the following format: Fri Dec 28
> 00:00:00 UTC 2012. I can't figure out how to filter based on that format.
>
> There are probably very obvious answers to these questions, but I'm quite
> new to this. Thoroughly enjoying it nonetheless and excited by the
> opportunities.
>
> Thanks in advance for any advice,
> Tom
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
I've actually encountered a further issue related to this since my initial
post. I've successfully published data from Aggregate to Fusion tables -
according to the "Published Data" page in Aggregate. However, when I click
the "View Fusion Table" link I get a message saying "Sorry, the table you
have requested does not exist. Please check the address and try again".
I've tried re-publishing the same and other submissions, with the same
result.