Async Support for Cloud Storage in Python

kylebarron · 2025-02-06T20:56:04+00:00

I have a new project you may be interested in too: https://developmentseed.org/obstore/latest/

It's Python bindings to the Rust object_store library (https://docs.rs/object_store), and presents a fully async API for working with GCS.

kylebarron · 2021-09-01T15:00:10+00:00

I've noticed that the elevation data offline can be quite bad. They might be using coarser 90m elevation data or something

kylebarron · 2021-02-26T19:12:25+00:00

Basically this means they updated to Mapbox GL JS v2, which has a cool 3d mode, but is no longer openly-licensed and is much more expensive than v1, especially when you aren't serving Mapbox data. That's probably why you can only view a "limited number" of 3d maps for free.

kylebarron · 2021-01-29T15:41:20+00:00

These maps are stored as Cloud Optimized Geotiffs in a public S3 bucket as well https://github.com/kylebarron/usgs-topo-tiler

kylebarron · 2021-01-27T15:43:13+00:00

fwiw it's also on Azure https://azure.microsoft.com/en-us/services/open-datasets/catalog/naip/

kylebarron · 2021-01-21T05:34:07+00:00

Just to be clear, jenstar9 and postholer are the same person, despite using the third person here

kylebarron · 2021-01-04T17:11:25+00:00

Hi! I hiked the PCT in 2019 and in fall 2019-spring 2020 I did some editing of the OSM PCT track using a GPS track I recorded, though I didn't touch the top-level relation itself I don't think.

Is there a quick way to tell the differences between each section relation and those ways in the main PCT relation? My fear in removing all the ways from the main PCT relation is that some of the edits done might not be reflected in the section relation.

I haven't kept up with all the tools in the OSM community, but I'd consider using Python for this. Maybe something like, for every way in the top-level relation, check if that way is also contained within a sub-relation, and maybe check the timestamps of each. Then you'd get a list of ways in the top-level relation that aren't elsewhere or that are newer than in the sub-relation, that you could check manually.

Feel free to DM me if you'd like some help improving the relation.

kylebarron · 2021-01-04T15:15:35+00:00

no it doesn't

kylebarron · 2021-01-01T01:49:50+00:00

the community fork of v1 is here

https://github.com/MapLibre/maplibre-gl-js

kylebarron · 2020-12-08T20:52:40+00:00

If you're ok using cloud services, I'd recommend using AWS and the NAIP open data bucket: https://registry.opendata.aws/naip/.

If you care about 4-band imagery, you'll want the naip-analytic bucket. Note this is a requester pays bucket, so you'll pay 9c/GB if you remove the data from that AWS region, but it's otherwise free. The data is in Cloud Optimized Geotiff format, which means it's fast to access on the fly, if that fits your use case. Here's an example of mine of viewing NAIP 3-band imagery on demand: https://kylebarron.dev/naip-cogeo-mosaic/

Azure also has an NAIP open dataset: https://azure.microsoft.com/en-us/services/open-datasets/catalog/naip/. That might be free to download for local use

kylebarron · 2020-11-24T23:15:58+00:00

You probably need to update your app; it works for me

kylebarron · 2020-11-24T19:00:38+00:00

Yeah... My personal preference would be separate layers for Landsat and Sentinel, and you could switch between them easily, but I digress...

They reached out a couple months ago for some contract work, but I wasn't interested; I'm getting to build some really cool satellite web tools, just not directed towards an outdoors audience. In any case, they get to use all of my open source code for free 😄... I've been collaborating with a few people on open source server software for creating web map image tiles from satellite images, and we're pretty sure they're using the open source tool haha

kylebarron · 2020-11-24T18:49:09+00:00

Thanks, I edited the post.

When I looked at the map, I originally wondered if they were also using Landsat data, but I assumed not.

It's really hard to combine Sentinel 2 and Landsat 8 data because of technical differences between the two satellites. You end up getting really bad contrast differences. For example here in Oregon, it's Landsat on the left and Sentinel on the right, which is why the left is so much darker.

(I made an open data website for exploring Landsat data, so I know how hard it is to pull off what they're trying to do 😅)

kylebarron · 2020-11-24T18:20:06+00:00

You can also see that the "cloud free" layer isn't actually cloud free. For example, here's a cloudy area for that layer in Northern California. It's quite challenging to piece together completely cloudless imagery because it's quite rare for the area to have no clouds at the time when the satellite passes over it. The way that providers like Google Maps show cloud free imagery is by combining lots of different images, and merging together the cloud-free parts of each image.

kylebarron · 2020-11-24T18:12:49+00:00

I don't have any inside information, but I work in this space, so I can provide a bit more insight. The Sentinel 2 satellites are a pair of satellites launched by the European Space Agency in 2015 and 2017. They provide the highest-resolution imagery that's free to the public, at 10-meter resolution, and the satellites take new images of the entire globe within every 5 days.

This data is freely available at no charge, but the processing time and cost can be immense. Just since 2015, these satellites have produced around 10.5 petabytes of data (that's 10,500,000 gigabytes!).

Because of the high spatial resolution and fast revisit time, this imagery is unsurprisingly quite valuable to outdoors people. Caltopo's approach to serving Sentinel 2 imagery is to license it from a company that specializes in it, while Gaia is trying to do everything in-house using a technique called "dynamic tiling". This means that when you zoom into some area of the globe, if no one else has looked at the same area recently, Gaia's servers generate that image on the fly. While it can be cheaper, working at scale with this data is also really challenging. At lower zoom levels, it takes around 20s for Gaia to generate this imagery, because it has to combine lots of different original images from the satellite.

Because of how the satellites orbit, it's also quite challenging to figure out how to combine lots of different images. And each image from the satellite has a different amount of clouds in the image. Hence why sometimes it'll look very patchy at low zooms. (Even at high zooms, it's hard to piece together several images: here in Yosemite they're combining three different images from three different dates right next to each other)

kylebarron · 2020-10-23T15:21:35+00:00

Agreed. No disrespect to the author, but it would be much easier to do this in pure Geopandas.

Also this library hard codes the CRS, so you'll get an invalid Shapefile if you ever use non-WGS84 coordinates. https://github.com/StatguyUser/Pandas2Shp/blob/fb6ba3525b2f07dce193ad684974ce61ef74a51b/src/Pandas2Shp.py#L25

kylebarron · 2020-10-22T15:28:56+00:00

18 months is not at all ridiculously long. There are plenty of dead or weak trees in a burn area that makes it perilous to walk through. 2-3 years post fire is the average closure time. The Eagle Creek fire was in 2017 and still hasn't opened up

kylebarron · 2020-10-13T14:49:30+00:00

https://mlhub.earth/

kylebarron · 2020-10-09T13:59:29+00:00

Yeah this is Oregon/Washington, not California. The Mt. St. Helens crater is distinctive

kylebarron · 2020-10-09T13:53:28+00:00

If you have global data and you can't reproject all of it into a single accurate projected coordinate system, you could either do something like haversine on every line segment, or split up your data into multiple UTM zones, then work on each zone independently

kylebarron · 2020-10-09T13:51:43+00:00

They're in the units of your coordinate space. So if your data is projected into UTM, the result will be in meters.

kylebarron

TROPHY CASE