robosat
robosat copied to clipboard
mapbox
Semantic segmentation on aerial and satellite imagery. Extracts features such as: buildings, parking lots, roads, water, clouds
We have two use-cases for handlers: - `rs extract` where handlers have to walk over OpenStreetMap gathering polygons - `rs features` where handlers have to do post-processing on segmentation masks...
When generating lists of tile ids covering geometries we are seeing a difference between the [tile-cover](https://github.com/mapbox/tile-cover) and the `rs cover` generated tile ids. For the same geometries: wc -l /tmp/tile-cover.tiles...
At the moment we _almost_ have a clean split in place: we have command line utilities in `robosat.tools` and everything else split off of it. What we should do is...
For features like buildings we want to sample OpenStreetMap when extracting geometries in `rs extract`. The osmium handlers in `robosat.osm` should take a sampler and then for every OpenStreetMap entity...
Python3's `pathlib` abstracts path handling and provides functionality which is otherwise not present or scattered across several modules. In addition it overloads operators for easier path joining. ```python from pathlib...
We still have a lot of code in the top level module from a time before we had sub-modules: https://github.com/mapbox/robosat/tree/52299b855b77225b795b015944e31cbddb9ce44b/robosat We should refactor the code here, e.g. putting the modelling...
I am aware that this repo is no longer maintained but I recently had to blow the dust off of it to replicate some stuff I did a few years...
Hello @daniel-j-h. Thank you for the amazing repository. However, I have some questions to use this repo for my project. I have an unlabeled dataset of UAV imagery with coordinates...
