Skip to content
This repository has been archived by the owner on Nov 3, 2023. It is now read-only.

MEOS integration with MoveTK #33

Open
aniketmitra001 opened this issue Nov 10, 2020 · 2 comments
Open

MEOS integration with MoveTK #33

aniketmitra001 opened this issue Nov 10, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@aniketmitra001
Copy link

Hi Krishna

My name is Aniket and I am one of the engineers of MoveTK (https://github.com/heremaps/movetk). I am reaching out to you to see if you think there is a scope for collaboration between the two projects?

@aniketmitra001 aniketmitra001 added the enhancement New feature or request label Nov 10, 2020
@chaitan94
Copy link
Member

Hi Aniket, yes definitely. In fact, I was trying to go through MoveTK and reach out to you as well sometime this week myself.

First of all, great project! We need more such projects in the movement data analysis domain 😄. And as of my understanding of the project so far, MoveTK seems to be great at various spatiotemporal algorithms (simplification, clustering etc).

With MEOS, the main objective I am looking for is for it to act as a common engine/glue for movement data analysis tools [1]. So that libraries like MoveTK can work together with each other. As such, MEOS's data structures closely model the format defined by MobliityDB, which might very well possibly be in line with the OGC moving features standard going forward [2].

I think it would be really a great idea if MEOS and MoveTK interoperate. The most obvious first step I can see here is that MoveTK can start supporting the input/output of Trajectory objects in the MobilityDB's WKT-like format, by making use of MEOS's C++ API. I noticed you are already adding support to GeoJSON format, so this could be a great add. If implemented, one immediate benefit MoveTK's users can see from this would be that interacting with MobilityDB will become a breeze for them.

Let me know your thoughts on this. Or if you had any other ideas - I am open to hear any kind of ideas you might have.


[1] Reference to our position paper on this - https://arxiv.org/abs/2006.16900 (thanks to Anita Graser and Esteban Zimanyi on this)
[2] This is thanks to our MobilityDB team's co-founder Mahmoud, who is a chair of the working group for the moving feature standards https://www.ogc.org/projects/groups/movfeatswg

@aniketmitra001
Copy link
Author

Sounds like a good plan. As you suggested, it will be great if the Trajectory objects in MobilityDB can be passed to the spatiotemporal algorithms in MoveTK using MEOS's API. I will create an issue regarding the same in MoveTK.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants