Aggregate is unable to export to KML when the form contains a repeat observation about aggregate HOT 6 OPEN

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

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

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.

This will be in the next server update.