[COG] Welcome!

[Kurt Schwehr]

My intro:

I'm a software engineer at Google on Earth Engine, I'm on the Project
Steering Committee for GDAL (and soon for PROJ), and I'm a
geologist/geophysicst by degrees.  Most of my field experience is with Mars
rovers and on ships doing geophysics, so my orbital remote sensing
experience is best classified as "noob".  I once (back in 2011) tried to
teach a research tools class for new graduate students doing ocean
mapping.  That and my (painful) experience as a graduate student trying to
use data drives a lot of what I do now.

I'm generally looking for ways on how to help the entire community get more
out of data.  I demoed handling ship tracking data in the cloud back in
2013 that was the start of Global Fishing Watch.  I see things like that as
trying to do far more with less budget for infrastructure enabling really
awesome research projects by small teams or single researchers.

I am looking forward to seeing the data and data processing ecosystem
continue to grow and get easier to use.

So far with COG, I've worked through Even's validate script e.g. c5ea8e4f
<https://github.com/OSGeo/gdal/commit/c5ea8e4f9e7fdf65174e75e4961ae6965c0cb92f#diff-87c09734d0c3a27bbda28cdb588ae6a7>
and
written validate_cloud_optimized_geotiff_test.py
<https://github.com/schwehr/gdal-autotest2/blob/master/python/apps/validate_cloud_optimized_geotiff_test.py>
.

-kurt

On Mon, Jun 4, 2018 at 4:09 PM, Chris Holmes <cholmes at radiant.earth> wrote:

> Hi everyone! Thanks for joining this list to discuss cloud
> optimized geotiffs (COGs). We've already got 68 people on the list. I don't
> anticipate it will be a super active list, but I believe there's a few
> things to discuss to evolve COGs a bit.
>
> I think I know a number of people on the list, but it'd be great if people
> could introduce themselves and share their interest in COG.
>
> * I'm Chris (aka 'cholmes'), and I work 3 days a week at Planet, plus one
> day at Radiant.Earth, and both give me time to help advance COG. At Planet
> all our data is COG, and so we're interested in more tools that can consume
> it, and hopefully save everyone money by using COG to stream our data and
> not having to copy and store so much. Radiant has been supporting the COG
> standard, building tools like cog-map <http://www.cogeo.org/map/> and
> tiles.rdnt.io. Radiant is building a platform for NGO's / developing
> world, and sees it resting on an infrastructure of COG's
>
> *Using the list*
>
> Feel free to post any questions, issues in working with COG's, best
> practices in working with the spec, or ideas of how to make COG's more
> useful. From the BoF at foss4g-na
> <https://medium.com/radiant-earth-insights/cloud-optimized-geotiff-birds-of-a-feather-at-foss4g-na-def26572ae1b>
>  there's a few topics to continue discussion on - feel free to kick those
> off in their own thread, or I'll frame them in a bit.
>
> *Next Steps*
>
> I believe the next step is to create an area in github for us to work. I
> believe a github 'organization
> <https://blog.github.com/2010-06-29-introducing-organizations/>' will
> serve us best, to be able to group a few different projects. We'll port the
> spec on gdal's <https://trac.osgeo.org/gdal/wiki/CloudOptimizedGeoTIFF>
> wiki to its own repo (cog-spec?), and then I'll move the website repo
> <https://github.com/cholmes/www.cogeo.org>, and I think it would make
> sense to move the validator <https://github.com/rouault/cog_validator> in
> to, as it's where the spec gets real. And perhaps do a repo on performance
> testing, with tools and results. And perhaps we can welcome other related
> tooling.
>
> Does anyone have any great ideas for the organization name? cog and cogeo
> are taken. The ideas I had were:
>
> * cogeotiff
> * co-geotiff
> * cog-repo
>
> Let me know if there are more ideas, and I'll send out a poll soon to
> decide. And also ping me if you're up to help create + organize the repos.
>
> best regards,
>
> Chris
>
>
>
>
> _______________________________________________
> COG mailing list
> COG at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/cog
>
>


-- 
--
http://schwehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/cog/attachments/20180605/07258ab8/attachment-0001.html>