Using Planetary Computer for web app backend to replace Google Earth Engine #297
Replies: 3 comments 1 reply
-
Not exactly the same, but you can achieve parts of what you're trying to do. Our STAC API returns URLs directly to blob storage, which you can read using any program that can make HTTP requests, so you can choose whatever kind of compute layer you want. If you're looking for a setup where you don't have any compute layer, you might want to look through our data API. That, along with our STAC API, powers our explorer. But you'll see that the data API is primarily focused on tiling and visualization. |
Beta Was this translation helpful? Give feedback.
-
Dear @staffordsmith83 @TomAugspurger Please check the R |
Beta Was this translation helpful? Give feedback.
-
Dear @staffordsmith83 Thanks to the excellent support provided by @TomAugspurger, |
Beta Was this translation helpful? Give feedback.
-
I have been building web applications using Googel Earth Engine as a geospatial processing backend. I make calls to GEE using the JS API, perform geospatial analysis on Earth Engine assets (including my own data that I have uploaded), and return the map results as tiled map services to my front end application.
Does Planetary Computer work like this?
With GEE I can easily perform things like image segmentation using google compute. I just call the operation from my front end by specifying algorithm parameters and datasets, and get a result to display in my front end.
I would love to replace this with Planetary Computer instead!
Beta Was this translation helpful? Give feedback.
All reactions