relationship to scikit-mobility about movingpandas HOT 2 CLOSED

Indeed, I've been in contact with the developers of scikit-mobility since summer 2019. One noteworthy difference is that they build directly on pandas and don't use geopandas. I tried to port their code to geopandas but go stuck. (This is the corresponding branch in my fork: https://github.com/anitagraser/scikit-mobility/tree/geodataframe)

Another implementation difference is that they use inheritance (a TrajDataFrame inherits pandas.DataFrame) while MovingPandas uses composition (a Trajectory has a geopandas.GeoDataFrame).

Converting between movingpandas.Trajectory and skmob.TrajDataFrame shouldn't be too hard.

from movingpandas.

For future reference: The fork above has one failing test where slicing a TrajDataFrame returns a GeoDataFrame instead of a TrajDataFrame.
anitagraser/scikit-mobility@34425e4

However, this seems to have been working correctly when TrajDataFrame was still a regular Pandas DataFrame. If anyone has an idea how to fix that, I'd love to hear it.

from movingpandas.