search

adonmo / meos

Mobility Engine, Open Source
https://adonmo.github.io/meos/
MIT License
21 stars 3 forks source link

MEOS integration with MoveTK #33

Open aniketmitra001 opened 3 years ago

aniketmitra001 commented 3 years ago

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?

chaitan94 commented 3 years ago

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 :smile:. 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 commented 3 years ago

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.