[Feature Request] User defined schedules
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by surveying the repository for its existing timestamp-alignment model and query interfaces, then define how regions, hierarchy, properties, geometry, schedules, and location queries fit together. Done requires an agreed scope and behavior for all six requested capabilities.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Inspections commonly include particular regions (e.g. grid cells in bathymetry, piles, etc), which may determine the types of data processing and analysis which need to occur. While naive data alignment by timestamp is definitely useful, more meaningful alignment is more likely based on user-defined regions, which may be defined by location data or time periods.
Describe the solution you'd like
- allow users to define regions with IDs
- support regions having a parent
- support properties/tags for regions (allows different types of analysis in different region types)
- support area polygons/central positions for regions (allows intelligent querying, and some level of plotting)
- support user-defined schedules that map time periods to region IDs (query timestamp -> most specific region ID)
- support location querying (query location -> most specific region ID)
Describe alternatives you've considered
| alternative | reason(s) why unsuitable |
|---|---|
| no regions, just timestamps | limits utility of alignment and analysis |
Additional context
- known regions could allow rough geo-tagging of photos even without a positioning system on the vehicle
- regions with locations and/or area polygons can be plotted, which can help make sense of data
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ES-Alexander/data-alignment
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
ES-Alexander/data-alignment#3 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
ES-Alexander/data-alignment#1 · 1 comment ·
All issues in ES-Alexander/data-alignment
Similar issues
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
PedestrianDynamics/pyFDS-Evac#552 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
resend/resend-skills#144 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
GNS3/gns3-server#2935 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TauricResearch/TradingAgents#1476 ·
Maintainers usually reply within 2 days