Form size

May I ask what is the limit for the size of a form? or how many fields are
allowed in a form. Is there a limit for the data storage? Thanks, Wen

The ODK tools support unlimited form length, and unlimited numbers of
filled-in forms (submissions).

··· ------------- FYI: our largest example form has 300 data fields -- this is the "eIMCI by D-Tree" form -- many of that form's data fields hold intermediate calculations. That takes a few seconds to load.

The entire form definition is read into memory before displaying your
form's first question. If your form has many relevancy conditions or
calculated fields, or many language translations, the underlying XForms
engine (JavaRosa) can take quite some time to load your form. At some
point, ether the load time for a form will become unacceptable or the time
it takes an interviewer to work through a form will become intolerable.


Accessing filled-in forms is done as efficiently as possible in ODK
Aggregate. For very large datasets (greater than 100,000 filled-in forms),
I expect that running your own MySQL or PostgreSQL database will provide
lower cost access to your data and better responsiveness than running on
AppEngine. This is especially true if you use row filters to selectively
view your data.

The one limitation within ODK Aggregate is in the Export-to-File
functionality. This has the limitation that the generated file must fit
within the server memory size. The server memory size is something you can
configure in AppEngine, which allows for export files approaching 1GB in
size, if needed (by default, you are limited to something less than 250MB
in size). This is, of course, freely configurable if you deploy your own
Tomcat server.

On Mon, Jul 16, 2012 at 11:07 AM, Wen wenliang@umich.edu wrote:

May I ask what is the limit for the size of a form? or how many fields
are allowed in a form. Is there a limit for the data storage? Thanks, Wen

--
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

Hi Wen,
I have 2,300 rows in my .xls form and everything works.

··· On Mon, Jul 16, 2012 at 2:07 PM, Wen wrote:

May I ask what is the limit for the size of a form? or how many fields
are allowed in a form. Is there a limit for the data storage? Thanks, Wen

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Oh, and also -- ODK Aggregate does not fully implement column and row
filters when a filled-in form must be saved across multiple underlying
tables because of limitations in the underlying datastore (AppEngine, MySQL
or PostgreSQL). This is most pronounced in MySQL and AppEngine. This
occurs when there are somewhere over 200 string questions in a form.

Mitch

··· On Mon, Jul 16, 2012 at 1:14 PM, Mitch S wrote:

The ODK tools support unlimited form length, and unlimited numbers of
filled-in forms (submissions).


FYI: our largest example form has 300 data fields -- this is the "eIMCI by
D-Tree" form -- many of that form's data fields hold intermediate
calculations. That takes a few seconds to load.

The entire form definition is read into memory before displaying your
form's first question. If your form has many relevancy conditions or
calculated fields, or many language translations, the underlying XForms
engine (JavaRosa) can take quite some time to load your form. At some
point, ether the load time for a form will become unacceptable or the time
it takes an interviewer to work through a form will become intolerable.


Accessing filled-in forms is done as efficiently as possible in ODK
Aggregate. For very large datasets (greater than 100,000 filled-in forms),
I expect that running your own MySQL or PostgreSQL database will provide
lower cost access to your data and better responsiveness than running on
AppEngine. This is especially true if you use row filters to selectively
view your data.

The one limitation within ODK Aggregate is in the Export-to-File
functionality. This has the limitation that the generated file must fit
within the server memory size. The server memory size is something you can
configure in AppEngine, which allows for export files approaching 1GB in
size, if needed (by default, you are limited to something less than 250MB
in size). This is, of course, freely configurable if you deploy your own
Tomcat server.

On Mon, Jul 16, 2012 at 11:07 AM, Wen wenliang@umich.edu wrote:

May I ask what is the limit for the size of a form? or how many fields
are allowed in a form. Is there a limit for the data storage? Thanks, Wen

--
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

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Thank you so much for your reply, Mitch.

··· On Monday, July 16, 2012 4:14:24 PM UTC-4, Mitch wrote: > > The ODK tools support unlimited form length, and unlimited numbers of > filled-in forms (submissions). > > ------------- > FYI: our largest example form has 300 data fields -- this is the "eIMCI by > D-Tree" form -- many of that form's data fields hold intermediate > calculations. That takes a few seconds to load. > > The entire form definition is read into memory before displaying your > form's first question. If your form has many relevancy conditions or > calculated fields, or many language translations, the underlying XForms > engine (JavaRosa) can take quite some time to load your form. At some > point, ether the load time for a form will become unacceptable or the time > it takes an interviewer to work through a form will become intolerable. > > ------------- > Accessing filled-in forms is done as efficiently as possible in ODK > Aggregate. For very large datasets (greater than 100,000 filled-in forms), > I expect that running your own MySQL or PostgreSQL database will provide > lower cost access to your data and better responsiveness than running on > AppEngine. This is especially true if you use row filters to selectively > view your data. > > The one limitation within ODK Aggregate is in the Export-to-File > functionality. This has the limitation that the generated file must fit > within the server memory size. The server memory size is something you can > configure in AppEngine, which allows for export files approaching 1GB in > size, if needed (by default, you are limited to something less than 250MB > in size). This is, of course, freely configurable if you deploy your own > Tomcat server. > > > On Mon, Jul 16, 2012 at 11:07 AM, Wen wrote: > >> May I ask what is the limit for the size of a form? or how many fields >> are allowed in a form. Is there a limit for the data storage? Thanks, Wen >> >> -- >> 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 >

Thank you so much for your reply, Brian.

··· On Monday, July 16, 2012 3:32:22 PM UTC-4, Brian Dyer wrote: > > Hi Wen, > I have 2,300 rows in my .xls form and everything works. > > > On Mon, Jul 16, 2012 at 2:07 PM, Wen wrote: > >> May I ask what is the limit for the size of a form? or how many fields >> are allowed in a form. Is there a limit for the data storage? Thanks, Wen >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > >