Skip to main content

Spatial datasets operations: From MODIS to model ready binary workflow


I have written a couple of articles regarding the potential issues during raster operations. Here I have put down some typical workflow for these operations.
For study area smaller than one MODIS granule, following these steps:

The common method that will work for you:
  1. Convert one HDF file to GeoTIFF using ArcMap, save this file as A.tif.
  2. Convert all HDF files to GeoTIFF using IDL and A.tif, call routine "hdf2tiff". In this step, you should set all unwanted pixel to missing value, such as -9999.
  3. Project one GeoTIFF A.tif to B.dat using ArcMap;
  4. Project all GeoTIFF to ENVI files using B.dat, call routine "project48";
  5. Define the missing value for all the ENVI files from step 4, call routine "define_envi_missing_value";
  6. Prepare the shapefile mask for the study area, C.shp using Arcmap, C should has the same projection as the target projection;
  7. Extract all ENVI files using the C.shp shapefile , call routine "extract50".
(Updated January 15 2017). 
Since in some cases it is impossible to re-project a raster from one projection to another using common projection method, which mean the above step 4 is going to fail unless you use rigorous projection method. At the same time, rigorous method takes a long time to run. Therefore, we recommend an extraction before projection (more details). And the new steps are:
  1. Convert one HDF file to GeoTIFF using ArcMap, save this file as A.tif.
  2. Convert all HDF files to GeoTIFF using IDL and A.tif, call routine "hdf2tiff". In this step, you should set all unwanted pixel to missing value, such as -9999.
  3. Prepare a rectangle shapefile B.shp which covers your study domain using ArcMap. B.shp has the same spatial reference with A.tif;
  4. Extract all the GeoTIFF files using the rectangle shapefile B.shp.
  5. Define the missing value for all the ENVI files from step 4;
  6. Extract the A.tif using B.shp and save it as C.dat;
  7. Project C.dat to D.dat with the target spatial reference using ArcMap;
  8. Project all ENVI files from step 4 using D.dat, call routine "project48";
  9. Prepare the shapefile mask for the study area, E.shp, E should has the same projection as the target projection;
  10. Extract all ENVI files from step 8 using the E.shp shapefile.
Good luck.

Comments

Popular posts from this blog

Spatial datasets operations: mask raster using region of interest

Climate change related studies usually involve spatial datasets extraction from a larger domain.
In this article, I will briefly discuss some potential issues and solutions.

In the most common scenario, we need to extract a raster file using a polygon based shapefile. And I will focus as an example.

In a typical desktop application such as ArcMap or ENVI, this is usually done with a tool called clip or extract using mask or ROI.

Before any analysis can be done, it is the best practice to project all datasets into the same projection.

If you are lucky enough, you may find that the polygon you will use actually matches up with the raster grid perfectly. But it rarely happens unless you created the shapefile using "fishnet" or other approaches.

What if luck is not with you? The algorithm within these tool usually will make the best estimate of the value based on the location. The nearest re-sample, but not limited to, will be used to calculate the value. But what about the outp…

Numerical simulation: ode/pde solver and spin-up

For Earth Science model development, I inevitably have to deal with ODE and PDE equations. I also have come across some discussion related to this topic, i.e.,

https://www.researchgate.net/post/What_does_one_mean_by_Model_Spin_Up_Time

In an attempt to answer this question, as well as redefine the problem I am dealing with, I decided to organize some materials to illustrate our current state on this topic.

Models are essentially equations. In Earth Science, these equations are usually ODE or PDE. So I want to discuss this from a mathematical perspective.

Ideally, we want to solve these ODE/PDE with initial condition (IC) and boundary condition (BC) using various numerical methods.
https://en.wikipedia.org/wiki/Initial_value_problem
https://en.wikipedia.org/wiki/Boundary_value_problem

Because of the nature of geology, everything is similar to its neighbors. So we can construct a system of equations which may have multiple equation for each single grid cell. Now we have an array of equation…

Lessons I have learnt during E3SM development

I have been involved with the E3SM development since I joined PNNL as a postdoc. Over the course of time, I have learnt a lot from the E3SM model. I also found many issues within the model, which reflects lots of similar struggles in the lifespan of software engineering.

Here I list a few major ones that we all dislike but they are around in almost every project we have worked on.

Excessive usage of existing framework even it is not meant to Working in a large project means that you should NOT re-invent the wheels if they are already there. But more often, developers tend to use existing data types and functions even when they were not designed to do so. The reason is simple: it is easier to use existing ones than to create new ones. For example, in E3SM, there was not a data type to transfer data between river and land. Instead, developers use the data type designed for atmosphere and land to do the job. While it is ok to do so, it added unnecessary confusion for future development a…