Matthew Perry

@sgillies the repo name has [special importance to homebrew's tap system](https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/brew-tap.md#repository-naming-conventions-and-assumptions) - it assumes that you've got `homebrew-` as the repo name and will install with `brew install //` -...

We could just name it `homebrew-mapbox` making the command sound like an incantation ``` brew install mapbox/mapbox/mapbox ``` 

I just went ahead with `homebrew-cli` as the working repo: https://github.com/mapbox/homebrew-cli We can adjust later if needed.

Another option to consider (though a bit on the experimental side) would be to transpile the Python code to Go using Google's [Grumpy](https://github.com/google/grumpy). This could produce static binaries on all...

Hi all, I'd like to contribute docs and code to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of...

Possibly. Try `rio info` on the raster and check the transform.

With that transform, it's likely that your data lacks georeferencing according to rasterio/GDAL. That's the identity transform and is unlikely the true transform for your data unless you have exactly...

@mataslauzadis I definitely see the need for better feedback while iterating through input features. I'm not sure the best way to implement it though - consider that `tqdm` and similar...

Hey @brendancol, I'd say `rasterstats` is designed for the _many polygons, one raster_ scenario so it's already fairly optimal - caching won't help much under that use case since you...

@johanvdw @brendancol so if the optional mini_raster was supplied, we would skip the rasterization step? At a high level, that seems like a reasonable approach. You'd still have to call...