Revisiting my inquiry into historical course of the Rio Grande border with an alternative approach: this time by importing GeoTIFF + .shp files into #Blender3D and keyframe camera movement
bsky.app/profile/jack...
Revisiting my inquiry into historical course of the Rio Grande border with an alternative approach: this time by importing GeoTIFF + .shp files into #Blender3D and keyframe camera movement
bsky.app/profile/jack...
but we never asked ourselves if we SHOULD
but we never asked ourselves if we SHOULD
I’ve been working with a 46GB GeoTIFF for my Mars mapping project. Fun!
I’ve been working with a 46GB GeoTIFF for my Mars mapping project. Fun!
cogeo.org
#gsijicatraining #COG #GeoTIFF #FuruhashiLab
cogeo.org
#gsijicatraining #COG #GeoTIFF #FuruhashiLab
www.loc.gov/item/2012593...
www.loc.gov/item/2012593...
Green square: approximately (134, 112, 115)
My assessment is we are looking at Soil, Confidence 60%
I will get the raw GeoTIFF from AirBus in a few, It should be in the lib soon if Google tasked this.
Green square: approximately (134, 112, 115)
My assessment is we are looking at Soil, Confidence 60%
I will get the raw GeoTIFF from AirBus in a few, It should be in the lib soon if Google tasked this.
Turns out the trick with PACE data in SEADAS is to just ignore all the scripts & tutorials & what not & just go to geometric tools and reproject/export as a geotiff vs just export as geotiff (even though it is geocoded)!
Oh GIS, always takes hours to figure out a single click!
Turns out the trick with PACE data in SEADAS is to just ignore all the scripts & tutorials & what not & just go to geometric tools and reproject/export as a geotiff vs just export as geotiff (even though it is geocoded)!
Oh GIS, always takes hours to figure out a single click!
Origin | Interest | Match