Hi Scott, coordinateAccurracy is the uncertainty radius for lat/lon in decimal degrees which we interpret and keep directly on the Occurrence class: https://github.com/gbif/gbif-api/blob/master/src/main/java/org/gbif/api/model/occurrence/Occurrence.java#L121 https://github.com/gbif/dwc-api/blob/master/src/main/java/org/gbif/dwc/terms/GbifTerm.java#L41
Our processing right now only recognizes dwc:coordinatePrecision as a source for the accurracy: https://github.com/gbif/occurrence/blob/master/occurrence-processor/src/main/java/org/gbif/occurrence/processor/interpreting/LocationInterpreter.java#L167 As you have seen there is an open issue still to also interpret the uncertainty in meters: http://dev.gbif.org/issues/browse/POR-1804 We need to check if it is never populated which would be a bug, Markus > On 21 Jul 2015, at 09:24, Tim Robertson <trobertson at gbif.org> wrote: > > Hi Scott, > > I don?t recall any coordinateAccurracy but I might be mistaken > > There are coordinateUncertaintyInMeters and coordinatePrecision - could it be > those you were thinking of? We only return the verbatim values, and don?t do > any parsing of those. > > Thanks, > Tim > > On 20 Jul 2015, at 22:21, Scott Chamberlain <myrmecocystus at gmail.com> > wrote: > >> Hi all, >> >> Did the coordinateAccurracy used to exist and was removed at some point? I >> can see mention of it e.g., here >> http://dev.gbif.org/issues/browse/POR-1804?jql=text%20~%20%22coordinateAccurracy%22 >> - but perhaps it has been removed? >> >> I can see that the elevationAccuracy field is returned with many records, >> but haven't seen coordinateAccurracy in any records. >> >> Thanks! Scott >> _______________________________________________ >> API-users mailing list >> API-users at lists.gbif.org >> http://lists.gbif.org/mailman/listinfo/api-users > > _______________________________________________ > API-users mailing list > API-users at lists.gbif.org > http://lists.gbif.org/mailman/listinfo/api-users
