No subject

" Looking closer at the program and at the USGS DEM standard I found that
 large parts of the header are actually supposed to be FORTRAN double
 precision values.  I'm surprised that r.in.dem works for anyone."

GDAL supports:
http://www.remotesensing.org/gdal/frmt_various.html#SDTS
 
> > ./src/raster/r.in.ll/
> This looks like it is very specific to a certain type of data import.
> Almost seems to do the same thing as r.proj but I don't really understand
> the man page.

Maybe also left to r.in.gdal?
 
> > ./src/sites/s.datum.shift/
> Isn't needed now s.proj can do datum shifts

ok
 
> > ./src.contrib/NPS/r.in.utm/
> Sounds like another specialised import/re-projection utility that isn't
> needed now.

ok
 
> > ./src.contrib/SCS/display/d.fix.ortho/
> Description:
>  Shifts raster map to position specified by mouse
> Is this useful? Might be and only uses coorcnv for reporting co-ordinates
> in lat/long to user so would be easy to fix.

It's more dangerous than useful as it modifies the cell_header of a
raster file. With that module you can move raster images by mouse click.
But in a GIS that issue is probably better left to i.rectify and related
modules.

> > ./src.contrib/SCS/vector/v.mkquads.scs/
> Maybe just an older version of v.mkquads?

... or a "private" SCS version?
 
> > ./src.contrib/SDTS/mapdev/v.out.sdts/

no idea

> > ./src.garden/grass.hdf/hdf5/r.in.hdf/

r.in.gdal supports HDF much better, so r.in.hdf is not needed.

> > ./src.garden/grass.tig.rim/v.in.tig.rim/
> More specialised import/export utilities probably; are any of them really
> needed or have they been replaced by something better.

RIM doesn't exist in GRASS any more.

Markus