14
NDVI is defined for any two bands with near-infrared and infrared data (it is an empirical remote sensing index). As such, you can calculate it straight from the DNs. This is mostly OK if you are only classifying or analyzing vegetation on a single image without significant atmospheric effects (cirrus clouds...)
However, if you are performing change ...
11
How about firing up an EC2 or rackspace instance and installing the EarthExplorer bulk download application:
http://earthexplorer.usgs.gov/bulk/
You could hit the EarthExplorer service with a POST request to submit jobs programmatically:
http://earthexplorer.usgs.gov/subscription/submit/
You would need to provide standingRequestName, frequency, ...
11
I saw a blog post from developmentseed for their command line utility landsat-util.
Power tools for Satellite Imagery
The landsat-util can be forked from github and compiled from source unless your OS offers it in a binary ready to go.
The blog describes it simply as:
a command line utility that makes it easy to search, download, and
process Landsat ...
10
Fundamentally the question here is "what does 'scientifically valid' mean". If you are looking to do spectral modelling on the data, then the answer is possibly different than if you are looking at doing classification / image segmentation. Pansharpening (depending on the method) is simply going to change the range of the values a fairly small amount and ...
8
I just thought I'd add that there are some 'pure' Python solutions for several nodes in this workflow, also.
Some file reading and basic processing:
Spectral Python: http://spectralpython.sourceforge.net/
More classification than you'll find in pure remote sensing and GIS packages:
http://scikit-learn.org/stable/
More links I can't share:
6S Python ...
8
The USGS provides a tool for bulk downloading of Landsat Metadata:
Landsat Bulk Metadata Service
The MTL files will allways be distributed with the data if you download the scenes through USGS EarthExplorer.
If you don't want to download the bands again and just the MTL text files for each scene you can take a look at Amazons Landsat Mirror. Each scene is ...
8
gnutls.h which is required is missing from the filesystem even if you install libcurl4-gnutls-dev which supposedly has the headers files for curl.
to correct for that error run:
# apt-get install libgnutls28-dev
to add the missing header and pip finally to install pycurl and landsat-util
8
Please, read the related answer.
Use the right parameters and always check metadata
You're trying to filter with BQA band and in SR product, there is no BQA band, there is pixel_qa band instead. Also, bits used are different (3 and 5). Finally, if you are trying to create a cloud-free composite, first sort by cloud cover.
var point = /* color: #98ff00 */...
8
Aldo's answer is the correct one, no doubt, but if you want to make the code shorter and you don't mind loosing the 'core' of cloud masking, you can use a module:
var point = /* color: #98ff00 */ee.Geometry.Point([35.83946228027344, -3.5380934964711126]);
//load images for composite
var sr14= ee.ImageCollection('LANDSAT/LC08/C01/T1_SR')
.filterBounds(point)...
7
If you really want to use python, and you need functionality similar to GRASS, perhaps the easiest solution would be to use GRASS via Python.
That isn't specific to Landsat8, but I don't think a processing solution should be tied that closely to a specific satellite. You could implement some simple wrappers / higher level functions if you're consistently ...
7
Take a look at i.landsat.rgb - Performs auto-balancing of colors for LANDSAT images, probably before running the pansharpening. You may also consider to convert the digital numbers of the individual channels to top-of-atmosphere radiance or reflectance with i.landsat.toar. See also http://grasswiki.osgeo.org/wiki/LANDSAT
BTW: having a range of 0-65535 for ...
7
Forgive me if this is too basic an answer: panchromatic and infrared are mutually exclusive.
Panchromatic means all visible light, which is generally considered to range 0.4μm to 0.7μm in wavelength.
Near (or reflected) infrared energy is generally considered to range 0.7μm to 0.9μm in wavelength, just beyond visible.
See Infrared vs. Panchromatic - Mt. ...
7
One flaw in your approach. You don't need to go through DN to radiance.
You can go straight to the DN to reflectance.
Just stick to ((B1*0.00002)-0.1)/0.74457226676389733207607359928648.
7
It's going to be something like this:
var landsat8= ee.ImageCollection('LANDSAT/LC8_L1T_TOA').filterBounds(geometry)
var waterThreshold = 0;
// water function:
var waterfunction = function(image){
//add the NDWI band to the image
var ndwi = image.normalizedDifference(['B3', 'B6']).rename('NDWI');
//get pixels above the threshold
var water01 = ndwi....
7
If you have a look at Sentinel 2 bands you'll find that all bands are type unsigned int 16 except for QA20 that is unsigned int 32, that band is causing the issue.
You can solve it in different ways, but I post here what I think is what you need:
var image = ee.ImageCollection('COPERNICUS/S2')
.filterBounds(PuntoQuellaveco1)
....
6
Right now I have checked into SVN a set of updates for i.landsat.toar into SVN for Landsat8, provided by the author E. Jorge Tizado. They hopefully solve your problem (NASA changed the metadata format).
You can download the updated winGRASS binary by tomorrow morning either through the OSGeo4W installer ("advanced") or as standalone daily snapshot version ...
6
The reason why it looks pixelated at 1:2500 (and probably at 1:10K or 1:20K) is that you are looking at a single resolution cell (30 metres on the ground, as pointed out by Mapperz) across multiple pixels on the screen.
Lets assume that you're looking at a 30m cell at 1:1000 (in true scale, ignore that your monitor probably doesn't really do that) - that ...
6
Satellite zenith angle
Images from Landsat 1 - 7 are always nadir.
In other words, their satellite zenith angle is close to 0°.
Likewise, the _MTL.txt you posted corresponds to a Landsat 5 image, and so is a nadir image.
Off-Nadir imagery has been introduced with Landsat 8.
Landsat 8 images have a field NADIR_OFFNADIR in their _MTL.txt metadata. The ...
6
You are right: the range of the NDVI is limited to values between -1 and 1 due to its' normalization properties.
The negative limit of -1 will be reached if you encounter maximal reflectance (1) in the red wavelength region and zero reflectance in the NIR. The positive limit will be reached by maximal reflectance in the NIR region and zero reflectance in the ...
6
You have downloaded the data and you can find it if you unpack the .tar.gz file using 7zip or similar software for unpacking files. The .tar.gz file is the fourth file from the top that can be seen in your first screenshot.
Do note that you have to unpack the .tar.gz twice in order to get to the data. You will easily recognize it as you will see the ...
6
I am not 100% familiar with the NDBI Index, but found an article here: https://www.researchgate.net/publication/273886729_Built-up_area_extraction_using_Landsat_8_OLI_imagery
Specifically on Page 14 that describes the NDBI as:
NDBI = (Band 5 - Band 4) / (Band 5 + Band 4)
Which is the original equation.
In order to get the NDBI for the Landsat 8 the ...
5
ROIs in ENVI are stored in pixel-based co-ordinates, with no geographic information at all. The size of the image used to create the ROI is stored in the ROI file, and when you open the ROI list for an image it only displays the currently loaded ROIs that match the image dimensions.
Although your images are all of the same location, in the same projection ...
5
Usually you start with cloud (and cloud shadow) removal then you run the classification. One of the best papers I know about cloud detection on Landsat is Zhu and Woodcock (2012)
5
Step 1: Convert from digital numbers (DN) to radiance
This is done by applying the multiplier and addition numbers as found in the metadata (.MTL) file. For the thermal bands (B10 and B11), the values are usually, but you should check the file:
Add: 0.1
Multiply by: 0.0003342 (3.3420E-04)
In ENVI you can apply this correction using 'band math':
float(b10)*...
5
Your clipping fails because the raster has the odd nodata value of -3.4E+38. Unfortunately, you can not enter that value in the input form.
So I suggest to use gdalwarp to change the nodata value and clip as well, but to the extent of the polygon layer:
gdalwarp -overwrite -s_srs EPSG:32634 -dstnodata -10 -q -cutline forest_2013_extent.shp -...
5
The Landsat 8 Surface Reflectance products are not sunglint corrected , so if your application is going to be adversely impacted by the presence of sunglints, then you should implement a suitable deglinting method.
For more detail on the exact processing algorithms used for the Surface Reflectance Product, see https://landsat.usgs.gov/landsat-surface-...
5
Yes, it affects the values of NDVI, and it may not give the desired results sometimes. Information from Wikipedia: Normalized Difference Vegetation Index provides some details about the effects of cloud and snow as follows:
clouds and snow tend to be rather bright in the red (as well as other
visible wavelengths) and quite dark in the near-infrared
...
5
Bare soil and urban areas are notoriously hard to segregate. Even with a perfect atmospheric correction, there will be relatively high confusion between the two, particularly when limited to multispectral datasets.
The atmospheric correction technique you are doing is a simple dark object subtraction, wherein the darkest objects in the landscape should have ...
5
You can perform a land cover classification on a single Landsat scene without performing spectral and radiometric corrections. You will only need to do those corrections if you're trying to apply reference spectra to your classification, performing a classification that covers multiple scenes or performing a classification over a time series of the same ...
5
You will want to use the *_sr_band1 to band7 data for your analyses as these are atmospherically corrected surface reflectance products (Figure 1). Only the Surface Reflectance data products and quality assessment bands are included in the deliverables (Figure 2). The ancillary bands (e.g. *_sensor_azimuth_band4) are used in the process of atmospheric ...
Only top voted, non community-wiki answers of a minimum length are eligible
