@kylebarron2@petegadomski I've not used fetch() specifically but the general story with Emscripten seems to be that it's easier to do synchronous stuff from within a Web Worker. The fact that they've got a `--proxy-to-worker` build mode makes me think that'll be the case here too.
@tmcw@STACspec@placemarkio Handling raw data from STAC catalogs client-side is not out of the question for GDAL-supported formats by using something like Loam; that would allow handling the multispectral case as well. https://t.co/Ngov5E7Rc9 (disclosure: primary Loam author)
Great talk by @dpdohler at @foss4g comparing server-side and client-side processing of GeoTIFFs. Really appreciate his thoughtful answers. And he introduced https://t.co/zumspS8Gpf !
@aldenks@azavea Not yet, but /vsi support is a really high priority! I think the best approach here is to alter GDAL to use Emscripten's fetch API (https://t.co/jn4vU4GgHa) instead of libcurl when compiling to wasm. If you've got expertise that could help speed that along, please get in touch!
Today, we are excited to announce Loam: an #OpenSource library that makes #GDAL available client-side. For examples of what you can do with Loam and a brief look at the technical architecture behind it, read the full blog: https://t.co/Z8mNoTvdy4
@mcmansionhell Do you know of any online source for the blueprints and materials sheets that are always available for mail-order in vintage plan books? I have a crazy idea about building one of these houses someday.
@howardbutler @EvenRouault At @azavea we've been experimenting with compiling GDAL (along with PROJ) into WASM and have had pretty good results. I've been able to utilize GDAL's built-in SRS definitions to warp coordinate lists, e.g. https://t.co/fB1FemJGJP h/t @lossyrob