MEOS (Mobility Engine, Open Source) is a C library which enables the manipulation of temporal and spatio-temporal data based on MobilityDB's data types and functions.
PyMEOS is a library built on top of MEOS that provides all of its functionality wrapped in a set of Python classes.
For the PyMEOS CFFI library, the middle layer between MEOS and PyMEOS, see the PyMEOS CFFI repository.
Usage
Installation
You can install PyMEOS (pymeos and pymeos-cffi) using pip, conda, or from sources.
Using pip
pip install pymeos
PyMEOS wheel should be compatible with any system, but it is possible that the pre-built distribution is not available for PyMEOS CFFI for some OS/Architecture.
Using conda
PyMEOS is also available on the conda-forge channel. To install it, first add the conda-forge channel to your conda configuration:
conda config --add channels conda-forge
conda config --set channel_priority strict
Then, you can install PyMEOS using the following command:
conda install conda-forge::pymeos
Source installation
For detailed instructions on how to install PyMEOS from sources, see the installation page in the PyMEOS Documentation.
Sample code
IMPORTANT Before using any PyMEOS function, always call
pymeos_initialize. Otherwise, the library will crash with aSegmentation Faulterror. You should also always callpymeos_finalizeat the end of your code.
from pymeos import pymeos_initialize, pymeos_finalize, TGeogPointInst, TGeogPointSeq
# Important: Always initialize MEOS library
pymeos_initialize()
sequence_from_string = TGeogPointSeq(
string='[Point(10.0 10.0)@2019-09-01 00:00:00+01, Point(20.0 20.0)@2019-09-02 00:00:00+01, Point(10.0 10.0)@2019-09-03 00:00:00+01]')
print(f'Output: {sequence_from_string}')
sequence_from_points = TGeogPointSeq(instant_list=[TGeogPointInst(string='Point(10.0 10.0)@2019-09-01 00:00:00+01'),
TGeogPointInst(string='Point(20.0 20.0)@2019-09-02 00:00:00+01'),
TGeogPointInst(string='Point(10.0 10.0)@2019-09-03 00:00:00+01')],
lower_inc=True, upper_inc=True)
speed = sequence_from_points.speed()
print(f'Speeds: {speed}')
# Call finish at the end of your code
pymeos_finalize()
Output: [POINT(10 10)@2019-09-01 01:00:00+02, POINT(20 20)@2019-09-02 01:00:00+02, POINT(10 10)@2019-09-03 01:00:00+02]
Speeds: Interp=Step;[17.84556057812839@2019-09-01 01:00:00+02, 17.84556057812839@2019-09-03 01:00:00+02]
For more examples and use-cases, see PyMEOS Examples repository
Documentation
Visit our ReadTheDocs page for a more complete and detailed documentation, including an installation manual and several examples.
3 maintainers
Metadata
3 maintainers
Release files for pymeos 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pymeos-1.2.0.tar.gz | 88.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pymeos-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 216.7 kB
Release files / pymeos-1.2.0.tar.gz
| Download URL | pymeos-1.2.0.tar.gz |
|---|---|
| Size | 88.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f941599d6f836d785c3b9ae14b53dc86fcb67881e5b5669ec8c2804245f4d7a0
|
|
BLAKE2b-256 checksum How to use checksums |
bc39db0ff35f29da3cb3123db3a3352c61729d6dd7dbf79154829930ef3dd383
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 1, 2024.
Transparency logRelease files / pymeos-1.2.0-py3-none-any.whl
| Download URL | pymeos-1.2.0-py3-none-any.whl |
|---|---|
| Size | 128.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6037e8b5b67af169eaa615726cb5d964f879bd80afe967539cbe253a1fb2ac09
|
|
BLAKE2b-256 checksum How to use checksums |
4d333a80e6e6eba08568f1a26fbd74af3afeb027ed8babe428305ddaf3ce3161
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 1, 2024.
Transparency log
