WKT (Polygon) not projected on occurrence detail page map

18414
Reporter: kbraak
Assignee: kbraak
Type: Improvement
Summary: WKT (Polygon) not projected on occurrence detail page map
Description: For LINESTRING representing ocean trawls it would be essential to represent direction with start and end indicated. Example http://www.gbif.org/occurrence/1229591899
Priority: Critical
Resolution: Duplicate
Status: Closed
Created: 2016-04-19 11:40:43.197
Updated: 2017-10-10 16:00:54.074
Resolved: 2017-10-10 16:00:54.053
        
    

Author: trobertson@gbif.org
Created: 2016-05-26 09:53:16.941
Updated: 2016-05-26 09:53:34.435
        
I'm not so sure it is essential.  Desirable yes.

Being able to say - "here is a route, which was covered between DD/MM/YYYY-HH:MM to DD/MM/YYYY-HH:MM during which species X was observed" is still useful information.
It is no different really to saying "species x was found within 1000m of lat,lng".

Slightly related might also be considering showing the other points of records of the same individualID (within the dataset).  They may or may not have timestamps, but if given, one could create a polyline.  That would be nice.

    

Author: hoefft
Comment: The data is not in sufficient quality to do so as it stands. Needs api work and communication with community. Kyle B is the first wave and have initiated a discussion with the community. Then we need to process/parse/filter and flag issues. Then we can show it on the occurrence page
Created: 2016-06-15 16:14:48.489
Updated: 2016-06-15 16:14:48.489

Author: kbraak@gbif.org
Created: 2016-06-15 16:25:41.903
Updated: 2016-06-15 16:25:41.903
        
Thank you Morten. Indeed I have proposed a DwC term change to make it easier and less error prone to store the footprintSRS of the footprintWKT. The status of this proposed change can be monitored in the following places:

DwC GitHub Issue: https://github.com/tdwg/dwc/issues/122
TDWG Content Mailing List Thread: http://lists.tdwg.org/pipermail/tdwg-content/2016-June/003617.html
    

Author: hoefft
Comment: while waiting for that there is an interim solution that works on non validated data https://github.com/gbif/portal16/issues/577
Created: 2017-10-10 16:00:54.072
Updated: 2017-10-10 16:00:54.072