You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sdap.apache.org by "Frank Greguska (JIRA)" <ji...@apache.org> on 2019/07/15 05:08:00 UTC

[jira] [Created] (SDAP-196) Account for time when finding closest match

Frank Greguska created SDAP-196:
-----------------------------------

             Summary: Account for time when finding closest match
                 Key: SDAP-196
                 URL: https://issues.apache.org/jira/browse/SDAP-196
             Project: Apache Science Data Analytics Platform
          Issue Type: Improvement
          Components: nexus
            Reporter: Frank Greguska
            Assignee: Frank Greguska


[https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms_spark/Matchup.py#L467-L484]

 

As you can see, we do only take into account spatial distance, not time distance. This would be where we need to modify the code to also take into account time distance when trying to find the closest match.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)