sis tool
S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
- splat [-t _\bt_\br_\ba_\bn_\bs_\bm_\bi_\bt_\bt_\be_\br_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh] [-r _\br_\be_\bc_\be_\bi_\bv_\be_\br_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh]
- [-c _\br_\bx_\b__\ba_\bn_\bt_\be_\bn_\bn_\ba_\b__\bh_\be_\bi_\bg_\bh_\bt_\b__\bf_\bo_\br_\b__\bl_\bo_\bs_\b__\bc_\bo_\bv_\be_\br_\ba_\bg_\be_\b__\ba_\bn_\ba_\bl_\by_\bs_\bi_\bs _\b(_\bf_\be_\be_\bt_\b)
- _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-L _\br_\bx_\b__\ba_\bn_\bt_\be_\bn_\bn_\ba_\b__\bh_\be_\bi_\bg_\bh_\bt_\b__\bf_\bo_\br_\b__\bL_\bo_\bn_\bg_\bl_\be_\by_\b-_\bR_\bi_\bc_\be_\b__\bc_\bo_\bv_\be_\br_\b-
- _\ba_\bg_\be_\b__\ba_\bn_\ba_\bl_\by_\bs_\bi_\bs _\b(_\bf_\be_\be_\bt_\b) _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-p _\bt_\be_\br_\br_\ba_\bi_\bn_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-e
- _\be_\bl_\be_\bv_\ba_\bt_\bi_\bo_\bn_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-h _\bh_\be_\bi_\bg_\bh_\bt_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-l _\bL_\bo_\bn_\bg_\b-
- _\bl_\be_\by_\b-_\bR_\bi_\bc_\be_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-o _\bt_\bo_\bp_\bo_\bg_\br_\ba_\bp_\bh_\bi_\bc_\b__\bm_\ba_\bp_\b__\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b._\bp_\bp_\bm]
- [-b _\bc_\ba_\br_\bt_\bo_\bg_\br_\ba_\bp_\bh_\bi_\bc_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by_\b__\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b._\bd_\ba_\bt] [-s
- _\bs_\bi_\bt_\be_\b/_\bc_\bi_\bt_\by_\b__\bd_\ba_\bt_\ba_\bb_\ba_\bs_\be_\b._\bd_\ba_\bt] [-d _\bs_\bd_\bf_\b__\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by_\b__\bp_\ba_\bt_\bh] [-m
- _\be_\ba_\br_\bt_\bh_\b__\br_\ba_\bd_\bi_\bu_\bs_\b__\bm_\bu_\bl_\bt_\bi_\bp_\bl_\bi_\be_\br _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-R _\bm_\ba_\bx_\bi_\bm_\bu_\bm_\b__\bc_\bo_\bv_\be_\br_\b-
- _\ba_\bg_\be_\b__\br_\ba_\bn_\bg_\be _\b(_\bf_\bo_\br _\b-_\bc _\bo_\br _\b-_\bL_\b) _\b(_\bm_\bi_\bl_\be_\bs_\b) _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-dB _\bm_\ba_\bx_\bi_\bm_\bu_\bm
- _\ba_\bt_\bt_\be_\bn_\bu_\ba_\bt_\bi_\bo_\bn _\bc_\bo_\bn_\bt_\bo_\bu_\br _\bt_\bo _\bd_\bi_\bs_\bp_\bl_\ba_\by _\bo_\bn _\bp_\ba_\bt_\bh _\bl_\bo_\bs_\bs _\bm_\ba_\bp_\bs _\b(_\b8_\b0_\b-_\b2_\b3_\b0
- _\bd_\bB_\b)] [-n] [-N]
+ splat [-t _\bt_\br_\ba_\bn_\bs_\bm_\bi_\bt_\bt_\be_\br_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh] [-r _\br_\be_\bc_\be_\bi_\bv_\be_\br_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh]
+ [-c _\br_\bx _\ba_\bn_\bt_\be_\bn_\bn_\ba _\bh_\be_\bi_\bg_\bh_\bt _\bf_\bo_\br _\bL_\bO_\bS _\bc_\bo_\bv_\be_\br_\ba_\bg_\be _\ba_\bn_\ba_\bl_\by_\bs_\bi_\bs
+ _\b(_\bf_\be_\be_\bt_\b/_\bm_\be_\bt_\be_\br_\bs_\b) _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-L _\br_\bx _\ba_\bn_\bt_\be_\bn_\bn_\ba _\bh_\be_\bi_\bg_\bh_\bt _\bf_\bo_\br _\bL_\bo_\bn_\bg_\bl_\be_\by_\b-
+ _\bR_\bi_\bc_\be _\bc_\bo_\bv_\be_\br_\ba_\bg_\be _\ba_\bn_\ba_\bl_\by_\bs_\bi_\bs _\b(_\bf_\be_\be_\bt_\b/_\bm_\be_\bt_\be_\br_\bs_\b) _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-p _\bt_\be_\br_\b-
+ _\br_\ba_\bi_\bn_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-e _\be_\bl_\be_\bv_\ba_\bt_\bi_\bo_\bn_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-h
+ _\bh_\be_\bi_\bg_\bh_\bt_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-H _\bn_\bo_\br_\bm_\ba_\bl_\bi_\bz_\be_\bd_\b__\bh_\be_\bi_\bg_\bh_\bt_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-l
+ _\bL_\bo_\bn_\bg_\bl_\be_\by_\b-_\bR_\bi_\bc_\be_\b__\bp_\br_\bo_\bf_\bi_\bl_\be_\b._\be_\bx_\bt] [-o _\bt_\bo_\bp_\bo_\bg_\br_\ba_\bp_\bh_\bi_\bc_\b__\bm_\ba_\bp_\b__\bf_\bi_\bl_\be_\b-
+ _\bn_\ba_\bm_\be_\b._\bp_\bp_\bm] [-b _\bc_\ba_\br_\bt_\bo_\bg_\br_\ba_\bp_\bh_\bi_\bc_\b__\bb_\bo_\bu_\bn_\bd_\ba_\br_\by_\b__\bf_\bi_\bl_\be_\bn_\ba_\bm_\be_\b._\bd_\ba_\bt] [-s
+ _\bs_\bi_\bt_\be_\b/_\bc_\bi_\bt_\by_\b__\bd_\ba_\bt_\ba_\bb_\ba_\bs_\be_\b._\bd_\ba_\bt] [-d _\bs_\bd_\bf_\b__\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by_\b__\bp_\ba_\bt_\bh] [-m _\be_\ba_\br_\bt_\bh
+ _\br_\ba_\bd_\bi_\bu_\bs _\bm_\bu_\bl_\bt_\bi_\bp_\bl_\bi_\be_\br _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-f _\bf_\br_\be_\bq_\bu_\be_\bn_\bc_\by _\b(_\bM_\bH_\bz_\b) _\bf_\bo_\br _\bF_\br_\be_\bs_\bn_\be_\bl
+ _\bz_\bo_\bn_\be _\bc_\ba_\bl_\bc_\bu_\bl_\ba_\bt_\bi_\bo_\bn_\bs _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-R _\bm_\ba_\bx_\bi_\bm_\bu_\bm _\bc_\bo_\bv_\be_\br_\ba_\bg_\be _\br_\ba_\bd_\bi_\bu_\bs
+ _\b(_\bm_\bi_\bl_\be_\bs_\b/_\bk_\bi_\bl_\bo_\bm_\be_\bt_\be_\br_\bs_\b) _\b(_\bf_\bl_\bo_\ba_\bt_\b)] [-dB _\bm_\ba_\bx_\bi_\bm_\bu_\bm _\ba_\bt_\bt_\be_\bn_\bu_\ba_\bt_\bi_\bo_\bn _\bc_\bo_\bn_\b-
+ _\bt_\bo_\bu_\br _\bt_\bo _\bd_\bi_\bs_\bp_\bl_\ba_\by _\bo_\bn _\bp_\ba_\bt_\bh _\bl_\bo_\bs_\bs _\bm_\ba_\bp_\bs _\b(_\b8_\b0_\b-_\b2_\b3_\b0 _\bd_\bB_\b)] [-nf _\bd_\bo _\bn_\bo_\bt
+ _\bp_\bl_\bo_\bt _\bF_\br_\be_\bs_\bn_\be_\bl _\bz_\bo_\bn_\be_\bs _\bi_\bn _\bh_\be_\bi_\bg_\bh_\bt _\bp_\bl_\bo_\bt_\bs] [-plo _\bp_\ba_\bt_\bh_\b__\bl_\bo_\bs_\bs_\b__\bo_\bu_\bt_\b-
+ _\bp_\bu_\bt_\b__\bf_\bi_\bl_\be_\b._\bt_\bx_\bt] [-pli _\bp_\ba_\bt_\bh_\b__\bl_\bo_\bs_\bs_\b__\bi_\bn_\bp_\bu_\bt_\b__\bf_\bi_\bl_\be_\b._\bt_\bx_\bt] [-udt
+ _\bu_\bs_\be_\br_\b__\bd_\be_\bf_\bi_\bn_\be_\bd_\b__\bt_\be_\br_\br_\ba_\bi_\bn_\b__\bf_\bi_\bl_\be_\b._\bd_\ba_\bt] [-n] [-N] [-geo] [-kml]
+ [-metric]
D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
- S\bSP\bPL\bLA\bAT\bT!\b! is a powerful terrestrial RF propagation and ter-
- rain analysis tool covering the spectrum between 20 MHz
- and 20 GHz. It is designed for operation on Unix and
- Linux-based workstations. S\bSP\bPL\bLA\bAT\bT!\b! is free software.
- Redistribution and/or modification is permitted under the
- terms of the GNU General Public License as published by
- the Free Software Foundation, either version 2 of the
- License or any later version. Adoption of S\bSP\bPL\bLA\bAT\bT!\b! source
- code in proprietary or closed-source applications is a
- violation of this license, and is s\bst\btr\bri\bic\bct\btl\bly\by forbidden.
-
- S\bSP\bPL\bLA\bAT\bT!\b! is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY, without even the implied war-
- ranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
+ S\bSP\bPL\bLA\bAT\bT!\b! is a powerful terrestrial RF propagation and ter-
+ rain analysis tool covering the spectrum between 20 MHz
+ and 20 GHz. S\bSP\bPL\bLA\bAT\bT!\b! is free software, and is designed for
+ operation on Unix and Linux-based workstations. Redistri-
+ bution and/or modification is permitted under the terms of
+ the GNU General Public License as published by the Free
+ Software Foundation, either version 2 of the License or
+ any later version. Adoption of S\bSP\bPL\bLA\bAT\bT!\b! source code in pro-
+ prietary or closed-source applications is a violation of
+ this license, and is s\bst\btr\bri\bic\bct\btl\bly\by forbidden.
+
+ S\bSP\bPL\bLA\bAT\bT!\b! is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY, without even the implied war-
+ ranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE. See the GNU General Public License for more details.
I\bIN\bNT\bTR\bRO\bOD\bDU\bUC\bCT\bTI\bIO\bON\bN
- Applications of S\bSP\bPL\bLA\bAT\bT!\b! include the visualization, design,
- and link budget analysis of wireless Wide Area Networks
+ Applications of S\bSP\bPL\bLA\bAT\bT!\b! include the visualization, design,
+ and link budget analysis of wireless Wide Area Networks
(WANs), commercial and amateur radio communication systems
- above 20 MHz, microwave links, frequency coordination, and
- the determination of analog and digital terrestrial radio
- and television contour regions.
+ above 20 MHz, microwave links, frequency coordination and
+ interference studies, and the determination of analog and
+ digital terrestrial radio and television contour regions.
S\bSP\bPL\bLA\bAT\bT!\b! provides RF site engineering data such as great
circle distances and bearings between sites, antenna ele-
vation angles (uptilt), depression angles (downtilt),
antenna height above mean sea level, antenna height above
average terrain, bearings and distances to known obstruc-
- tions, Longley-Rice path attenuation, and minimum antenna
- height requirements needed to establish line-of-sight com-
- munication paths absent of obstructions due to terrain.
- S\bSP\bPL\bLA\bAT\bT!\b! produces reports, graphs, and highly detailed and
- carefully annotated topographic maps depicting line-of-
- sight paths, path loss, and expected coverage areas of
- transmitters and repeater systems. When performing line-
- of-sight analysis in situations where multiple transmitter
- or repeater sites are employed, S\bSP\bPL\bLA\bAT\bT!\b! determines individ-
- ual and mutual areas of coverage within the network speci-
- fied.
+ tions, and Longley-Rice path attenuation. In addition,
+ the minimum antenna height requirements needed to clear
+ terrain, the first Fresnel zone, and 60% of the first
+ Fresnel zone are also provided.
+
+ S\bSP\bPL\bLA\bAT\bT!\b! produces reports, graphs, and high resolution topo-
+ graphic maps that depict line-of-sight paths, and regional
+ path loss contours through which expected coverage areas
+ of transmitters and repeater systems can be obtained.
+ When performing line-of-sight analysis in situations where
+ multiple transmitter or repeater sites are employed,
+ S\bSP\bPL\bLA\bAT\bT!\b! determines individual and mutual areas of coverage
+ within the network specified.
+
+ Simply typing splat on the command line will return a sum-
+ mary of S\bSP\bPL\bLA\bAT\bT!\b!'s command line options:
+
+ --==[ SPLAT! v1.2.0 Available Options...
+ ]==--
+
+ -t txsite(s).qth (max of 4)
+ -r rxsite.qth
+ -c plot coverage of TX(s) with an RX antenna at X
+ feet/meters AGL
+ -L plot path loss map of TX based on an RX at X
+ feet/meters AGL
+ -s filename(s) of city/site file(s) to import (max
+ of 5)
+ -b filename(s) of cartographic boundary file(s) to
+ import (5 max)
+ -p filename of terrain profile graph to plot
+ -e filename of terrain elevation graph to plot
+ -h filename of terrain height graph to plot
+ -H filename of normalized terrain height graph to
+ plot
+ -l filename of Longley-Rice graph to plot
+ -o filename of topographic map to generate (.ppm)
+ -u filename of user-defined terrain file to import
+ -d sdf file directory path (overrides path in
+ ~/.splat_path file)
+ -n no analysis, brief report
+ -N no analysis, no report
+ -m earth radius multiplier
+ -f frequency for Fresnel zone calculation (MHz)
+ -R modify default range for -c or -L (miles/kilome-
+ ters)
+ -db maximum loss contour to display on path loss maps
+ (80-230 dB)
+ -nf do not plot Fresnel zones in height plots
+ -plo filename of path-loss output file
+ -pli filename of path-loss input file
+ -udt filename of user defined terrain input file
+ -geo generate a .geo georeference file (with .ppm out-
+ put)
+ -kml generate a Google Earth .kml file (for point-to-
+ point links)
+ -metric employ metric rather than imperial units for all
+ user I/O
- S\bSP\bPL\bLA\bAT\bT!\b! operates in two distinct modes: _\bp_\bo_\bi_\bn_\bt_\b-_\bt_\bo_\b-_\bp_\bo_\bi_\bn_\bt
- _\bm_\bo_\bd_\be, and _\ba_\br_\be_\ba _\bp_\br_\be_\bd_\bi_\bc_\bt_\bi_\bo_\bn _\bm_\bo_\bd_\be, and may be invoked using
- either line-of-sight (LOS) or Irregular Terrain (ITM)
- propagation models. True Earth, four-thirds Earth, or any
- other Earth radius may be specified by the user when per-
- forming line-of-sight analysis.
I\bIN\bNP\bPU\bUT\bT F\bFI\bIL\bLE\bES\bS
S\bSP\bPL\bLA\bAT\bT!\b! is a command-line driven application, and reads
input data through a number of data files. Some files are
mandatory for successful execution of the program, while
- others are optional. Mandatory files include SPLAT Data
- Files (SDF files), site location files (QTH files), and
- Longley-Rice model parameter files (LRP files). Optional
- files include city/site location files, and cartographic
- boundary files.
+ others are optional. Mandatory files include 3-arc second
+ topography models in the form of SPLAT Data Files (SDF
+ files), site location files (QTH files), and Longley-Rice
+ model parameter files (LRP files). Optional files include
+ city location files, cartographic boundary files, user-
+ defined terrain files, path-loss input files, and antenna
+ radiation pattern files.
S\bSP\bPL\bLA\bAT\bT D\bDA\bAT\bTA\bA F\bFI\bIL\bLE\bES\bS
S\bSP\bPL\bLA\bAT\bT!\b! imports topographic data in the form of SPLAT Data
patible with this utility may be downloaded from:
_\bh_\bt_\bt_\bp_\b:_\b/_\b/_\be_\bd_\bc_\bf_\bt_\bp_\b._\bc_\br_\b._\bu_\bs_\bg_\bs_\b._\bg_\bo_\bv_\b/_\bp_\bu_\bb_\b/_\bd_\ba_\bt_\ba_\b/_\bD_\bE_\bM_\b/_\b2_\b5_\b0_\b/.
- Significantly better resolution can be obtained through
- the use of SRTM-3 Version 2 digital elevation models.
- These models are the result of the STS-99 Space Shuttle
- Radar Topography Mission, and are available for most popu-
- lated regions of the Earth. SPLAT Data Files may be gen-
- erated from SRTM data using the included s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf utility.
- SRTM-3 Version 2 data may be obtained through anonymous
- FTP from: _\bf_\bt_\bp_\b:_\b/_\b/_\be_\b0_\bs_\br_\bp_\b0_\b1_\bu_\b._\be_\bc_\bs_\b._\bn_\ba_\bs_\ba_\b._\bg_\bo_\bv_\b:_\b2_\b1_\b/_\bs_\br_\bt_\bm_\b/_\bv_\be_\br_\bs_\bi_\bo_\bn_\b2_\b/
-
- Despite the higher accuracy that SRTM data has to offer,
- some voids in the data sets exist. When voids are
- detected, the s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf utility replaces them with corre-
- sponding data found in existing SDF files (that were pre-
- sumably created from earlier USGS data through the
+ Significantly better resolution and accuracy can be
+ obtained through the use of SRTM-3 Version 2 digital ele-
+ vation models. These models are the product of the STS-99
+ Space Shuttle Radar Topography Mission, and are available
+ for most populated regions of the Earth. SPLAT Data Files
+ may be generated from SRTM data using the included
+ s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf utility. SRTM-3 Version 2 data may be obtained
+ through anonymous FTP from:
+ _\bf_\bt_\bp_\b:_\b/_\b/_\be_\b0_\bs_\br_\bp_\b0_\b1_\bu_\b._\be_\bc_\bs_\b._\bn_\ba_\bs_\ba_\b._\bg_\bo_\bv_\b:_\b2_\b1_\b/_\bs_\br_\bt_\bm_\b/_\bv_\be_\br_\bs_\bi_\bo_\bn_\b2_\b/
+
+ Despite the higher accuracy that SRTM data has to offer,
+ some voids in the data sets exist. When voids are
+ detected, the s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf utility replaces them with corre-
+ sponding data found in existing SDF files (that were pre-
+ sumably created from earlier USGS data through the
u\bus\bsg\bgs\bs2\b2s\bsd\bdf\bf utility). If USGS-derived SDF data is not avail-
- able, voids are handled through adjacent pixel averaging,
+ able, voids are handled through adjacent pixel averaging,
or direct replacement.
- SPLAT Data Files contain integer value topographic eleva-
+ SPLAT Data Files contain integer value topographic eleva-
tions (in meters) referenced to mean sea level for
- 1-degree by 1-degree regions of the earth with a resolu-
- tion of 3-arc seconds. SDF files can be read in either
- standard format (_\b._\bs_\bd_\bf) as generated by the u\bus\bsg\bgs\bs2\b2s\bsd\bdf\bf and
- s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf utilities, or in bzip2 compressed format
- (_\b._\bs_\bd_\bf_\b._\bb_\bz_\b2). Since uncompressed files can be processed
- slightly faster than files that have been compressed,
- S\bSP\bPL\bLA\bAT\bT!\b! searches for the needed SDF data in uncompressed
- format first. If uncompressed data cannot located, S\bSP\bPL\bLA\bAT\bT!\b!
- then searches for data in bzip2 compressed format. If no
- compressed SDF files can be found for the region
- requested, S\bSP\bPL\bLA\bAT\bT!\b! assumes the region is over water, and
+ 1-degree by 1-degree regions of the earth with a resolu-
+ tion of 3-arc seconds. SDF files can be read in either
+ standard format (_\b._\bs_\bd_\bf) as generated by the u\bus\bsg\bgs\bs2\b2s\bsd\bdf\bf and
+ s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf utilities, or in bzip2 compressed format
+ (_\b._\bs_\bd_\bf_\b._\bb_\bz_\b2). Since uncompressed files can be processed
+ slightly faster than files that have been compressed,
+ S\bSP\bPL\bLA\bAT\bT!\b! searches for needed SDF data in uncompressed format
+ first. If uncompressed data cannot be located, S\bSP\bPL\bLA\bAT\bT!\b!
+ then searches for data in bzip2 compressed format. If no
+ compressed SDF files can be found for the region
+ requested, S\bSP\bPL\bLA\bAT\bT!\b! assumes the region is over water, and
will assign an elevation of sea-level to these areas.
- This feature of S\bSP\bPL\bLA\bAT\bT!\b! makes it possible to perform path
- analysis not only over land, but also between coastal
- areas not represented by Digital Elevation Model data.
- This behavior of S\bSP\bPL\bLA\bAT\bT!\b! underscores the importance of hav-
- ing all the SDF files required for the region being ana-
- lyzed if meaningful results are to be expected.
+ This feature of S\bSP\bPL\bLA\bAT\bT!\b! makes it possible to perform path
+ analysis not only over land, but also between coastal
+ areas not represented by Digital Elevation Model data.
+ However, this behavior of S\bSP\bPL\bLA\bAT\bT!\b! underscores the impor-
+ tance of having all the SDF files required for the region
+ being analyzed if meaningful results are to be expected.
S\bSI\bIT\bTE\bE L\bLO\bOC\bCA\bAT\bTI\bIO\bON\bN (\b(Q\bQT\bTH\bH)\b) F\bFI\bIL\bLE\bES\bS
- S\bSP\bPL\bLA\bAT\bT!\b! imports site location information of transmitter
- and receiver sites analyzed by the program from ASCII
- files having a _\b._\bq_\bt_\bh extension. QTH files contain the
+ S\bSP\bPL\bLA\bAT\bT!\b! imports site location information of transmitter
+ and receiver sites analyzed by the program from ASCII
+ files having a _\b._\bq_\bt_\bh extension. QTH files contain the
site's name, the site's latitude (positive if North of the
- equator, negative if South), the site's longitude (in
- degrees West, 0 to 360 degrees), and the site's antenna
- height above ground level (AGL). A single line-feed char-
- acter separates each field. The antenna height is assumed
- to be specified in feet unless followed by the letter _\bm or
- the word _\bm_\be_\bt_\be_\br_\bs in either upper or lower case. Latitude
+ equator, negative if South), the site's longitude (in
+ degrees West, 0 to 360 degrees), and the site's antenna
+ height above ground level (AGL), each separated by a sin-
+ gle line-feed character. The antenna height is assumed to
+ be specified in feet unless followed by the letter _\bm or
+ the word _\bm_\be_\bt_\be_\br_\bs in either upper or lower case. Latitude
and longitude information may be expressed in either deci-
- mal format (74.6889) or degree, minute, second (DMS) for-
+ mal format (74.6889) or degree, minute, second (DMS) for-
mat (74 41 20.0).
- For example, a site location file describing television
- station WNJT, Trenton, NJ (_\bw_\bn_\bj_\bt_\b._\bq_\bt_\bh) might read as fol-
+ For example, a site location file describing television
+ station WNJT, Trenton, NJ (_\bw_\bn_\bj_\bt_\b._\bq_\bt_\bh) might read as fol-
lows:
WNJT
be represented by its own site location (QTH) file.
L\bLO\bON\bNG\bGL\bLE\bEY\bY-\b-R\bRI\bIC\bCE\bE P\bPA\bAR\bRA\bAM\bME\bET\bTE\bER\bR (\b(L\bLR\bRP\bP)\b) F\bFI\bIL\bLE\bES\bS
- S\bSP\bPL\bLA\bAT\bT!\b! imports Longley-Rice model parameter data from
- files having the same base name as the transmitter site
- QTH file, but with a _\b._\bl_\br_\bp extension, thus providing simple
- and accurate correlation between these associated data
- sets. The format for the Longley-Rice model parameter
- files is as follows (_\bw_\bn_\bj_\bt_\b._\bl_\br_\bp):
+ Longley-Rice parameter data files are required for S\bSP\bPL\bLA\bAT\bT!\b!
+ to determine RF path loss in either point-to-point or area
+ prediction mode. Longley-Rice model parameter data is
+ read from files having the same base name as the transmit-
+ ter site QTH file, but with a format (_\bw_\bn_\bj_\bt_\b._\bl_\br_\bp):
15.000 ; Earth Dielectric Constant (Relative per-
mittivity)
the statistical analysis provided by the Longley-Rice
model. In this example, S\bSP\bPL\bLA\bAT\bT!\b! will return the maximum
path loss occurring 50% of the time (fraction of time) in
- 50% of situations (fraction of situations). Use a frac-
- tion of time parameter of 0.97 for digital television,
- 0.50 for analog in the United States. Isotropic antennas
- are assumed.
+ 50% of situations (fraction of situations). In the United
+ States, use a fraction of time parameter of 0.97 for digi-
+ tal television (8VSB modulation), or 0.50 for analog (VSB-
+ AM+NTSC) transmissions.
For further information on these parameters, see:
_\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bf_\bl_\ba_\bt_\bt_\bo_\bp_\b._\bi_\bt_\bs_\b._\bb_\bl_\bd_\br_\bd_\bo_\bc_\b._\bg_\bo_\bv_\b/_\bi_\bt_\bm_\b._\bh_\bt_\bm_\bl and
points of interest may be imported and plotted on topo-
graphic maps generated by S\bSP\bPL\bLA\bAT\bT!\b!. S\bSP\bPL\bLA\bAT\bT!\b! imports the
names of cities and locations from ASCII files containing
- the location's name, the location's latitude, and the
- location's longitude. Each field is separated by a comma.
- Each record is separated by a single line feed character.
- As was the case with the _\b._\bq_\bt_\bh files, latitude and longi-
- tude information may be entered in either decimal or
- degree, minute, second (DMS) format.
+ the location of interest's name, latitude, and longitude.
+ Each field is separated by a comma. Each record is sepa-
+ rated by a single line feed character. As was the case
+ with the _\b._\bq_\bt_\bh files, latitude and longitude information
+ may be entered in either decimal or degree, minute, second
+ (DMS) format.
For example (_\bc_\bi_\bt_\bi_\be_\bs_\b._\bd_\ba_\bt):
at a time, and there is no limit to the size of these
files. S\bSP\bPL\bLA\bAT\bT!\b! reads city data on a "first come/first
served" basis, and plots only those locations whose anno-
- tations do not conflict with annotations of locations
- plotted earlier during S\bSP\bPL\bLA\bAT\bT's execution. This behavior
- minimizes clutter in S\bSP\bPL\bLA\bAT\bT!\b! generated topographic maps,
- but also mandates that important locations be placed
- toward the beginning of the first city data file, and
- disposable locations be positioned further down the list
- or in subsequent data files.
+ tations do not conflict with annotations of locations read
+ earlier in the current city data file, or in previous
+ files. This behavior minimizes clutter in S\bSP\bPL\bLA\bAT\bT!\b! gener-
+ ated topographic maps, but also mandates that important
+ locations be placed toward the beginning of the first city
+ data file, and locations less important be positioned fur-
+ ther down the list or in subsequent data files.
City data files may be generated manually using any text
editor, imported from other sources, or derived from data
graphic maps generated by S\bSP\bPL\bLA\bAT\bT!\b!. Such data must be of
the form of ARC/INFO Ungenerate (ASCII Format) Metadata
Cartographic Boundary Files, and are available from the
- U.S. Census Bureau via the Internet at: _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bc_\be_\bn_\b-
- _\bs_\bu_\bs_\b._\bg_\bo_\bv_\b/_\bg_\be_\bo_\b/_\bw_\bw_\bw_\b/_\bc_\bo_\bb_\b/_\bc_\bo_\b2_\b0_\b0_\b0_\b._\bh_\bt_\bm_\bl_\b#_\ba_\bs_\bc_\bi_\bi and _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bc_\be_\bn_\b-
- _\bs_\bu_\bs_\b._\bg_\bo_\bv_\b/_\bg_\be_\bo_\b/_\bw_\bw_\bw_\b/_\bc_\bo_\bb_\b/_\bp_\bl_\b2_\b0_\b0_\b0_\b._\bh_\bt_\bm_\bl_\b#_\ba_\bs_\bc_\bi_\bi. A total of five
- separate cartographic boundary files may be imported at a
- time. It is not necessary to import state boundaries if
- county boundaries have already been imported.
+ U.S. Census Bureau via the Internet at:
+ _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bc_\be_\bn_\bs_\bu_\bs_\b._\bg_\bo_\bv_\b/_\bg_\be_\bo_\b/_\bw_\bw_\bw_\b/_\bc_\bo_\bb_\b/_\bc_\bo_\b2_\b0_\b0_\b0_\b._\bh_\bt_\bm_\bl_\b#_\ba_\bs_\bc_\bi_\bi and
+ _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bc_\be_\bn_\bs_\bu_\bs_\b._\bg_\bo_\bv_\b/_\bg_\be_\bo_\b/_\bw_\bw_\bw_\b/_\bc_\bo_\bb_\b/_\bp_\bl_\b2_\b0_\b0_\b0_\b._\bh_\bt_\bm_\bl_\b#_\ba_\bs_\bc_\bi_\bi. A
+ total of five separate cartographic boundary files may be
+ imported at a time. It is not necessary to import state
+ boundaries if county boundaries have already been
+ imported.
P\bPR\bRO\bOG\bGR\bRA\bAM\bM O\bOP\bPE\bER\bRA\bAT\bTI\bIO\bON\bN
- S\bSP\bPL\bLA\bAT\bT!\b! is invoked via the command-line using a series of
- switches and arguments. Since S\bSP\bPL\bLA\bAT\bT!\b! is a CPU and memory
- intensive application, this type of interface minimizes
- overhead and lends itself well to scripted (batch) opera-
+ S\bSP\bPL\bLA\bAT\bT!\b! is invoked via the command-line using a series of
+ switches and arguments. Since S\bSP\bPL\bLA\bAT\bT!\b! is a CPU and memory
+ intensive application, this type of interface minimizes
+ overhead and lends itself well to scripted (batch) opera-
tions. S\bSP\bPL\bLA\bAT\bT!\b!'s CPU and memory scheduling priority may be
modified through the use of the Unix n\bni\bic\bce\be command.
The number and type of switches passed to S\bSP\bPL\bLA\bAT\bT!\b! determine
- its mode of operation and method of output data genera-
- tion. Nearly all of S\bSP\bPL\bLA\bAT\bT!\b!'s switches may be cascaded in
+ its mode of operation and method of output data genera-
+ tion. Nearly all of S\bSP\bPL\bLA\bAT\bT!\b!'s switches may be cascaded in
any order on the command line when invoking the program.
+ S\bSP\bPL\bLA\bAT\bT!\b! operates in two distinct modes: _\bp_\bo_\bi_\bn_\bt_\b-_\bt_\bo_\b-_\bp_\bo_\bi_\bn_\bt
+ _\bm_\bo_\bd_\be, and _\ba_\br_\be_\ba _\bp_\br_\be_\bd_\bi_\bc_\bt_\bi_\bo_\bn _\bm_\bo_\bd_\be. Either a line-of-sight
+ (LOS) or Longley-Rice Irregular Terrain (ITM) propagation
+ model may be invoked by the user. True Earth, four-thirds
+ Earth, or any other user-defined Earth radius may be spec-
+ ified when performing line-of-sight analysis.
+
P\bPO\bOI\bIN\bNT\bT-\b-T\bTO\bO-\b-P\bPO\bOI\bIN\bNT\bT A\bAN\bNA\bAL\bLY\bYS\bSI\bIS\bS
S\bSP\bPL\bLA\bAT\bT!\b! may be used to perform line-of-sight terrain analy-
sis between two specified site locations. For example:
splat -t tx_site.qth -r rx_site.qth
- invokes a terrain analysis between the transmitter speci-
- fied in _\bt_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh and receiver specified in _\br_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh,
- and writes a S\bSP\bPL\bLA\bAT\bT!\b! Obstruction Report to the current
- working directory. The report contains details of the
- transmitter and receiver sites, and identifies the loca-
- tion of any obstructions detected during the analysis. If
- an obstruction can be cleared by raising the receive
- antenna to a greater altitude, S\bSP\bPL\bLA\bAT\bT!\b! will indicate the
- minimum antenna height required for a line-of-sight path
- to exist between the transmitter and receiver locations
- specified. If the antenna must be raised a significant
- amount, this determination may take some time. Note that
- the results provided are the _\bm_\bi_\bn_\bi_\bm_\bu_\bm necessary for a line-
- of-sight path to exist, and do not take Fresnel zone
- clearance requirements into consideration.
+ invokes a line-of-sight terrain analysis between the
+ transmitter specified in _\bt_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh and receiver speci-
+ fied in _\br_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh using a True Earth radius model, and
+ writes a S\bSP\bPL\bLA\bAT\bT!\b! Obstruction Report to the current working
+ directory. The report contains details of the transmitter
+ and receiver sites, and identifies the location of any
+ obstructions detected along the line-of-sight path. If an
+ obstruction can be cleared by raising the receive antenna
+ to a greater altitude, S\bSP\bPL\bLA\bAT\bT!\b! will indicate the minimum
+ antenna height required for a line-of-sight path to exist
+ between the transmitter and receiver locations specified.
+ Note that imperial units (miles, feet) are specified
+ unless the _\b-_\bm_\be_\bt_\br_\bi_\bc switch is added to S\bSP\bPL\bLA\bAT\bT!\b!'s command
+ line options:
+
+ splat -t tx_site.qth -r rx_site.qth -metric
+
+ If the antenna must be raised a significant amount, this
+ determination may take a few moments. Note that the
+ results provided are the _\bm_\bi_\bn_\bi_\bm_\bu_\bm necessary for a line-of-
+ sight path to exist, and in the case of this simple exam-
+ ple, do not take Fresnel zone clearance requirements into
+ consideration.
_\bq_\bt_\bh extensions are assumed by S\bSP\bPL\bLA\bAT\bT!\b! for QTH files, and
- are optional when invoking the program. S\bSP\bPL\bLA\bAT\bT!\b! automati-
- cally reads all SPLAT Data Files necessary to conduct the
- terrain analysis between the sites specified. S\bSP\bPL\bLA\bAT\bT!\b!
- searches for the needed SDF files in the current working
- directory first. If the needed files are not found,
- S\bSP\bPL\bLA\bAT\bT!\b! then searches in the path specified by the _\b-_\bd
- command-line switch:
+ are optional when specifying -t and -r arguments on the
+ command-line. S\bSP\bPL\bLA\bAT\bT!\b! automatically reads all SPLAT Data
+ Files necessary to conduct the terrain analysis between
+ the sites specified. S\bSP\bPL\bLA\bAT\bT!\b! searches for the required
+ SDF files in the current working directory first. If the
+ needed files are not found, S\bSP\bPL\bLA\bAT\bT!\b! then searches in the
+ path specified by the _\b-_\bd command-line switch:
splat -t tx_site -r rx_site -d /cdrom/sdf/
An external directory path may be specified by placing a
".splat_path" file under the user's home directory. This
- file must contain the full directory path to the last
- resort location of all the SDF files. The path in the
- _\b$_\bH_\bO_\bM_\bE_\b/_\b._\bs_\bp_\bl_\ba_\bt_\b__\bp_\ba_\bt_\bh file must be of the form of a single
- line of ASCII text:
+ file must contain the full directory path of last resort
+ to all the SDF files. The path in the _\b$_\bH_\bO_\bM_\bE_\b/_\b._\bs_\bp_\bl_\ba_\bt_\b__\bp_\ba_\bt_\bh
+ file must be of the form of a single line of ASCII text:
/opt/splat/sdf/
and can be generated using any text editor.
- A graph of the terrain profile between the receiver and
- transmitter locations as a function of distance from the
+ A graph of the terrain profile between the receiver and
+ transmitter locations as a function of distance from the
receiver can be generated by adding the _\b-_\bp switch:
- splat -t tx_site -r rx_site -p terrain_profile.gif
+ splat -t tx_site -r rx_site -p terrain_profile.png
- S\bSP\bPL\bLA\bAT\bT!\b! invokes g\bgn\bnu\bup\bpl\blo\bot\bt when generating graphs. The file-
- name extension specified to S\bSP\bPL\bLA\bAT\bT!\b! determines the format
- of the graph produced. _\b._\bg_\bi_\bf will produce a 640x480 color
- GIF graphic file, while _\b._\bp_\bs or _\b._\bp_\bo_\bs_\bt_\bs_\bc_\br_\bi_\bp_\bt will produce
- postscript output. Output in formats such as PNG, Adobe
- Illustrator, AutoCAD dxf, LaTeX, and many others are
+ S\bSP\bPL\bLA\bAT\bT!\b! invokes g\bgn\bnu\bup\bpl\blo\bot\bt when generating graphs. The file-
+ name extension specified to S\bSP\bPL\bLA\bAT\bT!\b! determines the format
+ of the graph produced. _\b._\bp_\bn_\bg will produce a 640x480 color
+ PNG graphic file, while _\b._\bp_\bs or _\b._\bp_\bo_\bs_\bt_\bs_\bc_\br_\bi_\bp_\bt will produce
+ postscript output. Output in formats such as GIF, Adobe
+ Illustrator, AutoCAD dxf, LaTeX, and many others are
available. Please consult g\bgn\bnu\bup\bpl\blo\bot\bt, and g\bgn\bnu\bup\bpl\blo\bot\bt's documen-
tation for details on all the supported output formats.
A graph of elevations subtended by the terrain between the
- receiver and transmitter as a function of distance from
+ receiver and transmitter as a function of distance from
the receiver can be generated by using the _\b-_\be switch:
- splat -t tx_site -r rx_site -e elevation_profile.gif
+ splat -t tx_site -r rx_site -e elevation_profile.png
- The graph produced using this switch illustrates the ele-
- vation and depression angles resulting from the terrain
- between the receiver's location and the transmitter site
+ The graph produced using this switch illustrates the ele-
+ vation and depression angles resulting from the terrain
+ between the receiver's location and the transmitter site
from the perspective of the receiver's location. A second
- trace is plotted between the left side of the graph
+ trace is plotted between the left side of the graph
(receiver's location) and the location of the transmitting
- antenna on the right. This trace illustrates the eleva-
- tion angle required for a line-of-sight path to exist
- between the receiver and transmitter locations. If the
+ antenna on the right. This trace illustrates the eleva-
+ tion angle required for a line-of-sight path to exist
+ between the receiver and transmitter locations. If the
trace intersects the elevation profile at any point on the
- graph, then this is an indication that a line-of-sight
- path does not exist under the conditions given, and the
+ graph, then this is an indication that a line-of-sight
+ path does not exist under the conditions given, and the
obstructions can be clearly identified on the graph at the
point(s) of intersection.
- A graph illustrating terrain height referenced to a line-
- of-sight path between the transmitter and receiver may be
+ A graph illustrating terrain height referenced to a line-
+ of-sight path between the transmitter and receiver may be
generated using the _\b-_\bh switch:
- splat -t tx_site -r rx_site -h height_profile.gif
+ splat -t tx_site -r rx_site -h height_profile.png
+
+ A terrain height plot normalized to the transmitter and
+ receiver antenna heights can be obtained using the _\b-_\bH
+ switch:
+
+ splat -t tx_site -r rx_site -H normalized_height_pro-
+ file.png
+
+ A contour of the Earth's curvature is also plotted in this
+ mode.
- The Earth's curvature is clearly evident when plotting
- height profiles.
+ The first Fresnel Zone, and 60% of the first Fresnel Zone
+ can be added to height profile graphs by adding the _\b-_\bf
+ switch, and specifying a frequency (in MHz) at which the
+ Fresnel Zone should be modeled:
+
+ splat -t tx_site -r rx_site -f 439.250 -H normal-
+ ized_height_profile.png
A graph showing Longley-Rice path loss may be plotted
using the _\b-_\bl switch:
- splat -t tx_site -r rx_site -l path_loss_profile.gif
+ splat -t tx_site -r rx_site -l path_loss_profile.png
+
+ As before, adding the _\b-_\bm_\be_\bt_\br_\bi_\bc switch forces the graphs to
+ be plotted using metric units of measure.
- When performing path loss profiles, a Longley-Rice Model
- Path Loss Report is generated by S\bSP\bPL\bLA\bAT\bT!\b! in the form of a
+ When performing path loss profiles, a Longley-Rice Model
+ Path Loss Report is generated by S\bSP\bPL\bLA\bAT\bT!\b! in the form of a
text file with a _\b._\bl_\br_\bo filename extension. The report con-
- tains bearings and distances between the transmitter and
- receiver, as well as the Longley-Rice path loss for vari-
- ous distances between the transmitter and receiver loca-
- tions. The mode of propagation for points along the path
- are given as _\bL_\bi_\bn_\be_\b-_\bo_\bf_\b-_\bS_\bi_\bg_\bh_\bt, _\bS_\bi_\bn_\bg_\bl_\be _\bH_\bo_\br_\bi_\bz_\bo_\bn, _\bD_\bo_\bu_\bb_\bl_\be _\bH_\bo_\br_\bi_\b-
+ tains bearings and distances between the transmitter and
+ receiver, as well as the Longley-Rice path loss for vari-
+ ous distances between the transmitter and receiver loca-
+ tions. The mode of propagation for points along the path
+ are given as _\bL_\bi_\bn_\be_\b-_\bo_\bf_\b-_\bS_\bi_\bg_\bh_\bt, _\bS_\bi_\bn_\bg_\bl_\be _\bH_\bo_\br_\bi_\bz_\bo_\bn, _\bD_\bo_\bu_\bb_\bl_\be _\bH_\bo_\br_\bi_\b-
_\bz_\bo_\bn, _\bD_\bi_\bf_\bf_\br_\ba_\bc_\bt_\bi_\bo_\bn _\bD_\bo_\bm_\bi_\bn_\ba_\bn_\bt, and _\bT_\br_\bo_\bp_\bo_\bs_\bc_\ba_\bt_\bt_\be_\br _\bD_\bo_\bm_\bi_\bn_\ba_\bn_\bt.
- To determine the signal-to-noise (SNR) ratio at remote
- location where random Johnson (thermal) noise is the pri-
+ To determine the signal-to-noise (SNR) ratio at remote
+ location where random Johnson (thermal) noise is the pri-
mary limiting factor in reception:
_\bS_\bN_\bR=_\bT-_\bN_\bJ-_\bL+_\bG-_\bN_\bF
- where T\bT is the ERP of the transmitter in dBW, N\bNJ\bJ is John-
- son Noise in dBW (-136 dBW for a 6 MHz TV channel), L\bL is
- the path loss provided by S\bSP\bPL\bLA\bAT\bT!\b! in dB (as a _\bp_\bo_\bs_\bi_\bt_\bi_\bv_\be num-
- ber), G\bG is the receive antenna gain in dB over isotropic,
- and N\bNF\bF is the receiver noise figure in dB.
+ where T\bT is the ERP of the transmitter in dBW in the direc-
+ tion of the receiver, N\bNJ\bJ is Johnson Noise in dBW (-136 dBW
+ for a 6 MHz television channel), L\bL is the path loss pro-
+ vided by S\bSP\bPL\bLA\bAT\bT!\b! in dB (as a _\bp_\bo_\bs_\bi_\bt_\bi_\bv_\be number), G\bG is the
+ receive antenna gain in dB over isotropic, and N\bNF\bF is the
+ receiver noise figure in dB.
T\bT may be computed as follows:
_\bS_\bi_\bg_\bn_\ba_\bl__\bM_\ba_\br_\bg_\bi_\bn=_\bS_\bN_\bR-_\bS
- where S\bS is the minimum desired SNR ratio (15.5 dB for ATSC
- DTV, 42 dB for analog NTSC television).
+ where S\bS is the minimum required SNR ratio (15.5 dB for
+ ATSC (8-VSB) DTV, 42 dB for analog NTSC television).
A topographic map may be generated by S\bSP\bPL\bLA\bAT\bT!\b! to visualize
the path between the transmitter and receiver sites from
only exception to this is sea-level, which is represented
using the color blue.
- S\bSP\bPL\bLA\bAT\bT!\b! generated topographic maps are 24-bit TrueColor
- Portable PixMap (PPM) images. They may be viewed, edited,
- or converted to other graphic formats by popular image
- viewing applications such as x\bxv\bv, T\bTh\bhe\be G\bGI\bIM\bMP\bP, I\bIm\bma\bag\bge\beM\bMa\bag\bgi\bic\bck\bk,
- and X\bXP\bPa\bai\bin\bnt\bt. PNG format is highly recommended for lossless
- compressed storage of S\bSP\bPL\bLA\bAT\bT!\b! generated topographic output
- files. An excellent command-line utility capable of con-
- verting S\bSP\bPL\bLA\bAT\bT!\b! PPM graphic files to PNG files is w\bwp\bpn\bng\bg, and
- is available at:
- _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bl_\bi_\bb_\bp_\bn_\bg_\b._\bo_\br_\bg_\b/_\bp_\bu_\bb_\b/_\bp_\bn_\bg_\b/_\bb_\bo_\bo_\bk_\b/_\bs_\bo_\bu_\br_\bc_\be_\bs_\b._\bh_\bt_\bm_\bl. As a
- last resort, PPM files may be compressed using the bzip2
- utility, and read directly by T\bTh\bhe\be G\bGI\bIM\bMP\bP in this format.
- Topographic output is specified using the _\b-_\bo switch:
+ Topographic output is invoked using the _\b-_\bo switch:
splat -t tx_site -r rx_site -o topo_map.ppm
a time for analysis:
splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p
- profile.gif
+ profile.png
In this example, four separate terrain profiles and
obstruction reports will be generated by S\bSP\bPL\bLA\bAT\bT!\b!. A single
receiver will be in violet, and the path between the
fourth transmitter and the receiver will be in sienna.
-D\bDE\bET\bTE\bER\bRM\bMI\bIN\bNI\bIN\bNG\bG R\bRE\bEG\bGI\bIO\bON\bNA\bAL\bL C\bCO\bOV\bVE\bER\bRA\bAG\bGE\bE
+ S\bSP\bPL\bLA\bAT\bT!\b! generated topographic maps are 24-bit TrueColor
+ Portable PixMap (PPM) images. They may be viewed, edited,
+ or converted to other graphic formats by popular image
+ viewing applications such as x\bxv\bv, T\bTh\bhe\be G\bGI\bIM\bMP\bP, I\bIm\bma\bag\bge\beM\bMa\bag\bgi\bic\bck\bk,
+ and X\bXP\bPa\bai\bin\bnt\bt. PNG format is highly recommended for lossless
+ compressed storage of S\bSP\bPL\bLA\bAT\bT!\b! generated topographic output
+ files. I\bIm\bma\bag\bge\beM\bMa\bag\bgi\bic\bck\bk's command-line utility easily converts
+ S\bSP\bPL\bLA\bAT\bT!\b!'s PPM files to PNG format:
+
+ convert splat_map.ppm splat_map.png
+
+ Another excellent PPM to PNG command-line utility is
+ available at:
+ _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bl_\bi_\bb_\bp_\bn_\bg_\b._\bo_\br_\bg_\b/_\bp_\bu_\bb_\b/_\bp_\bn_\bg_\b/_\bb_\bo_\bo_\bk_\b/_\bs_\bo_\bu_\br_\bc_\be_\bs_\b._\bh_\bt_\bm_\bl. As a
+ last resort, PPM files may be compressed using the bzip2
+ utility, and read directly by T\bTh\bhe\be G\bGI\bIM\bMP\bP in this format.
+
+R\bRE\bEG\bGI\bIO\bON\bNA\bAL\bL C\bCO\bOV\bVE\bER\bRA\bAG\bGE\bE A\bAN\bNA\bAL\bLY\bYS\bSI\bIS\bS
S\bSP\bPL\bLA\bAT\bT!\b! can analyze a transmitter or repeater site, or net-
- work of sites, and predict the regional coverage for each
+ work of sites, and predict the regional coverage for each
site specified. In this mode, S\bSP\bPL\bLA\bAT\bT!\b! can generate a topo-
- graphic map displaying the geometric line-of-sight cover-
- age area of the sites based on the location of each site
- and the height of receive antenna wishing to communicate
+ graphic map displaying the geometric line-of-sight cover-
+ age area of the sites based on the location of each site
+ and the height of receive antenna wishing to communicate
with the site in question. S\bSP\bPL\bLA\bAT\bT!\b! switches from point-to-
- point analysis mode to area prediction mode when the _\b-_\bc
+ point analysis mode to area prediction mode when the _\b-_\bc
switch is invoked as follows:
- splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o
+ splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o
tx_coverage
In this example, S\bSP\bPL\bLA\bAT\bT!\b! generates a topographic map called
- _\bt_\bx_\b__\bc_\bo_\bv_\be_\br_\ba_\bg_\be_\b._\bp_\bp_\bm that illustrates the predicted line-of-
- sight regional coverage of _\bt_\bx_\b__\bs_\bi_\bt_\be to receiving locations
- having antennas 30.0 feet above ground level (AGL). The
- contents of _\bc_\bi_\bt_\bi_\be_\bs_\b._\bd_\ba_\bt are plotted on the map, as are the
- cartographic boundaries contained in the file
+ _\bt_\bx_\b__\bc_\bo_\bv_\be_\br_\ba_\bg_\be_\b._\bp_\bp_\bm that illustrates the predicted line-of-
+ sight regional coverage of _\bt_\bx_\b__\bs_\bi_\bt_\be to receiving locations
+ having antennas 30.0 feet above ground level (AGL). If
+ the _\b-_\bm_\be_\bt_\br_\bi_\bc switch is used, the argument following the _\b-_\bc
+ switch is interpreted as being in meters, rather than in
+ feet. The contents of _\bc_\bi_\bt_\bi_\be_\bs_\b._\bd_\ba_\bt are plotted on the map,
+ as are the cartographic boundaries contained in the file
_\bc_\bo_\b3_\b4_\b__\bd_\b0_\b0_\b._\bd_\ba_\bt.
- When plotting line-of-sight paths and areas of regional
- coverage, S\bSP\bPL\bLA\bAT\bT!\b! by default does not account for the
- effects of atmospheric bending. However, this behavior
- may be modified by using the Earth radius multiplier (_\b-_\bm)
+ When plotting line-of-sight paths and areas of regional
+ coverage, S\bSP\bPL\bLA\bAT\bT!\b! by default does not account for the
+ effects of atmospheric bending. However, this behavior
+ may be modified by using the Earth radius multiplier (_\b-_\bm)
switch:
- splat -t wnjt -c 30.0 -m 1.333 -s cities.dat -b coun-
+ splat -t wnjt -c 30.0 -m 1.333 -s cities.dat -b coun-
ties.dat -o map.ppm
- An earth radius multiplier of 1.333 instructs S\bSP\bPL\bLA\bAT\bT!\b! to
+ An earth radius multiplier of 1.333 instructs S\bSP\bPL\bLA\bAT\bT!\b! to
use the "four-thirds earth" model for line-of-sight propa-
- gation analysis. Any appropriate earth radius multiplier
+ gation analysis. Any appropriate earth radius multiplier
may be selected by the user.
- When invoked in area prediction mode, S\bSP\bPL\bLA\bAT\bT!\b! generates a
+ When invoked in area prediction mode, S\bSP\bPL\bLA\bAT\bT!\b! generates a
site report for each station analyzed. S\bSP\bPL\bLA\bAT\bT!\b! site
reports contain details of the site's geographic location,
- its height above mean sea level, the antenna's height
- above mean sea level, the antenna's height above average
- terrain, and the height of the average terrain calculated
- in the directions of 0, 45, 90, 135, 180, 225, 270, and
+ its height above mean sea level, the antenna's height
+ above mean sea level, the antenna's height above average
+ terrain, and the height of the average terrain calculated
+ in the directions of 0, 45, 90, 135, 180, 225, 270, and
315 degrees azimuth.
- If the _\b-_\bc switch is replaced by a _\b-_\bL switch, a Longley-
- Rice path loss map for a transmitter site may be gener-
- ated:
-
- splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o
- path_loss_map
-
- In this mode, S\bSP\bPL\bLA\bAT\bT!\b! generates a multi-color map illus-
- trating expected signal levels (path loss) in areas sur-
- rounding the transmitter site. A legend at the bottom of
- the map correlates each color with a specific path loss
- level in decibels. Since Longley-Rice area prediction map
- generation is very CPU intensive, provision for limiting
- the analysis range is provided by the _\b-_\bR switch. The
- argument must be given in miles. If a range wider than
- the generated topographic map is specified, S\bSP\bPL\bLA\bAT\bT!\b! will
- perform Longley-Rice path loss calculations between all
- four corners of the area prediction map.
-
- The _\b-_\bd_\bb switch allows a constraint to be placed on the
- maximum path loss region plotted on the map. A path loss
- between 80 and 230 dB may be specified using this switch.
- For example, if a path loss beyond -140 dB is irrelevant
- to the survey being conducted, S\bSP\bPL\bLA\bAT\bT!\b!'s path loss plot can
- be constrained to the region bounded by the 140 dB attenu-
- ation contour as follows:
-
- splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -db
- 140 -o plot.ppm
-
-
-D\bDE\bET\bTE\bER\bRM\bMI\bIN\bNI\bIN\bNG\bG M\bMU\bUL\bLT\bTI\bIP\bPL\bLE\bE R\bRE\bEG\bGI\bIO\bON\bNS\bS O\bOF\bF C\bCO\bOV\bVE\bER\bRA\bAG\bGE\bE
- S\bSP\bPL\bLA\bAT\bT!\b! can also display line-of-sight coverage areas for
- as many as four separate transmitter sites on a common
+D\bDE\bET\bTE\bER\bRM\bMI\bIN\bNI\bIN\bNG\bG M\bMU\bUL\bLT\bTI\bIP\bPL\bLE\bE R\bRE\bEG\bGI\bIO\bON\bNS\bS O\bOF\bF L\bLO\bOS\bS C\bCO\bOV\bVE\bER\bRA\bAG\bGE\bE
+ S\bSP\bPL\bLA\bAT\bT!\b! can also display line-of-sight coverage areas for
+ as many as four separate transmitter sites on a common
topographic map. For example:
- splat -t site1 site2 site3 site4 -c 30.0 -o network.ppm
+ splat -t site1 site2 site3 site4 -c 10.0 -metric -o net-
+ work.ppm
plots the regional line-of-sight coverage of site1, site2,
- site3, and site4 based on a receive antenna located 30.0
- feet above ground level. A topographic map is then
+ site3, and site4 based on a receive antenna located 10.0
+ meters above ground level. A topographic map is then
written to the file _\bn_\be_\bt_\bw_\bo_\br_\bk_\b._\bp_\bp_\bm. The line-of-sight cover-
age area of the transmitters are plotted as follows in the
colors indicated (along with their corresponding RGB val-
from as many as four separate locations on a single tower
may be generated by S\bSP\bPL\bLA\bAT\bT!\b!.
-T\bTO\bOP\bPO\bOG\bGR\bRA\bAP\bPH\bHI\bIC\bC M\bMA\bAP\bP G\bGE\bEN\bNE\bER\bRA\bAT\bTI\bIO\bON\bN
- In certain situations, it may be desirable to generate a
- topographic map of a region without plotting coverage
+L\bLO\bON\bNG\bGL\bLE\bEY\bY-\b-R\bRI\bIC\bCE\bE P\bPA\bAT\bTH\bH L\bLO\bOS\bSS\bS A\bAN\bNA\bAL\bLY\bYS\bSI\bIS\bS
+ If the _\b-_\bc switch is replaced by a _\b-_\bL switch, a Longley-
+ Rice path loss map for a transmitter site may be gener-
+ ated:
+
+ splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o
+ path_loss_map
+
+ In this mode, S\bSP\bPL\bLA\bAT\bT!\b! generates a multi-color map illus-
+ trating expected signal levels (path loss) in areas sur-
+ rounding the transmitter site. A legend at the bottom of
+ the map correlates each color with a specific path loss
+ range in decibels.
+
+ The Longley-Rice analysis range may be modified to a user-
+ specific value using the _\b-_\bR switch. The argument must be
+ given in miles (or kilometers if the _\b-_\bm_\be_\bt_\br_\bi_\bc switch is
+ used). If a range wider than the generated topographic
+ map is specified, S\bSP\bPL\bLA\bAT\bT!\b! will perform Longley-Rice path
+ loss calculations between all four corners of the area
+ prediction map.
+
+ The _\b-_\bd_\bb switch allows a constraint to be placed on the
+ maximum path loss region plotted on the map. A maximum
+ path loss between 80 and 230 dB may be specified using
+ this switch. For example, if a path loss beyond -140 dB
+ is irrelevant to the survey being conducted, S\bSP\bPL\bLA\bAT\bT!\b!'s path
+ loss plot can be constrained to the region bounded by the
+ 140 dB attenuation contour as follows:
+
+ splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -db
+ 140 -o plot.ppm
+
+
+A\bAN\bNT\bTE\bEN\bNN\bNA\bA R\bRA\bAD\bDI\bIA\bAT\bTI\bIO\bON\bN P\bPA\bAT\bTT\bTE\bER\bRN\bN P\bPA\bAR\bRA\bAM\bME\bET\bTE\bER\bRS\bS
+ Normalized field voltage patterns for a transmitting
+ antenna's horizontal and vertical planes are imported
+ automatically into S\bSP\bPL\bLA\bAT\bT!\b! when a Longley-Rice coverage
+ analysis is performed. Antenna pattern data is read from
+ a pair of files having the same base name as the transmit-
+ ter and LRP files, but with _\b._\ba_\bz and _\b._\be_\bl extensions for
+ azimuth and elevation pattern files, respectively. Speci-
+ fications regarding pattern rotation (if any) and
+ mechanical beam tilt and tilt direction (if any) are also
+ contained within S\bSP\bPL\bLA\bAT\bT!\b! antenna pattern files.
+
+ For example, the first few lines of a S\bSP\bPL\bLA\bAT\bT!\b! azimuth pat-
+ tern file might appear as follows (_\bk_\bv_\be_\ba_\b._\ba_\bz):
+
+ 183.0
+ 0 0.8950590
+ 1 0.8966406
+ 2 0.8981447
+ 3 0.8995795
+ 4 0.9009535
+ 5 0.9022749
+ 6 0.9035517
+ 7 0.9047923
+ 8 0.9060051
+
+ The first line of the _\b._\ba_\bz file specifies the amount of
+ azimuthal pattern rotation (measured clockwise in degrees
+ from True North) to be applied by S\bSP\bPL\bLA\bAT\bT!\b! to the data con-
+ tained in the _\b._\ba_\bz file. This is followed by azimuth head-
+ ings (0 to 360 degrees) and their associated normalized
+ field patterns (0.000 to 1.000) separated by whitespace.
+
+ The structure of S\bSP\bPL\bLA\bAT\bT!\b! elevation pattern files is
+ slightly different. The first line of the _\b._\be_\bl file speci-
+ fies the amount of mechanical beam tilt applied to the
+ antenna. Note that a _\bd_\bo_\bw_\bn_\bw_\ba_\br_\bd _\bt_\bi_\bl_\bt (below the horizon) is
+ expressed as a _\bp_\bo_\bs_\bi_\bt_\bi_\bv_\be _\ba_\bn_\bg_\bl_\be, while an _\bu_\bp_\bw_\ba_\br_\bd _\bt_\bi_\bl_\bt (above
+ the horizon) is expressed as a _\bn_\be_\bg_\ba_\bt_\bi_\bv_\be _\ba_\bn_\bg_\bl_\be. This data
+ is followed by the azimuthal direction of the tilt, sepa-
+ rated by whitespace.
+
+ The remainder of the file consists of elevation angles and
+ their corresponding normalized voltage radiation pattern
+ (0.000 to 1.000) values separated by whitespace. Eleva-
+ tion angles must be specified over a -10.0 to +90.0 degree
+ range. As was the convention with mechanical beamtilt,
+ _\bn_\be_\bg_\ba_\bt_\bi_\bv_\be _\be_\bl_\be_\bv_\ba_\bt_\bi_\bo_\bn _\ba_\bn_\bg_\bl_\be_\bs are used to represent elevations
+ _\ba_\bb_\bo_\bv_\be _\bt_\bh_\be _\bh_\bo_\br_\bi_\bz_\bo_\bn, while _\bp_\bo_\bs_\bi_\bt_\bi_\bv_\be _\ba_\bn_\bg_\bl_\be_\bs represents eleva-
+ tions _\bb_\be_\bl_\bo_\bw _\bt_\bh_\be _\bh_\bo_\br_\bi_\bz_\bo_\bn.
+
+ For example, the first few lines a S\bSP\bPL\bLA\bAT\bT!\b! elevation pat-
+ tern file might appear as follows (_\bk_\bv_\be_\ba_\b._\be_\bl):
+
+ 1.1 130.0
+ -10.0 0.172
+ -9.5 0.109
+ -9.0 0.115
+ -8.5 0.155
+ -8.0 0.157
+ -7.5 0.104
+ -7.0 0.029
+ -6.5 0.109
+ -6.0 0.185
+
+ In this example, the antenna is mechanically tilted down-
+ ward 1.1 degrees towards an azimuth of 130.0 degrees.
+
+ For best results, the resolution of azimuth pattern data
+ should be specified to the nearest degree azimuth, and
+ elevation pattern data resolution should be specified to
+ the nearest 0.01 degrees. If the pattern data specified
+ does not reach this level of resolution, S\bSP\bPL\bLA\bAT\bT!\b! will
+ interpolate the values provided to determine the data at
+ the required resolution, although this may result in a
+ loss in accuracy.
+
+
+I\bIM\bMP\bPO\bOR\bRT\bTI\bIN\bNG\bG A\bAN\bND\bD E\bEX\bXP\bPO\bOR\bRT\bTI\bIN\bNG\bG R\bRE\bEG\bGI\bIO\bON\bNA\bAL\bL P\bPA\bAT\bTH\bH L\bLO\bOS\bSS\bS C\bCO\bON\bNT\bTO\bOU\bUR\bR D\bDA\bAT\bTA\bA
+ Performing a Longley-Rice coverage analysis can be a very
+ time consuming process, especially if the analysis is
+ repeated repeatedly to discover what effects changes to
+ the antenna radiation patterns make to the predicted cov-
+ erage area.
+
+ This process can be expedited by exporting the Longley-
+ Rice regional path loss contour data to an output file,
+ modifying the path loss data externally to incorporate
+ antenna pattern effects, and then importing the modified
+ path loss data back into S\bSP\bPL\bLA\bAT\bT!\b! to rapidly produce a
+ revised path loss map.
+
+ For example, a path loss output file can be generated by
+ S\bSP\bPL\bLA\bAT\bT!\b! for a receive site 30 feet above ground level over
+ a 50 mile radius surrounding a transmitter site to a maxi-
+ mum path loss of 140 dB using the following syntax:
+
+ splat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat
+
+ S\bSP\bPL\bLA\bAT\bT!\b! path loss output files often exceed 100 megabytes
+ in size. They contain information relating to the bound-
+ aries of region they describe followed by latitudes
+ (degrees North), longitudes (degrees West), azimuths, ele-
+ vations (to the first obstruction), and path loss figures
+ (dB) for a series of specific points that comprise the
+ region surrounding the transmitter site. The first few
+ lines of a S\bSP\bPL\bLA\bAT\bT!\b! path loss output file take on the fol-
+ lowing appearance (_\bp_\ba_\bt_\bh_\bl_\bo_\bs_\bs_\b._\bd_\ba_\bt):
+
+ 119, 117 ; max_west, min_west
+ 35, 33 ; max_north, min_north
+ 34.2265434, 118.0631104, 48.171, -37.461, 67.70
+ 34.2270355, 118.0624390, 48.262, -26.212, 73.72
+ 34.2280197, 118.0611038, 48.269, -14.951, 79.74
+ 34.2285156, 118.0604401, 48.207, -11.351, 81.68
+ 34.2290077, 118.0597687, 48.240, -10.518, 83.26
+ 34.2294998, 118.0591049, 48.225, 23.201, 84.60
+ 34.2304878, 118.0577698, 48.213, 15.769, 137.84
+ 34.2309799, 118.0570984, 48.234, 15.965, 151.54
+ 34.2314720, 118.0564346, 48.224, 16.520, 149.45
+ 34.2319679, 118.0557632, 48.223, 15.588, 151.61
+ 34.2329521, 118.0544281, 48.230, 13.889, 135.45
+ 34.2334442, 118.0537643, 48.223, 11.693, 137.37
+ 34.2339401, 118.0530930, 48.222, 14.050, 126.32
+ 34.2344322, 118.0524292, 48.216, 16.274, 156.28
+ 34.2354164, 118.0510941, 48.222, 15.058, 152.65
+ 34.2359123, 118.0504227, 48.221, 16.215, 158.57
+ 34.2364044, 118.0497589, 48.216, 15.024, 157.30
+ 34.2368965, 118.0490875, 48.225, 17.184, 156.36
+
+ It is not uncommon for S\bSP\bPL\bLA\bAT\bT!\b! path loss files to contain
+ as many as 3 million or more lines of data. Comments can
+ be placed in the file if they are proceeded by a semicolon
+ character. The v\bvi\bim\bm text editor has proven capable of
+ editing files of this size.
+
+ Note as was the case in the antenna pattern files, nega-
+ tive elevation angles refer to upward tilt (above the
+ horizon), while positive angles refer to downward tilt
+ (below the horizon). These angles refer to the elevation
+ to the receiving antenna at the height above ground level
+ specified using the _\b-_\bL switch _\bi_\bf the path between trans-
+ mitter and receiver is unobstructed. If the path between
+ the transmitter and receiver is obstructed, then the ele-
+ vation angle to the first obstruction is returned by
+ S\bSP\bPL\bLA\bAT\bT!\b!. This is because the Longley-Rice model considers
+ the energy reaching a distant point over an obstructed
+ path as a derivative of the energy scattered from the top
+ of the first obstruction, only. Since energy cannot reach
+ the obstructed location directly, the actual elevation
+ angle to that point is irrelevant.
+
+ When modifying S\bSP\bPL\bLA\bAT\bT!\b! path loss files to reflect antenna
+ pattern data, _\bo_\bn_\bl_\by _\bt_\bh_\be _\bl_\ba_\bs_\bt _\bc_\bo_\bl_\bu_\bm_\bn _\b(_\bp_\ba_\bt_\bh _\bl_\bo_\bs_\bs_\b) should be
+ amended to reflect the antenna's normalized gain at the
+ azimuth and elevation angles specified in the file. (At
+ this time, programs and scripts capable of performing this
+ operation are left as an exercise for the user.)
+
+ Modified path loss maps can be imported back into S\bSP\bPL\bLA\bAT\bT!\b!
+ for generating revised coverage maps:
+
+ splat -t kvea -pli pathloss.dat -s city.dat -b county.dat
+ -o map.ppm
+
+ S\bSP\bPL\bLA\bAT\bT!\b! path loss files can also be used for conducting
+ coverage or interference studies outside of S\bSP\bPL\bLA\bAT\bT!\b!.
+
+U\bUS\bSE\bER\bR-\b-D\bDE\bEF\bFI\bIN\bNE\bED\bD T\bTE\bER\bRR\bRA\bAI\bIN\bN I\bIN\bNP\bPU\bUT\bT F\bFI\bIL\bLE\bES\bS
+ A user-defined terrain file is a user-generated text file
+ containing latitudes, longitudes, and heights above ground
+ level of specific terrain features believed to be of
+ importance to the S\bSP\bPL\bLA\bAT\bT!\b! analysis being conducted, but
+ noticeably absent from the SDF files being used. A user-
+ defined terrain file is imported into a S\bSP\bPL\bLA\bAT\bT!\b! analysis
+ using the _\b-_\bu_\bd_\bt switch:
+
+ splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm
+
+ A user-defined terrain file has the following appearance
+ and structure:
+
+ 40.32180556, 74.1325, 100.0 meters
+ 40.321805, 74.1315, 300.0
+ 40.3218055, 74.1305, 100.0 meters
+
+ Terrain height is interpreted as being described in feet
+ above ground level unless followed by the word _\bm_\be_\bt_\be_\br_\bs, and
+ is added _\bo_\bn _\bt_\bo_\bp _\bo_\bf the terrain specified in the SDF data
+ for the locations specified. Be aware that each user-
+ defined terrain feature specified will be interpreted as
+ being 3-arc seconds in both latitude and longitude. Fea-
+ tures described in the user-defined terrain file that
+ overlap previously defined features in the file are
+ ignored by S\bSP\bPL\bLA\bAT\bT!\b!.
+
+S\bSI\bIM\bMP\bPL\bLE\bE T\bTO\bOP\bPO\bOG\bGR\bRA\bAP\bPH\bHI\bIC\bC M\bMA\bAP\bP G\bGE\bEN\bNE\bER\bRA\bAT\bTI\bIO\bON\bN
+ In certain situations it may be desirable to generate a
+ topographic map of a region without plotting coverage
areas, line-of-sight paths, or generating obstruction
- reports. There are several ways of doing this. If one
- wishes to generate a topographic map illustrating the
- location of a transmitter and receiver site along with a
- brief text report describing the locations and distances
+ reports. There are several ways of doing this. If one
+ wishes to generate a topographic map illustrating the
+ location of a transmitter and receiver site along with a
+ brief text report describing the locations and distances
between the sites, the _\b-_\bn switch should be invoked as fol-
lows:
splat -t tx_site -r rx_site -N -o topo_map.ppm
- If the _\b-_\bo switch and output filename are omitted when
- using either the _\b-_\bn or _\b-_\bN switches, output is written to a
- file named _\bm_\ba_\bp_\b._\bp_\bp_\bm in the current working directory by
- default.
+ If a topographic map centered about a single site out to a
+ minimum specified radius is desired instead, a command
+ similar to the following can be used:
+
+ splat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o
+ topo_map.ppm
+
+ where -R specifies the minimum radius of the map in miles
+ (or kilometers if the _\b-_\bm_\be_\bt_\br_\bi_\bc switch is used).
+
+ If the _\b-_\bo switch and output filename are omitted in these
+ operations, topographic output is written to a file named
+ _\bm_\ba_\bp_\b._\bp_\bp_\bm in the current working directory by default.
+
+G\bGE\bEO\bOR\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE F\bFI\bIL\bLE\bE G\bGE\bEN\bNE\bER\bRA\bAT\bTI\bIO\bON\bN
+ Topographic, coverage (_\b-_\bc), and path loss contour (_\b-_\bL)
+ maps generated by S\bSP\bPL\bLA\bAT\bT!\b! may be imported into X\bXa\bas\bst\bti\bir\br (X
+ Amateur Station Tracking and Information Reporting) soft-
+ ware by generating a georeference file using S\bSP\bPL\bLA\bAT\bT!\b!'s _\b-_\bg_\be_\bo
+ switch:
+
+ splat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o
+ map.ppm
+
+ The georeference file generated will have the same base
+ name as the _\b-_\bo file specified, but have a _\b._\bg_\be_\bo extension,
+ and permit proper interpretation and display of S\bSP\bPL\bLA\bAT\bT!\b!'s
+ .ppm graphics in X\bXa\bas\bst\bti\bir\br software.
+
+G\bGO\bOO\bOG\bGL\bLE\bE M\bMA\bAP\bP K\bKM\bML\bL F\bFI\bIL\bLE\bE G\bGE\bEN\bNE\bER\bRA\bAT\bTI\bIO\bON\bN
+ Keyhole Markup Language files compatible with G\bGo\boo\bog\bgl\ble\be E\bEa\bar\brt\bth\bh
+ may be generated by S\bSP\bPL\bLA\bAT\bT!\b! when performing point-to-point
+ analyses by invoking the _\b-_\bk_\bm_\bl switch:
+
+ splat -t wnjt -r kd2bd -kml
+
+ The KML file generated will have the same filename struc-
+ ture as an Obstruction Report for the transmitter and
+ receiver site names given, except it will carry a _\b._\bk_\bm_\bl
+ extension.
+
+ Once loaded into G\bGo\boo\bog\bgl\ble\be E\bEa\bar\brt\bth\bh (File --> Open), the KML
+ file will annotate the map display with the names of the
+ transmitter and receiver site locations. The viewpoint of
+ the image will be from the position of the transmitter
+ site looking towards the location of the receiver. The
+ point-to-point path between the sites will be displayed as
+ a white line while the RF line-of-sight path will be dis-
+ played in green. G\bGo\boo\bog\bgl\ble\be E\bEa\bar\brt\bth\bh's navigation tools allow
+ the user to "fly" around the path, identify landmarks,
+ roads, and other featured content.
D\bDE\bET\bTE\bER\bRM\bMI\bIN\bNA\bAT\bTI\bIO\bON\bN O\bOF\bF A\bAN\bNT\bTE\bEN\bNN\bNA\bA H\bHE\bEI\bIG\bGH\bHT\bT A\bAB\bBO\bOV\bVE\bE A\bAV\bVE\bER\bRA\bAG\bGE\bE T\bTE\bER\bRR\bRA\bAI\bIN\bN
S\bSP\bPL\bLA\bAT\bT!\b! determines antenna height above average terrain
lie entirely over water or over land outside the United
States (areas for which no USGS topography data is avail-
able), then those radials are omitted from the calculation
- of average terrain. If part of a radial extends over a
- body of water or over land outside the United States, then
- only that part of the radial lying over United States land
- is used in the determination of average terrain.
-
- Note that SRTM elevation data, unlike older 3-arc second
- USGS data, extends beyond the borders of the United
- States. Therefore, HAAT results may not be in full com-
+ of average terrain.
+
+ Note that SRTM elevation data, unlike older 3-arc second
+ USGS data, extends beyond the borders of the United
+ States. Therefore, HAAT results may not be in full com-
pliance with FCC Part 73.313(d) in areas along the borders
- of the United States if the SDF files used by S\bSP\bPL\bLA\bAT\bT!\b! are
+ of the United States if the SDF files used by S\bSP\bPL\bLA\bAT\bT!\b! are
SRTM-derived.
- When performing point-to-point terrain analysis, S\bSP\bPL\bLA\bAT\bT!\b!
- determines the antenna height above average terrain only
- if enough topographic data has already been loaded by the
- program to perform the point-to-point analysis. In most
+ When performing point-to-point terrain analysis, S\bSP\bPL\bLA\bAT\bT!\b!
+ determines the antenna height above average terrain only
+ if enough topographic data has already been loaded by the
+ program to perform the point-to-point analysis. In most
cases, this will be true, unless the site in question does
- not lie within 10 miles of the boundary of the topography
+ not lie within 10 miles of the boundary of the topography
data in memory.
- When performing area prediction analysis, enough topogra-
- phy data is normally loaded by S\bSP\bPL\bLA\bAT\bT!\b! to perform average
- terrain calculations. Under such conditions, S\bSP\bPL\bLA\bAT\bT!\b! will
- provide the antenna height above average terrain as well
- as the average terrain above mean sea level for azimuths
- of 0, 45, 90, 135, 180, 225, 270, and 315 degrees, and
- include such information in the site report generated. If
+ When performing area prediction analysis, enough topogra-
+ phy data is normally loaded by S\bSP\bPL\bLA\bAT\bT!\b! to perform average
+ terrain calculations. Under such conditions, S\bSP\bPL\bLA\bAT\bT!\b! will
+ provide the antenna height above average terrain as well
+ as the average terrain above mean sea level for azimuths
+ of 0, 45, 90, 135, 180, 225, 270, and 315 degrees, and
+ include such information in the generated site report. If
one or more of the eight radials surveyed fall over water,
or over regions for which no SDF data is available, S\bSP\bPL\bLA\bAT\bT!\b!
reports _\bN_\bo _\bT_\be_\br_\br_\ba_\bi_\bn for the radial paths affected.
R\bRE\bES\bST\bTR\bRI\bIC\bCT\bTI\bIN\bNG\bG T\bTH\bHE\bE M\bMA\bAX\bXI\bIM\bMU\bUM\bM S\bSI\bIZ\bZE\bE O\bOF\bF A\bAN\bN A\bAN\bNA\bAL\bLY\bYS\bSI\bIS\bS R\bRE\bEG\bGI\bIO\bON\bN
- S\bSP\bPL\bLA\bAT\bT!\b! reads SDF files as needed into a series of memory
- "slots" within the structure of the program. Each "slot"
- holds one SDF file representing a one degree by one degree
- region of terrain. A _\b#_\bd_\be_\bf_\bi_\bn_\be _\bM_\bA_\bX_\bS_\bL_\bO_\bT_\bS statement in the
- first several lines of _\bs_\bp_\bl_\ba_\bt_\b._\bc_\bp_\bp sets the maximum number
- of "slots" available for topography data. It also sets
- the maximum size of the topographic maps generated by
- S\bSP\bPL\bLA\bAT\bT!\b!. MAXSLOTS is set to 9 by default. If S\bSP\bPL\bLA\bAT\bT!\b! pro-
- duces a segmentation fault on start-up with this default,
- it is an indication that not enough RAM and/or virtual
- memory (swap space) is available to run S\bSP\bPL\bLA\bAT\bT!\b! with this
- number of MAXSLOTS. In situations where available memory
- is low, MAXSLOTS may be reduced to 4 with the understand-
- ing that this will greatly limit the maximum region S\bSP\bPL\bLA\bAT\bT!\b!
- will be able to analyze. If 118 megabytes or more of
- total memory (swap space plus RAM) is available, then
- MAXSLOTS may be increased to 16. This will permit opera-
- tion over a 4-degree by 4-degree region, which is suffi-
- cient for single antenna heights in excess of 10,000 feet
- above mean sea level, or point-to-point distances of over
- 1000 miles.
+ S\bSP\bPL\bLA\bAT\bT!\b! reads SDF files as needed into a series of memory
+ pages or "slots" within the structure of the program.
+ Each "slot" holds one SDF file representing a one degree
+ by one degree region of terrain. A _\b#_\bd_\be_\bf_\bi_\bn_\be _\bM_\bA_\bX_\bS_\bL_\bO_\bT_\bS
+ statement in the first several lines of _\bs_\bp_\bl_\ba_\bt_\b._\bc_\bp_\bp sets the
+ maximum number of "slots" available for holding topography
+ data. It also sets the maximum size of the topographic
+ maps generated by S\bSP\bPL\bLA\bAT\bT!\b!. MAXSLOTS is set to 9 by
+ default. If S\bSP\bPL\bLA\bAT\bT!\b! produces a segmentation fault on
+ start-up with this default, it is an indication that not
+ enough RAM and/or virtual memory (swap space) is available
+ to run S\bSP\bPL\bLA\bAT\bT!\b! with the number of MAXSLOTS specified. In
+ situations where available memory is low, MAXSLOTS may be
+ reduced to 4 with the understanding that this will greatly
+ limit the maximum region S\bSP\bPL\bLA\bAT\bT!\b! will be able to analyze.
+ If 118 megabytes or more of total memory (swap space plus
+ RAM) is available, then MAXSLOTS may be increased to 16.
+ This will permit operation over a 4-degree by 4-degree
+ region, which is sufficient for single antenna heights in
+ excess of 10,000 feet above mean sea level, or point-to-
+ point distances of over 1000 miles.
A\bAD\bDD\bDI\bIT\bTI\bIO\bON\bNA\bAL\bL I\bIN\bNF\bFO\bOR\bRM\bMA\bAT\bTI\bIO\bON\bN
- Invoking S\bSP\bPL\bLA\bAT\bT!\b! without any arguments will display all the
- command-line options available with the program along with
- a brief summary of each.
-
- The latest news and information regarding S\bSP\bPL\bLA\bAT\bT!\b! software
+ The latest news and information regarding S\bSP\bPL\bLA\bAT\bT!\b! software
is available through the official S\bSP\bPL\bLA\bAT\bT!\b! software web page
located at: _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bq_\bs_\bl_\b._\bn_\be_\bt_\b/_\bk_\bd_\b2_\bb_\bd_\b/_\bs_\bp_\bl_\ba_\bt_\b._\bh_\bt_\bm_\bl.
Doug McDonald <_\bm_\bc_\bd_\bo_\bn_\ba_\bl_\bd_\b@_\bs_\bc_\bs_\b._\bu_\bi_\bu_\bc_\b._\be_\bd_\bu>
Longley-Rice Model integration
+ Ron Bentley <_\br_\bo_\bn_\bb_\be_\bn_\bt_\bl_\be_\by_\b@_\be_\ba_\br_\bt_\bh_\bl_\bi_\bn_\bk_\b._\bn_\be_\bt>
+ Fresnel Zone plotting and clearance determination
+
+
+KD2BD Software 20 December 2006 SPLAT!(1)
projects / debian / splat / blobdiff