feat: bring everything over

Author: gadomski

.gitignore

@@ -0,0 +1,164 @@
+target/
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$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
+
+# 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
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.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/

CHANGELOG.md

@@ -0,0 +1,100 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Removed
+
+- Validation, pending <https://github.com/stac-utils/stac-rs/issues/517>
+
+### Changed
+
+- Moved out of the <https://github.com/stac-utils/stac-rs> into <https://github.com/gadomski/stacrs>
+
+## [0.2.2] - 2024-10-22
+
+### Added
+
+- Send user agent when searching ([#487](https://github.com/stac-utils/stac-rs/pull/487))
+
+## [0.2.1] - 2024-10-21
+
+### Added
+
+- More wheels ([#481](https://github.com/stac-utils/stac-rs/pull/481))
+
+## [0.2.0] - 2024-10-19
+
+### Added
+
+- `version` ([#476](https://github.com/stac-utils/stac-rs/pull/476))
+
+### Changed
+
+- Moved docstrings to stub file ([#468](https://github.com/stac-utils/stac-rs/pull/468))
+
+### Removed
+
+- `pystac` ([#468](https://github.com/stac-utils/stac-rs/pull/468))
+
+## [0.1.3] - 2024-10-17
+
+### Added
+
+- Experimental DuckDB 🦆 search on **stac-geoparquet** files ([#458](https://github.com/stac-utils/stac-rs/pull/458))
+
+## [0.1.2] - 2024-09-22
+
+### Changed
+
+- Return the item count from `search_to` ([#426](https://github.com/stac-utils/stac-rs/pull/426))
+
+## [0.1.1] - 2024-09-21
+
+### Added
+
+- Extension module feature
+
+### Changed
+
+- Use Github Pages for docs ([#420](https://github.com/stac-utils/stac-rs/pull/420))
+
+## [0.1.0] - 2024-09-20
+
+### Added
+
+- `migrate_href` ([#334](https://github.com/stac-utils/stac-rs/pull/334))
+- `search` and `search_to` ([#387](https://github.com/stac-utils/stac-rs/pull/387))
+- `read`, `write`, and `pystac` ([#418](https://github.com/stac-utils/stac-rs/pull/418))
+
+## [0.0.3] - 2024-08-29
+
+### Added
+
+- `migrate` ([#309](https://github.com/stac-utils/stac-rs/pull/309))
+- `validate` and docs ([#307](https://github.com/stac-utils/stac-rs/pull/307))
+
+## [0.0.2] - 2024-08-28
+
+Non-functional release to fix releasing from Github actions.
+
+## [0.0.1] - 2024-08-28
+
+Initial release.
+
+[Unreleased]: https://github.com/stac-utils/stac-rs/compare/python-v0.2.2...main
+[0.2.2]: https://github.com/stac-utils/stac-rs/compare/python-v0.2.1...python-v0.2.2
+[0.2.1]: https://github.com/stac-utils/stac-rs/compare/python-v0.2.0...python-v0.2.1
+[0.2.0]: https://github.com/stac-utils/stac-rs/compare/python-v0.1.3...python-v0.2.0
+[0.1.3]: https://github.com/stac-utils/stac-rs/compare/python-v0.1.2...python-v0.1.3
+[0.1.2]: https://github.com/stac-utils/stac-rs/compare/python-v0.1.1...python-v0.1.2
+[0.1.1]: https://github.com/stac-utils/stac-rs/compare/python-v0.1.0...python-v0.1.1
+[0.1.0]: https://github.com/stac-utils/stac-rs/compare/python-v0.0.3...python-v0.1.0
+[0.0.3]: https://github.com/stac-utils/stac-rs/compare/python-v0.0.2...python-v0.0.3
+[0.0.2]: https://github.com/stac-utils/stac-rs/compare/python-v0.0.1...python-v0.0.2
+[0.0.1]: https://github.com/stac-utils/stac-rs/releases/tag/python-v0.0.1
+
+<!-- markdownlint-disable-file MD024 -->

CODE_OF_CONDUCT

@@ -0,0 +1 @@
+../CODE_OF_CONDUCT

CONTRIBUTING.md

@@ -0,0 +1,24 @@
+# Contributing to **stacrs**
+
+First off, thanks for contributing!
+We appreciates you.
+
+## Testing
+
+We aim for comprehensive unit testing of this library.
+Please provide tests for any new features, or to demonstrate bugs.
+Draft pull requests with a failing test to demonstrate a bug are much appreciated.
+
+## Submitting changes
+
+Please open a [pull request](https://docs.github.com/en/pull-requests) with your changes -- make sure to include unit tests.
+Please follow standard git commit formatting (subject line 50 characters max, wrap the body at 72 characters).
+
+We use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/).
+Your commits do not have to but if you'd like to format them this way, we would be grateful.
+
+If you can, use `git rebase -i` to create a clean, well-formatted history before opening your pull request.
+If you need to make changes after opening your pull request (e.g. to fix CI breakages) we will be grateful if you squash those fixes into their relevant commits.
+
+Thanks so much! \
+-Pete Gadomski