Specify: no accepted georeference

[MortenHofft]

I notice that locations do not have an accepted georeference. But they are georeferenced (aka they appear in the georeference table). In this case I think it is pretty clear that it just means that they are all accepted. But in the model I assume this is inteded to mean: someone provided these coordinates, but we do not acknowledge it as being correct. So it isn't flagged as accepted.

@tucotuco Does it mean that we ought to show it as dubious somehow? Since it isn't accepted?
Or does that flag only have meaning when there are multiple georefernces?

[tucotuco]

@MortenHofft In the Specify case, there is only one georeference per location, and it is by default accepted. As such, the accepted_georeference_id should be filled in in the location table.

In general we would expect there to be just one georeference, and that it would be accepted, but there are plenty of cases where there is a history of georeferencing, and with automated tools providing georeferences pre- or post- aggregation, this might start to happen even more often. Also in general there would be an accepted georeference, even if there is a list of them. But, it could happen that there is one or more georeference, and none of them is accepted. In that case a georeference would point to the location record they it is a georeference for, but the location would not point back to the georeference as the accepted one.

One aspect of the dubiousness of a georeference would actually be captured in georeference_verification_status, and that would be at the level of the Occurrence, because it is a statement about the georeference with respect to that Occurrence, not the georeference with respect to the description of the location.

[MortenHofft]

I'm happy to leave the data as is for this exercise. Just to say, that I do not expect you to change anything @acbentley

But for the purpose of exploring the UI I will continue to enrich some of your specimens @acbentley, but will just do so as scripts we can run after imports. Simply because it is interesting examples that is a nice challenge for the UI. I hope that is okay with you.

In this case I will update entity dcc04c84-1ed3-11e3-bfac-90b11c41863e with an accepted georeference

UPDATE "location"  
SET accepted_georeference_id = 'bae150cb-a39d-150b-7231-7c140b8f120a' 
WHERE location_id ='39b9075e-1662-4dc4-8442-e1609c6ac165'

[acbentley]

Have at it :)

[acbentley]

It is difficult for me to make that connection as the georeference_id had to be created by me in post-process as we do not have GUIDs for georeferences in Specify.