UPDATE: look like MODIS will be supporting OSGeo4w as a primary source of gdal. You can continue to use FWTools, if you like, but OSGeo4w is going to have the latest versions of Gdal for windows and that is what the MODIS package wants to use. You can continue with the tutorial on FWTools if you like to see how a GDAL command works, or you can just go install gdal using OSGeo4w in the next step.
Go get FWTools. The windows Binaries are here. I just download to my desktop and then install. The install happens in the Program Files (x86) directory. You should also read this. When you finish the install you will have a couple of desktop icons. One for FWTools Shell and the other for OpenEnv. Click on FWTools Shell.
(VLIV is also fast but doesn't allow you to zoom in/out nor make anything with the image.I contacted it's programmer and he told me that we need first to transfor the image to pyramidal format, but free windows tools don't make it well and are really slow.)
I began to use fwtools by viewing the MrSid-big mistake!. It begins by decompressing MrSid which takes forever on my machine. Looks like it will work ok, maybe even great with more study of the reader files. I think I need to be able to take SWAG at a crop size(without viewing first) to get a file that I can manage well with my regular tools. I will keep working on it.
I am able to run the batch file and convert successfully in FWTools shell, but windows cmd.exe tells me that 'ogr2ogr' is not recognised as a command. Is there any way I can set it up so that cmd.exe recognises it automatically and just runs the .bat file every time?
FWTools at least for windows, has the ESRI Geodatabase driver (referred to as PGeo for Personal Geodatabase) baked into the binary. This makes it relatively simple to export data out of the Personal Geodatabaseformat into other formats such as PostgreSQL or ESRI Shape
760c119bf3