Help! About MAPGEN make.mapdef and overlay file

This message is being re-posted to the grass list for Peter.
I recieved a mail error when posting with his email address.

   ----- Transcript of session follows -----
421 Host bingsuns.cc.binghamton.edu not found for mailer tcp.
550 br00369@bingsuns.cc.binghamton.edu... Host unknown

----- Begin Included Message -----

From jschuler Mon Jan 22 09:58 MST 1996
Return-Path: <jschuler@ftc.nrcs.usda.gov>
Date: Mon, 22 Jan 1996 09:58:40 +0700
From: jschuler (jill schuler)
Sender: grass-lists-owner@moon.cecer.army.mil.
Reply-To: grassu-list@moon.cecer.army.mil.
Precedence: Bulk
To: br00369@bingsuns.cc.binghamton.edu
Subject: Re: Help! About MAPGEN make.mapdef and overlay file
Cc: jschuler
X-Sun-Charset: US-ASCII
Content-Type: text
X-Lines: 175
Status: O
Content-Length: 6059
Lines: 182

Hi Peter,

First Problem:
_______________
Instead of using your own map definition file name, I strongly urge you to
use the default names until you are more familiar with mapgen.

Use the map definition name map.def . All interface command will ask for
this name. You can enter this by accepting the default with a return.

The show.sh command requires an optional flag if the default name is not used.
show.sh -m try.def ovm/*

Second Problem:
________________
It looks like your proj command does not recognize the ellipsoid "clark66".
Because of this, the map definition file try.def never was generated correctly.
Ever additional command in mapgen is dependent on the map definition file--
so no overlays were generated.

Use the command proj -le . This will list out the recognized ellipsoid
abbreviations. You probably only have clrk66.

Try running the make.mapdef command again and enter the ellipsoid name
clrk66 . This should eliminate the errors associated with the map definition
file.

Previous ERRORS:
<proj>:
no clark66 elliptical const. found
<proj>:
projection initialization failure
program abnormally terminated
<mapdef>: invalid header
mapdef abnormally terminated
cat: try.def: No such file or directary
grep: try.def: nO such file or directary
cat: try.def: No such file or directary

If the map definition command make.mapdef ran sucessfully now do a redo to
remake your line, misc, and label overlays.

Hopefully, when you do a show.sh you will see your map.

To correct the ellipsoid problem you will need to recompile the program proj.
The file under src called pj_ellps.c should be edited to include the ellipsoid
names that GRASS uses. Add clark66, clark80, grs80 for starters.

Third Problem:
________________
The geographic area that you have defined probably will not fit on E size
paper at your selected scale. Use the command verbose to determine your
map's paper size. If the plot size is bigger than 106.8 cm in the x and 82.0 c
m
in the y axis only part of your map will plot.

#pico try.def.par
78W 74W 39N 43N
+proj=eqc +ellps=clark66 +lat_0=41n +lon_0=76w
48000

2 2
2.54 20.32

***********************************************
Map Making with Mapgen:

1. Your very first step in making a map should be to define the mapping view.
You do this by displaying a grass vector file that represents the extent of
the data area to map (i.e., d.vect try.vect). Window in around the data extent
to map using the d.zoom command. Then redisplay new window with the d.vect
command. Note: the mapgen grid command will work best when you have your
GRASS window set as close to the data area as possible.

Now you are ready to run the make.mapdef command.

2. Run the make.neatline command to define your plot window.

3. Run the make.neatline command to define your data window.

4. Run the make.line command with a very simple vector file that displays
the extent of the area to be mapped. Note: It is not necessary to run
the dig.to.geo command, the make.line command will run this command for you.
Remember that the dig.to.geo command uses the PROJ_INFO file to georeference
your data to L/L. If the PROJ_INFO file does not correspond to the WIND file
then your georeferenced data will not display in your mapgen window.

Check your map size using the verbose command. Determine if the current
layout will meet your needs. If not, edit the map.def.par file (try.def.par)
and change the scale or map margin values. Run a redo all. Run verbose to
verify the changes meet your needs.

Display your map overlays using the show.sh, d.ovm or xzoom commands.

5. Run the make.text command to build the map's support information: title,
source note, legend title, etc.

6. Run the make.barscale, make.arrow, make.grid command to add esential
map elements.

7. Once the map layout is established begin to build the other map data
elements using the make.line, make.label, make.symbol and make.fill commands.

8. Run the make.legend command to add the legend boxes and symbols.

9. Plot out your overlays using the plot.sh or mapgen plotter command. If
you use the plot.sh command you should verify the the software file
$GISBASE/mapgen/etc/PLOTTER correctly identifies the hardwired plotter with
the print spooler name and tty port.

If you do not have a plotter hardwired to your cpu, you must use the mapgen
plotter command and output the plot instructions to a file:

plotter -d driver_paper [options] ovm/* -o output_filename

where:

driver_paper is one of the recognized mapgen plotter driver names with
output paper size appended. For example:

hpgl[a,b,c,d,e] -- hpgla
cps[a,b,c,d,e] -- cpsa Note: your version of software may not support
                          paper sizes bigger than b for this driver.
ps -- Note: your version probably only supports "a" paper.

Other plotter driver names:
calhpgl -- hpgl driver with 255 pens
hp650 -- hpgl2 driver with 255 pens for hp650 plotter
gerber -- is the gerber driver that supports 20 pens

options are the following:

-r will rotate the x to the y axis
-s value will scale the current map by the scale value (i.e., -s 0.48)

output_filename is the file name for the plotter instructions
hpcps -- postscript driver for hp650 plotter

Please email me your complete street address and I will try to send you a
manual.

Regards,

Jill
      __________________________________________
      ____ __ ________ ________ ________
        //^ // // // // // // //
       // ^ // // // // //
      // ^ // //____// // //____///
     // ^// // // // //
  _// ^/__// //_//_____////_____ //
_________________________________________

Jill R. Schuler
USDA
Natural Resource Conservation Service
2625 Redwing, Suite 110, Ft. Collins, Co 80526

e-mail: jschuler@ftc.nrcs.usda.gov Phone: (970) 282-2418

         /\ \ / /\
        //\\ .. //\\
        //\(( ))/\\
        / < `' > \

----- End Included Message -----