-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial progress on README.md #2
base: master
Are you sure you want to change the base?
Conversation
|
||
- [rio-tiler](https://github.com/cogeotiff/rio-tiler): Core module to read data from a COG | ||
- [rio-cogeo](https://github.com/cogeotiff/rio-cogeo): CLI + python module to easily create COG | ||
- [rio-tiler-mosaic](https://github.com/cogeotiff/rio-tiler-mosaic): rio-tiler plugin to handler multiple overlapping dataset (was made as a separate module to keep rio-tiler simple) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can remove this one
- [rio-viz](https://github.com/developmentseed/rio-viz) devseed visualize COG in browser | ||
- [cogeo-watchbot](https://github.com/developmentseed/cogeo-watchbot) devseed AWS stack - Create COG + MosaicJSON at scale | ||
- [cogeo-watchbot-light](https://github.com/developmentseed/cogeo-watchbot-light) devseed AWS stack - Create COG at scale | ||
- [cogeo-watchbot-fargate](https://github.com/developmentseed/cogeo-watchbot-fargate) devseed AWS stack - Create COG at scale using ECS fargate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove -light
and -fargate
, I'll add a mention in cogeo_watchbot
|
||
### CBERS | ||
|
||
- `rio-tiler-pds` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big fan of Sensor sections. IMO we should do like in https://github.com/mapbox/awesome-vector-tiles
e.g
- Reader/Writer (GDAL, Rasterio, Geotifjs ....
- Client (rio-tiler, aiocogeo ...)
- Application (rio-viz)
- Server (titiler ...)
- Articles (blog posts)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
We should also be sure to keep the tools list on the website up to date. Don't need any fancy automated thing, we should just periodically remember to check both website and here to make sure they have the same. Could also evolve to the website just listing 'key tools' and have a higher bar, and then link to this list, so that the website isn't.a super long list.
Also should add Google Earth Engine, it's been on my list to add to the website and do a little blog post on it. But they've had the ability to read cogs for a month or so now.
Open question of how to lay out the sections of the README