| Size: 259 Comment:  | Size: 2725 Comment:  | 
| Deletions are marked like this. | Additions are marked like this. | 
| Line 1: | Line 1: | 
| Line 3: | Line 4: | 
| === Input === * stdin * example: ZN1100.IN | This generates a bigmap from a set of maplets.  This can be used to generate shape models or images. === Requires (created) === * LMKFILES/ * LMRKLIST/ * [[LMRKLIST.TXT]] - Required. List of landmarks * MAPFILES/ * SHAPEFILES/ * [[BIGFILES]]/ - directory of LMK for each of the required bigmaps - directory must be created, but changes are made within. * [[SUMFILES]] / - info about the maplets === Requires (created & unique) === * [[BIGLIST.TXT]] - list of needed mapfiles (bigmaps) used to construct the working bigmap * [[INSIDE.TXT]] - (Created) The maplets that fall completely within the planned bigmap. Possibility created by bigmap.e * [[USED_MAPS]] - (Crated) All the maps used to create the bigmap. * Many files must be unique. All directories can be linked to a master. === Optional === * [[BIGMAP.IN]] - a list of landmarks that you want to use for bigmap. It allows you to reduce the number of files and avoid low resolution images. * [[LMRKLIST.TXT]] - Same as above, but only used if [[BIGMAP.IN]] is missing (used for historical purposes) * If there are neither of these files, then it will build the list of files that are included in the coverage === Input stdin === * A long set of commands are sent into this program that are usually contained within a file /!\ Longitude is in west longitude (meaning that you need a negative to match what is used in [[spheremapB.e]] * example: {{{ ~/bin/bigmap.e < ZN0208.IN }}} === Input file === The format is normally something like this. {{{ l (select location, 1 is lat/lon) 20 -40 (latitude, west longitude) 0.06250 500 1.23400 (scale, qsz (number of pixels), seed) ZN0208 (filename) 1 (end or integrate, 1 is integrate) .005 (input fraction) .025 (input weight) 1 (end, continue, change weight, smooth, 1 is continue integrating) 1 (end, continue, change weight, smooth, 1 is continue integrating) 1 (end, continue, change weight, smooth, 1 is continue integrating) 0 (end, continue, change weight, smooth, 0 is end iteration) 0 (no, square or round template, 0 is No Template) }}} === Output === * bigmap with the name based on the input (e.g. ZN0208.IN). * slopeb.pgm image, that shows the slope in both in horizontal and vertical. * SIGMAS.TXT - Each time BIGMAP is run, it will add a line to this file showing the current sigma values * SIGMAS.pgm - {{attachment:sig2.jpg}} - It graphically shows the highest level of error (sigma) is for maplets. | 
| Line 9: | Line 63: | 
| " l 0 0 0.06250 500 1.23400 ZN0000 1 .005 .025 1 1 1 1 1 1 1 0 0 " === Output === Generates a bigmap with the name based on the input (e.g. ZN0000) | CategoryPrograms CategoryPrograms | 
bigmap
This generates a bigmap from a set of maplets. This can be used to generate shape models or images.
Requires (created)
- LMKFILES/
- LMRKLIST/
- LMRKLIST.TXT - Required. List of landmarks 
- MAPFILES/
- SHAPEFILES/
- BIGFILES/ - directory of LMK for each of the required bigmaps - directory must be created, but changes are made within. 
- SUMFILES / - info about the maplets 
Requires (created & unique)
- BIGLIST.TXT - list of needed mapfiles (bigmaps) used to construct the working bigmap 
- INSIDE.TXT - (Created) The maplets that fall completely within the planned bigmap. Possibility created by bigmap.e 
- USED_MAPS - (Crated) All the maps used to create the bigmap. 
- Many files must be unique. All directories can be linked to a master.
Optional
- BIGMAP.IN - a list of landmarks that you want to use for bigmap. It allows you to reduce the number of files and avoid low resolution images. 
- LMRKLIST.TXT - Same as above, but only used if BIGMAP.IN is missing (used for historical purposes) 
- If there are neither of these files, then it will build the list of files that are included in the coverage
Input stdin
- A long set of commands are sent into this program that are usually contained within a file  Longitude is in west longitude (meaning that you need a negative to match what is used in spheremapB.e Longitude is in west longitude (meaning that you need a negative to match what is used in spheremapB.e
- example:
~/bin/bigmap.e < ZN0208.IN
Input file
The format is normally something like this.
l   (select location, 1 is lat/lon)
    20    -40    (latitude, west longitude)
   0.06250       500   1.23400     (scale, qsz (number of pixels), seed) 
ZN0208           (filename)
1                (end or integrate, 1 is integrate)
.005             (input fraction)
.025             (input weight)
1                (end, continue, change weight, smooth, 1 is continue integrating)
1                (end, continue, change weight, smooth, 1 is continue integrating)
1                (end, continue, change weight, smooth, 1 is continue integrating)
0                (end, continue, change weight, smooth, 0 is end iteration)
0                (no, square or round template, 0 is No Template)
Output
- bigmap with the name based on the input (e.g. ZN0208.IN).
- slopeb.pgm image, that shows the slope in both in horizontal and vertical.
- SIGMAS.TXT - Each time BIGMAP is run, it will add a line to this file showing the current sigma values
- SIGMAS.pgm -  - It graphically shows the highest level of error (sigma) is for maplets. - It graphically shows the highest level of error (sigma) is for maplets.







