I don't think they are supported in geojson . Since it only relates to a
point and not other types of geometry we will store it probably is best to
store at least initially in seperate altitude and accuracy fields.

On Wednesday, January 22, 2014, Peter Lubell-Doughtie <
notifications@github.com> wrote:

> In onadata/apps/odk_logger/models/instance.py:
>
> >
> > -    def get_root_node(self):
> > -        self._set_parser()
> > -        return self._parser.get_root_node()
> > +        if len(geo_xpaths):
> > +            for xpath in geo_xpaths:
> > +                # TODO store the altitude and precision
>
> We will still have the info in the XML so we could re-parse when we have a
> useful method of adding it. Right now only longitude and latitude are being
> stored so this isn't different from what we are currently doing. PostGIS is
> supposed to support altitude through a z-dimension attribute but this
> didn't work out of the box. I talked with Ivan about precision and he said
> this isn't stored in the same record, we could have a precision field that
> maps to the entries in the geometry collection.
> … <#143b742004625596_>
> On Jan 21, 2014 5:00 PM, "ukanga" <notifications@github.com<javascript:_e({}, 'cvml', 'notifications@github.com');>>
> wrote: In onadata/apps/odk_logger/models/instance.py: > > - def
> get_root_node(self): > - self._set_parser() > - return
> self._parser.get_root_node() > + if len(geo_xpaths): > + for xpath in
> geo_xpaths: > + # TODO store the altitude and precision Is there a specific
> reason why altitude and precision could not be added at this particular
> time? I tend to see a lot records with the 4 values, does it mean we are
> likely to loose this information on migration? — Reply to this email
> directly or view it on GitHub<
> https://github.com/onaio/onadata/pull/128/files#r9056472> .
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/onaio/onadata/pull/128/files#r9060451>
> .
>