Glad to see that #Trajectools passed the new #QGIS plugin security checks right out of the gate https://plugins.qgis.org/plugins/processing_trajectory/version/2.7.1/#security-tab
Glad to see that #Trajectools passed the new #QGIS plugin security checks right out of the gate https://plugins.qgis.org/plugins/processing_trajectory/version/2.7.1/#security-tab
@martinfleis following up on our chat at #SDSL2025, I finally found some time to see how a #QGIS Processing Algorithm Provider plugin can be unit tested. Here's what I've come up with so far:
https://codeberg.org/movingpandas/trajectools/src/branch/main/tests/test_run_algs.py
Next step: try to make it run on Codeberg CI
If you are at #EBDVF on Thursday and fancy some #MobilityDataAnalytics, come and join our final @emeraldseu event.
I'll be talking about #Trajectools for #QGIS and a similarly awesome @carto collaboration
From a bunch of csv files to a neat #SpatialAnalytics dataset:
Step-by-step GeoLife #GPS track collection processing with #DuckDB, #QGIS & #Trajectools
The last time I preprocessed the whole GeoLife dataset, I loaded it into PostGIS. Today, I want to share a new workflow that creates a (Geo)Parquet file and that is much faster. The dataset (GeoLifβ¦
At the #SDSL dev day today, experimenting with #pyogrio to address #Trajectools issues. Thanks @jorisvandenbossche for sharing your experience! π
In an attempt to speed-up (and make the conversion more robust, eg regarding datetime/timezone conversion and null values (https://codeberg.org/movingpandas/trajectools/issues/93)), we can try to use Arrow. Since QGIS currently does not support exporting a layer to Arrow, here is a test workaroun...
Been busy updating the #Trajectools archival records over at https://zenodo.org/records/17127311 in preparation for #SDSL2025 starting on Wednesday in Salzburg
Still need to check if it's possible / how to automatically publish to #Zenodo from #Codeberg
Changelog This release brings multiple usability enhancements: Added proper datetime fields in output layers (instead of previous string type fields). This enables us to directly use the output with e.g. the Temporal Controller. Made trajectory ID field optional (for input layers with only a single moving object), fixes #37 Improved help texts explaining trajectory ID and timestamp fields, fixes #35 Drop potential extraneous geometry columns from attribute table, fixes #44 Show better error message when NULL values cause parallel processing error, see #93
π€© #MobilityDataAnalytics & #GIScience all around:
Attending the @emeraldseu GA today. Presented progress on #Trajectools and our #explainableAI & #activeLearning for #MobilityDataScience. While simultaneously traveling to #AGIT2025 π
QGIS User Conf 2025 videos have landed!
The #QGISUC2025 team has done an awesome job recording and editing the conference presentations ...
http://anitagraser.com/2025/06/25/qgis-user-conf-2025-videos-have-landed/
Finally finished my #Trajectools presentation for #QGISUC2025 on Monday
May still have to cut here and there to stay within the time limit π