tin+topo
Briefly describe the purpose of this project here. What spatial problem does this solve? Who is the end user? What data does it produce?
This project follows the standard tin+topo template structure to keep data, exploration, and production code completely separated:
├── data/
│ ├── processed/ # Cleaned, derived, or finalized spatial data
│ └── raw/ # Original, unaltered spatial downloads (DO NOT COMMIT to Git)
├── notebooks/ # Jupyter Notebooks for spatial exploration and prototyping
├── scripts/ # Production-ready Python or Node.js scripts
├── .env.example # Template for local environment variables and secrets
├── .gitignore # Standard GIS ignore rules (blocks massive spatial binaries)
├── AGENTS.md # AI Coding Agent constraints and rules for TDF
├── README.md # Project documentation (You are here!)
└── requirements.txt # Python dependencies (pandas, geopandas, arcgis, etc.)
Clone this repository to your local machine (e.g., C:\github\[project-name]). Do not clone into a OneDrive-synced folder like Documents to avoid sync conflicts.
Never commit actual credentials to GitHub.
- Create a copy of
.env.exampleand rename it to.env. - Fill in your required credentials (e.g., AGOL Username, AGOL Password, API Keys) locally.
Install the required libraries to run this project:
# To install only the core production dependencies:
pip install -r requirements.txt
# To install all development tools (like JupyterLab) as well:
pip install -r requirements-dev.txt- Large Spatial Files: Do not commit
.shp,.gdb,.tif, or any large spatial binaries to this repository. - Raw Data: Store all raw downloads in
data/raw/. Treat this folder as read-only. - Outputs: Write all cleaned, intermediate, and final spatial outputs to
data/processed/.
This repository is pre-configured to work seamlessly with tin+topo's AI coding assistants and enterprise models.
- Please refer to
AGENTS.mdfor specific instructions on how agents should interact with this codebase.
- Project Owner: Colin T. Stiles | cts@tinandtopo.com
- Last Updated: [Date]