You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagery is collected in the Military Grid Reference System. Here's a KML you can use to find imagery intersections with the trail.
The Sentinel AWS Readme lists how the file structure is set up. So for example, the UTM grid square that intersects Glacier Peak in WA, on July 22, 2019 is here:
> aws s3 ls s3://sentinel-s2-l2a/tiles/10/U/FU/2019/7/22/0/ --request-payer
PRE R10m/
PRE R20m/
PRE R60m/
PRE auxiliary/
PRE qi/
2019-07-22 21:15:40 553239 metadata.xml
2019-07-22 21:15:49 1035 productInfo.json
2019-07-22 21:15:40 1491 tileInfo.json
The tileInfo.json has helpful information, including a GeoJSON representation of the geometry of the square, (not in WGS84), cloudyPixelPercentage(!!), and the path to the image.
Each of the B*.jp2 files are a different band. Wikipedia explains which band is which. However, easiest for my purposes is TCI.jp2, which stands for True Color Image I think. For the 10m resolution, each file is around 129MB.
If you download a few images and run gdal2tiles.py --srcnodata="0,0,0" *.jp2 tiles, you can get an image like this:
--srcnodata="0,0,0" means that all fully black areas will become transparent, as seen above. The path of the satellites means that it won't always be simple to find continuous bands to display.
Note that when you're creating the tiles, you should try to use -addalpha instead of applying -srcnodata on the black portions. This doesn't work for fstopo because it has a color table and not rgb bands, but I'm pretty sure Sentinel has rgb bands.
Imagery is collected in the Military Grid Reference System. Here's a KML you can use to find imagery intersections with the trail.
The Sentinel AWS Readme lists how the file structure is set up. So for example, the UTM grid square that intersects Glacier Peak in WA, on July 22, 2019 is here:
The
tileInfo.json
has helpful information, including a GeoJSON representation of the geometry of the square, (not in WGS84),cloudyPixelPercentage
(!!), and the path to the image.If you look into a given folder for (utm square / year / month / day / snapshot number / resolution), you'll see this:
Each of the B*.jp2 files are a different band. Wikipedia explains which band is which. However, easiest for my purposes is
TCI.jp2
, which stands for True Color Image I think. For the 10m resolution, each file is around 129MB.If you download a few images and run
gdal2tiles.py --srcnodata="0,0,0" *.jp2 tiles
, you can get an image like this:--srcnodata="0,0,0"
means that all fully black areas will become transparent, as seen above. The path of the satellites means that it won't always be simple to find continuous bands to display.Note that Lambda isn't really a great place for this processing, since it has a scratch disk space limit of 500MB.
Note that while signed in to the aws cli, you need to add
--request-payer
to do anything with a requester pays bucket. I.e.The text was updated successfully, but these errors were encountered: