https://github.com/developmentseed/stac-map
A map-first STAC search and visualization tool, with stac-geoparquet support
https://github.com/developmentseed/stac-map
stac stac-geoparquet
Last synced: 3 months ago
JSON representation
A map-first STAC search and visualization tool, with stac-geoparquet support
- Host: GitHub
- URL: https://github.com/developmentseed/stac-map
- Owner: developmentseed
- License: mit
- Created: 2025-05-19T17:37:38.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2026-01-12T19:36:04.000Z (3 months ago)
- Last Synced: 2026-01-12T21:33:07.007Z (3 months ago)
- Topics: stac, stac-geoparquet
- Language: TypeScript
- Homepage: https://developmentseed.org/stac-map/
- Size: 5.76 MB
- Stars: 55
- Watchers: 4
- Forks: 7
- Open Issues: 32
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# stac-map
[](https://github.com/developmentseed/stac-map/actions/workflows/ci.yaml)
[](https://github.com/developmentseed/stac-map/deployments/github-pages)
[](https://github.com/developmentseed/stac-map/releases)
The map-first, single-page, statically-hosted STAC visualizer at .
Includes:
- Natural language collection search
- **stac-geoparquet** visualization, upload, and download
> [!WARNING]
> This application is in its infancy :baby: and will change significantly and/or break at any time.
## Development
Get [yarn](https://yarnpkg.com/), then:
```shell
git clone git@github.com:developmentseed/stac-map
cd stac-map
yarn install
yarn dev
```
This will open a development server at .
We have some code quality checks/tools:
```shell
yarn lint
yarn format
```
And some simple tests:
```shell
yarn playwright install
yarn test
```
## Contributing
We have some [architecture documentation](./docs/architecture.md) to help you get the lay of the land.
We use Github [Pull Requests](https://github.com/developmentseed/stac-map/pulls) to propose changes, and [Issues](https://github.com/developmentseed/stac-map/issues) to report bugs and request features.
We use [semantic-release](https://github.com/semantic-release/semantic-release?tab=readme-ov-file) to create [releases](https://github.com/developmentseed/stac-map/releases).
This requires our commit messages to conform to [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
## Deploying
See [deploy.yaml](./.github/workflows/deploy.yaml) for a (drop-dead simple) example of deploying this application as a static site via Github Pages.
### White-label deployment
You can deploy your own customized version of stac-map using environment variables:
| Variable | Description | Default |
| ------------------- | ---------------------------------- | ------------------ |
| `VITE_BASE_PATH` | URL path prefix (e.g., `/my-app/`) | `/stac-map/` |
| `VITE_DEFAULT_HREF` | STAC resource to load on startup | None (shows intro) |
Example:
```shell
VITE_BASE_PATH=/ VITE_DEFAULT_HREF=https://my-stac-api.com yarn build
```
Or create a `.env` file:
```shell
VITE_BASE_PATH=/
VITE_DEFAULT_HREF=https://my-stac-api.com
```
Then run `yarn build` and deploy the `dist/` directory to your static hosting provider.
For an example of white-labeling **stac-map**, see https://github.com/gadomski/eoapi.stac-map.io.
## Versioning
For now, we use a form of [Sentimental Versioning](https://github.com/dominictarr/sentimental-versioning#readme), where we use MAJOR, MINOR, and PATCH versions to communicate the "weight" of changes.
We may formalize our releases into a stricter form of [Semantic Versioning](https://semver.org/) at some point in the future.