-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add areas #77
Add areas #77
Conversation
- We break up creating the filter expression for the processing script into functions - This is done in order to be able to reuse the code in another processing script - And if we need to change something later we don't have to edit both scripts
- Should be faster for filtering - The filter expression argument passed to TrajectoryLayer() becomes a bit obsolete. - I considered deleting it since I'm not sure we need it at all now but I guess there's not that much harm in keeping it around, maybe we'll need it later. - Also by deleting it you'd need to change some existing stuff
…ent-calculation-of-average-speed-of-trajectories-crossing-two-gates
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very good overall! However, there are some issues I noticed while testing the processing algorithms:
- If class of traveler is not set, vehicle_class field in resulting line/area layer will be empty
- Speed and acceleration are not rounded to digits precision in the exported gate/area layers
- Resulting trajectory layers could be named e.g. Trajectories - Areas and Trajectories - Gates for the sake of clarity
count_trajectories_area
connects trajectories with the same ID like this:
- Round avg speed / acceleration to a precision of 2 - If points were not filtered by class of traveler, set 'vehicle_class' to 'all'
@msorvoja I've addressed your comments, ready for another round. Also something I noticed and a fix is included: when exporting trajectories/gates/areas, the 'fid' field started incrementing from 0, for features the indexing starts typically from 1 so I changed that as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything seems to work now as intended, great job!
Fixes #74
#76 is included.
QgsVectorLayer.materialize
method