Hi Tim and Markus, Thanks for your quick responses.
coordinateUncertaintyInMeters is what I wanted, thanks for pointing that out. Does that field ever show up in search results though? e.g., from /occurrence/search I haven't seen it yet, but it does show up in verbatim results, e.g. http://api.gbif.org/v1/occurrence/1088909149/verbatim . But in the non-verbatim record of the same occurrence key coordinateUncertaintyInMeters isn't in the record http://api.gbif.org/v1/occurrence/1088909149/ Anyway, my users have requested this data (i.e., coordinateUncertaintyInMeters), but going to verbatim records for each occurrence key seems like a tedious approach. Will coordinateUncertaintyInMeters be populated in the results returned by the /occurrence/search route sometime in the future? If not, I can direct them to verbatim occurrence records. Best, Scott p.s. the occurrenceDetails field somehow got `http://unknown.org/` appended to the beginning of the field name, e.g, http://api.gbif.org/v1/occurrence/1088909149/ - I assume that is an error On Tue, Jul 21, 2015 at 1:46 AM Markus D?ring <mdoering at gbif.org> wrote: > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gbif.org/pipermail/api-users/attachments/20150721/ea619a5c/attachment.html>
