opentrash 0.0.0__tar.gz

opentrash-0.0.0/.gitignore

@@ -0,0 +1,228 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+_internal/
+private/
+data/raw/
+data/cache/
+*.parquet
+*.csv
+*.xlsx
+secrets/
+credentials/

opentrash-0.0.0/LICENSE

@@ -0,0 +1,23 @@
+cat > LICENSE <<'EOF'
+MIT License
+
+Copyright (c) 2026 Mohamad Yassin
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the “Software”), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+EOF

opentrash-0.0.0/PKG-INFO

@@ -0,0 +1,110 @@
+Metadata-Version: 2.4
+Name: opentrash
+Version: 0.0.0
+Summary: Cloud-native geospatial tools for residential waste operations.
+Project-URL: Homepage, https://github.com/OWNER/opentrash
+Project-URL: Documentation, https://OWNER.github.io/opentrash/
+Project-URL: Repository, https://github.com/OWNER/opentrash
+Author: AI Research Corps (AIRC)
+License: cat > LICENSE <<'EOF'
+        MIT License
+        
+        Copyright (c) 2026 Mohamad Yassin
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the “Software”), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+        EOF
+License-File: LICENSE
+Keywords: cloud-native,duckdb,geospatial,gis,routing,waste-management
+Classifier: Development Status :: 1 - Planning
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Topic :: Scientific/Engineering :: GIS
+Requires-Python: >=3.11
+Provides-Extra: dev
+Requires-Dist: build; extra == 'dev'
+Requires-Dist: pytest; extra == 'dev'
+Requires-Dist: ruff; extra == 'dev'
+Requires-Dist: twine; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: mkdocs-material; extra == 'docs'
+Description-Content-Type: text/markdown
+
+# opentrash
+
+> Cloud-native geospatial tools for residential waste operations.
+
+`opentrash` is an open source Python package for analyzing residential solid
+waste collection operations using GPS telematics, enterprise waste-management
+data, and municipal parcel layers. It produces **RouteView** — a self-contained
+interactive HTML map for any route on any day — and detects per-parcel weekly
+and biweekly service **patterns** over time.
+
+The same tools enterprise fleet software sells for six figures, built on open
+standards and open data, runnable on a laptop.
+
+## Status
+
+🚧 **Phase 0 — skeleton.** Version `0.0.0` is a name placeholder; the package is
+not yet functional. It is being built lesson by lesson alongside its
+documentation site and a public course.
+
+## What it will do
+
+- **RouteView** — one route + one day → an interactive HTML map (route polygon,
+  GPS trail, landfill tips, parcels served vs missed, tonnage).
+- **Patterns** — long GPS history → per-parcel weekly/biweekly service
+  signatures, as a portable parquet file RouteView can optionally consume.
+
+## Roadmap
+
+- **RouteEdit** — interactive route-editing tool, sister to RouteView.
+- **Sample synthetic data** — redistributable dataset for tutorials.
+- **Cloud-hosted demo** — publicly browsable RouteView instance.
+- **Hardware integrations** — RFID container reader, vehicle LiDAR.
+
+## Documentation
+
+The documentation site is built with MkDocs Material and deployed to GitHub
+Pages. To preview locally:
+
+```bash
+pip install mkdocs-material
+mkdocs serve
+```
+
+## Development
+
+```bash
+conda create -n opentrash python=3.11 -y
+conda activate opentrash
+pip install -e ".[dev,docs]"
+```
+
+## License
+
+Source-available under a non-commercial license. See [LICENSE](LICENSE).
+Commercial licensing inquiries: contact AIRC.
+
+## About
+
+An open source project under
+[AI Research Corps (AIRC)](https://airesearchcorps.org/), a 501(c)(3) nonprofit.

opentrash-0.0.0/README.md

@@ -0,0 +1,60 @@
+# opentrash
+
+> Cloud-native geospatial tools for residential waste operations.
+
+`opentrash` is an open source Python package for analyzing residential solid
+waste collection operations using GPS telematics, enterprise waste-management
+data, and municipal parcel layers. It produces **RouteView** — a self-contained
+interactive HTML map for any route on any day — and detects per-parcel weekly
+and biweekly service **patterns** over time.
+
+The same tools enterprise fleet software sells for six figures, built on open
+standards and open data, runnable on a laptop.
+
+## Status
+
+🚧 **Phase 0 — skeleton.** Version `0.0.0` is a name placeholder; the package is
+not yet functional. It is being built lesson by lesson alongside its
+documentation site and a public course.
+
+## What it will do
+
+- **RouteView** — one route + one day → an interactive HTML map (route polygon,
+  GPS trail, landfill tips, parcels served vs missed, tonnage).
+- **Patterns** — long GPS history → per-parcel weekly/biweekly service
+  signatures, as a portable parquet file RouteView can optionally consume.
+
+## Roadmap
+
+- **RouteEdit** — interactive route-editing tool, sister to RouteView.
+- **Sample synthetic data** — redistributable dataset for tutorials.
+- **Cloud-hosted demo** — publicly browsable RouteView instance.
+- **Hardware integrations** — RFID container reader, vehicle LiDAR.
+
+## Documentation
+
+The documentation site is built with MkDocs Material and deployed to GitHub
+Pages. To preview locally:
+
+```bash
+pip install mkdocs-material
+mkdocs serve
+```
+
+## Development
+
+```bash
+conda create -n opentrash python=3.11 -y
+conda activate opentrash
+pip install -e ".[dev,docs]"
+```
+
+## License
+
+Source-available under a non-commercial license. See [LICENSE](LICENSE).
+Commercial licensing inquiries: contact AIRC.
+
+## About
+
+An open source project under
+[AI Research Corps (AIRC)](https://airesearchcorps.org/), a 501(c)(3) nonprofit.

opentrash-0.0.0/__init__.py

@@ -0,0 +1,8 @@
+"""opentrash — cloud-native geospatial tools for residential waste operations.
+
+This package is being built lesson by lesson. At Phase 0 it is an empty
+skeleton; each lesson adds a module (core, prep, tonnage, patterns, routeview,
+and so on). See the course hub for the lesson series.
+"""
+
+__version__ = "0.0.0"

opentrash-0.0.0/docs/docs.yml

@@ -0,0 +1,32 @@
+# Builds the MkDocs documentation site and deploys it to the gh-pages branch
+# on every push to main. Enable Pages in repo Settings -> Pages -> Deploy from
+# branch -> gh-pages -> / (root).
+
+name: Deploy docs
+
+on:
+  push:
+    branches:
+      - main
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install docs dependencies
+        run: pip install mkdocs-material
+
+      - name: Build and deploy
+        run: mkdocs gh-deploy --force

opentrash-0.0.0/docs/index.md

@@ -0,0 +1,43 @@
+# opentrash
+
+> Cloud-native geospatial tools for residential waste operations.
+
+!!! note "Work in progress"
+    This documentation site is being built lesson by lesson alongside the
+    package itself. Right now it's a skeleton — check back as the project grows.
+
+`opentrash` is an open source Python package for analyzing residential solid
+waste collection operations using GPS telematics, enterprise waste-management
+data, and municipal parcel layers.
+
+## What it does
+
+**RouteView** — given one route and one day, produces a self-contained
+interactive HTML map: route polygon, GPS trail, landfill tips, parcels served
+vs missed, and tonnage delivered.
+
+**Patterns** — given a long GPS history, detects each parcel's weekly and
+biweekly service signature. An optional companion to RouteView.
+
+## Installation
+
+```bash
+pip install opentrash
+```
+
+!!! warning
+    The package is at version `0.0.0` (name placeholder). It is not yet
+    functional. Follow the project to know when the first usable release lands.
+
+## Learn how it's built
+
+Want to understand how this package is built from scratch? There's a full
+course that walks through it lesson by lesson. See the course hub (link to be
+added).
+
+## About
+
+`opentrash` is an open source project under
+[AI Research Corps (AIRC)](https://airesearchcorps.org/), a 501(c)(3) nonprofit.
+
+Source-available under a non-commercial license.

opentrash-0.0.0/mkdocs.yml

@@ -0,0 +1,51 @@
+# MkDocs configuration for the opentrash documentation site.
+# Grows lesson by lesson. At Phase 0 it serves a single placeholder page.
+
+site_name: opentrash
+site_description: Cloud-native geospatial tools for residential waste operations.
+# Update these to your actual URLs once the repo and Pages exist.
+site_url: https://OWNER.github.io/opentrash/
+repo_url: https://github.com/OWNER/opentrash
+repo_name: OWNER/opentrash
+
+theme:
+  name: material
+  palette:
+    # Light mode
+    - scheme: default
+      primary: black
+      accent: cyan
+      toggle:
+        icon: material/weather-night
+        name: Switch to dark mode
+    # Dark mode
+    - scheme: slate
+      primary: black
+      accent: cyan
+      toggle:
+        icon: material/weather-sunny
+        name: Switch to light mode
+  features:
+    - navigation.instant
+    - navigation.tracking
+    - navigation.sections
+    - navigation.top
+    - search.suggest
+    - search.highlight
+    - content.code.copy
+
+markdown_extensions:
+  - admonition
+  - pymdownx.details
+  - pymdownx.superfences
+  - pymdownx.highlight:
+      anchor_linenums: true
+  - pymdownx.inlinehilite
+  - toc:
+      permalink: true
+
+nav:
+  - Home: index.md
+  # Lessons add pages here as the package grows, e.g.:
+  # - Getting started: getting-started.md
+  # - API reference: reference/...

opentrash-0.0.0/pyproject.toml

@@ -0,0 +1,61 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "opentrash"
+version = "0.0.0"
+description = "Cloud-native geospatial tools for residential waste operations."
+readme = "README.md"
+requires-python = ">=3.11"
+license = { file = "LICENSE" }
+authors = [
+    { name = "AI Research Corps (AIRC)" },
+]
+keywords = [
+    "geospatial",
+    "waste-management",
+    "gis",
+    "duckdb",
+    "routing",
+    "cloud-native",
+]
+classifiers = [
+    "Development Status :: 1 - Planning",
+    "Intended Audience :: Science/Research",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Topic :: Scientific/Engineering :: GIS",
+]
+
+# Runtime dependencies are intentionally minimal at Phase 0.
+# Lessons add these as the corresponding modules are built.
+dependencies = []
+
+[project.optional-dependencies]
+# Documentation tooling (used to build the docs site).
+docs = [
+    "mkdocs-material",
+]
+# Development + testing tooling.
+dev = [
+    "pytest",
+    "ruff",
+    "build",
+    "twine",
+]
+
+[project.urls]
+# Update these to your actual repo / docs URLs once they exist.
+Homepage = "https://github.com/OWNER/opentrash"
+Documentation = "https://OWNER.github.io/opentrash/"
+Repository = "https://github.com/OWNER/opentrash"
+
+[tool.hatch.build.targets.wheel]
+packages = ["opentrash"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py311"