You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: services might have incompatible dependencies which you can resolve by using virtual environnement per service
23
+
22
24
**pre-commit**
23
25
24
26
This repo is set to use `pre-commit` to run *isort*, *ruff*, *pydocstring*, *black* ("uncompromising Python code formatter") and mypy when committing new code.
-**Focus on your use case:**`eoAPI` is used for large-scale data processing, building geographic information systems (GIS), creating real-time data applications, climate research and environmental monitoring, machine learning model training, and more.
40
+
`eoAPI` is proudly open-source and driven by a dedicated community of contributors. We believe in the power of open collaboration and welcome anyone to contribute, discuss, and grow this tool with us. Join the conversations on [GitHub Discussions](https://github.com/developmentseed/eoAPI/discussions)and make a difference in the Earth Observation realm.
41
41
42
-
-**Unified Repository:**`eoAPI` provides a single, unified repository to several state-of-the-art Earth Observation (EO) data services, including Metadata search (STAC), Raster, and Vector services. This can simplify the process of accessing and working with these services.
43
-
44
-
-**Interoperability:**`eoAPI` is designed to enable interoperability among its included services. This can make building complex applications that leverage different types of EO data easier.
45
-
46
-
-**Open Source and Community Support:** As an open-source project, `eoAPI` allows developers to inspect its code, contribute to its development, and use it as a base for custom solutions. It also benefits from the support and innovation of a community of developers and EO data users.
47
-
48
-
-**Scalability and Flexibility:** Each service in `eoAPI` can be used or deployed independently, which provides a lot of flexibility. If a developer's application only requires one or two of eoAPI's services, they don't need to deploy the entire suite.
49
-
50
-
-**Facilitate Earth Observation Tasks:**`eoAPI` includes specialized tools for working with EO data, such as dynamic tiling, metadata searching, and features/vector tiles API. These can significantly facilitate EO data processing, analysis, and visualization.
51
-
52
-
-**Ease of Deployment:**`eoAPI` supports containerized deployment using Docker, making it easier to set up, scale, and maintain applications built on it. Spin up the demo locally and start experimenting in minutes.
53
-
54
-
---
55
-
56
-
## Services Overview
57
-
58
-
59
-
-**STAC Metadata**: Built with [stac-fastapi.pgstac](https://github.com/stac-utils/stac-fastapi) and extended with a custom extension to connect it to **`TiTiler`** and a **[Search Viewer](http://localhost:8081/index.html)**. See [docs](http://localhost:8081/docs) for API details.
60
-
61
-
-**Raster Tiles**: Built with [titiler-pgstac](https://github.com/stac-utils/titiler-pgstac) and [pgstac](https://github.com/stac-utils/pgstac) to enable large scale mosaic based on results of STAC searches queries. See [docs](http://localhost:8082/docs) for API details.
62
-
63
-
-**OGC Features & Vector Tiles**: Built with [tipg](https://github.com/developmentseed/tipg) to create a lightweight OGC Features and Tiles API with a PostGIS database. See [docs](http://localhost:8083/api.html) for API details.
64
-
65
-
See [service details](./docs/src/services-details.md) for more information.
66
-
67
-
*Note: The documentation links referenced require lauching the application with `docker-compose` or another deployment*.
68
42
69
43
---
70
44
71
45
## Getting started
72
46
73
47
- Clone the repository: `git clone https://github.com/developmentseed/eoAPI.git`
74
48
- Navigate to the project: `cd eoAPI`
75
-
- Run services with `docker-compose up`
49
+
- Run services with `dockercompose up`
76
50
- Follow the [MAXAR open data demo](https://github.com/vincentsarago/MAXAR_opendata_to_pgstac) (or get inspired by the other [demos](./demo/)) to load some data into eoAPI
77
-
-Checkout the [Search Viewer](http://localhost:8081/index.html), and the API documentation ([STAC Metadata](http://localhost:8081/docs), [Raster Tiles](http://localhost:8082/docs), [Vector Tiles](http://localhost:8083/api.html))
51
+
-Check out the [Search Viewer](http://localhost:8081/index.html), and the API documentation ([STAC Metadata](http://localhost:8081/docs), [Raster Tiles](http://localhost:8082/docs), [Vector Tiles](http://localhost:8083/api.html))
78
52
79
53
Alternatively, you may launch the application locally:
Note: services might have incompatible dependencies which you can resolve by using virtual environement per service
67
+
Note: services might have incompatible dependencies which you can resolve by using a virtual environment for each service
94
68
95
69
---
70
+
96
71
## Deployment
97
72
98
-
See [DEPLOYMENT.md](https://github.com/developmentseed/eoAPI/blob/main/infrastructure/DEPLOYMENT.md)
73
+
This repository has current runtimes that are consistently updated with new functionality.
74
+
75
+
The services can be deployed locally via docker with `docker-compose up`. The official runtimes can be launched with `docker-compose -f docker-compose.yml -f docker-compose.official.yml up stac-fastapi titiler-pgstac tipg`.
76
+
77
+
Two Infrastructure as Code (IaC) repositories are available:
78
+
-[eoapi-cdk](https://github.com/developmentseed/eoapi-cdk): A set of AWS CDK constructs to deploy eoAPI services
79
+
-[eoapi-k8s](https://github.com/developmentseed/eoapi-k8s): IaC and Helm charts for deploying eoAPI services on AWS and GCP
80
+
81
+
Finally, [eoapi-template](https://github.com/developmentseed/eoapi-template) is an AWS CDK app that shows how to configure the eoapi-cdk constructs.
99
82
100
83
## Contribution & Development
101
84
102
-
See [CONTRIBUTING.md](https://github.com/developmentseed/eoAPI/blob/main/CONTRIBUTING.md)
85
+
We highly value and rely on our community! Whether you're an expert or just getting started, you can make a difference. Here's how:
86
+
87
+
-**Contribute**: Check out our [CONTRIBUTING.md](https://github.com/developmentseed/eoAPI/blob/main/CONTRIBUTING.md) guide to understand how you can contribute.
88
+
-**Engage in Discussions**: Share your ideas, ask questions, or provide feedback through [GitHub Discussions](https://github.com/developmentseed/eoAPI/discussions). This is where most of our project conversations take place.
89
+
-**Report Issues**: Found a bug or have a feature request? Raise it on our [issues page](https://github.com/developmentseed/eoAPI/issues).
103
90
91
+
---
104
92
## License
105
93
106
-
See [LICENSE](https://github.com/developmentseed/eoAPI/blob/main/LICENSE)
94
+
At Development Seed, we believe in open collaboration and making tools and data more accessible. In line with this ethos, we've explicitly chosen a MIT license for `eoAPI`.
95
+
96
+
For full license details, see [LICENSE](https://github.com/developmentseed/eoAPI/blob/main/LICENSE).
107
97
108
98
## Authors
109
99
110
-
Created by [Development Seed](<http://developmentseed.org>)
100
+
Nurtured by [Development Seed](<http://developmentseed.org>)
111
101
112
102
See [contributors](https://github.com/developmentseed/eoAPI/graphs/contributors) for a listing of individual contributors.
Note: services might have incompatible dependencies which you can resolve by using virtual environnement per service
27
+
28
+
**pre-commit**
29
+
30
+
This repo is set to use `pre-commit` to run *isort*, *ruff*, *pydocstring*, *black* ("uncompromising Python code formatter") and mypy when committing new code.
0 commit comments