aggregate
aggregate copied to clipboard
getodk
Geoshape and geotrace data types are retrieved with missing data.
Hello there. I am using GeoODK with an Aggregate server in appspot. We have a no-required question type geotrace to fill a perimeter of a land. Sometimes people are uploading the data but this data is coming with missing values.
Do you know if this is an issue of length of the field? or issue of the GeoODK app that's sending the info with some missing characters?
Data is always supposed to be an array of coordinates separated by a semicolon, where each coordinate is a 4-value array separated by spaces.
Is this an issue of Aggregate receiving/exporting the data? or an issue of GeoODK sending it?
ODK Aggregate has a default storage length of 255 characters.
It is entirely possible this is an issue if you are trying to capture more than 8 coordinates per data capture. i.e., if you assume a worst-case geopoint of 10-digit decimal numbers, then you would consume 4*10 + 4 == 44 characters per geopoint in a geotrace. This would limit you to no more than 5 coordinates per data capture. If you assume 2 10-digit values and 2 3-character values (0.0), this would give 30 characters per geopoint, limiting you to no more than 8 coordinates per data capture.
I forget whether the odk:length attribute is recognized on geotrace / geoshape fields. See https://opendatakit.org/help/form-design/guidelines/#datastore_string_length
Try specifying that; the form_id will need to be changed to get the length setting to be respected (you cannot simply modify the existing form definition to add an odk:length attribute). Please let me know whether there is an error when you attempt to upload a form with this setting and, if not, whether or not adding it resolves the 255-character limit problem. If it works, I will update the documentation calling this out as a concern and work-around.
On Tue, Jul 21, 2015 at 1:03 PM, Julián R. Figueroa < [email protected]> wrote:
Hello there. I am using GeoODK with an Aggregate server in appspot. We have a no-required question type geotrace to fill a perimeter of a land. Sometimes people are uploading the data but this data is coming with missing values.
Do you know if this is an issue of length of the field? or issue of the GeoODK app that's sending the info with some missing characters?
[image: bug1] https://cloud.githubusercontent.com/assets/4431392/8811144/9042cf88-2fb9-11e5-9669-c641aea8ecca.jpg
[image: bug2] https://cloud.githubusercontent.com/assets/4431392/8811100/0e812e68-2fb9-11e5-82d0-15465ce7e7fe.jpg
Data is always supposed to be an array of coordinates separated by a semicolon, where each coordinate is a 4-value array separated by spaces.
Is this an issue of Aggregate receiving/exporting the data? or an issue of GeoODK sending it?
— Reply to this email directly or view it on GitHub https://github.com/opendatakit/opendatakit/issues/1163.
Mitch Sundt Software Engineer University of Washington [email protected]
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a temporary error. The following address(es) deferred:
[email protected] Domain beorse.net has exceeded the max emails per hour (268/250 (107%)) allowed. Message will be reattempted later
------- This is a copy of the message, including all the headers. ------ ------ The body of the message is 5302 characters long; only the first ------ 5000 or so are included here. Received: from github-smtp2-ext2.iad.github.net ([192.30.252.193]:38721 helo=github-smtp2b-ext-cp1-prd.iad.github.net) by hp159.hostpapa.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from [email protected]) id 1dgMCb-000eZD-1V for [email protected]; Fri, 11 Aug 2017 22:31:01 -0400 Date: Fri, 11 Aug 2017 19:30:21 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1502505021; bh=Vfec16e5uFUnZKR4vuFf8aYGaMjLyCfGs1pSjezjt30=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Vm3WVoSpRKXWjvQA3/sIGZNh0z1VktgPW1mrGlbDRk4RMPKxUHhbyE6G5rD9yTH6t jjDStXoM4KUiLSkLlE4G6uwqzENAD9qBHx65yIdzegjZRlPyrIsGGipZSUDhoLZjR4 p2z5zQaen9Wn7lb3EcNhcAOfH/pQfcTmkWf9/7Ig= From: Open Data Kit [email protected] Reply-To: opendatakit/aggregate [email protected] To: opendatakit/aggregate [email protected] Cc: Subscribed [email protected] Message-ID: opendatakit/aggregate/issues/[email protected] Subject: [opendatakit/aggregate] Geoshape and geotrace data types are retrieved with missing data. (#76) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_598e683d7749e_5ae3fb2774b1c34777f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: opendatakit-bot X-GitHub-Recipient: jbeorse X-GitHub-Reason: subscribed List-ID: opendatakit/aggregate <aggregate.opendatakit.github.com> List-Archive: https://github.com/opendatakit/aggregate List-Post: mailto:[email protected] List-Unsubscribe: mailto:unsub+000519af06b47bd8d9d1ef102acc394286f3166c86d4de9992cf0000000115a62a3d92a169ce0ee36277@reply.github.com, https://github.com/notifications/unsubscribe/AAUZr5LvaAe1WD6N9ZJJQvykCk1pTHm2ks5sXQ49gaJpZM4O1SQw X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: [email protected]
----==_mimepart_598e683d7749e_5ae3fb2774b1c34777f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
Hello there. I am using GeoODK with an Aggregate server in appspot. We have a no-required question type geotrace to fill a perimeter of a land. Sometimes people are uploading the data but this data is coming with missing values.
Do you know if this is an issue of length of the field? or issue of the GeoODK app that's sending the info with some missing characters?
Data is always supposed to be an array of coordinates separated by a semicolon, where each coordinate is a 4-value array separated by spaces.
Is this an issue of Aggregate receiving/exporting the data? or an issue of GeoODK sending it?
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/opendatakit/aggregate/issues/76 ----==_mimepart_598e683d7749e_5ae3fb2774b1c34777f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Tuesday Jul 21, 2015 at 20:03 GMT
Originally opened as opendatakit/opendatakit#1163 (1 comment(s))
Hello there. I am using GeoODK with an Aggregate server in appspot. We have a no-required question type geotrace to fill a perimeter of a land. Sometimes people are uploading the data but this data is coming with missing values.
Do you know if this is an issue of length of the field? or issue of the GeoODK app that's sending the info with some missing characters?
Data is always supposed to be an array of coordinates separated by a semicolon, where each coordinate is a 4-value array separated by spaces.
Is this an issue of Aggregate receiving/exporting the data? or an issue of GeoODK sending it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a temporary error. The following address(es) deferred:
[email protected] Domain beorse.net has exceeded the max emails per hour (269/250 (107%)) allowed. Message will be reattempted later
------- This is a copy of the message, including all the headers. ------ ------ The body of the message is 11726 characters long; only the first ------ 5000 or so are included here. Received: from github-smtp2-ext2.iad.github.net ([192.30.252.193]:38837 helo=github-smtp2b-ext-cp1-prd.iad.github.net) by hp159.hostpapa.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from [email protected]) id 1dgMCc-000eZh-NF for [email protected]; Fri, 11 Aug 2017 22:31:02 -0400 Date: Fri, 11 Aug 2017 19:30:23 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1502505023; bh=7IL7iFIE4PkG4orplGYtocq4+o1OnUeV+jzsizYxDn0=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Cd3ZNMSSHZV5hywMn/m3y4Oc3Ujk1p+GpK1ENnrd4FpMHdQktHs8+CMw/YgC7OEEt HKndX7oMrxzijo/l9EyQgzjHabF4U6k+W2Y7d/lBC1/U86RZ7sX80db8mDF0LrM0rW vPkIqehyT7Y0MPjeLQnAUI32cKuCEb7LOmr41NaU= From: Open Data Kit [email protected] Reply-To: opendatakit/aggregate [email protected] To: opendatakit/aggregate [email protected] Cc: Subscribed [email protected] Message-ID: opendatakit/aggregate/issues/76/[email protected] In-Reply-To: opendatakit/aggregate/issues/[email protected] References: opendatakit/aggregate/issues/[email protected] Subject: Re: [opendatakit/aggregate] Geoshape and geotrace data types are retrieved with missing data. (#76) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_598e683f24961_dca3f8fdce77c2c1214e2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: opendatakit-bot X-GitHub-Recipient: jbeorse X-GitHub-Reason: subscribed List-ID: opendatakit/aggregate <aggregate.opendatakit.github.com> List-Archive: https://github.com/opendatakit/aggregate List-Post: mailto:[email protected] List-Unsubscribe: mailto:unsub+000519af9540069ac8769bfd264eef73279452728fcdff7b92cf0000000115a62a3f92a169ce0ee36277@reply.github.com, https://github.com/notifications/unsubscribe/AAUZr_09bA7mtbxl-z_87q8z6wPZ10nXks5sXQ4_gaJpZM4O1SQw X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: [email protected]
----==_mimepart_598e683f24961_dca3f8fdce77c2c1214e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
<a href=3D"https://github.com/mitchellsundt"><img src=3D"https://avatars1= .githubusercontent.com/u/2281171?v=3D4" align=3D"left" width=3D"48" heigh= t=3D"48" hspace=3D"10"> Comment by [mitchellsundt](https://gi= thub.com/mitchellsundt) Tuesday Jul 21, 2015 at 23:41 GMT
ODK Aggregate has a default storage length of 255 characters.
It is entirely possible this is an issue if you are trying to capture mor= e than 8 coordinates per data capture. i.e., if you assume a worst-case geopoint of 10-digit decimal numbers, then you would consume 4*10 + 4 =3D= =3D 44 characters per geopoint in a geotrace. This would limit you to no more than 5 coordinates per data capture. If you assume 2 10-digit values and= 2 3-character values (0.0), this would give 30 characters per geopoint, limiting you to no more than 8 coordinates per data capture.
I forget whether the odk:length attribute is recognized on geotrace / geoshape fields. See https://opendatakit.org/help/form-design/guidelines/#datastore_string_len= gth
Try specifying that; the form_id will need to be changed to get the lengt= h setting to be respected (you cannot simply modify the existing form definition to add an odk:length attribute). Please let me know whether there is an error when you attempt to upload a form with this setting and= , if not, whether or not adding it resolves the 255-character limit problem= . If it works, I will update the documentation calling this out as a concer= n and work-around.
On Tue, Jul 21, 2015 at 1:03 PM, Juli=C3=A1n R. Figueroa < [email protected]> wrote:
Hello there. I am using GeoODK with an Aggregate server in appspot. We have a no-required question type geotrace to fill a perimeter of a land. Sometimes people are uploading the data but this data is coming w= ith missing values.
Do you know if this is an issue of length of the field? or issue of the=
GeoODK app that's sending the info with some missing characters?
[image: bug1] https://cloud.githubusercontent.com/assets/4431392/8811144/9042cf88-2fb= 9-11e5-9669-c641aea8ecca.jpg
[image: bug2] https://cloud.githubusercontent.com/assets/4431392/8811100/0e812e68-2fb= 9-11e5-82d0-15465ce7e7fe.jpg
Data is always supposed to be an array of coordinates separated by a semicolon, where each coordinate is a 4-value array separated by spaces= .
Is this an issue of Aggregate receiving/exporting the data? or an issue= of GeoODK sending it?
=E2=80=94 Reply to this email directly or view it on GitHub https://github.com/opendatakit/opendatakit/issues/1163.
=
Mitch Sundt Software Engineer University of Washington [email protected]
-- =
You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/opendatakit/aggregate/issues/76#issuecomment-321952018=
----==_mimepart_598e683f24961_dca3f8fdce77c2c1214e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Comment =
by mitchellsundt
Tuesday Jul 21, 2015 at 23:41 GMT
ODK Aggregate has a default storage length of 255 characters.
It is entirely possible this is an issue if you are trying to capture =
more
than 8 coordinates per data capture. i.e., if you assume a worst-case
geopoint of 10-digit decimal numbers, then you would consume 4*10 + 4 =3D=
=3D 44
characters per geopoint in a geotrace. This would limit you to no more
than 5 coordinates per data capture. If you assume 2 10-digit values and=
2
3-character values (0.0), this would give 30 characters per geopoint,
=
limiting you to no more than 8 coordinates per data capture.
I forget whether the odk:length attribute is recognized on geotrace /
geoshape fields. See
https://opendatakit.org/help/form-design/guidelines/#data=
store_string_length
Try specifying that; the form_id will need to be changed to get the le=
ngth
setting to be respected (you cannot simply modify the existing form
definition to add an odk:length attribute). Please let me know whether
there is an error when you attempt to upload a form with this setting and=
,
if not, whether or not adding it resolves the 255-character limit problem=
.
If it works, I will update the documentation calling this out as a concer=
n
and work-around.
On Tue, Jul 21, 2015 at 1:03 PM, Juli=C3=A1n R. Figueroa
Attention! We're housekeeping! This issue will automatically be closed if no feedback is received in one week.
If this issue is important to you or you can provide more information about it, please, do so as soon as possible :)
