I have a task to develop some Android based software that needs to:
collect data from some custom hardware sensors
make the data available for upload into ODK Aggregate
The collected data will be analysed in conjunction with metrics and
other data collected using ODK Collect. Importantly it will not be
collected on equipment that has ODK Collect installed.
With this in mind, does anyone have any information on the XML format
that data must be encoded in order for upload to ODK Aggregate?
Do I just need to follow the example of the instance files generated
by ODK collect or is there a more formal specification that I need to
follow.
Once I have the data in the right format, I'll look into the issue of
uploading it.
···
On Sat, Sep 8, 2012 at 11:13 PM, Corey Wallis wrote:
> Hi,
>
> I have a task to develop some Android based software that needs to:
>
> - collect data from some custom hardware sensors
> - make the data available for upload into ODK Aggregate
>
> The collected data will be analysed in conjunction with metrics and
> other data collected using ODK Collect. Importantly it will not be
> collected on equipment that has ODK Collect installed.
>
> With this in mind, does anyone have any information on the XML format
> that data must be encoded in order for upload to ODK Aggregate?
>
> Do I just need to follow the example of the instance files generated
> by ODK collect or is there a more formal specification that I need to
> follow.
>
> Once I have the data in the right format, I'll look into the issue of
> uploading it.
>
> With thanks.
>
> -Corey
>
> Corey Wallis
> Lead Software Engineer, The MaGDAA project
> http://magdaaproject.org
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
So from what I can see in the second link the upload process is
basically a HTTP post with the need to check the return codes, and
optionally use authentication at the time of the post.
The first link talks about a lot of stuff that I don't think I'll need
to implement.
With this in mind, does anyone have an example of what is sent to ODK
Aggregate when ODK Collect uploads a completed form?
···
On Sun, Sep 9, 2012 at 11:18 PM, Yaw Anokwa wrote:
> https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaAPI
>
> https://bitbucket.org/javarosa/javarosa/wiki/FormSubmissionAPI is what
> you need to implement.
>
> On Sat, Sep 8, 2012 at 11:13 PM, Corey Wallis wrote:
>> Hi,
>>
>> I have a task to develop some Android based software that needs to:
>>
>> - collect data from some custom hardware sensors
>> - make the data available for upload into ODK Aggregate
>>
>> The collected data will be analysed in conjunction with metrics and
>> other data collected using ODK Collect. Importantly it will not be
>> collected on equipment that has ODK Collect installed.
>>
>> With this in mind, does anyone have any information on the XML format
>> that data must be encoded in order for upload to ODK Aggregate?
>>
>> Do I just need to follow the example of the instance files generated
>> by ODK collect or is there a more formal specification that I need to
>> follow.
>>
>> Once I have the data in the right format, I'll look into the issue of
>> uploading it.
>>
>> With thanks.
>>
>> -Corey
>>
>> Corey Wallis
>> Lead Software Engineer, The MaGDAA project
>> http://magdaaproject.org
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
The items in the post are what is in the instance folder.
Collect saves a completed form/instance/submission and any corresponding
files to the SD Card in the ODK folder. Each submission has it's own
instance folder that collects retrieves the files from and POSTs to the
server.
Waylon
···
On Sun, Sep 9, 2012 at 5:30 PM, Corey Wallis wrote:
Hi,
Thanks for the links.
So from what I can see in the second link the upload process is
basically a HTTP post with the need to check the return codes, and
optionally use authentication at the time of the post.
The first link talks about a lot of stuff that I don't think I'll need
to implement.
With this in mind, does anyone have an example of what is sent to ODK
Aggregate when ODK Collect uploads a completed form?
I have a task to develop some Android based software that needs to:
collect data from some custom hardware sensors
make the data available for upload into ODK Aggregate
The collected data will be analysed in conjunction with metrics and
other data collected using ODK Collect. Importantly it will not be
collected on equipment that has ODK Collect installed.
With this in mind, does anyone have any information on the XML format
that data must be encoded in order for upload to ODK Aggregate?
Do I just need to follow the example of the instance files generated
by ODK collect or is there a more formal specification that I need to
follow.
Once I have the data in the right format, I'll look into the issue of
uploading it.
Assuming a ODK Collect-style app would fit your needs if it were able to
connect to your custom device, you could avoid a rewrite of the
communications protocol and just write an external app that ODK Collect
would launch to collect your data and insert it into your data collection
form.
···
On Sun, Sep 9, 2012 at 8:08 PM, W. Brunette wrote:
The items in the post are what is in the instance folder.
Collect saves a completed form/instance/submission and any corresponding
files to the SD Card in the ODK folder. Each submission has it's own
instance folder that collects retrieves the files from and POSTs to the
server.
So from what I can see in the second link the upload process is
basically a HTTP post with the need to check the return codes, and
optionally use authentication at the time of the post.
The first link talks about a lot of stuff that I don't think I'll need
to implement.
With this in mind, does anyone have an example of what is sent to ODK
Aggregate when ODK Collect uploads a completed form?
I have a task to develop some Android based software that needs to:
collect data from some custom hardware sensors
make the data available for upload into ODK Aggregate
The collected data will be analysed in conjunction with metrics and
other data collected using ODK Collect. Importantly it will not be
collected on equipment that has ODK Collect installed.
With this in mind, does anyone have any information on the XML format
that data must be encoded in order for upload to ODK Aggregate?
Do I just need to follow the example of the instance files generated
by ODK collect or is there a more formal specification that I need to
follow.
Once I have the data in the right format, I'll look into the issue of
uploading it.
I've looked into this approach, and plan on using it for another of
our applications.
Unfortunately it won't work in this specific case as the Android
device and sensor package will be up in the air at the end of a pole
and needs to be autonomous. That is, it needs to collect data without
user interaction.
Since my original post I've been doing some more research, and have
taken a closer look at ODK Briefcase:
From what I can read on that page I think I all I need to do is:
develop a form and upload it into ODK Aggregate
collect data from our custom sensor package
write the data in the "instance" format in a location that ODK
Briefcase expects
use ODK Briefcase to copy the data off the device and into ODK Aggregate
Is that correct?
I'm assuming the form is required so that ODK Aggregate knows about
the data I want to upload, even though I won't be using ODK Collect to
collect it. Although as a side benefit if we needed to collect this
data manually we would have a form ready to do so.
In looking at the ODK Collect app on one of my test devices I see
forms are stored on the external storage here:
/odk/forms/
And instances are stored here:
/odk/instances/
The files in the instances folder appear to be XML files that
basically contains the same nodes as the section of the
form, except with the values populated.
With this in mind on the device that is collected to the sensor
package I could write XML files that emulated the instance format into
a folder with the same path.
Conceptually would this strategy work?
Many thanks for your time and patience.
-Corey
···
On Tue, Sep 11, 2012 at 4:38 AM, Mitch S wrote:
> Assuming a ODK Collect-style app would fit your needs if it were able to
> connect to your custom device, you could avoid a rewrite of the
> communications protocol and just write an external app that ODK Collect
> would launch to collect your data and insert it into your data collection
> form.
>
> What I'd recommend for widgets returning multiple values is here:
> http://code.google.com/p/opendatakit/wiki/XFormControlExtensionProposal
>
> An example of this for simple string, integer and decimal values is
> available in the BreathCounter app.
> http://code.google.com/p/opendatakit/source/browse?repo=androidextras
>
> The breathCount form:
> http://code.google.com/p/opendatakit/source/browse/BreathCounter/breathTest.xml?repo=androidextras
> will launch the BreathCounter app (available as an apk here:
> http://code.google.com/p/opendatakit/downloads/detail?name=BreathCounter.apk
> ) to collect a data value.
>
> Mitch
>
>
> On Sun, Sep 9, 2012 at 8:08 PM, W. Brunette wrote:
>>
>> The items in the post are what is in the instance folder.
>>
>> Collect saves a completed form/instance/submission and any corresponding
>> files to the SD Card in the ODK folder. Each submission has it's own
>> instance folder that collects retrieves the files from and POSTs to the
>> server.
>>
>> Waylon
>>
>>
>> On Sun, Sep 9, 2012 at 5:30 PM, Corey Wallis wrote:
>>>
>>> Hi,
>>>
>>> Thanks for the links.
>>>
>>> So from what I can see in the second link the upload process is
>>> basically a HTTP post with the need to check the return codes, and
>>> optionally use authentication at the time of the post.
>>>
>>> The first link talks about a lot of stuff that I don't think I'll need
>>> to implement.
>>>
>>> With this in mind, does anyone have an example of what is sent to ODK
>>> Aggregate when ODK Collect uploads a completed form?
>>>
>>> With thanks.
>>>
>>> -Corey
>>>
>>> Corey Wallis
>>> Lead Software Engineer, The MaGDAA project
>>> http://magdaaproject.org
>>>
>>>
>>> On Sun, Sep 9, 2012 at 11:18 PM, Yaw Anokwa wrote:
>>> > https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaAPI
>>> >
>>> > https://bitbucket.org/javarosa/javarosa/wiki/FormSubmissionAPI is what
>>> > you need to implement.
>>> >
>>> > On Sat, Sep 8, 2012 at 11:13 PM, Corey Wallis wrote:
>>> >> Hi,
>>> >>
>>> >> I have a task to develop some Android based software that needs to:
>>> >>
>>> >> - collect data from some custom hardware sensors
>>> >> - make the data available for upload into ODK Aggregate
>>> >>
>>> >> The collected data will be analysed in conjunction with metrics and
>>> >> other data collected using ODK Collect. Importantly it will not be
>>> >> collected on equipment that has ODK Collect installed.
>>> >>
>>> >> With this in mind, does anyone have any information on the XML format
>>> >> that data must be encoded in order for upload to ODK Aggregate?
>>> >>
>>> >> Do I just need to follow the example of the instance files generated
>>> >> by ODK collect or is there a more formal specification that I need to
>>> >> follow.
>>> >>
>>> >> Once I have the data in the right format, I'll look into the issue of
>>> >> uploading it.
>>> >>
>>> >> With thanks.
>>> >>
>>> >> -Corey
>>> >>
>>> >> Corey Wallis
>>> >> Lead Software Engineer, The MaGDAA project
>>> >> http://magdaaproject.org
>>> >>
>>> >> --
>>> >> Post: opendatakit@googlegroups.com
>>> >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> >> Options: http://groups.google.com/group/opendatakit?hl=en
>>> >
>>> > --
>>> > Post: opendatakit@googlegroups.com
>>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> > Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>> --
>>> Post: opendatakit@googlegroups.com
>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitchellsundt@gmail.com
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
Within your Android app, you can also copy the code under
InstanceUploaderTask and all the packages it uses to send the data to
Aggregate; by ensuring that authentication is configured using the
username/password saved in the app preferences before calling this task,
and by replumbing the error handling to not throw up Toasts or error or
authentication dialogs, then you would have something that could run
unattended and submit data into Aggregate. I don't think any of that code
relies on FormController or the javarosa libraries, so it should be fairly
straightforward to copy over to a new app.
Mitch
···
On Mon, Sep 10, 2012 at 5:25 PM, Corey Wallis wrote:
Hi Mitch,
I've looked into this approach, and plan on using it for another of
our applications.
Unfortunately it won't work in this specific case as the Android
device and sensor package will be up in the air at the end of a pole
and needs to be autonomous. That is, it needs to collect data without
user interaction.
Since my original post I've been doing some more research, and have
taken a closer look at ODK Briefcase:
From what I can read on that page I think I all I need to do is:
develop a form and upload it into ODK Aggregate
collect data from our custom sensor package
write the data in the "instance" format in a location that ODK
Briefcase expects
use ODK Briefcase to copy the data off the device and into ODK Aggregate
Is that correct?
I'm assuming the form is required so that ODK Aggregate knows about
the data I want to upload, even though I won't be using ODK Collect to
collect it. Although as a side benefit if we needed to collect this
data manually we would have a form ready to do so.
In looking at the ODK Collect app on one of my test devices I see
forms are stored on the external storage here:
/odk/forms/
And instances are stored here:
/odk/instances/
The files in the instances folder appear to be XML files that
basically contains the same nodes as the section of the
form, except with the values populated.
With this in mind on the device that is collected to the sensor
package I could write XML files that emulated the instance format into
a folder with the same path.
Assuming a ODK Collect-style app would fit your needs if it were able to
connect to your custom device, you could avoid a rewrite of the
communications protocol and just write an external app that ODK Collect
would launch to collect your data and insert it into your data collection
form.
The items in the post are what is in the instance folder.
Collect saves a completed form/instance/submission and any corresponding
files to the SD Card in the ODK folder. Each submission has it's own
instance folder that collects retrieves the files from and POSTs to the
server.
So from what I can see in the second link the upload process is
basically a HTTP post with the need to check the return codes, and
optionally use authentication at the time of the post.
The first link talks about a lot of stuff that I don't think I'll need
to implement.
With this in mind, does anyone have an example of what is sent to ODK
Aggregate when ODK Collect uploads a completed form?
I have a task to develop some Android based software that needs to:
collect data from some custom hardware sensors
make the data available for upload into ODK Aggregate
The collected data will be analysed in conjunction with metrics and
other data collected using ODK Collect. Importantly it will not be
collected on equipment that has ODK Collect installed.
With this in mind, does anyone have any information on the XML
format
that data must be encoded in order for upload to ODK Aggregate?
Do I just need to follow the example of the instance files generated
by ODK collect or is there a more formal specification that I need
to
follow.
Once I have the data in the right format, I'll look into the issue
of
uploading it.
I'll let the list now how I go as development progresses.
With thanks.
-Corey
···
On Tue, Sep 11, 2012 at 10:47 AM, Mitch S wrote:
> Yes, this is exactly correct and very doable.
>
> Within your Android app, you can also copy the code under
> InstanceUploaderTask and all the packages it uses to send the data to
> Aggregate; by ensuring that authentication is configured using the
> username/password saved in the app preferences before calling this task, and
> by replumbing the error handling to not throw up Toasts or error or
> authentication dialogs, then you would have something that could run
> unattended and submit data into Aggregate. I don't think any of that code
> relies on FormController or the javarosa libraries, so it should be fairly
> straightforward to copy over to a new app.
>
> Mitch
>
>
> On Mon, Sep 10, 2012 at 5:25 PM, Corey Wallis wrote:
>>
>> Hi Mitch,
>>
>> I've looked into this approach, and plan on using it for another of
>> our applications.
>>
>> Unfortunately it won't work in this specific case as the Android
>> device and sensor package will be up in the air at the end of a pole
>> and needs to be autonomous. That is, it needs to collect data without
>> user interaction.
>>
>> Since my original post I've been doing some more research, and have
>> taken a closer look at ODK Briefcase:
>>
>> http://opendatakit.org/use/briefcase/
>>
>> From what I can read on that page I think I all I need to do is:
>>
>> - develop a form and upload it into ODK Aggregate
>> - collect data from our custom sensor package
>> - write the data in the "instance" format in a location that ODK
>> Briefcase expects
>> - use ODK Briefcase to copy the data off the device and into ODK Aggregate
>>
>> Is that correct?
>>
>> I'm assuming the form is required so that ODK Aggregate knows about
>> the data I want to upload, even though I won't be using ODK Collect to
>> collect it. Although as a side benefit if we needed to collect this
>> data manually we would have a form ready to do so.
>>
>> In looking at the ODK Collect app on one of my test devices I see
>> forms are stored on the external storage here:
>>
>> /odk/forms/
>>
>> And instances are stored here:
>>
>> /odk/instances/
>>
>> The files in the instances folder appear to be XML files that
>> basically contains the same nodes as the section of the
>> form, except with the values populated.
>>
>> With this in mind on the device that is collected to the sensor
>> package I could write XML files that emulated the instance format into
>> a folder with the same path.
>>
>> Conceptually would this strategy work?
>>
>> Many thanks for your time and patience.
>>
>> -Corey
>>
>>
>> On Tue, Sep 11, 2012 at 4:38 AM, Mitch S wrote:
>> > Assuming a ODK Collect-style app would fit your needs if it were able to
>> > connect to your custom device, you could avoid a rewrite of the
>> > communications protocol and just write an external app that ODK Collect
>> > would launch to collect your data and insert it into your data
>> > collection
>> > form.
>> >
>> > What I'd recommend for widgets returning multiple values is here:
>> > http://code.google.com/p/opendatakit/wiki/XFormControlExtensionProposal
>> >
>> > An example of this for simple string, integer and decimal values is
>> > available in the BreathCounter app.
>> > http://code.google.com/p/opendatakit/source/browse?repo=androidextras
>> >
>> > The breathCount form:
>> >
>> > http://code.google.com/p/opendatakit/source/browse/BreathCounter/breathTest.xml?repo=androidextras
>> > will launch the BreathCounter app (available as an apk here:
>> >
>> > http://code.google.com/p/opendatakit/downloads/detail?name=BreathCounter.apk
>> > ) to collect a data value.
>> >
>> > Mitch
>> >
>> >
>> > On Sun, Sep 9, 2012 at 8:08 PM, W. Brunette wrote:
>> >>
>> >> The items in the post are what is in the instance folder.
>> >>
>> >> Collect saves a completed form/instance/submission and any
>> >> corresponding
>> >> files to the SD Card in the ODK folder. Each submission has it's own
>> >> instance folder that collects retrieves the files from and POSTs to the
>> >> server.
>> >>
>> >> Waylon
>> >>
>> >>
>> >> On Sun, Sep 9, 2012 at 5:30 PM, Corey Wallis wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> Thanks for the links.
>> >>>
>> >>> So from what I can see in the second link the upload process is
>> >>> basically a HTTP post with the need to check the return codes, and
>> >>> optionally use authentication at the time of the post.
>> >>>
>> >>> The first link talks about a lot of stuff that I don't think I'll need
>> >>> to implement.
>> >>>
>> >>> With this in mind, does anyone have an example of what is sent to ODK
>> >>> Aggregate when ODK Collect uploads a completed form?
>> >>>
>> >>> With thanks.
>> >>>
>> >>> -Corey
>> >>>
>> >>> Corey Wallis
>> >>> Lead Software Engineer, The MaGDAA project
>> >>> http://magdaaproject.org
>> >>>
>> >>>
>> >>> On Sun, Sep 9, 2012 at 11:18 PM, Yaw Anokwa wrote:
>> >>> > https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaAPI
>> >>> >
>> >>> > https://bitbucket.org/javarosa/javarosa/wiki/FormSubmissionAPI is
>> >>> > what
>> >>> > you need to implement.
>> >>> >
>> >>> > On Sat, Sep 8, 2012 at 11:13 PM, Corey Wallis wrote:
>> >>> >> Hi,
>> >>> >>
>> >>> >> I have a task to develop some Android based software that needs to:
>> >>> >>
>> >>> >> - collect data from some custom hardware sensors
>> >>> >> - make the data available for upload into ODK Aggregate
>> >>> >>
>> >>> >> The collected data will be analysed in conjunction with metrics and
>> >>> >> other data collected using ODK Collect. Importantly it will not be
>> >>> >> collected on equipment that has ODK Collect installed.
>> >>> >>
>> >>> >> With this in mind, does anyone have any information on the XML
>> >>> >> format
>> >>> >> that data must be encoded in order for upload to ODK Aggregate?
>> >>> >>
>> >>> >> Do I just need to follow the example of the instance files
>> >>> >> generated
>> >>> >> by ODK collect or is there a more formal specification that I need
>> >>> >> to
>> >>> >> follow.
>> >>> >>
>> >>> >> Once I have the data in the right format, I'll look into the issue
>> >>> >> of
>> >>> >> uploading it.
>> >>> >>
>> >>> >> With thanks.
>> >>> >>
>> >>> >> -Corey
>> >>> >>
>> >>> >> Corey Wallis
>> >>> >> Lead Software Engineer, The MaGDAA project
>> >>> >> http://magdaaproject.org
>> >>> >>
>> >>> >> --
>> >>> >> Post: opendatakit@googlegroups.com
>> >>> >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>> >> Options: http://groups.google.com/group/opendatakit?hl=en
>> >>> >
>> >>> > --
>> >>> > Post: opendatakit@googlegroups.com
>> >>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>> > Options: http://groups.google.com/group/opendatakit?hl=en
>> >>>
>> >>> --
>> >>> Post: opendatakit@googlegroups.com
>> >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>> Options: http://groups.google.com/group/opendatakit?hl=en
>> >>
>> >>
>> >> --
>> >> Post: opendatakit@googlegroups.com
>> >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >> Options: http://groups.google.com/group/opendatakit?hl=en
>> >
>> >
>> >
>> >
>> > --
>> > Mitch Sundt
>> > Software Engineer
>> > University of Washington
>> > mitchellsundt@gmail.com
>> >
>> > --
>> > Post: opendatakit@googlegroups.com
>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> > Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitchellsundt@gmail.com
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en