Aggregate is unable to export to KML when the form contains a repeat observation

[GoogleCodeExporter]

What steps will reproduce the problem?
1.use ODK Aggregate v1.0.1
2.Log into https://orrholly.appspot.com
Aggregate user: Student
Aggregate password: password
3.upload the attached file Lab-13v8_Biodiversity_v8.xml as a form
4.download form to Xoom Tablet on Kobo Collect App
5.send finished form back to Google App Engine site 
(https://orrholly.appspot.com) 
6. Try to export submission to KML with the following attributes:
Geopoint: location
Title: name
Picture: repeat_observation/image

What is the expected output? What do you see instead?
Should export KML.  Error message: Failure - will retry later

What version of the product are you using? On what operating system?
ODK Aggregate v1.0.1
Desktop Window 7
KoBo collect 1.1.7-rc-1
Motorola Xoom / Android Version 3.2.1

Please provide any additional information below.

Original issue reported on code.google.com by ho449@nyu.edu on 16 Nov 2011 at 1:52

Attachments:

• Lab-13v8_Biodiversity_v8.xml

[GoogleCodeExporter]

The error messages for this were not propagating back up to the user.  Kml 
generation has the following restriction:

Picture and Title must be in the submission (top-level) or must be in the same 
repeat group as the GeoPoint

In this case, the image is within a repeat group, but the geoPoint is at the 
top level. The fix is either to have the image at the top level or to have the 
geoPoint within the repeat group (you should be able to have a read-only field 
in the repeat group that holds a copy of the value from the top-level geopoint).

Original comment by mitchellsundt@gmail.com on 16 Nov 2011 at 6:59

• Changed state: Accepted
• Added labels: Aggregate

[GoogleCodeExporter]

Original comment by mitchellsundt@gmail.com on 1 Dec 2011 at 11:48

• Added labels: Documentation

[GoogleCodeExporter]

Hi Mitch -

The fix you mentioned above did not work.  I'm still getting the error message 
"Picture and Title must be in the submission (top-level) or must be in the same 
repeat group as the GeoPoint".  I've attached the form xml for review.

Thanks,
Holly Orr 
NYU

Original comment by ho449@nyu.edu on 20 Dec 2011 at 6:36

Attachments:

• SurveyingEnvironment.xml

[GoogleCodeExporter]

Unfortunately, the work-around I was suggesting is prevented by this issue:

http://code.google.com/p/opendatakit/issues/detail?id=563

The idea was to have the inner Geopoint have a calculate in its bind and be 
read-only. For clarity, I am renaming to the inner 
/data/repeat_observation/SiteLocation as 
/data/repeat_observation/SitePhotoLocation. The bind is then:

<bind nodeset="/data/repeat_observation/SitePhotoLocation" type="geopoint" 
calculate="/data/SiteLocation" readonly="true()"/>

Then you would have the SitePhotoLocation geopoint and image at the same level, 
and would only have to record the geopoint once.  When you Export to KML, you 
then choose the SitePhotoLocation (not the SiteLocation, which would also be 
listed) and the SitePhoto.

The cited Collect/javarosa issue prevents this.  The only work-around is to 
capture the geolocation separately with every photo.

Original comment by mitchellsundt@gmail.com on 23 Apr 2012 at 5:52

[GoogleCodeExporter]

This will be in the next server update.

Original comment by mitchellsundt@gmail.com on 12 Mar 2014 at 12:24

• Added labels: Mar2014