-Release 1.2.0b:
-By John A. Magliacane, <kd2bd@amsat.org> (15-Mar-2007):
+Release 1.2.1:
+By John A. Magliacane <kd2bd@amsat.org> (18-Oct-07):
+
+* SPLAT! now imports transmitter effective radiated power information and
+ predicts received field strength signal levels (dBuV/m) and antenna
+ voltage based on the transmitter's antenna pattern, computed path loss,
+ and ERP. ERP information is specified on the ninth line of SPLAT! .lrp
+ files.
+
+* The ability to plot signal strength contour maps has been added. The
+ color schemes for plotting signal strength and path loss contour maps
+ can now be customized by editing the contents of .scf and .lcf files
+ for each transmitter site. In addition, both signal strength and path
+ loss contour maps can now be generated for multiple transmitter sites,
+ with the greatest signal strength (or least path loss) illustrated in
+ overlapping regions between sites.
+
+* A new -ngs switch assigns all topography to the color white in .ppm
+ contour maps. The white background can be made transparent using
+ simple graphics utilities for merging SPLAT! contour maps with other
+ Mercator projection maps and graphics files of equivalent size and
+ resolution.
+
+* Path loss and signal strength contour regions can now be exported to
+ Google Earth as a semi-transparent ground overlay using the -kml switch.
+
+* The default contour map filename now defaults to the basename of the
+ transmitter site .qth file (or first transmitter site within a network)
+ with a .ppm extension (rather than "map.ppm").
+
+* The Fresnel zone clearance percentage, which was fixed at 60% in the
+ past, is now user-definable using the new -fz command-line option.
+
+* Information previously contained in SPLAT! Obstruction Reports has now
+ been merged with Longley-Rice path loss information into a single Path
+ Analysis report (with a .txt extension). (Longley-Rice output (.lro)
+ files are no longer generated.)
+
+* Graph plotting (the -l option) no longer needs to be forced to perform
+ a Longley-Rice path analysis in point-to-point mode. If a .lrp file is
+ available and contains the information needed, Longley-Rice path loss
+ information will be automatically included in SPLAT!'s Path Analysis
+ Report when performing a point-to-point analysis.
+
+* In addition to information previously contained, SPLAT! Path Loss Output
+ (-plo) files now contain additional information including path loss
+ considering the effects of the transmitting antenna's radiation pattern
+ (if pattern data is available), and field strength values (dBuV/m)
+ based on pattern data and ERP data (if available). An asterisk at
+ the end of each line indicates the path to the point referenced in
+ the file is obstructed by terrain.
+
+* The srtm2sdf utility now handles 3-arc second SRTM in .BIL (Band
+ Interleaved by Line) format, as well as the usual .HGT format.
+
+* SPLAT!'s associated itm.cpp file was updated to include the latest
+ public domain ITM code released on June 26, 2007.
+
+* References in source code and documentation to "slots" and "MAXSLOTS"
+ have been changed to "pages" and "MAXPAGES", respectively.
* Two bugs affecting the plotting of Fresnel zones were identified and fixed.
* Text documentation in Spanish was added (thanks to Charles Esobar).
+* The build scripts were modified to permit successful compilation with
+ bzip2-1.0.4 libraries. (Thanks to Janek, SQ5MJL)
+
----------------------------------------------------------------------------
Release 1.2.0:
* Support for user-defined terrain files (ground clutter) has been
added.
-* SPLAT! can now generate .geo Georeference Information Files
+* SPLAT! can now generate .geo Geo-reference Information Files
when .ppm topography and coverage maps are created, permitting
the integration of SPLAT! generated maps with X Amateur Station
Tracking and Information Reporting (www.xastir.org) software.
by John A. Magliacane <kd2bd@amsat.org> (08-Apr-2002):
* First public release of SPLAT!
+
============
SPLAT! requires the libbzip2-1.0.1 (or later) compression library and
header files for successful compilation. bzip2/libbzip2 is available
-at: http://www.bzip.org/
+at: http://sources.redhat.com/bzip2/
SPLAT! also requires the zlib general purpose compression library.
Any recent version included with your Linux distribution should work
You will also need an application for viewing large PPM graphics
files generated by SPLAT!. XV, ImageMagick, XPaint, and The GIMP
-all perform this task well, especially The GIMP.
+all perform this task well (especially The GIMP).
It goes without saying that a C++ compiler (gcc/g++) and math libraries
are also needed to build SPLAT! SPLAT! is fully compatible with the
under Slackware) as 'root':
cd /usr/src
- tar xvfz splat-1.2.0a.tar.gz
+ tar xvfz splat-1.2.1.tar.gz
-This action will generate a subdirectory named splat-1.2.0a.
+This action will generate a subdirectory named splat-1.2.1.
Next, cd into the directory:
- cd splat-1.2.0a
+ cd splat-1.2.1
Invoke the configure script to build SPLAT! and related utilities:
exit
Before running SPLAT!, carefully read the documentation located under
-the splat-1.2.0a/docs directory for information on the use of the program.
+the splat-1.2.1/docs directory for information on the use of the program.
+Some sample data files are located under the splat-1.2.1/sample_data
+directory.
REMEMBER: Topography data must be downloaded and SPLAT Data Files must
be generated using the included srtm2sdf, postdownload, or usgs2sdf
Please read the README file under the utils directory for information
on the utilities included with SPLAT!.
-Please read the documentation under the splat-1.2.0a/docs directory,
+Please read the documentation under the splat-1.2.1/docs directory,
or consult the program's man page for more information and examples
of SPLAT! use.
--
John A. Magliacane, KD2BD
-January 2007
-
+September, 2007
#!/bin/bash
#
# Simple shell script for building SPLAT! and associated utilities.
-# Written by John A. Magliacane, KD2BD May 2002 -- Last update: March 2006
+# Written by John A. Magliacane, KD2BD May 2002 -- Last update: October 2007
#
build_splat()
{
echo -n "Compiling SPLAT!... "
- g++ -Wall -O3 -lm -lbz2 -fomit-frame-pointer itm.cpp splat.cpp -o splat
+ g++ -Wall -O3 -fomit-frame-pointer -ffast-math itm.cpp splat.cpp -lm -lbz2 -o splat
echo "Done!"
}
echo "Usage: build { splat, utils, all }"
fi
fi
-
# Simple script to create a clean distribution
#
rm -f splat utils/fontdata utils/citydecoder utils/usgs2sdf utils/srtm2sdf
-cd docs/man
+cd docs/english/man
./docmaker
-cd ../../
+cd ../../spanish/man
+./docmaker 2> /dev/null
+cd ../../../
+splat (1.2.1-1) unstable; urgency=low
+
+ * new upstream version, closes: #450861
+ * fix problem building multiple times, closes: #442735
+
+ -- Bdale Garbee <bdale@gag.com> Sun, 11 Nov 2007 23:30:47 -0800
+
splat (1.2.0b-1) unstable; urgency=low
* new upstream version
clean:
dh_testdir
dh_testroot
- rm -f build-stamp
- rm -f splat utils/fontdata utils/citydecoder utils/usgs2sdf
+ rm -f build-stamp splat
+ rm -f utils/srtm2sdf utils/fontdata utils/citydecoder utils/usgs2sdf
dh_clean
install: build
cp utils/usgs2sdf $(CURDIR)/debian/splat/usr/bin
cp utils/srtm2sdf $(CURDIR)/debian/splat/usr/bin
cp utils/fontdata $(CURDIR)/debian/splat/usr/bin
- cp docs/man/splat.man $(CURDIR)/debian/splat/usr/share/man/man1/splat.1
+ cp docs/english/man/splat.man \
+ $(CURDIR)/debian/splat/usr/share/man/man1/splat.1
# Build architecture-independent files here.
binary-indep: build install
--- /dev/null
+#!/bin/bash
+# This script builds the man page, pdf, and postscript
+# and text documentation from the groff source "splat.man".
+echo -n "Creating postscript file... "
+groff -e -T ps -man splat.man > ../postscript/splat.ps
+echo
+echo -n "Creating man page... "
+groff -e -T ascii -man splat.man > splat.1
+echo
+echo -n "Creating text file... "
+ul -t dumb splat.1 > ../text/splat.txt
+echo
+echo -n "Creating pdf file... "
+ps2pdf ../postscript/splat.ps ../pdf/splat.pdf
+echo
+echo "Done!"
--- /dev/null
+SPLAT!(1) KD2BD Software SPLAT!(1)
+
+
+
+N\bNA\bAM\bME\bE
+ splat - An RF S\bSignal P\bPropagation, L\bLoss, A\bAnd T\bTerrain analy-
+ 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 _\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)] [-fz _\bF_\br_\be_\bs_\b-
+ _\bn_\be_\bl _\bz_\bo_\bn_\be _\bc_\bl_\be_\ba_\br_\ba_\bn_\bc_\be _\bp_\be_\br_\bc_\be_\bn_\bt_\ba_\bg_\be _\b(_\bd_\be_\bf_\ba_\bu_\bl_\bt _\b= _\b6_\b0_\b)] [-plo
+ _\bp_\ba_\bt_\bh_\b__\bl_\bo_\bs_\bs_\b__\bo_\bu_\bt_\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] [-nf]
+ [-ngs] [-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 for the spectrum between 20 MHz and 20
+ GHz. S\bSP\bPL\bLA\bAT\bT!\b! is free software, and is designed for opera-
+ tion on Unix and Linux-based workstations. Redistribution
+ and/or modification is permitted under the terms of the
+ GNU General Public License, Version 2, as published by the
+ Free Software Foundation. Adoption of S\bSP\bPL\bLA\bAT\bT!\b! source code
+ in proprietary or closed-source applications is a viola-
+ tion 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
+ (WANs), commercial and amateur radio communication systems
+ above 20 MHz, microwave links, frequency coordination and
+ interference studies, and the prediction 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, distances, and elevations to
+ known obstructions, Longley-Rice path attenuation, and
+ received signal strength. In addition, the minimum
+ antenna height requirements needed to clear terrain, the
+ first Fresnel zone, and any user-definable percentage 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 and signal strength contours through which
+ expected coverage areas of transmitters and repeater sys-
+ tems can be obtained. When performing line-of-sight and
+ Longley-Rice analyses in situations where multiple trans-
+ mitter 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.1 Available Options...
+ ]==--
+
+ -t txsite(s).qth (max of 4 with -c, max of 30 with
+ -L)
+ -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 (5 max)
+ -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)
+ -m earth radius multiplier
+ -n do not plot LOS paths in .ppm maps
+ -N do not produce unnecessary site or obstruction
+ reports
+ -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
+ -fz Fresnel zone clearance percentage (default = 60)
+ -ngs display greyscale topography as white in .ppm
+ files
+ -erp override ERP in .lrp file (Watts)
+ -pli filename of path-loss input file
+ -plo filename of path-loss output file
+ -udt filename of user defined terrain input file
+ -kml generate Google Earth (.kml) compatible output
+ -geo generate an Xastir .geo georeference file (with
+ .ppm output) -metric employ metric rather than imperial
+ units for all user I/O
+
+
+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 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, antenna
+ radiation pattern files, and color definition 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
+ Files (SDFs). These files may be generated from a number
+ of information sources. In the United States, SPLAT Data
+ Files can be generated through U.S. Geological Survey
+ Digital Elevation Models (DEMs) using the u\bus\bsg\bgs\bs2\b2s\bsd\bdf\bf utility
+ included with S\bSP\bPL\bLA\bAT\bT!\b!. USGS Digital Elevation Models com-
+ 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 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/
+
+ The s\bst\btr\brm\bm2\b2s\bsd\bdf\bf utility may also be used to convert 3-arc
+ second SRTM data in Band Interleaved by Line (.BIL) format
+ for use with S\bSP\bPL\bLA\bAT\bT!\b!. This data is available via the web
+ at: _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bs_\be_\ba_\bm_\bl_\be_\bs_\bs_\b._\bu_\bs_\bg_\bs_\b._\bg_\bo_\bv_\b/_\bw_\be_\bb_\bs_\bi_\bt_\be_\b/_\bs_\be_\ba_\bm_\bl_\be_\bs_\bs_\b/
+
+ Band Interleaved by Line data must be downloaded in a very
+ specific manner to be compatible with s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf and S\bSP\bPL\bLA\bAT\bT!\b!.
+ Please consult s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf's documentation for instructions
+ on downloading .BIL topographic data through the USGS's
+ Seamless Web Site.
+
+ 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,
+ or direct replacement.
+
+ 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 read 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 com-
+ pressed 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.
+ 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
+ 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, or degrees East 0 to -360
+ degrees), and the site's antenna height above ground level
+ (AGL), each separated by a single 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 infor-
+ mation may be expressed in either decimal format (74.6864)
+ or degree, minute, second (DMS) format (74 41 11.0).
+
+ For example, a site location file describing television
+ station WNJT-DT, Trenton, NJ (_\bw_\bn_\bj_\bt_\b-_\bd_\bt_\b._\bq_\bt_\bh) might read as
+ follows:
+
+ WNJT-DT
+ 40.2828
+ 74.6864
+ 990.00
+
+ Each transmitter and receiver site analyzed by S\bSP\bPL\bLA\bAT\bT!\b! must
+ 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
+ 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-_\bd_\bt_\b._\bl_\br_\bp):
+
+ 15.000 ; Earth Dielectric Constant (Relative per-
+ mittivity)
+ 0.005 ; Earth Conductivity (Siemens per meter)
+ 301.000 ; Atmospheric Bending Constant (N-units)
+ 647.000 ; Frequency in MHz (20 MHz to 20 GHz)
+ 5 ; Radio Climate (5 = Continental Temper-
+ ate)
+ 0 ; Polarization (0 = Horizontal, 1 = Verti-
+ cal)
+ 0.50 ; Fraction of situations (50% of loca-
+ tions)
+ 0.90 ; Fraction of time (90% of the time)
+ 46000.0 ; ERP in Watts (optional)
+
+ If an LRP file corresponding to the tx_site QTH file can-
+ not be found, S\bSP\bPL\bLA\bAT\bT!\b! scans the current working directory
+ for the file "splat.lrp". If this file cannot be found,
+ then default parameters will be assigned by S\bSP\bPL\bLA\bAT\bT!\b! and a
+ corresponding "splat.lrp" file containing these default
+ parameters will be written to the current working direc-
+ tory. The generated "splat.lrp" file can then be edited
+ by the user as needed.
+
+ Typical Earth dielectric constants and conductivity values
+ are as follows:
+
+ Dielectric Constant Conductiv-
+ ity
+ Salt water : 80 5.000
+ Good ground : 25 0.020
+ Fresh water : 80 0.010
+ Marshy land : 12 0.007
+ Farmland, forest : 15 0.005
+ Average ground : 15 0.005
+ Mountain, sand : 13 0.002
+ City : 5 0.001
+ Poor ground : 4 0.001
+
+ Radio climate codes used by S\bSP\bPL\bLA\bAT\bT!\b! are as follows:
+
+ 1: Equatorial (Congo)
+ 2: Continental Subtropical (Sudan)
+ 3: Maritime Subtropical (West coast of Africa)
+ 4: Desert (Sahara)
+ 5: Continental Temperate
+ 6: Maritime Temperate, over land (UK and west
+ coasts of US & EU)
+ 7: Maritime Temperate, over sea
+
+ The Continental Temperate climate is common to large land
+ masses in the temperate zone, such as the United States.
+ For paths shorter than 100 km, there is little difference
+ between Continental and Maritime Temperate climates.
+
+ The seventh and eighth parameters in the _\b._\bl_\br_\bp file corre-
+ spond to the statistical analysis provided by the Longley-
+ Rice model. In this example, S\bSP\bPL\bLA\bAT\bT!\b! will return the maxi-
+ mum path loss occurring 50% of the time (fraction of time)
+ in 90% of situations (fraction of situations). This is
+ often denoted as F(50,90) in Longley-Rice studies. In the
+ United States, an F(50,90) criteria is typically used for
+ digital television (8-level VSB modulation), while
+ F(50,50) is used for analog (VSB-AM+NTSC) broadcasts.
+
+ 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
+ _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bs_\bo_\bf_\bt_\bw_\br_\bi_\bg_\bh_\bt_\b._\bc_\bo_\bm_\b/_\bf_\ba_\bq_\b/_\be_\bn_\bg_\bi_\bn_\be_\be_\br_\bi_\bn_\bg_\b/_\bp_\br_\bo_\bp_\b__\bl_\bo_\bn_\bg_\b-
+ _\bl_\be_\by_\b__\br_\bi_\bc_\be_\b._\bh_\bt_\bm_\bl
+
+ The final parameter in the _\b._\bl_\br_\bp file corresponds to the
+ transmitter's effective radiated power, and is optional.
+ If it is included in the levels and field strength level
+ contours when performing Longley-Rice studies. If the
+ parameter is omitted, path loss is computed instead. The
+ ERP provided in the _\b._\bl_\br_\bp file can be overridden by using
+ S\bSP\bPL\bLA\bAT\bT!\b!'s _\b-_\be_\br_\bp command-line switch. If the _\b._\bl_\br_\bp file con-
+ tains an ERP parameter and the generation of path-loss
+ rather than signal strength contours is desired, the ERP
+ can be assigned to zero using the _\b-_\be_\br_\bp switch without hav-
+ ing to edit the _\b._\bl_\br_\bp file to accomplish the same result.
+
+C\bCI\bIT\bTY\bY L\bLO\bOC\bCA\bAT\bTI\bIO\bON\bN F\bFI\bIL\bLE\bES\bS
+ The names and locations of cities, tower sites, or other
+ 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 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):
+
+ Teaneck, 40.891973, 74.014506
+ Tenafly, 40.919212, 73.955892
+ Teterboro, 40.859511, 74.058908
+ Tinton Falls, 40.279966, 74.093924
+ Toms River, 39.977777, 74.183580
+ Totowa, 40.906160, 74.223310
+ Trenton, 40.219922, 74.754665
+
+ A total of five separate city data files may be imported
+ 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 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
+ available from the U.S. Census Bureau using the c\bci\bit\bty\byd\bde\be-\b-
+ c\bco\bod\bde\ber\br utility included with S\bSP\bPL\bLA\bAT\bT!\b!. Such data is avail-
+ able free of charge 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/_\bb_\bd_\by_\b__\bf_\bi_\bl_\be_\bs_\b._\bh_\bt_\bm_\bl, and must be in ASCII
+ format.
+
+C\bCA\bAR\bRT\bTO\bOG\bGR\bRA\bAP\bPH\bHI\bIC\bC B\bBO\bOU\bUN\bND\bDA\bAR\bRY\bY D\bDA\bAT\bTA\bA F\bFI\bIL\bLE\bES\bS
+ Cartographic boundary data may also be imported to plot
+ the boundaries of cities, counties, or states on topo-
+ 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.
+
+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-
+ 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
+ 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 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! Path Analysis Report to the current work-
+ ing directory. The report contains details of the trans-
+ mitter 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 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 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
+ receiver can be generated by adding the _\b-_\bp switch:
+
+ 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._\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
+ the receiver can be generated by using the _\b-_\be switch:
+
+ 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
+ from the perspective of the receiver's location. A second
+ 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
+ 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
+ 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
+ generated using the _\b-_\bh switch:
+
+ 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 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
+
+ Fresnel Zone clearances other 60% can be specified using
+ the _\b-_\bf_\bz switch as follows:
+
+ splat -t tx_site -r rx_site -f 439.250 -fz 75 -H
+ height_profile2.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.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 a point-to-point analysis, a S\bSP\bPL\bLA\bAT\bT!\b! Path
+ Analysis Report is generated in the form of a text file
+ with a _\b._\bt_\bx_\bt filename extension. The report contains bear-
+ ings and distances between the transmitter and receiver,
+ as well as the free-space and Longley-Rice path loss for
+ the path being analyzed. The mode of propagation for the
+ path is 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_\bz_\bo_\bn, _\bD_\bi_\bf_\bf_\br_\ba_\bc_\bt_\bi_\bo_\bn _\bD_\bo_\bm_\bi_\bn_\ba_\bn_\bt, or _\bT_\br_\bo_\bp_\bo_\bs_\bc_\ba_\bt_\bt_\be_\br _\bD_\bo_\bm_\bi_\bn_\ba_\bn_\bt.
+
+ Distances and locations to known obstructions along the
+ path between transmitter and receiver are also provided.
+ If the transmitter's effective radiated power is specified
+ in the transmitter's corresponding _\b._\bl_\br_\bp file, then pre-
+ dicted signal strength and antenna voltage at the receiv-
+ ing location is also provided in the Path Analysis Report.
+
+ 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 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:
+
+ _\bT=_\bT_\bI+_\bG_\bT
+
+ where T\bTI\bI is actual amount of RF power delivered to the
+ transmitting antenna in dBW, G\bGT\bT is the transmitting
+ antenna gain (over isotropic) in the direction of the
+ receiver (or the horizon if the receiver is over the hori-
+ zon).
+
+ To compute how much more signal is available over the min-
+ imum to necessary to achieve a specific signal-to-noise
+ ratio:
+
+ _\bS_\bi_\bg_\bn_\ba_\bl__\bM_\ba_\br_\bg_\bi_\bn=_\bS_\bN_\bR-_\bS
+
+ where S\bS is the minimum required SNR ratio (15.5 dB for
+ ATSC (8-level 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
+ yet another perspective. Topographic maps generated by
+ S\bSP\bPL\bLA\bAT\bT!\b! display elevations using a logarithmic grayscale,
+ with higher elevations represented through brighter shades
+ of gray. The dynamic range of the image is scaled between
+ the highest and lowest elevations present in the map. The
+ only exception to this is sea-level, which is represented
+ using the color blue.
+
+ Topographic output is invoked using the _\b-_\bo switch:
+
+ splat -t tx_site -r rx_site -o topo_map.ppm
+
+ The _\b._\bp_\bp_\bm extension on the output filename is assumed by
+ S\bSP\bPL\bLA\bAT\bT!\b!, and is optional.
+
+ In this example, _\bt_\bo_\bp_\bo_\b__\bm_\ba_\bp_\b._\bp_\bp_\bm will illustrate the loca-
+ tions of the transmitter and receiver sites specified. In
+ addition, the great circle path between the two sites will
+ be drawn over locations for which an unobstructed path
+ exists to the transmitter at a receiving antenna height
+ equal to that of the receiver site (specified in
+ _\br_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh).
+
+ It may desirable to populate the topographic map with
+ names and locations of cities, tower sites, or other
+ important locations. A city file may be passed to S\bSP\bPL\bLA\bAT\bT!\b!
+ using the _\b-_\bs switch:
+
+ splat -t tx_site -r rx_site -s cities.dat -o topo_map
+
+ Up to five separate city files may be passed to S\bSP\bPL\bLA\bAT\bT!\b! at
+ a time following the _\b-_\bs switch.
+
+ County and state boundaries may be added to the map by
+ specifying up to five U.S. Census Bureau cartographic
+ boundary files using the _\b-_\bb switch:
+
+ splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map
+
+ In situations where multiple transmitter sites are in use,
+ as many as four site locations may be passed to S\bSP\bPL\bLA\bAT\bT!\b! at
+ a time for analysis:
+
+ splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p
+ 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
+ topographic map can be specified using the _\b-_\bo switch, and
+ line-of-sight paths between each transmitter and the
+ receiver site indicated will be produced on the map, each
+ in its own color. The path between the first transmitter
+ specified to the receiver will be in green, the path
+ between the second transmitter and the receiver will be in
+ cyan, the path between the third transmitter and the
+ receiver will be in violet, and the path between the
+ fourth transmitter and the receiver will be in sienna.
+
+ 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.
+
+ The _\b-_\bn_\bg_\bs option assigns all terrain to the color white,
+ and can be used when it is desirable to generate a map
+ that is devoid of terrain:
+
+ splat -t tx_site -r rx_site -b co34_d00.dat -ngs -o
+ white_map
+
+ The resulting .ppm image file can be converted to .png
+ format with a transparent background using I\bIm\bma\bag\bge\beM\bMa\bag\bgi\bic\bck\bk's
+ c\bco\bon\bnv\bve\ber\brt\bt utility:
+
+ convert -transparent "#FFFFFF" white_map.ppm transpar-
+ ent_map.png
+
+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
+ 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
+ with the site in question. A regional analysis may be
+ performed by S\bSP\bPL\bLA\bAT\bT!\b! using the _\b-_\bc switch as follows:
+
+ 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). 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)
+ switch:
+
+ splat -t wnjt-dt -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
+ use the "four-thirds earth" model for line-of-sight propa-
+ gation analysis. Any appropriate earth radius multiplier
+ may be selected by the user.
+
+ When performing a regional analysis, 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
+ toward the bearings of 0, 45, 90, 135, 180, 225, 270, and
+ 315 degrees azimuth.
+
+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 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 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-
+ ues in decimal):
+
+ site1: Green (0,255,0)
+ site2: Cyan (0,255,255)
+ site3: Medium Violet (147,112,219)
+ site4: Sienna 1 (255,130,71)
+
+ site1 + site2: Yellow (255,255,0)
+ site1 + site3: Pink (255,192,203)
+ site1 + site4: Green Yellow (173,255,47)
+ site2 + site3: Orange (255,165,0)
+ site2 + site4: Dark Sea Green 1 (193,255,193)
+ site3 + site4: Dark Turquoise (0,206,209)
+
+ site1 + site2 + site3: Dark Green (0,100,0)
+ site1 + site2 + site4: Blanched Almond (255,235,205)
+ site1 + site3 + site4: Medium Spring Green (0,250,154)
+ site2 + site3 + site4: Tan (210,180,140)
+
+ site1 + site2 + site3 + site4: Gold2 (238,201,0)
+
+ If separate _\b._\bq_\bt_\bh files are generated, each representing a
+ common site location but a different antenna height, a
+ single topographic map illustrating the regional coverage
+ from as many as four separate locations on a single tower
+ may be generated by S\bSP\bPL\bLA\bAT\bT!\b!.
+
+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 in areas surrounding the
+ transmitter site. A legend at the bottom of the map cor-
+ relates each color with a specific path loss range in
+ decibels or signal strength in decibels over one microvolt
+ per meter (dBuV/m).
+
+ 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-dt -L 30.0 -s cities.dat -b co34_d00.dat -db
+ 140 -o plot.ppm
+
+
+S\bSI\bIG\bGN\bNA\bAL\bL C\bCO\bON\bNT\bTO\bOU\bUR\bR C\bCO\bOL\bLO\bOR\bR D\bDE\bEF\bFI\bIN\bNI\bIT\bTI\bIO\bON\bN P\bPA\bAR\bRA\bAM\bME\bET\bTE\bER\bRS\bS
+ The colors used to illustrate signal strength and path
+ loss contours in S\bSP\bPL\bLA\bAT\bT!\b! generated coverage maps may be
+ tailored by the user by creating or modifying S\bSP\bPL\bLA\bAT\bT!\b!'s
+ color definition files. S\bSP\bPL\bLA\bAT\bT!\b! color definition files
+ have the same base name as the transmitter's _\b._\bq_\bt_\bh file,
+ but carry _\b._\bl_\bc_\bf and _\b._\bs_\bc_\bf extensions.
+
+ When a regional Longley-Rice analysis is performed and the
+ transmitter's ERP is not specified or is zero, a _\b._\bl_\bc_\bf path
+ loss color definition file corresponding to the transmit-
+ ter site (_\b._\bq_\bt_\bh) is read by S\bSP\bPL\bLA\bAT\bT!\b! from the current working
+ directory. If a _\b._\bl_\bc_\bf file corresponding to the transmit-
+ ter site is not found, then a default file suitable for
+ manual editing by the user is automatically generated by
+ S\bSP\bPL\bLA\bAT\bT!\b!. If the transmitter's ERP is specified, then a
+ signal strength map is generated and a signal strength
+ color definition file (_\b._\bs_\bc_\bf) is read, or generated if one
+ is not available in the current working directory.
+
+ A path-loss color definition file possesses the following
+ structure (_\bw_\bn_\bj_\bt_\b-_\bd_\bt_\b._\bl_\bc_\bf):
+
+ ; SPLAT! Auto-generated Path-Loss Color Definition
+ ("wnjt-dt.lcf") File
+ ;
+ ; Format for the parameters held in this file is as fol-
+ lows:
+ ;
+ ; dB: red, green, blue
+ ;
+ ; ...where "dB" is the path loss (in dB) and
+ ; "red", "green", and "blue" are the corresponding RGB
+ color
+ ; definitions ranging from 0 to 255 for the region speci-
+ fied.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour
+ regions
+ ; may be defined in this file.
+ ;
+ ;
+ 80: 255, 0, 0
+ 90: 255, 128, 0
+ 100: 255, 165, 0
+ 110: 255, 206, 0
+ 120: 255, 255, 0
+ 130: 184, 255, 0
+ 140: 0, 255, 0
+ 150: 0, 208, 0
+ 160: 0, 196, 196
+ 170: 0, 148, 255
+ 180: 80, 80, 255
+ 190: 0, 38, 255
+ 200: 142, 63, 255
+ 210: 196, 54, 255
+ 220: 255, 0, 255
+ 230: 255, 194, 204
+
+
+ If the path loss is less than 80 dB, the color Red (RGB =
+ 255, 0, 0) is assigned to the region. If the path-loss is
+ greater than or equal to 80 dB, but less than 90 db, then
+ Dark Orange (255, 128, 0) is assigned to the region.
+ Orange (255, 165, 0) is assigned to regions having a path
+ loss greater than or equal to 90 dB, but less than 100 dB,
+ and so on. Greyscale terrain is displayed beyond the 230
+ dB path loss contour.
+
+ S\bSP\bPL\bLA\bAT\bT!\b! signal strength color definition files share a very
+ similar structure (_\bw_\bn_\bj_\bt_\b-_\bd_\bt_\b._\bs_\bc_\bf):
+
+ ; SPLAT! Auto-generated Signal Color Definition ("wnjt-
+ dt.scf") File
+ ;
+ ; Format for the parameters held in this file is as fol-
+ lows:
+ ;
+ ; dBuV/m: red, green, blue
+ ;
+ ; ...where "dBuV/m" is the signal strength (in dBuV/m)
+ and
+ ; "red", "green", and "blue" are the corresponding RGB
+ color
+ ; definitions ranging from 0 to 255 for the region speci-
+ fied.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour
+ regions
+ ; may be defined in this file.
+ ;
+ ;
+ 128: 255, 0, 0
+ 118: 255, 165, 0
+ 108: 255, 206, 0
+ 98: 255, 255, 0
+ 88: 184, 255, 0
+ 78: 0, 255, 0
+ 68: 0, 208, 0
+ 58: 0, 196, 196
+ 48: 0, 148, 255
+ 38: 80, 80, 255
+ 28: 0, 38, 255
+ 18: 142, 63, 255
+ 8: 140, 0, 128
+
+
+ If the signal strength is greater than or equal to 128 db
+ over 1 microvolt per meter (dBuV/m), the color Red (255,
+ 0, 0) is displayed for the region. If the signal strength
+ is greater than or equal to 118 dbuV/m, but less than 128
+ dbuV/m, then the color Orange (255, 165, 0) is displayed,
+ and so on. Greyscale terrain is displayed for regions
+ with signal strengths less than 8 dBuV/m.
+
+ Signal strength contours for some common VHF and UHF
+ broadcasting services in the United States are as follows:
+
+ Analog Television Broadcasting
+ ------------------------------
+ Channels 2-6: City Grade: >= 74 dBuV/m
+ Grade A: >= 68 dBuV/m
+ Grade B: >= 47 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 77 dBuV/m
+ Grade A: >= 71 dBuV/m
+ Grade B: >= 56 dBuV/m
+ --------------------------------------------
+ Channels 14-69: Indoor Grade: >= 94 dBuV/m
+ City Grade: >= 80 dBuV/m
+ Grade A: >= 74 dBuV/m
+ Grade B: >= 64 dBuV/m
+
+ Digital Television Broadcasting
+ -------------------------------
+ Channels 2-6: City Grade: >= 35 dBuV/m
+ Service Threshold: >= 28 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 43 dBuV/m
+ Service Threshold: >= 36 dBuV/m
+ --------------------------------------------
+ Channels 14-69: City Grade: >= 48 dBuV/m
+ Service Threshold: >= 41 dBuV/m
+
+ NOAA Weather Radio (162.400 - 162.550 MHz)
+ ------------------------------------------
+ Reliable: >= 18 dBuV/m
+ Not reliable: < 18 dBuV/m
+ Unlikely to receive: < 0 dBuV/m
+
+ FM Radio Broadcasting (88.1 - 107.9 MHz)
+ ----------------------------------------
+ Analog Service Contour: 60 dBuV/m
+ Digital Service Contour: 65 dBuV/m
+
+
+
+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 mechani-
+ cal beam tilt and tilt direction (if any) are also con-
+ tained 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
+ 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 no text report is desired, then the _\b-_\bN switch is used:
+
+ splat -t tx_site -r rx_site -N -o topo_map.ppm
+
+ 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). Note that
+ the tx_site name and location are not displayed in this
+ example. If display of this information is desired, sim-
+ ply create a S\bSP\bPL\bLA\bAT\bT!\b! city file (_\b-_\bs option) and append it to
+ the list of command-line options illustrated above.
+
+ If the _\b-_\bo switch and output filename are omitted in these
+ operations, topographic output is written to a file named
+ _\bt_\bx_\b__\bs_\bi_\bt_\be_\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
+ or regional coverage analyses by invoking the _\b-_\bk_\bm_\bl switch:
+
+ splat -t wnjt-dt -r kd2bd -kml
+
+ The KML file generated will have the same filename struc-
+ ture as a Path Analysis 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.
+
+ When performing regional coverage analysis, the _\b._\bk_\bm_\bl file
+ generated by S\bSP\bPL\bLA\bAT\bT!\b! will permit path loss or signal
+ strength contours to be layered on top of G\bGo\boo\bog\bgl\ble\be E\bEa\bar\brt\bth\bh's
+ display in a semi-transparent manner. The generated _\b._\bk_\bm_\bl
+ file will have the same basename as that of the _\b._\bp_\bp_\bm file
+ normally generated.
+
+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
+ (HAAT) according to the procedure defined by Federal Com-
+ munications Commission Part 73.313(d). According to this
+ definition, terrain elevations along eight radials between
+ 2 and 10 miles (3 and 16 kilometers) from the site being
+ analyzed are sampled and averaged for each 45 degrees of
+ azimuth starting with True North. If one or more radials
+ 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.
+
+ 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
+ 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
+ cases, this will be true, unless the site in question does
+ 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 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
+ "pages" within the structure of the program. Each "page"
+ 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_\bP_\bA_\bG_\bE_\bS statement in the
+ first several lines of _\bs_\bp_\bl_\ba_\bt_\b._\bc_\bp_\bp sets the maximum number
+ of "pages" available for holding topography data. It also
+ sets the maximum size of the topographic maps generated by
+ S\bSP\bPL\bLA\bAT\bT!\b!. MAXPAGES 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 the
+ number of MAXPAGES specified. In situations where avail-
+ able memory is low, MAXPAGES 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 avail-
+ able, then MAXPAGES 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 dis-
+ tances 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
+ 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.
+
+A\bAU\bUT\bTH\bHO\bOR\bRS\bS
+ John A. Magliacane, KD2BD <_\bk_\bd_\b2_\bb_\bd_\b@_\ba_\bm_\bs_\ba_\bt_\b._\bo_\br_\bg>
+ Creator, Lead Developer
+
+ Doug McDonald <_\bm_\bc_\bd_\bo_\bn_\ba_\bl_\bd_\b@_\bs_\bc_\bs_\b._\bu_\bi_\bu_\bc_\b._\be_\bd_\bu>
+ Original 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 16 September 2007 SPLAT!(1)
--- /dev/null
+.TH SPLAT! 1 "16 September 2007" "KD2BD Software" "KD2BD Software"
+.SH NAME
+splat \- An RF \fBS\fPignal \fBP\fPropagation, \fBL\fPoss, \fBA\fPnd \fBT\fPerrain analysis tool
+.SH SYNOPSIS
+splat [-t \fItransmitter_site.qth\fP]
+[-r \fIreceiver_site.qth\fP]
+[-c \fIrx antenna height for LOS coverage analysis (feet/meters) (float)\fP]
+[-L \fIrx antenna height for Longley-Rice coverage analysis (feet/meters) (float)\fP]
+[-p \fIterrain_profile.ext\fP]
+[-e \fIelevation_profile.ext\fP]
+[-h \fIheight_profile.ext\fP]
+[-H \fInormalized_height_profile.ext\fP]
+[-l \fILongley-Rice_profile.ext\fP]
+[-o \fItopographic_map_filename.ppm\fP]
+[-b \fIcartographic_boundary_filename.dat\fP]
+[-s \fIsite/city_database.dat\fP]
+[-d \fIsdf_directory_path\fP]
+[-m \fIearth radius multiplier (float)\fP]
+[-f \fIfrequency (MHz) for Fresnel zone calculations (float)\fP]
+[-R \fImaximum coverage radius (miles/kilometers) (float)\fP]
+[-dB \fImaximum attenuation contour to display on path loss maps (80-230 dB)\fP]
+[-fz \fIFresnel zone clearance percentage (default = 60)\fP]
+[-plo \fIpath_loss_output_file.txt\fP]
+[-pli \fIpath_loss_input_file.txt\fP]
+[-udt \fIuser_defined_terrain_file.dat\fP]
+[-n]
+[-N]
+[-nf]
+[-ngs]
+[-geo]
+[-kml]
+[-metric]
+.SH DESCRIPTION
+\fBSPLAT!\fP is a powerful terrestrial RF propagation and terrain
+analysis tool for the spectrum between 20 MHz and 20 GHz.
+\fBSPLAT!\fP is free software, and is designed for operation on Unix
+and Linux-based workstations. Redistribution and/or modification
+is permitted under the terms of the GNU General Public License, Version 2,
+as published by the Free Software Foundation. Adoption of \fBSPLAT!\fP
+source code in proprietary or closed-source applications is a violation
+of this license and is \fBstrictly\fP forbidden.
+
+\fBSPLAT!\fP is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY, without even the implied warranty of MERCHANTABILITY
+or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
+for more details.
+.SH INTRODUCTION
+Applications of \fBSPLAT!\fP 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 interference studies, and the prediction
+of analog and digital terrestrial radio and television contour regions.
+
+\fBSPLAT!\fP provides RF site engineering data such as great circle
+distances and bearings between sites, antenna elevation angles (uptilt),
+depression angles (downtilt), antenna height above mean sea level,
+antenna height above average terrain, bearings, distances, and elevations
+to known obstructions, Longley-Rice path attenuation, and received signal
+strength. In addition, the minimum antenna height requirements needed to
+clear terrain, the first Fresnel zone, and any user-definable percentage
+of the first Fresnel zone are also provided.
+
+\fBSPLAT!\fP produces reports, graphs, and high resolution topographic
+maps that depict line-of-sight paths, and regional path loss and signal
+strength contours through which expected coverage areas of transmitters
+and repeater systems can be obtained. When performing line-of-sight
+and Longley-Rice analyses in situations where multiple transmitter or
+repeater sites are employed, \fBSPLAT!\fP determines individual and
+mutual areas of coverage within the network specified.
+
+Simply typing \fCsplat\fR on the command line will return a summary
+of \fBSPLAT!\fP's command line options:
+\fC
+
+ --==[ SPLAT! v1.2.1 Available Options... ]==--
+
+ -t txsite(s).qth (max of 4 with -c, max of 30 with -L)
+ -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 (5 max)
+ -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)
+ -m earth radius multiplier
+ -n do not plot LOS paths in .ppm maps
+ -N do not produce unnecessary site or obstruction reports
+ -f frequency for Fresnel zone calculation (MHz)
+ -R modify default range for -c or -L (miles/kilometers)
+ -db maximum loss contour to display on path loss maps (80-230 dB)
+ -nf do not plot Fresnel zones in height plots
+ -fz Fresnel zone clearance percentage (default = 60)
+ -ngs display greyscale topography as white in .ppm files
+ -erp override ERP in .lrp file (Watts)
+ -pli filename of path-loss input file
+ -plo filename of path-loss output file
+ -udt filename of user defined terrain input file
+ -kml generate Google Earth (.kml) compatible output
+ -geo generate an Xastir .geo georeference file (with .ppm output)
+-metric employ metric rather than imperial units for all user I/O
+\fR
+.SH INPUT FILES
+\fBSPLAT!\fP 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 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, antenna
+radiation pattern files, and color definition files.
+.SH SPLAT DATA FILES
+\fBSPLAT!\fP imports topographic data in the form of SPLAT Data Files
+(SDFs). These files may be generated from a number of information sources.
+In the United States, SPLAT Data Files can be generated through U.S.
+Geological Survey Digital Elevation Models (DEMs) using the \fBusgs2sdf\fP
+utility included with \fBSPLAT!\fP. USGS Digital Elevation Models
+compatible with this utility may be downloaded from:
+\fIhttp://edcftp.cr.usgs.gov/pub/data/DEM/250/\fP.
+
+Significantly better resolution and accuracy can be obtained through
+the use of SRTM-3 Version 2 digital elevation 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 \fBsrtm2sdf\fP utility.
+SRTM-3 Version 2 data may be obtained through anonymous FTP from:
+\fIftp://e0srp01u.ecs.nasa.gov:21/srtm/version2/\fP
+
+The \fBstrm2sdf\fP utility may also be used to convert 3-arc second SRTM
+data in Band Interleaved by Line (.BIL) format for use with \fBSPLAT!\fP.
+This data is available via the web at:
+\fIhttp://seamless.usgs.gov/website/seamless/\fP
+
+Band Interleaved by Line data must be downloaded in a very specific manner
+to be compatible with \fBsrtm2sdf\fP and \fBSPLAT!\fP. Please consult
+\fBsrtm2sdf\fP's documentation for instructions on downloading .BIL
+topographic data through the USGS's Seamless Web Site.
+
+Despite the higher accuracy that SRTM data has to offer, some voids
+in the data sets exist. When voids are detected, the \fBsrtm2sdf\fP
+utility replaces them with corresponding data found in existing SDF
+files (that were presumably created from earlier USGS data through the
+\fBusgs2sdf\fP utility). If USGS-derived SDF data is not available, voids
+are handled through adjacent pixel averaging, or direct replacement.
+
+SPLAT Data Files contain integer value topographic elevations (in meters)
+referenced to mean sea level for 1-degree by 1-degree regions of the
+earth with a resolution of 3-arc seconds. SDF files can be read in
+either standard format (\fI.sdf\fP) as generated by the \fBusgs2sdf\fP
+and \fBsrtm2sdf\fP utilities, or in bzip2 compressed format
+(\fI.sdf.bz2\fP). Since uncompressed files can be read slightly
+faster than files that have been compressed, \fBSPLAT!\fP searches for
+needed SDF data in uncompressed format first. If uncompressed data
+cannot be located, \fBSPLAT!\fP then searches for data in bzip2 compressed
+format. If no compressed SDF files can be found for the region requested,
+\fBSPLAT!\fP assumes the region is over water, and will assign an
+elevation of sea-level to these areas.
+
+This feature of \fBSPLAT!\fP 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 \fBSPLAT!\fP
+underscores the importance of having all the SDF files required for
+the region being analyzed if meaningful results are to be expected.
+.SH SITE LOCATION (QTH) FILES
+\fBSPLAT!\fP imports site location information of transmitter and receiver
+sites analyzed by the program from ASCII files having a \fI.qth\fP 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, or degrees East 0 to -360 degrees), and the site's
+antenna height above ground level (AGL), each separated by a single
+line-feed character. The antenna height is assumed to be specified in
+feet unless followed by the letter \fIm\fP or the word \fImeters\fP in
+either upper or lower case. Latitude and longitude information may be
+expressed in either decimal format (74.6864) or degree, minute, second
+(DMS) format (74 41 11.0).
+
+For example, a site location file describing television station WNJT-DT,
+Trenton, NJ (\fIwnjt-dt.qth\fP) might read as follows:
+\fC
+ WNJT-DT
+ 40.2828
+ 74.6864
+ 990.00
+\fR
+Each transmitter and receiver site analyzed by \fBSPLAT!\fP must be
+represented by its own site location (QTH) file.
+.SH LONGLEY-RICE PARAMETER (LRP) FILES
+Longley-Rice parameter data files are required for \fBSPLAT!\fP 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 transmitter site QTH file, but with a
+\fI.lrp\fP extension. \fBSPLAT!\fP LRP files share the following
+format (\fIwnjt-dt.lrp\fP):
+\fC
+ 15.000 ; Earth Dielectric Constant (Relative permittivity)
+ 0.005 ; Earth Conductivity (Siemens per meter)
+ 301.000 ; Atmospheric Bending Constant (N-units)
+ 647.000 ; Frequency in MHz (20 MHz to 20 GHz)
+ 5 ; Radio Climate (5 = Continental Temperate)
+ 0 ; Polarization (0 = Horizontal, 1 = Vertical)
+ 0.50 ; Fraction of situations (50% of locations)
+ 0.90 ; Fraction of time (90% of the time)
+ 46000.0 ; ERP in Watts (optional)
+\fR
+If an LRP file corresponding to the tx_site QTH file cannot
+be found, \fBSPLAT!\fP scans the current working directory for
+the file "splat.lrp". If this file cannot be found, then default
+parameters will be assigned by \fBSPLAT!\fP and a corresponding
+"splat.lrp" file containing these default parameters will be written
+to the current working directory. The generated "splat.lrp" file can
+then be edited by the user as needed.
+
+Typical Earth dielectric constants and conductivity values are as
+follows:
+\fC
+ Dielectric Constant Conductivity
+ Salt water : 80 5.000
+ Good ground : 25 0.020
+ Fresh water : 80 0.010
+ Marshy land : 12 0.007
+ Farmland, forest : 15 0.005
+ Average ground : 15 0.005
+ Mountain, sand : 13 0.002
+ City : 5 0.001
+ Poor ground : 4 0.001
+\fR
+Radio climate codes used by \fBSPLAT!\fP are as follows:
+\fC
+ 1: Equatorial (Congo)
+ 2: Continental Subtropical (Sudan)
+ 3: Maritime Subtropical (West coast of Africa)
+ 4: Desert (Sahara)
+ 5: Continental Temperate
+ 6: Maritime Temperate, over land (UK and west coasts of US & EU)
+ 7: Maritime Temperate, over sea
+\fR
+The Continental Temperate climate is common to large land masses in
+the temperate zone, such as the United States. For paths shorter than
+100 km, there is little difference between Continental and Maritime
+Temperate climates.
+
+The seventh and eighth parameters in the \fI.lrp\fP file correspond to the
+statistical analysis provided by the Longley-Rice model. In this example,
+\fBSPLAT!\fP will return the maximum path loss occurring 50% of the time
+(fraction of time) in 90% of situations (fraction of situations). This is
+often denoted as F(50,90) in Longley-Rice studies. In the United States,
+an F(50,90) criteria is typically used for digital television (8-level
+VSB modulation), while F(50,50) is used for analog (VSB-AM+NTSC) broadcasts.
+
+For further information on these parameters, see:
+\fIhttp://flattop.its.bldrdoc.gov/itm.html\fP and
+\fIhttp://www.softwright.com/faq/engineering/prop_longley_rice.html\fP
+
+The final parameter in the \fI.lrp\fP file corresponds to the transmitter's
+effective radiated power, and is optional. If it is included in the
+\fI.lrp\fP file, then \fBSPLAT!\fP will compute received signal strength
+levels and field strength level contours when performing Longley-Rice
+studies. If the parameter is omitted, path loss is computed instead.
+The ERP provided in the \fI.lrp\fP file can be overridden by using
+\fBSPLAT!\fP's \fI-erp\fP command-line switch. If the \fI.lrp\fP file
+contains an ERP parameter and the generation of path-loss rather than
+signal strength contours is desired, the ERP can be assigned to zero
+using the \fI-erp\fP switch without having to edit the \fI.lrp\fP file
+to accomplish the same result.
+.SH CITY LOCATION FILES
+The names and locations of cities, tower sites, or other points of interest
+may be imported and plotted on topographic maps generated by \fBSPLAT!\fP.
+\fBSPLAT!\fP imports the names of cities and locations from ASCII files
+containing the location of interest's name, latitude, and longitude.
+Each field is separated by a comma. Each record is separated by a
+single line feed character. As was the case with the \fI.qth\fP
+files, latitude and longitude information may be entered in either
+decimal or degree, minute, second (DMS) format.
+
+For example (\fIcities.dat\fP):
+\fC
+ Teaneck, 40.891973, 74.014506
+ Tenafly, 40.919212, 73.955892
+ Teterboro, 40.859511, 74.058908
+ Tinton Falls, 40.279966, 74.093924
+ Toms River, 39.977777, 74.183580
+ Totowa, 40.906160, 74.223310
+ Trenton, 40.219922, 74.754665
+\fR
+A total of five separate city data files may be imported at a time,
+and there is no limit to the size of these files. \fBSPLAT!\fP reads
+city data on a "first come/first served" basis, and plots only those
+locations whose annotations do not conflict with annotations of
+locations read earlier in the current city data file, or in previous
+files. This behavior minimizes clutter in \fBSPLAT!\fP generated
+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 further 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 available from the
+U.S. Census Bureau using the \fBcitydecoder\fP utility included with
+\fBSPLAT!\fP. Such data is available free of charge via the Internet
+at: \fIhttp://www.census.gov/geo/www/cob/bdy_files.html\fP, and must
+be in ASCII format.
+.SH CARTOGRAPHIC BOUNDARY DATA FILES
+Cartographic boundary data may also be imported to plot the boundaries of
+cities, counties, or states on topographic maps generated by \fBSPLAT!\fP.
+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:
+\fIhttp://www.census.gov/geo/www/cob/co2000.html#ascii\fP and
+\fIhttp://www.census.gov/geo/www/cob/pl2000.html#ascii\fP. 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.
+.SH PROGRAM OPERATION
+\fBSPLAT!\fP is invoked via the command-line using a series of switches
+and arguments. Since \fBSPLAT!\fP is a CPU and memory intensive application,
+this type of interface minimizes overhead and lends itself well to
+scripted (batch) operations. \fBSPLAT!\fP's CPU and memory scheduling
+priority may be modified through the use of the Unix \fBnice\fP command.
+
+The number and type of switches passed to \fBSPLAT!\fP determine its
+mode of operation and method of output data generation. Nearly all
+of \fBSPLAT!\fP's switches may be cascaded in any order on the command
+line when invoking the program.
+
+\fBSPLAT!\fP operates in two distinct modes: \fIpoint-to-point mode\fP,
+and \fIarea prediction mode\fP. 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
+specified when performing line-of-sight analysis.
+.SH POINT-TO-POINT ANALYSIS
+\fBSPLAT!\fP may be used to perform line-of-sight terrain analysis
+between two specified site locations. For example:
+
+\fCsplat -t tx_site.qth -r rx_site.qth\fR
+
+invokes a line-of-sight terrain analysis between the transmitter
+specified in \fItx_site.qth\fP and receiver specified in \fIrx_site.qth\fP
+using a True Earth radius model, and writes a \fBSPLAT!\fP Path Analysis
+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,
+\fBSPLAT!\fP 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 \fI-metric\fP switch is added to \fBSPLAT!\fP's command line options:
+
+\fCsplat -t tx_site.qth -r rx_site.qth -metric\fR
+
+If the antenna must be raised a significant amount, this determination
+may take a few moments. Note that the results provided are the \fIminimum\fP
+necessary for a line-of-sight path to exist, and in the case of this
+simple example, do not take Fresnel zone clearance requirements into
+consideration.
+
+\fIqth\fP extensions are assumed by \fBSPLAT!\fP for QTH files, and
+are optional when specifying -t and -r arguments on the command-line.
+\fBSPLAT!\fP automatically reads all SPLAT Data Files necessary to
+conduct the terrain analysis between the sites specified. \fBSPLAT!\fP
+searches for the required SDF files in the current working directory
+first. If the needed files are not found, \fBSPLAT!\fP then searches
+in the path specified by the \fI-d\fP command-line switch:
+
+\fCsplat -t tx_site -r rx_site -d /cdrom/sdf/\fR
+
+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 of last resort to all the SDF files. The path in the
+\fI$HOME/.splat_path\fP file must be of the form of a single line of
+ASCII text:
+
+\fC/opt/splat/sdf/\fR
+
+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 receiver can be generated
+by adding the \fI-p\fP switch:
+
+\fCsplat -t tx_site -r rx_site -p terrain_profile.png\fR
+
+\fBSPLAT!\fP invokes \fBgnuplot\fP when generating graphs. The filename
+extension specified to \fBSPLAT!\fP determines the format of the graph
+produced. \fI.png\fP will produce a 640x480 color PNG graphic file,
+while \fI.ps\fP or \fI.postscript\fP will produce postscript output.
+Output in formats such as GIF, Adobe Illustrator, AutoCAD dxf,
+LaTeX, and many others are available. Please consult \fBgnuplot\fP,
+and \fBgnuplot\fP's documentation 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 the receiver can be generated
+by using the \fI-e\fP switch:
+
+\fCsplat -t tx_site -r rx_site -e elevation_profile.png\fR
+
+The graph produced using this switch illustrates the elevation 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
+(receiver's location) and the location of the transmitting antenna on
+the right. This trace illustrates the elevation 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 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 generated using
+the \fI-h\fP switch:
+
+\fCsplat -t tx_site -r rx_site -h height_profile.png\fR
+
+A terrain height plot normalized to the transmitter and receiver
+antenna heights can be obtained using the \fI-H\fP switch:
+
+\fCsplat -t tx_site -r rx_site -H normalized_height_profile.png\fR
+
+A contour of the Earth's curvature is also plotted in this mode.
+
+The first Fresnel Zone, and 60% of the first Fresnel Zone can be
+added to height profile graphs by adding the \fI-f\fP switch, and
+specifying a frequency (in MHz) at which the Fresnel Zone should be
+modeled:
+
+\fCsplat -t tx_site -r rx_site -f 439.250 -H normalized_height_profile.png\fR
+
+Fresnel Zone clearances other 60% can be specified using the \fI-fz\fP
+switch as follows:
+
+\fCsplat -t tx_site -r rx_site -f 439.250 -fz 75 -H height_profile2.png\fR
+
+A graph showing Longley-Rice path loss may be plotted using the
+\fI-l\fP switch:
+
+\fCsplat -t tx_site -r rx_site -l path_loss_profile.png\fR
+
+As before, adding the \fI-metric\fP switch forces the graphs to
+be plotted using metric units of measure.
+
+When performing a point-to-point analysis, a \fBSPLAT!\fP Path Analysis
+Report is generated in the form of a text file with a \fI.txt\fP filename
+extension. The report contains bearings and distances between the
+transmitter and receiver, as well as the free-space and Longley-Rice
+path loss for the path being analyzed. The mode of propagation for
+the path is given as \fILine-of-Sight\fP, \fISingle Horizon\fP,
+\fIDouble Horizon\fP, \fIDiffraction Dominant\fP, or \fITroposcatter
+Dominant\fP.
+
+Distances and locations to known obstructions along the path
+between transmitter and receiver are also provided. If the
+transmitter's effective radiated power is specified in the
+transmitter's corresponding \fI.lrp\fP file, then predicted
+signal strength and antenna voltage at the receiving location
+is also provided in the Path Analysis Report.
+
+To determine the signal-to-noise (SNR) ratio at remote location
+where random Johnson (thermal) noise is the primary limiting
+factor in reception:
+
+.EQ
+SNR = T - NJ - L + G - NF
+.EN
+
+where \fBT\fP is the ERP of the transmitter in dBW in the direction
+of the receiver, \fBNJ\fP is Johnson Noise in dBW (-136 dBW for a 6 MHz
+television channel), \fBL\fP is the path loss provided by \fBSPLAT!\fP
+in dB (as a \fIpositive\fP number), \fBG\fP is the receive antenna gain
+in dB over isotropic, and \fBNF\fP is the receiver noise figure in dB.
+
+\fBT\fP may be computed as follows:
+
+.EQ
+T = TI + GT
+.EN
+
+where \fBTI\fP is actual amount of RF power delivered to the transmitting
+antenna in dBW, \fBGT\fP is the transmitting antenna gain (over isotropic)
+in the direction of the receiver (or the horizon if the receiver is over
+the horizon).
+
+To compute how much more signal is available over the minimum to
+necessary to achieve a specific signal-to-noise ratio:
+
+.EQ
+Signal_Margin = SNR - S
+.EN
+
+where \fBS\fP is the minimum required SNR ratio (15.5 dB for
+ATSC (8-level VSB) DTV, 42 dB for analog NTSC television).
+
+A topographic map may be generated by \fBSPLAT!\fP to visualize the
+path between the transmitter and receiver sites from yet another
+perspective. Topographic maps generated by \fBSPLAT!\fP display
+elevations using a logarithmic grayscale, with higher elevations
+represented through brighter shades of gray. The dynamic range of
+the image is scaled between the highest and lowest elevations present
+in the map. The only exception to this is sea-level, which is
+represented using the color blue.
+
+Topographic output is invoked using the \fI-o\fP switch:
+
+\fCsplat -t tx_site -r rx_site -o topo_map.ppm\fR
+
+The \fI.ppm\fP extension on the output filename is assumed by
+\fBSPLAT!\fP, and is optional.
+
+In this example, \fItopo_map.ppm\fP will illustrate the locations of the
+transmitter and receiver sites specified. In addition, the great circle
+path between the two sites will be drawn over locations for which an
+unobstructed path exists to the transmitter at a receiving antenna
+height equal to that of the receiver site (specified in \fIrx_site.qth\fP).
+
+It may desirable to populate the topographic map with names and locations
+of cities, tower sites, or other important locations. A city file may be
+passed to \fBSPLAT!\fP using the \fI-s\fP switch:
+
+\fCsplat -t tx_site -r rx_site -s cities.dat -o topo_map\fR
+
+Up to five separate city files may be passed to \fBSPLAT!\fP at a time
+following the \fI-s\fP switch.
+
+County and state boundaries may be added to the map by specifying up
+to five U.S. Census Bureau cartographic boundary files using the \fI-b\fP
+switch:
+
+\fCsplat -t tx_site -r rx_site -b co34_d00.dat -o topo_map\fR
+
+In situations where multiple transmitter sites are in use, as many as
+four site locations may be passed to \fBSPLAT!\fP at a time for analysis:
+
+\fCsplat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p profile.png\fR
+
+In this example, four separate terrain profiles and obstruction reports
+will be generated by \fBSPLAT!\fP. A single topographic map can be
+specified using the \fI-o\fP switch, and line-of-sight paths between
+each transmitter and the receiver site indicated will be produced on
+the map, each in its own color. The path between the first transmitter
+specified to the receiver will be in green, the path between the
+second transmitter and the receiver will be in cyan, the path between
+the third transmitter and the receiver will be in violet, and the
+path between the fourth transmitter and the receiver will be in sienna.
+
+\fBSPLAT!\fP 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 \fBxv\fP,
+\fBThe GIMP\fP, \fBImageMagick\fP, and \fBXPaint\fP. PNG format is
+highly recommended for lossless compressed storage of \fBSPLAT!\fP
+generated topographic output files. \fBImageMagick\fP's command-line
+utility easily converts \fBSPLAT!\fP's PPM files to PNG format:
+
+\fCconvert splat_map.ppm splat_map.png\fR
+
+Another excellent PPM to PNG command-line utility is available
+at: \fIhttp://www.libpng.org/pub/png/book/sources.html\fP. As a last
+resort, PPM files may be compressed using the bzip2 utility, and read
+directly by \fBThe GIMP\fP in this format.
+
+The \fI-ngs\fP option assigns all terrain to the color white, and can be
+used when it is desirable to generate a map that is devoid of terrain:
+
+\fCsplat -t tx_site -r rx_site -b co34_d00.dat -ngs -o white_map\fR
+
+The resulting .ppm image file can be converted to .png format with a
+transparent background using \fBImageMagick\fP's \fBconvert\fP utility:
+
+\fCconvert -transparent "#FFFFFF" white_map.ppm transparent_map.png\fR
+.SH REGIONAL COVERAGE ANALYSIS
+\fBSPLAT!\fP can analyze a transmitter or repeater site, or network
+of sites, and predict the regional coverage for each site specified.
+In this mode, \fBSPLAT!\fP can generate a topographic map displaying
+the geometric line-of-sight coverage 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. A regional analysis may be
+performed by \fBSPLAT!\fP using the \fI-c\fP switch as follows:
+
+\fCsplat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o tx_coverage\fR
+
+In this example, \fBSPLAT!\fP generates a topographic map called
+\fItx_coverage.ppm\fP that illustrates the predicted line-of-sight
+regional coverage of \fItx_site\fP to receiving locations having
+antennas 30.0 feet above ground level (AGL). If the \fI-metric\fP
+switch is used, the argument following the \fI-c\fP switch is
+interpreted as being in meters rather than in feet. The contents
+of \fIcities.dat\fP are plotted on the map, as are the cartographic
+boundaries contained in the file \fIco34_d00.dat\fP.
+
+When plotting line-of-sight paths and areas of regional coverage,
+\fBSPLAT!\fP by default does not account for the effects of
+atmospheric bending. However, this behavior may be modified
+by using the Earth radius multiplier (\fI-m\fP) switch:
+
+\fCsplat -t wnjt-dt -c 30.0 -m 1.333 -s cities.dat -b counties.dat -o map.ppm\fR
+
+An earth radius multiplier of 1.333 instructs \fBSPLAT!\fP to use
+the "four-thirds earth" model for line-of-sight propagation analysis.
+Any appropriate earth radius multiplier may be selected by the user.
+
+When performing a regional analysis, \fBSPLAT!\fP generates a
+site report for each station analyzed. \fBSPLAT!\fP 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 toward the bearings of 0, 45, 90, 135,
+180, 225, 270, and 315 degrees azimuth.
+.SH DETERMINING MULTIPLE REGIONS OF LOS COVERAGE
+\fBSPLAT!\fP can also display line-of-sight coverage areas for as
+many as four separate transmitter sites on a common topographic map.
+For example:
+
+\fCsplat -t site1 site2 site3 site4 -c 10.0 -metric -o network.ppm\fR
+
+plots the regional line-of-sight coverage of site1, site2, site3,
+and site4 based on a receive antenna located 10.0 meters above ground
+level. A topographic map is then written to the file \fInetwork.ppm\fP.
+The line-of-sight coverage area of the transmitters are plotted as
+follows in the colors indicated (along with their corresponding RGB
+values in decimal):
+\fC
+ site1: Green (0,255,0)
+ site2: Cyan (0,255,255)
+ site3: Medium Violet (147,112,219)
+ site4: Sienna 1 (255,130,71)
+
+ site1 + site2: Yellow (255,255,0)
+ site1 + site3: Pink (255,192,203)
+ site1 + site4: Green Yellow (173,255,47)
+ site2 + site3: Orange (255,165,0)
+ site2 + site4: Dark Sea Green 1 (193,255,193)
+ site3 + site4: Dark Turquoise (0,206,209)
+
+ site1 + site2 + site3: Dark Green (0,100,0)
+ site1 + site2 + site4: Blanched Almond (255,235,205)
+ site1 + site3 + site4: Medium Spring Green (0,250,154)
+ site2 + site3 + site4: Tan (210,180,140)
+
+ site1 + site2 + site3 + site4: Gold2 (238,201,0)
+\fR
+If separate \fI.qth\fP files are generated, each representing a common
+site location but a different antenna height, a single topographic map
+illustrating the regional coverage from as many as four separate locations
+on a single tower may be generated by \fBSPLAT!\fP.
+.SH LONGLEY-RICE PATH LOSS ANALYSIS
+If the \fI-c\fP switch is replaced by a \fI-L\fP switch, a
+Longley-Rice path loss map for a transmitter site may be generated:
+
+\fCsplat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o path_loss_map\fR
+
+In this mode, \fBSPLAT!\fP generates a multi-color map illustrating
+expected signal levels in areas surrounding the transmitter site. A
+legend at the bottom of the map correlates each color with a specific
+path loss range in decibels or signal strength in decibels over one
+microvolt per meter (dBuV/m).
+
+The Longley-Rice analysis range may be modified to a user-specific
+value using the \fI-R\fP switch. The argument must be given in miles
+(or kilometers if the \fI-metric\fP switch is used). If a range wider
+than the generated topographic map is specified, \fBSPLAT!\fP will
+perform Longley-Rice path loss calculations between all four corners
+of the area prediction map.
+
+The \fI-db\fP 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,
+\fBSPLAT!\fP's path loss plot can be constrained to the region
+bounded by the 140 dB attenuation contour as follows:
+
+\fCsplat -t wnjt-dt -L 30.0 -s cities.dat -b co34_d00.dat -db 140 -o plot.ppm\fR
+
+.SH SIGNAL CONTOUR COLOR DEFINITION PARAMETERS
+The colors used to illustrate signal strength and path loss contours
+in \fBSPLAT!\fP generated coverage maps may be tailored by the user
+by creating or modifying \fBSPLAT!\fP's color definition files.
+\fBSPLAT!\fP color definition files have the same base name as the
+transmitter's \fI.qth\fP file, but carry \fI.lcf\fP and \fI.scf\fP
+extensions.
+
+When a regional Longley-Rice analysis is performed and the transmitter's
+ERP is not specified or is zero, a \fI.lcf\fP path loss color
+definition file corresponding to the transmitter site (\fI.qth\fP) is
+read by \fBSPLAT!\fP from the current working directory. If a \fI.lcf\fP
+file corresponding to the transmitter site is not found, then a default
+file suitable for manual editing by the user is automatically generated
+by \fBSPLAT!\fP. If the transmitter's ERP is specified, then a signal
+strength map is generated and a signal strength color definition file
+(\fI.scf\fP) is read, or generated if one is not available in the current
+working directory.
+
+A path-loss color definition file possesses the following structure
+(\fIwnjt-dt.lcf\fP):
+\fC
+ ; SPLAT! Auto-generated Path-Loss Color Definition ("wnjt-dt.lcf") File
+ ;
+ ; Format for the parameters held in this file is as follows:
+ ;
+ ; dB: red, green, blue
+ ;
+ ; ...where "dB" is the path loss (in dB) and
+ ; "red", "green", and "blue" are the corresponding RGB color
+ ; definitions ranging from 0 to 255 for the region specified.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour regions
+ ; may be defined in this file.
+ ;
+ ;
+ 80: 255, 0, 0
+ 90: 255, 128, 0
+ 100: 255, 165, 0
+ 110: 255, 206, 0
+ 120: 255, 255, 0
+ 130: 184, 255, 0
+ 140: 0, 255, 0
+ 150: 0, 208, 0
+ 160: 0, 196, 196
+ 170: 0, 148, 255
+ 180: 80, 80, 255
+ 190: 0, 38, 255
+ 200: 142, 63, 255
+ 210: 196, 54, 255
+ 220: 255, 0, 255
+ 230: 255, 194, 204
+\fR
+
+If the path loss is less than 80 dB, the color Red (RGB = 255, 0, 0) is
+assigned to the region. If the path-loss is greater than or equal to
+80 dB, but less than 90 db, then Dark Orange (255, 128, 0) is assigned
+to the region. Orange (255, 165, 0) is assigned to regions having a
+path loss greater than or equal to 90 dB, but less than 100 dB, and
+so on. Greyscale terrain is displayed beyond the 230 dB path loss
+contour.
+
+\fBSPLAT!\fP signal strength color definition files share a very similar
+structure (\fIwnjt-dt.scf\fP):
+\fC
+ ; SPLAT! Auto-generated Signal Color Definition ("wnjt-dt.scf") File
+ ;
+ ; Format for the parameters held in this file is as follows:
+ ;
+ ; dBuV/m: red, green, blue
+ ;
+ ; ...where "dBuV/m" is the signal strength (in dBuV/m) and
+ ; "red", "green", and "blue" are the corresponding RGB color
+ ; definitions ranging from 0 to 255 for the region specified.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour regions
+ ; may be defined in this file.
+ ;
+ ;
+ 128: 255, 0, 0
+ 118: 255, 165, 0
+ 108: 255, 206, 0
+ 98: 255, 255, 0
+ 88: 184, 255, 0
+ 78: 0, 255, 0
+ 68: 0, 208, 0
+ 58: 0, 196, 196
+ 48: 0, 148, 255
+ 38: 80, 80, 255
+ 28: 0, 38, 255
+ 18: 142, 63, 255
+ 8: 140, 0, 128
+\fR
+
+If the signal strength is greater than or equal to 128 db over 1 microvolt
+per meter (dBuV/m), the color Red (255, 0, 0) is displayed for the region.
+If the signal strength is greater than or equal to 118 dbuV/m, but less than
+128 dbuV/m, then the color Orange (255, 165, 0) is displayed, and so on.
+Greyscale terrain is displayed for regions with signal strengths less than
+8 dBuV/m.
+
+Signal strength contours for some common VHF and UHF broadcasting services
+in the United States are as follows:
+\fC
+ Analog Television Broadcasting
+ ------------------------------
+ Channels 2-6: City Grade: >= 74 dBuV/m
+ Grade A: >= 68 dBuV/m
+ Grade B: >= 47 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 77 dBuV/m
+ Grade A: >= 71 dBuV/m
+ Grade B: >= 56 dBuV/m
+ --------------------------------------------
+ Channels 14-69: Indoor Grade: >= 94 dBuV/m
+ City Grade: >= 80 dBuV/m
+ Grade A: >= 74 dBuV/m
+ Grade B: >= 64 dBuV/m
+
+ Digital Television Broadcasting
+ -------------------------------
+ Channels 2-6: City Grade: >= 35 dBuV/m
+ Service Threshold: >= 28 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 43 dBuV/m
+ Service Threshold: >= 36 dBuV/m
+ --------------------------------------------
+ Channels 14-69: City Grade: >= 48 dBuV/m
+ Service Threshold: >= 41 dBuV/m
+
+ NOAA Weather Radio (162.400 - 162.550 MHz)
+ ------------------------------------------
+ Reliable: >= 18 dBuV/m
+ Not reliable: < 18 dBuV/m
+ Unlikely to receive: < 0 dBuV/m
+
+ FM Radio Broadcasting (88.1 - 107.9 MHz)
+ ----------------------------------------
+ Analog Service Contour: 60 dBuV/m
+ Digital Service Contour: 65 dBuV/m
+\fR
+
+.SH ANTENNA RADIATION PATTERN PARAMETERS
+Normalized field voltage patterns for a transmitting antenna's horizontal
+and vertical planes are imported automatically into \fBSPLAT!\fP 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 transmitter
+and LRP files, but with \fI.az\fP and \fI.el\fP extensions for azimuth
+and elevation pattern files, respectively. Specifications regarding
+pattern rotation (if any) and mechanical beam tilt and tilt direction
+(if any) are also contained within \fBSPLAT!\fP antenna pattern files.
+
+For example, the first few lines of a \fBSPLAT!\fP azimuth pattern file
+might appear as follows (\fIkvea.az\fP):
+\fC
+ 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
+\fR
+The first line of the \fI.az\fP file specifies the amount of azimuthal
+pattern rotation (measured clockwise in degrees from True North) to be
+applied by \fBSPLAT!\fP to the data contained in the \fI.az\fP file.
+This is followed by azimuth headings (0 to 360 degrees) and their associated
+normalized field patterns (0.000 to 1.000) separated by whitespace.
+
+The structure of \fBSPLAT!\fP elevation pattern files is slightly different.
+The first line of the \fI.el\fP file specifies the amount of mechanical
+beam tilt applied to the antenna. Note that a \fIdownward tilt\fP
+(below the horizon) is expressed as a \fIpositive angle\fP, while an
+\fIupward tilt\fP (above the horizon) is expressed as a \fInegative angle\fP.
+This data is followed by the azimuthal direction of the tilt, separated 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. Elevation angles must be specified
+over a -10.0 to +90.0 degree range. As was the convention with mechanical
+beamtilt, \fInegative elevation angles\fP are used to represent elevations
+\fIabove the horizon\fP, while \fIpositive angles\fP represents elevations
+\fIbelow the horizon\fP.
+
+For example, the first few lines a \fBSPLAT!\fP elevation pattern file
+might appear as follows (\fIkvea.el\fP):
+\fC
+ 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
+\fR
+In this example, the antenna is mechanically tilted downward 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,
+\fBSPLAT!\fP will interpolate the values provided to determine the
+data at the required resolution, although this may result in a loss
+in accuracy.
+
+.SH IMPORTING AND EXPORTING REGIONAL PATH LOSS CONTOUR DATA
+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 coverage 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 \fBSPLAT!\fP
+to rapidly produce a revised path loss map.
+
+For example, a path loss output file can be generated by \fBSPLAT!\fP
+for a receive site 30 feet above ground level over a 50 mile radius
+surrounding a transmitter site to a maximum path loss of 140 dB using
+the following syntax:
+
+\fCsplat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat\fR
+
+\fBSPLAT!\fP path loss output files often exceed 100 megabytes in size.
+They contain information relating to the boundaries of region they describe
+followed by latitudes (degrees North), longitudes (degrees West), azimuths,
+elevations (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 \fBSPLAT!\fP path loss
+output file take on the following appearance (\fIpathloss.dat\fP):
+\fC
+ 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
+\fR
+It is not uncommon for \fBSPLAT!\fP 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 \fBvim\fP
+text editor has proven capable of editing files of this size.
+
+Note as was the case in the antenna pattern files, negative 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 \fI-L\fP switch \fIif\fP the path between transmitter
+and receiver is unobstructed. If the path between the transmitter
+and receiver is obstructed, then the elevation angle to the first
+obstruction is returned by \fBSPLAT!\fP. 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 \fBSPLAT!\fP path loss files to reflect antenna
+pattern data, \fIonly the last column (path loss)\fP 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 \fBSPLAT!\fP for
+generating revised coverage maps:
+
+\fCsplat -t kvea -pli pathloss.dat -s city.dat -b county.dat -o map.ppm\fR
+
+\fBSPLAT!\fP path loss files can also be used for conducting coverage or
+interference studies outside of \fBSPLAT!\fP.
+.SH USER-DEFINED TERRAIN INPUT FILES
+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 \fBSPLAT!\fP analysis being conducted, but noticeably
+absent from the SDF files being used. A user-defined terrain file is imported
+into a \fBSPLAT!\fP analysis using the \fI-udt\fP switch:
+
+\fC splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm\fR
+
+A user-defined terrain file has the following appearance and structure:
+\fC
+ 40.32180556, 74.1325, 100.0 meters
+ 40.321805, 74.1315, 300.0
+ 40.3218055, 74.1305, 100.0 meters
+\fR
+Terrain height is interpreted as being described in feet above ground
+level unless followed by the word \fImeters\fP, and is added \fIon top of\fP
+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. Features described
+in the user-defined terrain file that overlap previously defined features
+in the file are ignored by \fBSPLAT!\fP.
+.SH SIMPLE TOPOGRAPHIC MAP GENERATION
+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 between the sites, the \fI-n\fP
+switch should be invoked as follows:
+
+\fCsplat -t tx_site -r rx_site -n -o topo_map.ppm\fR
+
+If no text report is desired, then the \fI-N\fP switch is used:
+
+\fCsplat -t tx_site -r rx_site -N -o topo_map.ppm\fR
+
+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:
+
+\fCsplat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o topo_map.ppm\fR
+
+where -R specifies the minimum radius of the map in miles (or kilometers
+if the \fI-metric\fP switch is used). Note that the tx_site name and
+location are not displayed in this example. If display of this information
+is desired, simply create a \fBSPLAT!\fP city file (\fI-s\fP option) and
+append it to the list of command-line options illustrated above.
+
+If the \fI-o\fP switch and output filename are omitted in these
+operations, topographic output is written to a file named \fItx_site.ppm\fP
+in the current working directory by default.
+.SH GEOREFERENCE FILE GENERATION
+Topographic, coverage (\fI-c\fP), and path loss contour (\fI-L\fP) maps
+generated by \fBSPLAT!\fP may be imported into \fBXastir\fP (X Amateur
+Station Tracking and Information Reporting) software by generating a
+georeference file using \fBSPLAT!\fP's \fI-geo\fP switch:
+
+\fCsplat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o map.ppm\fR
+
+The georeference file generated will have the same base name as the
+\fI-o\fP file specified, but have a \fI .geo\fP extension, and permit
+proper interpretation and display of \fBSPLAT!\fP's .ppm graphics in
+\fBXastir\fP software.
+.SH GOOGLE MAP KML FILE GENERATION
+Keyhole Markup Language files compatible with \fBGoogle Earth\fP may
+be generated by \fBSPLAT!\fP when performing point-to-point or regional
+coverage analyses by invoking the \fI-kml\fP switch:
+
+\fCsplat -t wnjt-dt -r kd2bd -kml\fR
+
+The KML file generated will have the same filename structure as a
+Path Analysis Report for the transmitter and receiver site names given,
+except it will carry a \fI .kml\fP extension.
+
+Once loaded into \fBGoogle Earth\fP (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 displayed in
+green. \fBGoogle Earth\fP's navigation tools allow the user to
+"fly" around the path, identify landmarks, roads, and other
+featured content.
+
+When performing regional coverage analysis, the \fI .kml\fP file
+generated by \fBSPLAT!\fP will permit path loss or signal strength contours
+to be layered on top of \fBGoogle Earth\fP's display in a semi-transparent
+manner. The generated \fI.kml\fP file will have the same basename as
+that of the \fI.ppm\fP file normally generated.
+.SH DETERMINATION OF ANTENNA HEIGHT ABOVE AVERAGE TERRAIN
+\fBSPLAT!\fP determines antenna height above average terrain (HAAT)
+according to the procedure defined by Federal Communications Commission
+Part 73.313(d). According to this definition, terrain elevations along
+eight radials between 2 and 10 miles (3 and 16 kilometers) from the site
+being analyzed are sampled and averaged for each 45 degrees of azimuth
+starting with True North. If one or more radials lie entirely over water
+or over land outside the United States (areas for which no USGS topography
+data is available), then those radials are omitted from the calculation
+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 compliance with FCC Part 73.313(d)
+in areas along the borders of the United States if the SDF files
+used by \fBSPLAT!\fP are SRTM-derived.
+
+When performing point-to-point terrain analysis, \fBSPLAT!\fP 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 data in
+memory.
+
+When performing area prediction analysis, enough topography data is
+normally loaded by \fBSPLAT!\fP to perform average terrain calculations.
+Under such conditions, \fBSPLAT!\fP 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, \fBSPLAT!\fP reports \fINo Terrain\fP
+for the radial paths affected.
+.SH RESTRICTING THE MAXIMUM SIZE OF AN ANALYSIS REGION
+\fBSPLAT!\fP reads SDF files as needed into a series of memory "pages"
+within the structure of the program. Each "page" holds one SDF file
+representing a one degree by one degree region of terrain.
+A \fI#define MAXPAGES\fP statement in the first several lines of
+\fIsplat.cpp\fP sets the maximum number of "pages" available for holding
+topography data. It also sets the maximum size of the topographic maps
+generated by \fBSPLAT!\fP. MAXPAGES is set to 9 by default. If \fBSPLAT!\fP
+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 \fBSPLAT!\fP with the number of MAXPAGES specified. In situations where
+available memory is low, MAXPAGES may be reduced to 4 with the understanding
+that this will greatly limit the maximum region \fBSPLAT!\fP will be able
+to analyze. If 118 megabytes or more of total memory (swap space plus
+RAM) is available, then MAXPAGES 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.
+.SH ADDITIONAL INFORMATION
+The latest news and information regarding \fBSPLAT!\fP software is
+available through the official \fBSPLAT!\fP software web page located
+at: \fIhttp://www.qsl.net/kd2bd/splat.html\fP.
+.SH AUTHORS
+.TP
+John A. Magliacane, KD2BD <\fIkd2bd@amsat.org\fP>
+Creator, Lead Developer
+.TP
+Doug McDonald <\fImcdonald@scs.uiuc.edu\fP>
+Original Longley-Rice Model integration
+.TP
+Ron Bentley <\fIronbentley@earthlink.net\fP>
+Fresnel Zone plotting and clearance determination
+
--- /dev/null
+%!PS-Adobe-3.0
+%%Creator: groff version 1.17.2
+%%CreationDate: Fri Oct 19 15:57:12 2007
+%%DocumentNeededResources: font Times-Roman
+%%+ font Times-Bold
+%%+ font Times-Italic
+%%+ font Courier
+%%+ font Symbol
+%%DocumentSuppliedResources: procset grops 1.17 2
+%%Pages: 17
+%%PageOrder: Ascend
+%%Orientation: Portrait
+%%EndComments
+%%BeginProlog
+%%BeginResource: procset grops 1.17 2
+/setpacking where{
+pop
+currentpacking
+true setpacking
+}if
+/grops 120 dict dup begin
+/SC 32 def
+/A/show load def
+/B{0 SC 3 -1 roll widthshow}bind def
+/C{0 exch ashow}bind def
+/D{0 exch 0 SC 5 2 roll awidthshow}bind def
+/E{0 rmoveto show}bind def
+/F{0 rmoveto 0 SC 3 -1 roll widthshow}bind def
+/G{0 rmoveto 0 exch ashow}bind def
+/H{0 rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
+/I{0 exch rmoveto show}bind def
+/J{0 exch rmoveto 0 SC 3 -1 roll widthshow}bind def
+/K{0 exch rmoveto 0 exch ashow}bind def
+/L{0 exch rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
+/M{rmoveto show}bind def
+/N{rmoveto 0 SC 3 -1 roll widthshow}bind def
+/O{rmoveto 0 exch ashow}bind def
+/P{rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
+/Q{moveto show}bind def
+/R{moveto 0 SC 3 -1 roll widthshow}bind def
+/S{moveto 0 exch ashow}bind def
+/T{moveto 0 exch 0 SC 5 2 roll awidthshow}bind def
+/SF{
+findfont exch
+[exch dup 0 exch 0 exch neg 0 0]makefont
+dup setfont
+[exch/setfont cvx]cvx bind def
+}bind def
+/MF{
+findfont
+[5 2 roll
+0 3 1 roll
+neg 0 0]makefont
+dup setfont
+[exch/setfont cvx]cvx bind def
+}bind def
+/level0 0 def
+/RES 0 def
+/PL 0 def
+/LS 0 def
+/MANUAL{
+statusdict begin/manualfeed true store end
+}bind def
+/PLG{
+gsave newpath clippath pathbbox grestore
+exch pop add exch pop
+}bind def
+/BP{
+/level0 save def
+1 setlinecap
+1 setlinejoin
+72 RES div dup scale
+LS{
+90 rotate
+}{
+0 PL translate
+}ifelse
+1 -1 scale
+}bind def
+/EP{
+level0 restore
+showpage
+}bind def
+/DA{
+newpath arcn stroke
+}bind def
+/SN{
+transform
+.25 sub exch .25 sub exch
+round .25 add exch round .25 add exch
+itransform
+}bind def
+/DL{
+SN
+moveto
+SN
+lineto stroke
+}bind def
+/DC{
+newpath 0 360 arc closepath
+}bind def
+/TM matrix def
+/DE{
+TM currentmatrix pop
+translate scale newpath 0 0 .5 0 360 arc closepath
+TM setmatrix
+}bind def
+/RC/rcurveto load def
+/RL/rlineto load def
+/ST/stroke load def
+/MT/moveto load def
+/CL/closepath load def
+/FL{
+currentgray exch setgray fill setgray
+}bind def
+/BL/fill load def
+/LW/setlinewidth load def
+/RE{
+findfont
+dup maxlength 1 index/FontName known not{1 add}if dict begin
+{
+1 index/FID ne{def}{pop pop}ifelse
+}forall
+/Encoding exch def
+dup/FontName exch def
+currentdict end definefont pop
+}bind def
+/DEFS 0 def
+/EBEGIN{
+moveto
+DEFS begin
+}bind def
+/EEND/end load def
+/CNT 0 def
+/level1 0 def
+/PBEGIN{
+/level1 save def
+translate
+div 3 1 roll div exch scale
+neg exch neg exch translate
+0 setgray
+0 setlinecap
+1 setlinewidth
+0 setlinejoin
+10 setmiterlimit
+[]0 setdash
+/setstrokeadjust where{
+pop
+false setstrokeadjust
+}if
+/setoverprint where{
+pop
+false setoverprint
+}if
+newpath
+/CNT countdictstack def
+userdict begin
+/showpage{}def
+}bind def
+/PEND{
+clear
+countdictstack CNT sub{end}repeat
+level1 restore
+}bind def
+end def
+/setpacking where{
+pop
+setpacking
+}if
+%%EndResource
+%%IncludeResource: font Times-Roman
+%%IncludeResource: font Times-Bold
+%%IncludeResource: font Times-Italic
+%%IncludeResource: font Courier
+%%IncludeResource: font Symbol
+grops begin/DEFS 1 dict def DEFS begin/u{.001 mul}bind def end/RES 72
+def/PL 792 def/LS false def/ENC0[/asciicircum/asciitilde/Scaron/Zcaron
+/scaron/zcaron/Ydieresis/trademark/quotesingle/.notdef/.notdef/.notdef
+/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef
+/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef
+/.notdef/.notdef/space/exclam/quotedbl/numbersign/dollar/percent
+/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen
+/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon
+/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O
+/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/circumflex
+/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y
+/z/braceleft/bar/braceright/tilde/.notdef/quotesinglbase/guillemotleft
+/guillemotright/bullet/florin/fraction/perthousand/dagger/daggerdbl
+/endash/emdash/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/hungarumlaut
+/dotaccent/breve/caron/ring/ogonek/quotedblleft/quotedblright/oe/lslash
+/quotedblbase/OE/Lslash/.notdef/exclamdown/cent/sterling/currency/yen
+/brokenbar/section/dieresis/copyright/ordfeminine/guilsinglleft
+/logicalnot/minus/registered/macron/degree/plusminus/twosuperior
+/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior
+/ordmasculine/guilsinglright/onequarter/onehalf/threequarters
+/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE
+/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex
+/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis
+/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn
+/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla
+/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis
+/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash
+/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis]def
+/Courier@0 ENC0/Courier RE/Times-Italic@0 ENC0/Times-Italic RE
+/Times-Bold@0 ENC0/Times-Bold RE/Times-Roman@0 ENC0/Times-Roman RE
+%%EndProlog
+%%Page: 1 1
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10.95
+/Times-Bold@0 SF -.219(NA)72 84 S(ME).219 E F0(splat \255 An RF)108 96 Q
+/F2 10/Times-Bold@0 SF(S)2.5 E F0(ignal)A F2(P)2.5 E F0(ropag)A(ation,)
+-.05 E F2(L)2.5 E F0(oss,)A F2(A)2.5 E F0(nd)A F2(T)2.5 E F0
+(errain analysis tool)A F1(SYNOPSIS)72 112.8 Q F0 2.893(splat [-t)108
+124.8 R/F3 10/Times-Italic@0 SF(tr)7.893 E(ansmitter_site)-.15 E(.qth)
+-.15 E F0 5.393(][)C(-r)-5.393 E F3 -.37(re)5.393 G(ceiver_site).37 E
+(.qth)-.15 E F0 5.393(][)C(-c)-5.393 E F3 2.892
+(rx antenna height for LOS co)5.393 F(ver)-.1 E 3.092 -.1(age a)-.15 H
+(nalysis).1 E(\(feet/meter)108 136.8 Q .399(s\) \(\215oat\))-.1 F F0
+2.899(][)C(-L)-2.899 E F3 .399(rx antenna height for Longle)2.899 F .399
+(y-Rice co)-.3 F(ver)-.1 E .599 -.1(age a)-.15 H .399
+(nalysis \(feet/meter).1 F .4(s\) \(\215oat\))-.1 F F0 2.9(][)C(-p)-2.9
+E F3(ter)2.9 E(-)-.2 E -.15(ra)108 148.8 S(in_pr).15 E(o\214le)-.45 E
+(.e)-.15 E(xt)-.2 E F0 2.85(][)C(-e)-2.85 E F3(ele)2.85 E(vation_pr)-.15
+E(o\214le)-.45 E(.e)-.15 E(xt)-.2 E F0 2.85(][)C(-h)-2.85 E F3
+(height_pr)2.85 E(o\214le)-.45 E(.e)-.15 E(xt)-.2 E F0 2.85(][)C(-H)
+-2.85 E F3(normalized_height_pr)2.85 E(o\214le)-.45 E(.e)-.15 E(xt)-.2 E
+F0 2.85(][)C(-l)-2.85 E F3(Lon-)2.85 E(gle)108 160.8 Q(y-Rice_pr)-.3 E
+(o\214le)-.45 E(.e)-.15 E(xt)-.2 E F0 5.518(][)C(-o)-5.518 E F3(topo)
+5.518 E(gr)-.1 E(aphic_map_\214lename)-.15 E(.ppm)-.15 E F0 5.518(][)C
+(-b)-5.518 E F3(carto)5.518 E(gr)-.1 E(aphic_boundary_\214lename)-.15 E
+(.dat)-.15 E F0 5.518(][)C(-s)-5.518 E F3(site/city_database)108 172.8 Q
+(.dat)-.15 E F0 3.236(][)C(-d)-3.236 E F3(sdf_dir)3.236 E(ectory_path)
+-.37 E F0 3.236(][)C(-m)-3.236 E F3 .736(earth r)3.236 F .735
+(adius multiplier \(\215oat\))-.15 F F0 3.235(][)C(-f)-3.235 E F3(fr)
+3.235 E .735(equency \(MHz\) for)-.37 F -1.77 -.55(Fr e)108 184.8 T .815
+(snel zone calculations \(\215oat\)).55 F F0 3.315(][)C(-R)-3.315 E F3
+.815(maximum co)3.315 F(ver)-.1 E 1.016 -.1(age r)-.15 H .816
+(adius \(miles/kilometer)-.05 F .816(s\) \(\215oat\))-.1 F F0 3.316(][)C
+(-dB)-3.316 E F3(maximum)3.316 E 1.732
+(attenuation contour to display on path loss maps \(80-230 dB\))108
+196.8 R F0 4.232(][)C(-fz)-4.232 E F3 -1.77 -.55(Fr e)4.232 H 1.732
+(snel zone clear).55 F 1.732(ance per)-.15 F(centa)-.37 E -.1(ge)-.1 G
+4.055(\(default = 60\))108 208.8 R F0 6.555(][)C(-plo)-6.555 E F3
+(path_loss_output_\214le)6.555 E(.txt)-.15 E F0 6.555(][)C(-pli)-6.555 E
+F3(path_loss_input_\214le)6.555 E(.txt)-.15 E F0 6.555(][)C(-udt)-6.555
+E F3(user_de\214ned_ter)6.555 E(-)-.2 E -.15(ra)108 220.8 S(in_\214le)
+.15 E(.dat)-.15 E F0 2.5(][)C
+(-n] [-N] [-nf] [-ngs] [-geo] [-kml] [-metric])-2.5 E F1(DESCRIPTION)72
+237.6 Q F2(SPLA)108 249.6 Q(T!)-.95 E F0 1.499(is a po)3.999 F 1.499
+(werful terrestrial RF propag)-.25 F 1.498
+(ation and terrain analysis tool for the spectrum between 20)-.05 F .157
+(MHz and 20 GHz.)108 261.6 R F2(SPLA)5.157 E(T!)-.95 E F0 .157
+(is free softw)2.657 F .158
+(are, and is designed for operation on Unix and Linux-based w)-.1 F
+(ork-)-.1 E 4.744(stations. Redistrib)108 273.6 R 2.244(ution and/or mo\
+di\214cation is permitted under the terms of the GNU General Public)-.2
+F .883(License, V)108 285.6 R .883
+(ersion 2, as published by the Free Softw)-1.11 F .883(are F)-.1 F 3.383
+(oundation. Adoption)-.15 F(of)3.384 E F2(SPLA)3.384 E(T!)-.95 E F0 .884
+(source code in)5.884 F(proprietary or closed-source applications is a \
+violation of this license and is)108 297.6 Q F2(strictly)2.5 E F0
+(forbidden.)2.5 E F2(SPLA)108 321.6 Q(T!)-.95 E F0 .531(is distrib)3.031
+F .531(uted in the hope that it will be useful, b)-.2 F .53
+(ut WITHOUT ANY W)-.2 F(ARRANTY)-1.2 E 3.03(,w)-1.29 G .53(ithout e)
+-3.03 F -.15(ve)-.25 G(n).15 E .75(the implied w)108 333.6 R .751
+(arranty of MERCHANT)-.1 F .751(ABILITY or FITNESS FOR A P)-.93 F(AR)
+-.92 E .751(TICULAR PURPOSE.)-.6 F .751(See the)5.751 F
+(GNU General Public License for more details.)108 345.6 Q F1(INTR)72
+362.4 Q(ODUCTION)-.329 E F0 .575(Applications of)108 374.4 R F2(SPLA)
+3.075 E(T!)-.95 E F0 .574(include the visualization, design, and link b)
+3.075 F .574(udget analysis of wireless W)-.2 F .574(ide Area)-.4 F
+(Netw)108 386.4 Q 1.939(orks \(W)-.1 F 1.939
+(ANs\), commercial and amateur radio communication systems abo)-1.2 F
+2.239 -.15(ve 2)-.15 H 4.439(0M).15 G 1.94(Hz, micro)-4.439 F -.1(wa)
+-.25 G -.15(ve)-.1 G 1.091(links, frequenc)108 398.4 R 3.591(yc)-.15 G
+1.091(oordination and interference studies, and the prediction of analo\
+g and digital terrestrial)-3.591 F(radio and tele)108 410.4 Q
+(vision contour re)-.25 E(gions.)-.15 E F2(SPLA)108 434.4 Q(T!)-.95 E F0
+(pro)4.69 E 2.191(vides RF site engineering data such as great circle d\
+istances and bearings between sites,)-.15 F 2.725(antenna ele)108 446.4
+R -.25(va)-.25 G 2.724(tion angles \(uptilt\), depression angles \(do)
+.25 F 2.724(wntilt\), antenna height abo)-.25 F 3.024 -.15(ve m)-.15 H
+2.724(ean sea le).15 F -.15(ve)-.25 G(l,).15 E .858(antenna height abo)
+108 458.4 R 1.158 -.15(ve a)-.15 H -.15(ve)-.05 G .858
+(rage terrain, bearings, distances, and ele).15 F -.25(va)-.25 G .859
+(tions to kno).25 F .859(wn obstructions, Longle)-.25 F(y-)-.15 E .381
+(Rice path attenuation, and recei)108 470.4 R -.15(ve)-.25 G 2.881(ds)
+.15 G .381(ignal strength.)-2.881 F .381
+(In addition, the minimum antenna height requirements)5.381 F .096
+(needed to clear terrain, the \214rst Fresnel zone, and an)108 482.4 R
+2.597(yu)-.15 G(ser)-2.597 E .097
+(-de\214nable percentage of the \214rst Fresnel zone are)-.2 F(also pro)
+108 494.4 Q(vided.)-.15 E F2(SPLA)108 518.4 Q(T!)-.95 E F0 .102(produce\
+s reports, graphs, and high resolution topographic maps that depict lin\
+e-of-sight paths, and)2.603 F(re)108 530.4 Q .668
+(gional path loss and signal strength contours through which e)-.15 F
+.668(xpected co)-.15 F -.15(ve)-.15 G .668
+(rage areas of transmitters and).15 F .649
+(repeater systems can be obtained.)108 542.4 R .648
+(When performing line-of-sight and Longle)5.648 F .648
+(y-Rice analyses in situations)-.15 F .344
+(where multiple transmitter or repeater sites are emplo)108 554.4 R
+(yed,)-.1 E F2(SPLA)2.845 E(T!)-.95 E F0 .345(determines indi)2.845 F
+.345(vidual and mutual areas)-.25 F(of co)108 566.4 Q -.15(ve)-.15 G
+(rage within the netw).15 E(ork speci\214ed.)-.1 E(Simply typing)108
+590.4 Q/F4 10/Courier@0 SF(splat)2.5 E F0
+(on the command line will return a summary of)2.5 E F2(SPLA)2.5 E(T!)
+-.95 E F0 1.1 -.55('s c)D(ommand line options:).55 E F4
+(--==[ SPLAT! v1.2.1 Available Options... ]==--)186 626.4 Q
+(-t txsite\(s\).qth \(max of 4 with -c, max of 30 with -L\))138 650.4 Q
+(-r rxsite.qth)138 662.4 Q
+(-c plot coverage of TX\(s\) with an RX antenna at X feet/meters AGL)138
+674.4 Q(-L plot path loss map of TX based on an RX at X feet/meters AGL)
+138 686.4 Q(-s filename\(s\) of city/site file\(s\) to import \(5 max\))
+138 698.4 Q(-b filename\(s\) of cartographic boundary file\(s\) to impo\
+rt \(5 max\))138 710.4 Q(-p filename of terrain profile graph to plot)
+138 722.4 Q F0(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F(September 2007)
+2.5 E(1)190.115 E EP
+%%Page: 2 2
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(-e filename of terrain elevation graph to plot)138 84 Q
+(-h filename of terrain height graph to plot)138 96 Q
+(-H filename of normalized terrain height graph to plot)138 108 Q
+(-l filename of Longley-Rice graph to plot)138 120 Q
+(-o filename of topographic map to generate \(.ppm\))138 132 Q
+(-u filename of user-defined terrain file to import)138 144 Q
+(-d sdf file directory path \(overrides path in ~/.splat_path file\))138
+156 Q(-m earth radius multiplier)138 168 Q
+(-n do not plot LOS paths in .ppm maps)138 180 Q
+(-N do not produce unnecessary site or obstruction reports)138 192 Q
+(-f frequency for Fresnel zone calculation \(MHz\))138 204 Q
+(-R modify default range for -c or -L \(miles/kilometers\))138 216 Q
+(-db maximum loss contour to display on path loss maps \(80-230 dB\))132
+228 Q(-nf do not plot Fresnel zones in height plots)132 240 Q
+(-fz Fresnel zone clearance percentage \(default = 60\))132 252 Q
+(-ngs display greyscale topography as white in .ppm files)126 264 Q
+(-erp override ERP in .lrp file \(Watts\))126 276 Q
+(-pli filename of path-loss input file)126 288 Q
+(-plo filename of path-loss output file)126 300 Q
+(-udt filename of user defined terrain input file)126 312 Q
+(-kml generate Google Earth \(.kml\) compatible output)126 324 Q 2.667
+(-geo generate an Xastir .geo georeference file \(with .ppm output\))126
+336 R(-metric employ metric rather than imperial units for all user I/O)
+108 348 Q/F2 10.95/Times-Bold@0 SF(INPUT FILES)72 376.8 Q/F3 10
+/Times-Bold@0 SF(SPLA)108 388.8 Q(T!)-.95 E F0 .663
+(is a command-line dri)3.163 F -.15(ve)-.25 G 3.164(na).15 G .664
+(pplication and reads input data through a number of data \214les.)
+-3.164 F(Some)5.664 E 1.42(\214les are mandatory for successful e)108
+400.8 R -.15(xe)-.15 G 1.42
+(cution of the program, while others are optional.).15 F 1.42
+(Mandatory \214les)6.42 F 1.085(include 3-arc second topograph)108 412.8
+R 3.585(ym)-.05 G 1.085(odels in the form of SPLA)-3.585 F 3.585(TD)
+-1.11 G 1.085(ata Files \(SDF \214les\), site location \214les)-3.585 F
+.395(\(QTH \214les\), and Longle)108 424.8 R .394
+(y-Rice model parameter \214les \(LRP \214les\).)-.15 F .394
+(Optional \214les include city location \214les,)5.394 F .929
+(cartographic boundary \214les, user)108 436.8 R .929(-de\214ned terrai\
+n \214les, path-loss input \214les, antenna radiation pattern \214les,)
+-.2 F(and color de\214nition \214les.)108 448.8 Q F2(SPLA)72 465.6 Q
+2.738(TD)-1.04 G -1.644 -1.04(AT A)-3.121 H(FILES)3.778 E F3(SPLA)108
+477.6 Q(T!)-.95 E F0 .43(imports topographic data in the form of SPLA)
+2.93 F 2.93(TD)-1.11 G .43(ata Files \(SDFs\).)-2.93 F .43
+(These \214les may be generated)5.43 F .737
+(from a number of information sources.)108 489.6 R .737
+(In the United States, SPLA)5.737 F 3.237(TD)-1.11 G .737
+(ata Files can be generated through)-3.237 F 5.442(U.S. Geological)108
+501.6 R(Surv)5.442 E 3.242 -.15(ey D)-.15 H 2.942(igital Ele).15 F -.25
+(va)-.25 G 2.942(tion Models \(DEMs\) using the).25 F F3(usgs2sdf)5.441
+E F0 2.941(utility included with)5.441 F F3(SPLA)108 513.6 Q(T!)-.95 E
+F0 8.595(.U)C 3.595(SGS Digital Ele)-8.595 F -.25(va)-.25 G 3.595
+(tion Models compatible with this utility may be do).25 F 3.595
+(wnloaded from:)-.25 F/F4 10/Times-Italic@0 SF(http://edcftp.cr)108
+525.6 Q(.usgs.go)-1.11 E(v/pub/data/DEM/250/)-.1 E F0(.)A .798
+(Signi\214cantly better resolution and accurac)108 549.6 R 3.298(yc)-.15
+G .798(an be obtained through the use of SR)-3.298 F .798(TM-3 V)-.6 F
+.798(ersion 2 digital)-1.11 F(ele)108 561.6 Q -.25(va)-.25 G .659
+(tion models.).25 F .659
+(These models are the product of the STS-99 Space Shuttle Radar T)5.659
+F(opograph)-.8 E 3.16(yM)-.05 G(ission,)-3.16 E .046(and are a)108 573.6
+R -.25(va)-.2 G .046(ilable for most populated re).25 F .045
+(gions of the Earth.)-.15 F(SPLA)5.045 E 2.545(TD)-1.11 G .045
+(ata Files may be generated from SR)-2.545 F(TM)-.6 E .061
+(data using the included)108 585.6 R F3(srtm2sdf)2.561 E F0(utility)
+2.561 E 5.061(.S)-.65 G -.6(RT)-5.061 G .061(M-3 V).6 F .062
+(ersion 2 data may be obtained through anon)-1.11 F .062(ymous FTP)-.15
+F(from:)108 597.6 Q F4(ftp://e0srp01u.ecs.nasa.go)2.5 E(v:21/srtm/ver)
+-.1 E(sion2/)-.1 E F0(The)108 621.6 Q F3(strm2sdf)3.707 E F0 1.207
+(utility may also be used to con)3.707 F -.15(ve)-.4 G 1.206
+(rt 3-arc second SR).15 F 1.206(TM data in Band Interlea)-.6 F -.15(ve)
+-.2 G 3.706(db).15 G 3.706(yL)-3.706 G(ine)-3.706 E 1.106
+(\(.BIL\) format for use with)108 633.6 R F3(SPLA)3.606 E(T!)-.95 E F0
+6.106(.T)C 1.106(his data is a)-6.106 F -.25(va)-.2 G 1.107
+(ilable via the web at:).25 F F4(http://seamless.usgs.go)3.607 E(v/web-)
+-.1 E(site/seamless/)108 645.6 Q F0 2.121(Band Interlea)108 669.6 R -.15
+(ve)-.2 G 4.621(db).15 G 4.621(yL)-4.621 G 2.121(ine data must be do)
+-4.621 F 2.121(wnloaded in a v)-.25 F 2.12
+(ery speci\214c manner to be compatible with)-.15 F F3(srtm2sdf)108
+681.6 Q F0(and)3.904 E F3(SPLA)3.904 E(T!)-.95 E F0 6.404(.P)C 1.404
+(lease consult)-6.404 F F3(srtm2sdf)3.904 E F0 2.505 -.55('s d)D 1.405
+(ocumentation for instructions on do).55 F 1.405(wnloading .BIL)-.25 F
+(topographic data through the USGS')108 693.6 Q 2.5(sS)-.55 G(eamless W)
+-2.5 E(eb Site.)-.8 E .241(Despite the higher accurac)108 717.6 R 2.741
+(yt)-.15 G .241(hat SR)-2.741 F .241(TM data has to of)-.6 F(fer)-.25 E
+2.741(,s)-.4 G .241(ome v)-2.741 F .241(oids in the data sets e)-.2 F
+2.741(xist. When)-.15 F -.2(vo)2.741 G .241(ids are).2 F .332
+(detected, the)108 729.6 R F3(srtm2sdf)2.832 E F0 .332
+(utility replaces them with corresponding data found in e)2.832 F .332
+(xisting SDF \214les \(that were)-.15 F(KD2BD Softw)72 768 Q 120.785
+(are 16)-.1 F(September 2007)2.5 E(2)190.115 E EP
+%%Page: 3 3
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .034
+(presumably created from earlier USGS data through the)108 84 R/F1 10
+/Times-Bold@0 SF(usgs2sdf)2.533 E F0 2.533(utility\). If)2.533 F
+(USGS-deri)2.533 E -.15(ve)-.25 G 2.533(dS).15 G .033(DF data is not)
+-2.533 F -.2(av)108 96 S(ailable, v)-.05 E
+(oids are handled through adjacent pix)-.2 E(el a)-.15 E -.15(ve)-.2 G
+(raging, or direct replacement.).15 E(SPLA)108 120 Q 2.782(TD)-1.11 G
+.282(ata Files contain inte)-2.782 F .282(ger v)-.15 F .282
+(alue topographic ele)-.25 F -.25(va)-.25 G .282
+(tions \(in meters\) referenced to mean sea le).25 F -.15(ve)-.25 G
+2.782(lf).15 G(or)-2.782 E(1-de)108 132 Q .062(gree by 1-de)-.15 F .062
+(gree re)-.15 F .062
+(gions of the earth with a resolution of 3-arc seconds.)-.15 F .061
+(SDF \214les can be read in either)5.061 F .711(standard format \()108
+144 R/F2 10/Times-Italic@0 SF(.sdf)A F0 3.211(\)a)C 3.211(sg)-3.211 G
+.711(enerated by the)-3.211 F F1(usgs2sdf)3.211 E F0(and)3.211 E F1
+(srtm2sdf)3.211 E F0 .712(utilities, or in bzip2 compressed format)3.211
+F(\()108 156 Q F2(.sdf)A(.bz2)-.15 E F0 4.655(\). Since)B 2.155
+(uncompressed \214les can be read slightly f)4.655 F 2.155
+(aster than \214les that ha)-.1 F 2.455 -.15(ve b)-.2 H 2.155
+(een compressed,).15 F F1(SPLA)108 168 Q(T!)-.95 E F0 1.764
+(searches for needed SDF data in uncompressed format \214rst.)4.264 F
+1.765(If uncompressed data cannot be)6.764 F(located,)108 180 Q F1(SPLA)
+3.471 E(T!)-.95 E F0 .971
+(then searches for data in bzip2 compressed format.)3.471 F .97
+(If no compressed SDF \214les can be)5.971 F .778(found for the re)108
+192 R .778(gion requested,)-.15 F F1(SPLA)3.278 E(T!)-.95 E F0 .778
+(assumes the re)3.278 F .778(gion is o)-.15 F -.15(ve)-.15 G 3.278(rw)
+.15 G(ater)-3.378 E 3.278(,a)-.4 G .779(nd will assign an ele)-3.278 F
+-.25(va)-.25 G .779(tion of).25 F(sea-le)108 204 Q -.15(ve)-.25 G 2.5
+(lt).15 G 2.5(ot)-2.5 G(hese areas.)-2.5 E 1.062(This feature of)108 228
+R F1(SPLA)3.562 E(T!)-.95 E F0(mak)3.561 E 1.061
+(es it possible to perform path analysis not only o)-.1 F -.15(ve)-.15 G
+3.561(rl).15 G 1.061(and, b)-3.561 F 1.061(ut also between)-.2 F .554
+(coastal areas not represented by Digital Ele)108 240 R -.25(va)-.25 G
+.554(tion Model data.).25 F(Ho)5.554 E(we)-.25 E -.15(ve)-.25 G 1.354
+-.4(r, t).15 H .555(his beha).4 F .555(vior of)-.2 F F1(SPLA)3.055 E(T!)
+-.95 E F0(under)5.555 E(-)-.2 E 1.575(scores the importance of ha)108
+252 R 1.575(ving all the SDF \214les required for the re)-.2 F 1.575
+(gion being analyzed if meaningful)-.15 F(results are to be e)108 264 Q
+(xpected.)-.15 E/F3 10.95/Times-Bold@0 SF(SITE LOCA)72 280.8 Q
+(TION \(QTH\) FILES)-1.04 E F1(SPLA)108 292.8 Q(T!)-.95 E F0 .838
+(imports site location information of transmitter and recei)3.338 F -.15
+(ve)-.25 G 3.339(rs).15 G .839(ites analyzed by the program from)-3.339
+F .376(ASCII \214les ha)108 304.8 R .376(ving a)-.2 F F2(.qth)2.876 E F0
+-.15(ex)2.876 G 2.875(tension. QTH).15 F .375(\214les contain the site')
+2.875 F 2.875(sn)-.55 G .375(ame, the site')-2.875 F 2.875(sl)-.55 G
+.375(atitude \(positi)-2.875 F .675 -.15(ve i)-.25 H 2.875(fN).15 G
+(orth)-2.875 E .388(of the equator)108 316.8 R 2.888(,n)-.4 G -2.25 -.15
+(eg a)-2.888 H(ti).15 E .688 -.15(ve i)-.25 H 2.888(fS).15 G .388
+(outh\), the site')-2.888 F 2.888(sl)-.55 G .388(ongitude \(in de)-2.888
+F .388(grees W)-.15 F .389(est, 0 to 360 de)-.8 F .389(grees, or de)-.15
+F .389(grees East 0)-.15 F .639(to -360 de)108 328.8 R .639
+(grees\), and the site')-.15 F 3.138(sa)-.55 G .638(ntenna height abo)
+-3.138 F .938 -.15(ve g)-.15 H .638(round le).15 F -.15(ve)-.25 G 3.138
+(l\().15 G -.4(AG)-3.138 G .638(L\), each separated by a single line-).4
+F .371(feed character)108 340.8 R 5.371(.T)-.55 G .371
+(he antenna height is assumed to be speci\214ed in feet unless follo)
+-5.371 F .372(wed by the letter)-.25 F F2(m)2.872 E F0 .372(or the)2.872
+F -.1(wo)108 352.8 S(rd).1 E F2(meter)3.085 E(s)-.1 E F0 .585
+(in either upper or lo)3.085 F .584(wer case.)-.25 F .584
+(Latitude and longitude information may be e)5.584 F .584
+(xpressed in either)-.15 F(decimal format \(74.6864\) or de)108 364.8 Q
+(gree, minute, second \(DMS\) format \(74 41 11.0\).)-.15 E -.15(Fo)108
+388.8 S 3.771(re).15 G 1.271
+(xample, a site location \214le describing tele)-3.921 F 1.272
+(vision station WNJT)-.25 F(-DT)-.92 E 3.772(,T)-.74 G 1.272
+(renton, NJ \()-4.122 F F2(wnjt-dt.qth)A F0 3.772(\)m)C(ight)-3.772 E
+(read as follo)108 400.8 Q(ws:)-.25 E/F4 10/Courier@0 SF(WNJT-DT)156
+424.8 Q(40.2828)156 436.8 Q(74.6864)156 448.8 Q(990.00)156 460.8 Q F0
+.23(Each transmitter and recei)108 484.8 R -.15(ve)-.25 G 2.73(rs).15 G
+.23(ite analyzed by)-2.73 F F1(SPLA)2.73 E(T!)-.95 E F0 .23
+(must be represented by its o)2.73 F .23(wn site location \(QTH\))-.25 F
+(\214le.)108 496.8 Q F3(LONGLEY)72 513.6 Q(-RICE P)-1.007 E
+(ARAMETER \(LRP\) FILES)-.81 E F0(Longle)108 525.6 Q 1.081
+(y-Rice parameter data \214les are required for)-.15 F F1(SPLA)3.581 E
+(T!)-.95 E F0 1.082(to determine RF path loss in either point-to-)3.581
+F .292(point or area prediction mode.)108 537.6 R(Longle)5.291 E .291
+(y-Rice model parameter data is read from \214les ha)-.15 F .291
+(ving the same base)-.2 F(name as the transmitter site QTH \214le, b)108
+549.6 Q(ut with a format \()-.2 E F2(wnjt-dt.lrp)A F0(\):)A F4 6
+(15.000 ;)156 573.6 R
+(Earth Dielectric Constant \(Relative permittivity\))6 E 12(0.005 ;)156
+585.6 R(Earth Conductivity \(Siemens per meter\))6 E
+(301.000 ; Atmospheric Bending Constant \(N-units\))156 597.6 Q
+(647.000 ; Frequency in MHz \(20 MHz to 20 GHz\))156 609.6 Q 42(5;)156
+621.6 S(Radio Climate \(5 = Continental Temperate\))-36 E 42(0;)156
+633.6 S(Polarization \(0 = Horizontal, 1 = Vertical\))-36 E 18(0.50 ;)
+156 645.6 R(Fraction of situations \(50% of locations\))6 E 18(0.90 ;)
+156 657.6 R(Fraction of time \(90% of the time\))6 E
+(46000.0 ; ERP in Watts \(optional\))156 669.6 Q F0 .77(If an LRP \214l\
+e corresponding to the tx_site QTH \214le cannot be found,)108 693.6 R
+F1(SPLA)3.271 E(T!)-.95 E F0 .771(scans the current w)3.271 F(orking)-.1
+E 1.004(directory for the \214le "splat.lrp".)108 705.6 R 1.004
+(If this \214le cannot be found, then def)6.004 F 1.003
+(ault parameters will be assigned by)-.1 F F1(SPLA)108 717.6 Q(T!)-.95 E
+F0 .454(and a corresponding "splat.lrp" \214le containing these def)
+2.954 F .455(ault parameters will be written to the cur)-.1 F(-)-.2 E
+(rent w)108 729.6 Q(orking directory)-.1 E 5(.T)-.65 G(he generated "sp\
+lat.lrp" \214le can then be edited by the user as needed.)-5 E
+(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(3)
+190.115 E EP
+%%Page: 4 4
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E -.8(Ty)108 84 S
+(pical Earth dielectric constants and conducti).8 E(vity v)-.25 E
+(alues are as follo)-.25 E(ws:)-.25 E/F1 10/Courier@0 SF
+(Dielectric Constant)270 108 Q(Conductivity)12 E(Salt water)156 120 Q 48
+(:8)42 G 96(05)-48 G(.000)-96 E(Good ground)156 132 Q 48(:2)36 G 96(50)
+-48 G(.020)-96 E(Fresh water)156 144 Q 48(:8)36 G 96(00)-48 G(.010)-96 E
+(Marshy land)156 156 Q 48(:1)36 G 96(20)-48 G(.007)-96 E
+(Farmland, forest :)156 168 Q 90(15 0.005)48 F(Average ground)156 180 Q
+48(:1)18 G 96(50)-48 G(.005)-96 E(Mountain, sand)156 192 Q 48(:1)18 G 96
+(30)-48 G(.002)-96 E 72(City :)156 204 R 96(50)54 G(.001)-96 E
+(Poor ground)156 216 Q -18 54(:4 0)36 H(.001)-54 E F0
+(Radio climate codes used by)108 240 Q/F2 10/Times-Bold@0 SF(SPLA)2.5 E
+(T!)-.95 E F0(are as follo)2.5 E(ws:)-.25 E F1(1: Equatorial \(Congo\))
+156 264 Q(2: Continental Subtropical \(Sudan\))156 276 Q
+(3: Maritime Subtropical \(West coast of Africa\))156 288 Q
+(4: Desert \(Sahara\))156 300 Q(5: Continental Temperate)156 312 Q
+(6: Maritime Temperate, over land \(UK and west coasts of US & EU\))156
+324 Q(7: Maritime Temperate, over sea)156 336 Q F0 1.486
+(The Continental T)108 360 R 1.486(emperate climate is common to lar)-.7
+F 1.486(ge land masses in the temperate zone, such as the)-.18 F .756
+(United States.)108 372 R -.15(Fo)5.756 G 3.256(rp).15 G .756
+(aths shorter than 100 km, there is little dif)-3.256 F .756
+(ference between Continental and Maritime)-.25 F -.7(Te)108 384 S
+(mperate climates.).7 E .12(The se)108 408 R -.15(ve)-.25 G .12
+(nth and eighth parameters in the).15 F/F3 10/Times-Italic@0 SF(.lrp)
+2.62 E F0 .121(\214le correspond to the statistical analysis pro)2.621 F
+.121(vided by the Lon-)-.15 F(gle)108 420 Q .605(y-Rice model.)-.15 F
+.605(In this e)5.605 F(xample,)-.15 E F2(SPLA)3.105 E(T!)-.95 E F0 .604
+(will return the maximum path loss occurring 50% of the time)3.105 F
+.676
+(\(fraction of time\) in 90% of situations \(fraction of situations\).)
+108 432 R .676(This is often denoted as F\(50,90\) in Long-)5.676 F(le)
+108 444 Q .986(y-Rice studies.)-.15 F .986(In the United States, an F\(\
+50,90\) criteria is typically used for digital tele)5.986 F .986
+(vision \(8-le)-.25 F -.15(ve)-.25 G(l).15 E(VSB modulation\), while F\
+\(50,50\) is used for analog \(VSB-AM+NTSC\) broadcasts.)108 456 Q -.15
+(Fo)108 480 S 2.782(rf).15 G .282
+(urther information on these parameters, see:)-2.782 F F3
+(http://\215attop.its.bldr)2.782 E(doc.go)-.37 E(v/itm.html)-.1 E F0
+(and)2.783 E F3(http://www)2.783 E(.soft-)-.74 E
+(wright.com/faq/engineering/pr)108 492 Q(op_longle)-.45 E(y_rice)-.3 E
+(.html)-.15 E F0 .229(The \214nal parameter in the)108 516 R F3(.lrp)
+2.728 E F0 .228(\214le corresponds to the transmitter')2.728 F 2.728(se)
+-.55 G -.25(ff)-2.728 G(ecti).25 E .528 -.15(ve r)-.25 H .228
+(adiated po).15 F(wer)-.25 E 2.728(,a)-.4 G .228(nd is optional.)-2.728
+F .127(If it is included in the le)108 528 R -.15(ve)-.25 G .128
+(ls and \214eld strength le).15 F -.15(ve)-.25 G 2.628(lc).15 G .128
+(ontours when performing Longle)-2.628 F .128(y-Rice studies.)-.15 F
+.128(If the)5.128 F .139
+(parameter is omitted, path loss is computed instead.)108 540 R .138
+(The ERP pro)5.138 F .138(vided in the)-.15 F F3(.lrp)2.638 E F0 .138
+(\214le can be o)2.638 F -.15(ve)-.15 G .138(rridden by).15 F(using)108
+552 Q F2(SPLA)3.181 E(T!)-.95 E F0 -.55('s)C F3(-erp)3.731 E F0 .681
+(command-line switch.)3.181 F .681(If the)5.681 F F3(.lrp)3.181 E F0
+.682(\214le contains an ERP parameter and the generation)3.181 F .531(o\
+f path-loss rather than signal strength contours is desired, the ERP ca\
+n be assigned to zero using the)108 564 R F3(-erp)3.031 E F0
+(switch without ha)108 576 Q(ving to edit the)-.2 E F3(.lrp)2.5 E F0
+(\214le to accomplish the same result.)2.5 E/F4 10.95/Times-Bold@0 SF
+(CITY LOCA)72 592.8 Q(TION FILES)-1.04 E F0 .806
+(The names and locations of cities, to)108 604.8 R .807
+(wer sites, or other points of interest may be imported and plotted on)
+-.25 F .798(topographic maps generated by)108 616.8 R F2(SPLA)3.297 E
+(T!)-.95 E F0(.)A F2(SPLA)5.797 E(T!)-.95 E F0 .797
+(imports the names of cities and locations from ASCII)3.297 F .11
+(\214les containing the location of interest')108 628.8 R 2.61(sn)-.55 G
+.111(ame, latitude, and longitude.)-2.61 F .111
+(Each \214eld is separated by a comma.)5.111 F .949
+(Each record is separated by a single line feed character)108 640.8 R
+5.949(.A)-.55 G 3.449(sw)-5.949 G .949(as the case with the)-3.549 F F3
+(.qth)3.449 E F0 .949(\214les, latitude and)3.449 F
+(longitude information may be entered in either decimal or de)108 652.8
+Q(gree, minute, second \(DMS\) format.)-.15 E -.15(Fo)108 676.8 S 2.5
+(re).15 G(xample \()-2.65 E F3(cities.dat)A F0(\):)A F1
+(Teaneck, 40.891973, 74.014506)156 700.8 Q
+(Tenafly, 40.919212, 73.955892)156 712.8 Q
+(Teterboro, 40.859511, 74.058908)156 724.8 Q F0(KD2BD Softw)72 768 Q
+120.785(are 16)-.1 F(September 2007)2.5 E(4)190.115 E EP
+%%Page: 5 5
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(Tinton Falls, 40.279966, 74.093924)156 84 Q
+(Toms River, 39.977777, 74.183580)156 96 Q(Totowa, 40.906160, 74.223310)
+156 108 Q(Trenton, 40.219922, 74.754665)156 120 Q F0 3.199(At)108 144 S
+.699(otal of \214v)-3.199 F 3.199(es)-.15 G .7(eparate city data \214le\
+s may be imported at a time, and there is no limit to the size of these)
+-3.199 F(\214les.)108 156 Q/F2 10/Times-Bold@0 SF(SPLA)6.37 E(T!)-.95 E
+F0 1.37(reads city data on a "\214rst come/\214rst serv)3.87 F 1.369
+(ed" basis, and plots only those locations whose)-.15 F .113(annotation\
+s do not con\215ict with annotations of locations read earlier in the c\
+urrent city data \214le, or in pre)108 168 R(vi-)-.25 E .54
+(ous \214les.)108 180 R .54(This beha)5.54 F .539
+(vior minimizes clutter in)-.2 F F2(SPLA)3.039 E(T!)-.95 E F0 .539
+(generated topographic maps, b)3.039 F .539(ut also mandates that)-.2 F
+.149(important locations be placed to)108 192 R -.1(wa)-.25 G .149
+(rd the be).1 F .15(ginning of the \214rst city data \214le, and locati\
+ons less important be)-.15 F(positioned further do)108 204 Q
+(wn the list or in subsequent data \214les.)-.25 E .997
+(City data \214les may be generated manually using an)108 228 R 3.496
+(yt)-.15 G -.15(ex)-3.496 G 3.496(te).15 G(ditor)-3.496 E 3.496(,i)-.4 G
+.996(mported from other sources, or deri)-3.496 F -.15(ve)-.25 G(d).15 E
+1.535(from data a)108 240 R -.25(va)-.2 G 1.535
+(ilable from the U.S. Census Bureau using the).25 F F2(citydecoder)4.035
+E F0 1.535(utility included with)4.035 F F2(SPLA)4.035 E(T!)-.95 E F0(.)
+A .153(Such data is a)108 252 R -.25(va)-.2 G .153(ilable free of char)
+.25 F .153(ge via the Internet at:)-.18 F/F3 10/Times-Italic@0 SF
+(http://www)2.652 E(.census.go)-.74 E(v/g)-.1 E
+(eo/www/cob/bdy_\214les.html)-.1 E F0(,)A(and must be in ASCII format.)
+108 264 Q/F4 10.95/Times-Bold@0 SF(CAR)72 280.8 Q -.197(TO)-.438 G
+(GRAPHIC BOUND).197 E(AR)-.383 E 2.738(YD)-.383 G -1.644 -1.04(AT A)
+-3.121 H(FILES)3.778 E F0 1.17(Cartographic boundary data may also be i\
+mported to plot the boundaries of cities, counties, or states on)108
+292.8 R .072(topographic maps generated by)108 304.8 R F2(SPLA)2.572 E
+(T!)-.95 E F0 5.072(.S)C .071
+(uch data must be of the form of ARC/INFO Ungenerate \(ASCII)-5.072 F
+-.15(Fo)108 316.8 S 1.262
+(rmat\) Metadata Cartographic Boundary Files, and are a).15 F -.25(va)
+-.2 G 1.262(ilable from the U.S.).25 F 1.263(Census Bureau via the)6.262
+F 19.948(Internet at:)108 328.8 R F3(http://www)22.448 E(.census.go)-.74
+E(v/g)-.1 E(eo/www/cob/co2000.html#ascii)-.1 E F0(and)22.447 E F3
+(http://www)22.447 E(.cen-)-.74 E(sus.go)108 340.8 Q(v/g)-.1 E
+(eo/www/cob/pl2000.html#ascii)-.1 E F0 7.85(.A)C 2.85(total of \214v)
+-2.5 F 5.35(es)-.15 G 2.85(eparate cartographic boundary \214les may be)
+-5.35 F .813(imported at a time.)108 352.8 R .812
+(It is not necessary to import state boundaries if county boundaries ha)
+5.813 F 1.112 -.15(ve a)-.2 H .812(lready been).15 F(imported.)108 364.8
+Q F4(PR)72 381.6 Q(OGRAM OPERA)-.329 E(TION)-1.04 E F2(SPLA)108 393.6 Q
+(T!)-.95 E F0 1.03(is in)3.53 F -.2(vo)-.4 G -.1(ke).2 G 3.53(dv).1 G
+1.03(ia the command-line using a series of switches and ar)-3.53 F 3.53
+(guments. Since)-.18 F F2(SPLA)3.53 E(T!)-.95 E F0 1.03(is a)3.53 F .746
+(CPU and memory intensi)108 405.6 R 1.046 -.15(ve a)-.25 H .745
+(pplication, this type of interf).15 F .745(ace minimizes o)-.1 F -.15
+(ve)-.15 G .745(rhead and lends itself well to).15 F .421
+(scripted \(batch\) operations.)108 417.6 R F2(SPLA)5.421 E(T!)-.95 E F0
+1.521 -.55('s C)D .422
+(PU and memory scheduling priority may be modi\214ed through the).55 F
+(use of the Unix)108 429.6 Q F2(nice)2.5 E F0(command.)2.5 E .226
+(The number and type of switches passed to)108 453.6 R F2(SPLA)2.725 E
+(T!)-.95 E F0 .225(determine its mode of operation and method of output)
+2.725 F .007(data generation.)108 465.6 R .007(Nearly all of)5.007 F F2
+(SPLA)2.507 E(T!)-.95 E F0 1.107 -.55('s s)D .008
+(witches may be cascaded in an).55 F 2.508(yo)-.15 G .008
+(rder on the command line when)-2.508 F(in)108 477.6 Q -.2(vo)-.4 G
+(king the program.).2 E F2(SPLA)108 501.6 Q(T!)-.95 E F0 .69
+(operates in tw)3.19 F 3.19(od)-.1 G .69(istinct modes:)-3.19 F F3 .69
+(point-to-point mode)3.19 F F0 3.19(,a)C(nd)-3.19 E F3(ar)3.19 E .69
+(ea pr)-.37 F .69(ediction mode)-.37 F F0 5.69(.E)C .69
+(ither a line-of-)-5.69 F .334(sight \(LOS\) or Longle)108 513.6 R .334
+(y-Rice Irre)-.15 F .334(gular T)-.15 F .335(errain \(ITM\) propag)-.7 F
+.335(ation model may be in)-.05 F -.2(vo)-.4 G -.1(ke).2 G 2.835(db).1 G
+2.835(yt)-2.835 G .335(he user)-2.835 F 5.335(.T)-.55 G(rue)-5.685 E
+.626(Earth, four)108 525.6 R .626(-thirds Earth, or an)-.2 F 3.126(yo)
+-.15 G .626(ther user)-3.126 F .626
+(-de\214ned Earth radius may be speci\214ed when performing line-of-)-.2
+F(sight analysis.)108 537.6 Q F4(POINT)72 554.4 Q(-T)-1.007 E
+(O-POINT AN)-.197 E(AL)-.219 E(YSIS)-1.007 E F2(SPLA)108 566.4 Q(T!)-.95
+E F0 1.224
+(may be used to perform line-of-sight terrain analysis between tw)3.724
+F 3.725(os)-.1 G 1.225(peci\214ed site locations.)-3.725 F -.15(Fo)6.225
+G(r).15 E -.15(ex)108 578.4 S(ample:).15 E F1
+(splat -t tx_site.qth -r rx_site.qth)108 602.4 Q F0(in)108 626.4 Q -.2
+(vo)-.4 G -.1(ke).2 G 2.628(sal).1 G .128
+(ine-of-sight terrain analysis between the transmitter speci\214ed in)
+-2.628 F F3(tx_site)2.627 E(.qth)-.15 E F0 .127(and recei)2.627 F -.15
+(ve)-.25 G 2.627(rs).15 G(peci\214ed)-2.627 E(in)108 638.4 Q F3(rx_site)
+3.384 E(.qth)-.15 E F0 .884(using a T)3.384 F .884
+(rue Earth radius model, and writes a)-.35 F F2(SPLA)3.384 E(T!)-.95 E
+F0 -.15(Pa)3.384 G .884(th Analysis Report to the current).15 F -.1(wo)
+108 650.4 S .549(rking directory).1 F 5.549(.T)-.65 G .549
+(he report contains details of the transmitter and recei)-5.549 F -.15
+(ve)-.25 G 3.048(rs).15 G .548(ites, and identi\214es the loca-)-3.048 F
+.016(tion of an)108 662.4 R 2.516(yo)-.15 G .016
+(bstructions detected along the line-of-sight path.)-2.516 F .017
+(If an obstruction can be cleared by raising the)5.016 F(recei)108 674.4
+Q .497 -.15(ve a)-.25 H .197(ntenna to a greater altitude,).15 F F2
+(SPLA)2.697 E(T!)-.95 E F0 .197
+(will indicate the minimum antenna height required for a line-)2.697 F
+1.654(of-sight path to e)108 686.4 R 1.654
+(xist between the transmitter and recei)-.15 F -.15(ve)-.25 G 4.154(rl)
+.15 G 1.654(ocations speci\214ed.)-4.154 F 1.655
+(Note that imperial units)6.655 F
+(\(miles, feet\) are speci\214ed unless the)108 698.4 Q F3(-metric)2.5 E
+F0(switch is added to)2.5 E F2(SPLA)2.5 E(T!)-.95 E F0 1.1 -.55('s c)D
+(ommand line options:).55 E F1
+(splat -t tx_site.qth -r rx_site.qth -metric)108 722.4 Q F0(KD2BD Softw)
+72 768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(5)190.115 E EP
+%%Page: 6 6
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .534(If the antenna\
+ must be raised a signi\214cant amount, this determination may tak)108
+84 R 3.033(eaf)-.1 G 1.033 -.25(ew m)-3.033 H 3.033(oments. Note).25 F
+(that)3.033 E .329(the results pro)108 96 R .329(vided are the)-.15 F/F1
+10/Times-Italic@0 SF(minimum)2.829 E F0 .329
+(necessary for a line-of-sight path to e)2.829 F .33
+(xist, and in the case of this sim-)-.15 F(ple e)108 108 Q
+(xample, do not tak)-.15 E 2.5(eF)-.1 G
+(resnel zone clearance requirements into consideration.)-2.5 E F1(qth)
+108 132 Q F0 -.15(ex)2.534 G .034(tensions are assumed by).15 F/F2 10
+/Times-Bold@0 SF(SPLA)2.534 E(T!)-.95 E F0 .033
+(for QTH \214les, and are optional when specifying -t and -r ar)2.534 F
+(guments)-.18 E .532(on the command-line.)108 144 R F2(SPLA)5.532 E(T!)
+-.95 E F0 .532(automatically reads all SPLA)3.032 F 3.032(TD)-1.11 G
+.532(ata Files necessary to conduct the terrain)-3.032 F .912
+(analysis between the sites speci\214ed.)108 156 R F2(SPLA)5.912 E(T!)
+-.95 E F0 .911(searches for the required SDF \214les in the current w)
+5.911 F(orking)-.1 E .188(directory \214rst.)108 168 R .188
+(If the needed \214les are not found,)5.188 F F2(SPLA)2.688 E(T!)-.95 E
+F0 .189(then searches in the path speci\214ed by the)2.688 F F1(-d)2.689
+E F0(com-)2.689 E(mand-line switch:)108 180 Q/F3 10/Courier@0 SF
+(splat -t tx_site -r rx_site -d /cdrom/sdf/)108 204 Q F0 .33(An e)108
+228 R .329(xternal directory path may be speci\214ed by placing a ".spl\
+at_path" \214le under the user')-.15 F 2.829(sh)-.55 G .329
+(ome directory)-2.829 F(.)-.65 E 3.045(This \214le must contain the ful\
+l directory path of last resort to all the SDF \214les.)108 240 R 3.045
+(The path in the)8.045 F F1($HOME/.splat_path)108 252 Q F0
+(\214le must be of the form of a single line of ASCII te)2.5 E(xt:)-.15
+E F3(/opt/splat/sdf/)108 276 Q F0(and can be generated using an)108 300
+Q 2.5(yt)-.15 G -.15(ex)-2.5 G 2.5(te).15 G(ditor)-2.5 E(.)-.55 E 3.023
+(Ag)108 324 S .523(raph of the terrain pro\214le between the recei)
+-3.023 F -.15(ve)-.25 G 3.023(ra).15 G .523
+(nd transmitter locations as a function of distance from)-3.023 F
+(the recei)108 336 Q -.15(ve)-.25 G 2.5(rc).15 G
+(an be generated by adding the)-2.5 E F1(-p)2.5 E F0(switch:)2.5 E F3
+(splat -t tx_site -r rx_site -p terrain_profile.png)108 360 Q F2(SPLA)
+108 384 Q(T!)-.95 E F0(in)4.119 E -.2(vo)-.4 G -.1(ke).2 G(s).1 E F2
+(gnuplot)4.119 E F0 1.619(when generating graphs.)4.119 F 1.619
+(The \214lename e)6.619 F 1.619(xtension speci\214ed to)-.15 F F2(SPLA)
+4.12 E(T!)-.95 E F0(deter)4.12 E(-)-.2 E .346
+(mines the format of the graph produced.)108 396 R F1(.png)5.346 E F0
+.346(will produce a 640x480 color PNG graphic \214le, while)2.846 F F1
+(.ps)2.846 E F0(or)2.846 E F1(.postscript)108 408 Q F0 .15
+(will produce postscript output.)2.65 F .151
+(Output in formats such as GIF)5.151 F 2.651(,A)-.8 G .151
+(dobe Illustrator)-2.651 F 2.651(,A)-.4 G .151(utoCAD dxf,)-2.651 F(LaT)
+108 420 Q .16(eX, and man)-.7 F 2.66(yo)-.15 G .16(thers are a)-2.66 F
+-.25(va)-.2 G 2.659(ilable. Please).25 F(consult)2.659 E F2(gnuplot)
+2.659 E F0 2.659(,a)C(nd)-2.659 E F2(gnuplot)2.659 E F0 1.259 -.55('s d)
+D .159(ocumentation for details on).55 F
+(all the supported output formats.)108 432 Q 3.542(Ag)108 456 S 1.042
+(raph of ele)-3.542 F -.25(va)-.25 G 1.042
+(tions subtended by the terrain between the recei).25 F -.15(ve)-.25 G
+3.542(ra).15 G 1.043(nd transmitter as a function of dis-)-3.542 F
+(tance from the recei)108 468 Q -.15(ve)-.25 G 2.5(rc).15 G
+(an be generated by using the)-2.5 E F1(-e)2.5 E F0(switch:)2.5 E F3
+(splat -t tx_site -r rx_site -e elevation_profile.png)108 492 Q F0 .425
+(The graph produced using this switch illustrates the ele)108 516 R -.25
+(va)-.25 G .424(tion and depression angles resulting from the ter).25 F
+(-)-.2 E .553(rain between the recei)108 528 R -.15(ve)-.25 G(r').15 E
+3.053(sl)-.55 G .553
+(ocation and the transmitter site from the perspecti)-3.053 F .854 -.15
+(ve o)-.25 H 3.054(ft).15 G .554(he recei)-3.054 F -.15(ve)-.25 G(r').15
+E 3.054(sl)-.55 G(ocation.)-3.054 E 3.781(As)108 540 S 1.281
+(econd trace is plotted between the left side of the graph \(recei)
+-3.781 F -.15(ve)-.25 G(r').15 E 3.78(sl)-.55 G 1.28
+(ocation\) and the location of the)-3.78 F .448
+(transmitting antenna on the right.)108 552 R .449
+(This trace illustrates the ele)5.448 F -.25(va)-.25 G .449
+(tion angle required for a line-of-sight path).25 F 1.074(to e)108 564 R
+1.074(xist between the recei)-.15 F -.15(ve)-.25 G 3.574(ra).15 G 1.074
+(nd transmitter locations.)-3.574 F 1.074
+(If the trace intersects the ele)6.074 F -.25(va)-.25 G 1.073
+(tion pro\214le at an).25 F(y)-.15 E 1.031(point on the graph, then thi\
+s is an indication that a line-of-sight path does not e)108 576 R 1.032
+(xist under the conditions)-.15 F(gi)108 588 Q -.15(ve)-.25 G(n, and th\
+e obstructions can be clearly identi\214ed on the graph at the point\(s\
+\) of intersection.).15 E 3.671(Ag)108 612 S 1.171(raph illustrating te\
+rrain height referenced to a line-of-sight path between the transmitter\
+ and recei)-3.671 F -.15(ve)-.25 G(r).15 E(may be generated using the)
+108 624 Q F1(-h)2.5 E F0(switch:)2.5 E F3
+(splat -t tx_site -r rx_site -h height_profile.png)108 648 Q F0 3.245
+(At)108 672 S .745
+(errain height plot normalized to the transmitter and recei)-3.245 F
+-.15(ve)-.25 G 3.245(ra).15 G .745
+(ntenna heights can be obtained using the)-3.245 F F1(-H)108 684 Q F0
+(switch:)2.5 E F3
+(splat -t tx_site -r rx_site -H normalized_height_profile.png)108 708 Q
+F0(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(6)
+190.115 E EP
+%%Page: 7 7
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E 2.5(Ac)108 84 S
+(ontour of the Earth')-2.5 E 2.5(sc)-.55 G(urv)-2.5 E
+(ature is also plotted in this mode.)-.25 E .635(The \214rst Fresnel Zo\
+ne, and 60% of the \214rst Fresnel Zone can be added to height pro\214l\
+e graphs by adding)108 108 R(the)108 120 Q/F1 10/Times-Italic@0 SF(-f)
+2.5 E F0(switch, and specifying a frequenc)2.5 E 2.5(y\()-.15 G
+(in MHz\) at which the Fresnel Zone should be modeled:)-2.5 E/F2 10
+/Courier@0 SF(splat -t tx_site -r rx_site -f 439.250 -H normalized_heig\
+ht_profile.png)108 144 Q F0
+(Fresnel Zone clearances other 60% can be speci\214ed using the)108 168
+Q F1(-fz)2.5 E F0(switch as follo)2.5 E(ws:)-.25 E F2
+(splat -t tx_site -r rx_site -f 439.250 -fz 75 -H height_profile2.png)
+108 192 Q F0 2.5(Ag)108 216 S(raph sho)-2.5 E(wing Longle)-.25 E
+(y-Rice path loss may be plotted using the)-.15 E F1(-l)2.5 E F0
+(switch:)2.5 E F2(splat -t tx_site -r rx_site -l path_loss_profile.png)
+108 240 Q F0(As before, adding the)108 264 Q F1(-metric)2.5 E F0
+(switch forces the graphs to be plotted using metric units of measure.)
+2.5 E .735(When performing a point-to-point analysis, a)108 288 R/F3 10
+/Times-Bold@0 SF(SPLA)3.235 E(T!)-.95 E F0 -.15(Pa)3.235 G .735
+(th Analysis Report is generated in the form of a).15 F(te)108 300 Q
+.528(xt \214le with a)-.15 F F1(.txt)3.028 E F0 .528(\214lename e)3.028
+F 3.028(xtension. The)-.15 F .528
+(report contains bearings and distances between the transmitter)3.028 F
+.605(and recei)108 312 R -.15(ve)-.25 G 1.405 -.4(r, a).15 H 3.105(sw).4
+G .605(ell as the free-space and Longle)-3.105 F .605
+(y-Rice path loss for the path being analyzed.)-.15 F .606(The mode)
+5.606 F .935(of propag)108 324 R .935(ation for the path is gi)-.05 F
+-.15(ve)-.25 G 3.434(na).15 G(s)-3.434 E F1(Line-of-Sight)3.434 E F0(,)A
+F1 .934(Single Horizon)3.434 F F0(,)A F1 .934(Double Horizon)3.434 F F0
+(,)A F1(Dif)3.434 E(fr)-.18 E .934(action Domi-)-.15 F(nant)108 336 Q F0
+2.5(,o)C(r)-2.5 E F1 -1.85 -.55(Tr o)2.5 H(poscatter Dominant).55 E F0
+(.)A .126(Distances and locations to kno)108 360 R .127
+(wn obstructions along the path between transmitter and recei)-.25 F
+-.15(ve)-.25 G 2.627(ra).15 G .127(re also pro-)-2.627 F 3.268
+(vided. If)108 372 R .767(the transmitter')3.268 F 3.267(se)-.55 G -.25
+(ff)-3.267 G(ecti).25 E 1.067 -.15(ve r)-.25 H .767(adiated po).15 F
+.767(wer is speci\214ed in the transmitter')-.25 F 3.267(sc)-.55 G
+(orresponding)-3.267 E F1(.lrp)3.267 E F0(\214le,)3.267 E 1.39
+(then predicted signal strength and antenna v)108 384 R 1.391
+(oltage at the recei)-.2 F 1.391(ving location is also pro)-.25 F 1.391
+(vided in the P)-.15 F(ath)-.15 E(Analysis Report.)108 396 Q 2.36 -.8
+(To d)108 420 T .76(etermine the signal-to-noise \(SNR\) ratio at remot\
+e location where random Johnson \(thermal\) noise is).8 F
+(the primary limiting f)108 432 Q(actor in reception:)-.1 E F1(SNR)
+108.33 456 Q/F4 10/Symbol SF(=)3.07 E F1(T)2.71 E F4(-)3.47 E F1(NJ)2.9
+E F4(-)3.17 E F1(L)2.78 E F4(+)2.73 E F1(G)2.18 E F4(-)2.7 E F1(NF)2.9 E
+F0(where)108 480 Q F3(T)2.714 E F0 .215
+(is the ERP of the transmitter in dBW in the direction of the recei)
+2.714 F -.15(ve)-.25 G -.4(r,).15 G F3(NJ)3.115 E F0 .215
+(is Johnson Noise in dBW)2.715 F .725(\(-136 dBW for a 6 MHz tele)108
+492 R .725(vision channel\),)-.25 F F3(L)3.225 E F0 .725
+(is the path loss pro)3.225 F .725(vided by)-.15 F F3(SPLA)3.225 E(T!)
+-.95 E F0 .725(in dB \(as a)5.725 F F1(positive)3.225 E F0(number\),)108
+504 Q F3(G)2.5 E F0(is the recei)2.5 E .3 -.15(ve a)-.25 H(ntenna g).15
+E(ain in dB o)-.05 E -.15(ve)-.15 G 2.5(ri).15 G(sotropic, and)-2.5 E F3
+(NF)2.5 E F0(is the recei)2.5 E -.15(ve)-.25 G 2.5(rn).15 G
+(oise \214gure in dB.)-2.5 E F3(T)108 528 Q F0(may be computed as follo)
+2.5 E(ws:)-.25 E F1(T)107.91 552 Q F4(=)4.07 E F1(TI)2.71 E F4(+)3.21 E
+F1(GT)2.18 E F0(where)108 576 Q F3(TI)3.055 E F0 .555
+(is actual amount of RF po)3.055 F .555(wer deli)-.25 F -.15(ve)-.25 G
+.555(red to the transmitting antenna in dBW).15 F(,)-.92 E F3(GT)3.055 E
+F0 .555(is the transmit-)3.055 F .67(ting antenna g)108 588 R .67
+(ain \(o)-.05 F -.15(ve)-.15 G 3.17(ri).15 G .67
+(sotropic\) in the direction of the recei)-3.17 F -.15(ve)-.25 G 3.169
+(r\().15 G .669(or the horizon if the recei)-3.169 F -.15(ve)-.25 G
+3.169(ri).15 G 3.169(so)-3.169 G -.15(ve)-3.319 G 3.169(rt).15 G(he)
+-3.169 E(horizon\).)108 600 Q 1.801 -.8(To c)108 624 T .201(ompute ho).8
+F 2.701(wm)-.25 G .202(uch more signal is a)-2.701 F -.25(va)-.2 G .202
+(ilable o).25 F -.15(ve)-.15 G 2.702(rt).15 G .202
+(he minimum to necessary to achie)-2.702 F .502 -.15(ve a s)-.25 H .202
+(peci\214c signal-).15 F(to-noise ratio:)108 636 Q F1(Signal)108.33 660
+Q F0(_).51 E F1(Margin).68 E F4(=)3.04 E F1(SNR)3.13 E F4(-)2.47 E F1(S)
+2.53 E F0(where)108 684 Q F3(S)3.849 E F0 1.349
+(is the minimum required SNR ratio \(15.5 dB for A)3.849 F 1.349
+(TSC \(8-le)-1.11 F -.15(ve)-.25 G 3.849(lV).15 G 1.349(SB\) DTV)-3.849
+F 3.849(,4)-1.29 G 3.849(2d)-3.849 G 3.848(Bf)-3.849 G 1.348(or analog)
+-3.848 F(NTSC tele)108 696 Q(vision\).)-.25 E 2.61(At)108 720 S .11
+(opographic map may be generated by)-2.61 F F3(SPLA)2.611 E(T!)-.95 E F0
+.111(to visualize the path between the transmitter and recei)2.611 F
+-.15(ve)-.25 G(r).15 E(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F
+(September 2007)2.5 E(7)190.115 E EP
+%%Page: 8 8
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .099
+(sites from yet another perspecti)108 84 R -.15(ve)-.25 G 5.099(.T).15 G
+.099(opographic maps generated by)-5.899 F/F1 10/Times-Bold@0 SF(SPLA)
+2.598 E(T!)-.95 E F0 .098(display ele)2.598 F -.25(va)-.25 G .098
+(tions using a log-).25 F .335(arithmic grayscale, with higher ele)108
+96 R -.25(va)-.25 G .335
+(tions represented through brighter shades of gray).25 F 5.336(.T)-.65 G
+.336(he dynamic range)-5.336 F .257
+(of the image is scaled between the highest and lo)108 108 R .257
+(west ele)-.25 F -.25(va)-.25 G .257(tions present in the map.).25 F
+.257(The only e)5.257 F .257(xception to)-.15 F(this is sea-le)108 120 Q
+-.15(ve)-.25 G(l, which is represented using the color blue.).15 E -.8
+(To)108 144 S(pographic output is in).8 E -.2(vo)-.4 G -.1(ke).2 G 2.5
+(du).1 G(sing the)-2.5 E/F2 10/Times-Italic@0 SF(-o)2.5 E F0(switch:)2.5
+E/F3 10/Courier@0 SF(splat -t tx_site -r rx_site -o topo_map.ppm)108 168
+Q F0(The)108 192 Q F2(.ppm)2.5 E F0 -.15(ex)2.5 G
+(tension on the output \214lename is assumed by).15 E F1(SPLA)2.5 E(T!)
+-.95 E F0 2.5(,a)C(nd is optional.)-2.5 E .006(In this e)108 216 R
+(xample,)-.15 E F2(topo_map.ppm)2.506 E F0 .007
+(will illustrate the locations of the transmitter and recei)2.506 F -.15
+(ve)-.25 G 2.507(rs).15 G .007(ites speci\214ed.)-2.507 F(In)5.007 E .22
+(addition, the great circle path between the tw)108 228 R 2.72(os)-.1 G
+.22(ites will be dra)-2.72 F .22(wn o)-.15 F -.15(ve)-.15 G 2.72(rl).15
+G .22(ocations for which an unobstructed)-2.72 F 1.208(path e)108 240 R
+1.209(xists to the transmitter at a recei)-.15 F 1.209
+(ving antenna height equal to that of the recei)-.25 F -.15(ve)-.25 G
+3.709(rs).15 G 1.209(ite \(speci\214ed in)-3.709 F F2(rx_site)108 252 Q
+(.qth)-.15 E F0(\).)A .773(It may desirable to populate the topographic\
+ map with names and locations of cities, to)108 276 R .773
+(wer sites, or other)-.25 F(important locations.)108 288 Q 2.5(Ac)5 G
+(ity \214le may be passed to)-2.5 E F1(SPLA)2.5 E(T!)-.95 E F0
+(using the)2.5 E F2(-s)2.5 E F0(switch:)2.5 E F3
+(splat -t tx_site -r rx_site -s cities.dat -o topo_map)108 312 Q F0
+(Up to \214v)108 336 Q 2.5(es)-.15 G
+(eparate city \214les may be passed to)-2.5 E F1(SPLA)2.5 E(T!)-.95 E F0
+(at a time follo)2.5 E(wing the)-.25 E F2(-s)2.5 E F0(switch.)2.5 E .554
+(County and state boundaries may be added to the map by specifying up t\
+o \214v)108 360 R 3.055(eU)-.15 G .555(.S. Census Bureau carto-)-3.055 F
+(graphic boundary \214les using the)108 372 Q F2(-b)2.5 E F0(switch:)2.5
+E F3(splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map)108 396 Q
+F0 1.064
+(In situations where multiple transmitter sites are in use, as man)108
+420 R 3.563(ya)-.15 G 3.563(sf)-3.563 G 1.063
+(our site locations may be passed to)-3.563 F F1(SPLA)108 432 Q(T!)-.95
+E F0(at a time for analysis:)2.5 E F3
+(splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p profile.png)
+108 456 Q F0 .285(In this e)108 480 R .285(xample, four separate terrai\
+n pro\214les and obstruction reports will be generated by)-.15 F F1
+(SPLA)2.785 E(T!)-.95 E F0 5.285(.A)C(sin-)-2.5 E .509
+(gle topographic map can be speci\214ed using the)108 492 R F2(-o)3.009
+E F0 .508(switch, and line-of-sight paths between each transmitter)3.009
+F .816(and the recei)108 504 R -.15(ve)-.25 G 3.316(rs).15 G .816
+(ite indicated will be produced on the map, each in its o)-3.316 F .817
+(wn color)-.25 F 5.817(.T)-.55 G .817(he path between the)-5.817 F .767
+(\214rst transmitter speci\214ed to the recei)108 516 R -.15(ve)-.25 G
+3.267(rw).15 G .766
+(ill be in green, the path between the second transmitter and the)-3.267
+F(recei)108 528 Q -.15(ve)-.25 G 3.463(rw).15 G .963(ill be in c)-3.463
+F .964(yan, the path between the third transmitter and the recei)-.15 F
+-.15(ve)-.25 G 3.464(rw).15 G .964(ill be in violet, and the)-3.464 F
+(path between the fourth transmitter and the recei)108 540 Q -.15(ve)
+-.25 G 2.5(rw).15 G(ill be in sienna.)-2.5 E F1(SPLA)108 564 Q(T!)-.95 E
+F0 .59(generated topographic maps are 24-bit T)3.09 F .59
+(rueColor Portable PixMap \(PPM\) images.)-.35 F(The)5.59 E 3.09(ym)-.15
+G .59(ay be)-3.09 F(vie)108 576 Q 1.06(wed, edited, or con)-.25 F -.15
+(ve)-.4 G 1.06(rted to other graphic formats by popular image vie).15 F
+1.06(wing applications such as)-.25 F F1(xv)3.56 E F0(,)A F1 1.66
+(The GIMP)108 588 R F0(,)A F1(ImageMagick)4.16 E F0 4.16(,a)C(nd)-4.16 E
+F1(XP)4.16 E(aint)-.1 E F0 6.66(.P)C 1.66
+(NG format is highly recommended for lossless compressed)-6.66 F .726
+(storage of)108 600 R F1(SPLA)3.226 E(T!)-.95 E F0 .726
+(generated topographic output \214les.)5.726 F F1(ImageMagick)5.726 E F0
+1.827 -.55('s c)D .727(ommand-line utility easily con-).55 F -.15(ve)108
+612 S(rts).15 E F1(SPLA)2.5 E(T!)-.95 E F0 1.1 -.55('s P)D
+(PM \214les to PNG format:).55 E F3(convert splat_map.ppm splat_map.png)
+108 636 Q F0 17.667(Another e)108 660 R 17.667
+(xcellent PPM to PNG command-line utility is a)-.15 F -.25(va)-.2 G
+17.666(ilable at:).25 F F2(http://www)108 672 Q(.libpng)-.74 E(.or)-.15
+E(g/pub/png/book/sour)-.37 E(ces.html)-.37 E F0 5.152(.A)C 2.652(sal)
+-5.152 G .153(ast resort, PPM \214les may be compressed using the)-2.652
+F(bzip2 utility)108 684 Q 2.5(,a)-.65 G(nd read directly by)-2.5 E F1
+(The GIMP)2.5 E F0(in this format.)2.5 E(The)108 708 Q F2(-ngs)2.573 E
+F0 .072(option assigns all terrain to the color white, and can be used \
+when it is desirable to generate a map)2.573 F(that is de)108 720 Q -.2
+(vo)-.25 G(id of terrain:).2 E(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F
+(September 2007)2.5 E(8)190.115 E EP
+%%Page: 9 9
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(splat -t tx_site -r rx_site -b co34_d00.dat -ngs -o white_map)108 84 Q
+F0 2.452(The resulting .ppm image \214le can be con)108 108 R -.15(ve)
+-.4 G 2.452(rted to .png format with a transparent background using).15
+F/F2 10/Times-Bold@0 SF(ImageMagick)108 120 Q F0 -.55('s)C F2(con)3.05 E
+-.1(ve)-.4 G(rt).1 E F0(utility:)2.5 E F1
+(convert -transparent "#FFFFFF" white_map.ppm transparent_map.png)108
+144 Q/F3 10.95/Times-Bold@0 SF(REGION)72 160.8 Q(AL CO)-.219 E(VERA)
+-.548 E(GE AN)-.602 E(AL)-.219 E(YSIS)-1.007 E F2(SPLA)108 172.8 Q(T!)
+-.95 E F0 .098(can analyze a transmitter or repeater site, or netw)2.599
+F .098(ork of sites, and predict the re)-.1 F .098(gional co)-.15 F -.15
+(ve)-.15 G .098(rage for).15 F .682(each site speci\214ed.)108 184.8 R
+.682(In this mode,)5.682 F F2(SPLA)3.183 E(T!)-.95 E F0 .683
+(can generate a topographic map displaying the geometric line-)3.183 F
+.163(of-sight co)108 196.8 R -.15(ve)-.15 G .163(rage area of the sites\
+ based on the location of each site and the height of recei).15 F .462
+-.15(ve a)-.25 H .162(ntenna wish-).15 F .331
+(ing to communicate with the site in question.)108 208.8 R 2.831(Ar)
+5.331 G -.15(eg)-2.831 G .331(ional analysis may be performed by).15 F
+F2(SPLA)2.832 E(T!)-.95 E F0 .332(using the)2.832 F/F4 10/Times-Italic@0
+SF(-c)108 220.8 Q F0(switch as follo)2.5 E(ws:)-.25 E F1
+(splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o tx_coverage)
+108 244.8 Q F0 .27(In this e)108 268.8 R(xample,)-.15 E F2(SPLA)2.77 E
+(T!)-.95 E F0 .269(generates a topographic map called)2.769 F F4(tx_co)
+2.769 E(ver)-.1 E -.1(age)-.15 G(.ppm)-.05 E F0 .269
+(that illustrates the predicted)2.769 F 1.534(line-of-sight re)108 280.8
+R 1.534(gional co)-.15 F -.15(ve)-.15 G 1.534(rage of).15 F F4(tx_site)
+4.034 E F0 1.535(to recei)4.034 F 1.535(ving locations ha)-.25 F 1.535
+(ving antennas 30.0 feet abo)-.2 F 1.835 -.15(ve g)-.15 H(round).15 E
+(le)108 292.8 Q -.15(ve)-.25 G 3.162(l\().15 G -.4(AG)-3.162 G 3.162
+(L\). If).4 F(the)3.162 E F4(-metric)3.162 E F0 .662
+(switch is used, the ar)3.162 F .662(gument follo)-.18 F .662(wing the)
+-.25 F F4(-c)3.162 E F0 .661(switch is interpreted as being in)3.161 F
+.301(meters rather than in feet.)108 304.8 R .301(The contents of)5.301
+F F4(cities.dat)2.802 E F0 .302
+(are plotted on the map, as are the cartographic bound-)2.802 F
+(aries contained in the \214le)108 316.8 Q F4(co34_d00.dat)2.5 E F0(.)A
+.572(When plotting line-of-sight paths and areas of re)108 340.8 R .572
+(gional co)-.15 F -.15(ve)-.15 G(rage,).15 E F2(SPLA)3.072 E(T!)-.95 E
+F0 .572(by def)3.072 F .572(ault does not account for)-.1 F .031(the ef)
+108 352.8 R .032(fects of atmospheric bending.)-.25 F(Ho)5.032 E(we)-.25
+E -.15(ve)-.25 G .832 -.4(r, t).15 H .032(his beha).4 F .032
+(vior may be modi\214ed by using the Earth radius mul-)-.2 F(tiplier \()
+108 364.8 Q F4(-m)A F0 2.5(\)s)C(witch:)-2.5 E F1 3.273
+(splat -t wnjt-dt -c 30.0 -m 1.333 -s cities.dat -b counties.dat -o)108
+388.8 R(map.ppm)108 400.8 Q F0 .594
+(An earth radius multiplier of 1.333 instructs)108 424.8 R F2(SPLA)3.095
+E(T!)-.95 E F0 .595(to use the "four)3.095 F .595
+(-thirds earth" model for line-of-sight)-.2 F(propag)108 436.8 Q
+(ation analysis.)-.05 E(An)5 E 2.5(ya)-.15 G
+(ppropriate earth radius multiplier may be selected by the user)-2.5 E
+(.)-.55 E .713(When performing a re)108 460.8 R .712(gional analysis,)
+-.15 F F2(SPLA)3.212 E(T!)-.95 E F0 .712
+(generates a site report for each station analyzed.)3.212 F F2(SPLA)
+5.712 E(T!)-.95 E F0 .658(site reports contain details of the site')108
+472.8 R 3.159(sg)-.55 G .659(eographic location, its height abo)-3.159 F
+.959 -.15(ve m)-.15 H .659(ean sea le).15 F -.15(ve)-.25 G .659
+(l, the antenna').15 F(s)-.55 E .613(height abo)108 484.8 R .913 -.15
+(ve m)-.15 H .613(ean sea le).15 F -.15(ve)-.25 G .613(l, the antenna')
+.15 F 3.112(sh)-.55 G .612(eight abo)-3.112 F .912 -.15(ve a)-.15 H -.15
+(ve)-.05 G .612(rage terrain, and the height of the a).15 F -.15(ve)-.2
+G .612(rage ter).15 F(-)-.2 E(rain calculated to)108 496.8 Q -.1(wa)-.25
+G(rd the bearings of 0, 45, 90, 135, 180, 225, 270, and 315 de).1 E
+(grees azimuth.)-.15 E F3(DETERMINING MUL)72 513.6 Q
+(TIPLE REGIONS OF LOS CO)-1.007 E(VERA)-.548 E(GE)-.602 E F2(SPLA)108
+525.6 Q(T!)-.95 E F0 1.086(can also display line-of-sight co)3.586 F
+-.15(ve)-.15 G 1.086(rage areas for as man).15 F 3.586(ya)-.15 G 3.586
+(sf)-3.586 G 1.087(our separate transmitter sites on a)-3.586 F
+(common topographic map.)108 537.6 Q -.15(Fo)5 G 2.5(re).15 G(xample:)
+-2.65 E F1
+(splat -t site1 site2 site3 site4 -c 10.0 -metric -o network.ppm)108
+561.6 Q F0 .687(plots the re)108 585.6 R .687(gional line-of-sight co)
+-.15 F -.15(ve)-.15 G .687
+(rage of site1, site2, site3, and site4 based on a recei).15 F .986 -.15
+(ve a)-.25 H .686(ntenna located).15 F .762(10.0 meters abo)108 597.6 R
+1.062 -.15(ve g)-.15 H .762(round le).15 F -.15(ve)-.25 G 3.262(l. A).15
+F .763(topographic map is then written to the \214le)3.262 F F4
+(network.ppm)3.263 E F0 5.763(.T)C .763(he line-of-)-5.763 F .303
+(sight co)108 609.6 R -.15(ve)-.15 G .303
+(rage area of the transmitters are plotted as follo).15 F .302
+(ws in the colors indicated \(along with their corre-)-.25 F
+(sponding RGB v)108 621.6 Q(alues in decimal\):)-.25 E F1
+(site1: Green \(0,255,0\))132 645.6 Q(site2: Cyan \(0,255,255\))132
+657.6 Q(site3: Medium Violet \(147,112,219\))132 669.6 Q
+(site4: Sienna 1 \(255,130,71\))132 681.6 Q
+(site1 + site2: Yellow \(255,255,0\))132 705.6 Q
+(site1 + site3: Pink \(255,192,203\))132 717.6 Q
+(site1 + site4: Green Yellow \(173,255,47\))132 729.6 Q F0(KD2BD Softw)
+72 768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(9)190.115 E EP
+%%Page: 10 10
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(site2 + site3: Orange \(255,165,0\))132 84 Q
+(site2 + site4: Dark Sea Green 1 \(193,255,193\))132 96 Q
+(site3 + site4: Dark Turquoise \(0,206,209\))132 108 Q
+(site1 + site2 + site3: Dark Green \(0,100,0\))132 132 Q
+(site1 + site2 + site4: Blanched Almond \(255,235,205\))132 144 Q
+(site1 + site3 + site4: Medium Spring Green \(0,250,154\))132 156 Q
+(site2 + site3 + site4: Tan \(210,180,140\))132 168 Q
+(site1 + site2 + site3 + site4: Gold2 \(238,201,0\))132 192 Q F0 .246
+(If separate)108 216 R/F2 10/Times-Italic@0 SF(.qth)2.746 E F0 .247
+(\214les are generated, each representing a common site location b)2.747
+F .247(ut a dif)-.2 F .247(ferent antenna height,)-.25 F 3.536(as)108
+228 S 1.036(ingle topographic map illustrating the re)-3.536 F 1.036
+(gional co)-.15 F -.15(ve)-.15 G 1.036(rage from as man).15 F 3.535(ya)
+-.15 G 3.535(sf)-3.535 G 1.035(our separate locations on a)-3.535 F
+(single to)108 240 Q(wer may be generated by)-.25 E/F3 10/Times-Bold@0
+SF(SPLA)2.5 E(T!)-.95 E F0(.)A/F4 10.95/Times-Bold@0 SF(LONGLEY)72 256.8
+Q(-RICE P)-1.007 E -1.04(AT)-.81 G 2.738(HL)1.04 G(OSS AN)-2.738 E(AL)
+-.219 E(YSIS)-1.007 E F0 .344(If the)108 268.8 R F2(-c)2.844 E F0 .344
+(switch is replaced by a)2.844 F F2(-L)2.844 E F0 .344(switch, a Longle)
+2.844 F .345(y-Rice path loss map for a transmitter site may be gen-)
+-.15 F(erated:)108 280.8 Q F1
+(splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o path_loss_map)
+108 304.8 Q F0 .591(In this mode,)108 328.8 R F3(SPLA)3.091 E(T!)-.95 E
+F0 .591(generates a multi-color map illustrating e)3.091 F .591
+(xpected signal le)-.15 F -.15(ve)-.25 G .59(ls in areas surrounding).15
+F .277(the transmitter site.)108 340.8 R 2.778(Al)5.278 G -.15(eg)-2.778
+G .278(end at the bottom of the map correlates each color with a speci\
+\214c path loss range).15 F
+(in decibels or signal strength in decibels o)108 352.8 Q -.15(ve)-.15 G
+2.5(ro).15 G(ne micro)-2.5 E -.2(vo)-.15 G(lt per meter \(dBuV/m\).).2 E
+.63(The Longle)108 376.8 R .63
+(y-Rice analysis range may be modi\214ed to a user)-.15 F .63
+(-speci\214c v)-.2 F .63(alue using the)-.25 F F2(-R)3.13 E F0 3.13
+(switch. The)3.13 F(ar)3.13 E(gu-)-.18 E .522(ment must be gi)108 388.8
+R -.15(ve)-.25 G 3.022(ni).15 G 3.022(nm)-3.022 G .522
+(iles \(or kilometers if the)-3.022 F F2(-metric)3.022 E F0 .523
+(switch is used\).)3.023 F .523(If a range wider than the gener)5.523 F
+(-)-.2 E .927(ated topographic map is speci\214ed,)108 400.8 R F3(SPLA)
+3.426 E(T!)-.95 E F0 .926(will perform Longle)3.426 F .926
+(y-Rice path loss calculations between all)-.15 F
+(four corners of the area prediction map.)108 412.8 Q(The)108 436.8 Q F2
+(-db)3.344 E F0 .844(switch allo)3.344 F .845
+(ws a constraint to be placed on the maximum path loss re)-.25 F .845
+(gion plotted on the map.)-.15 F(A)5.845 E .21(maximum path loss betwee\
+n 80 and 230 dB may be speci\214ed using this switch.)108 448.8 R -.15
+(Fo)5.21 G 2.71(re).15 G .21(xample, if a path loss)-2.86 F(be)108 460.8
+Q .395(yond -140 dB is irrele)-.15 F -.25(va)-.25 G .395(nt to the surv)
+.25 F .695 -.15(ey b)-.15 H .395(eing conducted,).15 F F3(SPLA)2.895 E
+(T!)-.95 E F0 1.495 -.55('s p)D .396
+(ath loss plot can be constrained to).55 F(the re)108 472.8 Q
+(gion bounded by the 140 dB attenuation contour as follo)-.15 E(ws:)-.25
+E F1 3.818
+(splat -t wnjt-dt -L 30.0 -s cities.dat -b co34_d00.dat -db 140 -o)108
+496.8 R(plot.ppm)108 508.8 Q F4(SIGN)72 537.6 Q(AL CONT)-.219 E
+(OUR COLOR DEFINITION P)-.197 E(ARAMETERS)-.81 E F0 1.165(The colors us\
+ed to illustrate signal strength and path loss contours in)108 549.6 R
+F3(SPLA)3.665 E(T!)-.95 E F0 1.165(generated co)3.665 F -.15(ve)-.15 G
+1.165(rage maps).15 F .037
+(may be tailored by the user by creating or modifying)108 561.6 R F3
+(SPLA)2.537 E(T!)-.95 E F0 1.137 -.55('s c)D .037
+(olor de\214nition \214les.).55 F F3(SPLA)5.037 E(T!)-.95 E F0 .036
+(color de\214ni-)2.536 F(tion \214les ha)108 573.6 Q .3 -.15(ve t)-.2 H
+(he same base name as the transmitter').15 E(s)-.55 E F2(.qth)2.5 E F0
+(\214le, b)2.5 E(ut carry)-.2 E F2(.lcf)2.5 E F0(and)2.5 E F2(.scf)2.5 E
+F0 -.15(ex)2.5 G(tensions.).15 E .237(When a re)108 597.6 R .237
+(gional Longle)-.15 F .237
+(y-Rice analysis is performed and the transmitter')-.15 F 2.737(sE)-.55
+G .237(RP is not speci\214ed or is zero, a)-2.737 F F2(.lcf)108 609.6 Q
+F0 .943(path loss color de\214nition \214le corresponding to the transm\
+itter site \()3.443 F F2(.qth)A F0 3.443(\)i)C 3.443(sr)-3.443 G .943
+(ead by)-3.443 F F3(SPLA)3.443 E(T!)-.95 E F0 .942(from the)3.443 F .377
+(current w)108 621.6 R .377(orking directory)-.1 F 5.377(.I)-.65 G 2.877
+(fa)-5.377 G F2(.lcf).001 E F0 .378
+(\214le corresponding to the transmitter site is not found, then a def)
+2.878 F .378(ault \214le)-.1 F .603
+(suitable for manual editing by the user is automatically generated by)
+108 633.6 R F3(SPLA)3.103 E(T!)-.95 E F0 5.603(.I)C 3.103(ft)-5.603 G
+.603(he transmitter')-3.103 F 3.103(sE)-.55 G .603(RP is)-3.103 F .377(\
+speci\214ed, then a signal strength map is generated and a signal stren\
+gth color de\214nition \214le \()108 645.6 R F2(.scf)A F0 2.877(\)i)C
+2.877(sr)-2.877 G .377(ead, or)-2.877 F(generated if one is not a)108
+657.6 Q -.25(va)-.2 G(ilable in the current w).25 E(orking directory)-.1
+E(.)-.65 E 2.5(Ap)108 681.6 S
+(ath-loss color de\214nition \214le possesses the follo)-2.5 E
+(wing structure \()-.25 E F2(wnjt-dt.lcf)A F0(\):)A F1 6(;S)114 705.6 S
+(PLAT! Auto-generated Path-Loss Color Definition \("wnjt-dt.lcf"\) File)
+-6 E(;)114 717.6 Q 6(;F)114 729.6 S
+(ormat for the parameters held in this file is as follows:)-6 E F0
+(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(10)
+185.115 E EP
+%%Page: 11 11
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(;)114 84 Q 24(;d)114 96 S(B: red, green, blue)-24 E(;)114 108 Q 6(;.)
+114 120 S(..where "dB" is the path loss \(in dB\) and)-6 E 6(;")114 132
+S(red", "green", and "blue" are the corresponding RGB color)-6 E 6(;d)
+114 144 S(efinitions ranging from 0 to 255 for the region specified.)-6
+E(;)114 156 Q 6(;T)114 168 S
+(he following parameters may be edited and/or expanded)-6 E 6(;f)114 180
+S(or future runs of SPLAT!)-6 E 6(At)12 G(otal of 32 contour regions)-6
+E 6(;m)114 192 S(ay be defined in this file.)-6 E(;)114 204 Q(;)114 216
+Q(80: 255,)120 228 Q 12(0, 0)18 F(90: 255, 128,)120 240 Q(0)18 E
+(100: 255, 165,)114 252 Q(0)18 E(110: 255, 206,)114 264 Q(0)18 E
+(120: 255, 255,)114 276 Q(0)18 E(130: 184, 255,)114 288 Q(0)18 E 12
+(140: 0,)114 300 R 12(255, 0)6 F 12(150: 0,)114 312 R 12(208, 0)6 F 12
+(160: 0,)114 324 R(196, 196)6 E 12(170: 0,)114 336 R(148, 255)6 E 6
+(180: 80, 80,)114 348 R(255)6 E 12(190: 0,)114 360 R(38, 255)12 E
+(200: 142,)114 372 Q(63, 255)12 E(210: 196,)114 384 Q(54, 255)12 E
+(220: 255,)114 396 Q(0, 255)18 E(230: 255, 194, 204)114 408 Q F0 .608(I\
+f the path loss is less than 80 dB, the color Red \(RGB = 255, 0, 0\) i\
+s assigned to the re)108 444 R 3.109(gion. If)-.15 F .609(the path-)
+3.109 F .159(loss is greater than or equal to 80 dB, b)108 456 R .158(u\
+t less than 90 db, then Dark Orange \(255, 128, 0\) is assigned to the)
+-.2 F(re)108 468 Q 3.179(gion. Orange)-.15 F .679
+(\(255, 165, 0\) is assigned to re)3.179 F .679(gions ha)-.15 F .68
+(ving a path loss greater than or equal to 90 dB, b)-.2 F(ut)-.2 E
+(less than 100 dB, and so on.)108 480 Q(Gre)5 E
+(yscale terrain is displayed be)-.15 E
+(yond the 230 dB path loss contour)-.15 E(.)-.55 E/F2 10/Times-Bold@0 SF
+(SPLA)108 504 Q(T!)-.95 E F0
+(signal strength color de\214nition \214les share a v)2.5 E
+(ery similar structure \()-.15 E/F3 10/Times-Italic@0 SF(wnjt-dt.scf)A
+F0(\):)A F1 6(;S)114 528 S
+(PLAT! Auto-generated Signal Color Definition \("wnjt-dt.scf"\) File)-6
+E(;)114 540 Q 6(;F)114 552 S
+(ormat for the parameters held in this file is as follows:)-6 E(;)114
+564 Q 24(;d)114 576 S(BuV/m: red, green, blue)-24 E(;)114 588 Q 6(;.)114
+600 S(..where "dBuV/m" is the signal strength \(in dBuV/m\) and)-6 E 6
+(;")114 612 S(red", "green", and "blue" are the corresponding RGB color)
+-6 E 6(;d)114 624 S
+(efinitions ranging from 0 to 255 for the region specified.)-6 E(;)114
+636 Q 6(;T)114 648 S
+(he following parameters may be edited and/or expanded)-6 E 6(;f)114 660
+S(or future runs of SPLAT!)-6 E 6(At)12 G(otal of 32 contour regions)-6
+E 6(;m)114 672 S(ay be defined in this file.)-6 E(;)114 684 Q(;)114 696
+Q(128: 255,)114 708 Q 12(0, 0)18 F(118: 255, 165,)114 720 Q(0)18 E F0
+(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(11)
+185.115 E EP
+%%Page: 12 12
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(108: 255, 206,)114 84 Q(0)18 E(98: 255, 255,)120 96 Q(0)18 E
+(88: 184, 255,)120 108 Q(0)18 E 12(78: 0,)120 120 R 12(255, 0)6 F 12
+(68: 0,)120 132 R 12(208, 0)6 F 12(58: 0,)120 144 R(196, 196)6 E 12
+(48: 0,)120 156 R(148, 255)6 E 6(38: 80, 80,)120 168 R(255)6 E 12
+(28: 0,)120 180 R(38, 255)12 E(18: 142,)120 192 Q(63, 255)12 E(8: 140,)
+126 204 Q(0, 128)18 E F0 .178
+(If the signal strength is greater than or equal to 128 db o)108 240 R
+-.15(ve)-.15 G 2.677(r1m).15 G(icro)-2.677 E -.2(vo)-.15 G .177
+(lt per meter \(dBuV/m\), the color Red).2 F .071
+(\(255, 0, 0\) is displayed for the re)108 252 R 2.571(gion. If)-.15 F
+.071(the signal strength is greater than or equal to 118 db)2.571 F .071
+(uV/m, b)-.2 F .071(ut less)-.2 F 1.122(than 128 db)108 264 R 1.122
+(uV/m, then the color Orange \(255, 165, 0\) is displayed, and so on.)
+-.2 F(Gre)6.121 E 1.121(yscale terrain is dis-)-.15 F(played for re)108
+276 Q(gions with signal strengths less than 8 dBuV/m.)-.15 E .163(Signa\
+l strength contours for some common VHF and UHF broadcasting services i\
+n the United States are as)108 300 R(follo)108 312 Q(ws:)-.25 E F1
+(Analog Television Broadcasting)150 336 Q
+(------------------------------)150 348 Q(Channels 2-6:)150 360 Q
+(City Grade: >= 74 dBuV/m)42 E(Grade A: >= 68 dBuV/m)288 372 Q
+(Grade B: >= 47 dBuV/m)288 384 Q
+(--------------------------------------------)150 396 Q(Channels 7-13:)
+150 408 Q(City Grade: >= 77 dBuV/m)36 E(Grade A: >= 71 dBuV/m)288 420 Q
+(Grade B: >= 56 dBuV/m)288 432 Q
+(--------------------------------------------)150 444 Q(Channels 14-69:)
+150 456 Q(Indoor Grade: >= 94 dBuV/m)18 E(City Grade: >= 80 dBuV/m)270
+468 Q(Grade A: >= 74 dBuV/m)288 480 Q(Grade B: >= 64 dBuV/m)288 492 Q
+(Digital Television Broadcasting)150 516 Q
+(-------------------------------)150 528 Q(Channels 2-6:)150 540 Q
+(City Grade: >= 35 dBuV/m)42 E(Service Threshold: >= 28 dBuV/m)228 552 Q
+(--------------------------------------------)150 564 Q(Channels 7-13:)
+150 576 Q(City Grade: >= 43 dBuV/m)36 E(Service Threshold: >= 36 dBuV/m)
+228 588 Q(--------------------------------------------)150 600 Q
+(Channels 14-69:)150 612 Q(City Grade: >= 48 dBuV/m)30 E
+(Service Threshold: >= 41 dBuV/m)228 624 Q
+(NOAA Weather Radio \(162.400 - 162.550 MHz\))150 648 Q
+(------------------------------------------)150 660 Q
+(Reliable: >= 18 dBuV/m)216 672 Q(Not reliable: <)192 684 Q(18 dBuV/m)12
+E(Unlikely to receive: <)150 696 Q 6(0d)12 G(BuV/m)-6 E
+(FM Radio Broadcasting \(88.1 - 107.9 MHz\))150 720 Q F0(KD2BD Softw)72
+768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(12)185.115 E EP
+%%Page: 13 13
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(----------------------------------------)150 84 Q
+(Analog Service Contour:)150 96 Q(60 dBuV/m)12 E
+(Digital Service Contour: 65 dBuV/m)150 108 Q/F2 10.95/Times-Bold@0 SF
+(ANTENN)72 148.8 Q 2.738(AR)-.219 G(ADIA)-2.738 E(TION P)-1.04 E -1.04
+(AT)-.81 G(TERN P)1.04 E(ARAMETERS)-.81 E F0 .977(Normalized \214eld v)
+108 160.8 R .977(oltage patterns for a transmitting antenna')-.2 F 3.477
+(sh)-.55 G .977(orizontal and v)-3.477 F .977
+(ertical planes are imported)-.15 F .587(automatically into)108 172.8 R
+/F3 10/Times-Bold@0 SF(SPLA)3.087 E(T!)-.95 E F0 .587(when a Longle)
+3.087 F .588(y-Rice co)-.15 F -.15(ve)-.15 G .588
+(rage analysis is performed.).15 F .588(Antenna pattern data is)5.588 F
+.805(read from a pair of \214les ha)108 184.8 R .805
+(ving the same base name as the transmitter and LRP \214les, b)-.2 F
+.804(ut with)-.2 F/F4 10/Times-Italic@0 SF(.az)3.304 E F0(and)3.304 E F4
+(.el)3.304 E F0 -.15(ex)108 196.8 S .307(tensions for azimuth and ele)
+.15 F -.25(va)-.25 G .307(tion pattern \214les, respecti).25 F -.15(ve)
+-.25 G(ly).15 E 5.308(.S)-.65 G .308(peci\214cations re)-5.308 F -.05
+(ga)-.15 G .308(rding pattern rotation \(if).05 F(an)108 208.8 Q .451
+(y\) and mechanical beam tilt and tilt direction \(if an)-.15 F .45
+(y\) are also contained within)-.15 F F3(SPLA)2.95 E(T!)-.95 E F0 .45
+(antenna pattern)2.95 F(\214les.)108 220.8 Q -.15(Fo)108 244.8 S 2.5(re)
+.15 G(xample, the \214rst fe)-2.65 E 2.5(wl)-.25 G(ines of a)-2.5 E F3
+(SPLA)2.5 E(T!)-.95 E F0(azimuth pattern \214le might appear as follo)
+2.5 E(ws \()-.25 E F4(kvea.az)A F0(\):)A F1(183.0)156 268.8 Q 42(00)156
+280.8 S(.8950590)-42 E 42(10)156 292.8 S(.8966406)-42 E 42(20)156 304.8
+S(.8981447)-42 E 42(30)156 316.8 S(.8995795)-42 E 42(40)156 328.8 S
+(.9009535)-42 E 42(50)156 340.8 S(.9022749)-42 E 42(60)156 352.8 S
+(.9035517)-42 E 42(70)156 364.8 S(.9047923)-42 E 42(80)156 376.8 S
+(.9060051)-42 E F0 1.777(The \214rst line of the)108 400.8 R F4(.az)
+4.277 E F0 1.778(\214le speci\214es the amount of azimuthal pattern rot\
+ation \(measured clockwise in)4.277 F(de)108 412.8 Q .063(grees from T)
+-.15 F .063(rue North\) to be applied by)-.35 F F3(SPLA)2.563 E(T!)-.95
+E F0 .062(to the data contained in the)2.563 F F4(.az)2.562 E F0 2.562
+(\214le. This)2.562 F .062(is follo)2.562 F .062(wed by)-.25 F .87
+(azimuth headings \(0 to 360 de)108 424.8 R .871(grees\) and their asso\
+ciated normalized \214eld patterns \(0.000 to 1.000\) sepa-)-.15 F
+(rated by whitespace.)108 436.8 Q .069(The structure of)108 460.8 R F3
+(SPLA)2.569 E(T!)-.95 E F0(ele)2.569 E -.25(va)-.25 G .069
+(tion pattern \214les is slightly dif).25 F 2.569(ferent. The)-.25 F
+.069(\214rst line of the)2.569 F F4(.el)2.569 E F0 .068
+(\214le speci\214es the)2.569 F .891
+(amount of mechanical beam tilt applied to the antenna.)108 472.8 R .892
+(Note that a)5.892 F F4(downwar)3.392 E 3.392(dt)-.37 G(ilt)-3.392 E F0
+(\(belo)3.392 E 3.392(wt)-.25 G .892(he horizon\) is)-3.392 F -.15(ex)
+108 484.8 S 1.102(pressed as a).15 F F4 1.101(positive angle)3.602 F F0
+3.601(,w)C 1.101(hile an)-3.601 F F4(upwar)3.601 E 3.601(dt)-.37 G(ilt)
+-3.601 E F0(\(abo)3.601 E 1.401 -.15(ve t)-.15 H 1.101
+(he horizon\) is e).15 F 1.101(xpressed as a)-.15 F F4(ne)3.601 E 1.101
+(gative angle)-.4 F F0(.)A(This data is follo)108 496.8 Q
+(wed by the azimuthal direction of the tilt, separated by whitespace.)
+-.25 E .436(The remainder of the \214le consists of ele)108 520.8 R -.25
+(va)-.25 G .437(tion angles and their corresponding normalized v).25 F
+.437(oltage radiation)-.2 F .248(pattern \(0.000 to 1.000\) v)108 532.8
+R .248(alues separated by whitespace.)-.25 F(Ele)5.248 E -.25(va)-.25 G
+.247(tion angles must be speci\214ed o).25 F -.15(ve)-.15 G 2.747(ra-)
+.15 G .247(10.0 to)-2.747 F .13(+90.0 de)108 544.8 R .13(gree range.)
+-.15 F .13(As w)5.13 F .13(as the con)-.1 F -.15(ve)-.4 G .131
+(ntion with mechanical beamtilt,).15 F F4(ne)2.631 E .131(gative ele)-.4
+F .131(vation angles)-.15 F F0 .131(are used to)2.631 F(represent ele)
+108 556.8 Q -.25(va)-.25 G(tions).25 E F4(abo)2.5 E(ve the horizon)-.1 E
+F0 2.5(,w)C(hile)-2.5 E F4(positive angles)2.5 E F0(represents ele)2.5 E
+-.25(va)-.25 G(tions).25 E F4(below the horizon)2.5 E F0(.)A -.15(Fo)108
+580.8 S 2.5(re).15 G(xample, the \214rst fe)-2.65 E 2.5(wl)-.25 G
+(ines a)-2.5 E F3(SPLA)2.5 E(T!)-.95 E F0(ele)2.5 E -.25(va)-.25 G
+(tion pattern \214le might appear as follo).25 E(ws \()-.25 E F4
+(kvea.el)A F0(\):)A F1 18(1.1 130.0)156 604.8 R 12(-10.0 0.172)150 616.8
+R 18(-9.5 0.109)150 628.8 R 18(-9.0 0.115)150 640.8 R 18(-8.5 0.155)150
+652.8 R 18(-8.0 0.157)150 664.8 R 18(-7.5 0.104)150 676.8 R 18
+(-7.0 0.029)150 688.8 R 18(-6.5 0.109)150 700.8 R 18(-6.0 0.185)150
+712.8 R F0(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F(September 2007)2.5
+E(13)185.115 E EP
+%%Page: 14 14
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E 1.538(In this e)108
+84 R 1.538(xample, the antenna is mechanically tilted do)-.15 F(wnw)-.25
+E 1.538(ard 1.1 de)-.1 F 1.538(grees to)-.15 F -.1(wa)-.25 G 1.538
+(rds an azimuth of 130.0).1 F(de)108 96 Q(grees.)-.15 E -.15(Fo)108 120
+S 3.446(rb).15 G .946(est results, the resolution of azimuth pattern da\
+ta should be speci\214ed to the nearest de)-3.446 F .947(gree azimuth,)
+-.15 F 1.3(and ele)108 132 R -.25(va)-.25 G 1.299(tion pattern data res\
+olution should be speci\214ed to the nearest 0.01 de).25 F 3.799
+(grees. If)-.15 F 1.299(the pattern data)3.799 F .549
+(speci\214ed does not reach this le)108 144 R -.15(ve)-.25 G 3.049(lo)
+.15 G 3.049(fr)-3.049 G(esolution,)-3.049 E/F1 10/Times-Bold@0 SF(SPLA)
+3.049 E(T!)-.95 E F0 .55(will interpolate the v)3.049 F .55(alues pro)
+-.25 F .55(vided to determine)-.15 F(the data at the required resolutio\
+n, although this may result in a loss in accurac)108 156 Q -.65(y.)-.15
+G/F2 10.95/Times-Bold@0 SF(IMPOR)72 184.8 Q(TING AND EXPOR)-.438 E
+(TING REGION)-.438 E(AL P)-.219 E -1.04(AT)-.81 G 2.738(HL)1.04 G
+(OSS CONT)-2.738 E(OUR D)-.197 E -1.644 -1.04(AT A)-.383 H F0 .254
+(Performing a Longle)108 196.8 R .254(y-Rice co)-.15 F -.15(ve)-.15 G
+.254(rage analysis can be a v).15 F .254
+(ery time consuming process, especially if the anal-)-.15 F .935
+(ysis is repeated repeatedly to disco)108 208.8 R -.15(ve)-.15 G 3.435
+(rw).15 G .936(hat ef)-3.435 F .936
+(fects changes to the antenna radiation patterns mak)-.25 F 3.436(et)-.1
+G 3.436(ot)-3.436 G(he)-3.436 E(predicted co)108 220.8 Q -.15(ve)-.15 G
+(rage area.).15 E .722(This process can be e)108 244.8 R .722
+(xpedited by e)-.15 F .722(xporting the Longle)-.15 F .722(y-Rice re)
+-.15 F .722(gional path loss contour data to an output)-.15 F .775
+(\214le, modifying the path loss data e)108 256.8 R .775
+(xternally to incorporate antenna pattern ef)-.15 F .776
+(fects, and then importing the)-.25 F
+(modi\214ed path loss data back into)108 268.8 Q F1(SPLA)2.5 E(T!)-.95 E
+F0(to rapidly produce a re)5 E(vised path loss map.)-.25 E -.15(Fo)108
+292.8 S 3.254(re).15 G .753
+(xample, a path loss output \214le can be generated by)-3.404 F F1(SPLA)
+3.253 E(T!)-.95 E F0 .753(for a recei)5.753 F 1.053 -.15(ve s)-.25 H
+.753(ite 30 feet abo).15 F 1.053 -.15(ve g)-.15 H(round).15 E(le)108
+304.8 Q -.15(ve)-.25 G 2.997(lo).15 G -.15(ve)-3.147 G 2.997(ra5).15 G
+2.997(0m)-2.997 G .498(ile radius surrounding a transmitter site to a m\
+aximum path loss of 140 dB using the fol-)-2.997 F(lo)108 316.8 Q
+(wing syntax:)-.25 E/F3 10/Courier@0 SF
+(splat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat)108 340.8 Q F1
+(SPLA)108 364.8 Q(T!)-.95 E F0 .045(path loss output \214les often e)
+2.545 F .044(xceed 100 me)-.15 F -.05(ga)-.15 G .044(bytes in size.).05
+F(The)5.044 E 2.544(yc)-.15 G .044(ontain information relating to the)
+-2.544 F 2.58(boundaries of re)108 376.8 R 2.58(gion the)-.15 F 5.08(yd)
+-.15 G 2.58(escribe follo)-5.08 F 2.58(wed by latitudes \(de)-.25 F 2.58
+(grees North\), longitudes \(de)-.15 F 2.58(grees W)-.15 F(est\),)-.8 E
+.656(azimuths, ele)108 388.8 R -.25(va)-.25 G .656(tions \(to the \214r\
+st obstruction\), and path loss \214gures \(dB\) for a series of speci\
+\214c points that).25 F .541(comprise the re)108 400.8 R .541
+(gion surrounding the transmitter site.)-.15 F .542(The \214rst fe)5.542
+F 3.042(wl)-.25 G .542(ines of a)-3.042 F F1(SPLA)3.042 E(T!)-.95 E F0
+.542(path loss output \214le)3.042 F(tak)108 412.8 Q 2.5(eo)-.1 G 2.5
+(nt)-2.5 G(he follo)-2.5 E(wing appearance \()-.25 E/F4 10
+/Times-Italic@0 SF(pathloss.dat)A F0(\):)A F3(119, 117)156 436.8 Q 6(;m)
+24 G(ax_west, min_west)-6 E(35, 33)156 448.8 Q 6(;m)36 G
+(ax_north, min_north)-6 E
+(34.2265434, 118.0631104, 48.171, -37.461, 67.70)156 460.8 Q
+(34.2270355, 118.0624390, 48.262, -26.212, 73.72)156 472.8 Q
+(34.2280197, 118.0611038, 48.269, -14.951, 79.74)156 484.8 Q
+(34.2285156, 118.0604401, 48.207, -11.351, 81.68)156 496.8 Q
+(34.2290077, 118.0597687, 48.240, -10.518, 83.26)156 508.8 Q
+(34.2294998, 118.0591049, 48.225, 23.201, 84.60)156 520.8 Q
+(34.2304878, 118.0577698, 48.213, 15.769, 137.84)156 532.8 Q
+(34.2309799, 118.0570984, 48.234, 15.965, 151.54)156 544.8 Q
+(34.2314720, 118.0564346, 48.224, 16.520, 149.45)156 556.8 Q
+(34.2319679, 118.0557632, 48.223, 15.588, 151.61)156 568.8 Q
+(34.2329521, 118.0544281, 48.230, 13.889, 135.45)156 580.8 Q
+(34.2334442, 118.0537643, 48.223, 11.693, 137.37)156 592.8 Q
+(34.2339401, 118.0530930, 48.222, 14.050, 126.32)156 604.8 Q
+(34.2344322, 118.0524292, 48.216, 16.274, 156.28)156 616.8 Q
+(34.2354164, 118.0510941, 48.222, 15.058, 152.65)156 628.8 Q
+(34.2359123, 118.0504227, 48.221, 16.215, 158.57)156 640.8 Q
+(34.2364044, 118.0497589, 48.216, 15.024, 157.30)156 652.8 Q
+(34.2368965, 118.0490875, 48.225, 17.184, 156.36)156 664.8 Q F0 .135
+(It is not uncommon for)108 688.8 R F1(SPLA)2.635 E(T!)-.95 E F0 .135
+(path loss \214les to contain as man)2.635 F 2.635(ya)-.15 G 2.635(s3m)
+-2.635 G .134(illion or more lines of data.)-2.635 F(Com-)5.134 E 1.164
+(ments can be placed in the \214le if the)108 700.8 R 3.664(ya)-.15 G
+1.164(re proceeded by a semicolon character)-3.664 F 6.164(.T)-.55 G(he)
+-6.164 E F1(vim)3.665 E F0(te)3.665 E 1.165(xt editor has)-.15 F(pro)108
+712.8 Q -.15(ve)-.15 G 2.5(nc).15 G
+(apable of editing \214les of this size.)-2.5 E(KD2BD Softw)72 768 Q
+120.785(are 16)-.1 F(September 2007)2.5 E(14)185.115 E EP
+%%Page: 15 15
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .808(Note as w)108
+84 R .807(as the case in the antenna pattern \214les, ne)-.1 F -.05(ga)
+-.15 G(ti).05 E 1.107 -.15(ve e)-.25 H(le).15 E -.25(va)-.25 G .807
+(tion angles refer to upw).25 F .807(ard tilt \(abo)-.1 F 1.107 -.15
+(ve t)-.15 H(he).15 E .94(horizon\), while positi)108 96 R 1.24 -.15
+(ve a)-.25 H .94(ngles refer to do).15 F(wnw)-.25 E .94(ard tilt \(belo)
+-.1 F 3.44(wt)-.25 G .94(he horizon\).)-3.44 F .94
+(These angles refer to the ele-)5.94 F -.25(va)108 108 S 1.076
+(tion to the recei).25 F 1.076(ving antenna at the height abo)-.25 F
+1.376 -.15(ve g)-.15 H 1.076(round le).15 F -.15(ve)-.25 G 3.575(ls).15
+G 1.075(peci\214ed using the)-3.575 F/F1 10/Times-Italic@0 SF(-L)3.575 E
+F0(switch)3.575 E F1(if)3.575 E F0 1.075(the path)3.575 F 2.35
+(between transmitter and recei)108 120 R -.15(ve)-.25 G 4.85(ri).15 G
+4.85(su)-4.85 G 4.85(nobstructed. If)-4.85 F 2.35
+(the path between the transmitter and recei)4.85 F -.15(ve)-.25 G 4.85
+(ri).15 G(s)-4.85 E .01(obstructed, then the ele)108 132 R -.25(va)-.25
+G .01(tion angle to the \214rst obstruction is returned by).25 F/F2 10
+/Times-Bold@0 SF(SPLA)2.509 E(T!)-.95 E F0 5.009(.T)C .009
+(his is because the Lon-)-5.009 F(gle)108 144 Q .261
+(y-Rice model considers the ener)-.15 F .262
+(gy reaching a distant point o)-.18 F -.15(ve)-.15 G 2.762(ra).15 G
+2.762(no)-2.762 G .262(bstructed path as a deri)-2.762 F -.25(va)-.25 G
+(ti).25 E .562 -.15(ve o)-.25 H 2.762(ft).15 G(he)-2.762 E(ener)108 156
+Q .489(gy scattered from the top of the \214rst obstruction, only)-.18 F
+5.489(.S)-.65 G .489(ince ener)-5.489 F .488
+(gy cannot reach the obstructed loca-)-.18 F(tion directly)108 168 Q 2.5
+(,t)-.65 G(he actual ele)-2.5 E -.25(va)-.25 G
+(tion angle to that point is irrele).25 E -.25(va)-.25 G(nt.).25 E 1.141
+(When modifying)108 192 R F2(SPLA)3.641 E(T!)-.95 E F0 1.141
+(path loss \214les to re\215ect antenna pattern data,)3.641 F F1 1.142
+(only the last column \(path loss\))3.641 F F0 .233
+(should be amended to re\215ect the antenna')108 204 R 2.733(sn)-.55 G
+.233(ormalized g)-2.733 F .233(ain at the azimuth and ele)-.05 F -.25
+(va)-.25 G .233(tion angles speci\214ed in).25 F .395(the \214le.)108
+216 R .395(\(At this time, programs and scripts capable of performing t\
+his operation are left as an e)5.395 F -.15(xe)-.15 G .395(rcise for).15
+F(the user)108 228 Q(.\))-.55 E
+(Modi\214ed path loss maps can be imported back into)108 252 Q F2(SPLA)
+2.5 E(T!)-.95 E F0(for generating re)2.5 E(vised co)-.25 E -.15(ve)-.15
+G(rage maps:).15 E/F3 10/Courier@0 SF
+(splat -t kvea -pli pathloss.dat -s city.dat -b county.dat -o map.ppm)
+108 276 Q F2(SPLA)108 300 Q(T!)-.95 E F0 .006
+(path loss \214les can also be used for conducting co)2.507 F -.15(ve)
+-.15 G .006(rage or interference studies outside of).15 F F2(SPLA)2.506
+E(T!)-.95 E F0(.)A/F4 10.95/Times-Bold@0 SF
+(USER-DEFINED TERRAIN INPUT FILES)72 316.8 Q F0 3.541(Au)108 328.8 S
+(ser)-3.541 E 1.041(-de\214ned terrain \214le is a user)-.2 F 1.041
+(-generated te)-.2 F 1.042
+(xt \214le containing latitudes, longitudes, and heights abo)-.15 F -.15
+(ve)-.15 G 1.073(ground le)108 340.8 R -.15(ve)-.25 G 3.573(lo).15 G
+3.573(fs)-3.573 G 1.073(peci\214c terrain features belie)-3.573 F -.15
+(ve)-.25 G 3.573(dt).15 G 3.573(ob)-3.573 G 3.572(eo)-3.573 G 3.572(fi)
+-3.572 G 1.072(mportance to the)-3.572 F F2(SPLA)3.572 E(T!)-.95 E F0
+1.072(analysis being con-)3.572 F .601(ducted, b)108 352.8 R .601
+(ut noticeably absent from the SDF \214les being used.)-.2 F 3.101(Au)
+5.601 G(ser)-3.101 E .601(-de\214ned terrain \214le is imported into a)
+-.2 F F2(SPLA)108 364.8 Q(T!)-.95 E F0(analysis using the)2.5 E F1(-udt)
+2.5 E F0(switch:)2.5 E F3
+(splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm)114 388.8 Q F0
+2.5(Au)108 412.8 S(ser)-2.5 E(-de\214ned terrain \214le has the follo)
+-.2 E(wing appearance and structure:)-.25 E F3
+(40.32180556, 74.1325, 100.0 meters)150 436.8 Q
+(40.321805, 74.1315, 300.0)150 448.8 Q
+(40.3218055, 74.1305, 100.0 meters)150 460.8 Q F0 -.7(Te)108 484.8 S
+1.42(rrain height is interpreted as being described in feet abo).7 F
+1.72 -.15(ve g)-.15 H 1.42(round le).15 F -.15(ve)-.25 G 3.92(lu).15 G
+1.42(nless follo)-3.92 F 1.42(wed by the w)-.25 F(ord)-.1 E F1(meter)108
+496.8 Q(s)-.1 E F0 3.328(,a)C .829(nd is added)-3.328 F F1 .829
+(on top of)3.329 F F0 .829
+(the terrain speci\214ed in the SDF data for the locations speci\214ed.)
+3.329 F .829(Be a)5.829 F -.1(wa)-.15 G(re).1 E 1.061(that each user)108
+508.8 R 1.061(-de\214ned terrain feature speci\214ed will be interprete\
+d as being 3-arc seconds in both latitude)-.2 F .281(and longitude.)108
+520.8 R .281(Features described in the user)5.281 F .281
+(-de\214ned terrain \214le that o)-.2 F -.15(ve)-.15 G .282(rlap pre).15
+F .282(viously de\214ned features in)-.25 F(the \214le are ignored by)
+108 532.8 Q F2(SPLA)2.5 E(T!)-.95 E F0(.)A F4(SIMPLE T)72 549.6 Q
+(OPOGRAPHIC MAP GENERA)-.197 E(TION)-1.04 E F0 .034(In certain situatio\
+ns it may be desirable to generate a topographic map of a re)108 561.6 R
+.034(gion without plotting co)-.15 F -.15(ve)-.15 G(rage).15 E .969
+(areas, line-of-sight paths, or generating obstruction reports.)108
+573.6 R .969(There are se)5.969 F -.15(ve)-.25 G .969(ral w).15 F .97
+(ays of doing this.)-.1 F .97(If one)5.97 F .162(wishes to generate a t\
+opographic map illustrating the location of a transmitter and recei)108
+585.6 R -.15(ve)-.25 G 2.661(rs).15 G .161(ite along with a)-2.661 F
+.138(brief te)108 597.6 R .139(xt report describing the locations and d\
+istances between the sites, the)-.15 F F1(-n)2.639 E F0 .139
+(switch should be in)2.639 F -.2(vo)-.4 G -.1(ke).2 G 2.639(da).1 G(s)
+-2.639 E(follo)108 609.6 Q(ws:)-.25 E F3
+(splat -t tx_site -r rx_site -n -o topo_map.ppm)108 633.6 Q F0(If no te)
+108 657.6 Q(xt report is desired, then the)-.15 E F1(-N)2.5 E F0
+(switch is used:)2.5 E F3
+(splat -t tx_site -r rx_site -N -o topo_map.ppm)108 681.6 Q F0 .994(If \
+a topographic map centered about a single site out to a minimum speci\
+\214ed radius is desired instead, a)108 705.6 R
+(command similar to the follo)108 717.6 Q(wing can be used:)-.25 E
+(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(15)
+185.115 E EP
+%%Page: 16 16
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(splat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o topo_map.ppm)
+108 84 Q F0 .962(where -R speci\214es the minimum radius of the map in \
+miles \(or kilometers if the)108 108 R/F2 10/Times-Italic@0 SF(-metric)
+3.463 E F0 .963(switch is used\).)3.463 F .492
+(Note that the tx_site name and location are not displayed in this e)108
+120 R 2.991(xample. If)-.15 F .491(display of this information is)2.991
+F .057(desired, simply create a)108 132 R/F3 10/Times-Bold@0 SF(SPLA)
+2.557 E(T!)-.95 E F0 .057(city \214le \()2.557 F F2(-s)A F0 .057
+(option\) and append it to the list of command-line options illus-)2.557
+F(trated abo)108 144 Q -.15(ve)-.15 G(.).15 E .592(If the)108 168 R F2
+(-o)3.092 E F0 .592(switch and output \214lename are omitted in these o\
+perations, topographic output is written to a \214le)3.092 F(named)108
+180 Q F2(tx_site)2.5 E(.ppm)-.15 E F0(in the current w)2.5 E
+(orking directory by def)-.1 E(ault.)-.1 E/F4 10.95/Times-Bold@0 SF
+(GEOREFERENCE FILE GENERA)72 196.8 Q(TION)-1.04 E F0 -.8(To)108 208.8 S
+.849(pographic, co).8 F -.15(ve)-.15 G .849(rage \().15 F F2(-c)A F0
+.849(\), and path loss contour \()B F2(-L)A F0 3.349(\)m)C .849
+(aps generated by)-3.349 F F3(SPLA)3.35 E(T!)-.95 E F0 .85
+(may be imported into)3.35 F F3(Xastir)108 220.8 Q F0 .176
+(\(X Amateur Station T)2.676 F .175
+(racking and Information Reporting\) softw)-.35 F .175
+(are by generating a georeference \214le)-.1 F(using)108 232.8 Q F3
+(SPLA)2.5 E(T!)-.95 E F0 -.55('s)C F2(-g)3.05 E(eo)-.1 E F0(switch:)2.5
+E F1(splat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o map.ppm)
+108 256.8 Q F0 1.515(The georeference \214le generated will ha)108 280.8
+R 1.815 -.15(ve t)-.2 H 1.516(he same base name as the).15 F F2(-o)4.016
+E F0 1.516(\214le speci\214ed, b)4.016 F 1.516(ut ha)-.2 F 1.816 -.15
+(ve a)-.2 H F2(.g)6.666 E(eo)-.1 E F0 -.15(ex)108 292.8 S
+(tension, and permit proper interpretation and display of).15 E F3(SPLA)
+2.5 E(T!)-.95 E F0 1.1 -.55('s .)D(ppm graphics in).55 E F3(Xastir)2.5 E
+F0(softw)2.5 E(are.)-.1 E F4(GOOGLE MAP KML FILE GENERA)72 309.6 Q(TION)
+-1.04 E F0 -2.15 -.25(Ke y)108 321.6 T .775
+(hole Markup Language \214les compatible with).25 F F3 .774
+(Google Earth)3.274 F F0 .774(may be generated by)3.274 F F3(SPLA)3.274
+E(T!)-.95 E F0 .774(when per)3.274 F(-)-.2 E
+(forming point-to-point or re)108 333.6 Q(gional co)-.15 E -.15(ve)-.15
+G(rage analyses by in).15 E -.2(vo)-.4 G(king the).2 E F2(-kml)2.5 E F0
+(switch:)2.5 E F1(splat -t wnjt-dt -r kd2bd -kml)108 357.6 Q F0 .233
+(The KML \214le generated will ha)108 381.6 R .533 -.15(ve t)-.2 H .233
+(he same \214lename structure as a P).15 F .233
+(ath Analysis Report for the transmitter)-.15 F(and recei)108 393.6 Q
+-.15(ve)-.25 G 2.5(rs).15 G(ite names gi)-2.5 E -.15(ve)-.25 G(n, e).15
+E(xcept it will carry a)-.15 E F2(.kml)5 E F0 -.15(ex)2.5 G(tension.).15
+E 1.619(Once loaded into)108 417.6 R F3 1.619(Google Earth)4.119 F F0
+1.618(\(File --> Open\), the KML \214le will annotate the map display w\
+ith the)4.118 F .567(names of the transmitter and recei)108 429.6 R -.15
+(ve)-.25 G 3.067(rs).15 G .568(ite locations.)-3.067 F .568(The vie)
+5.568 F .568(wpoint of the image will be from the position)-.25 F 1.317
+(of the transmitter site looking to)108 441.6 R -.1(wa)-.25 G 1.317
+(rds the location of the recei).1 F -.15(ve)-.25 G 4.916 -.55(r. T).15 H
+1.316(he point-to-point path between the).55 F .792(sites will be displ\
+ayed as a white line while the RF line-of-sight path will be displayed \
+in green.)108 453.6 R F3(Google)5.792 E(Earth)108 465.6 Q F0 1.844 -.55
+('s n)D -.2(av).55 G(ig).2 E .744(ation tools allo)-.05 F 3.243(wt)-.25
+G .743(he user to "\215y" around the path, identify landmarks, roads, a\
+nd other fea-)-3.243 F(tured content.)108 477.6 Q .786
+(When performing re)108 501.6 R .786(gional co)-.15 F -.15(ve)-.15 G
+.786(rage analysis, the).15 F F2(.kml)5.787 E F0 .787
+(\214le generated by)3.287 F F3(SPLA)3.287 E(T!)-.95 E F0 .787
+(will permit path loss or)3.287 F .267
+(signal strength contours to be layered on top of)108 513.6 R F3 .267
+(Google Earth)2.767 F F0 1.367 -.55('s d)D .267
+(isplay in a semi-transparent manner).55 F 5.266(.T)-.55 G(he)-5.266 E
+(generated)108 525.6 Q F2(.kml)2.5 E F0(\214le will ha)2.5 E .3 -.15
+(ve t)-.2 H(he same basename as that of the).15 E F2(.ppm)2.5 E F0
+(\214le normally generated.)2.5 E F4(DETERMIN)72 542.4 Q -1.04(AT)-.219
+G(ION OF ANTENN)1.04 E 2.738(AH)-.219 G(EIGHT ABO)-2.738 E(VE A)-.548 E
+(VERA)-1.588 E(GE TERRAIN)-.602 E F3(SPLA)108 554.4 Q(T!)-.95 E F0 .947
+(determines antenna height abo)3.447 F 1.248 -.15(ve a)-.15 H -.15(ve)
+-.05 G .948(rage terrain \(HAA).15 F .948
+(T\) according to the procedure de\214ned by)-1.11 F .167
+(Federal Communications Commission P)108 566.4 R .167(art 73.313\(d\).)
+-.15 F .166(According to this de\214nition, terrain ele)5.166 F -.25(va)
+-.25 G .166(tions along).25 F .794(eight radials between 2 and 10 miles\
+ \(3 and 16 kilometers\) from the site being analyzed are sampled and)
+108 578.4 R -2.25 -.2(av e)108 590.4 T .614(raged for each 45 de).2 F
+.613(grees of azimuth starting with T)-.15 F .613(rue North.)-.35 F .613
+(If one or more radials lie entirely o)5.613 F -.15(ve)-.15 G(r).15 E
+-.1(wa)108 602.4 S .534(ter or o).1 F -.15(ve)-.15 G 3.034(rl).15 G .535
+(and outside the United States \(areas for which no USGS topograph)
+-3.034 F 3.035(yd)-.05 G .535(ata is a)-3.035 F -.25(va)-.2 G .535
+(ilable\), then).25 F
+(those radials are omitted from the calculation of a)108 614.4 Q -.15
+(ve)-.2 G(rage terrain.).15 E .918(Note that SR)108 638.4 R .918(TM ele)
+-.6 F -.25(va)-.25 G .918(tion data, unlik).25 F 3.418(eo)-.1 G .917
+(lder 3-arc second USGS data, e)-3.418 F .917(xtends be)-.15 F .917
+(yond the borders of the)-.15 F .866(United States.)108 650.4 R .867
+(Therefore, HAA)5.866 F 3.367(Tr)-1.11 G .867
+(esults may not be in full compliance with FCC P)-3.367 F .867
+(art 73.313\(d\) in areas)-.15 F
+(along the borders of the United States if the SDF \214les used by)108
+662.4 Q F3(SPLA)2.5 E(T!)-.95 E F0(are SR)2.5 E(TM-deri)-.6 E -.15(ve)
+-.25 G(d.).15 E .162(When performing point-to-point terrain analysis,)
+108 686.4 R F3(SPLA)2.662 E(T!)-.95 E F0 .162
+(determines the antenna height abo)2.662 F .461 -.15(ve a)-.15 H -.15
+(ve)-.05 G .161(rage ter).15 F(-)-.2 E .407(rain only if enough topogra\
+phic data has already been loaded by the program to perform the point-t\
+o-point)108 698.4 R 3.712(analysis. In)108 710.4 R 1.211(most cases, th\
+is will be true, unless the site in question does not lie within 10 mil\
+es of the)3.712 F(boundary of the topograph)108 722.4 Q 2.5(yd)-.05 G
+(ata in memory)-2.5 E(.)-.65 E(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F
+(September 2007)2.5 E(16)185.115 E EP
+%%Page: 17 17
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .491
+(When performing area prediction analysis, enough topograph)108 84 R
+2.991(yd)-.05 G .492(ata is normally loaded by)-2.991 F/F1 10
+/Times-Bold@0 SF(SPLA)2.992 E(T!)-.95 E F0 .492(to per)2.992 F(-)-.2 E
+.807(form a)108 96 R -.15(ve)-.2 G .807(rage terrain calculations.).15 F
+.807(Under such conditions,)5.807 F F1(SPLA)3.307 E(T!)-.95 E F0 .807
+(will pro)3.307 F .807(vide the antenna height abo)-.15 F -.15(ve)-.15 G
+-2.25 -.2(av e)108 108 T .203(rage terrain as well as the a).2 F -.15
+(ve)-.2 G .203(rage terrain abo).15 F .503 -.15(ve m)-.15 H .203
+(ean sea le).15 F -.15(ve)-.25 G 2.704(lf).15 G .204
+(or azimuths of 0, 45, 90, 135, 180, 225,)-2.704 F .162(270, and 315 de)
+108 120 R .162
+(grees, and include such information in the generated site report.)-.15
+F .161(If one or more of the eight)5.161 F 1.004(radials surv)108 132 R
+-.15(ey)-.15 G 1.004(ed f).15 F 1.004(all o)-.1 F -.15(ve)-.15 G 3.504
+(rw).15 G(ater)-3.604 E 3.504(,o)-.4 G 3.504(ro)-3.504 G -.15(ve)-3.654
+G 3.504(rr).15 G -.15(eg)-3.504 G 1.004(ions for which no SDF data is a)
+.15 F -.25(va)-.2 G(ilable,).25 E F1(SPLA)3.504 E(T!)-.95 E F0(reports)
+3.505 E/F2 10/Times-Italic@0 SF(No)3.505 E -.92(Te)108 144 S(rr).92 E
+(ain)-.15 E F0(for the radial paths af)2.5 E(fected.)-.25 E/F3 10.95
+/Times-Bold@0 SF(RESTRICTING THE MAXIMUM SIZE OF AN AN)72 160.8 Q(AL)
+-.219 E(YSIS REGION)-1.007 E F1(SPLA)108 172.8 Q(T!)-.95 E F0 1.004(rea\
+ds SDF \214les as needed into a series of memory "pages" within the str\
+ucture of the program.)3.505 F .121
+(Each "page" holds one SDF \214le representing a one de)108 184.8 R .121
+(gree by one de)-.15 F .121(gree re)-.15 F .121(gion of terrain.)-.15 F
+(A)5.121 E F2 .122(#de\214ne MAX-)2.622 F -1.05 -.9(PA G)108 196.8 T(ES)
+.9 E F0 .774(statement in the \214rst se)3.274 F -.15(ve)-.25 G .774
+(ral lines of).15 F F2(splat.cpp)3.274 E F0 .774
+(sets the maximum number of "pages" a)3.274 F -.25(va)-.2 G .773
+(ilable for).25 F 1.054(holding topograph)108 208.8 R 3.554(yd)-.05 G
+3.554(ata. It)-3.554 F 1.055
+(also sets the maximum size of the topographic maps generated by)3.554 F
+F1(SPLA)3.555 E(T!)-.95 E F0(.)A(MAXP)108 220.8 Q -.4(AG)-.92 G .231
+(ES is set to 9 by def).4 F 2.731(ault. If)-.1 F F1(SPLA)2.731 E(T!)-.95
+E F0 .231(produces a se)5.231 F .23(gmentation f)-.15 F .23
+(ault on start-up with this def)-.1 F(ault,)-.1 E .91
+(it is an indication that not enough RAM and/or virtual memory \(sw)108
+232.8 R .911(ap space\) is a)-.1 F -.25(va)-.2 G .911(ilable to run).25
+F F1(SPLA)3.411 E(T!)-.95 E F0 1.49(with the number of MAXP)108 244.8 R
+-.4(AG)-.92 G 1.489(ES speci\214ed.).4 F 1.489(In situations where a)
+6.489 F -.25(va)-.2 G 1.489(ilable memory is lo).25 F 2.789 -.65(w, M)
+-.25 H(AXP).65 E -.4(AG)-.92 G(ES).4 E .689(may be reduced to 4 with th\
+e understanding that this will greatly limit the maximum re)108 256.8 R
+(gion)-.15 E F1(SPLA)3.19 E(T!)-.95 E F0(will)3.19 E .79
+(be able to analyze.)108 268.8 R .79(If 118 me)5.79 F -.05(ga)-.15 G .79
+(bytes or more of total memory \(sw).05 F .79(ap space plus RAM\) is a)
+-.1 F -.25(va)-.2 G .79(ilable, then).25 F(MAXP)108 280.8 Q -.4(AG)-.92
+G 1.795(ES may be increased to 16.).4 F 1.795
+(This will permit operation o)6.795 F -.15(ve)-.15 G 4.296(ra4).15 G
+(-de)-4.296 E 1.796(gree by 4-de)-.15 F 1.796(gree re)-.15 F(gion,)-.15
+E 1.086(which is suf)108 292.8 R 1.086
+(\214cient for single antenna heights in e)-.25 F 1.085
+(xcess of 10,000 feet abo)-.15 F 1.385 -.15(ve m)-.15 H 1.085
+(ean sea le).15 F -.15(ve)-.25 G 1.085(l, or point-to-).15 F
+(point distances of o)108 304.8 Q -.15(ve)-.15 G 2.5(r1).15 G
+(000 miles.)-2.5 E F3(ADDITION)72 321.6 Q(AL INFORMA)-.219 E(TION)-1.04
+E F0 .332(The latest ne)108 333.6 R .332(ws and information re)-.25 F
+-.05(ga)-.15 G(rding).05 E F1(SPLA)2.832 E(T!)-.95 E F0(softw)2.832 E
+.332(are is a)-.1 F -.25(va)-.2 G .332(ilable through the of).25 F
+(\214cial)-.25 E F1(SPLA)2.833 E(T!)-.95 E F0(soft-)2.833 E -.1(wa)108
+345.6 S(re web page located at:).1 E F2(http://www)2.5 E
+(.qsl.net/kd2bd/splat.html)-.74 E F0(.)A F3 -.548(AU)72 362.4 S(THORS)
+.548 E F0(John A. Magliacane, KD2BD <)108 374.4 Q F2(kd2bd@amsat.or)A(g)
+-.37 E F0(>)A(Creator)144 386.4 Q 2.5(,L)-.4 G(ead De)-2.5 E -.15(ve)
+-.25 G(loper).15 E(Doug McDonald <)108 403.2 Q F2(mcdonald@scs.uiuc.edu)
+A F0(>)A(Original Longle)144 415.2 Q(y-Rice Model inte)-.15 E(gration)
+-.15 E(Ron Bentle)108 432 Q 2.5(y<)-.15 G F2 -.45(ro)-2.5 G(nbentle).45
+E(y@earthlink.net)-.3 E F0(>)A
+(Fresnel Zone plotting and clearance determination)144 444 Q
+(KD2BD Softw)72 768 Q 120.785(are 16)-.1 F(September 2007)2.5 E(17)
+185.115 E EP
+%%Trailer
+end
+%%EOF
--- /dev/null
+SPLAT!(1) KD2BD Software SPLAT!(1)
+
+
+
+NAME
+ splat - An RF Signal Propagation, Loss, And Terrain analy-
+ sis tool
+
+SYNOPSIS
+ splat [-t transmitter_site.qth] [-r receiver_site.qth]
+ [-c rx antenna height for LOS coverage analysis
+ (feet/meters) (float)] [-L rx antenna height for Longley-
+ Rice coverage analysis (feet/meters) (float)] [-p ter-
+ rain_profile.ext] [-e elevation_profile.ext] [-h
+ height_profile.ext] [-H normalized_height_profile.ext] [-l
+ Longley-Rice_profile.ext] [-o topographic_map_file-
+ name.ppm] [-b cartographic_boundary_filename.dat] [-s
+ site/city_database.dat] [-d sdf_directory_path] [-m earth
+ radius multiplier (float)] [-f frequency (MHz) for Fresnel
+ zone calculations (float)] [-R maximum coverage radius
+ (miles/kilometers) (float)] [-dB maximum attenuation con-
+ tour to display on path loss maps (80-230 dB)] [-fz Fres-
+ nel zone clearance percentage (default = 60)] [-plo
+ path_loss_output_file.txt] [-pli path_loss_input_file.txt]
+ [-udt user_defined_terrain_file.dat] [-n] [-N] [-nf]
+ [-ngs] [-geo] [-kml] [-metric]
+
+DESCRIPTION
+ SPLAT! is a powerful terrestrial RF propagation and ter-
+ rain analysis tool for the spectrum between 20 MHz and 20
+ GHz. SPLAT! is free software, and is designed for opera-
+ tion on Unix and Linux-based workstations. Redistribution
+ and/or modification is permitted under the terms of the
+ GNU General Public License, Version 2, as published by the
+ Free Software Foundation. Adoption of SPLAT! source code
+ in proprietary or closed-source applications is a viola-
+ tion of this license and is strictly forbidden.
+
+ SPLAT! 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.
+
+INTRODUCTION
+ Applications of SPLAT! 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
+ interference studies, and the prediction of analog and
+ digital terrestrial radio and television contour regions.
+
+ SPLAT! 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, distances, and elevations to
+ known obstructions, Longley-Rice path attenuation, and
+ received signal strength. In addition, the minimum
+ antenna height requirements needed to clear terrain, the
+ first Fresnel zone, and any user-definable percentage of
+ the first Fresnel zone are also provided.
+
+ SPLAT! produces reports, graphs, and high resolution topo-
+ graphic maps that depict line-of-sight paths, and regional
+ path loss and signal strength contours through which
+ expected coverage areas of transmitters and repeater sys-
+ tems can be obtained. When performing line-of-sight and
+ Longley-Rice analyses in situations where multiple trans-
+ mitter or repeater sites are employed, SPLAT! determines
+ individual and mutual areas of coverage within the network
+ specified.
+
+ Simply typing splat on the command line will return a sum-
+ mary of SPLAT!'s command line options:
+
+
+ --==[ SPLAT! v1.2.1 Available Options...
+ ]==--
+
+ -t txsite(s).qth (max of 4 with -c, max of 30 with
+ -L)
+ -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 (5 max)
+ -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)
+ -m earth radius multiplier
+ -n do not plot LOS paths in .ppm maps
+ -N do not produce unnecessary site or obstruction
+ reports
+ -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
+ -fz Fresnel zone clearance percentage (default = 60)
+ -ngs display greyscale topography as white in .ppm
+ files
+ -erp override ERP in .lrp file (Watts)
+ -pli filename of path-loss input file
+ -plo filename of path-loss output file
+ -udt filename of user defined terrain input file
+ -kml generate Google Earth (.kml) compatible output
+ -geo generate an Xastir .geo georeference file (with
+ .ppm output) -metric employ metric rather than imperial
+ units for all user I/O
+
+
+INPUT FILES
+ SPLAT! 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 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, antenna
+ radiation pattern files, and color definition files.
+
+SPLAT DATA FILES
+ SPLAT! imports topographic data in the form of SPLAT Data
+ Files (SDFs). These files may be generated from a number
+ of information sources. In the United States, SPLAT Data
+ Files can be generated through U.S. Geological Survey
+ Digital Elevation Models (DEMs) using the usgs2sdf utility
+ included with SPLAT!. USGS Digital Elevation Models com-
+ patible with this utility may be downloaded from:
+ http://edcftp.cr.usgs.gov/pub/data/DEM/250/.
+
+ 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
+ srtm2sdf utility. SRTM-3 Version 2 data may be obtained
+ through anonymous FTP from:
+ ftp://e0srp01u.ecs.nasa.gov:21/srtm/version2/
+
+ The strm2sdf utility may also be used to convert 3-arc
+ second SRTM data in Band Interleaved by Line (.BIL) format
+ for use with SPLAT!. This data is available via the web
+ at: http://seamless.usgs.gov/website/seamless/
+
+ Band Interleaved by Line data must be downloaded in a very
+ specific manner to be compatible with srtm2sdf and SPLAT!.
+ Please consult srtm2sdf's documentation for instructions
+ on downloading .BIL topographic data through the USGS's
+ Seamless Web Site.
+
+ Despite the higher accuracy that SRTM data has to offer,
+ some voids in the data sets exist. When voids are
+ detected, the srtm2sdf utility replaces them with corre-
+ sponding data found in existing SDF files (that were pre-
+ sumably created from earlier USGS data through the
+ usgs2sdf utility). If USGS-derived SDF data is not avail-
+ able, voids are handled through adjacent pixel averaging,
+ or direct replacement.
+
+ 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 (.sdf) as generated by the usgs2sdf and
+ srtm2sdf utilities, or in bzip2 compressed format
+ (.sdf.bz2). Since uncompressed files can be read slightly
+ faster than files that have been compressed, SPLAT!
+ searches for needed SDF data in uncompressed format first.
+ If uncompressed data cannot be located, SPLAT! then
+ searches for data in bzip2 compressed format. If no com-
+ pressed SDF files can be found for the region requested,
+ SPLAT! assumes the region is over water, and will assign
+ an elevation of sea-level to these areas.
+
+ This feature of SPLAT! 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 SPLAT! underscores the impor-
+ tance of having all the SDF files required for the region
+ being analyzed if meaningful results are to be expected.
+
+SITE LOCATION (QTH) FILES
+ SPLAT! imports site location information of transmitter
+ and receiver sites analyzed by the program from ASCII
+ files having a .qth 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, or degrees East 0 to -360
+ degrees), and the site's antenna height above ground level
+ (AGL), each separated by a single line-feed character.
+ The antenna height is assumed to be specified in feet
+ unless followed by the letter m or the word meters in
+ either upper or lower case. Latitude and longitude infor-
+ mation may be expressed in either decimal format (74.6864)
+ or degree, minute, second (DMS) format (74 41 11.0).
+
+ For example, a site location file describing television
+ station WNJT-DT, Trenton, NJ (wnjt-dt.qth) might read as
+ follows:
+
+ WNJT-DT
+ 40.2828
+ 74.6864
+ 990.00
+
+ Each transmitter and receiver site analyzed by SPLAT! must
+ be represented by its own site location (QTH) file.
+
+LONGLEY-RICE PARAMETER (LRP) FILES
+ Longley-Rice parameter data files are required for SPLAT!
+ 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 (wnjt-dt.lrp):
+
+ 15.000 ; Earth Dielectric Constant (Relative per-
+ mittivity)
+ 0.005 ; Earth Conductivity (Siemens per meter)
+ 301.000 ; Atmospheric Bending Constant (N-units)
+ 647.000 ; Frequency in MHz (20 MHz to 20 GHz)
+ 5 ; Radio Climate (5 = Continental Temper-
+ ate)
+ 0 ; Polarization (0 = Horizontal, 1 = Verti-
+ cal)
+ 0.50 ; Fraction of situations (50% of loca-
+ tions)
+ 0.90 ; Fraction of time (90% of the time)
+ 46000.0 ; ERP in Watts (optional)
+
+ If an LRP file corresponding to the tx_site QTH file can-
+ not be found, SPLAT! scans the current working directory
+ for the file "splat.lrp". If this file cannot be found,
+ then default parameters will be assigned by SPLAT! and a
+ corresponding "splat.lrp" file containing these default
+ parameters will be written to the current working direc-
+ tory. The generated "splat.lrp" file can then be edited
+ by the user as needed.
+
+ Typical Earth dielectric constants and conductivity values
+ are as follows:
+
+ Dielectric Constant Conductiv-
+ ity
+ Salt water : 80 5.000
+ Good ground : 25 0.020
+ Fresh water : 80 0.010
+ Marshy land : 12 0.007
+ Farmland, forest : 15 0.005
+ Average ground : 15 0.005
+ Mountain, sand : 13 0.002
+ City : 5 0.001
+ Poor ground : 4 0.001
+
+ Radio climate codes used by SPLAT! are as follows:
+
+ 1: Equatorial (Congo)
+ 2: Continental Subtropical (Sudan)
+ 3: Maritime Subtropical (West coast of Africa)
+ 4: Desert (Sahara)
+ 5: Continental Temperate
+ 6: Maritime Temperate, over land (UK and west
+ coasts of US & EU)
+ 7: Maritime Temperate, over sea
+
+ The Continental Temperate climate is common to large land
+ masses in the temperate zone, such as the United States.
+ For paths shorter than 100 km, there is little difference
+ between Continental and Maritime Temperate climates.
+
+ The seventh and eighth parameters in the .lrp file corre-
+ spond to the statistical analysis provided by the Longley-
+ Rice model. In this example, SPLAT! will return the maxi-
+ mum path loss occurring 50% of the time (fraction of time)
+ in 90% of situations (fraction of situations). This is
+ often denoted as F(50,90) in Longley-Rice studies. In the
+ United States, an F(50,90) criteria is typically used for
+ digital television (8-level VSB modulation), while
+ F(50,50) is used for analog (VSB-AM+NTSC) broadcasts.
+
+ For further information on these parameters, see:
+ http://flattop.its.bldrdoc.gov/itm.html and
+ http://www.softwright.com/faq/engineering/prop_long-
+ ley_rice.html
+
+ The final parameter in the .lrp file corresponds to the
+ transmitter's effective radiated power, and is optional.
+ If it is included in the levels and field strength level
+ contours when performing Longley-Rice studies. If the
+ parameter is omitted, path loss is computed instead. The
+ ERP provided in the .lrp file can be overridden by using
+ SPLAT!'s -erp command-line switch. If the .lrp file con-
+ tains an ERP parameter and the generation of path-loss
+ rather than signal strength contours is desired, the ERP
+ can be assigned to zero using the -erp switch without hav-
+ ing to edit the .lrp file to accomplish the same result.
+
+CITY LOCATION FILES
+ The names and locations of cities, tower sites, or other
+ points of interest may be imported and plotted on topo-
+ graphic maps generated by SPLAT!. SPLAT! imports the
+ names of cities and locations from ASCII files containing
+ 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 .qth files, latitude and longitude information
+ may be entered in either decimal or degree, minute, second
+ (DMS) format.
+
+ For example (cities.dat):
+
+ Teaneck, 40.891973, 74.014506
+ Tenafly, 40.919212, 73.955892
+ Teterboro, 40.859511, 74.058908
+ Tinton Falls, 40.279966, 74.093924
+ Toms River, 39.977777, 74.183580
+ Totowa, 40.906160, 74.223310
+ Trenton, 40.219922, 74.754665
+
+ A total of five separate city data files may be imported
+ at a time, and there is no limit to the size of these
+ files. SPLAT! 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 read
+ earlier in the current city data file, or in previous
+ files. This behavior minimizes clutter in SPLAT! 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
+ available from the U.S. Census Bureau using the cityde-
+ coder utility included with SPLAT!. Such data is avail-
+ able free of charge via the Internet at: http://www.cen-
+ sus.gov/geo/www/cob/bdy_files.html, and must be in ASCII
+ format.
+
+CARTOGRAPHIC BOUNDARY DATA FILES
+ Cartographic boundary data may also be imported to plot
+ the boundaries of cities, counties, or states on topo-
+ graphic maps generated by SPLAT!. 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: http://www.cen-
+ sus.gov/geo/www/cob/co2000.html#ascii and http://www.cen-
+ sus.gov/geo/www/cob/pl2000.html#ascii. 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.
+
+PROGRAM OPERATION
+ SPLAT! is invoked via the command-line using a series of
+ switches and arguments. Since SPLAT! is a CPU and memory
+ intensive application, this type of interface minimizes
+ overhead and lends itself well to scripted (batch) opera-
+ tions. SPLAT!'s CPU and memory scheduling priority may be
+ modified through the use of the Unix nice command.
+
+ The number and type of switches passed to SPLAT! determine
+ its mode of operation and method of output data genera-
+ tion. Nearly all of SPLAT!'s switches may be cascaded in
+ any order on the command line when invoking the program.
+
+ SPLAT! operates in two distinct modes: point-to-point
+ mode, and area prediction mode. 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.
+
+POINT-TO-POINT ANALYSIS
+ SPLAT! 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 line-of-sight terrain analysis between the
+ transmitter specified in tx_site.qth and receiver speci-
+ fied in rx_site.qth using a True Earth radius model, and
+ writes a SPLAT! Path Analysis Report to the current work-
+ ing directory. The report contains details of the trans-
+ mitter 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, SPLAT! 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 -metric switch is added to SPLAT!'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 minimum 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.
+
+ qth extensions are assumed by SPLAT! for QTH files, and
+ are optional when specifying -t and -r arguments on the
+ command-line. SPLAT! automatically reads all SPLAT Data
+ Files necessary to conduct the terrain analysis between
+ the sites specified. SPLAT! searches for the required
+ SDF files in the current working directory first. If the
+ needed files are not found, SPLAT! then searches in the
+ path specified by the -d 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 of last resort
+ to all the SDF files. The path in the $HOME/.splat_path
+ 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
+ receiver can be generated by adding the -p switch:
+
+ splat -t tx_site -r rx_site -p terrain_profile.png
+
+ SPLAT! invokes gnuplot when generating graphs. The file-
+ name extension specified to SPLAT! determines the format
+ of the graph produced. .png will produce a 640x480 color
+ PNG graphic file, while .ps or .postscript will produce
+ postscript output. Output in formats such as GIF, Adobe
+ Illustrator, AutoCAD dxf, LaTeX, and many others are
+ available. Please consult gnuplot, and gnuplot'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
+ the receiver can be generated by using the -e switch:
+
+ 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
+ from the perspective of the receiver's location. A second
+ 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
+ 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
+ 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
+ generated using the -h switch:
+
+ 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 -H
+ 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 first Fresnel Zone, and 60% of the first Fresnel Zone
+ can be added to height profile graphs by adding the -f
+ 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
+
+ Fresnel Zone clearances other 60% can be specified using
+ the -fz switch as follows:
+
+ splat -t tx_site -r rx_site -f 439.250 -fz 75 -H
+ height_profile2.png
+
+ A graph showing Longley-Rice path loss may be plotted
+ using the -l switch:
+
+ splat -t tx_site -r rx_site -l path_loss_profile.png
+
+ As before, adding the -metric switch forces the graphs to
+ be plotted using metric units of measure.
+
+ When performing a point-to-point analysis, a SPLAT! Path
+ Analysis Report is generated in the form of a text file
+ with a .txt filename extension. The report contains bear-
+ ings and distances between the transmitter and receiver,
+ as well as the free-space and Longley-Rice path loss for
+ the path being analyzed. The mode of propagation for the
+ path is given as Line-of-Sight, Single Horizon, Double
+ Horizon, Diffraction Dominant, or Troposcatter Dominant.
+
+ Distances and locations to known obstructions along the
+ path between transmitter and receiver are also provided.
+ If the transmitter's effective radiated power is specified
+ in the transmitter's corresponding .lrp file, then pre-
+ dicted signal strength and antenna voltage at the receiv-
+ ing location is also provided in the Path Analysis Report.
+
+ To determine the signal-to-noise (SNR) ratio at remote
+ location where random Johnson (thermal) noise is the pri-
+ mary limiting factor in reception:
+
+ SNR=T-NJ-L+G-NF
+
+ where T is the ERP of the transmitter in dBW in the direc-
+ tion of the receiver, NJ is Johnson Noise in dBW (-136 dBW
+ for a 6 MHz television channel), L is the path loss pro-
+ vided by SPLAT! in dB (as a positive number), G is the
+ receive antenna gain in dB over isotropic, and NF is the
+ receiver noise figure in dB.
+
+ T may be computed as follows:
+
+ T=TI+GT
+
+ where TI is actual amount of RF power delivered to the
+ transmitting antenna in dBW, GT is the transmitting
+ antenna gain (over isotropic) in the direction of the
+ receiver (or the horizon if the receiver is over the hori-
+ zon).
+
+ To compute how much more signal is available over the min-
+ imum to necessary to achieve a specific signal-to-noise
+ ratio:
+
+ Signal_Margin=SNR-S
+
+ where S is the minimum required SNR ratio (15.5 dB for
+ ATSC (8-level VSB) DTV, 42 dB for analog NTSC television).
+
+ A topographic map may be generated by SPLAT! to visualize
+ the path between the transmitter and receiver sites from
+ yet another perspective. Topographic maps generated by
+ SPLAT! display elevations using a logarithmic grayscale,
+ with higher elevations represented through brighter shades
+ of gray. The dynamic range of the image is scaled between
+ the highest and lowest elevations present in the map. The
+ only exception to this is sea-level, which is represented
+ using the color blue.
+
+ Topographic output is invoked using the -o switch:
+
+ splat -t tx_site -r rx_site -o topo_map.ppm
+
+ The .ppm extension on the output filename is assumed by
+ SPLAT!, and is optional.
+
+ In this example, topo_map.ppm will illustrate the loca-
+ tions of the transmitter and receiver sites specified. In
+ addition, the great circle path between the two sites will
+ be drawn over locations for which an unobstructed path
+ exists to the transmitter at a receiving antenna height
+ equal to that of the receiver site (specified in
+ rx_site.qth).
+
+ It may desirable to populate the topographic map with
+ names and locations of cities, tower sites, or other
+ important locations. A city file may be passed to SPLAT!
+ using the -s switch:
+
+ splat -t tx_site -r rx_site -s cities.dat -o topo_map
+
+ Up to five separate city files may be passed to SPLAT! at
+ a time following the -s switch.
+
+ County and state boundaries may be added to the map by
+ specifying up to five U.S. Census Bureau cartographic
+ boundary files using the -b switch:
+
+ splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map
+
+ In situations where multiple transmitter sites are in use,
+ as many as four site locations may be passed to SPLAT! at
+ a time for analysis:
+
+ splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p
+ profile.png
+
+ In this example, four separate terrain profiles and
+ obstruction reports will be generated by SPLAT!. A single
+ topographic map can be specified using the -o switch, and
+ line-of-sight paths between each transmitter and the
+ receiver site indicated will be produced on the map, each
+ in its own color. The path between the first transmitter
+ specified to the receiver will be in green, the path
+ between the second transmitter and the receiver will be in
+ cyan, the path between the third transmitter and the
+ receiver will be in violet, and the path between the
+ fourth transmitter and the receiver will be in sienna.
+
+ SPLAT! 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 xv, The GIMP, ImageMagick,
+ and XPaint. PNG format is highly recommended for lossless
+ compressed storage of SPLAT! generated topographic output
+ files. ImageMagick's command-line utility easily converts
+ SPLAT!'s PPM files to PNG format:
+
+ convert splat_map.ppm splat_map.png
+
+ Another excellent PPM to PNG command-line utility is
+ available at:
+ http://www.libpng.org/pub/png/book/sources.html. As a
+ last resort, PPM files may be compressed using the bzip2
+ utility, and read directly by The GIMP in this format.
+
+ The -ngs option assigns all terrain to the color white,
+ and can be used when it is desirable to generate a map
+ that is devoid of terrain:
+
+ splat -t tx_site -r rx_site -b co34_d00.dat -ngs -o
+ white_map
+
+ The resulting .ppm image file can be converted to .png
+ format with a transparent background using ImageMagick's
+ convert utility:
+
+ convert -transparent "#FFFFFF" white_map.ppm transpar-
+ ent_map.png
+
+REGIONAL COVERAGE ANALYSIS
+ SPLAT! can analyze a transmitter or repeater site, or net-
+ work of sites, and predict the regional coverage for each
+ site specified. In this mode, SPLAT! 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
+ with the site in question. A regional analysis may be
+ performed by SPLAT! using the -c switch as follows:
+
+ splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o
+ tx_coverage
+
+ In this example, SPLAT! generates a topographic map called
+ tx_coverage.ppm that illustrates the predicted line-of-
+ sight regional coverage of tx_site to receiving locations
+ having antennas 30.0 feet above ground level (AGL). If
+ the -metric switch is used, the argument following the -c
+ switch is interpreted as being in meters rather than in
+ feet. The contents of cities.dat are plotted on the map,
+ as are the cartographic boundaries contained in the file
+ co34_d00.dat.
+
+ When plotting line-of-sight paths and areas of regional
+ coverage, SPLAT! by default does not account for the
+ effects of atmospheric bending. However, this behavior
+ may be modified by using the Earth radius multiplier (-m)
+ switch:
+
+ splat -t wnjt-dt -c 30.0 -m 1.333 -s cities.dat -b coun-
+ ties.dat -o map.ppm
+
+ An earth radius multiplier of 1.333 instructs SPLAT! to
+ use the "four-thirds earth" model for line-of-sight propa-
+ gation analysis. Any appropriate earth radius multiplier
+ may be selected by the user.
+
+ When performing a regional analysis, SPLAT! generates a
+ site report for each station analyzed. SPLAT! 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
+ toward the bearings of 0, 45, 90, 135, 180, 225, 270, and
+ 315 degrees azimuth.
+
+DETERMINING MULTIPLE REGIONS OF LOS COVERAGE
+ SPLAT! 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 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 10.0
+ meters above ground level. A topographic map is then
+ written to the file network.ppm. The line-of-sight cover-
+ age area of the transmitters are plotted as follows in the
+ colors indicated (along with their corresponding RGB val-
+ ues in decimal):
+
+ site1: Green (0,255,0)
+ site2: Cyan (0,255,255)
+ site3: Medium Violet (147,112,219)
+ site4: Sienna 1 (255,130,71)
+
+ site1 + site2: Yellow (255,255,0)
+ site1 + site3: Pink (255,192,203)
+ site1 + site4: Green Yellow (173,255,47)
+ site2 + site3: Orange (255,165,0)
+ site2 + site4: Dark Sea Green 1 (193,255,193)
+ site3 + site4: Dark Turquoise (0,206,209)
+
+ site1 + site2 + site3: Dark Green (0,100,0)
+ site1 + site2 + site4: Blanched Almond (255,235,205)
+ site1 + site3 + site4: Medium Spring Green (0,250,154)
+ site2 + site3 + site4: Tan (210,180,140)
+
+ site1 + site2 + site3 + site4: Gold2 (238,201,0)
+
+ If separate .qth files are generated, each representing a
+ common site location but a different antenna height, a
+ single topographic map illustrating the regional coverage
+ from as many as four separate locations on a single tower
+ may be generated by SPLAT!.
+
+LONGLEY-RICE PATH LOSS ANALYSIS
+ If the -c switch is replaced by a -L 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, SPLAT! generates a multi-color map illus-
+ trating expected signal levels in areas surrounding the
+ transmitter site. A legend at the bottom of the map cor-
+ relates each color with a specific path loss range in
+ decibels or signal strength in decibels over one microvolt
+ per meter (dBuV/m).
+
+ The Longley-Rice analysis range may be modified to a user-
+ specific value using the -R switch. The argument must be
+ given in miles (or kilometers if the -metric switch is
+ used). If a range wider than the generated topographic
+ map is specified, SPLAT! will perform Longley-Rice path
+ loss calculations between all four corners of the area
+ prediction map.
+
+ The -db 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, SPLAT!'s path
+ loss plot can be constrained to the region bounded by the
+ 140 dB attenuation contour as follows:
+
+ splat -t wnjt-dt -L 30.0 -s cities.dat -b co34_d00.dat -db
+ 140 -o plot.ppm
+
+
+SIGNAL CONTOUR COLOR DEFINITION PARAMETERS
+ The colors used to illustrate signal strength and path
+ loss contours in SPLAT! generated coverage maps may be
+ tailored by the user by creating or modifying SPLAT!'s
+ color definition files. SPLAT! color definition files
+ have the same base name as the transmitter's .qth file,
+ but carry .lcf and .scf extensions.
+
+ When a regional Longley-Rice analysis is performed and the
+ transmitter's ERP is not specified or is zero, a .lcf path
+ loss color definition file corresponding to the transmit-
+ ter site (.qth) is read by SPLAT! from the current working
+ directory. If a .lcf file corresponding to the transmit-
+ ter site is not found, then a default file suitable for
+ manual editing by the user is automatically generated by
+ SPLAT!. If the transmitter's ERP is specified, then a
+ signal strength map is generated and a signal strength
+ color definition file (.scf) is read, or generated if one
+ is not available in the current working directory.
+
+ A path-loss color definition file possesses the following
+ structure (wnjt-dt.lcf):
+
+ ; SPLAT! Auto-generated Path-Loss Color Definition
+ ("wnjt-dt.lcf") File
+ ;
+ ; Format for the parameters held in this file is as fol-
+ lows:
+ ;
+ ; dB: red, green, blue
+ ;
+ ; ...where "dB" is the path loss (in dB) and
+ ; "red", "green", and "blue" are the corresponding RGB
+ color
+ ; definitions ranging from 0 to 255 for the region speci-
+ fied.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour
+ regions
+ ; may be defined in this file.
+ ;
+ ;
+ 80: 255, 0, 0
+ 90: 255, 128, 0
+ 100: 255, 165, 0
+ 110: 255, 206, 0
+ 120: 255, 255, 0
+ 130: 184, 255, 0
+ 140: 0, 255, 0
+ 150: 0, 208, 0
+ 160: 0, 196, 196
+ 170: 0, 148, 255
+ 180: 80, 80, 255
+ 190: 0, 38, 255
+ 200: 142, 63, 255
+ 210: 196, 54, 255
+ 220: 255, 0, 255
+ 230: 255, 194, 204
+
+
+ If the path loss is less than 80 dB, the color Red (RGB =
+ 255, 0, 0) is assigned to the region. If the path-loss is
+ greater than or equal to 80 dB, but less than 90 db, then
+ Dark Orange (255, 128, 0) is assigned to the region.
+ Orange (255, 165, 0) is assigned to regions having a path
+ loss greater than or equal to 90 dB, but less than 100 dB,
+ and so on. Greyscale terrain is displayed beyond the 230
+ dB path loss contour.
+
+ SPLAT! signal strength color definition files share a very
+ similar structure (wnjt-dt.scf):
+
+ ; SPLAT! Auto-generated Signal Color Definition ("wnjt-
+ dt.scf") File
+ ;
+ ; Format for the parameters held in this file is as fol-
+ lows:
+ ;
+ ; dBuV/m: red, green, blue
+ ;
+ ; ...where "dBuV/m" is the signal strength (in dBuV/m)
+ and
+ ; "red", "green", and "blue" are the corresponding RGB
+ color
+ ; definitions ranging from 0 to 255 for the region speci-
+ fied.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour
+ regions
+ ; may be defined in this file.
+ ;
+ ;
+ 128: 255, 0, 0
+ 118: 255, 165, 0
+ 108: 255, 206, 0
+ 98: 255, 255, 0
+ 88: 184, 255, 0
+ 78: 0, 255, 0
+ 68: 0, 208, 0
+ 58: 0, 196, 196
+ 48: 0, 148, 255
+ 38: 80, 80, 255
+ 28: 0, 38, 255
+ 18: 142, 63, 255
+ 8: 140, 0, 128
+
+
+ If the signal strength is greater than or equal to 128 db
+ over 1 microvolt per meter (dBuV/m), the color Red (255,
+ 0, 0) is displayed for the region. If the signal strength
+ is greater than or equal to 118 dbuV/m, but less than 128
+ dbuV/m, then the color Orange (255, 165, 0) is displayed,
+ and so on. Greyscale terrain is displayed for regions
+ with signal strengths less than 8 dBuV/m.
+
+ Signal strength contours for some common VHF and UHF
+ broadcasting services in the United States are as follows:
+
+ Analog Television Broadcasting
+ ------------------------------
+ Channels 2-6: City Grade: >= 74 dBuV/m
+ Grade A: >= 68 dBuV/m
+ Grade B: >= 47 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 77 dBuV/m
+ Grade A: >= 71 dBuV/m
+ Grade B: >= 56 dBuV/m
+ --------------------------------------------
+ Channels 14-69: Indoor Grade: >= 94 dBuV/m
+ City Grade: >= 80 dBuV/m
+ Grade A: >= 74 dBuV/m
+ Grade B: >= 64 dBuV/m
+
+ Digital Television Broadcasting
+ -------------------------------
+ Channels 2-6: City Grade: >= 35 dBuV/m
+ Service Threshold: >= 28 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 43 dBuV/m
+ Service Threshold: >= 36 dBuV/m
+ --------------------------------------------
+ Channels 14-69: City Grade: >= 48 dBuV/m
+ Service Threshold: >= 41 dBuV/m
+
+ NOAA Weather Radio (162.400 - 162.550 MHz)
+ ------------------------------------------
+ Reliable: >= 18 dBuV/m
+ Not reliable: < 18 dBuV/m
+ Unlikely to receive: < 0 dBuV/m
+
+ FM Radio Broadcasting (88.1 - 107.9 MHz)
+ ----------------------------------------
+ Analog Service Contour: 60 dBuV/m
+ Digital Service Contour: 65 dBuV/m
+
+
+
+ANTENNA RADIATION PATTERN PARAMETERS
+ Normalized field voltage patterns for a transmitting
+ antenna's horizontal and vertical planes are imported
+ automatically into SPLAT! 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 .az and .el extensions for
+ azimuth and elevation pattern files, respectively. Speci-
+ fications regarding pattern rotation (if any) and mechani-
+ cal beam tilt and tilt direction (if any) are also con-
+ tained within SPLAT! antenna pattern files.
+
+ For example, the first few lines of a SPLAT! azimuth pat-
+ tern file might appear as follows (kvea.az):
+
+ 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 .az file specifies the amount of
+ azimuthal pattern rotation (measured clockwise in degrees
+ from True North) to be applied by SPLAT! to the data con-
+ tained in the .az 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 SPLAT! elevation pattern files is
+ slightly different. The first line of the .el file speci-
+ fies the amount of mechanical beam tilt applied to the
+ antenna. Note that a downward tilt (below the horizon) is
+ expressed as a positive angle, while an upward tilt (above
+ the horizon) is expressed as a negative angle. 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,
+ negative elevation angles are used to represent elevations
+ above the horizon, while positive angles represents eleva-
+ tions below the horizon.
+
+ For example, the first few lines a SPLAT! elevation pat-
+ tern file might appear as follows (kvea.el):
+
+ 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, SPLAT! will
+ interpolate the values provided to determine the data at
+ the required resolution, although this may result in a
+ loss in accuracy.
+
+
+IMPORTING AND EXPORTING REGIONAL PATH LOSS CONTOUR DATA
+ 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 SPLAT! to rapidly produce a
+ revised path loss map.
+
+ For example, a path loss output file can be generated by
+ SPLAT! 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
+
+ SPLAT! 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 SPLAT! path loss output file take on the fol-
+ lowing appearance (pathloss.dat):
+
+ 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 SPLAT! 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 vim 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 -L switch if 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
+ SPLAT!. 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 SPLAT! path loss files to reflect antenna
+ pattern data, only the last column (path loss) 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 SPLAT!
+ for generating revised coverage maps:
+
+ splat -t kvea -pli pathloss.dat -s city.dat -b county.dat
+ -o map.ppm
+
+ SPLAT! path loss files can also be used for conducting
+ coverage or interference studies outside of SPLAT!.
+
+USER-DEFINED TERRAIN INPUT FILES
+ 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 SPLAT! analysis being conducted, but
+ noticeably absent from the SDF files being used. A user-
+ defined terrain file is imported into a SPLAT! analysis
+ using the -udt 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 meters, and
+ is added on top of 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 SPLAT!.
+
+SIMPLE TOPOGRAPHIC MAP GENERATION
+ 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
+ between the sites, the -n switch should be invoked as fol-
+ lows:
+
+ splat -t tx_site -r rx_site -n -o topo_map.ppm
+
+ If no text report is desired, then the -N switch is used:
+
+ splat -t tx_site -r rx_site -N -o topo_map.ppm
+
+ 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 -metric switch is used). Note that
+ the tx_site name and location are not displayed in this
+ example. If display of this information is desired, sim-
+ ply create a SPLAT! city file (-s option) and append it to
+ the list of command-line options illustrated above.
+
+ If the -o switch and output filename are omitted in these
+ operations, topographic output is written to a file named
+ tx_site.ppm in the current working directory by default.
+
+GEOREFERENCE FILE GENERATION
+ Topographic, coverage (-c), and path loss contour (-L)
+ maps generated by SPLAT! may be imported into Xastir (X
+ Amateur Station Tracking and Information Reporting) soft-
+ ware by generating a georeference file using SPLAT!'s -geo
+ 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 -o file specified, but have a .geo extension,
+ and permit proper interpretation and display of SPLAT!'s
+ .ppm graphics in Xastir software.
+
+GOOGLE MAP KML FILE GENERATION
+ Keyhole Markup Language files compatible with Google Earth
+ may be generated by SPLAT! when performing point-to-point
+ or regional coverage analyses by invoking the -kml switch:
+
+ splat -t wnjt-dt -r kd2bd -kml
+
+ The KML file generated will have the same filename struc-
+ ture as a Path Analysis Report for the transmitter and
+ receiver site names given, except it will carry a .kml
+ extension.
+
+ Once loaded into Google Earth (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. Google Earth's navigation tools allow
+ the user to "fly" around the path, identify landmarks,
+ roads, and other featured content.
+
+ When performing regional coverage analysis, the .kml file
+ generated by SPLAT! will permit path loss or signal
+ strength contours to be layered on top of Google Earth's
+ display in a semi-transparent manner. The generated .kml
+ file will have the same basename as that of the .ppm file
+ normally generated.
+
+DETERMINATION OF ANTENNA HEIGHT ABOVE AVERAGE TERRAIN
+ SPLAT! determines antenna height above average terrain
+ (HAAT) according to the procedure defined by Federal Com-
+ munications Commission Part 73.313(d). According to this
+ definition, terrain elevations along eight radials between
+ 2 and 10 miles (3 and 16 kilometers) from the site being
+ analyzed are sampled and averaged for each 45 degrees of
+ azimuth starting with True North. If one or more radials
+ 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.
+
+ 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 SPLAT! are
+ SRTM-derived.
+
+ When performing point-to-point terrain analysis, SPLAT!
+ 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
+ data in memory.
+
+ When performing area prediction analysis, enough topogra-
+ phy data is normally loaded by SPLAT! to perform average
+ terrain calculations. Under such conditions, SPLAT! 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, SPLAT!
+ reports No Terrain for the radial paths affected.
+
+RESTRICTING THE MAXIMUM SIZE OF AN ANALYSIS REGION
+ SPLAT! reads SDF files as needed into a series of memory
+ "pages" within the structure of the program. Each "page"
+ holds one SDF file representing a one degree by one degree
+ region of terrain. A #define MAXPAGES statement in the
+ first several lines of splat.cpp sets the maximum number
+ of "pages" available for holding topography data. It also
+ sets the maximum size of the topographic maps generated by
+ SPLAT!. MAXPAGES is set to 9 by default. If SPLAT! 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 SPLAT! with the
+ number of MAXPAGES specified. In situations where avail-
+ able memory is low, MAXPAGES may be reduced to 4 with the
+ understanding that this will greatly limit the maximum
+ region SPLAT! will be able to analyze. If 118 megabytes
+ or more of total memory (swap space plus RAM) is avail-
+ able, then MAXPAGES 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 dis-
+ tances of over 1000 miles.
+
+ADDITIONAL INFORMATION
+ The latest news and information regarding SPLAT! software
+ is available through the official SPLAT! software web page
+ located at: http://www.qsl.net/kd2bd/splat.html.
+
+AUTHORS
+ John A. Magliacane, KD2BD <kd2bd@amsat.org>
+ Creator, Lead Developer
+
+ Doug McDonald <mcdonald@scs.uiuc.edu>
+ Original Longley-Rice Model integration
+
+ Ron Bentley <ronbentley@earthlink.net>
+ Fresnel Zone plotting and clearance determination
+
+
+
+
+KD2BD Software 16 September 2007 SPLAT!(1)
+++ /dev/null
-#!/bin/bash
-# This script builds the man page, pdf, and postscript
-# and text documentation from the groff source "splat.man".
-echo -n "Creating postscript file... "
-groff -e -T ps -man splat.man > ../postscript/splat.ps
-echo
-echo -n "Creating man page... "
-groff -e -T ascii -man splat.man > splat.1
-echo
-echo -n "Creating text file... "
-ul -t dumb splat.1 > ../text/splat.txt
-echo
-echo -n "Creating pdf file... "
-ps2pdf ../postscript/splat.ps ../pdf/splat.pdf
-echo
-echo "Done!"
+++ /dev/null
-SPLAT!(1) KD2BD Software SPLAT!(1)
-
-
-
-N\bNA\bAM\bME\bE
- splat - An RF S\bSignal P\bPropagation, L\bLoss, A\bAnd T\bTerrain analy-
- 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 _\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. 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
- (WANs), commercial and amateur radio communication systems
- 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, 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
-
-
-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 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
- Files (SDFs). These files may be generated from a number
- of information sources. In the United States, SPLAT Data
- Files can be generated through U.S. Geological Survey
- Digital Elevation Models (DEMs) using the u\bus\bsg\bgs\bs2\b2s\bsd\bdf\bf utility
- included with S\bSP\bPL\bLA\bAT\bT!\b!. USGS Digital Elevation Models com-
- 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 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,
- or direct replacement.
-
- 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 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.
- 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
- 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), 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-
- 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-
- lows:
-
- WNJT
- 40.2833
- 74.6889
- 990.00
-
- Each transmitter and receiver site analyzed by S\bSP\bPL\bLA\bAT\bT!\b! must
- 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
- 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)
- 0.005 ; Earth Conductivity (Siemens per meter)
- 301.000 ; Atmospheric Bending Constant (N-units)
- 700.000 ; Frequency in MHz (20 MHz to 20 GHz)
- 5 ; Radio Climate (5 = Continental Temper-
- ate)
- 0 ; Polarization (0 = Horizontal, 1 = Verti-
- cal)
- 0.5 ; Fraction of situations (50% of loca-
- tions)
- 0.5 ; Fraction of time (50% of the time)
-
- If an LRP file corresponding to the tx_site QTH file can-
- not be found, S\bSP\bPL\bLA\bAT\bT!\b! scans the current working directory
- for the file "splat.lrp". If this file cannot be found,
- then the default parameters listed above will be assigned
- by S\bSP\bPL\bLA\bAT\bT!\b! and a corresponding "splat.lrp" file containing
- this data will be written to the current working direc-
- tory. "splat.lrp" can then be edited by the user as
- needed.
-
- Typical Earth dielectric constants and conductivity values
- are as follows:
-
- Dielectric Constant Conductiv-
- ity
- Salt water : 80 5.000
- Good ground : 25 0.020
- Fresh water : 80 0.010
- Marshy land : 12 0.007
- Farmland, forest : 15 0.005
- Average ground : 15 0.005
- Mountain, sand : 13 0.002
- City : 5 0.001
- Poor ground : 4 0.001
-
- Radio climate codes used by S\bSP\bPL\bLA\bAT\bT!\b! are as follows:
-
- 1: Equatorial (Congo)
- 2: Continental Subtropical (Sudan)
- 3: Maritime Subtropical (West coast of Africa)
- 4: Desert (Sahara)
- 5: Continental Temperate
- 6: Maritime Temperate, over land (UK and west
- coasts of US & EU)
- 7: Maritime Temperate, over sea
-
- The Continental Temperate climate is common to large land
- masses in the temperate zone, such as the United States.
- For paths shorter than 100 km, there is little difference
- between Continental and Maritime Temperate climates.
-
- The final two parameters in the _\b._\bl_\br_\bp file correspond to
- 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). 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
- _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bs_\bo_\bf_\bt_\bw_\br_\bi_\bg_\bh_\bt_\b._\bc_\bo_\bm_\b/_\bf_\ba_\bq_\b/_\be_\bn_\bg_\bi_\bn_\be_\be_\br_\bi_\bn_\bg_\b/_\bp_\br_\bo_\bp_\b__\bl_\bo_\bn_\bg_\b-
- _\bl_\be_\by_\b__\br_\bi_\bc_\be_\b._\bh_\bt_\bm_\bl
-
-C\bCI\bIT\bTY\bY L\bLO\bOC\bCA\bAT\bTI\bIO\bON\bN F\bFI\bIL\bLE\bES\bS
- The names and locations of cities, tower sites, or other
- 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 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):
-
- Teaneck, 40.891973, 74.014506
- Tenafly, 40.919212, 73.955892
- Teterboro, 40.859511, 74.058908
- Tinton Falls, 40.279966, 74.093924
- Toms River, 39.977777, 74.183580
- Totowa, 40.906160, 74.223310
- Trenton, 40.219922, 74.754665
-
- A total of five separate city data files may be imported
- 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 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
- available from the U.S. Census Bureau using the c\bci\bit\bty\byd\bde\be-\b-
- c\bco\bod\bde\ber\br utility included with S\bSP\bPL\bLA\bAT\bT!\b!. Such data is avail-
- able free of charge 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/_\bb_\bd_\by_\b__\bf_\bi_\bl_\be_\bs_\b._\bh_\bt_\bm_\bl, and must be in ASCII
- format.
-
-C\bCA\bAR\bRT\bTO\bOG\bGR\bRA\bAP\bPH\bHI\bIC\bC B\bBO\bOU\bUN\bND\bDA\bAR\bRY\bY D\bDA\bAT\bTA\bA F\bFI\bIL\bLE\bES\bS
- Cartographic boundary data may also be imported to plot
- the boundaries of cities, counties, or states on topo-
- 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_\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-
- 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
- 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 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 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 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
- receiver can be generated by adding the _\b-_\bp switch:
-
- 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._\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
- the receiver can be generated by using the _\b-_\be switch:
-
- 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
- from the perspective of the receiver's location. A second
- 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
- 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
- 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
- generated using the _\b-_\bh switch:
-
- 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 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.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
- 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-
- _\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-
- 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 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:
-
- _\bT=_\bT_\bI+_\bG_\bT
-
- where T\bTI\bI is actual amount of RF power delivered to the
- transmitting antenna in dBW, G\bGT\bT is the transmitting
- antenna gain (over isotropic) in the direction of the
- receiver (or the horizon if the receiver is over the hori-
- zon).
-
- To compute how much more signal is available over the min-
- imum to necessary to achieve a specific signal-to-noise
- ratio:
-
- _\bS_\bi_\bg_\bn_\ba_\bl__\bM_\ba_\br_\bg_\bi_\bn=_\bS_\bN_\bR-_\bS
-
- 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
- yet another perspective. Topographic maps generated by
- S\bSP\bPL\bLA\bAT\bT!\b! display elevations using a logarithmic grayscale,
- with higher elevations represented through brighter shades
- of gray. The dynamic range of the image is scaled between
- the highest and lowest elevations present in the map. The
- only exception to this is sea-level, which is represented
- using the color blue.
-
- Topographic output is invoked using the _\b-_\bo switch:
-
- splat -t tx_site -r rx_site -o topo_map.ppm
-
- The _\b._\bp_\bp_\bm extension on the output filename is assumed by
- S\bSP\bPL\bLA\bAT\bT!\b!, and is optional.
-
- In this example, _\bt_\bo_\bp_\bo_\b__\bm_\ba_\bp_\b._\bp_\bp_\bm will illustrate the loca-
- tions of the transmitter and receiver sites specified. In
- addition, the great circle path between the two sites will
- be drawn over locations for which an unobstructed path
- exists to the transmitter at a receiving antenna height
- equal to that of the receiver site (specified in
- _\br_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh).
-
- It may desirable to populate the topographic map with
- names and locations of cities, tower sites, or other
- important locations. A city file may be passed to S\bSP\bPL\bLA\bAT\bT!\b!
- using the _\b-_\bs switch:
-
- splat -t tx_site -r rx_site -s cities.dat -o topo_map
-
- Up to five separate city files may be passed to S\bSP\bPL\bLA\bAT\bT!\b! at
- a time following the _\b-_\bs switch.
-
- County and state boundaries may be added to the map by
- specifying up to five U.S. Census Bureau cartographic
- boundary files using the _\b-_\bb switch:
-
- splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map
-
- In situations where multiple transmitter sites are in use,
- as many as four site locations may be passed to S\bSP\bPL\bLA\bAT\bT!\b! at
- a time for analysis:
-
- splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p
- 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
- topographic map can be specified using the _\b-_\bo switch, and
- line-of-sight paths between each transmitter and the
- receiver site indicated will be produced on the map, each
- in its own color. The path between the first transmitter
- specified to the receiver will be in green, the path
- between the second transmitter and the receiver will be in
- cyan, the path between the third transmitter and the
- receiver will be in violet, and the path between the
- fourth transmitter and the receiver will be in sienna.
-
- 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
- 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
- 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
- switch is invoked as follows:
-
- 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). 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)
- switch:
-
- 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
- use the "four-thirds earth" model for line-of-sight propa-
- 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
- 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
- 315 degrees azimuth.
-
-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 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 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-
- ues in decimal):
-
- site1: Green (0,255,0)
- site2: Cyan (0,255,255)
- site3: Medium Violet (147,112,219)
- site4: Sienna 1 (255,130,71)
-
- site1 + site2: Yellow (255,255,0)
- site1 + site3: Pink (255,192,203)
- site1 + site4: Green Yellow (173,255,47)
- site2 + site3: Orange (255,165,0)
- site2 + site4: Dark Sea Green 1 (193,255,193)
- site3 + site4: Dark Turquoise (0,206,209)
-
- site1 + site2 + site3: Dark Green (0,100,0)
- site1 + site2 + site4: Blanched Almond (255,235,205)
- site1 + site3 + site4: Medium Spring Green (0,250,154)
- site2 + site3 + site4: Tan (210,180,140)
-
- site1 + site2 + site3 + site4: Gold2 (238,201,0)
-
- If separate _\b._\bq_\bt_\bh files are generated, each representing a
- common site location but a different antenna height, a
- single topographic map illustrating the regional coverage
- from as many as four separate locations on a single tower
- may be generated by S\bSP\bPL\bLA\bAT\bT!\b!.
-
-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
- 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 no text report is desired, then the _\b-_\bN switch is used:
-
- splat -t tx_site -r rx_site -N -o topo_map.ppm
-
- 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
- (HAAT) according to the procedure defined by Federal Com-
- munications Commission Part 73.313(d). According to this
- definition, terrain elevations along eight radials between
- 2 and 10 miles (3 and 16 kilometers) from the site being
- analyzed are sampled and averaged for each 45 degrees of
- azimuth starting with True North. If one or more radials
- 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.
-
- 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
- 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
- cases, this will be true, unless the site in question does
- 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 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
- 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
- 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.
-
-A\bAU\bUT\bTH\bHO\bOR\bRS\bS
- John A. Magliacane, KD2BD <_\bk_\bd_\b2_\bb_\bd_\b@_\ba_\bm_\bs_\ba_\bt_\b._\bo_\br_\bg>
- Creator, Lead Developer
-
- 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)
+++ /dev/null
-.TH SPLAT! 1 "20 December 2006" "KD2BD Software" "KD2BD Software"
-.SH NAME
-splat \- An RF \fBS\fPignal \fBP\fPropagation, \fBL\fPoss, \fBA\fPnd \fBT\fPerrain analysis tool
-.SH SYNOPSIS
-splat [-t \fItransmitter_site.qth\fP]
-[-r \fIreceiver_site.qth\fP]
-[-c \fIrx antenna height for LOS coverage analysis (feet/meters) (float)\fP]
-[-L \fIrx antenna height for Longley-Rice coverage analysis (feet/meters) (float)\fP]
-[-p \fIterrain_profile.ext\fP]
-[-e \fIelevation_profile.ext\fP]
-[-h \fIheight_profile.ext\fP]
-[-H \fInormalized_height_profile.ext\fP]
-[-l \fILongley-Rice_profile.ext\fP]
-[-o \fItopographic_map_filename.ppm\fP]
-[-b \fIcartographic_boundary_filename.dat\fP]
-[-s \fIsite/city_database.dat\fP]
-[-d \fIsdf_directory_path\fP]
-[-m \fIearth radius multiplier (float)\fP]
-[-f \fIfrequency (MHz) for Fresnel zone calculations (float)\fP]
-[-R \fImaximum coverage radius (miles/kilometers) (float)\fP]
-[-dB \fImaximum attenuation contour to display on path loss maps (80-230 dB)\fP]
-[-nf \fIdo not plot Fresnel zones in height plots\fP]
-[-plo \fIpath_loss_output_file.txt\fP]
-[-pli \fIpath_loss_input_file.txt\fP]
-[-udt \fIuser_defined_terrain_file.dat\fP]
-[-n]
-[-N]
-[-geo]
-[-kml]
-[-metric]
-.SH DESCRIPTION
-\fBSPLAT!\fP is a powerful terrestrial RF propagation and terrain
-analysis tool covering the spectrum between 20 MHz and 20 GHz.
-\fBSPLAT!\fP is free software, and is designed for operation on Unix
-and Linux-based workstations. 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 \fBSPLAT!\fP source code
-in proprietary or closed-source applications is a violation of this
-license, and is \fBstrictly\fP forbidden.
-
-\fBSPLAT!\fP is distributed in the hope that it will be useful, but
-WITHOUT ANY WARRANTY, without even the implied warranty of MERCHANTABILITY
-or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
-for more details.
-.SH INTRODUCTION
-Applications of \fBSPLAT!\fP 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 interference studies, and the determination
-of analog and digital terrestrial radio and television contour regions.
-
-\fBSPLAT!\fP provides RF site engineering data such as great circle
-distances and bearings between sites, antenna elevation angles (uptilt),
-depression angles (downtilt), antenna height above mean sea level,
-antenna height above average terrain, bearings and distances to known
-obstructions, 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.
-
-\fBSPLAT!\fP produces reports, graphs, and high resolution topographic
-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,
-\fBSPLAT!\fP determines individual and mutual areas of coverage within
-the network specified.
-
-Simply typing \fCsplat\fR on the command line will return a summary
-of \fBSPLAT!\fP's command line options:
-\fC
- --==[ 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/kilometers)
- -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 output)
- -kml generate a Google Earth .kml file (for point-to-point links)
- -metric employ metric rather than imperial units for all user I/O
-\fR
-.SH INPUT FILES
-\fBSPLAT!\fP 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 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.
-.SH SPLAT DATA FILES
-\fBSPLAT!\fP imports topographic data in the form of SPLAT Data Files
-(SDFs). These files may be generated from a number of information sources.
-In the United States, SPLAT Data Files can be generated through U.S.
-Geological Survey Digital Elevation Models (DEMs) using the \fBusgs2sdf\fP
-utility included with \fBSPLAT!\fP. USGS Digital Elevation Models
-compatible with this utility may be downloaded from:
-\fIhttp://edcftp.cr.usgs.gov/pub/data/DEM/250/\fP.
-
-Significantly better resolution and accuracy can be obtained through
-the use of SRTM-3 Version 2 digital elevation 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 \fBsrtm2sdf\fP utility.
-SRTM-3 Version 2 data may be obtained through anonymous FTP from:
-\fIftp://e0srp01u.ecs.nasa.gov:21/srtm/version2/\fP
-
-Despite the higher accuracy that SRTM data has to offer, some voids
-in the data sets exist. When voids are detected, the \fBsrtm2sdf\fP
-utility replaces them with corresponding data found in existing SDF
-files (that were presumably created from earlier USGS data through the
-\fBusgs2sdf\fP utility). If USGS-derived SDF data is not available, voids
-are handled through adjacent pixel averaging, or direct replacement.
-
-SPLAT Data Files contain integer value topographic elevations (in meters)
-referenced to mean sea level for 1-degree by 1-degree regions of the
-earth with a resolution of 3-arc seconds. SDF files can be read in
-either standard format (\fI.sdf\fP) as generated by the \fBusgs2sdf\fP
-and \fBsrtm2sdf\fP utilities, or in bzip2 compressed format
-(\fI.sdf.bz2\fP). Since uncompressed files can be processed slightly
-faster than files that have been compressed, \fBSPLAT!\fP searches for
-needed SDF data in uncompressed format first. If uncompressed data
-cannot be located, \fBSPLAT!\fP then searches for data in bzip2 compressed
-format. If no compressed SDF files can be found for the region requested,
-\fBSPLAT!\fP assumes the region is over water, and will assign an
-elevation of sea-level to these areas.
-
-This feature of \fBSPLAT!\fP 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 \fBSPLAT!\fP
-underscores the importance of having all the SDF files required for
-the region being analyzed if meaningful results are to be expected.
-.SH SITE LOCATION (QTH) FILES
-\fBSPLAT!\fP imports site location information of transmitter and receiver
-sites analyzed by the program from ASCII files having a \fI.qth\fP 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),
-each separated by a single line-feed character. The antenna height is
-assumed to be specified in feet unless followed by the letter \fIm\fP or
-the word \fImeters\fP in either upper or lower case. Latitude and
-longitude information may be expressed in either decimal format (74.6889)
-or degree, minute, second (DMS) format (74 41 20.0).
-
-For example, a site location file describing television station WNJT,
-Trenton, NJ (\fIwnjt.qth\fP) might read as follows:
-\fC
- WNJT
- 40.2833
- 74.6889
- 990.00
-\fR
-Each transmitter and receiver site analyzed by \fBSPLAT!\fP must be
-represented by its own site location (QTH) file.
-.SH LONGLEY-RICE PARAMETER (LRP) FILES
-Longley-Rice parameter data files are required for \fBSPLAT!\fP 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 transmitter site QTH file, but with a
-\fI.lrp\fP extension. \fBSPLAT!\fP LRP files share the following
-format (\fIwnjt.lrp\fP):
-\fC
- 15.000 ; Earth Dielectric Constant (Relative permittivity)
- 0.005 ; Earth Conductivity (Siemens per meter)
- 301.000 ; Atmospheric Bending Constant (N-units)
- 700.000 ; Frequency in MHz (20 MHz to 20 GHz)
- 5 ; Radio Climate (5 = Continental Temperate)
- 0 ; Polarization (0 = Horizontal, 1 = Vertical)
- 0.5 ; Fraction of situations (50% of locations)
- 0.5 ; Fraction of time (50% of the time)
-\fR
-If an LRP file corresponding to the tx_site QTH file cannot
-be found, \fBSPLAT!\fP scans the current working directory for
-the file "splat.lrp". If this file cannot be found, then the default
-parameters listed above will be assigned by \fBSPLAT!\fP and a
-corresponding "splat.lrp" file containing this data will be written
-to the current working directory. "splat.lrp" can then be edited
-by the user as needed.
-
-Typical Earth dielectric constants and conductivity values are as
-follows:
-\fC
- Dielectric Constant Conductivity
- Salt water : 80 5.000
- Good ground : 25 0.020
- Fresh water : 80 0.010
- Marshy land : 12 0.007
- Farmland, forest : 15 0.005
- Average ground : 15 0.005
- Mountain, sand : 13 0.002
- City : 5 0.001
- Poor ground : 4 0.001
-\fR
-Radio climate codes used by \fBSPLAT!\fP are as follows:
-\fC
- 1: Equatorial (Congo)
- 2: Continental Subtropical (Sudan)
- 3: Maritime Subtropical (West coast of Africa)
- 4: Desert (Sahara)
- 5: Continental Temperate
- 6: Maritime Temperate, over land (UK and west coasts of US & EU)
- 7: Maritime Temperate, over sea
-\fR
-The Continental Temperate climate is common to large land masses in
-the temperate zone, such as the United States. For paths shorter than
-100 km, there is little difference between Continental and Maritime
-Temperate climates.
-
-The final two parameters in the \fI.lrp\fP file correspond to the statistical
-analysis provided by the Longley-Rice model. In this example, \fBSPLAT!\fP
-will return the maximum path loss occurring 50% of the time (fraction
-of time) in 50% of situations (fraction of situations). In the United
-States, use a fraction of time parameter of 0.97 for digital television
-(8VSB modulation), or 0.50 for analog (VSB-AM+NTSC) transmissions.
-
-For further information on these parameters, see:
-\fIhttp://flattop.its.bldrdoc.gov/itm.html\fP and
-\fIhttp://www.softwright.com/faq/engineering/prop_longley_rice.html\fP
-.SH CITY LOCATION FILES
-The names and locations of cities, tower sites, or other points of interest
-may be imported and plotted on topographic maps generated by \fBSPLAT!\fP.
-\fBSPLAT!\fP imports the names of cities and locations from ASCII files
-containing the location of interest's name, latitude, and longitude.
-Each field is separated by a comma. Each record is separated by a
-single line feed character. As was the case with the \fI.qth\fP
-files, latitude and longitude information may be entered in either
-decimal or degree, minute, second (DMS) format.
-
-For example (\fIcities.dat\fP):
-\fC
- Teaneck, 40.891973, 74.014506
- Tenafly, 40.919212, 73.955892
- Teterboro, 40.859511, 74.058908
- Tinton Falls, 40.279966, 74.093924
- Toms River, 39.977777, 74.183580
- Totowa, 40.906160, 74.223310
- Trenton, 40.219922, 74.754665
-\fR
-A total of five separate city data files may be imported at a time,
-and there is no limit to the size of these files. \fBSPLAT!\fP reads
-city data on a "first come/first served" basis, and plots only those
-locations whose annotations do not conflict with annotations of
-locations read earlier in the current city data file, or in previous
-files. This behavior minimizes clutter in \fBSPLAT!\fP generated
-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 further 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 available from the
-U.S. Census Bureau using the \fBcitydecoder\fP utility included with
-\fBSPLAT!\fP. Such data is available free of charge via the Internet
-at: \fIhttp://www.census.gov/geo/www/cob/bdy_files.html\fP, and must
-be in ASCII format.
-.SH CARTOGRAPHIC BOUNDARY DATA FILES
-Cartographic boundary data may also be imported to plot the boundaries of
-cities, counties, or states on topographic maps generated by \fBSPLAT!\fP.
-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:
-\fIhttp://www.census.gov/geo/www/cob/co2000.html#ascii\fP and
-\fIhttp://www.census.gov/geo/www/cob/pl2000.html#ascii\fP. 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.
-.SH PROGRAM OPERATION
-\fBSPLAT!\fP is invoked via the command-line using a series of switches
-and arguments. Since \fBSPLAT!\fP is a CPU and memory intensive application,
-this type of interface minimizes overhead and lends itself well to
-scripted (batch) operations. \fBSPLAT!\fP's CPU and memory scheduling
-priority may be modified through the use of the Unix \fBnice\fP command.
-
-The number and type of switches passed to \fBSPLAT!\fP determine its
-mode of operation and method of output data generation. Nearly all
-of \fBSPLAT!\fP's switches may be cascaded in any order on the command
-line when invoking the program.
-
-\fBSPLAT!\fP operates in two distinct modes: \fIpoint-to-point mode\fP,
-and \fIarea prediction mode\fP. 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
-specified when performing line-of-sight analysis.
-.SH POINT-TO-POINT ANALYSIS
-\fBSPLAT!\fP may be used to perform line-of-sight terrain analysis
-between two specified site locations. For example:
-
-\fCsplat -t tx_site.qth -r rx_site.qth\fR
-
-invokes a line-of-sight terrain analysis between the transmitter
-specified in \fItx_site.qth\fP and receiver specified in \fIrx_site.qth\fP
-using a True Earth radius model, and writes a \fBSPLAT!\fP 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,
-\fBSPLAT!\fP 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 \fI-metric\fP switch is added to \fBSPLAT!\fP's command line options:
-
-\fCsplat -t tx_site.qth -r rx_site.qth -metric\fR
-
-If the antenna must be raised a significant amount, this determination
-may take a few moments. Note that the results provided are the \fIminimum\fP
-necessary for a line-of-sight path to exist, and in the case of this
-simple example, do not take Fresnel zone clearance requirements into
-consideration.
-
-\fIqth\fP extensions are assumed by \fBSPLAT!\fP for QTH files, and
-are optional when specifying -t and -r arguments on the command-line.
-\fBSPLAT!\fP automatically reads all SPLAT Data Files necessary to
-conduct the terrain analysis between the sites specified. \fBSPLAT!\fP
-searches for the required SDF files in the current working directory
-first. If the needed files are not found, \fBSPLAT!\fP then searches
-in the path specified by the \fI-d\fP command-line switch:
-
-\fCsplat -t tx_site -r rx_site -d /cdrom/sdf/\fR
-
-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 of last resort to all the SDF files. The path in the
-\fI$HOME/.splat_path\fP file must be of the form of a single line of
-ASCII text:
-
-\fC/opt/splat/sdf/\fR
-
-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 receiver can be generated
-by adding the \fI-p\fP switch:
-
-\fCsplat -t tx_site -r rx_site -p terrain_profile.png\fR
-
-\fBSPLAT!\fP invokes \fBgnuplot\fP when generating graphs. The filename
-extension specified to \fBSPLAT!\fP determines the format of the graph
-produced. \fI.png\fP will produce a 640x480 color PNG graphic file,
-while \fI.ps\fP or \fI.postscript\fP will produce postscript output.
-Output in formats such as GIF, Adobe Illustrator, AutoCAD dxf,
-LaTeX, and many others are available. Please consult \fBgnuplot\fP,
-and \fBgnuplot\fP's documentation 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 the receiver can be generated
-by using the \fI-e\fP switch:
-
-\fCsplat -t tx_site -r rx_site -e elevation_profile.png\fR
-
-The graph produced using this switch illustrates the elevation 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
-(receiver's location) and the location of the transmitting antenna on
-the right. This trace illustrates the elevation 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 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 generated using
-the \fI-h\fP switch:
-
-\fCsplat -t tx_site -r rx_site -h height_profile.png\fR
-
-A terrain height plot normalized to the transmitter and receiver
-antenna heights can be obtained using the \fI-H\fP switch:
-
-\fCsplat -t tx_site -r rx_site -H normalized_height_profile.png\fR
-
-A contour of the Earth's curvature is also plotted in this mode.
-
-The first Fresnel Zone, and 60% of the first Fresnel Zone can be
-added to height profile graphs by adding the \fI-f\fP switch, and
-specifying a frequency (in MHz) at which the Fresnel Zone should be
-modeled:
-
-\fCsplat -t tx_site -r rx_site -f 439.250 -H normalized_height_profile.png\fR
-
-A graph showing Longley-Rice path loss may be plotted using the
-\fI-l\fP switch:
-
-\fCsplat -t tx_site -r rx_site -l path_loss_profile.png\fR
-
-As before, adding the \fI-metric\fP 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 \fBSPLAT!\fP in the form of a text file with
-a \fI.lro\fP filename extension. The report contains bearings and
-distances between the transmitter and receiver, as well as the
-Longley-Rice path loss for various distances between the transmitter
-and receiver locations. The mode of propagation for points along the
-path are given as \fILine-of-Sight\fP, \fISingle Horizon\fP, \fIDouble
-Horizon\fP, \fIDiffraction Dominant\fP, and \fITroposcatter Dominant\fP.
-
-To determine the signal-to-noise (SNR) ratio at remote location
-where random Johnson (thermal) noise is the primary limiting
-factor in reception:
-
-.EQ
-SNR = T - NJ - L + G - NF
-.EN
-
-where \fBT\fP is the ERP of the transmitter in dBW in the direction
-of the receiver, \fBNJ\fP is Johnson Noise in dBW (-136 dBW for a 6 MHz
-television channel), \fBL\fP is the path loss provided by \fBSPLAT!\fP
-in dB (as a \fIpositive\fP number), \fBG\fP is the receive antenna gain
-in dB over isotropic, and \fBNF\fP is the receiver noise figure in dB.
-
-\fBT\fP may be computed as follows:
-
-.EQ
-T = TI + GT
-.EN
-
-where \fBTI\fP is actual amount of RF power delivered to the transmitting
-antenna in dBW, \fBGT\fP is the transmitting antenna gain (over isotropic)
-in the direction of the receiver (or the horizon if the receiver is over
-the horizon).
-
-To compute how much more signal is available over the minimum to
-necessary to achieve a specific signal-to-noise ratio:
-
-.EQ
-Signal_Margin = SNR - S
-.EN
-
-where \fBS\fP 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 \fBSPLAT!\fP to visualize the
-path between the transmitter and receiver sites from yet another
-perspective. Topographic maps generated by \fBSPLAT!\fP display
-elevations using a logarithmic grayscale, with higher elevations
-represented through brighter shades of gray. The dynamic range of
-the image is scaled between the highest and lowest elevations present
-in the map. The only exception to this is sea-level, which is
-represented using the color blue.
-
-Topographic output is invoked using the \fI-o\fP switch:
-
-\fCsplat -t tx_site -r rx_site -o topo_map.ppm\fR
-
-The \fI.ppm\fP extension on the output filename is assumed by
-\fBSPLAT!\fP, and is optional.
-
-In this example, \fItopo_map.ppm\fP will illustrate the locations of the
-transmitter and receiver sites specified. In addition, the great circle
-path between the two sites will be drawn over locations for which an
-unobstructed path exists to the transmitter at a receiving antenna
-height equal to that of the receiver site (specified in \fIrx_site.qth\fP).
-
-It may desirable to populate the topographic map with names and locations
-of cities, tower sites, or other important locations. A city file may be
-passed to \fBSPLAT!\fP using the \fI-s\fP switch:
-
-\fCsplat -t tx_site -r rx_site -s cities.dat -o topo_map\fR
-
-Up to five separate city files may be passed to \fBSPLAT!\fP at a time
-following the \fI-s\fP switch.
-
-County and state boundaries may be added to the map by specifying up
-to five U.S. Census Bureau cartographic boundary files using the \fI-b\fP
-switch:
-
-\fCsplat -t tx_site -r rx_site -b co34_d00.dat -o topo_map\fR
-
-In situations where multiple transmitter sites are in use, as many as
-four site locations may be passed to \fBSPLAT!\fP at a time for analysis:
-
-\fCsplat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p profile.png\fR
-
-In this example, four separate terrain profiles and obstruction reports
-will be generated by \fBSPLAT!\fP. A single topographic map can be
-specified using the \fI-o\fP switch, and line-of-sight paths between
-each transmitter and the receiver site indicated will be produced on
-the map, each in its own color. The path between the first transmitter
-specified to the receiver will be in green, the path between the
-second transmitter and the receiver will be in cyan, the path between
-the third transmitter and the receiver will be in violet, and the
-path between the fourth transmitter and the receiver will be in sienna.
-
-\fBSPLAT!\fP 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 \fBxv\fP,
-\fBThe GIMP\fP, \fBImageMagick\fP, and \fBXPaint\fP. PNG format is
-highly recommended for lossless compressed storage of \fBSPLAT!\fP
-generated topographic output files. \fBImageMagick\fP's command-line
-utility easily converts \fBSPLAT!\fP's PPM files to PNG format:
-
-\fCconvert splat_map.ppm splat_map.png\fR
-
-Another excellent PPM to PNG command-line utility is available
-at: \fIhttp://www.libpng.org/pub/png/book/sources.html\fP. As a last
-resort, PPM files may be compressed using the bzip2 utility, and read
-directly by \fBThe GIMP\fP in this format.
-.SH REGIONAL COVERAGE ANALYSIS
-\fBSPLAT!\fP can analyze a transmitter or repeater site, or network
-of sites, and predict the regional coverage for each site specified.
-In this mode, \fBSPLAT!\fP can generate a topographic map displaying
-the geometric line-of-sight coverage 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. \fBSPLAT!\fP switches from
-point-to-point analysis mode to area prediction mode when the \fI-c\fP
-switch is invoked as follows:
-
-\fCsplat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o tx_coverage\fR
-
-In this example, \fBSPLAT!\fP generates a topographic map called
-\fItx_coverage.ppm\fP that illustrates the predicted line-of-sight
-regional coverage of \fItx_site\fP to receiving locations having
-antennas 30.0 feet above ground level (AGL). If the \fI-metric\fP
-switch is used, the argument following the \fI-c\fP switch is
-interpreted as being in meters, rather than in feet. The contents
-of \fIcities.dat\fP are plotted on the map, as are the cartographic
-boundaries contained in the file \fIco34_d00.dat\fP.
-
-When plotting line-of-sight paths and areas of regional coverage,
-\fBSPLAT!\fP by default does not account for the effects of
-atmospheric bending. However, this behavior may be modified
-by using the Earth radius multiplier (\fI-m\fP) switch:
-
-\fCsplat -t wnjt -c 30.0 -m 1.333 -s cities.dat -b counties.dat -o map.ppm\fR
-
-An earth radius multiplier of 1.333 instructs \fBSPLAT!\fP to use
-the "four-thirds earth" model for line-of-sight propagation analysis.
-Any appropriate earth radius multiplier may be selected by the user.
-
-When invoked in area prediction mode, \fBSPLAT!\fP generates a
-site report for each station analyzed. \fBSPLAT!\fP 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 315 degrees azimuth.
-.SH DETERMINING MULTIPLE REGIONS OF LOS COVERAGE
-\fBSPLAT!\fP can also display line-of-sight coverage areas for as
-many as four separate transmitter sites on a common topographic map.
-For example:
-
-\fCsplat -t site1 site2 site3 site4 -c 10.0 -metric -o network.ppm\fR
-
-plots the regional line-of-sight coverage of site1, site2, site3,
-and site4 based on a receive antenna located 10.0 meters above ground
-level. A topographic map is then written to the file \fInetwork.ppm\fP.
-The line-of-sight coverage area of the transmitters are plotted as
-follows in the colors indicated (along with their corresponding RGB
-values in decimal):
-\fC
- site1: Green (0,255,0)
- site2: Cyan (0,255,255)
- site3: Medium Violet (147,112,219)
- site4: Sienna 1 (255,130,71)
-
- site1 + site2: Yellow (255,255,0)
- site1 + site3: Pink (255,192,203)
- site1 + site4: Green Yellow (173,255,47)
- site2 + site3: Orange (255,165,0)
- site2 + site4: Dark Sea Green 1 (193,255,193)
- site3 + site4: Dark Turquoise (0,206,209)
-
- site1 + site2 + site3: Dark Green (0,100,0)
- site1 + site2 + site4: Blanched Almond (255,235,205)
- site1 + site3 + site4: Medium Spring Green (0,250,154)
- site2 + site3 + site4: Tan (210,180,140)
-
- site1 + site2 + site3 + site4: Gold2 (238,201,0)
-\fR
-If separate \fI.qth\fP files are generated, each representing a common
-site location but a different antenna height, a single topographic map
-illustrating the regional coverage from as many as four separate locations
-on a single tower may be generated by \fBSPLAT!\fP.
-.SH LONGLEY-RICE PATH LOSS ANALYSIS
-If the \fI-c\fP switch is replaced by a \fI-L\fP switch, a
-Longley-Rice path loss map for a transmitter site may be generated:
-
-\fCsplat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o path_loss_map\fR
-
-In this mode, \fBSPLAT!\fP generates a multi-color map illustrating
-expected signal levels (path loss) in areas surrounding 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 \fI-R\fP switch. The argument must be given in miles
-(or kilometers if the \fI-metric\fP switch is used). If a range wider
-than the generated topographic map is specified, \fBSPLAT!\fP will
-perform Longley-Rice path loss calculations between all four corners
-of the area prediction map.
-
-The \fI-db\fP 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,
-\fBSPLAT!\fP's path loss plot can be constrained to the region
-bounded by the 140 dB attenuation contour as follows:
-
-\fCsplat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -db 140 -o plot.ppm\fR
-
-.SH ANTENNA RADIATION PATTERN PARAMETERS
-Normalized field voltage patterns for a transmitting antenna's horizontal
-and vertical planes are imported automatically into \fBSPLAT!\fP 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 transmitter
-and LRP files, but with \fI.az\fP and \fI.el\fP extensions for azimuth
-and elevation pattern files, respectively. Specifications regarding
-pattern rotation (if any) and mechanical beam tilt and tilt direction
-(if any) are also contained within \fBSPLAT!\fP antenna pattern files.
-
-For example, the first few lines of a \fBSPLAT!\fP azimuth pattern file
-might appear as follows (\fIkvea.az\fP):
-\fC
- 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
-\fR
-The first line of the \fI.az\fP file specifies the amount of azimuthal
-pattern rotation (measured clockwise in degrees from True North) to be
-applied by \fBSPLAT!\fP to the data contained in the \fI.az\fP file.
-This is followed by azimuth headings (0 to 360 degrees) and their associated
-normalized field patterns (0.000 to 1.000) separated by whitespace.
-
-The structure of \fBSPLAT!\fP elevation pattern files is slightly different.
-The first line of the \fI.el\fP file specifies the amount of mechanical
-beam tilt applied to the antenna. Note that a \fIdownward tilt\fP
-(below the horizon) is expressed as a \fIpositive angle\fP, while an
-\fIupward tilt\fP (above the horizon) is expressed as a \fInegative angle\fP.
-This data is followed by the azimuthal direction of the tilt, separated 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. Elevation angles must be specified
-over a -10.0 to +90.0 degree range. As was the convention with mechanical
-beamtilt, \fInegative elevation angles\fP are used to represent elevations
-\fIabove the horizon\fP, while \fIpositive angles\fP represents elevations
-\fIbelow the horizon\fP.
-
-For example, the first few lines a \fBSPLAT!\fP elevation pattern file
-might appear as follows (\fIkvea.el\fP):
-\fC
- 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
-\fR
-In this example, the antenna is mechanically tilted downward 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,
-\fBSPLAT!\fP will interpolate the values provided to determine the
-data at the required resolution, although this may result in a loss
-in accuracy.
-
-.SH IMPORTING AND EXPORTING REGIONAL PATH LOSS CONTOUR DATA
-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 coverage 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 \fBSPLAT!\fP
-to rapidly produce a revised path loss map.
-
-For example, a path loss output file can be generated by \fBSPLAT!\fP
-for a receive site 30 feet above ground level over a 50 mile radius
-surrounding a transmitter site to a maximum path loss of 140 dB using
-the following syntax:
-
-\fCsplat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat\fR
-
-\fBSPLAT!\fP path loss output files often exceed 100 megabytes in size.
-They contain information relating to the boundaries of region they describe
-followed by latitudes (degrees North), longitudes (degrees West), azimuths,
-elevations (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 \fBSPLAT!\fP path loss
-output file take on the following appearance (\fIpathloss.dat\fP):
-\fC
- 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
-\fR
-It is not uncommon for \fBSPLAT!\fP 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 \fBvim\fP
-text editor has proven capable of editing files of this size.
-
-Note as was the case in the antenna pattern files, negative 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 \fI-L\fP switch \fIif\fP the path between transmitter
-and receiver is unobstructed. If the path between the transmitter
-and receiver is obstructed, then the elevation angle to the first
-obstruction is returned by \fBSPLAT!\fP. 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 \fBSPLAT!\fP path loss files to reflect antenna
-pattern data, \fIonly the last column (path loss)\fP 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 \fBSPLAT!\fP for
-generating revised coverage maps:
-
-\fCsplat -t kvea -pli pathloss.dat -s city.dat -b county.dat -o map.ppm\fR
-
-\fBSPLAT!\fP path loss files can also be used for conducting coverage or
-interference studies outside of \fBSPLAT!\fP.
-.SH USER-DEFINED TERRAIN INPUT FILES
-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 \fBSPLAT!\fP analysis being conducted, but noticeably
-absent from the SDF files being used. A user-defined terrain file is imported
-into a \fBSPLAT!\fP analysis using the \fI-udt\fP switch:
-
-\fC splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm\fR
-
-A user-defined terrain file has the following appearance and structure:
-\fC
- 40.32180556, 74.1325, 100.0 meters
- 40.321805, 74.1315, 300.0
- 40.3218055, 74.1305, 100.0 meters
-\fR
-Terrain height is interpreted as being described in feet above ground
-level unless followed by the word \fImeters\fP, and is added \fIon top of\fP
-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. Features described
-in the user-defined terrain file that overlap previously defined features
-in the file are ignored by \fBSPLAT!\fP.
-.SH SIMPLE TOPOGRAPHIC MAP GENERATION
-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 between the sites, the \fI-n\fP
-switch should be invoked as follows:
-
-\fCsplat -t tx_site -r rx_site -n -o topo_map.ppm\fR
-
-If no text report is desired, then the \fI-N\fP switch is used:
-
-\fCsplat -t tx_site -r rx_site -N -o topo_map.ppm\fR
-
-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:
-
-\fCsplat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o topo_map.ppm\fR
-
-where -R specifies the minimum radius of the map in miles (or kilometers
-if the \fI-metric\fP switch is used).
-
-If the \fI-o\fP switch and output filename are omitted in these
-operations, topographic output is written to a file named \fImap.ppm\fP
-in the current working directory by default.
-.SH GEOREFERENCE FILE GENERATION
-Topographic, coverage (\fI-c\fP), and path loss contour (\fI-L\fP) maps
-generated by \fBSPLAT!\fP may be imported into \fBXastir\fP (X Amateur
-Station Tracking and Information Reporting) software by generating a
-georeference file using \fBSPLAT!\fP's \fI-geo\fP switch:
-
-\fCsplat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o map.ppm\fR
-
-The georeference file generated will have the same base name as the
-\fI-o\fP file specified, but have a \fI .geo\fP extension, and permit
-proper interpretation and display of \fBSPLAT!\fP's .ppm graphics in
-\fBXastir\fP software.
-.SH GOOGLE MAP KML FILE GENERATION
-Keyhole Markup Language files compatible with \fBGoogle Earth\fP may
-be generated by \fBSPLAT!\fP when performing point-to-point analyses
-by invoking the \fI-kml\fP switch:
-
-\fCsplat -t wnjt -r kd2bd -kml\fR
-
-The KML file generated will have the same filename structure as an
-Obstruction Report for the transmitter and receiver site names given,
-except it will carry a \fI .kml\fP extension.
-
-Once loaded into \fBGoogle Earth\fP (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 displayed in
-green. \fBGoogle Earth\fP's navigation tools allow the user to
-"fly" around the path, identify landmarks, roads, and other
-featured content.
-.SH DETERMINATION OF ANTENNA HEIGHT ABOVE AVERAGE TERRAIN
-\fBSPLAT!\fP determines antenna height above average terrain (HAAT)
-according to the procedure defined by Federal Communications Commission
-Part 73.313(d). According to this definition, terrain elevations along
-eight radials between 2 and 10 miles (3 and 16 kilometers) from the site
-being analyzed are sampled and averaged for each 45 degrees of azimuth
-starting with True North. If one or more radials lie entirely over water
-or over land outside the United States (areas for which no USGS topography
-data is available), then those radials are omitted from the calculation
-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 compliance with FCC Part 73.313(d)
-in areas along the borders of the United States if the SDF files
-used by \fBSPLAT!\fP are SRTM-derived.
-
-When performing point-to-point terrain analysis, \fBSPLAT!\fP 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 data in
-memory.
-
-When performing area prediction analysis, enough topography data is
-normally loaded by \fBSPLAT!\fP to perform average terrain calculations.
-Under such conditions, \fBSPLAT!\fP 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, \fBSPLAT!\fP reports \fINo Terrain\fP
-for the radial paths affected.
-.SH RESTRICTING THE MAXIMUM SIZE OF AN ANALYSIS REGION
-\fBSPLAT!\fP 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 \fI#define MAXSLOTS\fP statement in the first several lines of
-\fIsplat.cpp\fP sets the maximum number of "slots" available for holding
-topography data. It also sets the maximum size of the topographic maps
-generated by \fBSPLAT!\fP. MAXSLOTS is set to 9 by default. If \fBSPLAT!\fP
-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 \fBSPLAT!\fP 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 \fBSPLAT!\fP 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.
-.SH ADDITIONAL INFORMATION
-The latest news and information regarding \fBSPLAT!\fP software is
-available through the official \fBSPLAT!\fP software web page located
-at: \fIhttp://www.qsl.net/kd2bd/splat.html\fP.
-.SH AUTHORS
-.TP
-John A. Magliacane, KD2BD <\fIkd2bd@amsat.org\fP>
-Creator, Lead Developer
-.TP
-Doug McDonald <\fImcdonald@scs.uiuc.edu\fP>
-Longley-Rice Model integration
-.TP
-Ron Bentley <\fIronbentley@earthlink.net\fP>
-Fresnel Zone plotting and clearance determination
-
+++ /dev/null
-%!PS-Adobe-3.0
-%%Creator: groff version 1.17.2
-%%CreationDate: Fri Jan 19 15:42:11 2007
-%%DocumentNeededResources: font Times-Roman
-%%+ font Times-Bold
-%%+ font Times-Italic
-%%+ font Courier
-%%+ font Symbol
-%%DocumentSuppliedResources: procset grops 1.17 2
-%%Pages: 14
-%%PageOrder: Ascend
-%%Orientation: Portrait
-%%EndComments
-%%BeginProlog
-%%BeginResource: procset grops 1.17 2
-/setpacking where{
-pop
-currentpacking
-true setpacking
-}if
-/grops 120 dict dup begin
-/SC 32 def
-/A/show load def
-/B{0 SC 3 -1 roll widthshow}bind def
-/C{0 exch ashow}bind def
-/D{0 exch 0 SC 5 2 roll awidthshow}bind def
-/E{0 rmoveto show}bind def
-/F{0 rmoveto 0 SC 3 -1 roll widthshow}bind def
-/G{0 rmoveto 0 exch ashow}bind def
-/H{0 rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
-/I{0 exch rmoveto show}bind def
-/J{0 exch rmoveto 0 SC 3 -1 roll widthshow}bind def
-/K{0 exch rmoveto 0 exch ashow}bind def
-/L{0 exch rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
-/M{rmoveto show}bind def
-/N{rmoveto 0 SC 3 -1 roll widthshow}bind def
-/O{rmoveto 0 exch ashow}bind def
-/P{rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
-/Q{moveto show}bind def
-/R{moveto 0 SC 3 -1 roll widthshow}bind def
-/S{moveto 0 exch ashow}bind def
-/T{moveto 0 exch 0 SC 5 2 roll awidthshow}bind def
-/SF{
-findfont exch
-[exch dup 0 exch 0 exch neg 0 0]makefont
-dup setfont
-[exch/setfont cvx]cvx bind def
-}bind def
-/MF{
-findfont
-[5 2 roll
-0 3 1 roll
-neg 0 0]makefont
-dup setfont
-[exch/setfont cvx]cvx bind def
-}bind def
-/level0 0 def
-/RES 0 def
-/PL 0 def
-/LS 0 def
-/MANUAL{
-statusdict begin/manualfeed true store end
-}bind def
-/PLG{
-gsave newpath clippath pathbbox grestore
-exch pop add exch pop
-}bind def
-/BP{
-/level0 save def
-1 setlinecap
-1 setlinejoin
-72 RES div dup scale
-LS{
-90 rotate
-}{
-0 PL translate
-}ifelse
-1 -1 scale
-}bind def
-/EP{
-level0 restore
-showpage
-}bind def
-/DA{
-newpath arcn stroke
-}bind def
-/SN{
-transform
-.25 sub exch .25 sub exch
-round .25 add exch round .25 add exch
-itransform
-}bind def
-/DL{
-SN
-moveto
-SN
-lineto stroke
-}bind def
-/DC{
-newpath 0 360 arc closepath
-}bind def
-/TM matrix def
-/DE{
-TM currentmatrix pop
-translate scale newpath 0 0 .5 0 360 arc closepath
-TM setmatrix
-}bind def
-/RC/rcurveto load def
-/RL/rlineto load def
-/ST/stroke load def
-/MT/moveto load def
-/CL/closepath load def
-/FL{
-currentgray exch setgray fill setgray
-}bind def
-/BL/fill load def
-/LW/setlinewidth load def
-/RE{
-findfont
-dup maxlength 1 index/FontName known not{1 add}if dict begin
-{
-1 index/FID ne{def}{pop pop}ifelse
-}forall
-/Encoding exch def
-dup/FontName exch def
-currentdict end definefont pop
-}bind def
-/DEFS 0 def
-/EBEGIN{
-moveto
-DEFS begin
-}bind def
-/EEND/end load def
-/CNT 0 def
-/level1 0 def
-/PBEGIN{
-/level1 save def
-translate
-div 3 1 roll div exch scale
-neg exch neg exch translate
-0 setgray
-0 setlinecap
-1 setlinewidth
-0 setlinejoin
-10 setmiterlimit
-[]0 setdash
-/setstrokeadjust where{
-pop
-false setstrokeadjust
-}if
-/setoverprint where{
-pop
-false setoverprint
-}if
-newpath
-/CNT countdictstack def
-userdict begin
-/showpage{}def
-}bind def
-/PEND{
-clear
-countdictstack CNT sub{end}repeat
-level1 restore
-}bind def
-end def
-/setpacking where{
-pop
-setpacking
-}if
-%%EndResource
-%%IncludeResource: font Times-Roman
-%%IncludeResource: font Times-Bold
-%%IncludeResource: font Times-Italic
-%%IncludeResource: font Courier
-%%IncludeResource: font Symbol
-grops begin/DEFS 1 dict def DEFS begin/u{.001 mul}bind def end/RES 72
-def/PL 792 def/LS false def/ENC0[/asciicircum/asciitilde/Scaron/Zcaron
-/scaron/zcaron/Ydieresis/trademark/quotesingle/.notdef/.notdef/.notdef
-/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef
-/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef
-/.notdef/.notdef/space/exclam/quotedbl/numbersign/dollar/percent
-/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen
-/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon
-/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O
-/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/circumflex
-/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y
-/z/braceleft/bar/braceright/tilde/.notdef/quotesinglbase/guillemotleft
-/guillemotright/bullet/florin/fraction/perthousand/dagger/daggerdbl
-/endash/emdash/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/hungarumlaut
-/dotaccent/breve/caron/ring/ogonek/quotedblleft/quotedblright/oe/lslash
-/quotedblbase/OE/Lslash/.notdef/exclamdown/cent/sterling/currency/yen
-/brokenbar/section/dieresis/copyright/ordfeminine/guilsinglleft
-/logicalnot/minus/registered/macron/degree/plusminus/twosuperior
-/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior
-/ordmasculine/guilsinglright/onequarter/onehalf/threequarters
-/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE
-/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex
-/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis
-/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn
-/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla
-/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis
-/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash
-/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis]def
-/Courier@0 ENC0/Courier RE/Times-Italic@0 ENC0/Times-Italic RE
-/Times-Bold@0 ENC0/Times-Bold RE/Times-Roman@0 ENC0/Times-Roman RE
-%%EndProlog
-%%Page: 1 1
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10.95
-/Times-Bold@0 SF -.219(NA)72 84 S(ME).219 E F0(splat \255 An RF)108 96 Q
-/F2 10/Times-Bold@0 SF(S)2.5 E F0(ignal)A F2(P)2.5 E F0(ropag)A(ation,)
--.05 E F2(L)2.5 E F0(oss,)A F2(A)2.5 E F0(nd)A F2(T)2.5 E F0
-(errain analysis tool)A F1(SYNOPSIS)72 112.8 Q F0 2.893(splat [-t)108
-124.8 R/F3 10/Times-Italic@0 SF(tr)7.893 E(ansmitter_site)-.15 E(.qth)
--.15 E F0 5.393(][)C(-r)-5.393 E F3 -.37(re)5.393 G(ceiver_site).37 E
-(.qth)-.15 E F0 5.393(][)C(-c)-5.393 E F3 2.892
-(rx antenna height for LOS co)5.393 F(ver)-.1 E 3.092 -.1(age a)-.15 H
-(nalysis).1 E(\(feet/meter)108 136.8 Q .399(s\) \(\215oat\))-.1 F F0
-2.899(][)C(-L)-2.899 E F3 .399(rx antenna height for Longle)2.899 F .399
-(y-Rice co)-.3 F(ver)-.1 E .599 -.1(age a)-.15 H .399
-(nalysis \(feet/meter).1 F .4(s\) \(\215oat\))-.1 F F0 2.9(][)C(-p)-2.9
-E F3(ter)2.9 E(-)-.2 E -.15(ra)108 148.8 S(in_pr).15 E(o\214le)-.45 E
-(.e)-.15 E(xt)-.2 E F0 2.85(][)C(-e)-2.85 E F3(ele)2.85 E(vation_pr)-.15
-E(o\214le)-.45 E(.e)-.15 E(xt)-.2 E F0 2.85(][)C(-h)-2.85 E F3
-(height_pr)2.85 E(o\214le)-.45 E(.e)-.15 E(xt)-.2 E F0 2.85(][)C(-H)
--2.85 E F3(normalized_height_pr)2.85 E(o\214le)-.45 E(.e)-.15 E(xt)-.2 E
-F0 2.85(][)C(-l)-2.85 E F3(Lon-)2.85 E(gle)108 160.8 Q(y-Rice_pr)-.3 E
-(o\214le)-.45 E(.e)-.15 E(xt)-.2 E F0 5.518(][)C(-o)-5.518 E F3(topo)
-5.518 E(gr)-.1 E(aphic_map_\214lename)-.15 E(.ppm)-.15 E F0 5.518(][)C
-(-b)-5.518 E F3(carto)5.518 E(gr)-.1 E(aphic_boundary_\214lename)-.15 E
-(.dat)-.15 E F0 5.518(][)C(-s)-5.518 E F3(site/city_database)108 172.8 Q
-(.dat)-.15 E F0 3.236(][)C(-d)-3.236 E F3(sdf_dir)3.236 E(ectory_path)
--.37 E F0 3.236(][)C(-m)-3.236 E F3 .736(earth r)3.236 F .735
-(adius multiplier \(\215oat\))-.15 F F0 3.235(][)C(-f)-3.235 E F3(fr)
-3.235 E .735(equency \(MHz\) for)-.37 F -1.77 -.55(Fr e)108 184.8 T .815
-(snel zone calculations \(\215oat\)).55 F F0 3.315(][)C(-R)-3.315 E F3
-.815(maximum co)3.315 F(ver)-.1 E 1.016 -.1(age r)-.15 H .816
-(adius \(miles/kilometer)-.05 F .816(s\) \(\215oat\))-.1 F F0 3.316(][)C
-(-dB)-3.316 E F3(maximum)3.316 E 1.431
-(attenuation contour to display on path loss maps \(80-230 dB\))108
-196.8 R F0 3.931(][)C(-nf)-3.931 E F3 1.43(do not plot F)3.93 F -.37(re)
--.55 G 1.43(snel zones in height).37 F(plots)108 208.8 Q F0 2.874(][)C
-(-plo)-2.874 E F3(path_loss_output_\214le)2.874 E(.txt)-.15 E F0 2.874
-(][)C(-pli)-2.874 E F3(path_loss_input_\214le)2.874 E(.txt)-.15 E F0
-2.874(][)C(-udt)-2.874 E F3(user_de\214ned_terr)2.875 E(ain_\214le)-.15
-E(.dat)-.15 E F0 2.875(][)C(-n])-2.875 E([-N] [-geo] [-kml] [-metric])
-108 220.8 Q F1(DESCRIPTION)72 237.6 Q F2(SPLA)108 249.6 Q(T!)-.95 E F0
-.854(is a po)3.354 F .854(werful terrestrial RF propag)-.25 F .853
-(ation and terrain analysis tool co)-.05 F -.15(ve)-.15 G .853
-(ring the spectrum between).15 F .968(20 MHz and 20 GHz.)108 261.6 R F2
-(SPLA)5.968 E(T!)-.95 E F0 .968(is free softw)3.468 F .968
-(are, and is designed for operation on Unix and Linux-based)-.1 F -.1
-(wo)108 273.6 S 3.171(rkstations. Redistrib).1 F .671(ution and/or modi\
-\214cation is permitted under the terms of the GNU General Public)-.2 F
-.376(License as published by the Free Softw)108 285.6 R .376(are F)-.1 F
-.376(oundation, either v)-.15 F .376(ersion 2 of the License or an)-.15
-F 2.876(yl)-.15 G .376(ater v)-2.876 F(ersion.)-.15 E .349(Adoption of)
-108 297.6 R F2(SPLA)2.849 E(T!)-.95 E F0 .349(source code in proprietar\
-y or closed-source applications is a violation of this license,)2.849 F
-(and is)108 309.6 Q F2(strictly)2.5 E F0(forbidden.)2.5 E F2(SPLA)108
-333.6 Q(T!)-.95 E F0 .53(is distrib)3.03 F .531
-(uted in the hope that it will be useful, b)-.2 F .531(ut WITHOUT ANY W)
--.2 F(ARRANTY)-1.2 E 3.031(,w)-1.29 G .531(ithout e)-3.031 F -.15(ve)
--.25 G(n).15 E .96(the implied w)108 345.6 R .959(arranty of MERCHANT)
--.1 F .959(ABILITY or FITNESS FOR A P)-.93 F(AR)-.92 E .959
-(TICULAR PURPOSE. See the)-.6 F
-(GNU General Public License for more details.)108 357.6 Q F1(INTR)72
-374.4 Q(ODUCTION)-.329 E F0 .574(Applications of)108 386.4 R F2(SPLA)
-3.074 E(T!)-.95 E F0 .574(include the visualization, design, and link b)
-3.074 F .575(udget analysis of wireless W)-.2 F .575(ide Area)-.4 F
-(Netw)108 398.4 Q 1.94(orks \(W)-.1 F 1.939
-(ANs\), commercial and amateur radio communication systems abo)-1.2 F
-2.239 -.15(ve 2)-.15 H 4.439(0M).15 G 1.939(Hz, micro)-4.439 F -.1(wa)
--.25 G -.15(ve)-.1 G .92(links, frequenc)108 410.4 R 3.42(yc)-.15 G .92
-(oordination and interference studies, and the determination of analog \
-and digital terres-)-3.42 F(trial radio and tele)108 422.4 Q
-(vision contour re)-.25 E(gions.)-.15 E F2(SPLA)108 446.4 Q(T!)-.95 E F0
-(pro)4.691 E 2.191(vides RF site engineering data such as great circle \
-distances and bearings between sites,)-.15 F 2.724(antenna ele)108 458.4
-R -.25(va)-.25 G 2.724(tion angles \(uptilt\), depression angles \(do)
-.25 F 2.724(wntilt\), antenna height abo)-.25 F 3.024 -.15(ve m)-.15 H
-2.725(ean sea le).15 F -.15(ve)-.25 G(l,).15 E .22(antenna height abo)
-108 470.4 R .52 -.15(ve a)-.15 H -.15(ve)-.05 G .22
-(rage terrain, bearings and distances to kno).15 F .22
-(wn obstructions, and Longle)-.25 F .22(y-Rice path)-.15 F 2.726
-(attenuation. In)108 482.4 R .226(addition, the minimum antenna height \
-requirements needed to clear terrain, the \214rst Fresnel)2.726 F
-(zone, and 60% of the \214rst Fresnel zone are also pro)108 494.4 Q
-(vided.)-.15 E F2(SPLA)108 518.4 Q(T!)-.95 E F0 .102(produces reports, \
-graphs, and high resolution topographic maps that depict line-of-sight \
-paths, and)2.603 F(re)108 530.4 Q .153
-(gional path loss contours through which e)-.15 F .154(xpected co)-.15 F
--.15(ve)-.15 G .154(rage areas of transmitters and repeater systems can)
-.15 F 1.237(be obtained.)108 542.4 R 1.237(When performing line-of-sigh\
-t analysis in situations where multiple transmitter or repeater)6.237 F
-.368(sites are emplo)108 554.4 R(yed,)-.1 E F2(SPLA)2.868 E(T!)-.95 E F0
-.368(determines indi)2.868 F .369(vidual and mutual areas of co)-.25 F
--.15(ve)-.15 G .369(rage within the netw).15 F .369(ork speci-)-.1 F
-(\214ed.)108 566.4 Q(Simply typing)108 590.4 Q/F4 10/Courier@0 SF(splat)
-2.5 E F0(on the command line will return a summary of)2.5 E F2(SPLA)2.5
-E(T!)-.95 E F0 1.1 -.55('s c)D(ommand line options:).55 E F4
-(--==[ SPLAT! v1.2.0 Available Options... ]==--)198 614.4 Q
-(-t txsite\(s\).qth \(max of 4\))144 638.4 Q(-r rxsite.qth)144 650.4 Q
-(-c plot coverage of TX\(s\) with an RX antenna at X feet/meters AGL)144
-662.4 Q(-L plot path loss map of TX based on an RX at X feet/meters AGL)
-144 674.4 Q
-(-s filename\(s\) of city/site file\(s\) to import \(max of 5\))144
-686.4 Q(-b filename\(s\) of cartographic boundary file\(s\) to import \
-\(5 max\))144 698.4 Q(-p filename of terrain profile graph to plot)144
-710.4 Q(-e filename of terrain elevation graph to plot)144 722.4 Q F0
-(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F(December 2006)2.5 E(1)190.955
-E EP
-%%Page: 2 2
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
-(-h filename of terrain height graph to plot)144 84 Q
-(-H filename of normalized terrain height graph to plot)144 96 Q
-(-l filename of Longley-Rice graph to plot)144 108 Q
-(-o filename of topographic map to generate \(.ppm\))144 120 Q
-(-u filename of user-defined terrain file to import)144 132 Q
-(-d sdf file directory path \(overrides path in ~/.splat_path file\))144
-144 Q(-n no analysis, brief report)144 156 Q(-N no analysis, no report)
-144 168 Q(-m earth radius multiplier)144 180 Q
-(-f frequency for Fresnel zone calculation \(MHz\))144 192 Q
-(-R modify default range for -c or -L \(miles/kilometers\))144 204 Q
-(-db maximum loss contour to display on path loss maps \(80-230 dB\))138
-216 Q(-nf do not plot Fresnel zones in height plots)138 228 Q
-(-plo filename of path-loss output file)132 240 Q
-(-pli filename of path-loss input file)132 252 Q
-(-udt filename of user defined terrain input file)132 264 Q
-(-geo generate a .geo georeference file \(with .ppm output\))132 276 Q
-(-kml generate a Google Earth .kml file \(for point-to-point links\))132
-288 Q(-metric employ metric rather than imperial units for all user I/O)
-114 300 Q/F2 10.95/Times-Bold@0 SF(INPUT FILES)72 328.8 Q/F3 10
-/Times-Bold@0 SF(SPLA)108 340.8 Q(T!)-.95 E F0 .508
-(is a command-line dri)3.008 F -.15(ve)-.25 G 3.008(na).15 G .507
-(pplication, and reads input data through a number of data \214les.)
--3.008 F(Some)5.507 E 1.42(\214les are mandatory for successful e)108
-352.8 R -.15(xe)-.15 G 1.42
-(cution of the program, while others are optional.).15 F 1.42
-(Mandatory \214les)6.42 F 1.085(include 3-arc second topograph)108 364.8
-R 3.585(ym)-.05 G 1.085(odels in the form of SPLA)-3.585 F 3.585(TD)
--1.11 G 1.085(ata Files \(SDF \214les\), site location \214les)-3.585 F
-.394(\(QTH \214les\), and Longle)108 376.8 R .394
-(y-Rice model parameter \214les \(LRP \214les\).)-.15 F .395
-(Optional \214les include city location \214les,)5.394 F 1.324
-(cartographic boundary \214les, user)108 388.8 R 1.323(-de\214ned terra\
-in \214les, path-loss input \214les, and antenna radiation pattern)-.2 F
-(\214les.)108 400.8 Q F2(SPLA)72 417.6 Q 2.738(TD)-1.04 G -1.644 -1.04
-(AT A)-3.121 H(FILES)3.778 E F3(SPLA)108 429.6 Q(T!)-.95 E F0 .43
-(imports topographic data in the form of SPLA)2.93 F 2.93(TD)-1.11 G .43
-(ata Files \(SDFs\).)-2.93 F .43(These \214les may be generated)5.43 F
-.737(from a number of information sources.)108 441.6 R .737
-(In the United States, SPLA)5.737 F 3.237(TD)-1.11 G .737
-(ata Files can be generated through)-3.237 F 5.441(U.S. Geological)108
-453.6 R(Surv)5.441 E 3.241 -.15(ey D)-.15 H 2.941(igital Ele).15 F -.25
-(va)-.25 G 2.942(tion Models \(DEMs\) using the).25 F F3(usgs2sdf)5.442
-E F0 2.942(utility included with)5.442 F F3(SPLA)108 465.6 Q(T!)-.95 E
-F0 8.595(.U)C 3.595(SGS Digital Ele)-8.595 F -.25(va)-.25 G 3.595
-(tion Models compatible with this utility may be do).25 F 3.595
-(wnloaded from:)-.25 F/F4 10/Times-Italic@0 SF(http://edcftp.cr)108
-477.6 Q(.usgs.go)-1.11 E(v/pub/data/DEM/250/)-.1 E F0(.)A .798
-(Signi\214cantly better resolution and accurac)108 501.6 R 3.298(yc)-.15
-G .798(an be obtained through the use of SR)-3.298 F .798(TM-3 V)-.6 F
-.798(ersion 2 digital)-1.11 F(ele)108 513.6 Q -.25(va)-.25 G .66
-(tion models.).25 F .659
-(These models are the product of the STS-99 Space Shuttle Radar T)5.66 F
-(opograph)-.8 E 3.159(yM)-.05 G(ission,)-3.159 E .045(and are a)108
-525.6 R -.25(va)-.2 G .045(ilable for most populated re).25 F .045
-(gions of the Earth.)-.15 F(SPLA)5.045 E 2.545(TD)-1.11 G .046
-(ata Files may be generated from SR)-2.545 F(TM)-.6 E .062
-(data using the included)108 537.6 R F3(srtm2sdf)2.562 E F0(utility)
-2.562 E 5.061(.S)-.65 G -.6(RT)-5.061 G .061(M-3 V).6 F .061
-(ersion 2 data may be obtained through anon)-1.11 F .061(ymous FTP)-.15
-F(from:)108 549.6 Q F4(ftp://e0srp01u.ecs.nasa.go)2.5 E(v:21/srtm/ver)
--.1 E(sion2/)-.1 E F0 .241(Despite the higher accurac)108 573.6 R 2.741
-(yt)-.15 G .241(hat SR)-2.741 F .241(TM data has to of)-.6 F(fer)-.25 E
-2.741(,s)-.4 G .241(ome v)-2.741 F .241(oids in the data sets e)-.2 F
-2.741(xist. When)-.15 F -.2(vo)2.741 G .242(ids are).2 F .332
-(detected, the)108 585.6 R F3(srtm2sdf)2.832 E F0 .332
-(utility replaces them with corresponding data found in e)2.832 F .332
-(xisting SDF \214les \(that were)-.15 F .033
-(presumably created from earlier USGS data through the)108 597.6 R F3
-(usgs2sdf)2.533 E F0 2.533(utility\). If)2.533 F(USGS-deri)2.534 E -.15
-(ve)-.25 G 2.534(dS).15 G .034(DF data is not)-2.534 F -.2(av)108 609.6
-S(ailable, v)-.05 E(oids are handled through adjacent pix)-.2 E(el a)
--.15 E -.15(ve)-.2 G(raging, or direct replacement.).15 E(SPLA)108 633.6
-Q 2.782(TD)-1.11 G .282(ata Files contain inte)-2.782 F .282(ger v)-.15
-F .282(alue topographic ele)-.25 F -.25(va)-.25 G .282
-(tions \(in meters\) referenced to mean sea le).25 F -.15(ve)-.25 G
-2.782(lf).15 G(or)-2.782 E(1-de)108 645.6 Q .061(gree by 1-de)-.15 F
-.061(gree re)-.15 F .061
-(gions of the earth with a resolution of 3-arc seconds.)-.15 F .062
-(SDF \214les can be read in either)5.062 F .712(standard format \()108
-657.6 R F4(.sdf)A F0 3.212(\)a)C 3.212(sg)-3.212 G .712(enerated by the)
--3.212 F F3(usgs2sdf)3.211 E F0(and)3.211 E F3(srtm2sdf)3.211 E F0 .711
-(utilities, or in bzip2 compressed format)3.211 F(\()108 669.6 Q F4
-(.sdf)A(.bz2)-.15 E F0 3.067(\). Since)B .568
-(uncompressed \214les can be processed slightly f)3.067 F .568
-(aster than \214les that ha)-.1 F .868 -.15(ve b)-.2 H .568
-(een compressed,).15 F F3(SPLA)108 681.6 Q(T!)-.95 E F0 1.764
-(searches for needed SDF data in uncompressed format \214rst.)4.265 F
-1.764(If uncompressed data cannot be)6.764 F(located,)108 693.6 Q F3
-(SPLA)3.47 E(T!)-.95 E F0 .97
-(then searches for data in bzip2 compressed format.)3.47 F .971
-(If no compressed SDF \214les can be)5.971 F .779(found for the re)108
-705.6 R .779(gion requested,)-.15 F F3(SPLA)3.278 E(T!)-.95 E F0 .778
-(assumes the re)3.278 F .778(gion is o)-.15 F -.15(ve)-.15 G 3.278(rw)
-.15 G(ater)-3.378 E 3.278(,a)-.4 G .778(nd will assign an ele)-3.278 F
--.25(va)-.25 G .778(tion of).25 F(sea-le)108 717.6 Q -.15(ve)-.25 G 2.5
-(lt).15 G 2.5(ot)-2.5 G(hese areas.)-2.5 E(KD2BD Softw)72 768 Q 121.625
-(are 20)-.1 F(December 2006)2.5 E(2)190.955 E EP
-%%Page: 3 3
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E 1.061
-(This feature of)108 84 R/F1 10/Times-Bold@0 SF(SPLA)3.561 E(T!)-.95 E
-F0(mak)3.561 E 1.061(es it possible to perform path analysis not only o)
--.1 F -.15(ve)-.15 G 3.561(rl).15 G 1.062(and, b)-3.561 F 1.062
-(ut also between)-.2 F .555
-(coastal areas not represented by Digital Ele)108 96 R -.25(va)-.25 G
-.554(tion Model data.).25 F(Ho)5.554 E(we)-.25 E -.15(ve)-.25 G 1.354
--.4(r, t).15 H .554(his beha).4 F .554(vior of)-.2 F F1(SPLA)3.054 E(T!)
--.95 E F0(under)5.554 E(-)-.2 E 1.575(scores the importance of ha)108
-108 R 1.575(ving all the SDF \214les required for the re)-.2 F 1.575
-(gion being analyzed if meaningful)-.15 F(results are to be e)108 120 Q
-(xpected.)-.15 E/F2 10.95/Times-Bold@0 SF(SITE LOCA)72 136.8 Q
-(TION \(QTH\) FILES)-1.04 E F1(SPLA)108 148.8 Q(T!)-.95 E F0 .839
-(imports site location information of transmitter and recei)3.339 F -.15
-(ve)-.25 G 3.338(rs).15 G .838(ites analyzed by the program from)-3.338
-F .375(ASCII \214les ha)108 160.8 R .375(ving a)-.2 F/F3 10
-/Times-Italic@0 SF(.qth)2.875 E F0 -.15(ex)2.875 G 2.875(tension. QTH)
-.15 F .375(\214les contain the site')2.875 F 2.875(sn)-.55 G .375
-(ame, the site')-2.875 F 2.876(sl)-.55 G .376(atitude \(positi)-2.876 F
-.676 -.15(ve i)-.25 H 2.876(fN).15 G(orth)-2.876 E 1.127(of the equator)
-108 172.8 R 3.626(,n)-.4 G -2.25 -.15(eg a)-3.626 H(ti).15 E 1.426 -.15
-(ve i)-.25 H 3.626(fS).15 G 1.126(outh\), the site')-3.626 F 3.626(sl)
--.55 G 1.126(ongitude \(in de)-3.626 F 1.126(grees W)-.15 F 1.126
-(est, 0 to 360 de)-.8 F 1.126(grees\), and the site')-.15 F(s)-.55 E
-1.639(antenna height abo)108 184.8 R 1.939 -.15(ve g)-.15 H 1.639
-(round le).15 F -.15(ve)-.25 G 4.139(l\().15 G -.4(AG)-4.139 G 1.639
-(L\), each separated by a single line-feed character).4 F 6.64(.T)-.55 G
-1.64(he antenna)-6.64 F .459
-(height is assumed to be speci\214ed in feet unless follo)108 196.8 R
-.459(wed by the letter)-.25 F F3(m)2.959 E F0 .459(or the w)2.959 F(ord)
--.1 E F3(meter)2.959 E(s)-.1 E F0 .459(in either upper)2.959 F .424
-(or lo)108 208.8 R .424(wer case.)-.25 F .425
-(Latitude and longitude information may be e)5.424 F .425
-(xpressed in either decimal format \(74.6889\) or)-.15 F(de)108 220.8 Q
-(gree, minute, second \(DMS\) format \(74 41 20.0\).)-.15 E -.15(Fo)108
-244.8 S 3.356(re).15 G .856
-(xample, a site location \214le describing tele)-3.506 F .856
-(vision station WNJT)-.25 F 3.356(,T)-.74 G .856(renton, NJ \()-3.706 F
-F3(wnjt.qth)A F0 3.356(\)m)C .856(ight read as)-3.356 F(follo)108 256.8
-Q(ws:)-.25 E/F4 10/Courier@0 SF(WNJT)156 280.8 Q(40.2833)156 292.8 Q
-(74.6889)156 304.8 Q(990.00)156 316.8 Q F0 .23
-(Each transmitter and recei)108 340.8 R -.15(ve)-.25 G 2.73(rs).15 G .23
-(ite analyzed by)-2.73 F F1(SPLA)2.73 E(T!)-.95 E F0 .23
-(must be represented by its o)2.73 F .23(wn site location \(QTH\))-.25 F
-(\214le.)108 352.8 Q F2(LONGLEY)72 369.6 Q(-RICE P)-1.007 E
-(ARAMETER \(LRP\) FILES)-.81 E F0(Longle)108 381.6 Q 1.082
-(y-Rice parameter data \214les are required for)-.15 F F1(SPLA)3.581 E
-(T!)-.95 E F0 1.081(to determine RF path loss in either point-to-)3.581
-F .291(point or area prediction mode.)108 393.6 R(Longle)5.291 E .291
-(y-Rice model parameter data is read from \214les ha)-.15 F .292
-(ving the same base)-.2 F(name as the transmitter site QTH \214le, b)108
-405.6 Q(ut with a format \()-.2 E F3(wnjt.lrp)A F0(\):)A F4 6(15.000 ;)
-156 429.6 R(Earth Dielectric Constant \(Relative permittivity\))6 E 12
-(0.005 ;)156 441.6 R(Earth Conductivity \(Siemens per meter\))6 E
-(301.000 ; Atmospheric Bending Constant \(N-units\))156 453.6 Q
-(700.000 ; Frequency in MHz \(20 MHz to 20 GHz\))156 465.6 Q 42(5;)156
-477.6 S(Radio Climate \(5 = Continental Temperate\))-36 E 42(0;)156
-489.6 S(Polarization \(0 = Horizontal, 1 = Vertical\))-36 E 24(0.5 ;)156
-501.6 R(Fraction of situations \(50% of locations\))6 E 24(0.5 ;)156
-513.6 R(Fraction of time \(50% of the time\))6 E F0 .771(If an LRP \214\
-le corresponding to the tx_site QTH \214le cannot be found,)108 537.6 R
-F1(SPLA)3.27 E(T!)-.95 E F0 .77(scans the current w)3.27 F(orking)-.1 E
-.085(directory for the \214le "splat.lrp".)108 549.6 R .085
-(If this \214le cannot be found, then the def)5.085 F .085
-(ault parameters listed abo)-.1 F .385 -.15(ve w)-.15 H .085(ill be).15
-F .528(assigned by)108 561.6 R F1(SPLA)3.028 E(T!)-.95 E F0 .527(and a \
-corresponding "splat.lrp" \214le containing this data will be written t\
-o the current)3.028 F -.1(wo)108 573.6 S(rking directory).1 E 5(.")-.65
-G(splat.lrp" can then be edited by the user as needed.)-5 E -.8(Ty)108
-597.6 S(pical Earth dielectric constants and conducti).8 E(vity v)-.25 E
-(alues are as follo)-.25 E(ws:)-.25 E F4(Dielectric Constant)270 621.6 Q
-(Conductivity)12 E(Salt water)156 633.6 Q 48(:8)42 G 96(05)-48 G(.000)
--96 E(Good ground)156 645.6 Q 48(:2)36 G 96(50)-48 G(.020)-96 E
-(Fresh water)156 657.6 Q 48(:8)36 G 96(00)-48 G(.010)-96 E(Marshy land)
-156 669.6 Q 48(:1)36 G 96(20)-48 G(.007)-96 E(Farmland, forest :)156
-681.6 Q 90(15 0.005)48 F(Average ground)156 693.6 Q 48(:1)18 G 96(50)-48
-G(.005)-96 E(Mountain, sand)156 705.6 Q 48(:1)18 G 96(30)-48 G(.002)-96
-E 72(City :)156 717.6 R 96(50)54 G(.001)-96 E(Poor ground)156 729.6 Q
--18 54(:4 0)36 H(.001)-54 E F0(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F
-(December 2006)2.5 E(3)190.955 E EP
-%%Page: 4 4
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E
-(Radio climate codes used by)108 84 Q/F1 10/Times-Bold@0 SF(SPLA)2.5 E
-(T!)-.95 E F0(are as follo)2.5 E(ws:)-.25 E/F2 10/Courier@0 SF
-(1: Equatorial \(Congo\))156 108 Q(2: Continental Subtropical \(Sudan\))
-156 120 Q(3: Maritime Subtropical \(West coast of Africa\))156 132 Q
-(4: Desert \(Sahara\))156 144 Q(5: Continental Temperate)156 156 Q
-(6: Maritime Temperate, over land \(UK and west coasts of US & EU\))156
-168 Q(7: Maritime Temperate, over sea)156 180 Q F0 1.487
-(The Continental T)108 204 R 1.486(emperate climate is common to lar)-.7
-F 1.486(ge land masses in the temperate zone, such as the)-.18 F .756
-(United States.)108 216 R -.15(Fo)5.756 G 3.256(rp).15 G .756
-(aths shorter than 100 km, there is little dif)-3.256 F .756
-(ference between Continental and Maritime)-.25 F -.7(Te)108 228 S
-(mperate climates.).7 E .379(The \214nal tw)108 252 R 2.879(op)-.1 G
-.379(arameters in the)-2.879 F/F3 10/Times-Italic@0 SF(.lrp)2.879 E F0
-.379(\214le correspond to the statistical analysis pro)2.879 F .378
-(vided by the Longle)-.15 F(y-Rice)-.15 E 2.537(model. In)108 264 R .037
-(this e)2.537 F(xample,)-.15 E F1(SPLA)2.537 E(T!)-.95 E F0 .038(will r\
-eturn the maximum path loss occurring 50% of the time \(fraction of)
-5.037 F .346(time\) in 50% of situations \(fraction of situations\).)108
-276 R .346(In the United States, use a fraction of time parameter of)
-5.346 F(0.97 for digital tele)108 288 Q(vision \(8VSB modulation\), or \
-0.50 for analog \(VSB-AM+NTSC\) transmissions.)-.25 E -.15(Fo)108 312 S
-2.782(rf).15 G .282(urther information on these parameters, see:)-2.782
-F F3(http://\215attop.its.bldr)2.782 E(doc.go)-.37 E(v/itm.html)-.1 E F0
-(and)2.783 E F3(http://www)2.783 E(.soft-)-.74 E
-(wright.com/faq/engineering/pr)108 324 Q(op_longle)-.45 E(y_rice)-.3 E
-(.html)-.15 E/F4 10.95/Times-Bold@0 SF(CITY LOCA)72 340.8 Q(TION FILES)
--1.04 E F0 .807(The names and locations of cities, to)108 352.8 R .807
-(wer sites, or other points of interest may be imported and plotted on)
--.25 F .797(topographic maps generated by)108 364.8 R F1(SPLA)3.297 E
-(T!)-.95 E F0(.)A F1(SPLA)5.797 E(T!)-.95 E F0 .797
-(imports the names of cities and locations from ASCII)3.297 F .111
-(\214les containing the location of interest')108 376.8 R 2.611(sn)-.55
-G .111(ame, latitude, and longitude.)-2.611 F .11
-(Each \214eld is separated by a comma.)5.111 F .949
-(Each record is separated by a single line feed character)108 388.8 R
-5.949(.A)-.55 G 3.449(sw)-5.949 G .949(as the case with the)-3.549 F F3
-(.qth)3.449 E F0 .949(\214les, latitude and)3.449 F
-(longitude information may be entered in either decimal or de)108 400.8
-Q(gree, minute, second \(DMS\) format.)-.15 E -.15(Fo)108 424.8 S 2.5
-(re).15 G(xample \()-2.65 E F3(cities.dat)A F0(\):)A F2
-(Teaneck, 40.891973, 74.014506)156 448.8 Q
-(Tenafly, 40.919212, 73.955892)156 460.8 Q
-(Teterboro, 40.859511, 74.058908)156 472.8 Q
-(Tinton Falls, 40.279966, 74.093924)156 484.8 Q
-(Toms River, 39.977777, 74.183580)156 496.8 Q
-(Totowa, 40.906160, 74.223310)156 508.8 Q(Trenton, 40.219922, 74.754665)
-156 520.8 Q F0 3.2(At)108 544.8 S .7(otal of \214v)-3.2 F 3.2(es)-.15 G
-.699(eparate city data \214les may be imported at a time, and there is \
-no limit to the size of these)-3.2 F(\214les.)108 556.8 Q F1(SPLA)6.369
-E(T!)-.95 E F0 1.369(reads city data on a "\214rst come/\214rst serv)
-3.869 F 1.37(ed" basis, and plots only those locations whose)-.15 F .113
-(annotations do not con\215ict with annotations of locations read earli\
-er in the current city data \214le, or in pre)108 568.8 R(vi-)-.25 E
-.539(ous \214les.)108 580.8 R .539(This beha)5.539 F .539
-(vior minimizes clutter in)-.2 F F1(SPLA)3.039 E(T!)-.95 E F0 .539
-(generated topographic maps, b)3.039 F .54(ut also mandates that)-.2 F
-.15(important locations be placed to)108 592.8 R -.1(wa)-.25 G .15
-(rd the be).1 F .149(ginning of the \214rst city data \214le, and locat\
-ions less important be)-.15 F(positioned further do)108 604.8 Q
-(wn the list or in subsequent data \214les.)-.25 E .996
-(City data \214les may be generated manually using an)108 628.8 R 3.496
-(yt)-.15 G -.15(ex)-3.496 G 3.496(te).15 G(ditor)-3.496 E 3.496(,i)-.4 G
-.997(mported from other sources, or deri)-3.496 F -.15(ve)-.25 G(d).15 E
-1.535(from data a)108 640.8 R -.25(va)-.2 G 1.535
-(ilable from the U.S. Census Bureau using the).25 F F1(citydecoder)4.035
-E F0 1.535(utility included with)4.035 F F1(SPLA)4.035 E(T!)-.95 E F0(.)
-A .152(Such data is a)108 652.8 R -.25(va)-.2 G .153
-(ilable free of char).25 F .153(ge via the Internet at:)-.18 F F3
-(http://www)2.653 E(.census.go)-.74 E(v/g)-.1 E
-(eo/www/cob/bdy_\214les.html)-.1 E F0(,)A(and must be in ASCII format.)
-108 664.8 Q F4(CAR)72 681.6 Q -.197(TO)-.438 G(GRAPHIC BOUND).197 E(AR)
--.383 E 2.738(YD)-.383 G -1.644 -1.04(AT A)-3.121 H(FILES)3.778 E F0
-1.17(Cartographic boundary data may also be imported to plot the bounda\
-ries of cities, counties, or states on)108 693.6 R .071
-(topographic maps generated by)108 705.6 R F1(SPLA)2.571 E(T!)-.95 E F0
-5.071(.S)C .071
-(uch data must be of the form of ARC/INFO Ungenerate \(ASCII)-5.071 F
--.15(Fo)108 717.6 S 1.262
-(rmat\) Metadata Cartographic Boundary Files, and are a).15 F -.25(va)
--.2 G 1.262(ilable from the U.S.).25 F 1.262(Census Bureau via the)6.262
-F 48.573(Internet at:)108 729.6 R F3(http://www)51.073 E(.census.go)-.74
-E(v/g)-.1 E(eo/www/cob/co2000.html#ascii)-.1 E F0(and)51.074 E
-(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F(December 2006)2.5 E(4)190.955
-E EP
-%%Page: 5 5
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Times-Italic@0
-SF(http://www)108 84 Q(.census.go)-.74 E(v/g)-.1 E
-(eo/www/cob/pl2000.html#ascii)-.1 E F0 5.008(.A)C .008(total of \214v)
--2.5 F 2.507(es)-.15 G .007(eparate cartographic boundary \214les)-2.507
-F .196(may be imported at a time.)108 96 R .196
-(It is not necessary to import state boundaries if county boundaries ha)
-5.196 F .497 -.15(ve a)-.2 H(lready).15 E(been imported.)108 108 Q/F2
-10.95/Times-Bold@0 SF(PR)72 124.8 Q(OGRAM OPERA)-.329 E(TION)-1.04 E/F3
-10/Times-Bold@0 SF(SPLA)108 136.8 Q(T!)-.95 E F0 1.03(is in)3.53 F -.2
-(vo)-.4 G -.1(ke).2 G 3.53(dv).1 G 1.03
-(ia the command-line using a series of switches and ar)-3.53 F 3.53
-(guments. Since)-.18 F F3(SPLA)3.53 E(T!)-.95 E F0 1.03(is a)3.53 F .745
-(CPU and memory intensi)108 148.8 R 1.045 -.15(ve a)-.25 H .745
-(pplication, this type of interf).15 F .745(ace minimizes o)-.1 F -.15
-(ve)-.15 G .746(rhead and lends itself well to).15 F .422
-(scripted \(batch\) operations.)108 160.8 R F3(SPLA)5.422 E(T!)-.95 E F0
-1.522 -.55('s C)D .421
-(PU and memory scheduling priority may be modi\214ed through the).55 F
-(use of the Unix)108 172.8 Q F3(nice)2.5 E F0(command.)2.5 E .225
-(The number and type of switches passed to)108 196.8 R F3(SPLA)2.725 E
-(T!)-.95 E F0 .226(determine its mode of operation and method of output)
-2.725 F .008(data generation.)108 208.8 R .008(Nearly all of)5.008 F F3
-(SPLA)2.508 E(T!)-.95 E F0 1.108 -.55('s s)D .008
-(witches may be cascaded in an).55 F 2.507(yo)-.15 G .007
-(rder on the command line when)-2.507 F(in)108 220.8 Q -.2(vo)-.4 G
-(king the program.).2 E F3(SPLA)108 244.8 Q(T!)-.95 E F0 .69
-(operates in tw)3.19 F 3.19(od)-.1 G .69(istinct modes:)-3.19 F F1 .69
-(point-to-point mode)3.19 F F0 3.19(,a)C(nd)-3.19 E F1(ar)3.19 E .69
-(ea pr)-.37 F .69(ediction mode)-.37 F F0 5.69(.E)C .69
-(ither a line-of-)-5.69 F .335(sight \(LOS\) or Longle)108 256.8 R .335
-(y-Rice Irre)-.15 F .335(gular T)-.15 F .335(errain \(ITM\) propag)-.7 F
-.335(ation model may be in)-.05 F -.2(vo)-.4 G -.1(ke).2 G 2.834(db).1 G
-2.834(yt)-2.834 G .334(he user)-2.834 F 5.334(.T)-.55 G(rue)-5.684 E
-.625(Earth, four)108 268.8 R .625(-thirds Earth, or an)-.2 F 3.126(yo)
--.15 G .626(ther user)-3.126 F .626
-(-de\214ned Earth radius may be speci\214ed when performing line-of-)-.2
-F(sight analysis.)108 280.8 Q F2(POINT)72 297.6 Q(-T)-1.007 E
-(O-POINT AN)-.197 E(AL)-.219 E(YSIS)-1.007 E F3(SPLA)108 309.6 Q(T!)-.95
-E F0 1.224
-(may be used to perform line-of-sight terrain analysis between tw)3.725
-F 3.724(os)-.1 G 1.224(peci\214ed site locations.)-3.724 F -.15(Fo)6.224
-G(r).15 E -.15(ex)108 321.6 S(ample:).15 E/F4 10/Courier@0 SF
-(splat -t tx_site.qth -r rx_site.qth)108 345.6 Q F0(in)108 369.6 Q -.2
-(vo)-.4 G -.1(ke).2 G 2.627(sal).1 G .128
-(ine-of-sight terrain analysis between the transmitter speci\214ed in)
--2.627 F F1(tx_site)2.628 E(.qth)-.15 E F0 .128(and recei)2.628 F -.15
-(ve)-.25 G 2.628(rs).15 G(peci\214ed)-2.628 E(in)108 381.6 Q F1(rx_site)
-3.934 E(.qth)-.15 E F0 1.434(using a T)3.934 F 1.434
-(rue Earth radius model, and writes a)-.35 F F3(SPLA)3.934 E(T!)-.95 E
-F0 1.433(Obstruction Report to the current)3.934 F -.1(wo)108 393.6 S
-.548(rking directory).1 F 5.548(.T)-.65 G .549
-(he report contains details of the transmitter and recei)-5.548 F -.15
-(ve)-.25 G 3.049(rs).15 G .549(ites, and identi\214es the loca-)-3.049 F
-.017(tion of an)108 405.6 R 2.517(yo)-.15 G .017
-(bstructions detected along the line-of-sight path.)-2.517 F .016
-(If an obstruction can be cleared by raising the)5.016 F(recei)108 417.6
-Q .496 -.15(ve a)-.25 H .197(ntenna to a greater altitude,).15 F F3
-(SPLA)2.697 E(T!)-.95 E F0 .197
-(will indicate the minimum antenna height required for a line-)2.697 F
-1.655(of-sight path to e)108 429.6 R 1.654
-(xist between the transmitter and recei)-.15 F -.15(ve)-.25 G 4.154(rl)
-.15 G 1.654(ocations speci\214ed.)-4.154 F 1.654
-(Note that imperial units)6.654 F
-(\(miles, feet\) are speci\214ed unless the)108 441.6 Q F1(-metric)2.5 E
-F0(switch is added to)2.5 E F3(SPLA)2.5 E(T!)-.95 E F0 1.1 -.55('s c)D
-(ommand line options:).55 E F4
-(splat -t tx_site.qth -r rx_site.qth -metric)108 465.6 Q F0 .533(If the\
- antenna must be raised a signi\214cant amount, this determination may \
-tak)108 489.6 R 3.034(eaf)-.1 G 1.034 -.25(ew m)-3.034 H 3.034
-(oments. Note).25 F(that)3.034 E .33(the results pro)108 501.6 R .33
-(vided are the)-.15 F F1(minimum)2.83 E F0 .33
-(necessary for a line-of-sight path to e)2.83 F .329
-(xist, and in the case of this sim-)-.15 F(ple e)108 513.6 Q
-(xample, do not tak)-.15 E 2.5(eF)-.1 G
-(resnel zone clearance requirements into consideration.)-2.5 E F1(qth)
-108 537.6 Q F0 -.15(ex)2.533 G .033(tensions are assumed by).15 F F3
-(SPLA)2.533 E(T!)-.95 E F0 .034
-(for QTH \214les, and are optional when specifying -t and -r ar)2.533 F
-(guments)-.18 E .533(on the command-line.)108 549.6 R F3(SPLA)5.532 E
-(T!)-.95 E F0 .532(automatically reads all SPLA)3.032 F 3.032(TD)-1.11 G
-.532(ata Files necessary to conduct the terrain)-3.032 F .911
-(analysis between the sites speci\214ed.)108 561.6 R F3(SPLA)5.911 E(T!)
--.95 E F0 .912(searches for the required SDF \214les in the current w)
-5.911 F(orking)-.1 E .189(directory \214rst.)108 573.6 R .189
-(If the needed \214les are not found,)5.189 F F3(SPLA)2.688 E(T!)-.95 E
-F0 .188(then searches in the path speci\214ed by the)2.688 F F1(-d)2.688
-E F0(com-)2.688 E(mand-line switch:)108 585.6 Q F4
-(splat -t tx_site -r rx_site -d /cdrom/sdf/)108 609.6 Q F0 .329(An e)108
-633.6 R .329(xternal directory path may be speci\214ed by placing a ".s\
-plat_path" \214le under the user')-.15 F 2.83(sh)-.55 G .33
-(ome directory)-2.83 F(.)-.65 E 3.045(This \214le must contain the full\
- directory path of last resort to all the SDF \214les.)108 645.6 R 3.044
-(The path in the)8.044 F F1($HOME/.splat_path)108 657.6 Q F0
-(\214le must be of the form of a single line of ASCII te)2.5 E(xt:)-.15
-E F4(/opt/splat/sdf/)108 681.6 Q F0(and can be generated using an)108
-705.6 Q 2.5(yt)-.15 G -.15(ex)-2.5 G 2.5(te).15 G(ditor)-2.5 E(.)-.55 E
-3.022(Ag)108 729.6 S .523
-(raph of the terrain pro\214le between the recei)-3.022 F -.15(ve)-.25 G
-3.023(ra).15 G .523
-(nd transmitter locations as a function of distance from)-3.023 F
-(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F(December 2006)2.5 E(5)190.955
-E EP
-%%Page: 6 6
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E(the recei)108 84 Q
--.15(ve)-.25 G 2.5(rc).15 G(an be generated by adding the)-2.5 E/F1 10
-/Times-Italic@0 SF(-p)2.5 E F0(switch:)2.5 E/F2 10/Courier@0 SF
-(splat -t tx_site -r rx_site -p terrain_profile.png)108 108 Q/F3 10
-/Times-Bold@0 SF(SPLA)108 132 Q(T!)-.95 E F0(in)4.12 E -.2(vo)-.4 G -.1
-(ke).2 G(s).1 E F3(gnuplot)4.12 E F0 1.619(when generating graphs.)4.119
-F 1.619(The \214lename e)6.619 F 1.619(xtension speci\214ed to)-.15 F F3
-(SPLA)4.119 E(T!)-.95 E F0(deter)4.119 E(-)-.2 E .346
-(mines the format of the graph produced.)108 144 R F1(.png)5.346 E F0
-.346(will produce a 640x480 color PNG graphic \214le, while)2.846 F F1
-(.ps)2.847 E F0(or)2.847 E F1(.postscript)108 156 Q F0 .151
-(will produce postscript output.)2.651 F .151
-(Output in formats such as GIF)5.151 F 2.65(,A)-.8 G .15
-(dobe Illustrator)-2.65 F 2.65(,A)-.4 G .15(utoCAD dxf,)-2.65 F(LaT)108
-168 Q .159(eX, and man)-.7 F 2.659(yo)-.15 G .159(thers are a)-2.659 F
--.25(va)-.2 G 2.659(ilable. Please).25 F(consult)2.659 E F3(gnuplot)
-2.659 E F0 2.659(,a)C(nd)-2.659 E F3(gnuplot)2.659 E F0 1.26 -.55('s d)D
-.16(ocumentation for details on).55 F(all the supported output formats.)
-108 180 Q 3.543(Ag)108 204 S 1.043(raph of ele)-3.543 F -.25(va)-.25 G
-1.042(tions subtended by the terrain between the recei).25 F -.15(ve)
--.25 G 3.542(ra).15 G 1.042(nd transmitter as a function of dis-)-3.542
-F(tance from the recei)108 216 Q -.15(ve)-.25 G 2.5(rc).15 G
-(an be generated by using the)-2.5 E F1(-e)2.5 E F0(switch:)2.5 E F2
-(splat -t tx_site -r rx_site -e elevation_profile.png)108 240 Q F0 .424
-(The graph produced using this switch illustrates the ele)108 264 R -.25
-(va)-.25 G .425(tion and depression angles resulting from the ter).25 F
-(-)-.2 E .554(rain between the recei)108 276 R -.15(ve)-.25 G(r').15 E
-3.054(sl)-.55 G .553
-(ocation and the transmitter site from the perspecti)-3.054 F .853 -.15
-(ve o)-.25 H 3.053(ft).15 G .553(he recei)-3.053 F -.15(ve)-.25 G(r').15
-E 3.053(sl)-.55 G(ocation.)-3.053 E 3.78(As)108 288 S 1.28
-(econd trace is plotted between the left side of the graph \(recei)-3.78
-F -.15(ve)-.25 G(r').15 E 3.781(sl)-.55 G 1.281
-(ocation\) and the location of the)-3.781 F .449
-(transmitting antenna on the right.)108 300 R .449
-(This trace illustrates the ele)5.449 F -.25(va)-.25 G .448
-(tion angle required for a line-of-sight path).25 F 1.073(to e)108 312 R
-1.073(xist between the recei)-.15 F -.15(ve)-.25 G 3.574(ra).15 G 1.074
-(nd transmitter locations.)-3.574 F 1.074
-(If the trace intersects the ele)6.074 F -.25(va)-.25 G 1.074
-(tion pro\214le at an).25 F(y)-.15 E 1.031(point on the graph, then thi\
-s is an indication that a line-of-sight path does not e)108 324 R 1.031
-(xist under the conditions)-.15 F(gi)108 336 Q -.15(ve)-.25 G(n, and th\
-e obstructions can be clearly identi\214ed on the graph at the point\(s\
-\) of intersection.).15 E 3.67(Ag)108 360 S 1.171(raph illustrating ter\
-rain height referenced to a line-of-sight path between the transmitter \
-and recei)-3.67 F -.15(ve)-.25 G(r).15 E(may be generated using the)108
-372 Q F1(-h)2.5 E F0(switch:)2.5 E F2
-(splat -t tx_site -r rx_site -h height_profile.png)108 396 Q F0 3.245
-(At)108 420 S .745
-(errain height plot normalized to the transmitter and recei)-3.245 F
--.15(ve)-.25 G 3.245(ra).15 G .745
-(ntenna heights can be obtained using the)-3.245 F F1(-H)108 432 Q F0
-(switch:)2.5 E F2
-(splat -t tx_site -r rx_site -H normalized_height_profile.png)108 456 Q
-F0 2.5(Ac)108 480 S(ontour of the Earth')-2.5 E 2.5(sc)-.55 G(urv)-2.5 E
-(ature is also plotted in this mode.)-.25 E .635(The \214rst Fresnel Zo\
-ne, and 60% of the \214rst Fresnel Zone can be added to height pro\214l\
-e graphs by adding)108 504 R(the)108 516 Q F1(-f)2.5 E F0
-(switch, and specifying a frequenc)2.5 E 2.5(y\()-.15 G
-(in MHz\) at which the Fresnel Zone should be modeled:)-2.5 E F2(splat \
--t tx_site -r rx_site -f 439.250 -H normalized_height_profile.png)108
-540 Q F0 2.5(Ag)108 564 S(raph sho)-2.5 E(wing Longle)-.25 E
-(y-Rice path loss may be plotted using the)-.15 E F1(-l)2.5 E F0
-(switch:)2.5 E F2(splat -t tx_site -r rx_site -l path_loss_profile.png)
-108 588 Q F0(As before, adding the)108 612 Q F1(-metric)2.5 E F0
-(switch forces the graphs to be plotted using metric units of measure.)
-2.5 E .886(When performing path loss pro\214les, a Longle)108 636 R .886
-(y-Rice Model P)-.15 F .886(ath Loss Report is generated by)-.15 F F3
-(SPLA)3.386 E(T!)-.95 E F0(in)3.386 E .754(the form of a te)108 648 R
-.754(xt \214le with a)-.15 F F1(.lr)3.254 E(o)-.45 E F0 .754
-(\214lename e)3.254 F 3.254(xtension. The)-.15 F .754
-(report contains bearings and distances between)3.254 F .536
-(the transmitter and recei)108 660 R -.15(ve)-.25 G 1.336 -.4(r, a).15 H
-3.036(sw).4 G .536(ell as the Longle)-3.036 F .536
-(y-Rice path loss for v)-.15 F .535(arious distances between the trans-)
--.25 F .095(mitter and recei)108 672 R -.15(ve)-.25 G 2.595(rl).15 G
-2.595(ocations. The)-2.595 F .095(mode of propag)2.595 F .096
-(ation for points along the path are gi)-.05 F -.15(ve)-.25 G 2.596(na)
-.15 G(s)-2.596 E F1(Line-of-Sight)2.596 E F0(,)A F1(Single Horizon)108
-684 Q F0(,)A F1(Double Horizon)2.5 E F0(,)A F1(Dif)2.5 E(fr)-.18 E
-(action Dominant)-.15 E F0 2.5(,a)C(nd)-2.5 E F1 -1.85 -.55(Tr o)2.5 H
-(poscatter Dominant).55 E F0(.)A 2.36 -.8(To d)108 708 T .76(etermine t\
-he signal-to-noise \(SNR\) ratio at remote location where random Johnso\
-n \(thermal\) noise is).8 F(the primary limiting f)108 720 Q
-(actor in reception:)-.1 E(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F
-(December 2006)2.5 E(6)190.955 E EP
-%%Page: 7 7
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Times-Italic@0
-SF(SNR)108.33 84 Q/F2 10/Symbol SF(=)3.07 E F1(T)2.71 E F2(-)3.47 E F1
-(NJ)2.9 E F2(-)3.17 E F1(L)2.78 E F2(+)2.73 E F1(G)2.18 E F2(-)2.7 E F1
-(NF)2.9 E F0(where)108 108 Q/F3 10/Times-Bold@0 SF(T)2.714 E F0 .215
-(is the ERP of the transmitter in dBW in the direction of the recei)
-2.714 F -.15(ve)-.25 G -.4(r,).15 G F3(NJ)3.115 E F0 .215
-(is Johnson Noise in dBW)2.715 F .725(\(-136 dBW for a 6 MHz tele)108
-120 R .725(vision channel\),)-.25 F F3(L)3.225 E F0 .725
-(is the path loss pro)3.225 F .725(vided by)-.15 F F3(SPLA)3.225 E(T!)
--.95 E F0 .725(in dB \(as a)5.725 F F1(positive)3.225 E F0(number\),)108
-132 Q F3(G)2.5 E F0(is the recei)2.5 E .3 -.15(ve a)-.25 H(ntenna g).15
-E(ain in dB o)-.05 E -.15(ve)-.15 G 2.5(ri).15 G(sotropic, and)-2.5 E F3
-(NF)2.5 E F0(is the recei)2.5 E -.15(ve)-.25 G 2.5(rn).15 G
-(oise \214gure in dB.)-2.5 E F3(T)108 156 Q F0(may be computed as follo)
-2.5 E(ws:)-.25 E F1(T)107.91 180 Q F2(=)4.07 E F1(TI)2.71 E F2(+)3.21 E
-F1(GT)2.18 E F0(where)108 204 Q F3(TI)3.055 E F0 .555
-(is actual amount of RF po)3.055 F .555(wer deli)-.25 F -.15(ve)-.25 G
-.555(red to the transmitting antenna in dBW).15 F(,)-.92 E F3(GT)3.055 E
-F0 .555(is the transmit-)3.055 F .67(ting antenna g)108 216 R .67
-(ain \(o)-.05 F -.15(ve)-.15 G 3.17(ri).15 G .67
-(sotropic\) in the direction of the recei)-3.17 F -.15(ve)-.25 G 3.169
-(r\().15 G .669(or the horizon if the recei)-3.169 F -.15(ve)-.25 G
-3.169(ri).15 G 3.169(so)-3.169 G -.15(ve)-3.319 G 3.169(rt).15 G(he)
--3.169 E(horizon\).)108 228 Q 1.801 -.8(To c)108 252 T .201(ompute ho).8
-F 2.701(wm)-.25 G .202(uch more signal is a)-2.701 F -.25(va)-.2 G .202
-(ilable o).25 F -.15(ve)-.15 G 2.702(rt).15 G .202
-(he minimum to necessary to achie)-2.702 F .502 -.15(ve a s)-.25 H .202
-(peci\214c signal-).15 F(to-noise ratio:)108 264 Q F1(Signal)108.33 288
-Q F0(_).51 E F1(Margin).68 E F2(=)3.04 E F1(SNR)3.13 E F2(-)2.47 E F1(S)
-2.53 E F0(where)108 312 Q F3(S)3.487 E F0 .987
-(is the minimum required SNR ratio \(15.5 dB for A)3.487 F .987
-(TSC \(8-VSB\) DTV)-1.11 F 3.486(,4)-1.29 G 3.486(2d)-3.486 G 3.486(Bf)
--3.486 G .986(or analog NTSC)-3.486 F(tele)108 324 Q(vision\).)-.25 E
-2.61(At)108 348 S .11(opographic map may be generated by)-2.61 F F3
-(SPLA)2.611 E(T!)-.95 E F0 .111
-(to visualize the path between the transmitter and recei)2.611 F -.15
-(ve)-.25 G(r).15 E .099(sites from yet another perspecti)108 360 R -.15
-(ve)-.25 G 5.099(.T).15 G .099(opographic maps generated by)-5.899 F F3
-(SPLA)2.598 E(T!)-.95 E F0 .098(display ele)2.598 F -.25(va)-.25 G .098
-(tions using a log-).25 F .335(arithmic grayscale, with higher ele)108
-372 R -.25(va)-.25 G .335
-(tions represented through brighter shades of gray).25 F 5.336(.T)-.65 G
-.336(he dynamic range)-5.336 F .257
-(of the image is scaled between the highest and lo)108 384 R .257
-(west ele)-.25 F -.25(va)-.25 G .257(tions present in the map.).25 F
-.257(The only e)5.257 F .257(xception to)-.15 F(this is sea-le)108 396 Q
--.15(ve)-.25 G(l, which is represented using the color blue.).15 E -.8
-(To)108 420 S(pographic output is in).8 E -.2(vo)-.4 G -.1(ke).2 G 2.5
-(du).1 G(sing the)-2.5 E F1(-o)2.5 E F0(switch:)2.5 E/F4 10/Courier@0 SF
-(splat -t tx_site -r rx_site -o topo_map.ppm)108 444 Q F0(The)108 468 Q
-F1(.ppm)2.5 E F0 -.15(ex)2.5 G
-(tension on the output \214lename is assumed by).15 E F3(SPLA)2.5 E(T!)
--.95 E F0 2.5(,a)C(nd is optional.)-2.5 E .006(In this e)108 492 R
-(xample,)-.15 E F1(topo_map.ppm)2.506 E F0 .007
-(will illustrate the locations of the transmitter and recei)2.506 F -.15
-(ve)-.25 G 2.507(rs).15 G .007(ites speci\214ed.)-2.507 F(In)5.007 E .22
-(addition, the great circle path between the tw)108 504 R 2.72(os)-.1 G
-.22(ites will be dra)-2.72 F .22(wn o)-.15 F -.15(ve)-.15 G 2.72(rl).15
-G .22(ocations for which an unobstructed)-2.72 F 1.208(path e)108 516 R
-1.209(xists to the transmitter at a recei)-.15 F 1.209
-(ving antenna height equal to that of the recei)-.25 F -.15(ve)-.25 G
-3.709(rs).15 G 1.209(ite \(speci\214ed in)-3.709 F F1(rx_site)108 528 Q
-(.qth)-.15 E F0(\).)A .773(It may desirable to populate the topographic\
- map with names and locations of cities, to)108 552 R .773
-(wer sites, or other)-.25 F(important locations.)108 564 Q 2.5(Ac)5 G
-(ity \214le may be passed to)-2.5 E F3(SPLA)2.5 E(T!)-.95 E F0
-(using the)2.5 E F1(-s)2.5 E F0(switch:)2.5 E F4
-(splat -t tx_site -r rx_site -s cities.dat -o topo_map)108 588 Q F0
-(Up to \214v)108 612 Q 2.5(es)-.15 G
-(eparate city \214les may be passed to)-2.5 E F3(SPLA)2.5 E(T!)-.95 E F0
-(at a time follo)2.5 E(wing the)-.25 E F1(-s)2.5 E F0(switch.)2.5 E .554
-(County and state boundaries may be added to the map by specifying up t\
-o \214v)108 636 R 3.055(eU)-.15 G .555(.S. Census Bureau carto-)-3.055 F
-(graphic boundary \214les using the)108 648 Q F1(-b)2.5 E F0(switch:)2.5
-E F4(splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map)108 672 Q
-F0 1.064
-(In situations where multiple transmitter sites are in use, as man)108
-696 R 3.563(ya)-.15 G 3.563(sf)-3.563 G 1.063
-(our site locations may be passed to)-3.563 F F3(SPLA)108 708 Q(T!)-.95
-E F0(at a time for analysis:)2.5 E(KD2BD Softw)72 768 Q 121.625(are 20)
--.1 F(December 2006)2.5 E(7)190.955 E EP
-%%Page: 8 8
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
-(splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p profile.png)
-108 84 Q F0 .285(In this e)108 108 R .285(xample, four separate terrain\
- pro\214les and obstruction reports will be generated by)-.15 F/F2 10
-/Times-Bold@0 SF(SPLA)2.785 E(T!)-.95 E F0 5.285(.A)C(sin-)-2.5 E .509
-(gle topographic map can be speci\214ed using the)108 120 R/F3 10
-/Times-Italic@0 SF(-o)3.009 E F0 .508
-(switch, and line-of-sight paths between each transmitter)3.009 F .816
-(and the recei)108 132 R -.15(ve)-.25 G 3.316(rs).15 G .816
-(ite indicated will be produced on the map, each in its o)-3.316 F .817
-(wn color)-.25 F 5.817(.T)-.55 G .817(he path between the)-5.817 F .767
-(\214rst transmitter speci\214ed to the recei)108 144 R -.15(ve)-.25 G
-3.267(rw).15 G .766
-(ill be in green, the path between the second transmitter and the)-3.267
-F(recei)108 156 Q -.15(ve)-.25 G 3.463(rw).15 G .963(ill be in c)-3.463
-F .964(yan, the path between the third transmitter and the recei)-.15 F
--.15(ve)-.25 G 3.464(rw).15 G .964(ill be in violet, and the)-3.464 F
-(path between the fourth transmitter and the recei)108 168 Q -.15(ve)
--.25 G 2.5(rw).15 G(ill be in sienna.)-2.5 E F2(SPLA)108 192 Q(T!)-.95 E
-F0 .59(generated topographic maps are 24-bit T)3.09 F .59
-(rueColor Portable PixMap \(PPM\) images.)-.35 F(The)5.59 E 3.09(ym)-.15
-G .59(ay be)-3.09 F(vie)108 204 Q 1.06(wed, edited, or con)-.25 F -.15
-(ve)-.4 G 1.06(rted to other graphic formats by popular image vie).15 F
-1.06(wing applications such as)-.25 F F2(xv)3.56 E F0(,)A F2 1.66
-(The GIMP)108 216 R F0(,)A F2(ImageMagick)4.16 E F0 4.16(,a)C(nd)-4.16 E
-F2(XP)4.16 E(aint)-.1 E F0 6.66(.P)C 1.66
-(NG format is highly recommended for lossless compressed)-6.66 F .726
-(storage of)108 228 R F2(SPLA)3.226 E(T!)-.95 E F0 .726
-(generated topographic output \214les.)5.726 F F2(ImageMagick)5.726 E F0
-1.827 -.55('s c)D .727(ommand-line utility easily con-).55 F -.15(ve)108
-240 S(rts).15 E F2(SPLA)2.5 E(T!)-.95 E F0 1.1 -.55('s P)D
-(PM \214les to PNG format:).55 E F1(convert splat_map.ppm splat_map.png)
-108 264 Q F0 17.667(Another e)108 288 R 17.667
-(xcellent PPM to PNG command-line utility is a)-.15 F -.25(va)-.2 G
-17.666(ilable at:).25 F F3(http://www)108 300 Q(.libpng)-.74 E(.or)-.15
-E(g/pub/png/book/sour)-.37 E(ces.html)-.37 E F0 5.152(.A)C 2.652(sal)
--5.152 G .153(ast resort, PPM \214les may be compressed using the)-2.652
-F(bzip2 utility)108 312 Q 2.5(,a)-.65 G(nd read directly by)-2.5 E F2
-(The GIMP)2.5 E F0(in this format.)2.5 E/F4 10.95/Times-Bold@0 SF
-(REGION)72 328.8 Q(AL CO)-.219 E(VERA)-.548 E(GE AN)-.602 E(AL)-.219 E
-(YSIS)-1.007 E F2(SPLA)108 340.8 Q(T!)-.95 E F0 .098
-(can analyze a transmitter or repeater site, or netw)2.599 F .098
-(ork of sites, and predict the re)-.1 F .098(gional co)-.15 F -.15(ve)
--.15 G .098(rage for).15 F .682(each site speci\214ed.)108 352.8 R .682
-(In this mode,)5.682 F F2(SPLA)3.183 E(T!)-.95 E F0 .683
-(can generate a topographic map displaying the geometric line-)3.183 F
-.163(of-sight co)108 364.8 R -.15(ve)-.15 G .163(rage area of the sites\
- based on the location of each site and the height of recei).15 F .462
--.15(ve a)-.25 H .162(ntenna wish-).15 F .438
-(ing to communicate with the site in question.)108 376.8 R F2(SPLA)5.439
-E(T!)-.95 E F0 .439(switches from point-to-point analysis mode to area)
-2.939 F(prediction mode when the)108 388.8 Q F3(-c)2.5 E F0
-(switch is in)2.5 E -.2(vo)-.4 G -.1(ke).2 G 2.5(da).1 G 2.5(sf)-2.5 G
-(ollo)-2.5 E(ws:)-.25 E F1
-(splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o tx_coverage)
-108 412.8 Q F0 .27(In this e)108 436.8 R(xample,)-.15 E F2(SPLA)2.77 E
-(T!)-.95 E F0 .269(generates a topographic map called)2.769 F F3(tx_co)
-2.769 E(ver)-.1 E -.1(age)-.15 G(.ppm)-.05 E F0 .269
-(that illustrates the predicted)2.769 F 1.534(line-of-sight re)108 448.8
-R 1.534(gional co)-.15 F -.15(ve)-.15 G 1.534(rage of).15 F F3(tx_site)
-4.034 E F0 1.535(to recei)4.034 F 1.535(ving locations ha)-.25 F 1.535
-(ving antennas 30.0 feet abo)-.2 F 1.835 -.15(ve g)-.15 H(round).15 E
-(le)108 460.8 Q -.15(ve)-.25 G 3.162(l\().15 G -.4(AG)-3.162 G 3.162
-(L\). If).4 F(the)3.162 E F3(-metric)3.162 E F0 .662
-(switch is used, the ar)3.162 F .662(gument follo)-.18 F .662(wing the)
--.25 F F3(-c)3.162 E F0 .661(switch is interpreted as being in)3.161 F
-.162(meters, rather than in feet.)108 472.8 R .163(The contents of)5.163
-F F3(cities.dat)2.663 E F0 .163
-(are plotted on the map, as are the cartographic bound-)2.663 F
-(aries contained in the \214le)108 484.8 Q F3(co34_d00.dat)2.5 E F0(.)A
-.572(When plotting line-of-sight paths and areas of re)108 508.8 R .572
-(gional co)-.15 F -.15(ve)-.15 G(rage,).15 E F2(SPLA)3.072 E(T!)-.95 E
-F0 .572(by def)3.072 F .572(ault does not account for)-.1 F .031(the ef)
-108 520.8 R .032(fects of atmospheric bending.)-.25 F(Ho)5.032 E(we)-.25
-E -.15(ve)-.25 G .832 -.4(r, t).15 H .032(his beha).4 F .032
-(vior may be modi\214ed by using the Earth radius mul-)-.2 F(tiplier \()
-108 532.8 Q F3(-m)A F0 2.5(\)s)C(witch:)-2.5 E F1(splat -t wnjt -c 30.0\
- -m 1.333 -s cities.dat -b counties.dat -o map.ppm)108 556.8 Q F0 .595
-(An earth radius multiplier of 1.333 instructs)108 580.8 R F2(SPLA)3.095
-E(T!)-.95 E F0 .595(to use the "four)3.095 F .594
-(-thirds earth" model for line-of-sight)-.2 F(propag)108 592.8 Q
-(ation analysis.)-.05 E(An)5 E 2.5(ya)-.15 G
-(ppropriate earth radius multiplier may be selected by the user)-2.5 E
-(.)-.55 E .201(When in)108 616.8 R -.2(vo)-.4 G -.1(ke).2 G 2.701(di).1
-G 2.701(na)-2.701 G .201(rea prediction mode,)-2.701 F F2(SPLA)2.701 E
-(T!)-.95 E F0 .202(generates a site report for each station analyzed.)
-2.701 F F2(SPLA)5.202 E(T!)-.95 E F0 .659
-(site reports contain details of the site')108 628.8 R 3.159(sg)-.55 G
-.659(eographic location, its height abo)-3.159 F .959 -.15(ve m)-.15 H
-.658(ean sea le).15 F -.15(ve)-.25 G .658(l, the antenna').15 F(s)-.55 E
-.612(height abo)108 640.8 R .912 -.15(ve m)-.15 H .612(ean sea le).15 F
--.15(ve)-.25 G .612(l, the antenna').15 F 3.112(sh)-.55 G .612
-(eight abo)-3.112 F .912 -.15(ve a)-.15 H -.15(ve)-.05 G .613
-(rage terrain, and the height of the a).15 F -.15(ve)-.2 G .613
-(rage ter).15 F(-)-.2 E(rain calculated in the directions of 0, 45, 90,\
- 135, 180, 225, 270, and 315 de)108 652.8 Q(grees azimuth.)-.15 E F4
-(DETERMINING MUL)72 669.6 Q(TIPLE REGIONS OF LOS CO)-1.007 E(VERA)-.548
-E(GE)-.602 E F2(SPLA)108 681.6 Q(T!)-.95 E F0 1.087
-(can also display line-of-sight co)3.587 F -.15(ve)-.15 G 1.086
-(rage areas for as man).15 F 3.586(ya)-.15 G 3.586(sf)-3.586 G 1.086
-(our separate transmitter sites on a)-3.586 F(common topographic map.)
-108 693.6 Q -.15(Fo)5 G 2.5(re).15 G(xample:)-2.65 E F1
-(splat -t site1 site2 site3 site4 -c 10.0 -metric -o network.ppm)108
-717.6 Q F0(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F(December 2006)2.5 E
-(8)190.955 E EP
-%%Page: 9 9
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .686(plots the re)
-108 84 R .687(gional line-of-sight co)-.15 F -.15(ve)-.15 G .687
-(rage of site1, site2, site3, and site4 based on a recei).15 F .987 -.15
-(ve a)-.25 H .687(ntenna located).15 F .763(10.0 meters abo)108 96 R
-1.063 -.15(ve g)-.15 H .763(round le).15 F -.15(ve)-.25 G 3.263(l. A).15
-F .762(topographic map is then written to the \214le)3.263 F/F1 10
-/Times-Italic@0 SF(network.ppm)3.262 E F0 5.762(.T)C .762(he line-of-)
--5.762 F .302(sight co)108 108 R -.15(ve)-.15 G .302
-(rage area of the transmitters are plotted as follo).15 F .303
-(ws in the colors indicated \(along with their corre-)-.25 F
-(sponding RGB v)108 120 Q(alues in decimal\):)-.25 E/F2 10/Courier@0 SF
-(site1: Green \(0,255,0\))132 144 Q(site2: Cyan \(0,255,255\))132 156 Q
-(site3: Medium Violet \(147,112,219\))132 168 Q
-(site4: Sienna 1 \(255,130,71\))132 180 Q
-(site1 + site2: Yellow \(255,255,0\))132 204 Q
-(site1 + site3: Pink \(255,192,203\))132 216 Q
-(site1 + site4: Green Yellow \(173,255,47\))132 228 Q
-(site2 + site3: Orange \(255,165,0\))132 240 Q
-(site2 + site4: Dark Sea Green 1 \(193,255,193\))132 252 Q
-(site3 + site4: Dark Turquoise \(0,206,209\))132 264 Q
-(site1 + site2 + site3: Dark Green \(0,100,0\))132 288 Q
-(site1 + site2 + site4: Blanched Almond \(255,235,205\))132 300 Q
-(site1 + site3 + site4: Medium Spring Green \(0,250,154\))132 312 Q
-(site2 + site3 + site4: Tan \(210,180,140\))132 324 Q
-(site1 + site2 + site3 + site4: Gold2 \(238,201,0\))132 348 Q F0 .247
-(If separate)108 372 R F1(.qth)2.747 E F0 .247
-(\214les are generated, each representing a common site location b)2.747
-F .247(ut a dif)-.2 F .246(ferent antenna height,)-.25 F 3.535(as)108
-384 S 1.035(ingle topographic map illustrating the re)-3.535 F 1.036
-(gional co)-.15 F -.15(ve)-.15 G 1.036(rage from as man).15 F 3.536(ya)
--.15 G 3.536(sf)-3.536 G 1.036(our separate locations on a)-3.536 F
-(single to)108 396 Q(wer may be generated by)-.25 E/F3 10/Times-Bold@0
-SF(SPLA)2.5 E(T!)-.95 E F0(.)A/F4 10.95/Times-Bold@0 SF(LONGLEY)72 412.8
-Q(-RICE P)-1.007 E -1.04(AT)-.81 G 2.738(HL)1.04 G(OSS AN)-2.738 E(AL)
--.219 E(YSIS)-1.007 E F0 .345(If the)108 424.8 R F1(-c)2.845 E F0 .345
-(switch is replaced by a)2.845 F F1(-L)2.844 E F0 .344(switch, a Longle)
-2.844 F .344(y-Rice path loss map for a transmitter site may be gen-)
--.15 F(erated:)108 436.8 Q F2
-(splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o path_loss_map)
-108 460.8 Q F0 .977(In this mode,)108 484.8 R F3(SPLA)3.477 E(T!)-.95 E
-F0 .977(generates a multi-color map illustrating e)3.477 F .977
-(xpected signal le)-.15 F -.15(ve)-.25 G .978(ls \(path loss\) in areas)
-.15 F .997(surrounding the transmitter site.)108 496.8 R 3.497(Al)5.997
-G -.15(eg)-3.497 G .996
-(end at the bottom of the map correlates each color with a speci\214c)
-.15 F(path loss range in decibels.)108 508.8 Q .63(The Longle)108 532.8
-R .63(y-Rice analysis range may be modi\214ed to a user)-.15 F .63
-(-speci\214c v)-.2 F .63(alue using the)-.25 F F1(-R)3.13 E F0 3.13
-(switch. The)3.13 F(ar)3.13 E(gu-)-.18 E .523(ment must be gi)108 544.8
-R -.15(ve)-.25 G 3.023(ni).15 G 3.023(nm)-3.023 G .523
-(iles \(or kilometers if the)-3.023 F F1(-metric)3.023 E F0 .522
-(switch is used\).)3.022 F .522(If a range wider than the gener)5.522 F
-(-)-.2 E .926(ated topographic map is speci\214ed,)108 556.8 R F3(SPLA)
-3.426 E(T!)-.95 E F0 .926(will perform Longle)3.426 F .926
-(y-Rice path loss calculations between all)-.15 F
-(four corners of the area prediction map.)108 568.8 Q(The)108 592.8 Q F1
-(-db)3.345 E F0 .845(switch allo)3.345 F .845
-(ws a constraint to be placed on the maximum path loss re)-.25 F .844
-(gion plotted on the map.)-.15 F(A)5.844 E .21(maximum path loss betwee\
-n 80 and 230 dB may be speci\214ed using this switch.)108 604.8 R -.15
-(Fo)5.21 G 2.71(re).15 G .21(xample, if a path loss)-2.86 F(be)108 616.8
-Q .396(yond -140 dB is irrele)-.15 F -.25(va)-.25 G .395(nt to the surv)
-.25 F .695 -.15(ey b)-.15 H .395(eing conducted,).15 F F3(SPLA)2.895 E
-(T!)-.95 E F0 1.495 -.55('s p)D .395
-(ath loss plot can be constrained to).55 F(the re)108 628.8 Q
-(gion bounded by the 140 dB attenuation contour as follo)-.15 E(ws:)-.25
-E F2(splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -db 140 -o plo\
-t.ppm)108 652.8 Q F4(ANTENN)72 681.6 Q 2.738(AR)-.219 G(ADIA)-2.738 E
-(TION P)-1.04 E -1.04(AT)-.81 G(TERN P)1.04 E(ARAMETERS)-.81 E F0 .976
-(Normalized \214eld v)108 693.6 R .977
-(oltage patterns for a transmitting antenna')-.2 F 3.477(sh)-.55 G .977
-(orizontal and v)-3.477 F .977(ertical planes are imported)-.15 F .588
-(automatically into)108 705.6 R F3(SPLA)3.088 E(T!)-.95 E F0 .588
-(when a Longle)3.088 F .588(y-Rice co)-.15 F -.15(ve)-.15 G .588
-(rage analysis is performed.).15 F .587(Antenna pattern data is)5.587 F
-.804(read from a pair of \214les ha)108 717.6 R .805
-(ving the same base name as the transmitter and LRP \214les, b)-.2 F
-.805(ut with)-.2 F F1(.az)3.305 E F0(and)3.305 E F1(.el)3.305 E F0 -.15
-(ex)108 729.6 S .308(tensions for azimuth and ele).15 F -.25(va)-.25 G
-.308(tion pattern \214les, respecti).25 F -.15(ve)-.25 G(ly).15 E 5.307
-(.S)-.65 G .307(peci\214cations re)-5.307 F -.05(ga)-.15 G .307
-(rding pattern rotation \(if).05 F(KD2BD Softw)72 768 Q 121.625(are 20)
--.1 F(December 2006)2.5 E(9)190.955 E EP
-%%Page: 10 10
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E(an)108 84 Q .45
-(y\) and mechanical beam tilt and tilt direction \(if an)-.15 F .451
-(y\) are also contained within)-.15 F/F1 10/Times-Bold@0 SF(SPLA)2.951 E
-(T!)-.95 E F0 .451(antenna pattern)2.951 F(\214les.)108 96 Q -.15(Fo)108
-120 S 2.5(re).15 G(xample, the \214rst fe)-2.65 E 2.5(wl)-.25 G
-(ines of a)-2.5 E F1(SPLA)2.5 E(T!)-.95 E F0
-(azimuth pattern \214le might appear as follo)2.5 E(ws \()-.25 E/F2 10
-/Times-Italic@0 SF(kvea.az)A F0(\):)A/F3 10/Courier@0 SF(183.0)156 144 Q
-42(00)156 156 S(.8950590)-42 E 42(10)156 168 S(.8966406)-42 E 42(20)156
-180 S(.8981447)-42 E 42(30)156 192 S(.8995795)-42 E 42(40)156 204 S
-(.9009535)-42 E 42(50)156 216 S(.9022749)-42 E 42(60)156 228 S(.9035517)
--42 E 42(70)156 240 S(.9047923)-42 E 42(80)156 252 S(.9060051)-42 E F0
-1.778(The \214rst line of the)108 276 R F2(.az)4.278 E F0 1.777(\214le \
-speci\214es the amount of azimuthal pattern rotation \(measured clockwi\
-se in)4.278 F(de)108 288 Q .062(grees from T)-.15 F .062
-(rue North\) to be applied by)-.35 F F1(SPLA)2.562 E(T!)-.95 E F0 .063
-(to the data contained in the)2.562 F F2(.az)2.563 E F0 2.563
-(\214le. This)2.563 F .063(is follo)2.563 F .063(wed by)-.25 F .871
-(azimuth headings \(0 to 360 de)108 300 R .871(grees\) and their associ\
-ated normalized \214eld patterns \(0.000 to 1.000\) sepa-)-.15 F
-(rated by whitespace.)108 312 Q .068(The structure of)108 336 R F1(SPLA)
-2.569 E(T!)-.95 E F0(ele)2.569 E -.25(va)-.25 G .069
-(tion pattern \214les is slightly dif).25 F 2.569(ferent. The)-.25 F
-.069(\214rst line of the)2.569 F F2(.el)2.569 E F0 .069
-(\214le speci\214es the)2.569 F .892
-(amount of mechanical beam tilt applied to the antenna.)108 348 R .892
-(Note that a)5.892 F F2(downwar)3.392 E 3.392(dt)-.37 G(ilt)-3.392 E F0
-(\(belo)3.391 E 3.391(wt)-.25 G .891(he horizon\) is)-3.391 F -.15(ex)
-108 360 S 1.101(pressed as a).15 F F2 1.101(positive angle)3.601 F F0
-3.601(,w)C 1.101(hile an)-3.601 F F2(upwar)3.601 E 3.601(dt)-.37 G(ilt)
--3.601 E F0(\(abo)3.601 E 1.401 -.15(ve t)-.15 H 1.101
-(he horizon\) is e).15 F 1.101(xpressed as a)-.15 F F2(ne)3.602 E 1.102
-(gative angle)-.4 F F0(.)A(This data is follo)108 372 Q
-(wed by the azimuthal direction of the tilt, separated by whitespace.)
--.25 E .437(The remainder of the \214le consists of ele)108 396 R -.25
-(va)-.25 G .436(tion angles and their corresponding normalized v).25 F
-.436(oltage radiation)-.2 F .247(pattern \(0.000 to 1.000\) v)108 408 R
-.247(alues separated by whitespace.)-.25 F(Ele)5.247 E -.25(va)-.25 G
-.248(tion angles must be speci\214ed o).25 F -.15(ve)-.15 G 2.748(ra-)
-.15 G .248(10.0 to)-2.748 F .131(+90.0 de)108 420 R .131(gree range.)
--.15 F .131(As w)5.131 F .131(as the con)-.1 F -.15(ve)-.4 G .131
-(ntion with mechanical beamtilt,).15 F F2(ne)2.631 E .13(gative ele)-.4
-F .13(vation angles)-.15 F F0 .13(are used to)2.63 F(represent ele)108
-432 Q -.25(va)-.25 G(tions).25 E F2(abo)2.5 E(ve the horizon)-.1 E F0
-2.5(,w)C(hile)-2.5 E F2(positive angles)2.5 E F0(represents ele)2.5 E
--.25(va)-.25 G(tions).25 E F2(below the horizon)2.5 E F0(.)A -.15(Fo)108
-456 S 2.5(re).15 G(xample, the \214rst fe)-2.65 E 2.5(wl)-.25 G(ines a)
--2.5 E F1(SPLA)2.5 E(T!)-.95 E F0(ele)2.5 E -.25(va)-.25 G
-(tion pattern \214le might appear as follo).25 E(ws \()-.25 E F2
-(kvea.el)A F0(\):)A F3 18(1.1 130.0)156 480 R 12(-10.0 0.172)150 492 R
-18(-9.5 0.109)150 504 R 18(-9.0 0.115)150 516 R 18(-8.5 0.155)150 528 R
-18(-8.0 0.157)150 540 R 18(-7.5 0.104)150 552 R 18(-7.0 0.029)150 564 R
-18(-6.5 0.109)150 576 R 18(-6.0 0.185)150 588 R F0 1.538(In this e)108
-612 R 1.538(xample, the antenna is mechanically tilted do)-.15 F(wnw)
--.25 E 1.538(ard 1.1 de)-.1 F 1.538(grees to)-.15 F -.1(wa)-.25 G 1.538
-(rds an azimuth of 130.0).1 F(de)108 624 Q(grees.)-.15 E -.15(Fo)108 648
-S 3.447(rb).15 G .946(est results, the resolution of azimuth pattern da\
-ta should be speci\214ed to the nearest de)-3.447 F .946(gree azimuth,)
--.15 F 1.299(and ele)108 660 R -.25(va)-.25 G 1.299(tion pattern data r\
-esolution should be speci\214ed to the nearest 0.01 de).25 F 3.8
-(grees. If)-.15 F 1.3(the pattern data)3.8 F .55
-(speci\214ed does not reach this le)108 672 R -.15(ve)-.25 G 3.049(lo)
-.15 G 3.049(fr)-3.049 G(esolution,)-3.049 E F1(SPLA)3.049 E(T!)-.95 E F0
-.549(will interpolate the v)3.049 F .549(alues pro)-.25 F .549
-(vided to determine)-.15 F(the data at the required resolution, althoug\
-h this may result in a loss in accurac)108 684 Q -.65(y.)-.15 G
-(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F(December 2006)2.5 E(10)
-185.955 E EP
-%%Page: 11 11
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10.95
-/Times-Bold@0 SF(IMPOR)72 84 Q(TING AND EXPOR)-.438 E(TING REGION)-.438
-E(AL P)-.219 E -1.04(AT)-.81 G 2.738(HL)1.04 G(OSS CONT)-2.738 E(OUR D)
--.197 E -1.644 -1.04(AT A)-.383 H F0 .254(Performing a Longle)108 96 R
-.254(y-Rice co)-.15 F -.15(ve)-.15 G .254(rage analysis can be a v).15 F
-.254(ery time consuming process, especially if the anal-)-.15 F .936
-(ysis is repeated repeatedly to disco)108 108 R -.15(ve)-.15 G 3.436(rw)
-.15 G .936(hat ef)-3.436 F .935
-(fects changes to the antenna radiation patterns mak)-.25 F 3.435(et)-.1
-G 3.435(ot)-3.435 G(he)-3.435 E(predicted co)108 120 Q -.15(ve)-.15 G
-(rage area.).15 E .721(This process can be e)108 144 R .722
-(xpedited by e)-.15 F .722(xporting the Longle)-.15 F .722(y-Rice re)
--.15 F .722(gional path loss contour data to an output)-.15 F .776
-(\214le, modifying the path loss data e)108 156 R .775
-(xternally to incorporate antenna pattern ef)-.15 F .775
-(fects, and then importing the)-.25 F
-(modi\214ed path loss data back into)108 168 Q/F2 10/Times-Bold@0 SF
-(SPLA)2.5 E(T!)-.95 E F0(to rapidly produce a re)5 E
-(vised path loss map.)-.25 E -.15(Fo)108 192 S 3.253(re).15 G .753
-(xample, a path loss output \214le can be generated by)-3.403 F F2(SPLA)
-3.253 E(T!)-.95 E F0 .753(for a recei)5.753 F 1.053 -.15(ve s)-.25 H
-.754(ite 30 feet abo).15 F 1.054 -.15(ve g)-.15 H(round).15 E(le)108 204
-Q -.15(ve)-.25 G 2.998(lo).15 G -.15(ve)-3.148 G 2.998(ra5).15 G 2.998
-(0m)-2.998 G .497(ile radius surrounding a transmitter site to a maximu\
-m path loss of 140 dB using the fol-)-2.998 F(lo)108 216 Q(wing syntax:)
--.25 E/F3 10/Courier@0 SF
-(splat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat)108 240 Q F2
-(SPLA)108 264 Q(T!)-.95 E F0 .044(path loss output \214les often e)2.544
-F .044(xceed 100 me)-.15 F -.05(ga)-.15 G .044(bytes in size.).05 F(The)
-5.045 E 2.545(yc)-.15 G .045(ontain information relating to the)-2.545 F
-2.58(boundaries of re)108 276 R 2.58(gion the)-.15 F 5.08(yd)-.15 G 2.58
-(escribe follo)-5.08 F 2.58(wed by latitudes \(de)-.25 F 2.58
-(grees North\), longitudes \(de)-.15 F 2.58(grees W)-.15 F(est\),)-.8 E
-.655(azimuths, ele)108 288 R -.25(va)-.25 G .656(tions \(to the \214rst\
- obstruction\), and path loss \214gures \(dB\) for a series of speci\
-\214c points that).25 F .542(comprise the re)108 300 R .542
-(gion surrounding the transmitter site.)-.15 F .542(The \214rst fe)5.542
-F 3.042(wl)-.25 G .542(ines of a)-3.042 F F2(SPLA)3.042 E(T!)-.95 E F0
-.541(path loss output \214le)3.041 F(tak)108 312 Q 2.5(eo)-.1 G 2.5(nt)
--2.5 G(he follo)-2.5 E(wing appearance \()-.25 E/F4 10/Times-Italic@0 SF
-(pathloss.dat)A F0(\):)A F3(119, 117)156 336 Q 6(;m)24 G
-(ax_west, min_west)-6 E(35, 33)156 348 Q 6(;m)36 G(ax_north, min_north)
--6 E(34.2265434, 118.0631104, 48.171, -37.461, 67.70)156 360 Q
-(34.2270355, 118.0624390, 48.262, -26.212, 73.72)156 372 Q
-(34.2280197, 118.0611038, 48.269, -14.951, 79.74)156 384 Q
-(34.2285156, 118.0604401, 48.207, -11.351, 81.68)156 396 Q
-(34.2290077, 118.0597687, 48.240, -10.518, 83.26)156 408 Q
-(34.2294998, 118.0591049, 48.225, 23.201, 84.60)156 420 Q
-(34.2304878, 118.0577698, 48.213, 15.769, 137.84)156 432 Q
-(34.2309799, 118.0570984, 48.234, 15.965, 151.54)156 444 Q
-(34.2314720, 118.0564346, 48.224, 16.520, 149.45)156 456 Q
-(34.2319679, 118.0557632, 48.223, 15.588, 151.61)156 468 Q
-(34.2329521, 118.0544281, 48.230, 13.889, 135.45)156 480 Q
-(34.2334442, 118.0537643, 48.223, 11.693, 137.37)156 492 Q
-(34.2339401, 118.0530930, 48.222, 14.050, 126.32)156 504 Q
-(34.2344322, 118.0524292, 48.216, 16.274, 156.28)156 516 Q
-(34.2354164, 118.0510941, 48.222, 15.058, 152.65)156 528 Q
-(34.2359123, 118.0504227, 48.221, 16.215, 158.57)156 540 Q
-(34.2364044, 118.0497589, 48.216, 15.024, 157.30)156 552 Q
-(34.2368965, 118.0490875, 48.225, 17.184, 156.36)156 564 Q F0 .134
-(It is not uncommon for)108 588 R F2(SPLA)2.634 E(T!)-.95 E F0 .135
-(path loss \214les to contain as man)2.635 F 2.635(ya)-.15 G 2.635(s3m)
--2.635 G .135(illion or more lines of data.)-2.635 F(Com-)5.135 E 1.165
-(ments can be placed in the \214le if the)108 600 R 3.664(ya)-.15 G
-1.164(re proceeded by a semicolon character)-3.664 F 6.164(.T)-.55 G(he)
--6.164 E F2(vim)3.664 E F0(te)3.664 E 1.164(xt editor has)-.15 F(pro)108
-612 Q -.15(ve)-.15 G 2.5(nc).15 G
-(apable of editing \214les of this size.)-2.5 E .807(Note as w)108 636 R
-.807(as the case in the antenna pattern \214les, ne)-.1 F -.05(ga)-.15 G
-(ti).05 E 1.107 -.15(ve e)-.25 H(le).15 E -.25(va)-.25 G .807
-(tion angles refer to upw).25 F .808(ard tilt \(abo)-.1 F 1.108 -.15
-(ve t)-.15 H(he).15 E .94(horizon\), while positi)108 648 R 1.24 -.15
-(ve a)-.25 H .94(ngles refer to do).15 F(wnw)-.25 E .94(ard tilt \(belo)
--.1 F 3.44(wt)-.25 G .94(he horizon\).)-3.44 F .94
-(These angles refer to the ele-)5.94 F -.25(va)108 660 S 1.075
-(tion to the recei).25 F 1.075(ving antenna at the height abo)-.25 F
-1.376 -.15(ve g)-.15 H 1.076(round le).15 F -.15(ve)-.25 G 3.576(ls).15
-G 1.076(peci\214ed using the)-3.576 F F4(-L)3.576 E F0(switch)3.576 E F4
-(if)3.576 E F0 1.076(the path)3.576 F 2.35
-(between transmitter and recei)108 672 R -.15(ve)-.25 G 4.85(ri).15 G
-4.85(su)-4.85 G 4.85(nobstructed. If)-4.85 F 2.35
-(the path between the transmitter and recei)4.85 F -.15(ve)-.25 G 4.85
-(ri).15 G(s)-4.85 E .009(obstructed, then the ele)108 684 R -.25(va)-.25
-G .009(tion angle to the \214rst obstruction is returned by).25 F F2
-(SPLA)2.51 E(T!)-.95 E F0 5.01(.T)C .01(his is because the Lon-)-5.01 F
-(gle)108 696 Q .262(y-Rice model considers the ener)-.15 F .262
-(gy reaching a distant point o)-.18 F -.15(ve)-.15 G 2.762(ra).15 G
-2.762(no)-2.762 G .262(bstructed path as a deri)-2.762 F -.25(va)-.25 G
-(ti).25 E .561 -.15(ve o)-.25 H 2.761(ft).15 G(he)-2.761 E(ener)108 708
-Q .489(gy scattered from the top of the \214rst obstruction, only)-.18 F
-5.489(.S)-.65 G .489(ince ener)-5.489 F .489
-(gy cannot reach the obstructed loca-)-.18 F(tion directly)108 720 Q 2.5
-(,t)-.65 G(he actual ele)-2.5 E -.25(va)-.25 G
-(tion angle to that point is irrele).25 E -.25(va)-.25 G(nt.).25 E
-(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F(December 2006)2.5 E(11)
-185.955 E EP
-%%Page: 12 12
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E 1.142
-(When modifying)108 84 R/F1 10/Times-Bold@0 SF(SPLA)3.642 E(T!)-.95 E F0
-1.141(path loss \214les to re\215ect antenna pattern data,)3.642 F/F2 10
-/Times-Italic@0 SF 1.141(only the last column \(path loss\))3.641 F F0
-.233(should be amended to re\215ect the antenna')108 96 R 2.733(sn)-.55
-G .233(ormalized g)-2.733 F .233(ain at the azimuth and ele)-.05 F -.25
-(va)-.25 G .234(tion angles speci\214ed in).25 F .395(the \214le.)108
-108 R .395(\(At this time, programs and scripts capable of performing t\
-his operation are left as an e)5.395 F -.15(xe)-.15 G .395(rcise for).15
-F(the user)108 120 Q(.\))-.55 E
-(Modi\214ed path loss maps can be imported back into)108 144 Q F1(SPLA)
-2.5 E(T!)-.95 E F0(for generating re)2.5 E(vised co)-.25 E -.15(ve)-.15
-G(rage maps:).15 E/F3 10/Courier@0 SF
-(splat -t kvea -pli pathloss.dat -s city.dat -b county.dat -o map.ppm)
-108 168 Q F1(SPLA)108 192 Q(T!)-.95 E F0 .006
-(path loss \214les can also be used for conducting co)2.506 F -.15(ve)
--.15 G .007(rage or interference studies outside of).15 F F1(SPLA)2.507
-E(T!)-.95 E F0(.)A/F4 10.95/Times-Bold@0 SF
-(USER-DEFINED TERRAIN INPUT FILES)72 208.8 Q F0 3.542(Au)108 220.8 S
-(ser)-3.542 E 1.042(-de\214ned terrain \214le is a user)-.2 F 1.041
-(-generated te)-.2 F 1.041
-(xt \214le containing latitudes, longitudes, and heights abo)-.15 F -.15
-(ve)-.15 G 1.072(ground le)108 232.8 R -.15(ve)-.25 G 3.572(lo).15 G
-3.572(fs)-3.572 G 1.072(peci\214c terrain features belie)-3.572 F -.15
-(ve)-.25 G 3.572(dt).15 G 3.572(ob)-3.572 G 3.573(eo)-3.572 G 3.573(fi)
--3.573 G 1.073(mportance to the)-3.573 F F1(SPLA)3.573 E(T!)-.95 E F0
-1.073(analysis being con-)3.573 F .602(ducted, b)108 244.8 R .601
-(ut noticeably absent from the SDF \214les being used.)-.2 F 3.101(Au)
-5.601 G(ser)-3.101 E .601(-de\214ned terrain \214le is imported into a)
--.2 F F1(SPLA)108 256.8 Q(T!)-.95 E F0(analysis using the)2.5 E F2(-udt)
-2.5 E F0(switch:)2.5 E F3
-(splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm)114 280.8 Q F0
-2.5(Au)108 304.8 S(ser)-2.5 E(-de\214ned terrain \214le has the follo)
--.2 E(wing appearance and structure:)-.25 E F3
-(40.32180556, 74.1325, 100.0 meters)150 328.8 Q
-(40.321805, 74.1315, 300.0)150 340.8 Q
-(40.3218055, 74.1305, 100.0 meters)150 352.8 Q F0 -.7(Te)108 376.8 S
-1.42(rrain height is interpreted as being described in feet abo).7 F
-1.72 -.15(ve g)-.15 H 1.42(round le).15 F -.15(ve)-.25 G 3.92(lu).15 G
-1.42(nless follo)-3.92 F 1.42(wed by the w)-.25 F(ord)-.1 E F2(meter)108
-388.8 Q(s)-.1 E F0 3.329(,a)C .829(nd is added)-3.329 F F2 .829
-(on top of)3.329 F F0 .829
-(the terrain speci\214ed in the SDF data for the locations speci\214ed.)
-3.329 F .828(Be a)5.829 F -.1(wa)-.15 G(re).1 E 1.06(that each user)108
-400.8 R 1.061(-de\214ned terrain feature speci\214ed will be interprete\
-d as being 3-arc seconds in both latitude)-.2 F .282(and longitude.)108
-412.8 R .282(Features described in the user)5.282 F .281
-(-de\214ned terrain \214le that o)-.2 F -.15(ve)-.15 G .281(rlap pre).15
-F .281(viously de\214ned features in)-.25 F(the \214le are ignored by)
-108 424.8 Q F1(SPLA)2.5 E(T!)-.95 E F0(.)A F4(SIMPLE T)72 441.6 Q
-(OPOGRAPHIC MAP GENERA)-.197 E(TION)-1.04 E F0 .034(In certain situatio\
-ns it may be desirable to generate a topographic map of a re)108 453.6 R
-.035(gion without plotting co)-.15 F -.15(ve)-.15 G(rage).15 E .97
-(areas, line-of-sight paths, or generating obstruction reports.)108
-465.6 R .969(There are se)5.969 F -.15(ve)-.25 G .969(ral w).15 F .969
-(ays of doing this.)-.1 F .969(If one)5.969 F .162(wishes to generate a\
- topographic map illustrating the location of a transmitter and recei)
-108 477.6 R -.15(ve)-.25 G 2.662(rs).15 G .162(ite along with a)-2.662 F
-.139(brief te)108 489.6 R .139(xt report describing the locations and d\
-istances between the sites, the)-.15 F F2(-n)2.639 E F0 .138
-(switch should be in)2.639 F -.2(vo)-.4 G -.1(ke).2 G 2.638(da).1 G(s)
--2.638 E(follo)108 501.6 Q(ws:)-.25 E F3
-(splat -t tx_site -r rx_site -n -o topo_map.ppm)108 525.6 Q F0(If no te)
-108 549.6 Q(xt report is desired, then the)-.15 E F2(-N)2.5 E F0
-(switch is used:)2.5 E F3
-(splat -t tx_site -r rx_site -N -o topo_map.ppm)108 573.6 Q F0 .994(If \
-a topographic map centered about a single site out to a minimum speci\
-\214ed radius is desired instead, a)108 597.6 R
-(command similar to the follo)108 609.6 Q(wing can be used:)-.25 E F3
-(splat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o topo_map.ppm)
-108 633.6 Q F0(where -R speci\214es the minimum radius of the map in mi\
-les \(or kilometers if the)108 657.6 Q F2(-metric)2.5 E F0
-(switch is used\).)2.5 E .592(If the)108 681.6 R F2(-o)3.092 E F0 .592(\
-switch and output \214lename are omitted in these operations, topograph\
-ic output is written to a \214le)3.092 F(named)108 693.6 Q F2(map.ppm)
-2.5 E F0(in the current w)2.5 E(orking directory by def)-.1 E(ault.)-.1
-E(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F(December 2006)2.5 E(12)
-185.955 E EP
-%%Page: 13 13
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10.95
-/Times-Bold@0 SF(GEOREFERENCE FILE GENERA)72 84 Q(TION)-1.04 E F0 -.8
-(To)108 96 S .849(pographic, co).8 F -.15(ve)-.15 G .849(rage \().15 F
-/F2 10/Times-Italic@0 SF(-c)A F0 .849(\), and path loss contour \()B F2
-(-L)A F0 3.349(\)m)C .849(aps generated by)-3.349 F/F3 10/Times-Bold@0
-SF(SPLA)3.35 E(T!)-.95 E F0 .85(may be imported into)3.35 F F3(Xastir)
-108 108 Q F0 .176(\(X Amateur Station T)2.676 F .175
-(racking and Information Reporting\) softw)-.35 F .175
-(are by generating a georeference \214le)-.1 F(using)108 120 Q F3(SPLA)
-2.5 E(T!)-.95 E F0 -.55('s)C F2(-g)3.05 E(eo)-.1 E F0(switch:)2.5 E/F4
-10/Courier@0 SF
-(splat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o map.ppm)108
-144 Q F0 1.515(The georeference \214le generated will ha)108 168 R 1.815
--.15(ve t)-.2 H 1.516(he same base name as the).15 F F2(-o)4.016 E F0
-1.516(\214le speci\214ed, b)4.016 F 1.516(ut ha)-.2 F 1.816 -.15(ve a)
--.2 H F2(.g)6.666 E(eo)-.1 E F0 -.15(ex)108 180 S
-(tension, and permit proper interpretation and display of).15 E F3(SPLA)
-2.5 E(T!)-.95 E F0 1.1 -.55('s .)D(ppm graphics in).55 E F3(Xastir)2.5 E
-F0(softw)2.5 E(are.)-.1 E F1(GOOGLE MAP KML FILE GENERA)72 196.8 Q(TION)
--1.04 E F0 -2.15 -.25(Ke y)108 208.8 T .775
-(hole Markup Language \214les compatible with).25 F F3 .774
-(Google Earth)3.274 F F0 .774(may be generated by)3.274 F F3(SPLA)3.274
-E(T!)-.95 E F0 .774(when per)3.274 F(-)-.2 E
-(forming point-to-point analyses by in)108 220.8 Q -.2(vo)-.4 G
-(king the).2 E F2(-kml)2.5 E F0(switch:)2.5 E F4
-(splat -t wnjt -r kd2bd -kml)108 244.8 Q F0 .429
-(The KML \214le generated will ha)108 268.8 R .729 -.15(ve t)-.2 H .43(\
-he same \214lename structure as an Obstruction Report for the transmitt\
-er).15 F(and recei)108 280.8 Q -.15(ve)-.25 G 2.5(rs).15 G(ite names gi)
--2.5 E -.15(ve)-.25 G(n, e).15 E(xcept it will carry a)-.15 E F2(.kml)5
-E F0 -.15(ex)2.5 G(tension.).15 E 1.619(Once loaded into)108 304.8 R F3
-1.619(Google Earth)4.119 F F0 1.618(\(File --> Open\), the KML \214le w\
-ill annotate the map display with the)4.118 F .567
-(names of the transmitter and recei)108 316.8 R -.15(ve)-.25 G 3.067(rs)
-.15 G .568(ite locations.)-3.067 F .568(The vie)5.568 F .568
-(wpoint of the image will be from the position)-.25 F 1.317
-(of the transmitter site looking to)108 328.8 R -.1(wa)-.25 G 1.317
-(rds the location of the recei).1 F -.15(ve)-.25 G 4.916 -.55(r. T).15 H
-1.316(he point-to-point path between the).55 F .792(sites will be displ\
-ayed as a white line while the RF line-of-sight path will be displayed \
-in green.)108 340.8 R F3(Google)5.792 E(Earth)108 352.8 Q F0 1.844 -.55
-('s n)D -.2(av).55 G(ig).2 E .744(ation tools allo)-.05 F 3.243(wt)-.25
-G .743(he user to "\215y" around the path, identify landmarks, roads, a\
-nd other fea-)-3.243 F(tured content.)108 364.8 Q F1(DETERMIN)72 381.6 Q
--1.04(AT)-.219 G(ION OF ANTENN)1.04 E 2.738(AH)-.219 G(EIGHT ABO)-2.738
-E(VE A)-.548 E(VERA)-1.588 E(GE TERRAIN)-.602 E F3(SPLA)108 393.6 Q(T!)
--.95 E F0 .947(determines antenna height abo)3.447 F 1.248 -.15(ve a)
--.15 H -.15(ve)-.05 G .948(rage terrain \(HAA).15 F .948
-(T\) according to the procedure de\214ned by)-1.11 F .167
-(Federal Communications Commission P)108 405.6 R .167(art 73.313\(d\).)
--.15 F .166(According to this de\214nition, terrain ele)5.166 F -.25(va)
--.25 G .166(tions along).25 F .794(eight radials between 2 and 10 miles\
- \(3 and 16 kilometers\) from the site being analyzed are sampled and)
-108 417.6 R -2.25 -.2(av e)108 429.6 T .614(raged for each 45 de).2 F
-.613(grees of azimuth starting with T)-.15 F .613(rue North.)-.35 F .613
-(If one or more radials lie entirely o)5.613 F -.15(ve)-.15 G(r).15 E
--.1(wa)108 441.6 S .534(ter or o).1 F -.15(ve)-.15 G 3.034(rl).15 G .535
-(and outside the United States \(areas for which no USGS topograph)
--3.034 F 3.035(yd)-.05 G .535(ata is a)-3.035 F -.25(va)-.2 G .535
-(ilable\), then).25 F
-(those radials are omitted from the calculation of a)108 453.6 Q -.15
-(ve)-.2 G(rage terrain.).15 E .918(Note that SR)108 477.6 R .918(TM ele)
--.6 F -.25(va)-.25 G .918(tion data, unlik).25 F 3.418(eo)-.1 G .917
-(lder 3-arc second USGS data, e)-3.418 F .917(xtends be)-.15 F .917
-(yond the borders of the)-.15 F .866(United States.)108 489.6 R .867
-(Therefore, HAA)5.866 F 3.367(Tr)-1.11 G .867
-(esults may not be in full compliance with FCC P)-3.367 F .867
-(art 73.313\(d\) in areas)-.15 F
-(along the borders of the United States if the SDF \214les used by)108
-501.6 Q F3(SPLA)2.5 E(T!)-.95 E F0(are SR)2.5 E(TM-deri)-.6 E -.15(ve)
--.25 G(d.).15 E .162(When performing point-to-point terrain analysis,)
-108 525.6 R F3(SPLA)2.662 E(T!)-.95 E F0 .162
-(determines the antenna height abo)2.662 F .461 -.15(ve a)-.15 H -.15
-(ve)-.05 G .161(rage ter).15 F(-)-.2 E .407(rain only if enough topogra\
-phic data has already been loaded by the program to perform the point-t\
-o-point)108 537.6 R 3.712(analysis. In)108 549.6 R 1.211(most cases, th\
-is will be true, unless the site in question does not lie within 10 mil\
-es of the)3.712 F(boundary of the topograph)108 561.6 Q 2.5(yd)-.05 G
-(ata in memory)-2.5 E(.)-.65 E .491
-(When performing area prediction analysis, enough topograph)108 585.6 R
-2.991(yd)-.05 G .492(ata is normally loaded by)-2.991 F F3(SPLA)2.992 E
-(T!)-.95 E F0 .492(to per)2.992 F(-)-.2 E .807(form a)108 597.6 R -.15
-(ve)-.2 G .807(rage terrain calculations.).15 F .807
-(Under such conditions,)5.807 F F3(SPLA)3.307 E(T!)-.95 E F0 .807
-(will pro)3.307 F .807(vide the antenna height abo)-.15 F -.15(ve)-.15 G
--2.25 -.2(av e)108 609.6 T .203(rage terrain as well as the a).2 F -.15
-(ve)-.2 G .203(rage terrain abo).15 F .503 -.15(ve m)-.15 H .203
-(ean sea le).15 F -.15(ve)-.25 G 2.704(lf).15 G .204
-(or azimuths of 0, 45, 90, 135, 180, 225,)-2.704 F .162(270, and 315 de)
-108 621.6 R .162
-(grees, and include such information in the generated site report.)-.15
-F .161(If one or more of the eight)5.161 F 1.004(radials surv)108 633.6
-R -.15(ey)-.15 G 1.004(ed f).15 F 1.004(all o)-.1 F -.15(ve)-.15 G 3.504
-(rw).15 G(ater)-3.604 E 3.504(,o)-.4 G 3.504(ro)-3.504 G -.15(ve)-3.654
-G 3.504(rr).15 G -.15(eg)-3.504 G 1.004(ions for which no SDF data is a)
-.15 F -.25(va)-.2 G(ilable,).25 E F3(SPLA)3.504 E(T!)-.95 E F0(reports)
-3.505 E F2(No)3.505 E -.92(Te)108 645.6 S(rr).92 E(ain)-.15 E F0
-(for the radial paths af)2.5 E(fected.)-.25 E F1
-(RESTRICTING THE MAXIMUM SIZE OF AN AN)72 662.4 Q(AL)-.219 E
-(YSIS REGION)-1.007 E F3(SPLA)108 674.4 Q(T!)-.95 E F0 .269(reads SDF \
-\214les as needed into a series of memory pages or "slots" within the s\
-tructure of the pro-)2.77 F 2.774(gram. Each)108 686.4 R .274
-("slot" holds one SDF \214le representing a one de)2.774 F .275
-(gree by one de)-.15 F .275(gree re)-.15 F .275(gion of terrain.)-.15 F
-(A)5.275 E F2(#de\214ne)2.775 E(MAXSLO)108 698.4 Q(TS)-.4 E F0 .786
-(statement in the \214rst se)3.286 F -.15(ve)-.25 G .785(ral lines of)
-.15 F F2(splat.cpp)3.285 E F0 .785(sets the maximum number of "slots" a)
-3.285 F -.25(va)-.2 G(ilable).25 E .103(for holding topograph)108 710.4
-R 2.603(yd)-.05 G 2.603(ata. It)-2.603 F .104
-(also sets the maximum size of the topographic maps generated by)2.604 F
-F3(SPLA)2.604 E(T!)-.95 E F0(.)A(MAXSLO)108 722.4 Q .242
-(TS is set to 9 by def)-.4 F 2.742(ault. If)-.1 F F3(SPLA)2.742 E(T!)
--.95 E F0 .242(produces a se)5.242 F .242(gmentation f)-.15 F .241
-(ault on start-up with this def)-.1 F(ault,)-.1 E(KD2BD Softw)72 768 Q
-121.625(are 20)-.1 F(December 2006)2.5 E(13)185.955 E EP
-%%Page: 14 14
-%%BeginPageSetup
-BP
-%%EndPageSetup
-/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
-(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .91
-(it is an indication that not enough RAM and/or virtual memory \(sw)108
-84 R .911(ap space\) is a)-.1 F -.25(va)-.2 G .911(ilable to run).25 F
-/F1 10/Times-Bold@0 SF(SPLA)3.411 E(T!)-.95 E F0 .002
-(with the number of MAXSLO)108 96 R .002(TS speci\214ed.)-.4 F .001
-(In situations where a)5.002 F -.25(va)-.2 G .001(ilable memory is lo)
-.25 F 1.301 -.65(w, M)-.25 H(AXSLO).65 E .001(TS may)-.4 F .019(be redu\
-ced to 4 with the understanding that this will greatly limit the maximu\
-m re)108 108 R(gion)-.15 E F1(SPLA)2.519 E(T!)-.95 E F0 .019
-(will be able)2.519 F .624(to analyze.)108 120 R .624(If 118 me)5.624 F
--.05(ga)-.15 G .624(bytes or more of total memory \(sw).05 F .623
-(ap space plus RAM\) is a)-.1 F -.25(va)-.2 G .623(ilable, then MAXS-)
-.25 F(LO)108 132 Q .102(TS may be increased to 16.)-.4 F .103
-(This will permit operation o)5.103 F -.15(ve)-.15 G 2.603(ra4).15 G
-(-de)-2.603 E .103(gree by 4-de)-.15 F .103(gree re)-.15 F .103
-(gion, which is suf-)-.15 F .426
-(\214cient for single antenna heights in e)108 144 R .426
-(xcess of 10,000 feet abo)-.15 F .725 -.15(ve m)-.15 H .425(ean sea le)
-.15 F -.15(ve)-.25 G .425(l, or point-to-point distances).15 F(of o)108
-156 Q -.15(ve)-.15 G 2.5(r1).15 G(000 miles.)-2.5 E/F2 10.95
-/Times-Bold@0 SF(ADDITION)72 172.8 Q(AL INFORMA)-.219 E(TION)-1.04 E F0
-.332(The latest ne)108 184.8 R .332(ws and information re)-.25 F -.05
-(ga)-.15 G(rding).05 E F1(SPLA)2.832 E(T!)-.95 E F0(softw)2.832 E .332
-(are is a)-.1 F -.25(va)-.2 G .332(ilable through the of).25 F(\214cial)
--.25 E F1(SPLA)2.833 E(T!)-.95 E F0(soft-)2.833 E -.1(wa)108 196.8 S
-(re web page located at:).1 E/F3 10/Times-Italic@0 SF(http://www)2.5 E
-(.qsl.net/kd2bd/splat.html)-.74 E F0(.)A F2 -.548(AU)72 213.6 S(THORS)
-.548 E F0(John A. Magliacane, KD2BD <)108 225.6 Q F3(kd2bd@amsat.or)A(g)
--.37 E F0(>)A(Creator)144 237.6 Q 2.5(,L)-.4 G(ead De)-2.5 E -.15(ve)
--.25 G(loper).15 E(Doug McDonald <)108 254.4 Q F3(mcdonald@scs.uiuc.edu)
-A F0(>)A(Longle)144 266.4 Q(y-Rice Model inte)-.15 E(gration)-.15 E
-(Ron Bentle)108 283.2 Q 2.5(y<)-.15 G F3 -.45(ro)-2.5 G(nbentle).45 E
-(y@earthlink.net)-.3 E F0(>)A
-(Fresnel Zone plotting and clearance determination)144 295.2 Q
-(KD2BD Softw)72 768 Q 121.625(are 20)-.1 F(December 2006)2.5 E(14)
-185.955 E EP
-%%Trailer
-end
-%%EOF
--- /dev/null
+#!/bin/bash
+# This script builds the man page, pdf, and postscript
+# and text documentation from the groff source "splat.man".
+echo -n "Creating postscript file... "
+groff -e -T ps -man splat.man > ../postscript/splat.ps
+echo
+echo -n "Creating man page... "
+groff -e -T ascii -man splat.man > splat.1
+echo
+echo -n "Creating text file... "
+ul -t dumb splat.1 > ../text/splat.txt
+echo
+echo -n "Creating pdf file... "
+ps2pdf ../postscript/splat.ps ../pdf/splat.pdf
+echo
+echo "Done!"
--- /dev/null
+SPLAT!(1) KD2BD Software SPLAT!(1)
+
+
+
+N\bNO\bOM\bMB\bBR\bRE\bE
+ splat - An RF S\bSignal P\bPropagation, L\bLoss, A\bAnd T\bTerrain anal-
+ ysis tool S\bSP\bPL\bLA\bAT\bT!\b!
+
+ splat - Es una herramienta para el anlisis de Propagacin
+ de Seales RF, Prdidas, y caractersticas del Terreno
+
+S\bSI\bIN\bNO\bOP\bPS\bSI\bIS\bS
+ splat [-t _\bs_\bi_\bt_\bi_\bo_\b__\bt_\br_\ba_\bn_\bs_\bm_\bi_\bs_\bo_\br_\b._\bq_\bt_\bh] [-r _\bs_\bi_\bt_\bi_\bo_\b__\br_\be_\bc_\be_\bp_\bt_\bo_\br_\b._\bq_\bt_\bh]
+ [-c _\br_\bx _\ba_\bl_\bt_\bu_\br_\ba _\bd_\be _\bl_\ba _\ba_\bn_\bt_\be_\bn_\ba _\bp_\ba_\br_\ba _\be_\bl _\ba_\bn_\bl_\bi_\bs_\bi_\bs _\bd_\be _\bc_\bo_\bb_\be_\br_\bt_\bu_\br_\ba
+ _\bL_\bO_\bS _\b(_\bp_\bi_\be_\bs_\b/_\bm_\be_\bt_\br_\bo_\bs_\b) _\b(_\bf_\bl_\bo_\bt_\ba_\bn_\bt_\be_\b)] [-L _\br_\bx _\ba_\bl_\bt_\bu_\br_\ba _\bd_\be _\bl_\ba _\ba_\bn_\bt_\be_\bn_\ba
+ _\bp_\ba_\br_\ba _\be_\bl _\ba_\bn_\bl_\bi_\bs_\bi_\bs _\bd_\be _\bc_\bo_\bb_\be_\br_\bt_\bu_\br_\ba _\bL_\bo_\bn_\bg_\bl_\be_\by_\b-_\bR_\bi_\bc_\be _\b(_\bp_\bi_\be_\bs_\b/_\bm_\be_\bt_\br_\bo_\bs_\b)
+ _\b(_\bf_\bl_\bo_\bt_\ba_\bn_\bt_\be_\b)] [-p _\bp_\be_\br_\bf_\bi_\bl_\b__\bt_\be_\br_\br_\be_\bn_\bo_\b._\be_\bx_\bt] [-e _\bp_\be_\br_\bf_\bi_\bl_\b__\be_\bl_\be_\bv_\ba_\b-
+ _\bc_\bi_\bo_\bn_\b._\be_\bx_\bt] [-h _\bp_\be_\br_\bf_\bi_\bl_\b__\ba_\bl_\bt_\bu_\br_\ba_\b._\be_\bx_\bt] [-H _\bp_\be_\br_\bf_\bi_\bl_\b__\ba_\bl_\bt_\bu_\br_\ba_\b__\bn_\bo_\br_\bm_\ba_\bl_\b-
+ _\bi_\bz_\ba_\bd_\ba_\b._\be_\bx_\bt] [-l _\bp_\be_\br_\bf_\bi_\bl_\b__\bL_\bo_\bn_\bg_\bl_\be_\by_\b-_\bR_\bi_\bc_\be_\b._\be_\bx_\bt] [-o _\bn_\bo_\bm_\b-
+ _\bb_\br_\be_\b__\ba_\br_\bc_\bh_\bi_\bv_\bo_\b__\bm_\ba_\bp_\ba_\b__\bt_\bo_\bp_\bo_\bg_\br_\bf_\bi_\bc_\bo_\b._\bp_\bp_\bm] [-b _\ba_\br_\bc_\bh_\bi_\bv_\bo_\b__\bl_\bm_\bi_\bt_\be_\bs_\b__\bc_\ba_\br_\b-
+ _\bt_\bo_\bg_\br_\ba_\bf_\bi_\bc_\bo_\bs_\b._\bd_\ba_\bt] [-s _\bb_\ba_\bs_\be_\b__\bd_\ba_\bt_\bo_\bs_\b__\bs_\bi_\bt_\bi_\bo_\bs_\b/_\bc_\bi_\bu_\bd_\ba_\bd_\be_\bs_\b._\bd_\ba_\bt] [-d
+ _\br_\bu_\bt_\ba_\b__\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\bi_\bo_\b__\bs_\bd_\bf] [-m _\br_\ba_\bd_\bi_\bo _\bm_\bu_\bl_\bt_\bi_\bp_\bl_\bi_\bc_\ba_\bd_\bo_\br _\bt_\bi_\be_\br_\br_\ba
+ _\b(_\bf_\bl_\bo_\bt_\ba_\bn_\bt_\be_\b)] [-f _\bf_\br_\be_\bq_\bu_\be_\bn_\bc_\bi_\ba _\b(_\bM_\bH_\bz_\b) _\bp_\ba_\br_\ba _\bc_\bl_\bc_\bu_\bl_\bo_\bs _\bd_\be _\bl_\ba _\bz_\bo_\bn_\ba
+ _\bd_\be _\bF_\br_\be_\bs_\bn_\be_\bl _\b(_\bf_\bl_\bo_\bt_\ba_\bn_\bt_\be_\b)] [-R _\bm_\bx_\bi_\bm_\bo _\br_\ba_\bd_\bi_\bo _\bd_\be _\bc_\bo_\bv_\be_\br_\bt_\bu_\br_\ba _\b(_\bm_\bi_\bl_\b-
+ _\bl_\ba_\bs_\b/_\bk_\bi_\bl_\bm_\be_\bt_\br_\bo_\bs_\b) _\b(_\bf_\bl_\bo_\bt_\ba_\bn_\bt_\be_\b)] [-dB _\bm_\bx_\bi_\bm_\bo _\bc_\bo_\bn_\bt_\bo_\br_\bn_\bo _\bd_\be _\ba_\bt_\be_\bn_\b-
+ _\bu_\ba_\bc_\bi_\bn _\ba _\bp_\br_\be_\bs_\be_\bn_\bt_\ba_\br _\bs_\bo_\bb_\br_\be _\bu_\bn _\bm_\ba_\bp_\ba _\bd_\be _\bp_\br_\bd_\bi_\bd_\ba_\bs _\bp_\bo_\br _\bt_\br_\ba_\by_\be_\bc_\bt_\bo_\br_\bi_\ba
+ _\b(_\b8_\b0_\b-_\b2_\b3_\b0 _\bd_\bB_\b)] [-fz _\bp_\bo_\br_\bc_\be_\bn_\bt_\ba_\bj_\be _\bd_\be_\bs_\bp_\be_\bj_\ba_\bd_\bo _\bd_\be _\bl_\ba _\bz_\bo_\bn_\ba _\bd_\be _\bF_\br_\be_\bs_\b-
+ _\bn_\be_\bl _\b(_\bd_\be_\bf_\ba_\bu_\bl_\bt _\b= _\b6_\b0_\b)] [-plo _\ba_\br_\bc_\bh_\bi_\bv_\bo_\b__\bs_\ba_\bl_\bi_\bd_\ba_\b__\bp_\br_\bd_\bi_\b-
+ _\bd_\ba_\bs_\b__\bp_\bo_\br_\b__\bt_\br_\ba_\by_\be_\bc_\bt_\bo_\br_\bi_\ba_\b._\bt_\bx_\bt] [-pli _\ba_\br_\bc_\bh_\bi_\bv_\bo_\b__\be_\bn_\bt_\br_\ba_\bd_\ba_\b__\bp_\br_\bd_\bi_\b-
+ _\bd_\ba_\bs_\b__\bp_\bo_\br_\b__\bt_\br_\ba_\by_\be_\bc_\bt_\bo_\br_\bi_\ba_\b._\bt_\bx_\bt] [-udt _\ba_\br_\bc_\bh_\bi_\bv_\bo_\b__\bt_\be_\br_\b-
+ _\br_\be_\bn_\bo_\b__\bd_\be_\bf_\bi_\bn_\bi_\bd_\bo_\b__\bp_\bo_\br_\b__\be_\bl_\b__\bu_\bs_\bu_\ba_\br_\bi_\bo_\b._\bd_\ba_\bt] [-n] [-N] [-nf] [-ngs]
+ [-geo] [-kml] [-metric]
+
+D\bDE\bES\bSC\bCR\bRI\bIP\bPC\bCI\bIN\bN
+ S\bSP\bPL\bLA\bAT\bT!\b! es una poderosa herramienta para el anlisis de
+ terreno y propagacin RF cubriendo el espectro entre 20
+ Megahertz y 20 Gigahertz. S\bSP\bPL\bLA\bAT\bT!\b! es Software Libre y est
+ diseado para operar en escritorios Unix y basados en
+ Linux. La redistribucin y/ modificacin est permitida bajo
+ los trminos de la licencia pblica general GNU segn lo pub-
+ licado por la Fundacin de Software Libre, versin 2. La
+ adopcin del cdigo fuente de S\bSP\bPL\bLA\bAT\bT!\b! en aplicaciones propi-
+ etarias o de fuente-cerrada es una violacin de esta
+ licencia, y esta e\bes\bst\btr\bri\bic\bct\bta\bam\bme\ben\bnt\bte\be prohibida.
+
+ S\bSP\bPL\bLA\bAT\bT!\b! es distribudo con la esperanza de que sea til, pero
+ SIN NINGUNA GARANTA, an la garanta implcita de COMERCIAL-
+ IZACIN de la APLICACIN PARA UN PROPSITO PARTICULAR. Vea
+ la licencia GNU para ms detalles.
+
+I\bIN\bNT\bTR\bRO\bOD\bDU\bUC\bCC\bCI\bIN\bN
+ Las aplicaciones de S\bSP\bPL\bLA\bAT\bT!\b! incluyen la visualizacin,
+ diseo, y anlisis de enlaces de redes inalmbricas WAN,
+ sistemas de radio comunicaciones comerciales y aficionados
+ sobre los 20 megahertz, enlaces microonda, estudios de
+ interferencia y coordinacin de frecuencias, y determinacin
+ del contorno de cobertura de las regiones de radio y tele-
+ visin terrestres anlogas y digitales.
+
+ S\bSP\bPL\bLA\bAT\bT!\b! proporciona datos de ingeniera RF del sitio, tales
+ como distancias sobre el arco terrestre y azimut entre
+ sitios de transmisin y recepcin, ngulos de elevacin de la
+ antena (uptilt), ngulos de depresin (downtilt), altura de
+ la antena sobre nivel del mar, altura de la antena sobre
+ el promedio del terreno, azimut, distancias y elevaciones
+ para determinar obstrucciones, Atenuaciones de trayectoria
+ Longley-Rice, e intensidad de seal recibida, Adicional-
+ mente, los requisitos mnimos necesarios de altura de las
+ antenas para establecer trayectorias de comunicacin de
+ lnea-de-vista sin obstrucciones debido al terreno, la
+ primera zona de Fresnel, y cualquier porcentaje definido
+ por el usuario de la primera zona de Fresnel.
+
+ S\bSP\bPL\bLA\bAT\bT!\b! produce informes, grficos, y mapas topogrficos
+ altamente detallados y cuidadosamente descritos que pre-
+ sentan las trayectorias de lnea-de-vista, contornos
+ regionales de prdidas por trayectoria y contornos de
+ intensidad de seal a travs de los cuales se puede determi-
+ nar la prediccin del rea de cobertura de sistemas de
+ transmisores y repetidoras. Al realizar anlisis de lnea
+ de vista y prdidas Longley-Rice cuando se emplean mltiples
+ sitios de transmisores o repetidores, S\bSP\bPL\bLA\bAT\bT!\b! determina las
+ reas de cobertura individuales y mutuas dentro de la red
+ especificada.
+
+ Simplemente tipee splat en la consola de comandos, esto
+ retornar un resumen de las opciones de lnea de comando de
+ S\bSP\bPL\bLA\bAT\bT!\b!:
+
+
+
+ --==[ SPLAT! v1.2.1 Available Options...
+ ]==--
+
+ -t txsite(s).qth ( max 4 con -c, max 30 con -L)
+ -r rxsite.qth (sitio de recepcin)
+ -c grafica la cobertura del TX(s) (antena RX a X
+ pies/metros SNT)
+ -L grafica prdidas por trayectoria del TX (RX a X
+ pies/metros SNT)
+ -s nombre de archivo(s) de ciudades/sitios a importar
+ (max 5)
+ -b nombre de archivo(s) de lmites cartogrficos a importar
+ (max 5)
+ -p nombre de archivo para graficar el perfil del terreno
+ -e nombre de archivo para graficar la elevacin del ter-
+ reno
+ -h nombre de archivo para graficar la altura del terreno
+ -H nombre de archivo para graficar la altura normalizada
+ del terreno
+ -l nombre de archivo para graficar el modelo Longley-Rice
+ -o nombre de archivo para generar el mapa topogrfico
+ (.ppm)
+ -u nombre del archivo del terreno definido-por-el-usuario
+ a importar
+ -d directorio que contiene los archivos sdf (reemplaza
+ ~/.splat_path)
+ -m multiplicador del radio de la tierra
+ -n no grafica las rutas de LDV in mapas .ppm
+ -N no produce reportes innecesarios del sitio reportes
+ de obstruccin
+ -f frecuencia para el clculo de la zona de Fresnel (MHz)
+ -R modifica el rango por defecto para -c -L (millas/kil-
+ metros)
+ -db mximo contorno de prdidas por trayectoria (80-230
+ dB)
+ -nf no grafica la zona de Fresnel en los grficos de
+ altura
+ -fz porcentaje de despeje de la zona de Fresnel (default
+ = 60)
+ -ngs muestra topografa de escala de grises en blanco
+ (archivos .ppm)
+ -erp valor ERP en lugar del declarado en el archivo .lrp
+ (Watts)
+ -pli nombre del archivo de entrada de prdidas-por-trayec-
+ toria
+ -plo nombre del archivo de salida de prdidas-por-trayec-
+ toria
+ -udt nombre del archivo de entrada de terreno definido-
+ por-el-usuario
+ -kml genera archivo compatible Google Earth .kml(enlaces
+ punto-a-punto)
+ -geo genera un archivo Xastir de georeferencia .geo (con
+ salida .ppm)
+ -metric usa unidades mtricas en lugar de imperiales (I/O
+ del usuario)
+
+
+F\bFI\bIC\bCH\bHE\bER\bRO\bOS\bS D\bDE\bE E\bEN\bNT\bTR\bRA\bAD\bDA\bA
+ S\bSP\bPL\bLA\bAT\bT!\b! es una aplicacin manejada por linea de comandos
+ terminal de textos (shell), y lee los datos de entrada a
+ travs de un nmero de ficheros de datos. Algunos archivos
+ son obligatorios para la apropiada ejecucin del programa,
+ mientras que otros son opcionales. Los archivos obligato-
+ rios incluyen los modelos topogrficos 3-arco segundo en la
+ forma de archivos de datos de SPLAT (archivos SDF),
+ archivos de localizacin del sitio (archivos QTH), y
+ archivos de parmetros para el modelo Longley-Rice
+ (archivos LRP). Los archivos opcionales incluyen archivos
+ de localizacin de ciudades/sitios, archivos de lmites car-
+ togrficos, archivos de terreno definidos por el usuario,
+ archivos de entrada de prdidas-por-trayectoria, archivos
+ de patrones de radiacin de antenas, y archivos de
+ definicin de color.
+
+F\bFI\bIC\bCH\bHE\bER\bRO\bOS\bS D\bDE\bE D\bDA\bAT\bTO\bOS\bS S\bSP\bPL\bLA\bAT\bT
+ S\bSP\bPL\bLA\bAT\bT!\b! importa los datos topogrficos desde los ficheros de
+ datos SPLAT (SDFs). Estos archivos se pueden generar desde
+ varias fuentes de informacin. En los Estados Unidos, los
+ ficheros de datos SPLAT se pueden generar a travs de la
+ U.S. Geological Survey Digital Elevation Models (DEMs)
+ usando la herramienta usgs2sdf incluida con S\bSP\bPL\bLA\bAT\bT!\b!. Los
+ modelos de elevacin digital USGS compatibles con esta
+ utilidad pueden ser descargados de:
+ _\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/.
+
+ Una resolucin significativamente mejor se puede obtener
+ con el uso de los modelos digitales de elevacin versin 2
+ SRTM-3. Estos modelos son el resultado de la misin
+ topografca del radar espacial Shuttle STS-99, y estn
+ disponibles para la mayora de las regiones pobladas de la
+ tierra. Los ficheros de datos SPLAT pueden ser generados
+ desde los datos SRTM usando la herramienta incluida
+ srtm2sdf. Los archivo SRTM-3 versin 2 se pueden obtener a
+ travs de FTP annimo desde:
+ _\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/
+
+ La utilidad s\bst\btr\brm\bm2\b2s\bsd\bdf\bf tambin puede ser usada para convertir
+ los datos SRTM 3-arco segundo en formato Band Interleaved
+ by Line (.BIL) para usar con S\bSP\bPL\bLA\bAT\bT!\b!. Estos datos estn
+ disponibles va web en: _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bs_\be_\ba_\bm_\bl_\be_\bs_\bs_\b._\bu_\bs_\bg_\bs_\b._\bg_\bo_\bv_\b/_\bw_\be_\bb_\b-
+ _\bs_\bi_\bt_\be_\b/_\bs_\be_\ba_\bm_\bl_\be_\bs_\bs_\b/
+
+ los datos Band Interleaved by Line deben ser descargados
+ en una manera especfica para ser compatible con s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf y
+ S\bSP\bPL\bLA\bAT\bT!\b!. por favor consulte la documentacin s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf's para
+ instrucciones sobre la descarga de datos topogrficos .BIL
+ a travs del Sitio Web USGS's Seamless.
+
+ A pesar de la exactitud ms alta que los datos SRTM ofre-
+ cen, existen algunos vacos en los conjuntos de datos.
+ Cuando se detectan estos vacos, la utilidad s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf los
+ substituye por los datos encontrados en los archivos SDF
+ existentes (que presumiblemente fueron creados de datos
+ anteriores de la USGS con la utilidad u\bus\bsg\bgs\bs2\b2s\bsd\bdf\bf). Si los
+ datos SDF, USGS-derivados no estn disponibles, los vacos
+ se reemplazan con el promedio de los pixeles adyacentes, o
+ reemplazo directo.
+
+ Los ficheros de datos de SPLAT contienen valores enteros
+ de las elevaciones topogrficas (en metros) referenciados
+ al nivel del mar para regiones de la tierra de 1-grado por
+ 1-grado con una resolucin de 3-arco segundos. Los archivos
+ SDF pueden ser ledos desde el formato estndar (_\b._\bs_\bd_\bf) gen-
+ erado por las utilidades u\bus\bsg\bgs\bs2\b2s\bsd\bdf\bf y s\bsr\brt\btm\bm2\b2s\bsd\bdf\bf, en formato
+ comprimido bzip2 (.sdf .bz2). Puesto que los archivos sin
+ comprimir se pueden procesar ligeramente ms rpido que los
+ archivos comprimidos, S\bSP\bPL\bLA\bAT\bT!\b! busca los datos SDF necesar-
+ ios en formato sin comprimir primero. Si los datos sin
+ comprimir no pueden ser localizados, S\bSP\bPL\bLA\bAT\bT!\b! entonces busca
+ los datos en formato comprimido bzip2. Si tampoco se
+ pueden encontrar los archivos SDF comprimidos para la
+ regin solicitada, S\bSP\bPL\bLA\bAT\bT!\b! asume que la regin es el ocano, y
+ asignar una elevacin del nivel del mar a estas reas.
+
+ Esta caracterstica de S\bSP\bPL\bLA\bAT\bT!\b! permite realizar el anlisis
+ de trayectorias no solamente sobre la tierra, sino tambin
+ entre las reas costeras no representadas por los datos del
+ Modelo de Elevacin Digital. Sin embargo, este compor-
+ tamiento de S\bSP\bPL\bLA\bAT\bT!\b! resalta la importancia de tener todos
+ los archivos SDF requeridos para la regin a ser analizada,
+ para as obtener resultados significativos.
+
+A\bAR\bRC\bCH\bHI\bIV\bVO\bOS\bS D\bDE\bE L\bLO\bOC\bCA\bAL\bLI\bIZ\bZA\bAC\bCI\bIN\bN D\bDE\bEL\bL S\bSI\bIT\bTI\bIO\bO (\b(Q\bQT\bTH\bH)\b)
+ S\bSP\bPL\bLA\bAT\bT!\b! SPLAT! importa la informacin de la localizacin de
+ los sitios del transmisor y del receptor analizados por el
+ programa de los archivos ASCII que tienen una extensin
+ _\b._\bq_\bt_\bh. Los archivos QTH contienen el nombre del sitio, la
+ latitud del sitio (positiva al norte del ecuador, negativa
+ al sur), la longitud del sitio (en grados oeste W de 0 a
+ 360 grados), y; La altura de la antena del sitio sobre el
+ nivel del suelo (AGL), cada uno separado por un caracter
+ de salto-de-lnea. La altura de la antena se asume a ser
+ especificada en pies a menos que sea seguida por la letra
+ _\bm o de la palabra _\bm_\be_\bt_\be_\br_\bs en maysculas minsculas. La
+ informacin de la latitud y de la longitud se puede expre-
+ sar en formato decimal (74.6889) en formato grados, min-
+ utos, segundos (DMS) (74 41 20.0).
+
+ Por ejemplo, un archivo de localizacin de sitio que
+ describa la estacin de televisin WNJT-DT, Trenton, NJ
+ (_\bw_\bn_\bj_\bt_\b-_\bd_\bt_\b._\bq_\bt_\bh) se puede leer como sigue:
+
+
+ WNJT-DT
+ 40.2828
+ 74.6864
+ 990.00
+
+
+ Cada sitio de transmisor y receptor analizado por S\bSP\bPL\bLA\bAT\bT!\b!
+ debe ser representado por su propio archivo de la local-
+ izacin de sitio (QTH).
+
+A\bAR\bRC\bCH\bHI\bIV\bVO\bOS\bS D\bDE\bE P\bPA\bAR\bRM\bME\bET\bTR\bRO\bOS\bS L\bLO\bON\bNG\bGL\bLE\bEY\bY-\b-R\bRI\bIC\bCE\bE (\b(L\bLR\bRP\bP)\b)
+ Los archivos de datos de parmetros Longley-Rice son
+ requeridos por S\bSP\bPL\bLA\bAT\bT!\b! para determinar ls prdidas por
+ trayectoria RF ya sea en el modo punto-a-punto prediccin
+ de rea. Los datos de parmetros para el modelo Longley-Rice
+ desde archivos que tienen el mismo nombre base del archivo
+ QTH del sitio del transmisor, pero con extensin _\b._\bl_\br_\bp. Los
+ Archivos S\bSP\bPL\bLA\bAT\bT!\b! LRP comparte el siguiente formato (_\bw_\bn_\bj_\bt_\b-
+ _\bd_\bt_\b._\bl_\br_\bp):
+
+
+ 15.000 ; Earth Dielectric Constant (Relative per-
+ mittivity)
+ 0.005 ; Earth Conductivity (Siemens per meter)
+ 301.000 ; Atmospheric Bending Constant (N-units)
+ 647.000 ; Frequency in MHz (20 MHz to 20 GHz)
+ 5 ; Radio Climate (5 = Continental Temper-
+ ate)
+ 0 ; Polarization (0 = Horizontal, 1 = Verti-
+ cal)
+ 0.50 ; Fraction of situations (50% of loca-
+ tions)
+ 0.90 ; Fraction of time (90% of the time)
+ 46000.0 ; ERP in Watts (optional)
+
+
+ Si un archivo LRP correspondiente al archivo QTH del sitio
+ de transmisin no puede ser encontrado, S\bSP\bPL\bLA\bAT\bT!\b! explorar el
+ directorio de trabajo actual buscando el archivo
+ "splat.lrp". Si este archivo tampoco puede ser encontrado,
+ entonces los parmetros por defecto enumerados arriba sern
+ asignados por S\bSP\bPL\bLA\bAT\bT!\b! y un archivo correspondiente
+ "splat.lrp" conteniendo estos parmetros por defecto ser
+ escrito al directorio actual de trabajo. El archivo
+ "splat.lrp" generado se puede editar de acuerdo a las
+ necesidades del usuario.
+
+ Las constantes dielctricas tpicas de la tierra y sus val-
+ ores de conductividad son los siguientes:
+
+
+ Dielectric Constant Conductiv-
+ ity
+ Salt water : 80 5.000
+ Good ground : 25 0.020
+ Fresh water : 80 0.010
+ Marshy land : 12 0.007
+ Farmland, forest : 15 0.005
+ Average ground : 15 0.005
+ Mountain, sand : 13 0.002
+ City : 5 0.001
+ Poor ground : 4 0.001
+
+
+ Los cdigos de Clima de Radio usados por S\bSP\bPL\bLA\bAT\bT!\b! son los
+ siguientes:
+
+
+ 1: Equatorial (Congo)
+ 2: Continental Subtropical (Sudan)
+ 3: Maritime Subtropical (West coast of Africa)
+ 4: Desert (Sahara)
+ 5: Continental Temperate
+ 6: Maritime Temperate, over land (UK and west
+ coasts of US & EU)
+ 7: Maritime Temperate, over sea
+
+
+ El clima templado continental es comn a las grandes masas
+ de la tierra en la zona templada, tal como los Estados
+ Unidos. Para trayectorias inferiores a 100 kilmetros, es
+ poca la diferencia entre los climas templados continen-
+ tales y martimos.
+
+ Los parmetros sptimo y octavo en el archivo _\b._\bl_\br_\bp corre-
+ sponden al anlisis estadstico proporcionado por el modelo
+ Longley-Rice. En este ejemplo, S\bSP\bPL\bLA\bAT\bT!\b! devolver la mxima
+ prdida de trayectoria que ocurre el 50% del tiempo (frac-
+ cin del tiempo) en el 90% de las situaciones (fraccin de
+ situaciones). Esto es a menudo denotado como F(50,90) en
+ los estudios Longley_Rice. En los Estados Unidos un crite-
+ rio F(50,90) es tpicamente usado para televisin digital
+ (8-level VSB modulation), mientras que F(50,50) es usado
+ para radiodifusin analgica (VSB-AM+NTSC).
+
+ Para mayor informacin de esos parmetros, puede visitar:
+ _\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
+ _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bs_\bo_\bf_\bt_\bw_\br_\bi_\bg_\bh_\bt_\b._\bc_\bo_\bm_\b/_\bf_\ba_\bq_\b/_\be_\bn_\bg_\bi_\bn_\be_\be_\br_\bi_\bn_\bg_\b/_\bp_\br_\bo_\bp_\b__\bl_\bo_\bn_\bg_\b-
+ _\bl_\be_\by_\b__\br_\bi_\bc_\be_\b._\bh_\bt_\bm_\bl
+
+ El parmetro final en el archivo _\b._\bl_\br_\bp corresponde a la
+ potencia efectiva radiada, y es opcional. Si esta es
+ incluida en el archivo seal y los contornos de niveles de
+ intensidad de campo cuando se realicen los estudios Long-
+ ley-rice. Si el parmetro es omitido, se computan las prdi-
+ das por trayectoria en su lugar. El ERP provisto en el
+ archivo _\b._\bl_\br_\bp puede ser invalidado usando la opcin S\bSP\bPL\bLA\bAT\bT!\b!
+ de lnea-de-comando _\b-_\be_\br_\bp sin tener que editar el archivo
+ _\b._\bl_\br_\bp para conseguir el mismo resultado.
+
+A\bAR\bRC\bCH\bHI\bIV\bVO\bOS\bS D\bDE\bE L\bLO\bOC\bCA\bAL\bLI\bIZ\bZA\bAC\bCI\bIN\bN D\bDE\bE C\bCI\bIU\bUD\bDA\bAD\bDE\bES\bS
+ Los nombres y las localizaciones de ciudades, sitios de la
+ torre, u otros puntos de inters se pueden importar y
+ trazar en los mapas topogrficos generados por S\bSP\bPL\bLA\bAT\bT!\b!.
+ S\bSP\bPL\bLA\bAT\bT!\b! importa los nombres de ciudades y localizaciones de
+ los archivos ASCII que contienen el nombre, latitud y lon-
+ gitud de la localizacin de inters. Cada campo es separado
+ por una coma. Cada expediente es separado por un caracter
+ de salto-de-linea. Al igual que con los archivos _\b._\bq_\bt_\bh, la
+ informacin de la latitud y la longitud se puede ingresar
+ en formato decimal en formato de grados, minutos, segun-
+ dos (DMS).
+
+ Por ejemplo (_\bc_\bi_\bt_\bi_\be_\bs_\b._\bd_\ba_\bt):
+
+ Teaneck, 40.891973, 74.014506
+ Tenafly, 40.919212, 73.955892
+ Teterboro, 40.859511, 74.058908
+ Tinton Falls, 40.279966, 74.093924
+ Toms River, 39.977777, 74.183580
+ Totowa, 40.906160, 74.223310
+ Trenton, 40.219922, 74.754665
+
+
+ Un total de cinco ficheros de datos separados de ciudades
+ se pueden importar a la vez, y no hay lmite al tamao de
+ estos archivos. S\bSP\bPL\bLA\bAT\bT!\b! lee datos de las ciudades en base
+ a "primero ingresada primero servida", y traza solamente
+ las localizaciones cuyas anotaciones no estn en conflicto
+ con anotaciones de las localizaciones ledas anteriormente
+ durante en el archivo actual de datos de ciudades, en
+ archivo previos. Este comportamiento en S\bSP\bPL\bLA\bAT\bT!\b! reduce al
+ mnimo el alboroto al generar los mapas topogrficos, pero
+ tambin determina que por mandato las localizaciones impor-
+ tantes estn puestas al principio del primer fichero de
+ datos de ciudades, y las localizaciones de menor importan-
+ cia sean colocadas a continuacin en la lista o en los
+ ficheros de datos subsecuentes.
+
+ Los ficheros de datos de las ciudades se pueden generar
+ manualmente usando cualquier editor de textos, importar de
+ otras fuentes, o derivar de los datos disponibles de la
+ oficina de censo de los Estados Unidos, usando la her-
+ ramienta c\bci\bit\bty\byd\bde\bec\bco\bod\bde\ber\br incluida con S\bSP\bPL\bLA\bAT\bT!\b!. Estos datos
+ estn disponibles gratuitamente va Internet en:
+ http://www.census.gov/geo/www/cob/bdy_files.html, y deben
+ estar en formato ASCII.
+
+A\bAR\bRC\bCH\bHI\bIV\bVO\bOS\bS D\bDE\bE D\bDA\bAT\bTO\bOS\bS D\bDE\bE L\bLI\bIM\bMI\bIT\bTE\bES\bS C\bCA\bAR\bRT\bTO\bOG\bGR\bRF\bFI\bIC\bCO\bOS\bS
+ Los datos cartogrficos de lmites se pueden tambin importar
+ para trazar los lmites de las ciudades, condados, o esta-
+ dos en los mapas topogrficos generados por S\bSP\bPL\bLA\bAT\bT!\b!. Estos
+ datos deben estar en el formato de metadatos de archivos
+ cartogrficos de lmites ARC/INFO Ungenerate (formato
+ ASCII), y estn disponibles para los E.E.U.U..en la Oficina
+ de Censos va Internet en: _\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 y _\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. Un total de cinco
+ archivos cartogrficos separados de lmites se puede impor-
+ tar a la vez. No es necesario importar lmites de estado
+ si ya se han importado los lmites del condado.
+
+O\bOP\bPE\bER\bRA\bAC\bCI\bIN\bN D\bDE\bEL\bL P\bPR\bRO\bOG\bGR\bRA\bAM\bMA\bA
+ S\bSP\bPL\bLA\bAT\bT!\b! Debido a que S\bSP\bPL\bLA\bAT\bT!\b! hace un uso intensivo del CPU y
+ la memoria, se invoca va lnea de comandos usando una serie
+ de opciones y argumentos, este tipo de interfaz reduce al
+ mnimo gastos indirectos y se presta a operaciones escrip-
+ tadas (batch). El uso de CPU y prioridad de memoria por
+ S\bSP\bPL\bLA\bAT\bT!\b! se pueden modificar con el uso de comandos n\bni\bic\bce\be
+ Unix.
+
+ El nmero y el tipo de opciones pasados a S\bSP\bPL\bLA\bAT\bT!\b! determinan
+ su modo de operacin y el mtodo de generacin de los datos
+ de salida. Casi todos los opciones de S\bSP\bPL\bLA\bAT\bT!\b! se pueden
+ llamar en cascada y en cualquier orden al invocar el pro-
+ grama desde la lnea de comandos.
+
+ S\bSP\bPL\bLA\bAT\bT!\b! opera en dos modos distintos: _\bm_\bo_\bd_\bo _\bp_\bu_\bn_\bt_\bo_\b-_\ba_\b-_\bp_\bu_\bn_\bt_\bo, y
+ _\bm_\bo_\bd_\bo _\bd_\be _\bp_\br_\be_\bd_\bi_\bc_\bc_\bi_\bn _\bd_\be_\bl _\br_\be_\ba _\bd_\be _\bc_\bo_\bb_\be_\br_\bt_\bu_\br_\ba, y puede ser invo-
+ cado por el usuario usando el modo de lnea de vista (LOS)
+ el modelo de propagacin sobre terreno irregular (ITM)
+ Longley-Rice. El radio de tierra verdadera, cuatro-ter-
+ cios, o cualquier otro radio de la tierra definido-por-el-
+ usuario pueden ser especificados al realizar los anlisis
+ de lnea-de-vista.
+
+A\bAN\bNL\bLI\bIS\bSI\bIS\bS P\bPU\bUN\bNT\bTO\bO-\b-A\bA-\b-P\bPU\bUN\bNT\bTO\bO
+ S\bSP\bPL\bLA\bAT\bT!\b! puede ser utilizado para determinar si existe lnea
+ de vista entre dos localizaciones especificadas realizando
+ para ello el anlisis del perfil del terreno. Por ejemplo:
+
+ splat -t tx_site.qth -r rx_site.qth
+
+ invoca un anlisis del perfil del terreno entre el trans-
+ misor especificado en _\bt_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh y el receptor especifi-
+ cado en _\br_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh _\by _\be_\bs_\bc_\br_\bi_\bb_\be _\bu_\bn _\bR_\be_\bp_\bo_\br_\bt_\be _\bd_\be _\bO_\bb_\bs_\bt_\br_\bu_\bc_\bc_\bi_\bo_\bn_\be_\bs
+ S\bSP\bPL\bLA\bAT\bT!\b! _\ba_\bl _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\bi_\bo _\bd_\be _\bt_\br_\ba_\bb_\ba_\bj_\bo _\ba_\bc_\bt_\bu_\ba_\bl_\b. _\bE_\bl _\br_\be_\bp_\bo_\br_\bt_\be _\bc_\bo_\bn_\b-
+ _\bt_\bi_\be_\bn_\be _\bl_\bo_\bs _\bd_\be_\bt_\ba_\bl_\bl_\be_\bs _\bd_\be _\bl_\bo_\bs _\bs_\bi_\bt_\bi_\bo_\bs _\bd_\be_\bl _\bt_\br_\ba_\bn_\bs_\bm_\bi_\bs_\bo_\br _\by _\bd_\be_\bl
+ _\br_\be_\bc_\be_\bp_\bt_\bo_\br_\b, _\be _\bi_\bd_\be_\bn_\bt_\bi_\bf_\bi_\bc_\ba _\bl_\ba _\bl_\bo_\bc_\ba_\bl_\bi_\bz_\ba_\bc_\bi_\bn _\bd_\be _\bc_\bu_\ba_\bl_\bq_\bu_\bi_\be_\br
+ _\bo_\bb_\bs_\bt_\br_\bu_\bc_\bc_\bi_\bn _\bd_\be_\bt_\be_\bc_\bt_\ba_\bd_\ba _\ba _\bl_\bo _\bl_\ba_\br_\bg_\bo _\bd_\be _\bl_\ba _\bt_\br_\ba_\by_\be_\bc_\bt_\bo_\br_\bi_\ba _\bd_\be _\bl_\bn_\be_\ba_\b-
+ _\bd_\be_\b-_\bv_\bi_\bs_\bt_\ba_\b. _\bS_\bi _\bu_\bn_\ba _\bo_\bb_\bs_\bt_\br_\bu_\bc_\bc_\bi_\bn _\bp_\bu_\be_\bd_\be _\bs_\be_\br _\bd_\be_\bs_\bp_\be_\bj_\ba_\bd_\ba _\bl_\be_\bv_\ba_\bn_\bt_\ba_\bn_\bd_\bo
+ _\bl_\ba _\ba_\bn_\bt_\be_\bn_\ba _\bd_\be _\br_\be_\bc_\be_\bp_\bc_\bi_\bn _\ba _\bu_\bn_\ba _\bm_\ba_\by_\bo_\br _\ba_\bl_\bt_\bi_\bt_\bu_\bd_\b, S\bSP\bPL\bLA\bAT\bT!\b! _\bi_\bn_\bd_\bi_\bc_\ba_\br
+ _\bl_\ba _\ba_\bl_\bt_\bu_\br_\ba _\bm_\bn_\bi_\bm_\ba _\bd_\be _\bl_\ba _\ba_\bn_\bt_\be_\bn_\ba _\br_\be_\bq_\bu_\be_\br_\bi_\bd_\ba _\bp_\ba_\br_\ba _\bq_\bu_\be _\be_\bx_\bi_\bs_\bt_\ba
+ _\bl_\bn_\be_\ba_\b-_\bd_\be_\b-_\bv_\bi_\bs_\bt_\ba _\be_\bn_\bt_\br_\be _\bl_\ba_\bs _\bl_\bo_\bc_\ba_\bl_\bi_\bz_\ba_\bc_\bi_\bo_\bn_\be_\bs _\bd_\be_\bl _\bt_\br_\ba_\bn_\bs_\bm_\bi_\bs_\bo_\br _\by _\be_\bl
+ _\br_\be_\bc_\be_\bp_\bt_\bo_\br _\be_\bs_\bp_\be_\bc_\bi_\bf_\bi_\bc_\ba_\bd_\ba_\bs_\b. _\bO_\bb_\bs_\be_\br_\bv_\be _\bq_\bu_\be _\bl_\ba_\bs _\bu_\bn_\bi_\bd_\ba_\bd_\be_\bs _\bi_\bm_\bp_\be_\br_\bi_\b-
+ _\ba_\bl_\be_\bs _\b(_\bm_\bi_\bl_\bl_\ba_\bs_\b, _\bp_\bi_\be_\bs_\b) _\bs_\be _\bu_\bs_\ba_\bn _\bp_\bo_\br _\bd_\be_\bf_\be_\bc_\bt_\bo_\b, _\ba _\bm_\be_\bn_\bo_\bs _\bq_\bu_\be _\bs_\be
+ _\bu_\bs_\be _\bl_\ba _\bo_\bp_\bc_\bi_\bn _\b-_\bm_\be_\bt_\br_\bi_\bc _\be_\bn _\bl_\ba _\bo_\br_\bd_\be_\bn S\bSP\bPL\bLA\bAT\bT!\b! _\bd_\be _\bl_\bn_\be_\ba _\bd_\be _\bc_\bo_\bm_\ba_\bn_\b-
+ _\bd_\bo_\bs_\b.
+
+ _\bs_\bp_\bl_\ba_\bt _\b-_\bt _\bt_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh _\b-_\br _\br_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh _\b-_\bm_\be_\bt_\br_\bi_\bc
+
+ Si la antena se debe levantar una cantidad significativa,
+ esta determinacin puede tomar una cierta cantidad de
+ tiempo. Observe que los resultados proporcionados son el
+ _\bm_\bn_\bi_\bm_\bo necesario para que exista una trayectoria de la
+ lnea-de-vista, y en el caso de este simple ejemplo, no
+ considera los requisitos de la zona de Fresnel.
+
+ Las extensiones _\bq_\bt_\bh son asumidas por SPLAT! para los
+ archivos QTH, y son opcionales cuando se especifican los
+ argumentos -t y -r en la lnea de comandos. S\bSP\bPL\bLA\bAT\bT!\b! lee
+ automticamente todos los ficheros de datos de SPLAT nece-
+ sarios para el anlisis del terreno entre los sitios
+ especificados. S\bSP\bPL\bLA\bAT\bT!\b! busca primero los archivos SDF
+ necesarios en el directorio de trabajo actual. Si estos
+ archivos no se encuentran, S\bSP\bPL\bLA\bAT\bT!\b! entonces busca en la
+ ruta especificada por la opcin _\b-_\bd:
+
+ splat -t tx_site -r rx_site -d /cdrom/sdf/
+
+ Una ruta a un directorio externo puede ser especificada
+ creando el archivo ".splat_path" en el directorio de tra-
+ bajo del usuario. Este archivo _\b$_\bH_\bO_\bM_\bE_\b/_\b._\bs_\bp_\bl_\ba_\bt_\b__\bp_\ba_\bt_\bh debe con-
+ tener una sola lnea de texto ASCII en la que indique la
+ ruta completa del directorio que contiene todos los
+ archivos SDF.
+
+ /opt/splat/sdf/
+
+ Y puede ser generado usando cualquier editor de texto.
+
+ Un grfico que muestre el perfil del terreno en funcin de
+ la distancia, partiendo desde el receptor, entre las
+ localizaciones del transmisor y receptor se puede generar
+ adicionando la opcin _\b-_\bp:
+
+ splat -t tx_site -r rx_site -p terrain_profile.png
+
+ SPLAT! invoca al programa g\bgn\bnu\bup\bpl\blo\bot\bt cuando genera los grfi-
+ cos. La extensin del nombre del archivo especificado a
+ S\bSP\bPL\bLA\bAT\bT!\b! determina el formato del grfico a ser producido
+ _\b._\bp_\bn_\bg generar un archivo de grfico PNG a color con una res-
+ olucin de 640x480, mientras que _\b._\bp_\bs o _\b._\bp_\bo_\bs_\bt_\bs_\bc_\br_\bi_\bp_\bt generarn
+ archivos de salida postscritp. La salida en formatos como
+ GIF, Adobe Illustrator, AutoCAD dxf, LaTex, y muchos otros
+ estn disponibles. Por favor consulte g\bgn\bnu\bup\bpl\blo\bot\bt, y la docu-
+ mentacin de g\bgn\bnu\bup\bpl\blo\bot\bt para detalles de todos los formatos de
+ salida soportados.
+
+ En el lado del receptor un grfico de elevaciones en
+ funcin de la distancia determinado por el ngulo de incli-
+ nacin debido al terreno entre el receptor y el transmisor
+ se puede generar usando la opcin _\b-_\be:
+
+ splat -t tx_site -r rx_site -e elevation_profile.png
+
+ El grfico producido usando esta opcin ilustra los ngulos
+ de elevacin y depresin resultado del terreno entre la
+ localizacin del receptor y el sitio del transmisor desde
+ la perspectiva del receptor. Un segundo trazo es dibu-
+ jado entre el lado izquierdo del grfico (localizacin del
+ receptor) y la localizacin de la antena que transmite a la
+ derecha. Este trazo ilustra el ngulo de elevacin
+ requerido para que exista una trayectoria de lnea-de-
+ vista entre el receptor y transmisor. Si la traza inter-
+ seca el perfil de elevacin en cualquier punto del grfico,
+ entonces esto es una indicacin que bajo las condiciones
+ dadas no existe una trayectoria de lnea-de-vista, y las
+ obstrucciones se pueden identificar claramente en el
+ grfico en los puntos de interseccin.
+
+ Un grfico ilustrando la altura del terreno referenciado a
+ la trayectoria de lnea-de-vista entre el transmisor y el
+ receptor se puede generar usando la opcin _\b-_\bh:
+
+ splat -t tx_site -r rx_site -h height_profile.png
+
+ La altura del terreno normalizada a las alturas de las
+ antenas del transmisor y receptor pueden ser obtenidas con
+ la opcin _\b-_\bH:
+
+ splat -t tx_site -r rx_site -H normalized_height_pro-
+ file.png
+
+ El contorno de curvatura de la Tierra tambin es graficada
+ en este modo.
+
+ La primera Zona de Fresnel, y el 60% de la primera Zona de
+ Fresnel puede ser adicionada al grfico de perfiles de
+ altura con la opcin _\b-_\bf, y especificando una frecuencia (en
+ MHz) a la cual la Zona de Fresnel ser modelada:
+
+ splat -t tx_site -r rx_site -f 439.250 -H normal-
+ ized_height_profile.png
+
+ Zonas de despeje de la zona de Fresnel distintas al 60%
+ pueden ser especificadas usando la opcin _\b-_\bf_\bz como sigue:
+
+ splat -t tx_site -r rx_site -f 439.250 -fz 75 -H
+ height_profile2.png
+
+ Un grfico que muestre las prdidas de trayectoria Longley-
+ Rice se puede dibujar usando la opcin _\b-_\bl:
+
+ splat -t tx_site -r rx_site -l path_loss_profile.png
+
+ Como antes, adicionando la opcin _\b-_\bm_\be_\bt_\br_\bi_\bc se forza al
+ grfico a usar unidades de medida mtrica.
+
+ Al realizar un anlisis punto-a-punto, un reporte S\bSP\bPL\bLA\bAT\bT!\b! de
+ anlisis de trayectoria es generado en la forma de un
+ archivo de texto con una extensin de archivo _\b._\bt_\bx_\bt. El
+ reporte contiene azimut y distancias entre el transmisor y
+ receptor, as mismo cuando se analizan las perdidas por
+ espacio-libre y trayectoria Longley-Rice. El modo de
+ propagacin para la trayectoria est dado como _\bL_\bn_\be_\ba_\b-_\bd_\be_\b-
+ _\bV_\bi_\bs_\bt_\ba, _\bH_\bo_\br_\bi_\bz_\bo_\bn_\bt_\be _\bS_\bi_\bm_\bp_\bl_\be, _\bH_\bo_\br_\bi_\bz_\bo_\bn_\bt_\be _\bD_\bo_\bb_\bl_\be, _\bD_\bi_\bf_\br_\ba_\bc_\bc_\bi_\bn _\bd_\bo_\bm_\bi_\b-
+ _\bn_\ba_\bn_\bt_\be, _\bT_\br_\bo_\bp_\bo_\bs_\bc_\ba_\bt_\bt_\be_\br _\bd_\bo_\bm_\bi_\bn_\ba_\bn_\bt_\be.
+
+ Distancias y localizaciones para identificar las
+ obtrucciones a lo largo de la trayectoria entre el trans-
+ misor y el receptor tambin se proveen. Si la potencia
+ efectiva radiada del transmisor es especificada en el
+ archivo _\b._\bl_\br_\bp del transmisor correspondiente, entonces la
+ prediccin de intensidad de seal y voltaje de antena en la
+ localizacin de recepcin tambin se provee en el reporte de
+ anlisis de trayectoria.
+
+ Para determinar la relacin seal-a-ruido (SNR) en el sitio
+ remoto donde el ruido (trmico) aleatorio de Johnson es el
+ el factor limitante primario en la recepcin:
+
+ _\bS_\bN_\bR=_\bT-_\bN_\bJ-_\bL+_\bG-_\bN_\bF
+
+ donde T\bT es la potencia ERP del transmisor en dBW en la
+ direccin del recedptor, N\bNJ\bJ es el ruido de Johnson en dBW
+ (-136 dBW para un canal de TV de 6 MHz), L\bL es las prdidas
+ por trayectoria provistas por S\bSP\bPL\bLA\bAT\bT!\b! en dB (como un nmero
+ _\bp_\bo_\bs_\bi_\bt_\bi_\bv_\bo), G\bG es la ganancia de la antena receptora en dB
+ referenciada a un radiador isotrpico, y N\bNF\bF es la figura de
+ ruido en el receptor en dB.
+
+ T\bT puede ser computado como sigue:
+
+ _\bT=_\bT_\bI+_\bG_\bT
+
+ donde T\bTI\bI es la cantidad actual de potencia RF entregada a
+ la antena transmisora en dBW, G\bGT\bT es la ganancia de la
+ antena transmisora (referenciada a una isotrpica) en la
+ direccin del receptor ( al horizonte si el receptor est
+ sobre el horizonte).
+
+ Para calcular cuanta mas seal est disponible sobre el
+ mnimo necesario para conseguir una especfica relacin seal-
+ a-ruido:
+
+ _\bS_\bi_\bg_\bn_\ba_\bl__\bM_\ba_\br_\bg_\bi_\bn=_\bS_\bN_\bR-_\bS
+
+ donde S\bS es la mnima relacin SNR deseada (15.5 dB para ATSC
+ (8-level VSB) DTV, 42 dB para televisin analgica NTSC).
+
+ Un mapa topogrfico puede ser generado por S\bSP\bPL\bLA\bAT\bT!\b! para
+ visualizar la trayectoria entre el transmisor y el recep-
+ tor desde otra perspectiva. Los mapas topogrficos genera-
+ dos por S\bSP\bPL\bLA\bAT\bT!\b! presentan las elevaciones usando una escala
+ de grises logartmica, con las elevaciones ms altas repre-
+ sentadas a travs de capas ms brillantes de gris. El rango
+ dinmico de la imagen es escalada entre las elevaciones ms
+ altas y ms bajas presentes en el mapa. La nica excepcin de
+ esto es al nivel del mar, el cual se representa usando el
+ color azul.
+
+ La salida topogrfica se puede especificar usando la opcin
+ _\b-_\bo:
+
+ splat -t tx_site -r rx_site -o topo_map.ppm
+
+ La extensin _\b._\bp_\bp_\bm del archivo de salida es asumida por
+ S\bSP\bPL\bLA\bAT\bT!\b!, y es opcional.
+
+ En este ejemplo, _\bt_\bo_\bp_\bo_\b__\bm_\ba_\bp_\b._\bp_\bp_\bm ilustrar las localizaciones
+ de los sitios especificados del transmisor y del receptor.
+ Adems, la trayectoria entre los dos sitios ser dibujada
+ sobre las localizaciones para las cuales existe una
+ trayectoria sin obstculo hacia el transmisor con una
+ altura de la antena de recepcin igual a la del sitio del
+ receptor (especificado en _\br_\bx_\b__\bs_\bi_\bt_\be_\b._\bq_\bt_\bh).
+
+ Puede ser deseable poblar el mapa topogrfico con nombres y
+ localizaciones de ciudades, sitios de torres, o de otras
+ localizaciones importantes. Un archivo de ciudades se
+ puede pasar a S\bSP\bPL\bLA\bAT\bT!\b! usando la opcin _\b-_\bs:
+
+ splat -t tx_site -r rx_site -s cities.dat -o topo_map
+
+ Hasta cinco archivos separados pueden ser pasados a S\bSP\bPL\bLA\bAT\bT!\b!
+ a la vez luego de la opcin _\b-_\bs.
+
+ Lmites de estados y ciudades pueden ser adicionados al
+ mapa especificando hasta cinco archivos de lmites cartogr-
+ ficos de Censo Bureu de los U.S. usando la opcin _\b-_\bb:
+
+ splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map
+
+ En situaciones donde mltiples sitios de transmisores estn
+ en uso, se pueden pasar a S\bSP\bPL\bLA\bAT\bT!\b! hasta cuatro localiza-
+ ciones simultneas para sus anlisis:
+
+ splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p
+ profile.png
+
+ En este ejemplo, S\bSP\bPL\bLA\bAT\bT!\b! genera cuatro reportes separados
+ de obstruccin y de perfiles de terreno . Un simple mapa
+ topogrfico puede ser especificado usando la opcin _\b-_\bo, y
+ las trayectorias de lnea de vista entre cada transmisor y
+ el sitio indicado del receptor ser producido en el mapa,
+ cada uno en su propio color. La trayectoria entre el
+ primer transmisor especificado al receptor ser verde, la
+ trayectoria entre el segundo transmisor y el receptor ser
+ cyan, la trayectoria entre el tercer transmisor y el
+ receptor ser violeta, y la trayectoria entre el cuarto
+ transmisor y el receptor ser siena.
+
+ Los mapas topogrficos generados por SPLAT! son imgenes
+ TrueColor PixMap Portables de 24-bit (PPM) y pueden ser
+ vistos, corregidos, o convertidos a otros formatos grficos
+ usando populares programas de imgenes tales como 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. El formato PNG es alta-
+ mente recomendado para el almacenamiento comprimido sin
+ prdidas de los archivos topogrficos de salida generados
+ por SPLAT!. La utilidad de lnea de comandos I\bIm\bma\bag\bge\beM\bMa\bag\bgi\bic\bck\bk's
+ convierte fcilmente los archivos grficos SPLAT! PPM al
+ formato PNG:
+
+ convert splat_map.ppm splat_map.png
+
+ Otra utilidad de de lnea de comandos excelente para con-
+ vertir archivos PPM a PNG es wpng, y est disponible en:
+ _\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. Como
+ recurso adicional, los archivos PPM pueden ser comprimidos
+ usando la utilidad bzip2, y ser ledos directamente en este
+ formato por T\bTh\bhe\be G\bGI\bIM\bMP\bP.
+
+ La opcin _\b-_\bn_\bg_\bs asigna a todo el terreno el color blanco, y
+ puede ser usada cuando se quiere generar mapas desprovis-
+ tos de terreno
+
+ splat -t tx_site -r rx_site -b co34_d00.dat -ngs -o
+ white_map
+
+ El archivo imagen .ppm resultante puede ser convertido al
+ formato .png con un fondo transparente usando la utilidad
+ c\bco\bon\bnv\bve\ber\brt\bt de I\bIm\bma\bag\bge\beM\bMa\bag\bgi\bic\bck\bk's.
+
+ convert -transparent "#FFFFFF" white_map.ppm transpar-
+ ent_map.png
+
+D\bDE\bET\bTE\bER\bRM\bMI\bIN\bNA\bAN\bND\bDO\bO L\bLA\bA C\bCO\bOB\bBE\bER\bRT\bTU\bUR\bRA\bA R\bRE\bEG\bGI\bIO\bON\bNA\bAL\bL
+ S\bSP\bPL\bLA\bAT\bT!\b! puede analizar un sitio de transmisor repetidora,
+ redes de sitios, y predecir la cobertura regional para
+ cada sitio especificado. En este modo S\bSP\bPL\bLA\bAT\bT!\b! puede generar
+ un mapa topogrfico presentando la lnea-de-vista geomtrica
+ del rea de cobertura de los sitios, basados en la local-
+ izacin de cada sitio y la altura de la antena receptora
+ que se desea comunicar con el sitio en cuestin. Un anli-
+ sis regional puede ser realizado por S\bSP\bPL\bLA\bAT\bT!\b! usando la
+ opcin _\b-_\bc como sigue:
+
+ splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o
+ tx_coverage
+
+ En este ejemplo, SPLAT! genera un mapa topogrfico llamado
+ _\bt_\bx_\b__\bc_\bo_\bv_\be_\br_\ba_\bg_\be_\b._\bp_\bp_\bm que ilustra la prediccin de cobertura
+ regional de lnea-de-vista del _\bt_\bx_\b__\bs_\bi_\bt_\be a las estaciones
+ receptoras que tienen una antena de 30 pies de altura
+ sobre el nivel del terreno (AGL). Si la opcin _\b-_\bm_\be_\bt_\br_\bi_\bc es
+ usada, el argumento que sigue a la opcin _\b-_\bc es interpre-
+ tada en metros, en lugar de pies. El contenido de
+ cities.dat son dibujados sobre el mapa, como tambin los
+ lmites cartogrficos contenidos en el archivo _\bc_\bo_\b3_\b4_\b__\bd_\b0_\b0_\b._\bd_\ba_\bt.
+
+ Cuando se grafica las trayectorias de lnea-de-vista y las
+ reas de cobertura regional, S\bSP\bPL\bLA\bAT\bT!\b! por defecto no consid-
+ era los efectos de la flexin atmosfrica. Sin embargo esta
+ caracterstica puede ser modificada usando el multiplicador
+ de radio de la tierra con la opcin (_\b-_\bm):
+
+ splat -t wnjt-dt -c 30.0 -m 1.333 -s cities.dat -b coun-
+ ties.dat -o map.ppm
+
+ Un radio multiplicador de 1.333 instruye a S\bSP\bPL\bLA\bAT\bT!\b! a usar
+ el modelo de "cuatro-tercios" para el anlisis de propa-
+ gacin de lnea de vista. Cualquier multiplicador del radio
+ de la tierra apropiado puede ser seleccionado por el
+ usuario.
+
+ Cuandorealiza un anlisis regional, S\bSP\bPL\bLA\bAT\bT!\b! genera un
+ reporte para cada estacin analizada. Los reportes de sitio
+ S\bSP\bPL\bLA\bAT\bT!\b! contienen detalles de la localizacin geogrfica del
+ sitio, su altura sobre el nivel del mar, la altura de la
+ antena sobre el promedio del terreno, y la altura del
+ promedio del terreno calculada en las direcciones de los
+ azimut de 0, 45, 90, 135, 180, 225, 270, y 315 grados.
+
+D\bDE\bET\bTE\bER\bRM\bMI\bIN\bNA\bAN\bND\bDO\bO M\bML\bLT\bTI\bIP\bPL\bLE\bES\bS R\bRE\bEG\bGI\bIO\bON\bNE\bES\bS D\bDE\bE C\bCO\bOB\bBE\bER\bRT\bTU\bUR\bRA\bA D\bDE\bE L\bLD\bDV\bV
+ S\bSP\bPL\bLA\bAT\bT!\b! tambin puede presentar reas de cobertura de lnea-
+ de-vista hasta para cuatro sitios de transmisores separa-
+ dos sobre un mapa topogrfico comn. Por ejemplo:
+
+ splat -t site1 site2 site3 site4 -c 10.0 -metric -o net-
+ work.ppm
+
+ Grafica las coberturas regionales de lnea de vista del
+ site1 site2 site3 y site4 basado en una antena receptora
+ localizada a 10.0 metros sobre el nivel del terreno. Un
+ mapa topogrfico entonces es escrito al archivo _\bn_\be_\bt_\b-
+ _\bw_\bo_\br_\bk_\b._\bp_\bp_\bm. El rea de cobertura de lnea-de-vista del trans-
+ misor es graficada como sigue en los colores indicados
+ (junto con sus valores RGB correspondientes en decimal):
+
+ site1: Green (0,255,0)
+ site2: Cyan (0,255,255)
+ site3: Medium Violet (147,112,219)
+ site4: Sienna 1 (255,130,71)
+
+ site1 + site2: Yellow (255,255,0)
+ site1 + site3: Pink (255,192,203)
+ site1 + site4: Green Yellow (173,255,47)
+ site2 + site3: Orange (255,165,0)
+ site2 + site4: Dark Sea Green 1 (193,255,193)
+ site3 + site4: Dark Turquoise (0,206,209)
+
+ site1 + site2 + site3: Dark Green (0,100,0)
+ site1 + site2 + site4: Blanched Almond (255,235,205)
+ site1 + site3 + site4: Medium Spring Green (0,250,154)
+ site2 + site3 + site4: Tan (210,180,140)
+
+ site1 + site2 + site3 + site4: Gold2 (238,201,0)
+
+
+ Si se generan archivos _\b._\bq_\bt_\bh separados, cada uno represen-
+ tando una localizacin de un sitio comn, pero con difer-
+ entes alturas de antena, S\bSP\bPL\bLA\bAT\bT!\b! puede generar un mapa
+ topogrfico sencillo que ilustra la cobertura regional
+ desde las estaciones (hasta cuatro) separadas por la
+ altura en un nica torre.
+
+A\bAN\bNA\bAL\bLI\bIS\bSI\bIS\bS D\bDE\bE P\bPR\bRD\bDI\bID\bDA\bAS\bS P\bPO\bOR\bR T\bTR\bRA\bAY\bYE\bEC\bCT\bTO\bOR\bRI\bIA\bA L\bLO\bON\bNG\bGL\bLE\bEY\bY-\b-R\bRI\bIC\bCE\bE
+ Si la opcin _\b-_\bc se reemplaza por la opcin _\b-_\bL, se puede
+ generar un mapa de prdidas de trayectorias Longley-Rice:
+
+ splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o
+ path_loss_map
+
+ En este modo, S\bSP\bPL\bLA\bAT\bT!\b! genera un mapa multicolor que ilustra
+ los niveles de seal esperados (prdidas por trayectoria) en
+ las reas alrededor del transmisor. Una leyenda en la parte
+ inferior del mapa relaciona cada color con sus respectivas
+ prdidas por trayectoria especficas en decibeles intensidad
+ de seal en decibeles sobre un microvoltio por metro
+ (dBuV/m).
+
+ El rango de anlisis Longley-Rice puede modificado a un
+ valor especfico-de-usuario con la opcin _\b-_\bR. El argumento
+ debe ser dado en millas ( kilmetros si la opcin _\b-_\bm_\be_\bt_\br_\bi_\bc es
+ usada). Si se especifica un rango mayor que el mapa
+ topogrfico generado, S\bSP\bPL\bLA\bAT\bT!\b! realizar los clculos de perdi-
+ das Longley-Rice de trayectoria entre todas las cuatro
+ esquinas del rea del mapa de prediccin.
+
+ La opcin _\b-_\bd_\bb permite limitar el mximo de perdidas de la
+ regin a ser graficada en el mapa. Prdidas de trayectoria
+ entre 80 y 230 dB pueden ser especificadas usando esta
+ opcin. Por ejemplo si las perdidas por debajo de -140 dB
+ son irrelevantes al anlisis que se est realizando,
+ entonces las prdidas por trayectoria a ser graficadas por
+ S\bSP\bPL\bLA\bAT\bT!\b! pueden ser limitadas a la regin de atenuacin del
+ contorno de 140 dB como sigue:
+
+ splat -t wnjt-dt -L 30.0 -s cities.dat -b co34_d00.dat -db
+ 140 -o plot.ppm
+
+P\bPA\bAR\bRM\bME\bET\bTR\bRO\bOS\bS P\bPA\bAR\bRA\bA L\bLA\bA D\bDE\bEF\bFI\bIN\bNI\bIC\bCI\bIN\bN D\bDE\bE C\bCO\bOL\bLO\bOR\bR D\bDE\bEL\bL C\bCO\bON\bNT\bTO\bOR\bRN\bNO\bO D\bDE\bE L\bLA\bA S\bSE\bEA\bAL\bL
+ Los colores usados para ilustrar los contornos de
+ intensidad de seal y de prdidas por trayectoria en la gen-
+ eracin de mapas de mapa de cobertura en S\bSP\bPL\bLA\bAT\bT!\b! pueden ser
+ adaptados por el usuario creando o modificando los archivo
+ de definicin de color S\bSP\bPL\bLA\bAT\bT!\b!. Los ardchivos de definicin
+ de color S\bSP\bPL\bLA\bAT\bT!\b! tienen el mismo nombre base que el del
+ archivo _\b._\bq_\bt_\bh del transmisor, pero llevan las extensiones
+ _\b._\bl_\bc_\bf y _\b._\bs_\bc_\bf.
+
+ Cuando un anlisis regional Longley-Rice es realizado y el
+ ERP del transmisor no se ha especificado es cero, un
+ archivo de definicin de color de prdidas por trayectoria
+ _\b._\bl_\bc_\bf correspondiente al sitio del transmisor (_\b._\bq_\bt_\bh) es
+ ledo por S\bSP\bPL\bLA\bAT\bT!\b! desde el directorio de trabajo actual. Si
+ el archivo
+ _\b._\bl_\bc_\bf correspondiente al sitio del transmisor no se
+ encuentra, entonces un archivo por defecto para edicin
+ manual por el usuario es automticamente generado por
+ S\bSP\bPL\bLA\bAT\bT!\b!. Si el ERP del transmisor es especificado, entonces
+ un mapa de intensidad de seal es generado y un archivo de
+ definicin de color de intensidad de seal es ledo, o gener-
+ ado si no est disponible en el directorio de trabajo
+ actual.
+
+ Un archivo de definicin de color de prdidas por trayecto-
+ ria posee la siguiente estructura: (_\bw_\bn_\bj_\bt_\b-_\bd_\bt_\b._\bl_\bc_\bf):
+
+
+ ; SPLAT! Auto-generated Path-Loss Color Definition
+ ("wnjt-dt.lcf") File
+ ;
+ ; Format for the parameters held in this file is as fol-
+ lows:
+ ;
+ ; dB: red, green, blue
+ ;
+ ; ...where "dB" is the path loss (in dB) and
+ ; "red", "green", and "blue" are the corresponding RGB
+ color
+ ; definitions ranging from 0 to 255 for the region speci-
+ fied.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour
+ regions
+ ; may be defined in this file.
+ ;
+ ;
+ 80: 255, 0, 0
+ 90: 255, 128, 0
+ 100: 255, 165, 0
+ 110: 255, 206, 0
+ 120: 255, 255, 0
+ 130: 184, 255, 0
+ 140: 0, 255, 0
+ 150: 0, 208, 0
+ 160: 0, 196, 196
+ 170: 0, 148, 255
+ 180: 80, 80, 255
+ 190: 0, 38, 255
+ 200: 142, 63, 255
+ 210: 196, 54, 255
+ 220: 255, 0, 255
+ 230: 255, 194, 204
+
+
+ Si la prdida por trayectoria es menor que 80 dB, el color
+ Rojo (RGB = 255, 0, 0) es asignado a la regin. Si la
+ prdida-por-trayectoria es mayor o igual a 80 dB, pero
+ menor que 90 dB, entonces Naranja Oscuro (255, 128, 0) es
+ asignado a la regin. Naranja (255, 165, 0) es asignado a
+ regiones que tienen una prdida por trayectoria mayor o
+ igual a 90 dB, pero menor que 100 dB, y as en adelante. El
+ terreno en escala de grises es presentado por debajo del
+ contorno de prdidas por trayectoria de 230 dB.
+
+ El archivo S\bSP\bPL\bLA\bAT\bT!\b! de definicin de color de intensidad de
+ seal comparte una estructura muy similar. structure
+ (_\bw_\bn_\bj_\bt_\b-_\bd_\bt_\b._\bs_\bc_\bf):
+
+
+ ; SPLAT! Auto-generated Signal Color Definition ("wnjt-
+ dt.scf") File
+ ;
+ ; Format for the parameters held in this file is as fol-
+ lows:
+ ;
+ ; dBuV/m: red, green, blue
+ ;
+ ; ...where "dBuV/m" is the signal strength (in dBuV/m)
+ and
+ ; "red", "green", and "blue" are the corresponding RGB
+ color
+ ; definitions ranging from 0 to 255 for the region speci-
+ fied.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour
+ regions
+ ; may be defined in this file.
+ ;
+ ;
+ 128: 255, 0, 0
+ 118: 255, 165, 0
+ 108: 255, 206, 0
+ 98: 255, 255, 0
+ 88: 184, 255, 0
+ 78: 0, 255, 0
+ 68: 0, 208, 0
+ 58: 0, 196, 196
+ 48: 0, 148, 255
+ 38: 80, 80, 255
+ 28: 0, 38, 255
+ 18: 142, 63, 255
+ 8: 140, 0, 128
+
+
+ Si la intensidad de seal es mayor o igual a 128 db sobre 1
+ microvoltio por metro (dBuV/m), el color Rojo (255, 0, 0)
+ es presentado para la regin. Si la intensidad de seal es
+ mayor o igual a 118 dbuV/m, pero menor que 128 dbuV/m,
+ entonces el color naranja (255, 165, 0) es presentado y
+ asi en adelante. El terreno en escala de grises es pre-
+ sentado para regiones con intensidad de seal menores que 8
+ dBuV/m.
+
+ Los contornos de intensidad de seal para algunos servicios
+ de radiodifusin comunes en VHF y UHF en los Estados Unidos
+ son los siguientes:
+
+
+ Analog Television Broadcasting
+ ------------------------------
+ Channels 2-6: City Grade: >= 74 dBuV/m
+ Grade A: >= 68 dBuV/m
+ Grade B: >= 47 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 77 dBuV/m
+ Grade A: >= 71 dBuV/m
+ Grade B: >= 56 dBuV/m
+ --------------------------------------------
+ Channels 14-69: Indoor Grade: >= 94 dBuV/m
+ City Grade: >= 80 dBuV/m
+ Grade A: >= 74 dBuV/m
+ Grade B: >= 64 dBuV/m
+
+ Digital Television Broadcasting
+ -------------------------------
+ Channels 2-6: City Grade: >= 35 dBuV/m
+ Service Threshold: >= 28 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 43 dBuV/m
+ Service Threshold: >= 36 dBuV/m
+ --------------------------------------------
+ Channels 14-69: City Grade: >= 48 dBuV/m
+ Service Threshold: >= 41 dBuV/m
+
+ NOAA Weather Radio (162.400 - 162.550 MHz)
+ ------------------------------------------
+ Reliable: >= 18 dBuV/m
+ Not reliable: < 18 dBuV/m
+ Unlikely to receive: < 0 dBuV/m
+
+ FM Radio Broadcasting (88.1 - 107.9 MHz)
+ ----------------------------------------
+ Analog Service Contour: 60 dBuV/m
+ Digital Service Contour: 65 dBuV/m
+
+
+
+P\bPA\bAR\bRM\bME\bET\bTR\bRO\bOS\bS P\bPA\bAR\bRA\bA P\bPA\bAT\bTR\bRO\bON\bNE\bES\bS D\bDE\bE R\bRA\bAD\bDI\bIA\bAC\bCI\bIN\bN D\bDE\bE A\bAN\bNT\bTE\bEN\bNA\bAS\bS
+ Los patrones de voltaje de campo normalizado para planos
+ verticales y horizontales de antenas transmisoras son
+ importados automticamente dentro de S\bSP\bPL\bLA\bAT\bT!\b! cuando se real-
+ izan los anlisis de cobertura Longley-Rice. Los datos de
+ los patrones de antena son ledos de un par de archivos que
+ tienen el mismo nombre base que el transmisor y los
+ archivos LRP, pero con extensiones _\b._\ba_\bz y _\b._\be_\bl, para los
+ patrones de azimut y elevacin respectivamente. Especifica-
+ ciones acerca de la rotacin del patrn (si existe) e incli-
+ nacin mecnica y direccin de la inclinacin (si existe) tam-
+ bin son contenidos dentro de los archivos de patrones de
+ radiacin de las antenas.
+
+ Por ejemplo las primeras pocas lneas de un archivo de
+ patrn de azimut S\bSP\bPL\bLA\bAT\bT!\b! podran aparecer como sigue
+ (_\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
+
+
+ La primera lnea de el archivo _\b._\ba_\bz especifica la cantidad
+ de rotacin del patrn de azimut (medido en grados desde el
+ norte verdadero en sentido horario) a ser aplicado por
+ S\bSP\bPL\bLA\bAT\bT!\b! a los datos contenidos en el archivo _\b._\ba_\bz. Esto es
+ seguido por el correspondiente azimut (0 a 360 grados) y
+ su asociado patrn de campo normalizado (0.000 a 1.000)
+ separado por un espacio en blanco.
+
+ La estructura del archivo del patrn de elevacin S\bSP\bPL\bLA\bAT\bT!\b! es
+ ligeramente diferente. La primera lnea del archivo _\b._\be_\bl
+ especifica la cantidad de elevacin mecnica aplicada a la
+ antena. Note que una _\be_\bl_\be_\bv_\ba_\bc_\bi_\bn _\bh_\ba_\bc_\bi_\ba _\ba_\bb_\ba_\bj_\bo (bajo el hori-
+ zonte) es expresada como un _\bn_\bg_\bu_\bl_\bo _\bp_\bo_\bs_\bi_\bt_\bi_\bv_\bo, mientras que
+ _\bh_\ba_\bc_\bi_\ba _\ba_\br_\br_\bi_\bb_\ba (sobre el horizonte) es expresada como un
+ _\bn_\bg_\bu_\bl_\bo _\bn_\be_\bg_\ba_\bt_\bi_\bv_\bo. Estos datos son seguidos por la direccin
+ del azimut de la elevacin, separado por un espacio en
+ blanco.
+
+ El remanente del archivo consiste en los valores de los
+ ngulos de elevacin y su correspondiente patrn de radiacin
+ de voltaje normalizado (0.000 a 1.000) separados por un
+ espacio en blanco. Los ngulos de elevacin deben ser
+ especificados sobre un rango de -10 a +90 grados. Igual
+ que la notacin en la elevacin mecnica, _\bn_\bg_\bu_\bl_\bo_\bs _\bd_\be _\be_\bl_\be_\bv_\ba_\bc_\bi_\bn
+ _\bn_\be_\bg_\ba_\bt_\bi_\bv_\ba son usados para representar elevaciones _\bs_\bo_\bb_\br_\be _\be_\bl
+ _\bh_\bo_\br_\bi_\bz_\bo_\bn_\bt_\be,
+ mientras que los _\bn_\bg_\bu_\bl_\bo_\bs _\bp_\bo_\bs_\bi_\bt_\bi_\bv_\bo_\bs representan elevaciones
+ _\bb_\ba_\bj_\bo _\be_\bl _\bh_\bo_\br_\bi_\bz_\bo_\bn_\bt_\be.
+
+ Por ejemplo las primeras pocas lneas de un archivo patrn
+ de elevacin S\bSP\bPL\bLA\bAT\bT!\b! podra aparecer como sigue (_\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
+
+
+ En este ejemplo, la antena es mecanicamente inclinada
+ hacia abajo 1.1 grados hacia un azimut de 130 grados
+
+ Para mejores resultados, la resolucin de los datos de
+ patrones de radiacin debera ser especificados lo mas cerca
+ posibles a los grados azimut, y la resolucin de datos del
+ patrn de elevacin deveran ser especificados lo mas cerca
+ posible a 0.01 grados. Si los datos del patrn especificado
+ no alcanzan este nivel de resolucin, S\bSP\bPL\bLA\bAT\bT!\b! interpolar los
+ valores provistos para determinar los datos en la resolu-
+ cin requerida, aunque esto puede resultar en una prdida en
+ exactitud.
+
+I\bIM\bMP\bPO\bOR\bRT\bTA\bAN\bND\bDO\bO Y\bY E\bEX\bXP\bPO\bOR\bRT\bTA\bAN\bND\bDO\bO D\bDA\bAT\bTO\bOS\bS D\bDE\bEL\bL C\bCO\bON\bNT\bTO\bOR\bRN\bNO\bO R\bRE\bEG\bGI\bIO\bON\bNA\bAL\bL D\bDE\bE P\bPR\bRD\bDI\bID\bDA\bAS\bS
+ P\bPO\bOR\bR T\bTR\bRA\bAY\bYE\bEC\bCT\bTO\bOR\bRI\bIA\bA
+ Realizar un anlisis de cobertura Longley-Rice puede ser un
+ proceso que consume mucho tiempo, especialmente si el
+ anlisis es repetido varias veces para descubrir cuales son
+ los efectos que los cambios a los patrones de radiacin de
+ las antenas hacen a la prediccin del rea de cobertura
+
+ Este proceso puede ser apresurado al exportar los datos
+ del contorno regional de prdidas por trayectoria a un
+ archivo de salida, modificar externamente los datos de
+ prdida por trayectoria para incorporar los efectos de los
+ patrones de antena, y entonces importar nuevamente los
+ datos de prdidas por trayectoria modificados dentro de
+ S\bSP\bPL\bLA\bAT\bT!\b! para rapidamente producir un mapa revisado de prdi-
+ das por trayectoria.
+
+ Por ejemplo un archivo de salida de prdidas por trayecto-
+ ria puede ser generado por S\bSP\bPL\bLA\bAT\bT!\b! para un sitio de
+ recepcin a 30 pies sobre el nivel del terreno, con un
+ radio de 50 millas alrededor del sitio de transmisin para
+ prdidas por trayectoria mximas de 140 dB, usando la sigu-
+ iente sintaxis:
+
+ splat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat
+
+ Los archivos de salida por prdidas por trayectoria S\bSP\bPL\bLA\bAT\bT!\b!
+ a menudo exceden los 100 megabytes de tamao. Contienen la
+ informacin referentes a los lmites de la regin que
+ describen seguido por latitudes (grados norte), longitudes
+ (grados oeste), azimut, elevaciones(a la primera obstruc-
+ cin), y figuras de prdidas por trayectoria(dB) para una
+ serie de puntos especficos que abarca la regin que rodea
+ al sitio de transmisin. Las primeras pocas lneas de un
+ archivo de salida de prdidas por trayectoria S\bSP\bPL\bLA\bAT\bT!\b! tiene
+ la siguiente apariencia (_\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
+
+
+ No es poco comn para los archivos S\bSP\bPL\bLA\bAT\bT!\b! de prdidas por
+ trayectoria que contengan tanto como 3 millones o ms de
+ lneas de datos. Si el archivo es procesado, comentarios
+ pueden ser puestos con un caracter de punto y coma. El
+ editor de texto v\bvi\bim\bm ha probado ser capaz de editar
+ archivos de este tamao.
+
+ Note que al igual que el caso de los archivos de patrones
+ de antena, ngulos de elevacin negativos se refieren a
+ inclinaciones hacia arriba (sobre el horizonte), mientras
+ que ngulos positivos se refieren a inclinaciones hacia
+ abajo (bajo el horizonte). Esos ngulos se refieren a la
+ elevacin para la antena receptora en la altura sobre el
+ nivel del terreno especificada usando la opcin _\b-_\bL si la
+ trayectoria entre el transmisor y el receptor no tiene
+ obstrucciones. Si la trayectoria entre el transmisor y el
+ receptor est obstruida, entonces el ngulo a la primera
+ obstruccin es retornado por S\bSP\bPL\bLA\bAT\bT!\b!. Esto es porque el
+ modelo Longley-Rice considera la energa que alcanza un
+ punto distante sobre una trayectoria obstruida como un
+ derivado de la energa dispersada de la punta de la primera
+ instruccin, solamente. Puesto que la energa no puede
+ alcanzar directamente la localizacin obstruida, el actual
+ ngulo de elevacin a ese punto es irrelevante.
+
+ Cuando se modifican los archivos S\bSP\bPL\bLA\bAT\bT!\b! de prdidas por
+ trayectoria para reflejar datos de patrones de antena,
+ _\bs_\bo_\bl_\bo _\bl_\ba _\bl_\bt_\bi_\bm_\ba _\bc_\bo_\bl_\bu_\bm_\bn_\ba _\b(_\bp_\ba_\bt_\bh _\bl_\bo_\bs_\bs_\b) deberan ser enmendados
+ para reflejar la ganacia de antena normalizada en los ngu-
+ los de elevacin y azimut especificados en el archivo. (Por
+ ahora, programas y scripts capaces de realizar esta
+ operacin son dejados como tarea al usuario.)
+
+ Los mapas modificados de prdidas por trayectoria pueden
+ ser importados nuevamente a S\bSP\bPL\bLA\bAT\bT!\b! para generar mapas de
+ cobertura revisados.
+
+ splat -t kvea -pli pathloss.dat -s city.dat -b county.dat
+ -o map.ppm
+
+ Los archivos S\bSP\bPL\bLA\bAT\bT!\b! de prdidas por trayectoria tambin
+ pueden ser usados para guiar estudios de cobertura o
+ interferencia fuera de S\bSP\bPL\bLA\bAT\bT!\b!.
+
+A\bAR\bRC\bCH\bHI\bIV\bVO\bOS\bS D\bDE\bE E\bEN\bNT\bTR\bRA\bAD\bDA\bA D\bDE\bE T\bTE\bER\bRR\bRE\bEN\bNO\bO D\bDE\bEF\bFI\bIN\bNI\bID\bDO\bOS\bS P\bPO\bOR\bR E\bEL\bL U\bUS\bSU\bUA\bAR\bRI\bIO\bO
+ Un archivo de terreno definido por el usuario es un
+ archivo de texto generado-por-el-usuario que contiene lat-
+ itudes, longitudes, y alturas sobre el nivel de la tierra
+ de caractersticas de terreno especfica que se cree son de
+ importancia para el anlisis que S\bSP\bPL\bLA\bAT\bT!\b! est desarrollando,
+ pero perceptiblemente ausentes de los archivos SDF que
+ estn siendo usados. Un archivo de terreno definido-por-el-
+ usuario es importado dentro de un anlisis de S\bSP\bPL\bLA\bAT\bT!\b!
+ usando la opcin _\b-_\bu_\bd_\bt:
+
+ splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm
+
+ Un archivo de terreno definido-por-el-usuario tiene la
+ siguiente apariencia y estructura:
+
+
+ 40.32180556, 74.1325, 100.0 meters
+ 40.321805, 74.1315, 300.0
+ 40.3218055, 74.1305, 100.0 meters
+
+
+ La altura del terreno es interpretada en pies sobre el
+ nivel del suelo a menos que sea seguido por la palabra
+ meters, y es adicionado en la parte superior de el terreno
+ especificado en los datos SDF para la localizacin especi-
+ ficada. Debe saber que las caractersticas especificadas en
+ los archivos de terreno especificados-por-el-usuario sern
+ interpretados como 3-arco segundos en latitud y longitud.
+ Caractersticas descritas en el archivo de terreno
+ definido-por-el-usuario que traslapen las caractersticas
+ previamente definidas en el archivo son ignoradas por
+ S\bSP\bPL\bLA\bAT\bT!\b!.
+
+G\bGE\bEN\bNE\bER\bRA\bAC\bCI\bIN\bN D\bDE\bE M\bMA\bAP\bPA\bAS\bS T\bTO\bOP\bPO\bOG\bGR\bRF\bFI\bIC\bCO\bOS\bS S\bSI\bIM\bMP\bPL\bLE\bES\bS
+ En ciertas ocasiones puede ser deseable generar un mapa
+ topogrfico de una regin sin graficar reas de cobertura,
+ trayectorias de lnea-de-vista, o generar reportes de
+ obstrucciones. Existen varias maneras de hacer esto. Si
+ se desea generar un mapa topogrfico ilustrando la local-
+ izacin de un sitio del transmisor y receptor con un breve
+ reporte de texto describiendo las localizaciones y distan-
+ cias entre los sitios, entonces, entonces se debe invocar
+ la opcin _\b-_\bn como sigue:
+
+ splat -t tx_site -r rx_site -n -o topo_map.ppm
+
+ Si no se desea un reporte de texto, entonces debe usar la
+ opcin _\b-_\bN:
+
+ splat -t tx_site -r rx_site -N -o topo_map.ppm
+
+ Si se desea un mapa topogrfico centrado cerca de un sitio
+ para un radio mnimo especificado, un comando similar al
+ siguiente puede ser utilizado:
+
+ splat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o
+ topo_map.ppm
+
+ donde -R especifica el mnimo radio de el mapa en millas (
+ kilmetros si la opcin _\b-_\bm_\be_\bt_\br_\bi_\bc es usada). Note que el nom-
+ bre del sitio_tx y la localizacin no son presentadas en
+ este ejemplo. Si se desea presentar esta informacin, sim-
+ plemente cree un archivo de ciudades S\bSP\bPL\bLA\bAT\bT!\b! con la opcin
+ (_\b-_\bs) y adicinele a las opciones de la lnea-de-comandos
+ ilustradas arriba. Si la opcin _\b-_\bo y el archivo de salida
+ son omitidos en esa operacin, la salida topogrfica es
+ escrita a un archivo por defecto llamado _\bt_\bx_\b__\bs_\bi_\bt_\be_\b._\bp_\bp_\bm en el
+ directorio de trabajo actual.
+
+G\bGE\bEN\bNE\bER\bRA\bAC\bCI\bIN\bN D\bDE\bE A\bAR\bRC\bCH\bHI\bIV\bVO\bOS\bS D\bDE\bE G\bGE\bEO\bOR\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCI\bIA\bA
+ Los mapas topogrficos, de cobertura (_\b-_\bc), y contornos de
+ prdidas por trayectoria (_\b-_\bL) generados por S\bSP\bPL\bLA\bAT\bT!\b! pueden
+ ser importados dentro del programa X\bXa\bas\bst\bti\bir\br (X Amateur Sta-
+ tion Tracking and Information Reporting), generando un
+ archivo de georeferencia usando la opcin S\bSP\bPL\bLA\bAT\bT!\b! _\b-_\bg_\be_\bo:
+
+ splat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o
+ map.ppm
+
+ El archivo de georeferencia creado tendr el mismo nombre
+ base que el archivo_\b-_\bo especificado, pero con extensin
+ _\b._\bg_\be_\bo, y permite la apropiada interpretacin y presentacin
+ de los grficos .ppm S\bSP\bPL\bLA\bAT\bT!\b! en el programa X\bXa\bas\bst\bti\bir\br.
+
+G\bGE\bEN\bNE\bER\bRA\bAC\bCI\bIO\bON\bN D\bDE\bE A\bAR\bRC\bCH\bHI\bIV\bVO\bOS\bS K\bKM\bML\bL G\bGO\bOO\bOG\bGL\bLE\bE M\bMA\bAP\bP
+ Archivos Keyhole Markup Language compatibles con G\bGo\boo\bog\bgl\ble\be
+ E\bEa\bar\brt\bth\bh pueden ser generados por S\bSP\bPL\bLA\bAT\bT!\b! cuando se realizan
+ anlisis punto-a-punto invocando la opcin _\b-_\bk_\bm_\bl:
+
+ splat -t wnjt-dt -r kd2bd -kml
+
+ El archivo KML generado tendr la misma estructura que el
+ nombre del Reporte de Obstrucciones para los sitios del
+ transmisor y receptor dados, excepto que tendr una
+ extensin _\b._\bk_\bm_\bl.
+
+ Una vez cargado dentro del G\bGo\boo\bog\bgl\ble\be E\bEa\bar\brt\bth\bh (Archivo -->
+ Abrir), el archivo KLM exhibir las localizaciones de los
+ sitios de transmisin y recepcin en el mapa. Los puntos de
+ vista de la imagen sern desde la posicin del sitio de
+ transmisin mirando hacia la localizacin del receptor. La
+ trayectoria punto-a-punto entre los sitios ser presentada
+ como una lnea blanca, mientras que la trayectoria de
+ linea-de-vista RF ser presentada en verde. Las herramien-
+ tas de navegacin de G\bGo\boo\bog\bgl\ble\be E\bEa\bar\brt\bth\bh le permiten al usuario
+ "volar" alrededor de la trayectoria, identificando seales,
+ caminos, y otras caractersticas contenidas.
+
+ Cuando se realiza el anlisis de cobertura regional, el
+ archivo _\b._\bk_\bm_\bl generado por S\bSP\bPL\bLA\bAT\bT!\b! permitir a los contornos
+ de intensidad de seal o de prdidas por trayectoria a ser
+ graficados como capas sobre mapas G\bGo\boo\bog\bgl\ble\be E\bEa\bar\brt\bth\bh presentados
+ en una manera semi-transparente. El archivo _\b._\bk_\bm_\bl generado
+ tendr el mismo nombre base como el del archivo _\b._\bp_\bp_\bm nor-
+ malmente generado.
+
+D\bDE\bET\bTE\bER\bRM\bMI\bIN\bNA\bAC\bCI\bIN\bN D\bDE\bE L\bLA\bA A\bAL\bLT\bTU\bUR\bRA\bA D\bDE\bE L\bLA\bA A\bAN\bNT\bTE\bEN\bNA\bA S\bSO\bOB\bBR\bRE\bE E\bEL\bL P\bPR\bRO\bOM\bME\bED\bDI\bIO\bO D\bDE\bEL\bL T\bTE\bER\bR-\b-
+ R\bRE\bEN\bNO\bO
+ S\bSP\bPL\bLA\bAT\bT!\b! determina la altura de la antena sobre el promedio
+ del terreno (HAAT) de acuerdo al procedimiento definido
+ por la Comisin Federal de Comunicaciones. Parte 73.313(d).
+ De acuerdo a esta definicin, la elevacin del terreno a lo
+ largo de ocho radiales entre 2 y 16 millas (3 y 16 Kilmet-
+ ros) desde el sitio que est siendo analizado es muestreado
+ y promediado para los azimut cada 45 grados comenzando
+ con el norte verdadero. Si uno o mas radiales caen enter-
+ amente sobre el mar o sobre el continente fuera de los
+ Estados Unidos (reas para las cuales no existen
+ disponibles datos topogrficos USGS), entonces esos radi-
+ ales son omitidos de los clculos del promedio del terreno.
+ Si parte de los radiales se extienden sobre el mar o fuera
+ de los Estados Unidos, entonces solo la parte de esos
+ radiales que caen sobre la tierra de los Estados Unidos
+ son usados en la determinacin del promedio del terreno.
+
+ Note que los datos de elevaciones SRTM, a diferencia de
+ los antiguos datos 3-arcos segundos USGS, se extienden ms
+ all de las fronteras de los Estados Unidos. Por esta razn,
+ los resultados HAAT, no estarn en fiel cumplimiento con
+ la FCC parte 73.313(d) en reas a lo largo de la frontera
+ de los Estados Unidos si los archivos SDF usados por
+ S\bSP\bPL\bLA\bAT\bT!\b! son derivados-SRTM.
+
+ Cuando se realiza anlisis punto-a-punto del terreno,
+ S\bSP\bPL\bLA\bAT\bT!\b! determina la altura de la antena sobre el promedio
+ del terreno solo si suficientes datos topogrficos han
+ sido cargados por el programa para realizar el anlisis
+ punto-a-punto. En la mayora de los casos, esto ser ver-
+ dadero, a menos que el sitio en cuestin no est dentro de
+ 10 millas de la frontera de los datos topogrficos cargados
+ en memoria.
+
+ Cuando se realiza el anlisis de prediccin de rea, sufi-
+ cientes datos topogrficos son normalmente cargados por
+ S\bSP\bPL\bLA\bAT\bT!\b! para realizar los clculos del promedio del terreno.
+ Bajo esas condiciones, S\bSP\bPL\bLA\bAT\bT!\b! proveer la altura de la
+ antena sobre el promedio del terreno, como tambin el
+ promedio del terreno sobre el nivel del mar para los
+ azimut de 0, 45, 90, 135, 180, 225, 270, y 315 grados, e
+ incluir dicha informacin en el reporte de sitio generado.
+ Si uno o ms de los ocho radiales caen sobre el mar o sobre
+ regiones para las cuales no existen datos SDF disponibles,
+ S\bSP\bPL\bLA\bAT\bT!\b! reportar sin terreno la trayectoria de los radi-
+ ales afectados.
+
+R\bRE\bES\bST\bTR\bRI\bIN\bNG\bGI\bIE\bEN\bND\bDO\bO E\bEL\bL T\bTA\bAM\bMA\bAO\bO M\bMX\bXI\bIM\bMO\bO D\bDE\bE U\bUN\bNA\bA R\bRE\bEG\bGI\bIN\bN A\bAN\bNA\bAL\bLI\bIZ\bZA\bAD\bDA\bA
+ S\bSP\bPL\bLA\bAT\bT!\b! lee los archivos SDF de acuerdo a sus necesidades
+ dentro de una serie de "pginas" de memoria dentro de la
+ estructura del programa. Cada "pgina" contiene un archivo
+ SDF representando una regin de terreno de un grado por un
+ grado. Una sentencia _\b#_\bd_\be_\bf_\bi_\bn_\be _\bM_\bA_\bX_\bP_\bA_\bG_\bE_\bS en las primeras
+ lneas del archivo splat.cpp configura el mximo nmero de
+ "pginas" disponibles para los datos topogrficos. Esto
+ tambin configura el tamao mximo de los mapas generados
+ por S\bSP\bPL\bLA\bAT\bT!\b!. Por defecto MAXPAGES es configurado a 9. Si
+ S\bSP\bPL\bLA\bAT\bT!\b! produce un fallo de segmentacin al arrancar con
+ estos parmetros por defecto, significa que no hay sufi-
+ ciente memoria RAM y/ memoria virtual (particin swap) para
+ correr S\bSP\bPL\bLA\bAT\bT!\b! con este nmero de MAXPAGES. En situaciones
+ donde la memoria disponible es baja, MAXPAGES pueden ser
+ reducidos a 4 con el entendimiento de que esto limitar
+ grandemente la mxima regin que S\bSP\bPL\bLA\bAT\bT!\b! estar habilitado a
+ analizar. Si se tiene disponible 118 megabytes mas de la
+ memoria total (particin swap sumada la RAM), entonces MAX-
+ PAGES puede ser incrementado a 16. esto permitir opera-
+ ciones sobre una regin de 4-grados por 4-grados, lo cual
+ es suficiente para alturas de antenas que excedan los
+ 10,000 pies sobre el nivel del mar, distancias punto-a-
+ punto sobre las 1000 millas.
+
+I\bIN\bNF\bFO\bOR\bRM\bMA\bAC\bCI\bIN\bN A\bAD\bDI\bIC\bCI\bIO\bON\bNA\bAL\bL
+ Las ltimas noticias e informacin respecto al programa
+ S\bSP\bPL\bLA\bAT\bT!\b! est disponible a travs de la pgina web oficial
+ localizada en: _\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.
+
+A\bAU\bUT\bTO\bOR\bRE\bES\bS
+ John A. Magliacane, KD2BD <_\bk_\bd_\b2_\bb_\bd_\b@_\ba_\bm_\bs_\ba_\bt_\b._\bo_\br_\bg>
+ Creator, Lead Developer
+
+ Doug McDonald <_\bm_\bc_\bd_\bo_\bn_\ba_\bl_\bd_\b@_\bs_\bc_\bs_\b._\bu_\bi_\bu_\bc_\b._\be_\bd_\bu>
+ Original 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 16 de Septiembre de 2007 SPLAT!(1)
--- /dev/null
+.TH SPLAT! 1 "16 de Septiembre de 2007" "KD2BD Software" "KD2BD Software"
+.SH NOMBRE
+splat \- An RF \fBS\fPignal \fBP\fPropagation, \fBL\fPoss, \fBA\fPnd \fBT\fPerrain analysis tool
+\fBSPLAT!\fP
+
+splat \- Es una herramienta para el análisis de Propagación de Señales RF, Pérdidas, y características del Terreno
+.SH SINOPSIS
+splat [-t \fIsitio_transmisor.qth\fP]
+[-r \fIsitio_receptor.qth\fP]
+[-c \fIrx altura de la antena para el análisis de cobertura LOS (pies/metros) (flotante)\fP]
+[-L \fIrx altura de la antena para el análisis de cobertura Longley-Rice (pies/metros) (flotante)\fP]
+[-p \fIperfil_terreno.ext\fP]
+[-e \fIperfil_elevacion.ext\fP]
+[-h \fIperfil_altura.ext\fP]
+[-H \fIperfil_altura_normalizada.ext\fP]
+[-l \fIperfil_Longley-Rice.ext\fP]
+[-o \fInombre_archivo_mapa_topográfico.ppm\fP]
+[-b \fIarchivo_límites_cartograficos.dat\fP]
+[-s \fIbase_datos_sitios/ciudades.dat\fP]
+[-d \fIruta_directorio_sdf\fP]
+[-m \fIradio multiplicador tierra (flotante)\fP]
+[-f \fIfrequencia (MHz) para cálculos de la zona de Fresnel (flotante)\fP]
+[-R \fImáximo radio de covertura (millas/kilómetros) (flotante)\fP]
+[-dB \fImáximo contorno de atenuación a presentar sobre un mapa de pérdidas por trayectoria (80-230 dB)\fP]
+[-fz \fIporcentaje despejado de la zona de Fresnel (default = 60)\fP]
+[-plo \fIarchivo_salida_pérdidas_por_trayectoria.txt\fP]
+[-pli \fIarchivo_entrada_pérdidas_por_trayectoria.txt\fP]
+[-udt \fIarchivo_terreno_definido_por_el_usuario.dat\fP]
+[-n]
+[-N]
+[-nf]
+[-ngs]
+[-geo]
+[-kml]
+[-metric]
+.SH DESCRIPCIÓN
+\fBSPLAT!\fP es una poderosa herramienta para el análisis de terreno
+y propagación RF cubriendo el espectro entre 20 Megahertz y 20 Gigahertz.
+\fBSPLAT!\fP es Software Libre y está diseñado para operar en escritorios
+Unix y basados en Linux. La redistribución y/ó modificación está permitida
+bajo los términos de la licencia pública general GNU según lo publicado por
+la Fundación de Software Libre, versión 2. La adopción del código fuente de
+\fBSPLAT!\fP en aplicaciones propietarias o de fuente-cerrada es una
+violación de esta licencia, y esta \fBestrictamente\fP prohibida.
+
+\fBSPLAT!\fP es distribuído con la esperanza de que sea útil, pero
+SIN NINGUNA GARANTÍA, aún la garantía implícita de COMERCIALIZACIÓN
+ó de la APLICACIÓN PARA UN PROPÓSITO PARTICULAR. Vea la licencia GNU
+para más detalles.
+.SH INTRODUCCIÓN
+Las aplicaciones de \fBSPLAT!\fP incluyen la visualización, diseño, y
+análisis de enlaces de redes inalámbricas WAN, sistemas de radio
+comunicaciones comerciales y aficionados sobre los 20 megahertz,
+enlaces microonda, estudios de interferencia y coordinación de
+frecuencias, y determinación del contorno de cobertura de las regiones
+de radio y televisión terrestres análogas y digitales.
+
+\fBSPLAT!\fP proporciona datos de ingeniería RF del sitio, tales como
+distancias sobre el arco terrestre y azimut entre sitios de transmisión
+y recepción, ángulos de elevación de la antena (uptilt), ángulos de
+depresión (downtilt), altura de la antena sobre nivel del mar, altura de
+la antena sobre el promedio del terreno, azimut, distancias y elevaciones
+para determinar obstrucciones, Atenuaciones de trayectoria Longley-Rice,
+e intensidad de señal recibida, Adicionalmente, los requisitos mínimos
+necesarios de altura de las antenas para establecer trayectorias de
+comunicación de línea-de-vista sin obstrucciones debido al terreno, la
+primera zona de Fresnel, y cualquier porcentaje definido por el usuario
+de la primera zona de Fresnel.
+
+\fBSPLAT!\fP produce informes, gráficos, y mapas topográficos altamente
+detallados y cuidadosamente descritos que presentan las trayectorias de
+línea-de-vista, contornos regionales de pérdidas por trayectoria y contornos
+de intensidad de señal a través de los cuales se puede determinar la predicción
+del área de cobertura de sistemas de transmisores y repetidoras. Al realizar
+análisis de línea de vista y pérdidas Longley-Rice cuando se emplean
+múltiples sitios de transmisores o repetidores, \fBSPLAT!\fP determina las
+áreas de cobertura individuales y mutuas dentro de la red especificada.
+
+Simplemente tipee \fCsplat\fR en la consola de comandos, esto retornará un
+resumen de las opciones de línea de comando de \fBSPLAT!\fP:
+\fC
+
+
+ --==[ SPLAT! v1.2.1 Available Options... ]==--
+
+ -t txsite(s).qth ( max 4 con -c, max 30 con -L)
+ -r rxsite.qth (sitio de recepción)
+ -c grafica la cobertura del TX(s) (antena RX a X pies/metros SNT)
+ -L grafica pérdidas por trayectoria del TX (RX a X pies/metros SNT)
+ -s nombre de archivo(s) de ciudades/sitios a importar (max 5)
+ -b nombre de archivo(s) de límites cartográficos a importar (max 5)
+ -p nombre de archivo para graficar el perfil del terreno
+ -e nombre de archivo para graficar la elevación del terreno
+ -h nombre de archivo para graficar la altura del terreno
+ -H nombre de archivo para graficar la altura normalizada del terreno
+ -l nombre de archivo para graficar el modelo Longley-Rice
+ -o nombre de archivo para generar el mapa topográfico (.ppm)
+ -u nombre del archivo del terreno definido-por-el-usuario a importar
+ -d directorio que contiene los archivos sdf (reemplaza ~/.splat_path)
+ -m multiplicador del radio de la tierra
+ -n no grafica las rutas de LDV in mapas .ppm
+ -N no produce reportes innecesarios del sitio ó reportes de obstrucción
+ -f frecuencia para el cálculo de la zona de Fresnel (MHz)
+ -R modifica el rango por defecto para -c ó -L (millas/kilómetros)
+ -db máximo contorno de pérdidas por trayectoria (80-230 dB)
+ -nf no grafica la zona de Fresnel en los gráficos de altura
+ -fz porcentaje de despeje de la zona de Fresnel (default = 60)
+ -ngs muestra topografía de escala de grises en blanco (archivos .ppm)
+ -erp valor ERP en lugar del declarado en el archivo .lrp (Watts)
+ -pli nombre del archivo de entrada de pérdidas-por-trayectoria
+ -plo nombre del archivo de salida de pérdidas-por-trayectoria
+ -udt nombre del archivo de entrada de terreno definido-por-el-usuario
+ -kml genera archivo compatible Google Earth .kml(enlaces punto-a-punto)
+ -geo genera un archivo Xastir de georeferencia .geo (con salida .ppm)
+ -metric usa unidades métricas en lugar de imperiales (I/O del usuario)
+\fR
+.SH FICHEROS DE ENTRADA
+\fBSPLAT!\fP es una aplicación manejada por linea de comandos ó terminal de
+textos (shell), y lee los datos de entrada a través de un número de ficheros
+de datos. Algunos archivos son obligatorios para la apropiada ejecución del
+programa, mientras que otros son opcionales. Los archivos obligatorios incluyen
+los modelos topográficos 3-arco segundo en la forma de archivos de datos de SPLAT
+(archivos SDF), archivos de localización del sitio (archivos QTH), y archivos de
+parámetros para el modelo Longley-Rice (archivos LRP).
+Los archivos opcionales incluyen archivos de localización de ciudades/sitios,
+archivos de límites cartográficos, archivos de terreno definidos por el usuario,
+archivos de entrada de pérdidas-por-trayectoria, archivos de patrones de
+radiación de antenas, y archivos de definición de color.
+.SH FICHEROS DE DATOS SPLAT
+\fBSPLAT!\fP importa los datos topográficos desde los ficheros de datos SPLAT
+(SDFs). Estos archivos se pueden generar desde varias fuentes de información.
+En los Estados Unidos, los ficheros de datos SPLAT se pueden generar a través
+de la U.S. Geological Survey Digital Elevation Models (DEMs) usando la herramienta
+usgs2sdf incluida con \fBSPLAT!\fP. Los modelos de elevación digital USGS compatibles
+con esta utilidad pueden ser descargados de:
+\fIhttp://edcftp.cr.usgs.gov/pub/data/DEM/250/\fP.
+
+Una resolución significativamente mejor se puede obtener con el uso
+de los modelos digitales de elevación versión 2 SRTM-3. Estos modelos
+son el resultado de la misión topografíca del radar espacial Shuttle
+STS-99, y están disponibles para la mayoría de las regiones pobladas de
+la tierra. Los ficheros de datos SPLAT pueden ser generados desde los
+datos SRTM usando la herramienta incluida srtm2sdf. Los archivo SRTM-3
+versión 2 se pueden obtener a través de FTP anónimo desde:
+\fIftp://e0srp01u.ecs.nasa.gov:21/srtm/version2/\fP
+
+La utilidad \fBstrm2sdf\fP también puede ser usada para convertir los datos
+SRTM 3-arco segundo en formato Band Interleaved by Line (.BIL) para usar con
+\fBSPLAT!\fP.
+Estos datos están disponibles vía web en:
+\fIhttp://seamless.usgs.gov/website/seamless/\fP
+
+los datos Band Interleaved by Line deben ser descargados en una manera específica
+para ser compatible con \fBsrtm2sdf\fP y \fBSPLAT!\fP. por favor consulte
+la documentación \fBsrtm2sdf\fP's para instrucciones sobre la descarga de datos
+topográficos .BIL a través del Sitio Web USGS's Seamless.
+
+A pesar de la exactitud más alta que los datos SRTM ofrecen, existen algunos
+vacíos en los conjuntos de datos. Cuando se detectan estos vacíos, la utilidad
+\fBsrtm2sdf\fP los substituye por los datos encontrados en los archivos SDF
+existentes (que presumiblemente fueron creados de datos anteriores de la USGS
+con la utilidad \fBusgs2sdf\fP). Si los datos SDF, USGS-derivados no están
+disponibles, los vacíos se reemplazan con el promedio de los pixeles adyacentes,
+o reemplazo directo.
+
+Los ficheros de datos de SPLAT contienen valores enteros de las elevaciones
+topográficas (en metros) referenciados al nivel del mar para regiones de la
+tierra de 1-grado por 1-grado con una resolución de 3-arco segundos. Los
+archivos SDF pueden ser leídos desde el formato estándar (\fI.sdf\fP)
+generado por las utilidades \fBusgs2sdf\fP y \fBsrtm2sdf\fP, ó en formato
+comprimido bzip2 (.sdf .bz2). Puesto que los archivos sin comprimir se pueden
+procesar ligeramente más rápido que los archivos comprimidos, \fBSPLAT!\fP busca
+los datos SDF necesarios en formato sin comprimir primero. Si los datos sin
+comprimir no pueden ser localizados, \fBSPLAT!\fP entonces busca los datos en
+formato comprimido bzip2. Si tampoco se pueden encontrar los archivos SDF
+comprimidos para la región solicitada, \fBSPLAT!\fP asume que la región es
+el océano, y asignará una elevación del nivel del mar a estas áreas.
+
+Esta característica de \fBSPLAT!\fP permite realizar el análisis de
+trayectorias no solamente sobre la tierra, sino también entre las áreas
+costeras no representadas por los datos del Modelo de Elevación Digital.
+Sin embargo, este comportamiento de \fBSPLAT!\fP resalta la importancia
+de tener todos los archivos SDF requeridos para la región a ser analizada,
+para así obtener resultados significativos.
+.SH ARCHIVOS DE LOCALIZACIÓN DEL SITIO (QTH)
+\fBSPLAT!\fP SPLAT! importa la información de la localización de los sitios
+del transmisor y del receptor analizados por el programa de los archivos
+ASCII que tienen una extensión \fI.qth\fP. Los archivos QTH contienen el
+nombre del sitio, la latitud del sitio (positiva al norte del ecuador,
+negativa al sur), la longitud del sitio (en grados oeste W de 0 a 360 grados),
+y; La altura de la antena del sitio sobre el nivel del suelo (AGL), cada
+uno separado por un caracter de salto-de-línea. La altura de la antena se
+asume a ser especificada en pies a menos que sea seguida por la letra \fIm\fP
+o de la palabra \fImeters\fP en mayúsculas ó minúsculas. La información de la
+latitud y de la longitud se puede expresar en formato decimal (74.6889)
+ó en formato grados, minutos, segundos (DMS) (74 41 20.0).
+
+Por ejemplo, un archivo de localización de sitio que describía la estación de
+televisión WNJT-DT, Trenton, NJ (\fIwnjt-dt.qth\fP) se puede leer como sigue:
+
+\fC
+ WNJT-DT
+ 40.2828
+ 74.6864
+ 990.00
+\fR
+
+Cada sitio de transmisor y receptor analizado por \fBSPLAT!\fP debe ser
+representado por su propio archivo de la localización de sitio (QTH).
+.SH ARCHIVOS DE PARÁMETROS LONGLEY-RICE (LRP)
+Los archivos de datos de parámetros Longley-Rice son requeridos
+por \fBSPLAT!\fP para determinar ls pérdidas por trayectoria RF
+ya sea en el modo punto-a-punto ó predicción de área. Los datos de
+parámetros para el modelo Longley-Rice desde archivos que tienen el
+mismo nombre base del archivo QTH del sitio del transmisor, pero con
+extensión \fI.lrp\fP. Los Archivos \fBSPLAT!\fP LRP comparte el
+siguiente formato (\fIwnjt-dt.lrp\fP):
+
+\fC
+ 15.000 ; Earth Dielectric Constant (Relative permittivity)
+ 0.005 ; Earth Conductivity (Siemens per meter)
+ 301.000 ; Atmospheric Bending Constant (N-units)
+ 647.000 ; Frequency in MHz (20 MHz to 20 GHz)
+ 5 ; Radio Climate (5 = Continental Temperate)
+ 0 ; Polarization (0 = Horizontal, 1 = Vertical)
+ 0.50 ; Fraction of situations (50% of locations)
+ 0.90 ; Fraction of time (90% of the time)
+ 46000.0 ; ERP in Watts (optional)
+
+\fR
+Si un archivo LRP correspondiente al archivo QTH del sitio de
+transmisión no puede ser encontrado, \fBSPLAT!\fP explorará el
+directorio de trabajo actual buscando el archivo "splat.lrp". Si
+este archivo tampoco puede ser encontrado, entonces los parámetros
+por defecto enumerados arriba serán asignados por \fBSPLAT!\fP y un
+archivo correspondiente "splat.lrp" conteniendo estos parámetros por
+defecto será escrito al directorio actual de trabajo. El archivo
+"splat.lrp" generado se puede editar de acuerdo a las necesidades del
+usuario.
+
+Las constantes dieléctricas típicas de la tierra y sus valores de
+conductividad son los siguientes:
+\fC
+
+ Dielectric Constant Conductivity
+ Salt water : 80 5.000
+ Good ground : 25 0.020
+ Fresh water : 80 0.010
+ Marshy land : 12 0.007
+ Farmland, forest : 15 0.005
+ Average ground : 15 0.005
+ Mountain, sand : 13 0.002
+ City : 5 0.001
+ Poor ground : 4 0.001
+\fR
+
+Los códigos de Clima de Radio usados por \fBSPLAT!\fP son los siguientes:
+
+\fC
+ 1: Equatorial (Congo)
+ 2: Continental Subtropical (Sudan)
+ 3: Maritime Subtropical (West coast of Africa)
+ 4: Desert (Sahara)
+ 5: Continental Temperate
+ 6: Maritime Temperate, over land (UK and west coasts of US & EU)
+ 7: Maritime Temperate, over sea
+\fR
+
+El clima templado continental es común a las grandes masas de la tierra
+en la zona templada, tal como los Estados Unidos. Para trayectorias
+inferiores a 100 kilómetros, es poca la diferencia entre los climas templados
+continentales y marítimos.
+
+Los parámetros séptimo y octavo en el archivo \fI.lrp\fP corresponden al análisis estadístico
+proporcionado por el modelo Longley-Rice. En este ejemplo, \fBSPLAT!\fP devolverá
+la máxima pérdida de trayectoria que ocurre el 50% del tiempo (fracción del tiempo)
+en el 90% de las situaciones (fracción de situaciones). Esto es a menudo denotado
+como F(50,90) en los estudios Longley_Rice. En los Estados Unidos un criterio
+F(50,90) es típicamente usado para televisión digital (8-level VSB modulation),
+mientras que F(50,50) es usado para radiodifusión analógica (VSB-AM+NTSC).
+
+Para mayor información de esos parámetros, puede visitar:
+\fIhttp://flattop.its.bldrdoc.gov/itm.html\fP and
+\fIhttp://www.softwright.com/faq/engineering/prop_longley_rice.html\fP
+
+El parámetro final en el archivo \fI.lrp\fP corresponde a la potencia
+efectiva radiada, y es opcional. Si esta es incluida en el archivo
+\fI.lrp\fP, entonces \fBSPLAT!\fP computará los niveles de intesidad de
+señal y los contornos de niveles de intensidad de campo cuando se realicen
+los estudios Longley-rice. Si el parámetro es omitido, se computan las
+pérdidas por trayectoria en su lugar. El ERP provisto en el archivo \fI.lrp\fP
+puede ser invalidado usando la opción \fBSPLAT!\fP de línea-de-comando
+\fI-erp\fP sin tener que editar el archivo \fI.lrp\fP para conseguir el
+mismo resultado.
+.SH ARCHIVOS DE LOCALIZACIÓN DE CIUDADES
+Los nombres y las localizaciones de ciudades, sitios de la torre, u otros
+puntos de interés se pueden importar y trazar en los mapas topográficos
+generados por \fBSPLAT!\fP. \fBSPLAT!\fP importa los nombres de ciudades y
+localizaciones de los archivos ASCII que contienen el nombre, latitud y longitud
+de la localización de interés. Cada campo es separado por una coma.
+Cada expediente es separado por un caracter de salto-de-linea. Al igual que
+con los archivos \fI.qth\fP, la información de la latitud y la longitud se puede
+ingresar en formato decimal ó en formato de grados, minutos, segundos (DMS).
+
+Por ejemplo (\fIcities.dat\fP):
+\fC
+ Teaneck, 40.891973, 74.014506
+ Tenafly, 40.919212, 73.955892
+ Teterboro, 40.859511, 74.058908
+ Tinton Falls, 40.279966, 74.093924
+ Toms River, 39.977777, 74.183580
+ Totowa, 40.906160, 74.223310
+ Trenton, 40.219922, 74.754665
+\fR
+
+Un total de cinco ficheros de datos separados de ciudades se pueden
+importar a la vez, y no hay límite al tamaño de estos archivos.
+\fBSPLAT!\fP lee datos de las ciudades en base a "primero ingresada
+primero servida", y traza solamente las localizaciones cuyas anotaciones
+no estén en conflicto con anotaciones de las localizaciones leídas
+anteriormente durante en el archivo actual de datos de ciudades, ó en
+archivo previos. Este comportamiento en \fBSPLAT!\fP reduce al mínimo
+el alboroto al generar los mapas topográficos, pero también determina
+que por mandato las localizaciones importantes estén puestas al principio
+del primer fichero de datos de ciudades, y las localizaciones de menor
+importancia sean colocadas a continuación en la lista o en los ficheros
+de datos subsecuentes.
+
+Los ficheros de datos de las ciudades se pueden generar manualmente
+usando cualquier editor de textos, importar de otras fuentes, o derivar
+de los datos disponibles de la oficina de censo de los Estados Unidos,
+usando la herramienta \fBcitydecoder\fP incluida con \fBSPLAT!\fP.
+Estos datos están disponibles gratuitamente vía Internet en:
+http://www.census.gov/geo/www/cob/bdy_files.html, y deben estar en
+formato ASCII.
+.SH ARCHIVOS DE DATOS DE LIMITES CARTOGRÁFICOS
+Los datos cartográficos de límites se pueden también importar para trazar
+los límites de las ciudades, condados, o estados en los mapas topográficos
+generados por \fBSPLAT!\fP. Estos datos deben estar en el formato de metadatos
+de archivos cartográficos de límites ARC/INFO Ungenerate (formato ASCII), y
+están disponibles para los E.E.U.U..en la Oficina de Censos vía Internet en:
+\fIhttp://www.census.gov/geo/www/cob/co2000.html#ascii\fP y
+\fIhttp://www.census.gov/geo/www/cob/pl2000.html#ascii\fP. Un total de cinco
+archivos cartográficos separados de límites se puede importar a la vez.
+No es necesario importar límites de estado si ya se han importado los
+límites del condado.
+.SH OPERACIÓN DEL PROGRAMA
+\fBSPLAT!\fP Debido a que \fBSPLAT!\fP hace un uso intensivo del CPU y
+la memoria, se invoca vía línea de comandos usando una serie de opciones
+y argumentos, este tipo de interfaz reduce al mínimo gastos indirectos y
+se presta a operaciones escriptadas (batch). El uso de CPU y prioridad
+de memoria por \fBSPLAT!\fP se pueden modificar con el uso de comandos
+\fBnice\fP Unix.
+
+El número y el tipo de opciones pasados a \fBSPLAT!\fP determinan su modo de
+operación y el método de generación de los datos de salida. Casi todos los
+opciones de \fBSPLAT!\fP se pueden llamar en cascada y en cualquier orden
+al invocar el programa desde la línea de comandos.
+
+\fBSPLAT!\fP opera en dos modos distintos: \fImodo punto-a-punto\fP,
+y \fImodo de predicción del área de cobertura\fP, y puede ser invocado por el
+usuario usando el modo de línea de vista (LOS) ó el modelo de propagación
+sobre terreno irregular (ITM) Longley-Rice. El radio de tierra verdadera,
+cuatro-tercios, o cualquier otro radio de la tierra definido-por-el-usuario
+pueden ser especificados al realizar los análisis de línea-de-vista.
+.SH ANÁLISIS PUNTO-A-PUNTO
+\fBSPLAT!\fP puede ser utilizado para determinar si existe línea de vista
+entre dos localizaciones especificadas realizando para ello el análisis del
+perfil del terreno. Por ejemplo:
+
+\fCsplat -t tx_site.qth -r rx_site.qth\fR
+
+invoca un análisis del perfil del terreno entre el transmisor especificado en
+\fItx_site.qth\fP y el receptor especificado en \fIrx_site.qth\f, y escribe un
+Reporte de Obstrucciones \fBSPLAT!\fP al directorio de trabajo actual. El reporte
+contiene los detalles de los sitios del transmisor y del receptor, e identifica la
+localización de cualquier obstrucción detectada a lo largo de la trayectoria de
+línea-de-vista. Si una obstrucción puede ser despejada levantando la antena de
+recepción a una mayor altitud, \fBSPLAT!\fP indicará la altura mínima de la antena
+requerida para que exista línea-de-vista entre las localizaciones del transmisor y
+el receptor especificadas. Observe que las unidades imperiales (millas, pies) se
+usan por defecto, a menos que se use la opción \fI-metric\fP en la orden \fBSPLAT!\fP
+de línea de comandos.
+
+\fCsplat -t tx_site.qth -r rx_site.qth -metric\fR
+
+Si la antena se debe levantar una cantidad significativa, esta determinación
+puede tomar una cierta cantidad de tiempo. Observe que los resultados
+proporcionados son el \fImínimo\fP necesario para que exista una trayectoria
+de la línea-de-vista, y en el caso de este simple ejemplo, no considera los
+requisitos de la zona de Fresnel.
+
+Las extensiones \fIqth\fP son asumidas por SPLAT! para los archivos QTH, y
+son opcionales cuando se especifican los argumentos -t y -r en la línea de
+comandos. \fBSPLAT!\fP lee automáticamente todos los ficheros de datos de
+SPLAT necesarios para el análisis del terreno entre los sitios especificados.
+\fBSPLAT!\fP busca primero los archivos SDF necesarios en el directorio de
+trabajo actual. Si estos archivos no se encuentran, \fBSPLAT!\fP entonces
+busca en la ruta especificada por la opción \fI-d\fP:
+
+\fCsplat -t tx_site -r rx_site -d /cdrom/sdf/\fR
+
+Una ruta a un directorio externo puede ser especificada creando el archivo
+".splat_path" en el directorio de trabajo del usuario. Este archivo \fI$HOME/.splat_path\fP
+debe contener una sola línea de texto ASCII en la que indique la ruta
+completa del directorio que contiene todos los archivos SDF.
+
+\fC/opt/splat/sdf/\fR
+
+Y puede ser generado usando cualquier editor de texto.
+
+Un gráfico que muestre el perfil del terreno en función de la distancia,
+partiendo desde el receptor, entre las localizaciones del transmisor y
+receptor se puede generar adicionando la opción \fI-p\fP:
+
+\fCsplat -t tx_site -r rx_site -p terrain_profile.png\fR
+
+SPLAT! invoca al programa \fBgnuplot\fP cuando genera los gráficos.
+La extensión del nombre del archivo especificado a \fBSPLAT!\fP determina
+el formato del gráfico a ser producido \fI.png\fP generará un archivo de gráfico
+PNG a color con una resolución de 640x480, mientras que \fI.ps\fP o \fI.postscript\fP
+generarán archivos de salida postscritp. La salida en formatos como GIF,
+Adobe Illustrator, AutoCAD dxf, LaTex, y muchos otros están disponibles.
+Por favor consulte \fBgnuplot\fP, y la documentación de \fBgnuplot\fP para
+detalles de todos los formatos de salida soportados.
+
+En el lado del receptor un gráfico de elevaciones en función de la
+distancia determinado por el ángulo de inclinación debido al terreno
+entre el receptor y el transmisor se puede generar usando la opción \fI-e\fP:
+
+\fCsplat -t tx_site -r rx_site -e elevation_profile.png\fR
+
+El gráfico producido usando esta opción ilustra los ángulos de elevación
+y depresión resultado del terreno entre la localización del receptor y
+el sitio del transmisor desde la perspectiva del receptor. Un segundo
+trazo es dibujado entre el lado izquierdo del gráfico (localización del
+receptor) y la localización de la antena que transmite a la derecha.
+Este trazo ilustra el ángulo de elevación requerido para que exista una
+trayectoria de línea-de-vista entre el receptor y transmisor. Si la traza
+interseca el perfil de elevación en cualquier punto del gráfico, entonces
+esto es una indicación que bajo las condiciones dadas no existe una
+trayectoria de línea-de-vista, y las obstrucciones se pueden identificar
+claramente en el gráfico en los puntos de intersección.
+
+Un gráfico ilustrando la altura del terreno referenciado a la trayectoria
+de línea-de-vista entre el transmisor y el receptor se puede generar
+usando la opción \fI-h\fP:
+
+\fCsplat -t tx_site -r rx_site -h height_profile.png\fR
+
+La altura del terreno normalizada a las alturas de las antenas del transmisor
+y receptor pueden ser obtenidas con la opción \fI-H\fP:
+
+\fCsplat -t tx_site -r rx_site -H normalized_height_profile.png\fR
+
+El contorno de curvatura de la Tierra también es graficada en este modo.
+
+La primera Zona de Fresnel, y el 60% de la primera Zona de Fresnel puede ser
+adicionada al gráfico de perfiles de altura con la opción \fI-f\fP, y
+especificando una frecuencia (en MHz) a la cual la Zona de Fresnel será modelada:
+
+\fCsplat -t tx_site -r rx_site -f 439.250 -H normalized_height_profile.png\fR
+
+Zonas de despeje de la zona de Fresnel distintas al 60% pueden ser especificadas
+usando la opción \fI-fz\fP como sigue:
+
+\fCsplat -t tx_site -r rx_site -f 439.250 -fz 75 -H height_profile2.png\fR
+
+Un gráfico que muestre las pérdidas de trayectoria Longley-Rice se puede
+dibujar usando la opción \fI-l\fP:
+
+\fCsplat -t tx_site -r rx_site -l path_loss_profile.png\fR
+
+Como antes, adicionando la opción \fI-metric\fP se forza al gráfico
+a usar unidades de medida métrica.
+
+Al realizar un análisis punto-a-punto, un reporte \fBSPLAT!\fP de análisis
+de trayectoria es generado en la forma de un archivo de texto con una
+extensión de archivo \fI.txt\fP. El reporte contiene azimut y distancias
+entre el transmisor y receptor, así mismo cuando se analizan las perdidas
+por espacio-libre y trayectoria Longley-Rice. El modo de propagación para
+la trayectoria está dado como \fILínea-de-Vista\fP, \fIHorizonte Simple\fP,
+\fIHorizonte Doble\fP, \fIDifracción dominante\fP, ó \fITroposcatter
+dominante\fP.
+
+Distancias y localizaciones para identificar las obtrucciones
+a lo largo de la trayectoria entre el transmisor y el receptor
+también se proveen. Si la potencia efectiva radiada del transmisor es
+especificada en el archivo \fI.lrp\fP del transmisor correspondiente,
+entonces la predicción de intensidad de señal y voltaje de antena
+en la localización de recepción también se provee en el reporte de
+análisis de trayectoria.
+
+Para determinar la relación señal-a-ruido (SNR) en el sitio remoto
+donde el ruido (térmico) aleatorio de Johnson es el el factor
+limitante primario en la recepción:
+
+.EQ
+SNR = T - NJ - L + G - NF
+.EN
+
+donde \fBT\fP es la potencia ERP del transmisor en dBW en la dirección
+del recedptor, \fBNJ\fP es el ruido de Johnson en dBW (-136 dBW para un
+canal de TV de 6 MHz), \fBL\fP es las pérdidas por trayectoria provistas
+por \fBSPLAT!\fP en dB (como un número \fIpositivo\fP), \fBG\fP es la ganancia
+de la antena receptora en dB referenciada a un radiador isotrópico,
+y \fBNF\fP es la figura de ruido en el receptor en dB.
+
+\fBT\fP puede ser computado como sigue:
+
+.EQ
+T = TI + GT
+.EN
+
+donde \fBTI\fP es la cantidad actual de potencia RF entregada a la antena
+transmisora en dBW, \fBGT\fP es la ganancia de la antena transmisora
+(referenciada a una isotrópica) en la dirección del receptor (ó al horizonte
+si el receptor está sobre el horizonte).
+
+Para calcular cuanta mas señal está disponible sobre el mínimo necesario para
+conseguir una específica relación señal-a-ruido:
+
+.EQ
+Signal_Margin = SNR - S
+.EN
+
+donde \fBS\fP es la mínima relación SNR deseada (15.5 dB para
+ATSC (8-level VSB) DTV, 42 dB para televisión analógica NTSC).
+
+Un mapa topográfico puede ser generado por \fBSPLAT!\fP para visualizar
+la trayectoria entre el transmisor y el receptor desde otra perspectiva.
+Los mapas topográficos generados por \fBSPLAT!\fP presentan las elevaciones
+usando una escala de grises logarítmica, con las elevaciones más altas
+representadas a través de capas más brillantes de gris. El rango dinámico
+de la imagen es escalada entre las elevaciones más altas y más bajas presentes
+en el mapa. La única excepción de esto es al nivel del mar, el cual se representa
+usando el color azul.
+
+La salida topográfica se puede especificar usando la opción \fI-o\fP:
+
+\fCsplat -t tx_site -r rx_site -o topo_map.ppm\fR
+
+La extensión \fI.ppm\fP del archivo de salida es asumida por \fBSPLAT!\fP,
+y es opcional.
+
+En este ejemplo, \fItopo_map.ppm\fP ilustrará las localizaciones de los
+sitios especificados del transmisor y del receptor. Además, la trayectoria
+entre los dos sitios será dibujada sobre las localizaciones para las cuales
+existe una trayectoria sin obstáculo hacia el transmisor con una altura de
+la antena de recepción igual a la del sitio del receptor (especificado en
+\fIrx_site.qth\fP).
+
+Puede ser deseable poblar el mapa topográfico con nombres y localizaciones
+de ciudades, sitios de torres, o de otras localizaciones importantes.
+Un archivo de ciudades se puede pasar a \fBSPLAT!\fP usando la opción \fI-s\fP:
+
+\fCsplat -t tx_site -r rx_site -s cities.dat -o topo_map\fR
+
+Hasta cinco archivos separados pueden ser pasados a \fBSPLAT!\fP a la vez
+luego de la opción \fI-s\fP.
+
+Límites de estados y ciudades pueden ser adicionados al mapa especificando
+hasta cinco archivos de límites cartográficos de Censo Bureu de los U.S.
+usando la opción \fI-b\fP:
+
+\fCsplat -t tx_site -r rx_site -b co34_d00.dat -o topo_map\fR
+
+En situaciones donde múltiples sitios de transmisores están en uso,
+se pueden pasar a \fBSPLAT!\fP hasta cuatro localizaciones simultáneas para
+sus análisis:
+
+\fCsplat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p profile.png\fR
+
+En este ejemplo, \fBSPLAT!\fP genera cuatro reportes separados de obstrucción y
+de perfiles de terreno . Un simple mapa topográfico puede ser especificado
+usando la opción \fI-o\fP, y las trayectorias de línea de vista entre cada
+transmisor y el sitio indicado del receptor será producido en el mapa, cada
+uno en su propio color. La trayectoria entre el primer transmisor especificado
+al receptor será verde, la trayectoria entre el segundo transmisor y el receptor
+será cyan, la trayectoria entre el tercer transmisor y el receptor será violeta,
+y la trayectoria entre el cuarto transmisor y el receptor será siena.
+
+Los mapas topográficos generados por SPLAT! son imágenes TrueColor PixMap
+Portables de 24-bit (PPM) y pueden ser vistos, corregidos, o convertidos
+a otros formatos gráficos usando populares programas de imágenes tales
+como \fBxv\fP, \fBThe GIMP\fP, \fBImageMagick\fP, and \fBXPaint\fP.
+El formato PNG es altamente recomendado para el almacenamiento comprimido
+sin pérdidas de los archivos topográficos de salida generados por SPLAT!.
+La utilidad de línea de comandos \fBImageMagick\fP's convierte fácilmente los
+archivos gráficos SPLAT! PPM al formato PNG:
+
+\fCconvert splat_map.ppm splat_map.png\fR
+
+Otra utilidad de de línea de comandos excelente para convertir archivos PPM a
+PNG es wpng, y está disponible en: \fIhttp://www.libpng.org/pub/png/book/sources.html\fP.
+Como recurso adicional, los archivos PPM pueden ser comprimidos usando la
+utilidad bzip2, y ser leídos directamente en este formato por \fBThe GIMP\fP.
+
+La opción \fI-ngs\fP asigna a todo el terreno el color blanco, y puede
+ser usada cuando se quiere generar mapas desprovistos de terreno
+
+\fCsplat -t tx_site -r rx_site -b co34_d00.dat -ngs -o white_map\fR
+
+El archivo imagen .ppm resultante puede ser convertido al formato .png
+con un fondo transparente usando la utilidad \fBconvert\fP de \fBImageMagick\fP's.
+
+\fCconvert -transparent "#FFFFFF" white_map.ppm transparent_map.png\fR
+.SH DETERMINANDO LA COBERTURA REGIONAL
+\fBSPLAT!\fP puede analizar un sitio de transmisor ó repetidora,
+ó redes de sitios, y predecir la cobertura regional para cada sitio
+especificado. En este modo \fBSPLAT!\fP puede generar un mapa topográfico
+presentando la línea-de-vista geométrica del área de cobertura de
+los sitios, basados en la localización de cada sitio y la altura de
+la antena receptora que se desea comunicar con el sitio en cuestión.
+Un análisis regional puede ser realizado por \fBSPLAT!\fP usando la
+opción \fI-c\fP como sigue:
+
+\fCsplat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o tx_coverage\fR
+
+En este ejemplo, SPLAT! genera un mapa topográfico llamado \fItx_coverage.ppm\fP
+que ilustra la predicción de cobertura regional de línea-de-vista del \fItx_site\fP
+a las estaciones receptoras que tienen una antena de 30 pies de altura sobre el
+nivel del terreno (AGL). Si la opción \fI-metric\fP es usada, el argumento que
+sigue a la opción \fI-c\fP es interpretada en metros, en lugar de pies. El contenido
+de cities.dat son dibujados sobre el mapa, como también los límites cartográficos
+contenidos en el archivo \fIco34_d00.dat\fP.
+
+Cuando se grafica las trayectorias de línea-de-vista y las áreas de
+cobertura regional, \fBSPLAT!\fP por defecto no considera los efectos
+de la flexión atmosférica. Sin embargo esta característica puede ser
+modificada usando el multiplicador de radio de la tierra con la opción (\fI-m\fP):
+
+\fCsplat -t wnjt-dt -c 30.0 -m 1.333 -s cities.dat -b counties.dat -o map.ppm\fR
+
+Un radio multiplicador de 1.333 instruye a \fBSPLAT!\fP a usar el modelo de
+"cuatro-tercios" para el análisis de propagación de línea de vista.
+Cualquier multiplicador del radio de la tierra apropiado puede ser seleccionado
+por el usuario.
+
+Cuandorealiza un análisis regional, \fBSPLAT!\fP genera un reporte para cada
+estación analizada. Los reportes de sitio \fBSPLAT!\fP contienen detalles de
+la localización geográfica del sitio, su altura sobre el nivel del mar,
+la altura de la antena sobre el promedio del terreno, y la altura del promedio
+del terreno calculada en las direcciones de los azimut de 0, 45, 90, 135,
+180, 225, 270, y 315 grados.
+.SH DETERMINANDO MÚLTIPLES REGIONES DE COBERTURA DE LDV
+
+\fBSPLAT!\fP también puede presentar áreas de cobertura de línea-de-vista hasta
+para cuatro sitios de transmisores separados sobre un mapa topográfico común.
+Por ejemplo:
+
+\fCsplat -t site1 site2 site3 site4 -c 10.0 -metric -o network.ppm\fR
+
+Grafica las coberturas regionales de línea de vista del site1 site2 site3
+y site4 basado en una antena receptora localizada a 10.0 metros sobre el nivel
+del terreno. Un mapa topográfico entonces es escrito al archivo \fInetwork.ppm\fP.
+El área de cobertura de línea-de-vista del transmisor es graficada como sigue
+en los colores indicados (junto con sus valores RGB correspondientes en decimal):
+\fC
+ site1: Green (0,255,0)
+ site2: Cyan (0,255,255)
+ site3: Medium Violet (147,112,219)
+ site4: Sienna 1 (255,130,71)
+
+ site1 + site2: Yellow (255,255,0)
+ site1 + site3: Pink (255,192,203)
+ site1 + site4: Green Yellow (173,255,47)
+ site2 + site3: Orange (255,165,0)
+ site2 + site4: Dark Sea Green 1 (193,255,193)
+ site3 + site4: Dark Turquoise (0,206,209)
+
+ site1 + site2 + site3: Dark Green (0,100,0)
+ site1 + site2 + site4: Blanched Almond (255,235,205)
+ site1 + site3 + site4: Medium Spring Green (0,250,154)
+ site2 + site3 + site4: Tan (210,180,140)
+
+ site1 + site2 + site3 + site4: Gold2 (238,201,0)
+\fR
+
+Si se generan archivos \fI.qth\fP separados, cada uno representando una
+localización de un sitio común, pero con diferentes alturas de antena,
+\fBSPLAT!\fP puede generar un mapa topográfico sencillo que ilustra la
+cobertura regional desde las estaciones (hasta cuatro) separadas por la
+altura en un única torre.
+.SH ANALISIS DE PÉRDIDAS POR TRAYECTORIA LONGLEY-RICE
+Si la opción \fI-c\fP se reemplaza por la opción \fI-L\fP, se puede generar un mapa
+de pérdidas de trayectorias Longley-Rice:
+
+\fCsplat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o path_loss_map\fR
+
+En este modo, \fBSPLAT!\fP genera un mapa multicolor que ilustra los niveles de
+señal esperados (pérdidas por trayectoria) en las áreas alrededor del
+transmisor. Una leyenda en la parte inferior del mapa relaciona cada color
+con sus respectivas pérdidas por trayectoria específicas en decibeles ó
+intensidad de señal en decibeles sobre un microvoltio por metro (dBuV/m).
+
+El rango de análisis Longley-Rice puede modificado a un valor específico-de-usuario
+con la opción \fI-R\fP. El argumento debe ser dado en millas (ó kilómetros si la
+opción \fI-metric\fP es usada). Si se especifica un rango mayor que el mapa topográfico
+generado, \fBSPLAT!\fP realizará los cálculos de perdidas Longley-Rice de trayectoria
+entre todas las cuatro esquinas del área del mapa de predicción.
+
+La opción \fI-db\fP permite limitar el máximo de perdidas de la región
+a ser graficada en el mapa. Pérdidas de trayectoria entre 80 y 230 dB
+pueden ser especificadas usando esta opción. Por ejemplo si las perdidas
+por debajo de -140 dB son irrelevantes al análisis que se está realizando,
+entonces las pérdidas por trayectoria a ser graficadas por \fBSPLAT!\fP
+pueden ser limitadas a la región de atenuación del contorno de 140 dB
+como sigue:
+
+\fCsplat -t wnjt-dt -L 30.0 -s cities.dat -b co34_d00.dat -db 140 -o plot.ppm\fR
+.SH PARÁMETROS PARA LA DEFINICIÓN DE COLOR DEL CONTORNO DE LA SEÑAL
+Los colores usados para ilustrar los contornos de intensidad de señal y
+de pérdidas por trayectoria en la generación de mapas de mapa de cobertura
+en \fBSPLAT!\fP pueden ser adaptados por el usuario creando o modificando
+los archivo de definición de color \fBSPLAT!\fP. Los ardchivos de definición
+de color \fBSPLAT!\fP tienen el mismo nombre base que el del archivo \fI.qth\fP
+del transmisor, pero llevan las extensiones \fI.lcf\fP y \fI.scf\fP.
+
+Cuando un análisis regional Longley-Rice es realizado y el ERP del transmisor no
+se ha especificado ó es cero, un archivo de definición de color de pérdidas por
+trayectoria \fI.lcf\fP correspondiente al sitio del transmisor (\fI.qth\fP)
+es leído por \fBSPLAT!\fP desde el directorio de trabajo actual. Si el archivo
+\fI .lcf\fP correspondiente al sitio del transmisor no se encuentra, entonces
+un archivo por defecto para edición manual por el usuario es automáticamente
+generado por \fBSPLAT!\fP. Si el ERP del transmisor es especificado, entonces
+un mapa de intensidad de señal es generado y un archivo de definición de color
+de intensidad de señal es leído, o generado si no está disponible en el
+directorio de trabajo actual.
+
+Un archivo de definición de color de pérdidas por trayectoria posee la siguiente
+estructura:
+(\fIwnjt-dt.lcf\fP):
+
+\fC
+ ; SPLAT! Auto-generated Path-Loss Color Definition ("wnjt-dt.lcf") File
+ ;
+ ; Format for the parameters held in this file is as follows:
+ ;
+ ; dB: red, green, blue
+ ;
+ ; ...where "dB" is the path loss (in dB) and
+ ; "red", "green", and "blue" are the corresponding RGB color
+ ; definitions ranging from 0 to 255 for the region specified.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour regions
+ ; may be defined in this file.
+ ;
+ ;
+ 80: 255, 0, 0
+ 90: 255, 128, 0
+ 100: 255, 165, 0
+ 110: 255, 206, 0
+ 120: 255, 255, 0
+ 130: 184, 255, 0
+ 140: 0, 255, 0
+ 150: 0, 208, 0
+ 160: 0, 196, 196
+ 170: 0, 148, 255
+ 180: 80, 80, 255
+ 190: 0, 38, 255
+ 200: 142, 63, 255
+ 210: 196, 54, 255
+ 220: 255, 0, 255
+ 230: 255, 194, 204
+\fR
+
+Si la pérdida por trayectoria es menor que 80 dB, el color Rojo (RGB = 255, 0, 0)
+es asignado a la región. Si la pérdida-por-trayectoria es mayor o igual a
+80 dB, pero menor que 90 dB, entonces Naranja Oscuro (255, 128, 0) es
+asignado a la región. Naranja (255, 165, 0) es asignado a regiones que tienen
+una pérdida por trayectoria mayor o igual a 90 dB, pero menor que 100 dB, y
+así en adelante. El terreno en escala de grises es presentado por debajo del
+contorno de pérdidas por trayectoria de 230 dB.
+
+El archivo \fBSPLAT!\fP de definición de color de intensidad de señal comparte una
+estructura muy similar.
+structure (\fIwnjt-dt.scf\fP):
+
+\fC
+ ; SPLAT! Auto-generated Signal Color Definition ("wnjt-dt.scf") File
+ ;
+ ; Format for the parameters held in this file is as follows:
+ ;
+ ; dBuV/m: red, green, blue
+ ;
+ ; ...where "dBuV/m" is the signal strength (in dBuV/m) and
+ ; "red", "green", and "blue" are the corresponding RGB color
+ ; definitions ranging from 0 to 255 for the region specified.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour regions
+ ; may be defined in this file.
+ ;
+ ;
+ 128: 255, 0, 0
+ 118: 255, 165, 0
+ 108: 255, 206, 0
+ 98: 255, 255, 0
+ 88: 184, 255, 0
+ 78: 0, 255, 0
+ 68: 0, 208, 0
+ 58: 0, 196, 196
+ 48: 0, 148, 255
+ 38: 80, 80, 255
+ 28: 0, 38, 255
+ 18: 142, 63, 255
+ 8: 140, 0, 128
+\fR
+
+Si la intensidad de señal es mayor o igual a 128 db sobre 1 microvoltio
+por metro (dBuV/m), el color Rojo (255, 0, 0) es presentado para la región.
+Si la intensidad de señal es mayor o igual a 118 dbuV/m, pero menor que
+128 dbuV/m, entonces el color naranja (255, 165, 0) es presentado y asi en
+adelante. El terreno en escala de grises es presentado para regiones con
+intensidad de señal menores que 8 dBuV/m.
+
+Los contornos de intensidad de señal para algunos servicios de radiodifusión
+comunes en VHF y UHF en los Estados Unidos son los siguientes:
+\fC
+
+ Analog Television Broadcasting
+ ------------------------------
+ Channels 2-6: City Grade: >= 74 dBuV/m
+ Grade A: >= 68 dBuV/m
+ Grade B: >= 47 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 77 dBuV/m
+ Grade A: >= 71 dBuV/m
+ Grade B: >= 56 dBuV/m
+ --------------------------------------------
+ Channels 14-69: Indoor Grade: >= 94 dBuV/m
+ City Grade: >= 80 dBuV/m
+ Grade A: >= 74 dBuV/m
+ Grade B: >= 64 dBuV/m
+
+ Digital Television Broadcasting
+ -------------------------------
+ Channels 2-6: City Grade: >= 35 dBuV/m
+ Service Threshold: >= 28 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 43 dBuV/m
+ Service Threshold: >= 36 dBuV/m
+ --------------------------------------------
+ Channels 14-69: City Grade: >= 48 dBuV/m
+ Service Threshold: >= 41 dBuV/m
+
+ NOAA Weather Radio (162.400 - 162.550 MHz)
+ ------------------------------------------
+ Reliable: >= 18 dBuV/m
+ Not reliable: < 18 dBuV/m
+ Unlikely to receive: < 0 dBuV/m
+
+ FM Radio Broadcasting (88.1 - 107.9 MHz)
+ ----------------------------------------
+ Analog Service Contour: 60 dBuV/m
+ Digital Service Contour: 65 dBuV/m
+\fR
+
+.SH PARÁMETROS PARA PATRONES DE RADIACIÓN DE ANTENAS
+Los patrones de voltaje de campo normalizado para planos verticales y
+horizontales de antenas transmisoras son importados automáticamente dentro
+de \fBSPLAT!\fP cuando se realizan los análisis de cobertura Longley-Rice.
+Los datos de los patrones de antena son leídos de un par de archivos que
+tienen el mismo nombre base que el transmisor y los archivos LRP, pero con
+extensiones \fI.az\fP y \fI.el\fP, para los patrones de azimut y elevación
+respectivamente. Especificaciones acerca de la rotación del patrón (si existe)
+e inclinación mecánica y dirección de la inclinación (si existe) también son
+contenidos dentro de los archivos de patrones de radiación de las antenas.
+
+Por ejemplo las primeras pocas líneas de un archivo de patrón de azimut \fBSPLAT!\fP
+podrían aparecer como sigue (\fIkvea.az\fP):
+\fC
+ 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
+\fR
+
+La primera línea de el archivo \fI.az\fP especifica la cantidad de
+rotación del patrón de azimut (medido en grados desde el norte verdadero
+en sentido horario) a ser aplicado por \fBSPLAT!\fP a los datos contenidos
+en el archivo \fI.az\fP. Esto es seguido por el correspondiente azimut
+(0 a 360 grados) y su asociado patrón de campo normalizado (0.000 a 1.000)
+separado por un espacio en blanco.
+
+La estructura del archivo del patrón de elevación \fBSPLAT!\fP es ligeramente
+diferente. La primera línea del archivo \fI.el\fP especifica la cantidad de
+elevación mecánica aplicada a la antena. Note que una \fIelevación hacia abajo\fP
+(bajo el horizonte) es expresada como un \fIángulo positivo\fP, mientras que \fIhacia
+arriba\fP (sobre el horizonte) es expresada como un \fIángulo negativo\fP. Estos datos
+son seguidos por la dirección del azimut de la elevación, separado por un
+espacio en blanco.
+
+El remanente del archivo consiste en los valores de los ángulos de elevación y su
+correspondiente patrón de radiación de voltaje normalizado (0.000 a 1.000)
+separados por un espacio en blanco. Los ángulos de elevación deben ser especificados
+sobre un rango de -10 a +90 grados. Igual que la notación en la elevación mecánica,
+\fIángulos de elevación negativa\fP son usados para representar elevaciones \fIsobre el horizonte\fP,
+ mientras que los \fIángulos positivos\fP representan elevaciones \fIbajo el horizonte\fP.
+
+Por ejemplo las primeras pocas líneas de un archivo patrón de elevación \fBSPLAT!\fP
+podría aparecer como sigue (\fIkvea.el\fP):
+\fC
+ 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
+\fR
+
+En este ejemplo, la antena es mecanicamente inclinada hacia abajo 1.1
+grados hacia un azimut de 130 grados
+
+Para mejores resultados, la resolución de los datos de patrones de radiación
+debería ser especificados lo mas cerca posibles a los grados azimut,
+y la resolución de datos del patrón de elevación deverían ser especificados
+lo mas cerca posible a 0.01 grados. Si los datos del patrón especificado
+no alcanzan este nivel de resolución, \fBSPLAT!\fP interpolará los valores
+provistos para determinar los datos en la resolución requerida, aunque esto
+puede resultar en una pérdida en exactitud.
+.SH IMPORTANDO Y EXPORTANDO DATOS DEL CONTORNO REGIONAL DE PÉRDIDAS POR TRAYECTORIA
+Realizar un análisis de cobertura Longley-Rice puede ser un proceso que consume
+mucho tiempo, especialmente si el análisis es repetido varias veces para descubrir
+cuales son los efectos que los cambios a los patrones de radiación de las antenas
+hacen a la predicción del área de cobertura
+
+Este proceso puede ser apresurado al exportar los datos del contorno regional
+de pérdidas por trayectoria a un archivo de salida, modificar externamente
+los datos de pérdida por trayectoria para incorporar los efectos de los
+patrones de antena, y entonces importar nuevamente los datos de pérdidas por
+trayectoria modificados dentro de \fBSPLAT!\fP para rapidamente producir un mapa
+revisado de pérdidas por trayectoria.
+
+Por ejemplo un archivo de salida de pérdidas por trayectoria puede ser generado
+por \fBSPLAT!\fP para un sitio de recepción a 30 pies sobre el nivel del terreno,
+con un radio de 50 millas alrededor del sitio de transmisión para pérdidas por
+trayectoria máximas de 140 dB, usando la siguiente sintaxis:
+
+\fCsplat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat\fR
+
+Los archivos de salida por pérdidas por trayectoria \fBSPLAT!\fP a menudo
+exceden los 100 megabytes de tamaño. Contienen la información referentes a
+los límites de la región que describen seguido por latitudes (grados norte),
+longitudes (grados oeste), azimut, elevaciones(a la primera obstrucción), y
+figuras de pérdidas por trayectoria(dB) para una serie de puntos específicos que
+abarca la región que rodea al sitio de transmisión. Las primeras pocas líneas
+de un archivo de salida de pérdidas por trayectoria \fBSPLAT!\fP tiene la siguiente
+apariencia (\fIpathloss.dat\fP):
+\fC
+
+ 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
+\fR
+
+No es poco común para los archivos \fBSPLAT!\fP de pérdidas por trayectoria que
+contengan tanto como 3 millones o más de líneas de datos. Si el archivo es procesado,
+comentarios pueden ser puestos con un caracter de punto y coma. El editor de texto
+\fBvim\fP ha probado ser capaz de editar archivos de este tamaño.
+
+Note que al igual que el caso de los archivos de patrones de antena, ángulos
+de elevación negativos se refieren a inclinaciones hacia arriba (sobre el
+horizonte), mientras que ángulos positivos se refieren a inclinaciones hacia
+abajo (bajo el horizonte). Esos ángulos se refieren a la elevación para la
+antena receptora en la altura sobre el nivel del terreno especificada usando
+la opción \fI-L\fP si la trayectoria entre el transmisor y el receptor no
+tiene obstrucciones. Si la trayectoria entre el transmisor y el receptor está
+obstruida, entonces el ángulo a la primera obstrucción es retornado por \fBSPLAT!\fP.
+Esto es porque el modelo Longley-Rice considera la energía que alcanza un punto
+distante sobre una trayectoria obstruida como un derivado de la energía dispersada
+de la punta de la primera instrucción, solamente. Puesto que la energía no puede
+alcanzar directamente la localización obstruida, el actual ángulo de elevación
+a ese punto es irrelevante.
+
+Cuando se modifican los archivos \fBSPLAT!\fP de pérdidas por trayectoria
+para reflejar datos de patrones de antena, \fIsolo la última columna (path loss)\fP
+deberían ser enmendados para reflejar la ganacia de antena normalizada en los
+ángulos de elevación y azimut especificados en el archivo. (Por ahora, programas
+y scripts capaces de realizar esta operación son dejados como tarea al usuario.)
+
+Los mapas modificados de pérdidas por trayectoria pueden ser importados nuevamente
+a \fBSPLAT!\fP para generar mapas de cobertura revisados.
+
+\fCsplat -t kvea -pli pathloss.dat -s city.dat -b county.dat -o map.ppm\fR
+
+Los archivos \fBSPLAT!\fP de pérdidas por trayectoria también pueden ser usados
+para guiar estudios de cobertura o interferencia fuera de \fBSPLAT!\fP.
+.SH ARCHIVOS DE ENTRADA DE TERRENO DEFINIDOS POR EL USUARIO
+Un archivo de terreno definido por el usuario es un archivo de texto
+generado-por-el-usuario que contiene latitudes, longitudes, y alturas sobre
+el nivel de la tierra de características de terreno específica que se cree
+son de importancia para el análisis que \fBSPLAT!\fP está desarrollando, pero
+perceptiblemente ausentes de los archivos SDF que están siendo usados. Un archivo
+de terreno definido-por-el-usuario es importado dentro de un análisis de \fBSPLAT!\fP
+usando la opción \fI-udt\fP:
+
+\fC splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm\fR
+
+Un archivo de terreno definido-por-el-usuario tiene la siguiente apariencia y estructura:
+\fC
+
+ 40.32180556, 74.1325, 100.0 meters
+ 40.321805, 74.1315, 300.0
+ 40.3218055, 74.1305, 100.0 meters
+\fR
+
+La altura del terreno es interpretada en pies sobre el nivel del suelo a menos que sea
+seguido por la palabra meters, y es adicionado en la parte superior de el terreno
+especificado en los datos SDF para la localización especificada. Debe saber que las
+características especificadas en los archivos de terreno especificados-por-el-usuario
+serán interpretados como 3-arco segundos en latitud y longitud. Características descritas
+en el archivo de terreno definido-por-el-usuario que traslapen las características
+previamente definidas en el archivo son ignoradas por \fBSPLAT!\fP.
+.SH GENERACIÓN DE MAPAS TOPOGRÁFICOS SIMPLES
+En ciertas ocasiones puede ser deseable generar un mapa topográfico de una región sin graficar
+áreas de cobertura, trayectorias de línea-de-vista, o generar reportes de obstrucciones.
+Existen varias maneras de hacer esto. Si se desea generar un mapa topográfico ilustrando
+la localización de un sitio del transmisor y receptor con un breve reporte de texto describiendo
+las localizaciones y distancias entre los sitios, entonces, entonces se debe invocar
+la opción \fI-n\fP como sigue:
+
+\fCsplat -t tx_site -r rx_site -n -o topo_map.ppm\fR
+
+Si no se desea un reporte de texto, entonces debe usar la opción \fI-N\fP:
+
+\fCsplat -t tx_site -r rx_site -N -o topo_map.ppm\fR
+
+Si se desea un mapa topográfico centrado cerca de un sitio para un radio
+mínimo especificado, un comando similar al siguiente puede ser utilizado:
+
+\fCsplat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o topo_map.ppm\fR
+
+donde -R especifica el mínimo radio de el mapa en millas (ó kilómetros
+si la opción \fI-metric\fP es usada). Note que el nombre del sitio_tx y
+la localización no son presentadas en este ejemplo. Si se desea presentar
+esta información, simplemente cree un archivo de ciudades \fBSPLAT!\fP
+con la opción (\fI-s\fP) y adiciónele a las opciones de la línea-de-comandos
+ilustradas arriba.
+Si la opción \fI-o\fP y el archivo de salida son omitidos en esa operación,
+la salida topográfica es escrita a un archivo por defecto llamado \fItx_site.ppm\fP
+en el directorio de trabajo actual.
+.SH GENERACIÓN DE ARCHIVOS DE GEOREFERENCIA
+Los mapas topográficos, de cobertura (\fI-c\fP), y contornos de pérdidas
+por trayectoria (\fI-L\fP) generados por \fBSPLAT!\fP pueden ser importados
+dentro del programa \fBXastir\fP (X Amateur Station Tracking and Information
+Reporting), generando un archivo de georeferencia usando la opción \fBSPLAT!\fP \fI-geo\fP:
+
+\fCsplat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o map.ppm\fR
+
+El archivo de georeferencia creado tendrá el mismo nombre base que el archivo\fI-o\fP
+especificado, pero con extensión \fI .geo\fP, y permite la apropiada interpretación
+y presentación de los gráficos .ppm \fBSPLAT!\fP en el programa \fBXastir\fP.
+.SH GENERACION DE ARCHIVOS KML GOOGLE MAP
+Archivos Keyhole Markup Language compatibles con \fBGoogle Earth\fP
+pueden ser generados por \fBSPLAT!\fP cuando se realizan análisis
+punto-a-punto invocando la opción \fI-kml\fP:
+
+\fCsplat -t wnjt-dt -r kd2bd -kml\fR
+
+El archivo KML generado tendrá la misma estructura que el nombre del
+Reporte de Obstrucciones para los sitios del transmisor y receptor dados,
+excepto que tendrá una extensión \fI .kml\fP.
+
+Una vez cargado dentro del \fBGoogle Earth\fP (Archivo --> Abrir), el archivo
+KLM exhibirá las localizaciones de los sitios de transmisión y recepción en el mapa.
+Los puntos de vista de la imagen serán desde la posición del sitio de transmisión
+mirando hacia la localización del receptor. La trayectoria punto-a-punto entre
+los sitios será presentada como una línea blanca, mientras que la trayectoria
+de linea-de-vista RF será presentada en verde. Las herramientas de navegación
+de \fBGoogle Earth\fP le permiten al usuario "volar" alrededor de la trayectoria,
+identificando señales, caminos, y otras características contenidas.
+
+Cuando se realiza el análisis de cobertura regional, el archivo \fI .kml\fP
+generado por \fBSPLAT!\fP permitirá a los contornos de intensidad de
+señal o de pérdidas por trayectoria a ser graficados como capas sobre
+mapas \fBGoogle Earth\fP presentados en una manera semi-transparente.
+El archivo \fI.kml\fP generado tendrá el mismo nombre base como el del
+archivo \fI.ppm\fP normalmente generado.
+.SH DETERMINACIÓN DE LA ALTURA DE LA ANTENA SOBRE EL PROMEDIO DEL TERRENO
+\fBSPLAT!\fP determina la altura de la antena sobre el promedio del
+terreno (HAAT) de acuerdo al procedimiento definido por la Comisión
+Federal de Comunicaciones. Parte 73.313(d). De acuerdo a esta definición,
+la elevación del terreno a lo largo de ocho radiales entre 2 y 16 millas
+(3 y 16 Kilómetros) desde el sitio que está siendo analizado es muestreado
+y promediado para los azimut cada 45 grados comenzando con el norte verdadero.
+Si uno o mas radiales caen enteramente sobre el mar o sobre el continente fuera
+de los Estados Unidos (áreas para las cuales no existen disponibles datos
+topográficos USGS), entonces esos radiales son omitidos de los cálculos del
+promedio del terreno. Si parte de los radiales se extienden sobre el mar o
+fuera de los Estados Unidos, entonces solo la parte de esos radiales que caen
+sobre la tierra de los Estados Unidos son usados en la determinación del
+promedio del terreno.
+
+Note que los datos de elevaciones SRTM, a diferencia de los antiguos datos
+3-arcos segundos USGS, se extienden más allá de las fronteras de los Estados
+Unidos. Por esta razón, los resultados HAAT, no estarán en fiel cumplimiento
+con la FCC parte 73.313(d) en áreas a lo largo de la frontera de los Estados
+Unidos si los archivos SDF usados por \fBSPLAT!\fP son derivados-SRTM.
+
+Cuando se realiza análisis punto-a-punto del terreno, \fBSPLAT!\fP determina
+la altura de la antena sobre el promedio del terreno solo si suficientes
+datos topográficos han sido cargados por el programa para realizar el análisis
+punto-a-punto. En la mayoría de los casos, esto será verdadero, a menos que
+el sitio en cuestión no esté dentro de 10 millas de la frontera de los datos
+topográficos cargados en memoria.
+
+Cuando se realiza el análisis de predicción de área, suficientes
+datos topográficos son normalmente cargados por \fBSPLAT!\fP para
+realizar los cálculos del promedio del terreno. Bajo esas condiciones,
+\fBSPLAT!\fP proveerá la altura de la antena sobre el promedio del terreno,
+como también el promedio del terreno sobre el nivel del mar para los azimut
+de 0, 45, 90, 135, 180, 225, 270, y 315 grados, e incluirá dicha información
+en el reporte de sitio generado. Si uno o más de los ocho radiales caen sobre
+el mar o sobre regiones para las cuales no existen datos SDF disponibles,
+\fBSPLAT!\fP reportará sin terreno la trayectoria de los radiales afectados.
+.SH RESTRINGIENDO EL TAMAÑO MÁXIMO DE UNA REGIÓN ANALIZADA
+\fBSPLAT!\fP lee los archivos SDF de acuerdo a sus necesidades dentro de una serie
+de "páginas" de memoria dentro de la estructura del programa. Cada "página" contiene
+un archivo SDF representando una región de terreno de un grado por un grado.
+Una sentencia \fI#define MAXPAGES\fP en las primeras líneas del archivo splat.cpp
+configura el máximo número de "páginas" disponibles para los datos topográficos.
+Esto también configura el tamaño máximo de los mapas generados por \fBSPLAT!\fP.
+Por defecto MAXPAGES es configurado a 9. Si \fBSPLAT!\fP produce un fallo de
+segmentación al arrancar con estos parámetros por defecto, significa que no hay
+suficiente memoria RAM y/ó memoria virtual (partición swap) para correr \fBSPLAT!\fP
+con este número de MAXPAGES. En situaciones donde la memoria disponible es baja,
+MAXPAGES pueden ser reducidos a 4 con el entendimiento de que esto limitará grandemente
+la máxima región que \fBSPLAT!\fP estará habilitado a analizar. Si se tiene disponible
+118 megabytes ó mas de la memoria total (partición swap sumada la RAM), entonces MAXPAGES
+puede ser incrementado a 16. esto permitirá operaciones sobre una región de 4-grados por
+4-grados, lo cual es suficiente para alturas de antenas que excedan los 10,000 pies sobre
+el nivel del mar, ó distancias punto-a-punto sobre las 1000 millas.
+.SH INFORMACIÓN ADICIONAL
+Las últimas noticias e información respecto al programa \fBSPLAT!\fP
+está disponible a través de la página web oficial localizada en:
+\fIhttp://www.qsl.net/kd2bd/splat.html\fP.
+.SH AUTORES
+.TP
+John A. Magliacane, KD2BD <\fIkd2bd@amsat.org\fP>
+Creator, Lead Developer
+.TP
+Doug McDonald <\fImcdonald@scs.uiuc.edu\fP>
+Original Longley-Rice Model integration
+.TP
+Ron Bentley <\fIronbentley@earthlink.net\fP>
+Fresnel Zone plotting and clearance determination
+
--- /dev/null
+%!PS-Adobe-3.0
+%%Creator: groff version 1.17.2
+%%CreationDate: Fri Oct 19 15:57:15 2007
+%%DocumentNeededResources: font Times-Roman
+%%+ font Times-Bold
+%%+ font Times-Italic
+%%+ font Courier
+%%+ font Symbol
+%%DocumentSuppliedResources: procset grops 1.17 2
+%%Pages: 18
+%%PageOrder: Ascend
+%%Orientation: Portrait
+%%EndComments
+%%BeginProlog
+%%BeginResource: procset grops 1.17 2
+/setpacking where{
+pop
+currentpacking
+true setpacking
+}if
+/grops 120 dict dup begin
+/SC 32 def
+/A/show load def
+/B{0 SC 3 -1 roll widthshow}bind def
+/C{0 exch ashow}bind def
+/D{0 exch 0 SC 5 2 roll awidthshow}bind def
+/E{0 rmoveto show}bind def
+/F{0 rmoveto 0 SC 3 -1 roll widthshow}bind def
+/G{0 rmoveto 0 exch ashow}bind def
+/H{0 rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
+/I{0 exch rmoveto show}bind def
+/J{0 exch rmoveto 0 SC 3 -1 roll widthshow}bind def
+/K{0 exch rmoveto 0 exch ashow}bind def
+/L{0 exch rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
+/M{rmoveto show}bind def
+/N{rmoveto 0 SC 3 -1 roll widthshow}bind def
+/O{rmoveto 0 exch ashow}bind def
+/P{rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
+/Q{moveto show}bind def
+/R{moveto 0 SC 3 -1 roll widthshow}bind def
+/S{moveto 0 exch ashow}bind def
+/T{moveto 0 exch 0 SC 5 2 roll awidthshow}bind def
+/SF{
+findfont exch
+[exch dup 0 exch 0 exch neg 0 0]makefont
+dup setfont
+[exch/setfont cvx]cvx bind def
+}bind def
+/MF{
+findfont
+[5 2 roll
+0 3 1 roll
+neg 0 0]makefont
+dup setfont
+[exch/setfont cvx]cvx bind def
+}bind def
+/level0 0 def
+/RES 0 def
+/PL 0 def
+/LS 0 def
+/MANUAL{
+statusdict begin/manualfeed true store end
+}bind def
+/PLG{
+gsave newpath clippath pathbbox grestore
+exch pop add exch pop
+}bind def
+/BP{
+/level0 save def
+1 setlinecap
+1 setlinejoin
+72 RES div dup scale
+LS{
+90 rotate
+}{
+0 PL translate
+}ifelse
+1 -1 scale
+}bind def
+/EP{
+level0 restore
+showpage
+}bind def
+/DA{
+newpath arcn stroke
+}bind def
+/SN{
+transform
+.25 sub exch .25 sub exch
+round .25 add exch round .25 add exch
+itransform
+}bind def
+/DL{
+SN
+moveto
+SN
+lineto stroke
+}bind def
+/DC{
+newpath 0 360 arc closepath
+}bind def
+/TM matrix def
+/DE{
+TM currentmatrix pop
+translate scale newpath 0 0 .5 0 360 arc closepath
+TM setmatrix
+}bind def
+/RC/rcurveto load def
+/RL/rlineto load def
+/ST/stroke load def
+/MT/moveto load def
+/CL/closepath load def
+/FL{
+currentgray exch setgray fill setgray
+}bind def
+/BL/fill load def
+/LW/setlinewidth load def
+/RE{
+findfont
+dup maxlength 1 index/FontName known not{1 add}if dict begin
+{
+1 index/FID ne{def}{pop pop}ifelse
+}forall
+/Encoding exch def
+dup/FontName exch def
+currentdict end definefont pop
+}bind def
+/DEFS 0 def
+/EBEGIN{
+moveto
+DEFS begin
+}bind def
+/EEND/end load def
+/CNT 0 def
+/level1 0 def
+/PBEGIN{
+/level1 save def
+translate
+div 3 1 roll div exch scale
+neg exch neg exch translate
+0 setgray
+0 setlinecap
+1 setlinewidth
+0 setlinejoin
+10 setmiterlimit
+[]0 setdash
+/setstrokeadjust where{
+pop
+false setstrokeadjust
+}if
+/setoverprint where{
+pop
+false setoverprint
+}if
+newpath
+/CNT countdictstack def
+userdict begin
+/showpage{}def
+}bind def
+/PEND{
+clear
+countdictstack CNT sub{end}repeat
+level1 restore
+}bind def
+end def
+/setpacking where{
+pop
+setpacking
+}if
+%%EndResource
+%%IncludeResource: font Times-Roman
+%%IncludeResource: font Times-Bold
+%%IncludeResource: font Times-Italic
+%%IncludeResource: font Courier
+%%IncludeResource: font Symbol
+grops begin/DEFS 1 dict def DEFS begin/u{.001 mul}bind def end/RES 72
+def/PL 792 def/LS false def/ENC0[/asciicircum/asciitilde/Scaron/Zcaron
+/scaron/zcaron/Ydieresis/trademark/quotesingle/.notdef/.notdef/.notdef
+/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef
+/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef
+/.notdef/.notdef/space/exclam/quotedbl/numbersign/dollar/percent
+/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen
+/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon
+/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O
+/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/circumflex
+/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y
+/z/braceleft/bar/braceright/tilde/.notdef/quotesinglbase/guillemotleft
+/guillemotright/bullet/florin/fraction/perthousand/dagger/daggerdbl
+/endash/emdash/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/hungarumlaut
+/dotaccent/breve/caron/ring/ogonek/quotedblleft/quotedblright/oe/lslash
+/quotedblbase/OE/Lslash/.notdef/exclamdown/cent/sterling/currency/yen
+/brokenbar/section/dieresis/copyright/ordfeminine/guilsinglleft
+/logicalnot/minus/registered/macron/degree/plusminus/twosuperior
+/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior
+/ordmasculine/guilsinglright/onequarter/onehalf/threequarters
+/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE
+/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex
+/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis
+/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn
+/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla
+/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis
+/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash
+/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis]def
+/Courier@0 ENC0/Courier RE/Times-Italic@0 ENC0/Times-Italic RE
+/Times-Bold@0 ENC0/Times-Bold RE/Times-Roman@0 ENC0/Times-Roman RE
+%%EndProlog
+%%Page: 1 1
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10.95
+/Times-Bold@0 SF(NOMBRE)72 84 Q F0 2.5(splat \255)108 96 R(An RF)2.5 E
+/F2 10/Times-Bold@0 SF(S)2.5 E F0(ignal)A F2(P)2.5 E F0(ropag)A(ation,)
+-.05 E F2(L)2.5 E F0(oss,)A F2(A)2.5 E F0(nd)A F2(T)2.5 E F0
+(errain analysis tool)A F2(SPLA)2.5 E(T!)-.95 E F0 3.39(splat \255)108
+120 R .89(Es una herramienta para el an\341lisis de Propag)3.39 F .89
+(aci\363n de Se\361ales RF)-.05 F 3.39(,P)-.8 G .89
+(\351rdidas, y caracter\355sticas del)-3.39 F -.7(Te)108 132 S(rreno).7
+E F1(SINOPSIS)72 148.8 Q F0 .236(splat [-t)108 160.8 R/F3 10
+/Times-Italic@0 SF(sitio_tr)5.236 E(ansmisor)-.15 E(.qth)-1.11 E F0
+2.736(][)C(-r)-2.736 E F3(sitio_r)2.736 E(eceptor)-.37 E(.qth)-1.11 E F0
+2.736(][)C(-c)-2.736 E F3 .236(rx altur)2.736 F 2.736(ad)-.15 G 2.736
+(el)-2.736 G 2.736(aa)-2.736 G .236(ntena par)-2.736 F 2.736(ae)-.15 G
+2.736(la)-2.736 G .236(n\341lisis de cobertur)-2.736 F(a)-.15 E 2.732
+(LOS \(pies/metr)108 172.8 R 2.732(os\) \(\215otante\))-.45 F F0 5.232
+(][)C(-L)-5.232 E F3 2.732(rx altur)5.232 F 5.232(ad)-.15 G 5.231(el)
+-5.232 G 5.231(aa)-5.231 G 2.731(ntena par)-5.231 F 5.231(ae)-.15 G
+5.231(la)-5.231 G 2.731(n\341lisis de cobertur)-5.231 F 5.231(aL)-.15 G
+(ongle)-5.231 E(y-Rice)-.3 E(\(pies/metr)108 184.8 Q 3.41
+(os\) \(\215otante\))-.45 F F0 5.91(][)C(-p)-5.91 E F3(per\214l_terr)
+5.91 E(eno.e)-.37 E(xt)-.2 E F0 5.91(][)C(-e)-5.91 E F3(per\214l_ele)
+5.91 E(vacion.e)-.15 E(xt)-.2 E F0 5.91(][)C(-h)-5.91 E F3
+(per\214l_altur)5.91 E(a.e)-.15 E(xt)-.2 E F0 5.91(][)C(-H)-5.91 E F3
+(per)5.91 E(-)-.2 E(\214l_altur)108 196.8 Q(a_normalizada.e)-.15 E(xt)
+-.2 E F0 5.31(][)C(-l)-5.31 E F3(per\214l_Longle)5.31 E(y-Rice)-.3 E(.e)
+-.15 E(xt)-.2 E F0 5.31(][)C(-o)-5.31 E F3(nombr)5.31 E(e_ar)-.37 E -.15
+(ch)-.37 G(ivo_mapa_topo).15 E(gr\341\214co.ppm)-.1 E F0 5.31(][)C(-b)
+-5.31 E F3(ar)108 208.8 Q -.15(ch)-.37 G(ivo_l\355mites_carto).15 E(gr)
+-.1 E(a\214cos.dat)-.15 E F0 4.346(][)C(-s)-4.346 E F3
+(base_datos_sitios/ciudades.dat)4.346 E F0 4.347(][)C(-d)-4.347 E F3
+(ruta_dir)4.347 E(ectorio_sdf)-.37 E F0 4.347(][)C(-m)-4.347 E F3 -.15
+(ra)4.347 G(dio).15 E 1.491(multiplicador tierr)108 220.8 R 3.991(a\()
+-.15 G(\215otante\))-3.991 E F0 3.991(][)C(-f)-3.991 E F3(fr)3.991 E
+1.491(equencia \(MHz\) par)-.37 F 3.991(ac)-.15 G 1.491
+(\341lculos de la zona de F)-3.991 F -.37(re)-.55 G 1.49
+(snel \(\215otante\)).37 F F0 3.99(][)C(-R)-3.99 E F3 .18(m\341ximo r)
+108 232.8 R .18(adio de co)-.15 F(vertur)-.1 E 2.68(a\()-.15 G
+(millas/kil\363metr)-2.68 E .18(os\) \(\215otante\))-.45 F F0 2.68(][)C
+(-dB)-2.68 E F3 .18(m\341ximo contorno de atenuaci\363n a pr)2.68 F
+(esentar)-.37 E(sobr)108 244.8 Q 3.356(eu)-.37 G 3.356(nm)-3.356 G .856
+(apa de p\351r)-3.356 F .856(didas por tr)-.37 F .856
+(ayectoria \(80-230 dB\))-.15 F F0 3.356(][)C(-fz)-3.356 E F3(por)3.356
+E .855(centaje despejado de la zona de F)-.37 F -.37(re)-.55 G(snel).37
+E 7.94(\(default = 60\))108 256.8 R F0 10.44(][)C(-plo)-10.44 E F3(ar)
+10.44 E -.15(ch)-.37 G(ivo_salida_p\351r).15 E(didas_por_tr)-.37 E
+(ayectoria.txt)-.15 E F0 10.44(][)C(-pli)-10.44 E F3(ar)10.44 E -.15(ch)
+-.37 G(ivo_entr).15 E(ada_p\351r)-.15 E(di-)-.37 E(das_por_tr)108 268.8
+Q(ayectoria.txt)-.15 E F0 4.176(][)C(-udt)-4.176 E F3(ar)4.176 E -.15
+(ch)-.37 G(ivo_terr).15 E(eno_de\214nido_por_el_usuario.dat)-.37 E F0
+4.176(][)C 1.676(-n] [-N] [-nf] [-ngs] [-geo])-4.176 F([-kml] [-metric])
+108 280.8 Q F1(DESCRIPCI\323N)72 297.6 Q F2(SPLA)108 309.6 Q(T!)-.95 E
+F0 .595(es una)3.095 F .595(poderosa herramienta)5.595 F .595
+(para el an\341lisis de terreno y propag)5.595 F .596
+(aci\363n RF cubriendo el espectro)-.05 F .595(entre 20 Me)108 321.6 R
+-.05(ga)-.15 G .595(hertz y 20 Gig).05 F(ahertz.)-.05 E F2(SPLA)5.595 E
+(T!)-.95 E F0 .595(es Softw)3.095 F .595
+(are Libre y est\341 dise\361ado para operar en escritorios)-.1 F .192
+(Unix y basados en Linux. La redistrib)108 333.6 R .193(uci\363n y/\363\
+ modi\214caci\363n est\341 permitida bajo los t\351rminos de la licenci\
+a)-.2 F .78(p\372blica general GNU se)108 345.6 R .78
+(g\372n lo publicado por la Fundaci\363n de Softw)-.15 F .78
+(are Libre, v)-.1 F .78(ersi\363n 2. La adopci\363n del)-.15 F .648
+(c\363digo fuente de)108 357.6 R F2(SPLA)3.148 E(T!)-.95 E F0 .649
+(en aplicaciones propietarias o de fuente-cerrada)3.148 F .649
+(es una violaci\363n de esta licen-)5.649 F(cia, y esta)108 369.6 Q F2
+(estrictamente)2.5 E F0(prohibida.)2.5 E F2(SPLA)108 393.6 Q(T!)-.95 E
+F0 .228(es distrib)2.728 F .228
+(u\355do con la esperanza de que sea \372til, pero SIN NINGUN)-.2 F
+2.727(AG)-.35 G .227(ARANT\315A, a\372n la g)-2.727 F(arant\355a)-.05 E
+.48(impl\355cita de COMERCIALIZA)108 405.6 R .481
+(CI\323N \363 de la APLICA)-.4 F .481(CI\323N P)-.4 F .481(ARA UN PR)
+-.92 F(OP\323SIT)-.4 E 2.981(OP)-.18 G(AR)-3.901 E .481(TICULAR. V)-.6 F
+(ea)-1.11 E(la licencia GNU para m\341s detalles.)108 417.6 Q F1(INTR)72
+434.4 Q(ODUCCI\323N)-.329 E F0 .217(Las aplicaciones de)108 446.4 R F2
+(SPLA)2.717 E(T!)-.95 E F0 .216
+(incluyen la visualizaci\363n, dise\361o, y an\341lisis de enlaces)2.717
+F 2.716(de redes)5.216 F(inal\341mbricas)2.716 E -1.2(WA)108 458.4 S
+2.582(N, sistemas de radio comunicaciones comerciales y a\214cionados)
+1.2 F 2.583(sobre los 20 me)7.583 F -.05(ga)-.15 G 2.583(hertz, enlaces)
+.05 F .157(microonda, estudios de interferencia y coordinaci\363n de fr\
+ecuencias, y determinaci\363n del contorno de cober)108 470.4 R(-)-.2 E
+(tura de las re)108 482.4 Q(giones de radio y tele)-.15 E
+(visi\363n terrestres an\341log)-.25 E(as y digitales.)-.05 E F2(SPLA)
+108 506.4 Q(T!)-.95 E F0 .206(proporciona datos de ingenier\355a RF del\
+ sitio, tales como distancias sobre el arco terrestre y azimut)2.705 F
+1.338(entre sitios de transmisi\363n y recepci\363n, \341ngulos de ele)
+108 518.4 R -.25(va)-.25 G 1.338
+(ci\363n de la antena \(uptilt\), \341ngulos de depresi\363n).25 F(\(do)
+108 530.4 Q .144(wntilt\), altura de la antena sobre ni)-.25 F -.15(ve)
+-.25 G 2.644(ld).15 G .144(el mar)-2.644 F 2.644(,a)-.4 G .144
+(ltura de la antena sobre el promedio del terreno, azimut,)-2.644 F .378
+(distancias y ele)108 542.4 R -.25(va)-.25 G .377(ciones para determina\
+r obstrucciones, Atenuaciones de trayectoria Longle).25 F .377
+(y-Rice, e inten-)-.15 F 1.081(sidad de se\361al recibida, Adicionalmen\
+te, los requisitos m\355nimos necesarios de altura de las antenas)108
+554.4 R(para)6.081 E 1.31(establecer trayectorias de comunicaci\363n de\
+ l\355nea-de-vista sin obstrucciones debido al terreno, la primera)108
+566.4 R(zona de Fresnel, y cualquier porcentaje de\214nido por el usuar\
+io de la primera zona de Fresnel.)108 578.4 Q F2(SPLA)108 602.4 Q(T!)
+-.95 E F0 3.662(produce informes, gr\341\214cos, y)6.162 F 3.662
+(mapas topogr\341\214cos altamente detallados y cuidadosamente)8.662 F
+.605(descritos que presentan las trayectorias de l\355nea-de-vista,)108
+614.4 R .605(contornos re)5.605 F .605
+(gionales de p\351rdidas por trayectoria)-.15 F 3.862(yc)108 626.4 S
+1.362(ontornos de intensidad de se\361al a tra)-3.862 F 1.363(v\351s de\
+ los cuales se puede determinar la predicci\363n del \341rea de)-.2 F
+.374(cobertura de sistemas de transmisores y)108 638.4 R .374(repetidor\
+as. Al realizar an\341lisis de l\355nea de vista y p\351rdidas Long-)
+5.374 F(le)108 650.4 Q .444(y-Rice cuando se emplean m\372ltiples sitio\
+s de transmisores o repetidores,)-.15 F F2(SPLA)2.944 E(T!)-.95 E F0
+.445(determina las \341reas de)2.945 F(cobertura indi)108 662.4 Q
+(viduales y)-.25 E 2.5(mutuas dentro)5 F(de la red especi\214cada.)2.5 E
+.564(Simplemente tipee)108 686.4 R/F4 10/Courier@0 SF(splat)3.064 E F0
+.564(en la consola de comandos, esto retornar\341 un resumen de las opc\
+iones de l\355nea)3.064 F(de comando de)108 698.4 Q F2(SPLA)2.5 E(T!)
+-.95 E F0(:)A(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F
+(de Septiembre de 2007)2.5 E(1)176.785 E EP
+%%Page: 2 2
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(--==[ SPLAT! v1.2.1 Available Options... ]==--)186 84 Q
+(-t txsite\(s\).qth \( max 4 con -c, max 30 con -L\))114 108 Q
+(-r rxsite.qth \(sitio de recepci\363n\))114 120 Q
+(-c grafica la cobertura)114 132 Q
+(del TX\(s\) \(antena RX a X pies/metros SNT\))12 E(-L grafica p\351rdi\
+das por trayectoria del TX \(RX a X pies/metros SNT\))114 144 Q
+(-s nombre de archivo\(s\) de ciudades/sitios a importar \(max 5\))114
+156 Q(-b nombre de archivo\(s\) de l\355mites cartogr\341ficos a import\
+ar \(max 5\))114 168 Q
+(-p nombre de archivo para graficar el perfil del terreno)114 180 Q
+(-e nombre de archivo para graficar la elevaci\363n del terreno)114 192
+Q(-h nombre de archivo para graficar la altura del terreno)114 204 Q
+(-H nombre de archivo para graficar la altura normalizada del terreno)
+114 216 Q(-l nombre de archivo para graficar el modelo Longley-Rice)114
+228 Q(-o nombre de archivo para generar el mapa topogr\341fico \(.ppm\))
+114 240 Q
+(-u nombre del archivo del terreno definido-por-el-usuario a importar)
+114 252 Q(-d directorio que contiene los archivos sdf \(reemplaza ~/.sp\
+lat_path\))114 264 Q(-m multiplicador del radio de la tierra)114 276 Q
+(-n no grafica las rutas de LDV in mapas .ppm)114 288 Q(-N no produce r\
+eportes innecesarios del sitio \363 reportes de obstrucci\363n)114 300 Q
+(-f frecuencia para el c\341lculo de la zona de Fresnel \(MHz\))114 312
+Q(-R modifica el rango por defecto para -c \363 -L \(millas/kil\363metr\
+os\))114 324 Q(-db m\341ximo contorno de p\351rdidas por trayectoria)114
+336 Q(\(80-230 dB\))12 E(-nf no grafica la zona de Fresnel en)114 348 Q
+(los gr\341ficos de)12 E(altura)12 E
+(-fz porcentaje de despeje de la zona de Fresnel \(default = 60\))114
+360 Q(-ngs muestra topograf\355a de escala de grises en blanco \(archiv\
+os .ppm\))114 372 Q
+(-erp valor ERP en lugar del declarado en el archivo .lrp \(Watts\))114
+384 Q(-pli nombre del archivo de entrada de p\351rdidas-por-trayectoria)
+114 396 Q
+(-plo nombre del archivo de salida de p\351rdidas-por-trayectoria)114
+408 Q
+(-udt nombre del archivo de entrada de terreno definido-por-el-usuario)
+114 420 Q(-kml genera archivo compatible Google Earth .kml\(enlaces pun\
+to-a-punto\))114 432 Q(-geo genera un archivo Xastir de georeferencia .\
+geo \(con salida .ppm\))114 444 Q(-metric usa unidades m\351tricas en l\
+ugar de imperiales \(I/O del usuario\))114 456 Q/F2 10.95/Times-Bold@0
+SF(FICHER)72 484.8 Q(OS DE ENTRAD)-.329 E(A)-.383 E/F3 10/Times-Bold@0
+SF(SPLA)108 496.8 Q(T!)-.95 E F0 .5(es una aplicaci\363n manejada por l\
+inea de comandos \363 terminal de te)3 F .5
+(xtos \(shell\), y lee los datos de)-.15 F .002(entrada a tra)108 508.8
+R .001(v\351s de un n\372mero de \214cheros de datos. Algunos archi)-.2
+F -.2(vo)-.25 G 2.501(ss).2 G .001(on oblig)-2.501 F .001
+(atorios para la apropiada eje-)-.05 F 1.2
+(cuci\363n del programa, mientras que otros son opcionales. Los archi)
+108 520.8 R -.2(vo)-.25 G 3.7(so).2 G(blig)-3.7 E 1.2
+(atorios incluyen los modelos)-.05 F .277(topogr\341\214cos 3-arco se)
+108 532.8 R .276(gundo en la forma de archi)-.15 F -.2(vo)-.25 G 2.776
+(sd).2 G 2.776(ed)-2.776 G .276(atos de SPLA)-2.776 F 2.776(T\()-1.11 G
+(archi)-2.776 E -.2(vo)-.25 G 2.776(sS).2 G .276(DF\), archi)-2.776 F
+-.2(vo)-.25 G 2.776(sd).2 G 2.776(el)-2.776 G(ocal-)-2.776 E .752
+(izaci\363n del sitio \(archi)108 544.8 R -.2(vo)-.25 G 3.252(sQ).2 G
+.752(TH\), y archi)-3.252 F -.2(vo)-.25 G 3.252(sd).2 G 3.252(ep)-3.252
+G .752(ar\341metros para el modelo)-3.252 F(Longle)5.752 E .753
+(y-Rice \(archi)-.15 F -.2(vo)-.25 G 3.253(sL).2 G(RP\).)-3.253 E 2.409
+(Los archi)108 556.8 R -.2(vo)-.25 G 4.909(so).2 G 2.409
+(pcionales incluyen archi)-4.909 F -.2(vo)-.25 G 4.908(sd).2 G 4.908(el)
+-4.908 G 2.408(ocalizaci\363n de ciudades/sitios, archi)-4.908 F -.2(vo)
+-.25 G 4.908(sd).2 G 4.908(el)-4.908 G 2.408(\355mites car)-4.908 F(-)
+-.2 E 1.586(togr\341\214cos, archi)108 568.8 R -.2(vo)-.25 G 4.086(sd).2
+G 4.086(et)-4.086 G 1.587(erreno de\214nidos por el usuario, archi)
+-4.086 F -.2(vo)-.25 G 4.087(sd).2 G 4.087(ee)-4.087 G 1.587
+(ntrada de p\351rdidas-por)-4.087 F(-trayectoria,)-.2 E(archi)108 580.8
+Q -.2(vo)-.25 G 2.5(sd).2 G 2.5(ep)-2.5 G
+(atrones de radiaci\363n de antenas, y archi)-2.5 E -.2(vo)-.25 G 2.5
+(sd).2 G 2.5(ed)-2.5 G(e\214nici\363n de color)-2.5 E(.)-.55 E F2
+(FICHER)72 597.6 Q(OS DE D)-.329 E -.855 -1.04(AT O)-.383 H 2.738(SS)
+1.04 G(PLA)-2.738 E(T)-1.04 E F3(SPLA)108 609.6 Q(T!)-.95 E F0 2.01
+(importa los datos topogr\341\214cos desde los \214cheros de datos SPLA)
+4.51 F 4.51(T\()-1.11 G 2.01(SDFs\). Estos archi)-4.51 F -.2(vo)-.25 G
+4.51(ss).2 G(e)-4.51 E .395(pueden generar desde v)108 621.6 R .395
+(arias fuentes de informaci\363n.)-.25 F .396
+(En los Estados Unidos, los \214cheros de datos)5.395 F(SPLA)5.396 E(T)
+-1.11 E .501(se pueden generar a tra)108 633.6 R .501(v\351s de la U.S.)
+-.2 F .501(Geological Surv)5.501 F .801 -.15(ey D)-.15 H .5(igital Ele)
+.15 F -.25(va)-.25 G .5(tion Models \(DEMs\) usando la her).25 F(-)-.2 E
+.07(ramienta usgs2sdf incluida con)108 645.6 R F3(SPLA)2.57 E(T!)-.95 E
+F0 2.57(.L)C .07(os modelos de ele)-2.57 F -.25(va)-.25 G .07
+(ci\363n digital USGS compatibles con esta util-).25 F
+(idad pueden ser descar)108 657.6 Q -.05(ga)-.18 G(dos de:).05 E/F4 10
+/Times-Italic@0 SF(http://edcftp.cr)2.5 E(.usgs.go)-1.11 E
+(v/pub/data/DEM/250/)-.1 E F0(.)A .242(Una resoluci\363n signi\214cati)
+108 681.6 R -.25(va)-.25 G .241
+(mente mejor se puede obtener con el uso de los modelos digitales de).25
+F(ele)5.241 E -.25(va)-.25 G(ci\363n).25 E -.15(ve)108 693.6 S 1.612
+(rsi\363n 2 SR).15 F 1.612(TM-3. Estos modelos son el resultado de la m\
+isi\363n topograf\355ca del radar)-.6 F 1.612(espacial Shuttle)6.612 F
+1.226(STS-99, y est\341n disponibles para la mayor\355a de las re)108
+705.6 R 1.225(giones pobladas de la tierra. Los \214cheros de datos)-.15
+F(SPLA)108 717.6 Q 2.98(Tp)-1.11 G .48
+(ueden ser generados desde los datos SR)-2.98 F .48
+(TM usando la herramienta incluida srtm2sdf. Los archi)-.6 F -.2(vo)-.25
+G(SR)108 729.6 Q 13.883(TM-3 v)-.6 F 13.883
+(ersi\363n 2 se pueden obtener a tra)-.15 F 13.882
+(v\351s de FTP an\363nimo desde:)-.2 F(KD2BD Softw)72 768 Q 107.455
+(are 16)-.1 F(de Septiembre de 2007)2.5 E(2)176.785 E EP
+%%Page: 3 3
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Times-Italic@0
+SF(ftp://e0srp01u.ecs.nasa.go)108 84 Q(v:21/srtm/ver)-.1 E(sion2/)-.1 E
+F0 .706(La utilidad)108 108 R/F2 10/Times-Bold@0 SF(strm2sdf)3.206 E F0
+.707(tambi\351n puede ser usada para con)3.206 F -.15(ve)-.4 G 3.207
+(rtir los).15 F .707(datos SR)3.207 F .707(TM 3-arco se)-.6 F .707
+(gundo en formato)-.15 F 2.484(Band Interlea)108 120 R -.15(ve)-.2 G
+4.984(db).15 G 4.984(yL)-4.984 G 2.484(ine \(.BIL\) para usar con)-4.984
+F F2(SPLA)4.983 E(T!)-.95 E F0 7.483(.E)C 2.483
+(stos datos est\341n disponibles v\355a web en:)-7.483 F F1
+(http://seamless.usgs.go)108 132 Q(v/website/seamless/)-.1 E F0 .03
+(los datos Band Interlea)108 156 R -.15(ve)-.2 G 2.53(db).15 G 2.53(yL)
+-2.53 G .03(ine deben ser descar)-2.53 F -.05(ga)-.18 G .03
+(dos en una manera espec\355\214ca para ser compatible con).05 F F2
+(srtm2sdf)108 168 Q F0(y)2.961 E F2(SPLA)2.961 E(T!)-.95 E F0 2.961(.p)C
+.461(or f)-2.961 F -.2(avo)-.1 G 2.961(rc).2 G .461
+(onsulte la documentaci\363n)-2.961 F F2(srtm2sdf)2.961 E F0 1.561 -.55
+('s p)D .46(ara instrucciones sobre la descar).55 F -.05(ga)-.18 G
+(de datos topogr\341\214cos .BIL a tra)108 180 Q(v\351s del Sitio W)-.2
+E(eb USGS')-.8 E 2.5(sS)-.55 G(eamless.)-2.5 E 3.172(Ap)108 204 S .672
+(esar de la e)-3.172 F .672(xactitud m\341s alta que los datos SR)-.15 F
+.672(TM ofrecen, e)-.6 F 3.172(xisten algunos)-.15 F -.25(va)3.172 G
+.673(c\355os en los conjuntos de).25 F .126
+(datos. Cuando se detectan estos v)108 216 R .126(ac\355os, la utilidad)
+-.25 F F2(srtm2sdf)2.626 E F0 .125(los substituye por los datos)2.626 F
+.125(encontrados en los)5.125 F(archi)108 228 Q -.2(vo)-.25 G 2.956(sS)
+.2 G .456(DF e)-2.956 F .456(xistentes \(que presumiblemente fueron cre\
+ados de datos anteriores de la USGS con la utili-)-.15 F(dad)108 240 Q
+F2(usgs2sdf)3.702 E F0 1.202(\). Si los datos SDF)B 3.701(,U)-.8 G
+(SGS-deri)-3.701 E -.25(va)-.25 G 1.201
+(dos no est\341n disponibles, los v).25 F 1.201
+(ac\355os se reemplazan con el)-.25 F(promedio de los pix)108 252 Q
+(eles adyacentes, o reemplazo directo.)-.15 E .074
+(Los \214cheros de datos de SPLA)108 276 R 2.574(Tc)-1.11 G .074
+(ontienen v)-2.574 F .074(alores enteros de las ele)-.25 F -.25(va)-.25
+G .074(ciones topogr\341\214cas \(en metros\) refer).25 F(-)-.2 E 1.013
+(enciados al ni)108 288 R -.15(ve)-.25 G 3.513(ld).15 G 1.013
+(el mar para re)-3.513 F 1.013(giones de la tierra de 1-grado por 1-gra\
+do con una resoluci\363n de 3-arco)-.15 F(se)108 300 Q .53
+(gundos. Los archi)-.15 F -.2(vo)-.25 G 3.03(sS).2 G .53
+(DF pueden ser le\355dos desde el formato est\341ndar \()-3.03 F F1
+(.sdf)A F0 3.03(\)g)C .53(enerado por las utilidades)-3.03 F F2
+(usgs2sdf)108 312 Q F0(y)5.104 E F2(srtm2sdf)2.604 E F0 2.603(,\363e)C
+2.603(nf)-2.603 G .103
+(ormato comprimido bzip2 \(.sdf .bz2\). Puesto que los archi)-2.603 F
+-.2(vo)-.25 G 2.603(ss).2 G .103(in comprimir se)-2.603 F .043
+(pueden procesar ligeramente m\341s r\341pido que los archi)108 324 R
+-.2(vo)-.25 G 2.544(sc).2 G(omprimidos,)-2.544 E F2(SPLA)2.544 E(T!)-.95
+E F0 -.2(bu)2.544 G .044(sca los datos SDF nece-).2 F .958(sarios en fo\
+rmato sin comprimir primero. Si los datos sin comprimir no pueden ser l\
+ocalizados,)108 336 R F2(SPLA)3.458 E(T!)-.95 E F0 .384(entonces b)108
+348 R .384(usca los datos en formato comprimido)-.2 F .384
+(bzip2. Si tampoco se pueden encontrar los archi)5.384 F -.2(vo)-.25 G
+2.884(sS).2 G(DF)-2.884 E .275(comprimidos para la re)108 360 R .275
+(gi\363n solicitada,)-.15 F F2(SPLA)2.775 E(T!)-.95 E F0 .274
+(asume que la re)2.775 F .274
+(gi\363n es el oc\351ano, y asignar\341 una ele)-.15 F -.25(va)-.25 G
+(ci\363n).25 E(del ni)108 372 Q -.15(ve)-.25 G 2.5(ld).15 G
+(el mar a estas \341reas.)-2.5 E .462(Esta caracter\355stica de)108 396
+R F2(SPLA)2.962 E(T!)-.95 E F0 .463(permite realizar el an\341lisis de \
+trayectorias no solamente sobre la tierra, sino)2.962 F 1.968(tambi\351\
+n entre las \341reas costeras no representadas por los datos del Modelo\
+ de Ele)108 408 R -.25(va)-.25 G 1.968(ci\363n Digital.).25 F(Sin)6.968
+E(embar)108 420 Q .518(go, este comportamiento de)-.18 F F2(SPLA)3.018 E
+(T!)-.95 E F0 .519(resalta la importancia de tener todos los archi)3.018
+F -.2(vo)-.25 G 3.019(sS).2 G .519(DF requeri-)-3.019 F(dos para la re)
+108 432 Q
+(gi\363n a ser analizada, para as\355 obtener resultados signi\214cati)
+-.15 E -.2(vo)-.25 G(s.).2 E/F3 10.95/Times-Bold@0 SF(ARCHIV)72 448.8 Q
+(OS DE LOCALIZA)-.493 E(CI\323N DEL SITIO \(QTH\))-.602 E F2(SPLA)108
+460.8 Q(T!)-.95 E F0(SPLA)2.705 E .205(T! importa la)-1.11 F .205(infor\
+maci\363n de la localizaci\363n de los sitios del transmisor y del rece\
+ptor anal-)5.205 F .004(izados por el programa de los archi)108 472.8 R
+-.2(vo)-.25 G 2.504(sA).2 G .004(SCII que tienen una e)-2.504 F
+(xtensi\363n)-.15 E F1(.qth)2.504 E F0 2.504(.L)C .004(os archi)-2.504 F
+-.2(vo)-.25 G 2.504(sQ).2 G .005(TH contienen el)-2.504 F .542
+(nombre del sitio, la latitud del sitio \(positi)108 484.8 R 1.042 -.25
+(va a)-.25 H 3.042(ln).25 G .542(orte del ecuador)-3.042 F 3.042(,n)-.4
+G -2.25 -.15(eg a)-3.042 H(ti).15 E 1.042 -.25(va a)-.25 H 3.042(ls).25
+G .542(ur\), la longitud del sitio \(en)-3.042 F .51(grados oeste W de \
+0 a 360 grados\), y; La altura de la antena del sitio sobre el ni)108
+496.8 R -.15(ve)-.25 G 3.011(ld).15 G .511(el suelo \(A)-3.011 F .511
+(GL\), cada)-.4 F .405(uno separado por un caracter de salto-de-l\355ne\
+a. La altura de la antena se asume a ser especi\214cada en pies a)108
+508.8 R .392(menos que sea se)108 520.8 R .392(guida por la letra)-.15 F
+F1(m)2.892 E F0 2.892(od)2.892 G 2.892(el)-2.892 G 2.892(ap)-2.892 G
+(alabra)-2.892 E F1(meter)5.392 E(s)-.1 E F0 .393
+(en may\372sculas \363 min\372sculas. La informaci\363n)5.392 F .571
+(de la latitud y de la longitud se puede e)108 532.8 R .571(xpresar en)
+-.15 F .571(formato decimal \(74.6889\) \363 en formato grados, minu-)
+5.571 F(tos, se)108 544.8 Q(gundos \(DMS\) \(74 41 20.0\).)-.15 E .356
+(Por ejemplo, un archi)108 568.8 R .756 -.2(vo d)-.25 H 2.856(el).2 G
+.356(ocalizaci\363n de sitio que describ\355a la estaci\363n de tele)
+-2.856 F .356(visi\363n WNJT)-.25 F(-DT)-.92 E 2.856(,T)-.74 G(renton,)
+-3.206 E(NJ \()108 580.8 Q F1(wnjt-dt.qth)A F0 2.5(\)s)C 2.5(ep)-2.5 G
+2.5(uede leer)-2.5 F(como sigue:)2.5 E/F4 10/Courier@0 SF(WNJT-DT)156
+616.8 Q(40.2828)156 628.8 Q(74.6864)156 640.8 Q(990.00)156 652.8 Q F0 .6
+(Cada sitio de transmisor y receptor analizado por)108 688.8 R F2(SPLA)
+3.1 E(T!)-.95 E F0 .6(debe ser representado por su propio archi)3.1 F 1
+-.2(vo d)-.25 H(e).2 E(la localizaci\363n de sitio \(QTH\).)108 700.8 Q
+(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(3)176.785 E EP
+%%Page: 4 4
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10.95
+/Times-Bold@0 SF(ARCHIV)72 84 Q(OS DE P)-.493 E(AR\301METR)-.81 E
+(OS LONGLEY)-.329 E(-RICE \(LRP\))-1.007 E F0 .299(Los archi)108 96 R
+-.2(vo)-.25 G 2.799(sd).2 G 2.799(ed)-2.799 G .299
+(atos de par\341metros Longle)-2.799 F .299(y-Rice son requeridos por)
+-.15 F/F2 10/Times-Bold@0 SF(SPLA)2.799 E(T!)-.95 E F0 .3
+(para determinar ls p\351rdidas)2.8 F .564(por trayectoria RF ya sea en\
+ el modo punto-a-punto \363 predicci\363n de \341rea. Los datos de par\
+\341metros para el)108 108 R .16(modelo Longle)108 120 R .16
+(y-Rice desde archi)-.15 F -.2(vo)-.25 G 2.66(sq).2 G .16
+(ue tienen el mismo nombre base del archi)-2.66 F .56 -.2(vo Q)-.25 H
+.16(TH del sitio del trans-).2 F(misor)108 132 Q 2.5(,p)-.4 G(ero con e)
+-2.5 E(xtensi\363n)-.15 E/F3 10/Times-Italic@0 SF(.lrp)2.5 E F0 2.5(.L)C
+(os Archi)-2.5 E -.2(vo)-.25 G(s).2 E F2(SPLA)2.5 E(T!)-.95 E F0
+(LRP comparte el siguiente formato \()2.5 E F3(wnjt-dt.lrp)A F0(\):)A/F4
+10/Courier@0 SF 6(15.000 ;)156 168 R
+(Earth Dielectric Constant \(Relative permittivity\))6 E 12(0.005 ;)156
+180 R(Earth Conductivity \(Siemens per meter\))6 E
+(301.000 ; Atmospheric Bending Constant \(N-units\))156 192 Q
+(647.000 ; Frequency in MHz \(20 MHz to 20 GHz\))156 204 Q 42(5;)156 216
+S(Radio Climate \(5 = Continental Temperate\))-36 E 42(0;)156 228 S
+(Polarization \(0 = Horizontal, 1 = Vertical\))-36 E 18(0.50 ;)156 240 R
+(Fraction of situations \(50% of locations\))6 E 18(0.90 ;)156 252 R
+(Fraction of time \(90% of the time\))6 E
+(46000.0 ; ERP in Watts \(optional\))156 264 Q F0 1.938(Si un archi)108
+300 R 2.338 -.2(vo L)-.25 H 1.938(RP correspondiente al archi).2 F 2.338
+-.2(vo Q)-.25 H 1.938
+(TH del sitio de transmisi\363n no puede ser encontrado,).2 F F2(SPLA)
+108 312 Q(T!)-.95 E F0 -.15(ex)3.373 G .873
+(plorar\341 el directorio de trabajo actual b).15 F .874
+(uscando el archi)-.2 F 1.274 -.2(vo ")-.25 H .874
+(splat.lrp". Si este archi).2 F 1.274 -.2(vo t)-.25 H(ampoco).2 E .235(\
+puede ser encontrado, entonces los par\341metros por defecto enumerados\
+ arriba ser\341n asignados por)108 324 R F2(SPLA)2.735 E(T!)-.95 E F0
+2.923(yu)108 336 S 2.923(na)-2.923 G(rchi)-2.923 E .823 -.2(vo c)-.25 H
+.423(orrespondiente "splat.lrp" conteniendo estos par\341metros por def\
+ecto ser\341 escrito al directorio).2 F(actual de trabajo. El archi)108
+348 Q .4 -.2(vo ")-.25 H(splat.lrp" generado se puede editar de acuerdo\
+ a las necesidades del usuario.).2 E
+(Las constantes diel\351ctricas t\355picas de la tierra y sus v)108 372
+Q(alores de conducti)-.25 E(vidad son los siguientes:)-.25 E F4
+(Dielectric Constant)270 408 Q(Conductivity)12 E(Salt water)156 420 Q 48
+(:8)42 G 96(05)-48 G(.000)-96 E(Good ground)156 432 Q 48(:2)36 G 96(50)
+-48 G(.020)-96 E(Fresh water)156 444 Q 48(:8)36 G 96(00)-48 G(.010)-96 E
+(Marshy land)156 456 Q 48(:1)36 G 96(20)-48 G(.007)-96 E
+(Farmland, forest :)156 468 Q 90(15 0.005)48 F(Average ground)156 480 Q
+48(:1)18 G 96(50)-48 G(.005)-96 E(Mountain, sand)156 492 Q 48(:1)18 G 96
+(30)-48 G(.002)-96 E 72(City :)156 504 R 96(50)54 G(.001)-96 E
+(Poor ground)156 516 Q -18 54(:4 0)36 H(.001)-54 E F0
+(Los c\363digos de Clima de Radio usados por)108 552 Q F2(SPLA)2.5 E(T!)
+-.95 E F0(son los siguientes:)2.5 E F4(1: Equatorial \(Congo\))156 588 Q
+(2: Continental Subtropical \(Sudan\))156 600 Q
+(3: Maritime Subtropical \(West coast of Africa\))156 612 Q
+(4: Desert \(Sahara\))156 624 Q(5: Continental Temperate)156 636 Q
+(6: Maritime Temperate, over land \(UK and west coasts of US & EU\))156
+648 Q(7: Maritime Temperate, over sea)156 660 Q F0 .46(El clima templad\
+o continental es com\372n a las grandes masas de la tierra en la zona t\
+emplada, tal como los)108 696 R .131(Estados Unidos. P)108 708 R .131(a\
+ra trayectorias inferiores a 100 kil\363metros, es poca la diferencia e\
+ntre los climas templa-)-.15 F(dos continentales y mar\355timos.)108 720
+Q(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(4)176.785 E EP
+%%Page: 5 5
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .665
+(Los par\341metros s\351ptimo y octa)108 84 R 1.065 -.2(vo e)-.2 H 3.165
+(ne).2 G 3.165(la)-3.165 G(rchi)-3.165 E -.2(vo)-.25 G/F1 10
+/Times-Italic@0 SF(.lrp)3.365 E F0 .665
+(corresponden al an\341lisis estad\355stico proporcionado por)3.165 F
+.43(el modelo Longle)108 96 R .43(y-Rice. En este ejemplo,)-.15 F/F2 10
+/Times-Bold@0 SF(SPLA)2.929 E(T!)-.95 E F0(de)2.929 E -.2(vo)-.25 G(lv)
+.2 E .429(er\341 la m\341xima p\351rdida de trayectoria que ocurre)-.15
+F .733(el 50%)108 108 R .733(del tiempo \(fracci\363n del tiempo\) en e\
+l 90% de las situaciones \(fracci\363n de situaciones\). Esto es a)5.733
+F .136(menudo denotado como F\(50,90\) en los estudios Longle)108 120 R
+.135(y_Rice. En los Estados Unidos un criterio F\(50,90\))-.15 F .232
+(es t\355picamente usado para tele)108 132 R .233
+(visi\363n digital \(8-le)-.25 F -.15(ve)-.25 G 2.733(lV).15 G .233
+(SB modulation\), mientras que F\(50,50\) es usado para)-2.733 F
+(radiodifusi\363n anal\363gica \(VSB-AM+NTSC\).)108 144 Q -.15(Pa)108
+168 S 3.32
+(ra mayor informaci\363n de esos par\341metros, puede visitar:).15 F F1
+(http://\215attop.its.bldr)5.82 E(doc.go)-.37 E(v/itm.html)-.1 E F0(and)
+5.82 E F1(http://www)108 180 Q(.softwright.com/faq/engineering/pr)-.74 E
+(op_longle)-.45 E(y_rice)-.3 E(.html)-.15 E F0 1.08
+(El par\341metro \214nal en el archi)108 204 R -.2(vo)-.25 G F1(.lrp)
+3.78 E F0 1.08(corresponde a la potencia efecti)3.58 F 1.58 -.25(va r)
+-.25 H 1.08(adiada, y es opcional. Si esta es).25 F .441
+(incluida en el archi)108 216 R .841 -.2(vo s)-.25 H .441
+(e\361al y los contornos de ni).2 F -.15(ve)-.25 G .44
+(les de intensidad de campo cuando se realicen los estu-).15 F .23
+(dios Longle)108 228 R .231(y-rice. Si el par\341metro es omitido, se c\
+omputan las p\351rdidas por trayectoria en su lug)-.15 F(ar)-.05 E 2.731
+(.E)-.55 G 2.731(lE)-2.731 G(RP)-2.731 E(pro)108 240 Q 1.136
+(visto en el archi)-.15 F -.2(vo)-.25 G F1(.lrp)3.836 E F0 1.136
+(puede ser in)3.636 F -.25(va)-.4 G 1.136(lidado usando la opci\363n).25
+F F2(SPLA)3.636 E(T!)-.95 E F0 1.136(de l\355nea-de-comando)3.636 F F1
+(-erp)3.636 E F0(sin)3.636 E(tener que editar el archi)108 252 Q -.2(vo)
+-.25 G F1(.lrp)2.7 E F0(para conse)2.5 E(guir el mismo resultado.)-.15 E
+/F3 10.95/Times-Bold@0 SF(ARCHIV)72 268.8 Q(OS DE LOCALIZA)-.493 E
+(CI\323N DE CIUD)-.602 E(ADES)-.383 E F0 .373(Los nombres y las localiz\
+aciones de ciudades, sitios de la torre, u otros puntos de inter\351s s\
+e pueden impor)108 280.8 R(-)-.2 E .335
+(tar y trazar en los mapas topogr\341\214cos generados por)108 292.8 R
+F2(SPLA)2.834 E(T!)-.95 E F0(.)A F2(SPLA)2.834 E(T!)-.95 E F0 .334
+(importa los nombres de ciudades y)2.834 F 1.686
+(localizaciones de los archi)108 304.8 R -.2(vo)-.25 G 4.186(sA).2 G
+1.686(SCII que contienen el nombre, latitud y longitud de la localizaci\
+\363n de)-4.186 F .647(inter\351s. Cada campo es separado por una coma.)
+108 316.8 R .646(Cada e)5.646 F .646
+(xpediente es separado por un caracter de salto-de-)-.15 F .163
+(linea. Al igual que con los archi)108 328.8 R -.2(vo)-.25 G(s).2 E F1
+(.qth)2.663 E F0 2.663(,l)C 2.663(ai)-2.663 G .164
+(nformaci\363n de la latitud y la longitud se puede ingresar en)-2.663 F
+(for)5.164 E(-)-.2 E
+(mato decimal \363 en formato de grados, minutos, se)108 340.8 Q
+(gundos \(DMS\).)-.15 E(Por ejemplo \()108 364.8 Q F1(cities.dat)A F0
+(\):)A/F4 10/Courier@0 SF(Teaneck, 40.891973, 74.014506)156 388.8 Q
+(Tenafly, 40.919212, 73.955892)156 400.8 Q
+(Teterboro, 40.859511, 74.058908)156 412.8 Q
+(Tinton Falls, 40.279966, 74.093924)156 424.8 Q
+(Toms River, 39.977777, 74.183580)156 436.8 Q
+(Totowa, 40.906160, 74.223310)156 448.8 Q(Trenton, 40.219922, 74.754665)
+156 460.8 Q F0 .765(Un total de cinco \214cheros de datos separados de \
+ciudades se pueden importar a la v)108 496.8 R .764
+(ez, y no hay l\355mite al)-.15 F 2.46(tama\361o de estos archi)108
+508.8 R -.2(vo)-.25 G(s.).2 E F2(SPLA)7.46 E(T!)-.95 E F0 2.46
+(lee datos de las ciudades en base a "primero ingresada primero)4.96 F
+.91(servida", y traza solamente las localizaciones cuyas anotaciones no\
+ est\351n en con\215icto con anotaciones de)108 520.8 R .483
+(las localizaciones le\355das anteriormente durante en el archi)108
+532.8 R .884 -.2(vo a)-.25 H .484
+(ctual de datos de ciudades, \363 en archi).2 F .884 -.2(vo p)-.25 H
+(re-).2 E 1.008(vios. Este comportamiento en)108 544.8 R F2(SPLA)3.508 E
+(T!)-.95 E F0 1.008(reduce al m\355nimo el alboroto al generar)6.008 F
+1.007(los mapas topogr\341\214cos,)6.008 F 2.061(pero tambi\351n determ\
+ina que por mandato las localizaciones importantes est\351n puestas al \
+principio del)108 556.8 R 1.14(primer \214chero de datos de ciudades, y\
+ las localizaciones de menor importancia sean colocadas a contin-)108
+568.8 R
+(uaci\363n en la lista o en los \214cheros de datos subsecuentes.)108
+580.8 Q 1.075(Los \214cheros de datos de las ciudades se pueden generar\
+ manualmente usando cualquier editor de te)108 604.8 R(xtos,)-.15 E .667
+(importar de otras fuentes, o deri)108 616.8 R -.25(va)-.25 G 3.167(rd)
+.25 G 3.167(el)-3.167 G .666
+(os datos disponibles de la o\214cina de censo de los Estados Unidos,)
+-3.167 F .574(usando la herramienta)108 628.8 R F2(citydecoder)3.074 E
+F0 .574(incluida con)3.074 F F2(SPLA)3.074 E(T!)-.95 E F0 5.574(.E)C
+.574(stos datos est\341n disponibles gratuitamente v\355a)-5.574 F
+(Internet en: http://www)108 640.8 Q(.census.go)-.65 E
+(v/geo/www/cob/bdy_\214les.html, y deben estar en formato ASCII.)-.15 E
+F3(ARCHIV)72 657.6 Q(OS DE D)-.493 E -.855 -1.04(AT O)-.383 H 2.738(SD)
+1.04 G 2.738(EL)-2.738 G(IMITES CAR)-2.738 E -.197(TO)-.438 G
+(GR\301FICOS).197 E F0 .408(Los datos cartogr\341\214cos de l\355mites \
+se pueden tambi\351n importar para trazar los l\355mites de las ciudade\
+s,)108 669.6 R(con-)5.407 E .674
+(dados, o estados en los mapas topogr\341\214cos generados por)108 681.6
+R F2(SPLA)3.174 E(T!)-.95 E F0 3.174(.E)C .675
+(stos datos deben estar en el formato)-3.174 F 5.049(de metadatos)108
+693.6 R 2.549(de archi)5.049 F -.2(vo)-.25 G 5.049(sc).2 G 2.548
+(artogr\341\214cos de l\355mites)-5.049 F 2.548
+(ARC/INFO Ungenerate \(formato ASCII\), y est\341n)7.548 F 7.954(dispon\
+ibles para los E.E.U.U..en la O\214cina de Censos v\355a Internet en:)
+108 705.6 R F1(http://www)10.455 E(.cen-)-.74 E(sus.go)108 717.6 Q(v/g)
+-.1 E(eo/www/cob/co2000.html#ascii)-.1 E F0(y)9.187 E F1(http://www)
+9.187 E(.census.go)-.74 E(v/g)-.1 E(eo/www/cob/pl2000.html#ascii)-.1 E
+F0 9.186(.U)C(n)-9.186 E 1.661(total de cinco archi)108 729.6 R -.2(vo)
+-.25 G 4.162(sc).2 G 1.662
+(artogr\341\214cos separados de l\355mites se puede importar a la v)
+-4.162 F 4.162(ez. No)-.15 F 1.662(es necesario)4.162 F(KD2BD Softw)72
+768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E(5)176.785 E EP
+%%Page: 6 6
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E
+(importar l\355mites de estado si ya)108 84 Q
+(se han importado los l\355mites del condado.)5 E/F1 10.95/Times-Bold@0
+SF(OPERA)72 100.8 Q(CI\323N DEL PR)-.602 E(OGRAMA)-.329 E/F2 10
+/Times-Bold@0 SF(SPLA)108 112.8 Q(T!)-.95 E F0 .059(Debido a que)2.559 F
+F2(SPLA)2.559 E(T!)-.95 E F0 .059(hace un uso intensi)2.559 F .458 -.2
+(vo d)-.25 H .058(el CPU y la memoria, se in).2 F -.2(vo)-.4 G .058
+(ca v\355a l\355nea de coman-).2 F .566
+(dos usando una serie de opciones y ar)108 124.8 R .566
+(gumentos, este tipo de interf)-.18 F .566(az reduce al m\355nimo g)-.1
+F .566(astos indirectos y)-.05 F .228(se presta a operaciones)108 136.8
+R .228(escriptadas \(batch\). El uso de CPU y prioridad de memoria por)
+5.228 F F2(SPLA)2.727 E(T!)-.95 E F0 .227(se pueden)2.727 F
+(modi\214car con el uso de comandos)108 148.8 Q F2(nice)2.5 E F0(Unix.)
+2.5 E .348(El n\372mero y el tipo de opciones pasados a)108 172.8 R F2
+(SPLA)2.848 E(T!)-.95 E F0 .349
+(determinan su modo de operaci\363n y el m\351todo de gen-)2.848 F 1.619
+(eraci\363n de los datos de)108 184.8 R 1.618
+(salida. Casi todos los opciones de)6.619 F F2(SPLA)4.118 E(T!)-.95 E F0
+1.618(se pueden llamar en cascada y en)4.118 F(cualquier orden al in)108
+196.8 Q -.2(vo)-.4 G(car el programa desde la l\355nea de comandos.).2 E
+F2(SPLA)108 220.8 Q(T!)-.95 E F0 .068(opera en dos modos distintos:)
+2.568 F/F3 10/Times-Italic@0 SF .068(modo punto-a-punto)2.568 F F0 2.568
+(,y)C F3 .068(modo de pr)B .068(edicci\363n del \341r)-.37 F .068
+(ea de cobertur)-.37 F(a)-.15 E F0 2.569(,y)C 1.016(puede ser in)108
+232.8 R -.2(vo)-.4 G 1.016(cado por el usuario usando el modo de l\355n\
+ea de vista \(LOS\) \363 el).2 F 3.515(modelo de)6.015 F(propag)3.515 E
+(aci\363n)-.05 E 1.181(sobre terreno irre)108 244.8 R 1.181
+(gular \(ITM\) Longle)-.15 F 1.182(y-Rice. El radio de tierra v)-.15 F
+1.182(erdadera, cuatro-tercios, o cualquier otro)-.15 F
+(radio de la tierra de\214nido-por)108 256.8 Q(-el-usuario pueden ser e\
+speci\214cados al realizar los an\341lisis de l\355nea-de-vista.)-.2 E
+F1(AN\301LISIS PUNT)72 273.6 Q(O-A-PUNT)-.197 E(O)-.197 E F2(SPLA)108
+285.6 Q(T!)-.95 E F0 .744(puede ser utilizado para determinar si e)3.244
+F .743(xiste l\355nea de vista entre dos localizaciones especi\214cadas)
+-.15 F(realizando para ello el an\341lisis del per\214l del terreno. Po\
+r ejemplo:)108 297.6 Q/F4 10/Courier@0 SF
+(splat -t tx_site.qth -r rx_site.qth)108 321.6 Q F0(in)108 345.6 Q -.2
+(vo)-.4 G .229(ca un an\341lisis del per\214l del terreno entre el tran\
+smisor especi\214cado en).2 F F3(tx_site)2.73 E(.qth)-.15 E F0 2.73(ye)
+2.73 G 2.73(lr)-2.73 G .23(eceptor especi\214-)-2.73 F 1.633(cado en)108
+357.6 R F3(rx_site)4.133 E 1.633
+(.qth y escribe un Reporte de Obstrucciones)-.15 F F2(SPLA)4.133 E(T!)
+-.95 E F3 1.632(al dir)4.133 F 1.632(ectorio de tr)-.37 F 1.632
+(abajo actual. El)-.15 F -.37(re)108 369.6 S 1.831
+(porte contiene los detalles de los sitios del tr).37 F 1.831
+(ansmisor y del r)-.15 F(eceptor)-.37 E -6.83 4.331(,e i)-1.11 H 1.832
+(denti\214ca la localizaci\363n de)-4.331 F .097
+(cualquier obstrucci\363n detectada a lo lar)108 381.6 R .097
+(go de la tr)-.37 F .096
+(ayectoria de l\355nea-de-vista. Si una obstrucci\363n puede ser)-.15 F
+.105(despejada le)108 393.6 R .105(vantando la antena de r)-.15 F .106
+(ecepci\363n a una mayor altitud,)-.37 F F2(SPLA)2.606 E(T!)-.95 E F3
+.106(indicar\341 la altur)2.606 F 2.606(am)-.15 G .106(\355nima de la)
+-2.606 F .103(antena r)108 405.6 R .103(equerida par)-.37 F 2.603(aq)
+-.15 G .103(ue e)-2.603 F .103(xista l\355nea-de-vista entr)-.2 F 2.603
+(el)-.37 G .103(as localizaciones del tr)-2.603 F .103(ansmisor y el r)
+-.15 F .102(eceptor especi-)-.37 F 1.428(\214cadas. Observe que las uni\
+dades imperiales \(millas, pies\) se usan por defecto, a menos que se u\
+se la)108 417.6 R(opci\363n -metric en la or)108 429.6 Q(den)-.37 E F2
+(SPLA)2.5 E(T!)-.95 E F3(de l\355nea de comandos.)5 E F4
+(splat -t tx_site.qth -r rx_site.qth -metric)108 453.6 Q F0 .281
+(Si la antena se debe le)108 477.6 R -.25(va)-.25 G .281
+(ntar una cantidad signi\214cati).25 F -.25(va)-.25 G 2.781(,e).25 G .28
+(sta determinaci\363n puede tomar una cierta cantidad)-2.781 F .456
+(de tiempo. Observ)108 489.6 R 2.956(eq)-.15 G .456
+(ue los resultados proporcionados son el)-2.956 F F3(m\355nimo)2.956 E
+F0 .456(necesario para que e)2.956 F .456(xista una trayec-)-.15 F 1.206
+(toria de la l\355nea-de-vista, y en el caso de este simple ejemplo, no\
+ considera los requisitos de la zona de)108 501.6 R(Fresnel.)108 513.6 Q
+.183(Las e)108 537.6 R(xtensiones)-.15 E F3(qth)2.683 E F0 .184
+(son asumidas por SPLA)2.683 F .184(T! para los archi)-1.11 F -.2(vo)
+-.25 G 2.684(sQ).2 G .184(TH, y son opcionales cuando se especi\214-)
+-2.684 F 1.299(can los ar)108 549.6 R 1.299
+(gumentos -t y -r en la l\355nea de comandos.)-.18 F F2(SPLA)3.799 E(T!)
+-.95 E F0 1.298(lee autom\341ticamente todos los \214cheros de)3.799 F
+2.292(datos de SPLA)108 561.6 R 4.793(Tn)-1.11 G 2.293(ecesarios para e\
+l an\341lisis del terreno entre los sitios especi\214cados.)-4.793 F F2
+(SPLA)7.293 E(T!)-.95 E F0 -.2(bu)4.793 G(sca).2 E .447
+(primero los archi)108 573.6 R -.2(vo)-.25 G 2.947(sS).2 G .447
+(DF necesarios)-2.947 F .447
+(en el directorio de trabajo actual. Si estos archi)5.447 F -.2(vo)-.25
+G 2.947(sn).2 G 2.946(os)-2.947 G 2.946(ee)-2.946 G(ncuentran,)-2.946 E
+F2(SPLA)108 585.6 Q(T!)-.95 E F0(entonces b)2.5 E
+(usca en la ruta especi\214cada por la opci\363n)-.2 E F3(-d)2.5 E F0(:)
+A F4(splat -t tx_site -r rx_site -d /cdrom/sdf/)108 609.6 Q F0 .441
+(Una ruta a un directorio e)108 633.6 R .441
+(xterno puede ser especi\214cada creando el archi)-.15 F .841 -.2(vo ")
+-.25 H .442(.splat_path" en el directorio de).2 F 1.104
+(trabajo del usuario. Este archi)108 645.6 R -.2(vo)-.25 G F3
+($HOME/.splat_path)3.804 E F0 1.104
+(debe contener una sola l\355nea de te)3.604 F 1.104(xto ASCII en)-.15 F
+(la)6.104 E(que indique la ruta completa)108 657.6 Q
+(del directorio que contiene todos los archi)5 E -.2(vo)-.25 G 2.5(sS).2
+G(DF)-2.5 E(.)-.8 E F4(/opt/splat/sdf/)108 681.6 Q F0 2.5(Yp)108 705.6 S
+(uede ser generado usando cualquier editor de te)-2.5 E(xto.)-.15 E .201
+(Un gr\341\214co que muestre el per\214l del terreno en funci\363n de l\
+a distancia, partiendo desde el receptor)108 729.6 R 2.702(,e)-.4 G .202
+(ntre las)-2.702 F(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F
+(de Septiembre de 2007)2.5 E(6)176.785 E EP
+%%Page: 7 7
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E(localizaciones del \
+transmisor y receptor se puede generar adicionando la opci\363n)108 84 Q
+/F1 10/Times-Italic@0 SF(-p)2.5 E F0(:)A/F2 10/Courier@0 SF
+(splat -t tx_site -r rx_site -p terrain_profile.png)108 108 Q F0(SPLA)
+108 132 Q 1.623(T! in)-1.11 F -.2(vo)-.4 G 1.623(ca al programa).2 F/F3
+10/Times-Bold@0 SF(gnuplot)4.122 E F0 1.622
+(cuando genera los gr\341\214cos.)4.122 F 1.622(La e)6.622 F 1.622
+(xtensi\363n del nombre del archi)-.15 F -.2(vo)-.25 G 1.974
+(especi\214cado a)108 144 R F3(SPLA)4.474 E(T!)-.95 E F0 1.974
+(determina el formato del gr\341\214co a ser producido)4.474 F F1(.png)
+4.474 E F0 1.974(generar\341 un archi)4.474 F 2.374 -.2(vo d)-.25 H(e).2
+E .766(gr\341\214co PNG a color con una resoluci\363n de 640x480, mient\
+ras que)108 156 R F1(.ps)3.265 E F0(o)3.265 E F1(.postscript)3.265 E F0
+.765(generar\341n archi)3.265 F -.2(vo)-.25 G 3.265(sd).2 G(e)-3.265 E
+.125(salida postscritp. La salida en formatos como GIF)108 168 R 2.625
+(,A)-.8 G .125(dobe Illustrator)-2.625 F 2.625(,A)-.4 G .126
+(utoCAD dxf, LaT)-2.625 F -.15(ex)-.7 G 2.626(,ym).15 G .126
+(uchos otros)-2.626 F .946(est\341n disponibles.)108 180 R .946(Por f)
+5.946 F -.2(avo)-.1 G 3.446(rc).2 G(onsulte)-3.446 E F3(gnuplot)3.446 E
+F0 3.446(,yl)C 3.446(ad)-3.446 G .946(ocumentaci\363n de)-3.446 F F3
+(gnuplot)3.446 E F0 .946(para detalles de todos los)3.446 F
+(formatos de salida soportados.)108 192 Q .622(En el lado del receptor)
+108 216 R .623(un gr\341\214co de ele)5.623 F -.25(va)-.25 G .623
+(ciones en funci\363n de la distancia determinado por el \341ngulo de)
+.25 F(inclinaci\363n debido al terreno entre el receptor y el transmiso\
+r se puede generar usando la opci\363n)108 228 Q F1(-e)2.5 E F0(:)A F2
+(splat -t tx_site -r rx_site -e elevation_profile.png)108 252 Q F0 .338
+(El gr\341\214co producido usando esta opci\363n ilustra los \341ngulos\
+ de ele)108 276 R -.25(va)-.25 G .338(ci\363n y depresi\363n).25 F .338
+(resultado del terreno)7.838 F .952(entre la localizaci\363n del recept\
+or y el sitio del transmisor desde la perspecti)108 288 R 6.453 -.25
+(va d)-.25 H .953(el receptor).25 F 3.453(.U)-.55 G 3.453(ns)-3.453 G
+-.15(eg)-3.453 G(undo).15 E .055(trazo es dib)108 300 R .055(ujado entr\
+e el lado izquierdo del gr\341\214co \(localizaci\363n del receptor\) y\
+ la localizaci\363n de la antena)-.2 F .032(que transmite a la derecha.)
+108 312 R .032(Este trazo ilustra el \341ngulo de ele)5.032 F -.25(va)
+-.25 G .033(ci\363n requerido para que e).25 F 2.533(xista una)-.15 F
+(trayecto-)2.533 E .775
+(ria de l\355nea-de-vista entre el receptor y transmisor)108 324 R 3.275
+(.S)-.55 G 3.275(il)-3.275 G 3.275(at)-3.275 G .774
+(raza interseca el per\214l de ele)-3.275 F -.25(va)-.25 G .774
+(ci\363n en cualquier).25 F .469(punto del gr\341\214co, entonces esto \
+es una indicaci\363n que bajo las condiciones dadas no e)108 336 R .47
+(xiste una trayectoria)-.15 F .612(de l\355nea-de-vista, y las obstrucc\
+iones se pueden identi\214car claramente en el gr\341\214co en los punt\
+os de inter)108 348 R(-)-.2 E(secci\363n.)108 360 Q .419(Un gr\341\214c\
+o ilustrando la altura del terreno referenciado a la trayectoria de l\
+\355nea-de-vista entre el transmisor)108 384 R 2.5(ye)108 396 S 2.5(lr)
+-2.5 G(eceptor se puede generar usando la opci\363n)-2.5 E F1(-h)2.5 E
+F0(:)A F2(splat -t tx_site -r rx_site -h height_profile.png)108 420 Q F0
+.141(La altura del terreno normalizada a las alturas de las antenas del\
+ transmisor y receptor pueden ser obtenidas)108 444 R(con la opci\363n)
+108 456 Q F1(-H)2.5 E F0(:)A F2
+(splat -t tx_site -r rx_site -H normalized_height_profile.png)108 480 Q
+F0(El contorno de curv)108 504 Q(atura de la T)-.25 E
+(ierra tambi\351n es gra\214cada en este modo.)-.35 E .074(La primera Z\
+ona de Fresnel, y el 60% de la primera Zona de Fresnel puede ser adicio\
+nada al gr\341\214co de per)108 528 R(-)-.2 E .62
+(\214les de altura con la opci\363n)108 540 R F1(-f)3.12 E F0 3.12(,ye)C
+.62(speci\214cando una frecuencia \(en MHz\) a la cual la Zona de Fresn\
+el ser\341)-3.12 F(modelada:)108 552 Q F2(splat -t tx_site -r rx_site -\
+f 439.250 -H normalized_height_profile.png)108 576 Q F0 .085(Zonas de d\
+espeje de la zona de Fresnel distintas al 60% pueden ser especi\214cada\
+s usando la opci\363n)108 600 R F1(-fz)2.585 E F0(como)2.585 E(sigue:)
+108 612 Q F2
+(splat -t tx_site -r rx_site -f 439.250 -fz 75 -H height_profile2.png)
+108 636 Q F0
+(Un gr\341\214co que muestre las p\351rdidas de trayectoria Longle)108
+660 Q(y-Rice se puede dib)-.15 E(ujar usando la opci\363n)-.2 E F1(-l)
+2.5 E F0(:)A F2(splat -t tx_site -r rx_site -l path_loss_profile.png)108
+684 Q F0(Como antes, adicionando la opci\363n)108 708 Q F1(-metric)2.5 E
+F0(se forza al gr\341\214co a usar unidades de medida m\351trica.)2.5 E
+(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(7)176.785 E EP
+%%Page: 8 8
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .173
+(Al realizar un an\341lisis punto-a-punto, un reporte)108 84 R/F1 10
+/Times-Bold@0 SF(SPLA)2.673 E(T!)-.95 E F0 .173
+(de an\341lisis de trayectoria es generado en la forma)2.673 F .985
+(de un archi)108 96 R 1.385 -.2(vo d)-.25 H 3.485(et).2 G -.15(ex)-3.485
+G .985(to con una e).15 F .985(xtensi\363n de archi)-.15 F -.2(vo)-.25 G
+/F2 10/Times-Italic@0 SF(.txt)3.685 E F0 3.485(.E)C 3.485(lr)-3.485 G
+.985(eporte contiene azimut y distancias entre el)-3.485 F .844
+(transmisor y receptor)108 108 R 3.344(,a)-.4 G .843(s\355 mismo cuando\
+ se analizan las perdidas por espacio-libre y trayectoria Longle)-3.344
+F(y-)-.15 E .581(Rice. El modo de propag)108 120 R .581
+(aci\363n para la trayectoria est\341 dado como)-.05 F F2(L\355nea-de-V)
+3.082 E(ista)-.74 E F0(,)A F2 .582(Horizonte Simple)3.082 F F0(,)A F2
+(Hori-)3.082 E(zonte Doble)108 132 Q F0(,)A F2(Difr)2.5 E
+(acci\363n dominante)-.15 E F0 2.5<2cf3>C F2 -1.85 -.55(Tr o)D
+(poscatter dominante).55 E F0(.)A .143(Distancias y localizaciones para\
+ identi\214car las obtrucciones a lo lar)108 156 R .142
+(go de la trayectoria entre el transmisor y)-.18 F .575
+(el receptor tambi\351n se pro)108 168 R -.15(ve)-.15 G .575
+(en. Si la potencia efecti).15 F 1.075 -.25(va r)-.25 H .575
+(adiada del transmisor es especi\214cada en el archi).25 F -.2(vo)-.25 G
+F2(.lrp)108 180 Q F0 .49(del transmisor correspondiente, entonces la pr\
+edicci\363n de intensidad de se\361al y v)2.99 F .49
+(oltaje de antena en la)-.2 F
+(localizaci\363n de recepci\363n tambi\351n se pro)108 192 Q -.15(ve)
+-.15 G 2.5(ee).15 G 2.5(ne)-2.5 G 2.5(lr)-2.5 G
+(eporte de an\341lisis de trayectoria.)-2.5 E -.15(Pa)108 216 S 1.242(r\
+a determinar la relaci\363n se\361al-a-ruido \(SNR\) en el sitio remoto\
+ donde el ruido \(t\351rmico\) aleatorio de).15 F(Johnson es el el f)108
+228 Q(actor limitante primario en la recepci\363n:)-.1 E F2(SNR)108.33
+252 Q/F3 10/Symbol SF(=)3.07 E F2(T)2.71 E F3(-)3.47 E F2(NJ)2.9 E F3(-)
+3.17 E F2(L)2.78 E F3(+)2.73 E F2(G)2.18 E F3(-)2.7 E F2(NF)2.9 E F0
+(donde)108 276 Q F1(T)2.554 E F0 .054(es la potencia ERP del transmisor\
+ en dBW en la direcci\363n del recedptor)2.554 F(,)-.4 E F1(NJ)2.554 E
+F0 .054(es el ruido de Johnson)2.554 F 1.653
+(en dBW \(-136 dBW para un canal de)108 288 R 1.653(TV de 6 MHz\),)6.653
+F F1(L)4.153 E F0 1.653(es las p\351rdidas por trayectoria pro)4.153 F
+1.654(vistas por)-.15 F F1(SPLA)108 300 Q(T!)-.95 E F0 .076
+(en dB \(como un n\372mero)2.576 F F2(positivo)2.576 E F0(\),)A F1(G)
+2.576 E F0 .076(es la g)2.576 F .076
+(anancia de la antena receptora en dB referenciada a un)-.05 F
+(radiador isotr\363pico, y)108 312 Q F1(NF)2.5 E F0
+(es la \214gura de ruido en el receptor en dB.)2.5 E F1(T)108 336 Q F0
+(puede ser computado como sigue:)2.5 E F2(T)107.91 360 Q F3(=)4.07 E F2
+(TI)2.71 E F3(+)3.21 E F2(GT)2.18 E F0(donde)108 384 Q F1(TI)2.803 E F0
+.303(es la cantidad actual de potencia RF entre)2.803 F -.05(ga)-.15 G
+.303(da a la antena transmisora en dBW).05 F(,)-.92 E F1(GT)2.803 E F0
+.304(es la g)5.304 F(anan-)-.05 E .304(cia de la antena transmisora \(r\
+eferenciada a una isotr\363pica\) en la direcci\363n del receptor \(\
+\363 al horizonte si el)108 396 R
+(receptor est\341 sobre el horizonte\).)108 408 Q -.15(Pa)108 432 S
+1.441(ra calcular cuanta mas se\361al est\341 disponible sobre el m\355\
+nimo necesario para conse).15 F 1.442(guir una espec\355\214ca)-.15 F
+(relaci\363n se\361al-a-ruido:)108 444 Q F2(Signal)108.33 468 Q F0(_).51
+E F2(Margin).68 E F3(=)3.04 E F2(SNR)3.13 E F3(-)2.47 E F2(S)2.53 E F0
+(donde)108 492 Q F1(S)2.537 E F0 .037
+(es la m\355nima relaci\363n SNR deseada \(15.5 dB para A)2.537 F .037
+(TSC \(8-le)-1.11 F -.15(ve)-.25 G 2.536(lV).15 G .036(SB\) DTV)-2.536 F
+2.536(,4)-1.29 G 2.536(2d)-2.536 G 2.536(Bp)-2.536 G .036(ara tele)
+-2.536 F(visi\363n)-.25 E(anal\363gica NTSC\).)108 504 Q .295
+(Un mapa topogr\341\214co puede ser generado por)108 528 R F1(SPLA)2.795
+E(T!)-.95 E F0 .295
+(para visualizar la trayectoria entre el transmisor y el)2.795 F .57
+(receptor desde otra perspecti)108 540 R -.25(va)-.25 G 5.569(.L).25 G
+.569(os mapas topogr\341\214cos generados por)-5.569 F F1(SPLA)3.069 E
+(T!)-.95 E F0 .569(presentan las ele)3.069 F -.25(va)-.25 G(ciones).25 E
+.474(usando una escala de grises log)108 552 R .474
+(ar\355tmica, con las ele)-.05 F -.25(va)-.25 G .475
+(ciones m\341s altas representadas a tra).25 F .475
+(v\351s de capas m\341s)-.2 F .684(brillantes de gris. El rango din\341\
+mico de la imagen es escalada entre las ele)108 564 R -.25(va)-.25 G
+.684(ciones m\341s altas y m\341s bajas).25 F .57
+(presentes en el mapa. La \372nica e)108 576 R .57
+(xcepci\363n de esto es al ni)-.15 F -.15(ve)-.25 G 3.07(ld).15 G .57
+(el mar)-3.07 F 3.07(,e)-.4 G 3.07(lc)-3.07 G .57
+(ual se representa usando el color)-3.07 F(azul.)108 588 Q
+(La salida topogr\341\214ca se puede especi\214car)108 612 Q
+(usando la opci\363n)5 E F2(-o)2.5 E F0(:)A/F4 10/Courier@0 SF
+(splat -t tx_site -r rx_site -o topo_map.ppm)108 636 Q F0(La e)108 660 Q
+(xtensi\363n)-.15 E F2(.ppm)2.5 E F0(del archi)2.5 E .4 -.2(vo d)-.25 H
+2.5(es).2 G(alida es asumida por)-2.5 E F1(SPLA)2.5 E(T!)-.95 E F0 2.5
+(,ye)C 2.5(so)-2.5 G(pcional.)-2.5 E .583(En este ejemplo,)108 684 R F2
+(topo_map.ppm)3.083 E F0 .583(ilustrar\341 las localizaciones de los si\
+tios especi\214cados del transmisor y del)3.083 F(receptor)108 696 Q
+3.486(.A)-.55 G .986
+(dem\341s, la trayectoria entre los dos sitios ser\341 dib)-3.486 F .987
+(ujada sobre las localizaciones para las cuales)-.2 F -.15(ex)108 708 S
+.373(iste una trayectoria sin obst\341culo hacia el transmisor con).15 F
+.372(una altura de la antena de recepci\363n)5.372 F .372(igual a la)
+5.372 F(del sitio del receptor \(especi\214cado en)108 720 Q F2(rx_site)
+2.5 E(.qth)-.15 E F0(\).)A(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F
+(de Septiembre de 2007)2.5 E(8)176.785 E EP
+%%Page: 9 9
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .2(Puede ser deseab\
+le poblar el mapa topogr\341\214co con nombres y localizaciones de ciud\
+ades, sitios de torres, o)108 84 R .027
+(de otras localizaciones importantes.)108 96 R .027(Un archi)5.027 F
+.427 -.2(vo d)-.25 H 2.527(ec).2 G .027(iudades se puede pasar a)-2.527
+F/F1 10/Times-Bold@0 SF(SPLA)2.527 E(T!)-.95 E F0 2.527(usando la)2.527
+F(opci\363n)2.526 E/F2 10/Times-Italic@0 SF(-s)2.526 E F0(:)A/F3 10
+/Courier@0 SF(splat -t tx_site -r rx_site -s cities.dat -o topo_map)108
+120 Q F0(Hasta cinco archi)108 144 Q -.2(vo)-.25 G 2.5(ss).2 G
+(eparados pueden ser pasados a)-2.5 E F1(SPLA)2.5 E(T!)-.95 E F0 2.5(al)
+2.5 G 2.5(av)-2.5 G(ez lue)-2.65 E(go de la opci\363n)-.15 E F2(-s)2.5 E
+F0(.)A .076(L\355mites de estados y ciudades pueden ser adicionados al \
+mapa especi\214cando hasta cinco archi)108 168 R -.2(vo)-.25 G 2.576(sd)
+.2 G 2.576(el)-2.576 G(\355mites)-2.576 E
+(cartogr\341\214cos de Censo Bureu de los U.S.)108 180 Q
+(usando la opci\363n)5 E F2(-b)2.5 E F0(:)A F3
+(splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map)108 204 Q F0
+.274(En situaciones donde m\372ltiples sitios de transmisores est\341n \
+en uso, se pueden pasar a)108 228 R F1(SPLA)2.774 E(T!)-.95 E F0 .274
+(hasta cuatro)2.774 F(localizaciones simult\341neas para sus)108 240 Q
+(an\341lisis:)5 E F3
+(splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p profile.png)
+108 264 Q F0 1.266(En este ejemplo,)108 288 R F1(SPLA)3.767 E(T!)-.95 E
+F0 1.267(genera cuatro reportes separados de obstrucci\363n y de per\
+\214les de terreno . Un)3.767 F 1.224(simple mapa topogr\341\214co pued\
+e ser especi\214cado usando la opci\363n)108 300 R F2(-o)3.724 E F0
+3.724(,yl)C 1.223(as trayectorias de l\355nea de vista)-3.724 F 1.243(e\
+ntre cada transmisor y el sitio indicado del receptor ser\341 producido\
+ en el mapa, cada uno en su propio)108 312 R(color)108 324 Q 3.523(.L)
+-.55 G 3.523(at)-3.523 G 1.023(rayectoria entre el primer transmisor es\
+peci\214cado al receptor ser\341 v)-3.523 F 1.022
+(erde, la trayectoria entre el)-.15 F(se)108 336 Q .731
+(gundo transmisor y el receptor ser\341 c)-.15 F .731(yan, la trayector\
+ia entre el tercer transmisor y el receptor ser\341 vio-)-.15 F(leta, y\
+ la trayectoria entre el cuarto transmisor y el receptor ser\341 siena.)
+108 348 Q 2.514(Los mapas topogr\341\214cos generados por SPLA)108 372 R
+2.514(T! son im\341genes T)-1.11 F 2.514
+(rueColor PixMap Portables de 24-bit)-.35 F .892
+(\(PPM\) y pueden ser vistos, corre)108 384 R .892(gidos, o con)-.15 F
+-.15(ve)-.4 G .892(rtidos a otros formatos gr\341\214cos usando).15 F
+.893(populares progra-)5.893 F .884(mas de im\341genes tales como)108
+396 R F1(xv)3.384 E F0(,)A F1 .884(The GIMP)3.384 F F0(,)A F1
+(ImageMagick)3.384 E F0 3.384(,a)C(nd)-3.384 E F1(XP)3.384 E(aint)-.1 E
+F0 5.884(.E)C 3.384(lf)-5.884 G .884(ormato PNG es altamente)-3.384 F
+.323(recomendado para el almacenamiento comprimido sin p\351rdidas de l\
+os archi)108 408 R -.2(vo)-.25 G 2.823(st).2 G .323
+(opogr\341\214cos de salida)-2.823 F(gen-)5.324 E .973(erados por SPLA)
+108 420 R 3.473(T!. La)-1.11 F .972(utilidad de l\355nea de comandos)
+3.473 F F1(ImageMagick)3.472 E F0 2.072 -.55('s c)D(on).55 E .972
+(vierte f\341cilmente los archi)-.4 F -.2(vo)-.25 G(s).2 E
+(gr\341\214cos SPLA)108 432 Q(T! PPM al formato PNG:)-1.11 E F3
+(convert splat_map.ppm splat_map.png)108 456 Q F0 1.824
+(Otra utilidad de de l\355nea de comandos e)108 480 R 1.824
+(xcelente para con)-.15 F -.15(ve)-.4 G 1.824(rtir archi).15 F -.2(vo)
+-.25 G 4.324(sP).2 G 1.824(PM a PNG es wpng, y est\341)-4.324 F 2.329
+(disponible en:)108 492 R F2(http://www)7.329 E(.libpng)-.74 E(.or)-.15
+E(g/pub/png/book/sour)-.37 E(ces.html)-.37 E F0 7.329(.C)C 2.328
+(omo recurso adicional, los archi)-7.329 F -.2(vo)-.25 G(s).2 E .562(PP\
+M pueden ser comprimidos usando la utilidad bzip2, y ser le\355dos dire\
+ctamente en este formato por)108 504 R F1(The)3.062 E(GIMP)108 516 Q F0
+(.)A .434(La opci\363n)108 540 R F2(-ngs)2.934 E F0 .433(asigna a todo \
+el terreno el color blanco, y puede ser usada cuando se quiere generar \
+mapas)2.934 F(despro)108 552 Q(vistos de terreno)-.15 E F3
+(splat -t tx_site -r rx_site -b co34_d00.dat -ngs -o white_map)108 576 Q
+F0 .557(El archi)108 600 R .957 -.2(vo i)-.25 H .557
+(magen .ppm resultante puede ser con).2 F -.15(ve)-.4 G .558
+(rtido al formato .png con un fondo transparente usando).15 F
+(la utilidad)108 612 Q F1(con)2.5 E -.1(ve)-.4 G(rt).1 E F0(de)2.5 E F1
+(ImageMagick)2.5 E F0 -.55('s)C(.).55 E F3
+(convert -transparent "#FFFFFF" white_map.ppm transparent_map.png)108
+636 Q/F4 10.95/Times-Bold@0 SF(DETERMIN)72 652.8 Q(ANDO LA COBER)-.219 E
+(TURA REGION)-.438 E(AL)-.219 E F1(SPLA)108 664.8 Q(T!)-.95 E F0 2.064(\
+puede analizar un sitio de transmisor \363 repetidora, \363 redes de si\
+tios, y predecir la cobertura)4.565 F(re)108 676.8 Q 1.081
+(gional para cada sitio especi\214cado. En este modo)-.15 F F1(SPLA)
+3.581 E(T!)-.95 E F0 1.082
+(puede generar un mapa topogr\341\214co presen-)3.582 F 1
+(tando la l\355nea-de-vista geom\351trica del \341rea de cobertura)108
+688.8 R 1(de los sitios, basados en la localizaci\363n de cada)6 F .191
+(sitio y la altura de la antena receptora que se desea comunicar con el\
+ sitio en cuesti\363n.)108 700.8 R .191(Un an\341lisis re)5.191 F
+(gional)-.15 E(puede ser realizado por)108 712.8 Q F1(SPLA)5 E(T!)-.95 E
+F0(usando la opci\363n)2.5 E F2(-c)2.5 E F0(como sigue:)2.5 E
+(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(9)176.785 E EP
+%%Page: 10 10
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+(splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o tx_coverage)
+108 84 Q F0 .033(En este ejemplo, SPLA)108 108 R .033
+(T! genera un mapa topogr\341\214co llamado)-1.11 F/F2 10/Times-Italic@0
+SF(tx_co)2.533 E(ver)-.1 E -.1(age)-.15 G(.ppm)-.05 E F0 .033
+(que ilustra la predicci\363n de)2.533 F .419(cobertura re)108 120 R
+.419(gional de l\355nea-de-vista del)-.15 F F2(tx_site)2.919 E F0 2.919
+(al)2.919 G .42
+(as estaciones receptoras que tienen una antena de 30 pies)-2.919 F .098
+(de altura sobre el ni)108 132 R -.15(ve)-.25 G 2.598(ld).15 G .098
+(el terreno \(A)-2.598 F .098(GL\). Si la opci\363n)-.4 F F2(-metric)
+2.598 E F0 .098(es usada, el ar)2.598 F .098
+(gumento que sigue a la opci\363n)-.18 F F2(-c)108 144 Q F0 .252
+(es interpretada en metros, en lug)2.752 F .253
+(ar de pies. El contenido de cities.dat son dib)-.05 F .253
+(ujados sobre el mapa, como)-.2 F
+(tambi\351n los l\355mites cartogr\341\214cos contenidos en el archi)108
+156 Q -.2(vo)-.25 G F2(co34_d00.dat)2.7 E F0(.)A .659(Cuando se gra\214\
+ca las trayectorias de l\355nea-de-vista y las \341reas de cobertura re)
+108 180 R(gional,)-.15 E/F3 10/Times-Bold@0 SF(SPLA)3.158 E(T!)-.95 E F0
+.658(por defecto)3.158 F 1.344(no considera los efectos de la \215e)108
+192 R 1.344(xi\363n atmosf\351rica. Sin embar)-.15 F 1.345
+(go esta caracter\355stica puede ser modi\214cada)-.18 F
+(usando el multiplicador de radio de la tierra con la opci\363n \()108
+204 Q F2(-m)A F0(\):)A F1 3.273
+(splat -t wnjt-dt -c 30.0 -m 1.333 -s cities.dat -b counties.dat -o)108
+228 R(map.ppm)108 240 Q F0 .138
+(Un radio multiplicador de 1.333 instruye a)108 264 R F3(SPLA)5.139 E
+(T!)-.95 E F0 2.639(au)2.639 G .139
+(sar el modelo de "cuatro-tercios" para el an\341lisis de)-2.639 F
+(propag)108 276 Q 1.347(aci\363n de l\355nea de vista.)-.05 F 1.347(Cua\
+lquier multiplicador del radio de la tierra apropiado puede ser selec-)
+6.347 F(cionado por el usuario.)108 288 Q .867
+(Cuandorealiza un an\341lisis re)108 312 R(gional,)-.15 E F3(SPLA)3.367
+E(T!)-.95 E F0 .867
+(genera un reporte para cada estaci\363n analizada. Los reportes)3.367 F
+.027(de sitio)108 324 R F3(SPLA)2.527 E(T!)-.95 E F0 .027(contienen det\
+alles de la localizaci\363n geogr\341\214ca del sitio, su altura sobre \
+el ni)2.527 F -.15(ve)-.25 G 2.526(ld).15 G .026(el mar)-2.526 F 2.526
+(,l)-.4 G(a)-2.526 E .053(altura de la antena sobre el promedio del ter\
+reno, y la altura del promedio del terreno calculada en las direc-)108
+336 R
+(ciones de los azimut de 0, 45, 90, 135, 180, 225, 270, y 315 grados.)
+108 348 Q/F4 10.95/Times-Bold@0 SF(DETERMIN)72 364.8 Q(ANDO M\332L)-.219
+E(TIPLES REGIONES DE COBER)-1.007 E(TURA DE LD)-.438 E(V)-.438 E F3
+(SPLA)108 376.8 Q(T!)-.95 E F0 1.389(tambi\351n puede presentar \341rea\
+s de cobertura de l\355nea-de-vista hasta para)3.89 F 1.389
+(cuatro sitios de trans-)6.389 F
+(misores separados sobre un mapa topogr\341\214co com\372n.)108 388.8 Q
+(Por ejemplo:)5 E F1
+(splat -t site1 site2 site3 site4 -c 10.0 -metric -o network.ppm)108
+412.8 Q F0 .48(Gra\214ca las coberturas re)108 436.8 R .48
+(gionales de l\355nea de vista del)-.15 F .48
+(site1 site2 site3 y site4 basado en una antena recep-)5.48 F .386
+(tora localizada a 10.0 metros sobre el ni)108 448.8 R -.15(ve)-.25 G
+2.886(ld).15 G .386
+(el terreno. Un mapa topogr\341\214co entonces es escrito al archi)
+-2.886 F -.2(vo)-.25 G F2(network.ppm)108 460.8 Q F0 5.547(.E)C 3.047
+<6ce1>-5.547 G .547(rea de cobertura de l\355nea-de-vista del transmiso\
+r es gra\214cada como sigue en los colores)-3.047 F
+(indicados \(junto con sus v)108 472.8 Q
+(alores RGB correspondientes en decimal\):)-.25 E F1
+(site1: Green \(0,255,0\))132 496.8 Q(site2: Cyan \(0,255,255\))132
+508.8 Q(site3: Medium Violet \(147,112,219\))132 520.8 Q
+(site4: Sienna 1 \(255,130,71\))132 532.8 Q
+(site1 + site2: Yellow \(255,255,0\))132 556.8 Q
+(site1 + site3: Pink \(255,192,203\))132 568.8 Q
+(site1 + site4: Green Yellow \(173,255,47\))132 580.8 Q
+(site2 + site3: Orange \(255,165,0\))132 592.8 Q
+(site2 + site4: Dark Sea Green 1 \(193,255,193\))132 604.8 Q
+(site3 + site4: Dark Turquoise \(0,206,209\))132 616.8 Q
+(site1 + site2 + site3: Dark Green \(0,100,0\))132 640.8 Q
+(site1 + site2 + site4: Blanched Almond \(255,235,205\))132 652.8 Q
+(site1 + site3 + site4: Medium Spring Green \(0,250,154\))132 664.8 Q
+(site2 + site3 + site4: Tan \(210,180,140\))132 676.8 Q
+(site1 + site2 + site3 + site4: Gold2 \(238,201,0\))132 700.8 Q F0
+(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(10)171.785 E EP
+%%Page: 11 11
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .142
+(Si se generan archi)108 84 R -.2(vo)-.25 G(s).2 E/F1 10/Times-Italic@0
+SF(.qth)2.642 E F0 .142(separados, cada uno representando una localizac\
+i\363n de un sitio com\372n, pero con)2.642 F .832
+(diferentes alturas de antena,)108 96 R/F2 10/Times-Bold@0 SF(SPLA)3.333
+E(T!)-.95 E F0 .833(puede generar un mapa topogr\341\214co sencillo que\
+ ilustra la cobertura)3.333 F(re)108 108 Q(gional desde las estaciones \
+\(hasta cuatro\) separadas por la altura en un \372nica torre.)-.15 E/F3
+10.95/Times-Bold@0 SF(AN)72 124.8 Q(ALISIS DE P\311RDID)-.219 E
+(AS POR TRA)-.383 E(YECT)-1.095 E(ORIA LONGLEY)-.197 E(-RICE)-1.007 E F0
+.273(Si la opci\363n)108 136.8 R F1(-c)2.772 E F0 .272
+(se reemplaza por la opci\363n)5.272 F F1(-L)2.772 E F0 2.772(,s)C 2.772
+(ep)-2.772 G .272
+(uede generar un mapa de p\351rdidas de trayectorias Long-)-2.772 F(le)
+108 148.8 Q(y-Rice:)-.15 E/F4 10/Courier@0 SF
+(splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o path_loss_map)
+108 172.8 Q F0 .404(En este modo,)108 196.8 R F2(SPLA)2.904 E(T!)-.95 E
+F0 .404(genera un mapa multicolor que ilustra los ni)2.904 F -.15(ve)
+-.25 G .405(les de se\361al esperados \(p\351rdidas por).15 F .473
+(trayectoria\) en las \341reas alrededor del transmisor)108 208.8 R
+2.973(.U)-.55 G .473(na le)-2.973 F .473
+(yenda en la parte inferior del mapa relaciona cada)-.15 F .007
+(color con sus respecti)108 220.8 R -.25(va)-.25 G 2.507(sp).25 G .007(\
+\351rdidas por trayectoria espec\355\214cas en decibeles \363 intensida\
+d de se\361al en decibeles)-2.507 F(sobre un micro)108 232.8 Q -.2(vo)
+-.15 G(ltio por metro \(dBuV/m\).).2 E .647
+(El rango de an\341lisis Longle)108 256.8 R .647
+(y-Rice puede modi\214cado a un v)-.15 F .646
+(alor espec\355\214co-de-usuario con la opci\363n)-.25 F F1(-R)3.146 E
+F0 3.146(.E)C(l)-3.146 E(ar)108 268.8 Q .758
+(gumento debe ser dado en millas \(\363 kil\363metros si la opci\363n)
+-.18 F F1(-metric)3.258 E F0 .758
+(es usada\). Si se especi\214ca un rango)3.258 F 1.913
+(mayor que el mapa topogr\341\214co generado,)108 280.8 R F2(SPLA)4.412
+E(T!)-.95 E F0 1.912(realizar\341 los c\341lculos de perdidas Longle)
+4.412 F 1.912(y-Rice de)-.15 F
+(trayectoria entre todas las cuatro esquinas del \341rea del mapa)108
+292.8 Q(de predicci\363n.)5 E .702(La opci\363n)108 316.8 R F1(-db)3.202
+E F0 .702(permite limitar el m\341ximo de perdidas de la re)3.202 F .703
+(gi\363n a ser gra\214cada en el mapa. P\351rdidas de)-.15 F .416(traye\
+ctoria entre 80 y 230 dB pueden ser especi\214cadas usando esta opci\
+\363n. Por ejemplo si las perdidas por)108 328.8 R .186
+(debajo de -140 dB son irrele)108 340.8 R -.25(va)-.25 G .186(ntes al a\
+n\341lisis que se est\341 realizando, entonces las p\351rdidas por tray\
+ectoria a).25 F .808(ser gra\214cadas por)108 352.8 R F2(SPLA)3.308 E
+(T!)-.95 E F0 .808(pueden ser limitadas a la re)5.808 F .807
+(gi\363n de atenuaci\363n del contorno de 140 dB como)-.15 F(sigue:)108
+364.8 Q F4 3.818
+(splat -t wnjt-dt -L 30.0 -s cities.dat -b co34_d00.dat -db 140 -o)108
+388.8 R(plot.ppm)108 400.8 Q F3 -.81(PA)72 417.6 S(R\301METR).81 E(OS P)
+-.329 E(ARA LA DEFINICI\323N DE COLOR DEL CONT)-.81 E
+(ORNO DE LA SE\321AL)-.197 E F0 1.185(Los colores usados para ilustrar \
+los contornos de intensidad de se\361al y de p\351rdidas por trayectori\
+a en la)108 429.6 R(generaci\363n de mapas de mapa de cobertura en)108
+441.6 Q F2(SPLA)2.501 E(T!)-.95 E F0 .001
+(pueden ser adaptados por el usuario creando o mod-)2.501 F .182
+(i\214cando los archi)108 453.6 R .582 -.2(vo d)-.25 H 2.682(ed).2 G
+.181(e\214nici\363n de color)-2.682 F F2(SPLA)2.681 E(T!)-.95 E F0 2.681
+(.L)C .181(os ardchi)-2.681 F -.2(vo)-.25 G 2.681(sd).2 G 2.681(ed)
+-2.681 G .181(e\214nici\363n de color)-2.681 F F2(SPLA)2.681 E(T!)-.95 E
+F0 .181(tienen el)2.681 F(mismo nombre base que el del archi)108 465.6 Q
+-.2(vo)-.25 G F1(.qth)2.7 E F0(del transmisor)2.5 E 2.5(,p)-.4 G
+(ero lle)-2.5 E -.25(va)-.25 G 2.5(nl).25 G(as e)-2.5 E(xtensiones)-.15
+E F1(.lcf)2.5 E F0(y)2.5 E F1(.scf)2.5 E F0(.)A .465
+(Cuando un an\341lisis re)108 489.6 R 2.966(gional Longle)-.15 F .466(y\
+-Rice es realizado y el ERP del transmisor no se ha especi\214cado \363\
+ es)-.15 F 1.132(cero, un archi)108 501.6 R 1.532 -.2(vo d)-.25 H 3.632
+(ed).2 G 1.131(e\214nici\363n de color de p\351rdidas por trayectoria)
+-3.632 F F1(.lcf)3.631 E F0 1.131(correspondiente al sitio del trans-)
+3.631 F(misor \()108 513.6 Q F1(.qth)A F0 2.5(\)e)C 2.5(sl)-2.5 G
+(e\355do por)-2.5 E F2(SPLA)2.5 E(T!)-.95 E F0
+(desde el directorio de trabajo actual. Si el archi)2.5 E -.2(vo)-.25 G
+F1(.lcf)110.5 525.6 Q F0 .873(correspondiente al sitio del transmisor n\
+o se encuentra, entonces un archi)3.373 F 1.274 -.2(vo p)-.25 H .874
+(or defecto para edici\363n).2 F .182
+(manual por el usuario es autom\341ticamente generado por)108 537.6 R F2
+(SPLA)2.682 E(T!)-.95 E F0 2.682(.S)C 2.682(ie)-2.682 G 2.682(lE)-2.682
+G .182(RP del transmisor es especi\214cado,)-2.682 F .604
+(entonces un mapa de intensidad de se\361al es generado y un archi)108
+549.6 R 1.004 -.2(vo d)-.25 H 3.104(ed).2 G .604
+(e\214nici\363n de color de intensidad de)-3.104 F(se\361al es le\355do\
+, o generado si no est\341 disponible en el directorio de trabajo actua\
+l.)108 561.6 Q(Un archi)108 585.6 Q .4 -.2(vo d)-.25 H 2.5(ed).2 G(e\
+\214nici\363n de color de p\351rdidas por trayectoria posee la siguient\
+e estructura: \()-2.5 E F1(wnjt-dt.lcf)A F0(\):)A F4 6(;S)114 621.6 S
+(PLAT! Auto-generated Path-Loss Color Definition \("wnjt-dt.lcf"\) File)
+-6 E(;)114 633.6 Q 6(;F)114 645.6 S
+(ormat for the parameters held in this file is as follows:)-6 E(;)114
+657.6 Q 24(;d)114 669.6 S(B: red, green, blue)-24 E(;)114 681.6 Q 6(;.)
+114 693.6 S(..where "dB" is the path loss \(in dB\) and)-6 E 6(;")114
+705.6 S(red", "green", and "blue" are the corresponding RGB color)-6 E 6
+(;d)114 717.6 S
+(efinitions ranging from 0 to 255 for the region specified.)-6 E(;)114
+729.6 Q F0(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F
+(de Septiembre de 2007)2.5 E(11)171.785 E EP
+%%Page: 12 12
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF 6
+(;T)114 84 S(he following parameters may be edited and/or expanded)-6 E
+6(;f)114 96 S(or future runs of SPLAT!)-6 E 6(At)12 G
+(otal of 32 contour regions)-6 E 6(;m)114 108 S
+(ay be defined in this file.)-6 E(;)114 120 Q(;)114 132 Q(80: 255,)120
+144 Q 12(0, 0)18 F(90: 255, 128,)120 156 Q(0)18 E(100: 255, 165,)114 168
+Q(0)18 E(110: 255, 206,)114 180 Q(0)18 E(120: 255, 255,)114 192 Q(0)18 E
+(130: 184, 255,)114 204 Q(0)18 E 12(140: 0,)114 216 R 12(255, 0)6 F 12
+(150: 0,)114 228 R 12(208, 0)6 F 12(160: 0,)114 240 R(196, 196)6 E 12
+(170: 0,)114 252 R(148, 255)6 E 6(180: 80, 80,)114 264 R(255)6 E 12
+(190: 0,)114 276 R(38, 255)12 E(200: 142,)114 288 Q(63, 255)12 E
+(210: 196,)114 300 Q(54, 255)12 E(220: 255,)114 312 Q(0, 255)18 E
+(230: 255, 194, 204)114 324 Q F0 .425(Si la p\351rdida por trayectoria \
+es menor que 80 dB, el color Rojo \(RGB = 255, 0, 0\) es asignado a la \
+re)108 360 R(gi\363n.)-.15 E .969(Si la p\351rdida-por)108 372 R .968(-\
+trayectoria es mayor o igual a 80 dB, pero menor que 90 dB, entonces Na\
+ranja Oscuro)-.2 F .564(\(255, 128, 0\) es asignado a la re)108 384 R
+.565(gi\363n. Naranja \(255, 165, 0\) es asignado a re)-.15 F .565
+(giones que tienen una p\351rdida)-.15 F .735(por trayectoria mayor o i\
+gual a 90 dB, pero menor que 100 dB, y as\355 en adelante. El terreno e\
+n escala de)108 396 R(grises es presentado por debajo del contorno de p\
+\351rdidas por trayectoria de 230 dB.)108 408 Q 1.526(El archi)108 432 R
+-.2(vo)-.25 G/F2 10/Times-Bold@0 SF(SPLA)4.226 E(T!)-.95 E F0 1.527(de \
+de\214nici\363n de color de intensidad de se\361al comparte una estruct\
+ura muy similar)4.026 F(.)-.55 E(structure \()108 444 Q/F3 10
+/Times-Italic@0 SF(wnjt-dt.scf)A F0(\):)A F1 6(;S)114 480 S
+(PLAT! Auto-generated Signal Color Definition \("wnjt-dt.scf"\) File)-6
+E(;)114 492 Q 6(;F)114 504 S
+(ormat for the parameters held in this file is as follows:)-6 E(;)114
+516 Q 24(;d)114 528 S(BuV/m: red, green, blue)-24 E(;)114 540 Q 6(;.)114
+552 S(..where "dBuV/m" is the signal strength \(in dBuV/m\) and)-6 E 6
+(;")114 564 S(red", "green", and "blue" are the corresponding RGB color)
+-6 E 6(;d)114 576 S
+(efinitions ranging from 0 to 255 for the region specified.)-6 E(;)114
+588 Q 6(;T)114 600 S
+(he following parameters may be edited and/or expanded)-6 E 6(;f)114 612
+S(or future runs of SPLAT!)-6 E 6(At)12 G(otal of 32 contour regions)-6
+E 6(;m)114 624 S(ay be defined in this file.)-6 E(;)114 636 Q(;)114 648
+Q(128: 255,)114 660 Q 12(0, 0)18 F(118: 255, 165,)114 672 Q(0)18 E
+(108: 255, 206,)114 684 Q(0)18 E(98: 255, 255,)120 696 Q(0)18 E
+(88: 184, 255,)120 708 Q(0)18 E 12(78: 0,)120 720 R 12(255, 0)6 F F0
+(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(12)171.785 E EP
+%%Page: 13 13
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10/Courier@0 SF
+12(68: 0,)120 84 R 12(208, 0)6 F 12(58: 0,)120 96 R(196, 196)6 E 12
+(48: 0,)120 108 R(148, 255)6 E 6(38: 80, 80,)120 120 R(255)6 E 12
+(28: 0,)120 132 R(38, 255)12 E(18: 142,)120 144 Q(63, 255)12 E(8: 140,)
+126 156 Q(0, 128)18 E F0 .328
+(Si la intensidad de se\361al es mayor o igual a 128 db sobre 1 micro)
+108 192 R -.2(vo)-.15 G .327(ltio por metro \(dBuV/m\), el color Rojo).2
+F 1.051(\(255, 0, 0\) es presentado para la re)108 204 R 3.551
+(gi\363n. Si)-.15 F 1.052
+(la intensidad de se\361al es mayor o igual a 118 db)3.551 F 1.052
+(uV/m, pero)-.2 F .298(menor que 128 db)108 216 R .297
+(uV/m, entonces el color naranja \(255, 165, 0\) es presentado y asi)-.2
+F .297(en adelante. El terreno)5.297 F
+(en escala de grises es presentado para re)108 228 Q
+(giones con intensidad de se\361al menores que 8 dBuV/m.)-.15 E .684(Lo\
+s contornos de intensidad de se\361al para algunos servicios de radiodi\
+fusi\363n comunes en VHF y UHF en)108 252 R
+(los Estados Unidos son los siguientes:)108 264 Q F1
+(Analog Television Broadcasting)150 300 Q
+(------------------------------)150 312 Q(Channels 2-6:)150 324 Q
+(City Grade: >= 74 dBuV/m)42 E(Grade A: >= 68 dBuV/m)288 336 Q
+(Grade B: >= 47 dBuV/m)288 348 Q
+(--------------------------------------------)150 360 Q(Channels 7-13:)
+150 372 Q(City Grade: >= 77 dBuV/m)36 E(Grade A: >= 71 dBuV/m)288 384 Q
+(Grade B: >= 56 dBuV/m)288 396 Q
+(--------------------------------------------)150 408 Q(Channels 14-69:)
+150 420 Q(Indoor Grade: >= 94 dBuV/m)18 E(City Grade: >= 80 dBuV/m)270
+432 Q(Grade A: >= 74 dBuV/m)288 444 Q(Grade B: >= 64 dBuV/m)288 456 Q
+(Digital Television Broadcasting)150 480 Q
+(-------------------------------)150 492 Q(Channels 2-6:)150 504 Q
+(City Grade: >= 35 dBuV/m)42 E(Service Threshold: >= 28 dBuV/m)228 516 Q
+(--------------------------------------------)150 528 Q(Channels 7-13:)
+150 540 Q(City Grade: >= 43 dBuV/m)36 E(Service Threshold: >= 36 dBuV/m)
+228 552 Q(--------------------------------------------)150 564 Q
+(Channels 14-69:)150 576 Q(City Grade: >= 48 dBuV/m)30 E
+(Service Threshold: >= 41 dBuV/m)228 588 Q
+(NOAA Weather Radio \(162.400 - 162.550 MHz\))150 612 Q
+(------------------------------------------)150 624 Q
+(Reliable: >= 18 dBuV/m)216 636 Q(Not reliable: <)192 648 Q(18 dBuV/m)12
+E(Unlikely to receive: <)150 660 Q 6(0d)12 G(BuV/m)-6 E
+(FM Radio Broadcasting \(88.1 - 107.9 MHz\))150 684 Q
+(----------------------------------------)150 696 Q
+(Analog Service Contour:)150 708 Q(60 dBuV/m)12 E
+(Digital Service Contour: 65 dBuV/m)150 720 Q F0(KD2BD Softw)72 768 Q
+107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E(13)171.785 E EP
+%%Page: 14 14
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E/F1 10.95
+/Times-Bold@0 SF -.81(PA)72 84 S(R\301METR).81 E(OS P)-.329 E(ARA P)-.81
+E -1.04(AT)-.81 G -.329(RO)1.04 G(NES DE RADIA).329 E(CI\323N DE ANTEN)
+-.602 E(AS)-.219 E F0 .016(Los patrones de v)108 96 R .016
+(oltaje de campo normalizado para planos v)-.2 F .015
+(erticales y horizontales de antenas transmisoras)-.15 F .65
+(son importados autom\341ticamente dentro de)108 108 R/F2 10
+/Times-Bold@0 SF(SPLA)3.15 E(T!)-.95 E F0 .65
+(cuando se realizan los an\341lisis de cobertura Longle)3.15 F(y-)-.15 E
+3.437(Rice. Los)108 120 R .936
+(datos de los patrones de antena son le\355dos de un par de archi)3.437
+F -.2(vo)-.25 G 3.436(sq).2 G .936(ue tienen el mismo nombre)-3.436 F
+.189(base que el transmisor y los archi)108 132 R -.2(vo)-.25 G 2.689
+(sL).2 G(RP)-2.689 E 2.689(,p)-1.11 G .189(ero con e)-2.689 F
+(xtensiones)-.15 E/F3 10/Times-Italic@0 SF(.az)2.689 E F0(y)2.689 E F3
+(.el)2.689 E F0 2.689(,p)C .189(ara los patrones de azimut y ele-)-2.689
+F -.25(va)108 144 S .276(ci\363n respecti).25 F -.25(va)-.25 G .275(men\
+te. Especi\214caciones acerca de la rotaci\363n del patr\363n \(si e).25
+F .275(xiste\) e inclinaci\363n mec\341nica)-.15 F 4.368(yd)108 156 S
+1.868(irecci\363n de la inclinaci\363n \(si e)-4.368 F 1.868
+(xiste\) tambi\351n son contenidos dentro de los archi)-.15 F -.2(vo)
+-.25 G 4.368(sd).2 G 4.369(ep)-4.368 G 1.869(atrones de)-4.369 F
+(radiaci\363n de las antenas.)108 168 Q .583
+(Por ejemplo las primeras pocas l\355neas de un archi)108 192 R .982 -.2
+(vo d)-.25 H 3.082(ep).2 G .582(atr\363n de azimut)-3.082 F F2(SPLA)
+3.082 E(T!)-.95 E F0 .582(podr\355an aparecer como)5.582 F(sigue \()108
+204 Q F3(kvea.az)A F0(\):)A/F4 10/Courier@0 SF(183.0)156 228 Q 42(00)156
+240 S(.8950590)-42 E 42(10)156 252 S(.8966406)-42 E 42(20)156 264 S
+(.8981447)-42 E 42(30)156 276 S(.8995795)-42 E 42(40)156 288 S(.9009535)
+-42 E 42(50)156 300 S(.9022749)-42 E 42(60)156 312 S(.9035517)-42 E 42
+(70)156 324 S(.9047923)-42 E 42(80)156 336 S(.9060051)-42 E F0 .095
+(La primera l\355nea de el archi)108 372 R -.2(vo)-.25 G F3(.az)2.795 E
+F0 .096(especi\214ca la cantidad de rotaci\363n del patr\363n de azimut\
+ \(medido en grados)2.595 F .079(desde el norte v)108 384 R .079
+(erdadero en sentido horario\) a ser aplicado por)-.15 F F2(SPLA)2.579 E
+(T!)-.95 E F0 2.579(al)2.579 G .079(os datos contenidos en el archi)
+-2.579 F -.2(vo)-.25 G F3(.az)108 396 Q F0 2.747(.E)C .247(sto es se)
+-2.747 F .247(guido por el correspondiente azimut \(0 a 360 grados\) y \
+su asociado patr\363n de campo normal-)-.15 F
+(izado \(0.000 a 1.000\) separado por un espacio en blanco.)108 408 Q
+1.082(La estructura del archi)108 432 R 1.482 -.2(vo d)-.25 H 1.082
+(el patr\363n de ele).2 F -.25(va)-.25 G(ci\363n).25 E F2(SPLA)3.582 E
+(T!)-.95 E F0 1.082(es ligeramente diferente. La primera l\355nea del)
+3.582 F(archi)108 444 Q -.2(vo)-.25 G F3(.el)3.006 E F0 .306
+(especi\214ca la cantidad de ele)2.806 F -.25(va)-.25 G .306
+(ci\363n mec\341nica aplicada a la antena. Note que una).25 F F3(ele)
+2.807 E .307(vaci\363n hacia)-.15 F(abajo)108 456 Q F0 .607
+(\(bajo el horizonte\) es e)3.107 F .607(xpresada como un)-.15 F F3 .607
+(\341ngulo positivo)3.107 F F0 3.107(,m)C .607(ientras que)-3.107 F F3
+.607(hacia arriba)3.107 F F0 .606(\(sobre el hori-)3.107 F .848
+(zonte\) es e)108 468 R .848(xpresada como un)-.15 F F3 .849
+(\341ngulo ne)3.349 F(gativo)-.4 E F0 3.349(.E)C .849(stos datos son se)
+-3.349 F .849(guidos por la direcci\363n del azimut de la)-.15 F(ele)108
+480 Q -.25(va)-.25 G(ci\363n, separado por un espacio en blanco.).25 E
+.177(El remanente del archi)108 504 R .577 -.2(vo c)-.25 H .177
+(onsiste en los v).2 F .177(alores de los \341ngulos de ele)-.25 F -.25
+(va)-.25 G .177(ci\363n y su correspondiente patr\363n de).25 F .646
+(radiaci\363n de v)108 516 R .647(oltaje normalizado \(0.000 a 1.000\) \
+separados por un espacio en blanco. Los \341ngulos de ele-)-.2 F -.25
+(va)108 528 S .787(ci\363n deben ser especi\214cados sobre un rango de \
+-10 a +90 grados. Igual que la notaci\363n en la ele).25 F -.25(va)-.25
+G(ci\363n).25 E(mec\341nica,)108 540 Q F3(\341ngulos de ele)2.5 E
+(vaci\363n ne)-.15 E(gativa)-.4 E F0(son usados para representar ele)2.5
+E -.25(va)-.25 G(ciones).25 E F3(sobr)2.5 E 2.5(ee)-.37 G 2.5(lh)-2.5 G
+(orizonte)-2.5 E F0(,)A(mientras que los)110.5 552 Q F3
+(\341ngulos positivos)2.5 E F0(representan ele)2.5 E -.25(va)-.25 G
+(ciones).25 E F3(bajo el horizonte)2.5 E F0(.)A 1.044
+(Por ejemplo las primeras pocas l\355neas de un archi)108 576 R 1.444
+-.2(vo p)-.25 H 1.044(atr\363n de ele).2 F -.25(va)-.25 G(ci\363n).25 E
+F2(SPLA)3.544 E(T!)-.95 E F0 1.044(podr\355a aparecer como)6.044 F
+(sigue \()108 588 Q F3(kvea.el)A F0(\):)A F4 18(1.1 130.0)156 612 R 12
+(-10.0 0.172)150 624 R 18(-9.5 0.109)150 636 R 18(-9.0 0.115)150 648 R
+18(-8.5 0.155)150 660 R 18(-8.0 0.157)150 672 R 18(-7.5 0.104)150 684 R
+18(-7.0 0.029)150 696 R 18(-6.5 0.109)150 708 R 18(-6.0 0.185)150 720 R
+F0(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(14)171.785 E EP
+%%Page: 15 15
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .402(En este ejempl\
+o, la antena es mecanicamente inclinada hacia abajo 1.1 grados hacia un\
+ azimut de 130 gra-)108 84 R(dos)108 96 Q -.15(Pa)108 120 S .019(ra mej\
+ores resultados, la resoluci\363n de los datos de patrones de radiaci\
+\363n deber\355a ser especi\214cados lo mas).15 F .308(cerca posibles a\
+ los grados azimut, y la resoluci\363n de datos del patr\363n de ele)108
+132 R -.25(va)-.25 G .307(ci\363n de).25 F -.15(ve)-.25 G .307
+(r\355an ser especi\214ca-).15 F .672(dos lo mas cerca posible a 0.01 g\
+rados. Si los datos del patr\363n especi\214cado no alcanzan este ni)108
+144 R -.15(ve)-.25 G 3.172(ld).15 G 3.172(er)-3.172 G(es-)-3.172 E
+(oluci\363n,)108 156 Q/F1 10/Times-Bold@0 SF(SPLA)4.067 E(T!)-.95 E F0
+1.566(interpolar\341 los v)4.067 F 1.566(alores pro)-.25 F 1.566
+(vistos para determinar los datos en la resoluci\363n requerida,)-.15 F
+(aunque esto puede resultar en una p\351rdida en e)108 168 Q(xactitud.)
+-.15 E/F2 10.95/Times-Bold@0 SF(IMPOR)72 184.8 Q -.986(TA)-.438 G .773
+(NDO Y EXPOR).986 F -.986(TA)-.438 G .773(NDO D).986 F -.855 -1.04(AT O)
+-.383 H 3.512(SD)1.04 G .774(EL CONT)-3.512 F .774(ORNO REGION)-.197 F
+.774(AL DE P\311RDID)-.219 F .774(AS POR)-.383 F(TRA)108 196.8 Q(YECT)
+-1.095 E(ORIA)-.197 E F0 .141
+(Realizar un an\341lisis de cobertura Longle)108 208.8 R .141
+(y-Rice puede ser un proceso que consume mucho tiempo, especial-)-.15 F
+1.28(mente si el an\341lisis es repetido v)108 220.8 R 1.28(arias v)-.25
+F 1.28(eces para descubrir cuales son los efectos que los cambios a los)
+-.15 F(patrones de radiaci\363n de las antenas hacen a la predicci\363n\
+ del \341rea de cobertura)108 232.8 Q .429
+(Este proceso puede ser apresurado al e)108 256.8 R .429
+(xportar los datos del contorno re)-.15 F .428
+(gional de p\351rdidas por trayectoria a)-.15 F .032(un archi)108 268.8
+R .432 -.2(vo d)-.25 H 2.532(es).2 G .032(alida, modi\214car e)-2.532 F
+.033(xternamente los datos de p\351rdida por trayectoria para incorpora\
+r los efectos)-.15 F .58
+(de los patrones de antena, y entonces importar nue)108 280.8 R -.25(va)
+-.25 G .58(mente los datos de p\351rdidas por trayectoria modi\214ca-)
+.25 F(dos dentro de)108 292.8 Q F1(SPLA)2.5 E(T!)-.95 E F0
+(para rapidamente producir un mapa re)2.5 E
+(visado de p\351rdidas por trayectoria.)-.25 E .417
+(Por ejemplo un archi)108 316.8 R .817 -.2(vo d)-.25 H 2.917(es).2 G
+.418(alida de p\351rdidas por trayectoria puede ser generado por)-2.917
+F F1(SPLA)2.918 E(T!)-.95 E F0 .418(para un sitio)2.918 F 1.166
+(de recepci\363n a 30 pies sobre el ni)108 328.8 R -.15(ve)-.25 G 3.666
+(ld).15 G 1.166
+(el terreno, con un radio de 50 millas alrededor del sitio de trans-)
+-3.666 F(misi\363n para p\351rdidas por trayectoria m\341ximas de 140 d\
+B, usando la siguiente sintaxis:)108 340.8 Q/F3 10/Courier@0 SF
+(splat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat)108 364.8 Q F0
+1.829(Los archi)108 388.8 R -.2(vo)-.25 G 4.329(sd).2 G 4.329(es)-4.329
+G 1.829(alida por p\351rdidas por trayectoria)-4.329 F F1(SPLA)4.329 E
+(T!)-.95 E F0 4.329(am)4.329 G 1.83(enudo e)-4.329 F 1.83
+(xceden los 100 me)-.15 F -.05(ga)-.15 G 1.83(bytes de).05 F .64(tama\
+\361o. Contienen la informaci\363n referentes a los l\355mites de la re)
+108 400.8 R .639(gi\363n que describen se)-.15 F .639
+(guido por latitudes)-.15 F .392
+(\(grados norte\), longitudes \(grados oeste\), azimut, ele)108 412.8 R
+-.25(va)-.25 G .393
+(ciones\(a la primera obstrucci\363n\), y \214guras de p\351rdi-).25 F
+.126(das por trayectoria\(dB\) para una serie de puntos espec\355\214co\
+s que abarca la re)108 424.8 R .126
+(gi\363n que rodea al sitio de trans-)-.15 F .106
+(misi\363n. Las primeras pocas l\355neas de un archi)108 436.8 R .506
+-.2(vo d)-.25 H 2.606(es).2 G .107(alida de p\351rdidas por trayectoria)
+-2.606 F F1(SPLA)2.607 E(T!)-.95 E F0 .107(tiene la sigu-)2.607 F
+(iente apariencia \()108 448.8 Q/F4 10/Times-Italic@0 SF(pathloss.dat)A
+F0(\):)A F3(119, 117)156 484.8 Q 6(;m)24 G(ax_west, min_west)-6 E
+(35, 33)156 496.8 Q 6(;m)36 G(ax_north, min_north)-6 E
+(34.2265434, 118.0631104, 48.171, -37.461, 67.70)156 508.8 Q
+(34.2270355, 118.0624390, 48.262, -26.212, 73.72)156 520.8 Q
+(34.2280197, 118.0611038, 48.269, -14.951, 79.74)156 532.8 Q
+(34.2285156, 118.0604401, 48.207, -11.351, 81.68)156 544.8 Q
+(34.2290077, 118.0597687, 48.240, -10.518, 83.26)156 556.8 Q
+(34.2294998, 118.0591049, 48.225, 23.201, 84.60)156 568.8 Q
+(34.2304878, 118.0577698, 48.213, 15.769, 137.84)156 580.8 Q
+(34.2309799, 118.0570984, 48.234, 15.965, 151.54)156 592.8 Q
+(34.2314720, 118.0564346, 48.224, 16.520, 149.45)156 604.8 Q
+(34.2319679, 118.0557632, 48.223, 15.588, 151.61)156 616.8 Q
+(34.2329521, 118.0544281, 48.230, 13.889, 135.45)156 628.8 Q
+(34.2334442, 118.0537643, 48.223, 11.693, 137.37)156 640.8 Q
+(34.2339401, 118.0530930, 48.222, 14.050, 126.32)156 652.8 Q
+(34.2344322, 118.0524292, 48.216, 16.274, 156.28)156 664.8 Q
+(34.2354164, 118.0510941, 48.222, 15.058, 152.65)156 676.8 Q
+(34.2359123, 118.0504227, 48.221, 16.215, 158.57)156 688.8 Q
+(34.2364044, 118.0497589, 48.216, 15.024, 157.30)156 700.8 Q
+(34.2368965, 118.0490875, 48.225, 17.184, 156.36)156 712.8 Q F0
+(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(15)171.785 E EP
+%%Page: 16 16
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .387
+(No es poco com\372n para los archi)108 84 R -.2(vo)-.25 G(s).2 E/F1 10
+/Times-Bold@0 SF(SPLA)2.887 E(T!)-.95 E F0 .387
+(de p\351rdidas por trayectoria que conteng)2.887 F .387
+(an tanto como 3 mil-)-.05 F .388
+(lones o m\341s de l\355neas de datos. Si el archi)108 96 R .788 -.2
+(vo e)-.25 H 2.888(sp).2 G .389
+(rocesado, comentarios pueden ser puestos con un caracter)-2.888 F
+(de punto y coma. El editor de te)108 108 Q(xto)-.15 E F1(vim)2.5 E F0
+(ha probado ser capaz de editar archi)2.5 E -.2(vo)-.25 G 2.5(sd).2 G
+2.5(ee)-2.5 G(ste tama\361o.)-2.5 E 1.455
+(Note que al igual que el caso de los archi)108 132 R -.2(vo)-.25 G
+3.955(sd).2 G 3.955(ep)-3.955 G 1.455
+(atrones de antena, \341ngulos de ele)-3.955 F -.25(va)-.25 G 1.455
+(ci\363n ne).25 F -.05(ga)-.15 G(ti).05 E -.2(vo)-.25 G 3.955(ss).2 G(e)
+-3.955 E .429(re\214eren a inclinaciones hacia arriba \(sobre el horizo\
+nte\), mientras que \341ngulos positi)108 144 R -.2(vo)-.25 G 2.93(ss).2
+G 2.93(er)-2.93 G .43(e\214eren a incli-)-2.93 F .286(naciones hacia ab\
+ajo \(bajo el horizonte\). Esos \341ngulos se re\214eren a la ele)108
+156 R -.25(va)-.25 G .286(ci\363n para la antena receptora en).25 F .35
+(la altura sobre el ni)108 168 R -.15(ve)-.25 G 2.85(ld).15 G .35
+(el terreno especi\214cada usando la opci\363n)-2.85 F/F2 10
+/Times-Italic@0 SF(-L)2.851 E F0 .351
+(si la trayectoria entre el transmisor y el)2.851 F .131(receptor no ti\
+ene obstrucciones. Si la trayectoria entre el transmisor y el receptor \
+est\341 obstruida, entonces el)108 180 R .192
+(\341ngulo a la primera obstrucci\363n es retornado por)108 192 R F1
+(SPLA)2.693 E(T!)-.95 E F0 5.193(.E)C .193
+(sto es porque el modelo Longle)-5.193 F .193(y-Rice consid-)-.15 F .225
+(era la ener)108 204 R .224(g\355a que alcanza un punto distante sobre \
+una trayectoria obstruida como un deri)-.18 F -.25(va)-.25 G .224
+(do de la ener).25 F(g\355a)-.18 E .317(dispersada de la punta de la pr\
+imera instrucci\363n, solamente. Puesto que la ener)108 216 R .317
+(g\355a no puede alcanzar direc-)-.18 F
+(tamente la localizaci\363n obstruida, el actual \341ngulo de ele)108
+228 Q -.25(va)-.25 G(ci\363n a ese punto es irrele).25 E -.25(va)-.25 G
+(nte.).25 E 1.103(Cuando se modi\214can los archi)108 252 R -.2(vo)-.25
+G(s).2 E F1(SPLA)3.603 E(T!)-.95 E F0 1.102
+(de p\351rdidas por trayectoria para re\215ejar datos de patrones de)
+3.603 F(antena,)108 264 Q F2 .477
+(solo la \372ltima columna \(path loss\))2.976 F F0 .477
+(deber\355an ser enmendados para re\215ejar la g)2.977 F .477
+(anacia de antena nor)-.05 F(-)-.2 E .433
+(malizada en los \341ngulos de ele)108 276 R -.25(va)-.25 G .433
+(ci\363n y azimut especi\214cados en el archi).25 F -.2(vo)-.25 G 2.933
+(.\().2 G .433(Por ahora, programas y scripts)-2.933 F(capaces de reali\
+zar esta operaci\363n son dejados como tarea al usuario.\))108 288 Q
+1.618(Los mapas modi\214cados de p\351rdidas por trayectoria pueden ser\
+ importados nue)108 312 R -.25(va)-.25 G 1.618(mente a).25 F F1(SPLA)
+4.118 E(T!)-.95 E F0(para)4.118 E(generar mapas de cobertura re)108 324
+Q(visados.)-.25 E/F3 10/Courier@0 SF
+(splat -t kvea -pli pathloss.dat -s city.dat -b county.dat -o map.ppm)
+108 348 Q F0 .45(Los archi)108 372 R -.2(vo)-.25 G(s).2 E F1(SPLA)2.95 E
+(T!)-.95 E F0 .45(de p\351rdidas por trayectoria tambi\351n pueden ser \
+usados para guiar estudios de cober)2.95 F(-)-.2 E
+(tura o interferencia fuera de)108 384 Q F1(SPLA)2.5 E(T!)-.95 E F0(.)A
+/F4 10.95/Times-Bold@0 SF(ARCHIV)72 400.8 Q(OS DE ENTRAD)-.493 E 2.738
+(AD)-.383 G 2.738(ET)-2.738 G(ERRENO DEFINIDOS POR EL USU)-2.738 E(ARIO)
+-.657 E F0 .686(Un archi)108 412.8 R 1.086 -.2(vo d)-.25 H 3.186(et).2 G
+.687(erreno de\214nido por el usuario es un archi)-3.186 F 1.087 -.2
+(vo d)-.25 H 3.187(et).2 G -.15(ex)-3.187 G .687(to generado-por).15 F
+.687(-el-usuario que contiene)-.2 F .492
+(latitudes, longitudes, y alturas sobre el ni)108 424.8 R -.15(ve)-.25 G
+2.991(ld).15 G 2.991(el)-2.991 G 2.991(at)-2.991 G .491
+(ierra de caracter\355sticas de terreno espec\355\214ca que se cree)
+-2.991 F .593(son de importancia para el an\341lisis que)108 436.8 R F1
+(SPLA)3.094 E(T!)-.95 E F0 .594
+(est\341 desarrollando, pero perceptiblemente ausentes de los)3.094 F
+(archi)108 448.8 Q -.2(vo)-.25 G 3.257(sS).2 G .757
+(DF que est\341n siendo usados. Un archi)-3.257 F 1.157 -.2(vo d)-.25 H
+3.257(et).2 G .757(erreno de\214nido-por)-3.257 F .757
+(-el-usuario es importado dentro)-.2 F(de un an\341lisis de)108 460.8 Q
+F1(SPLA)2.5 E(T!)-.95 E F0(usando la opci\363n)5 E F2(-udt)2.5 E F0(:)A
+F3(splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm)114 484.8 Q
+F0(Un archi)108 508.8 Q .4 -.2(vo d)-.25 H 2.5(et).2 G
+(erreno de\214nido-por)-2.5 E
+(-el-usuario tiene la siguiente apariencia y estructura:)-.2 E F3
+(40.32180556, 74.1325, 100.0 meters)150 544.8 Q
+(40.321805, 74.1315, 300.0)150 556.8 Q
+(40.3218055, 74.1305, 100.0 meters)150 568.8 Q F0 .299
+(La altura del terreno es interpretada en pies sobre el ni)108 604.8 R
+-.15(ve)-.25 G 2.8(ld).15 G .3(el suelo a menos que sea se)-2.8 F .3
+(guido por la palabra)-.15 F .194(meters, y es adicionado en la parte s\
+uperior de el terreno especi\214cado en los datos SDF para la localizac\
+i\363n)108 616.8 R .672(especi\214cada. Debe saber que las caracter\355\
+sticas especi\214cadas en los archi)108 628.8 R -.2(vo)-.25 G 3.173(sd)
+.2 G 3.173(et)-3.173 G .673(erreno especi\214cados-por)-3.173 F(-)-.2 E
+1.155(el-usuario ser\341n interpretados como 3-arco se)108 640.8 R 1.154
+(gundos en latitud y longitud. Caracter\355sticas descritas en el)-.15 F
+(archi)108 652.8 Q 2.618 -.2(vo d)-.25 H 4.718(et).2 G 2.218
+(erreno de\214nido-por)-4.718 F 2.218
+(-el-usuario que traslapen las caracter\355sticas pre)-.2 F 2.219
+(viamente de\214nidas en el)-.25 F(archi)108 664.8 Q .4 -.2(vo s)-.25 H
+(on ignoradas por).2 E F1(SPLA)2.5 E(T!)-.95 E F0(.)A F4(GENERA)72 681.6
+Q(CI\323N DE MAP)-.602 E(AS T)-.81 E(OPOGR\301FICOS SIMPLES)-.197 E F0
+1.08(En ciertas ocasiones puede ser deseable generar un mapa topogr\341\
+\214co de una re)108 693.6 R 1.08(gi\363n sin gra\214car \341reas de)
+-.15 F 1.309(cobertura, trayectorias de l\355nea-de-vista, o generar re\
+portes de obstrucciones.)108 705.6 R 1.309(Existen v)6.309 F 1.31
+(arias maneras de)-.25 F .531(hacer esto. Si se desea generar un mapa t\
+opogr\341\214co ilustrando la localizaci\363n de un sitio del transmiso\
+r)108 717.6 R(y)5.53 E .12(receptor con un bre)108 729.6 R .42 -.15
+(ve r)-.25 H .12(eporte de te).15 F .121(xto describiendo las localizac\
+iones y distancias entre los sitios, entonces,)-.15 F(KD2BD Softw)72 768
+Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E(16)171.785 E EP
+%%Page: 17 17
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E(entonces se debe in)
+108 84 Q -.2(vo)-.4 G(car la opci\363n).2 E/F1 10/Times-Italic@0 SF(-n)
+2.5 E F0(como sigue:)2.5 E/F2 10/Courier@0 SF
+(splat -t tx_site -r rx_site -n -o topo_map.ppm)108 108 Q F0
+(Si no se desea un reporte de te)108 132 Q
+(xto, entonces debe usar la opci\363n)-.15 E F1(-N)2.5 E F0(:)A F2
+(splat -t tx_site -r rx_site -N -o topo_map.ppm)108 156 Q F0 .221(Si se\
+ desea un mapa topogr\341\214co centrado cerca de un sitio para un radi\
+o m\355nimo especi\214cado, un comando)108 180 R
+(similar al siguiente puede ser utilizado:)108 192 Q F2
+(splat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o topo_map.ppm)
+108 216 Q F0 .108(donde -R especi\214ca el m\355nimo radio de el mapa e\
+n millas \(\363 kil\363metros si la opci\363n)108 240 R F1(-metric)2.609
+E F0 .109(es usada\). Note)2.609 F .594(que el nombre del sitio_tx y la\
+ localizaci\363n no son presentadas en este ejemplo. Si se desea presen\
+tar esta)108 252 R 1.991(informaci\363n, simplemente cree un archi)108
+264 R 2.391 -.2(vo d)-.25 H 4.491(ec).2 G(iudades)-4.491 E/F3 10
+/Times-Bold@0 SF(SPLA)4.491 E(T!)-.95 E F0 1.991(con la opci\363n \()
+6.991 F F1(-s)A F0 4.492(\)ya)C 1.992(dici\363nele a las)-4.492 F .622
+(opciones de la l\355nea-de-comandos ilustradas arriba.)108 276 R .622
+(Si la opci\363n)5.622 F F1(-o)3.122 E F0 3.122(ye)3.122 G 3.122(la)
+-3.122 G(rchi)-3.122 E 1.022 -.2(vo d)-.25 H 3.121(es).2 G .621
+(alida son omitidos en)-3.121 F .447
+(esa operaci\363n, la salida topogr\341\214ca es escrita a un archi)108
+288 R .847 -.2(vo p)-.25 H .447(or defecto llamado).2 F F1(tx_site)2.947
+E(.ppm)-.15 E F0 .447(en el directorio)2.947 F(de trabajo actual.)108
+300 Q/F4 10.95/Times-Bold@0 SF(GENERA)72 316.8 Q(CI\323N DE ARCHIV)-.602
+E(OS DE GEOREFERENCIA)-.493 E F0 1.937
+(Los mapas topogr\341\214cos, de cobertura \()108 328.8 R F1(-c)A F0
+1.936(\), y contornos de p\351rdidas por trayectoria \()B F1(-L)A F0
+4.436(\)g)C 1.936(enerados por)-4.436 F F3(SPLA)108 340.8 Q(T!)-.95 E F0
+.174(pueden ser importados dentro del programa)2.673 F F3(Xastir)2.674 E
+F0 .174(\(X Amateur)2.674 F .174(Station T)5.174 F .174
+(racking and Information)-.35 F(Reporting\), generando un archi)108
+352.8 Q .4 -.2(vo d)-.25 H 2.5(eg).2 G(eoreferencia usando la opci\363n)
+-2.5 E F3(SPLA)2.5 E(T!)-.95 E F1(-g)2.5 E(eo)-.1 E F0(:)A F2
+(splat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o map.ppm)108
+376.8 Q F0 .943(El archi)108 400.8 R 1.343 -.2(vo d)-.25 H 3.443(eg).2 G
+.943(eoreferencia creado tendr\341 el mismo nombre base que el archi)
+-3.443 F -.2(vo)-.25 G F1(-o).2 E F0 .942(especi\214cado, pero con)3.442
+F -.15(ex)108 412.8 S(tensi\363n).15 E F1(.g)6.125 E(eo)-.1 E F0 3.625
+(,yp)C 1.125(ermite la apropiada interpretaci\363n y presentaci\363n de\
+ los gr\341\214cos .ppm)-3.625 F F3(SPLA)3.626 E(T!)-.95 E F0 1.126
+(en el)3.626 F(programa)108 424.8 Q F3(Xastir)2.5 E F0(.)A F4(GENERA)72
+441.6 Q(CION DE ARCHIV)-.602 E(OS KML GOOGLE MAP)-.493 E F0(Archi)108
+453.6 Q -.2(vo)-.25 G 3.703(sK).2 G -.15(ey)-3.953 G 1.203
+(hole Markup Language compatibles con).15 F F3 1.202(Google Earth)3.703
+F F0 1.202(pueden ser generados por)3.702 F F3(SPLA)3.702 E(T!)-.95 E F0
+(cuando se realizan an\341lisis punto-a-punto in)108 465.6 Q -.2(vo)-.4
+G(cando la opci\363n).2 E F1(-kml)2.5 E F0(:)A F2
+(splat -t wnjt-dt -r kd2bd -kml)108 489.6 Q F0 .298(El archi)108 513.6 R
+.698 -.2(vo K)-.25 H .298(ML generado tendr\341 la misma estructura que\
+ el nombre del Reporte de Obstrucciones para los).2 F
+(sitios del transmisor y receptor dados, e)108 525.6 Q
+(xcepto que tendr\341 una e)-.15 E(xtensi\363n)-.15 E F1(.kml)5 E F0(.)A
+.342(Una v)108 549.6 R .342(ez car)-.15 F -.05(ga)-.18 G .342
+(do dentro del).05 F F3 .341(Google Earth)2.842 F F0(\(Archi)2.841 E
+.741 -.2(vo -)-.25 H .341(-> Abrir\), el archi).2 F .741 -.2(vo K)-.25 H
+.341(LM e).2 F .341(xhibir\341 las localizaciones)-.15 F 1.672
+(de los sitios de transmisi\363n y recepci\363n en el mapa.)108 561.6 R
+1.673(Los puntos de vista de la imagen ser\341n desde la)6.673 F 1.014(\
+posici\363n del sitio de transmisi\363n mirando hacia la localizaci\363\
+n del receptor)108 573.6 R 3.514(.L)-.55 G 3.513(at)-3.514 G 1.013
+(rayectoria punto-a-punto)-3.513 F .287(entre los sitios ser\341 presen\
+tada como una l\355nea blanca, mientras que la trayectoria de linea-de-\
+vista RF ser\341)108 585.6 R 1.953(presentada en v)108 597.6 R 1.953
+(erde. Las herramientas de na)-.15 F -2.25 -.15(veg a)-.2 H 1.953
+(ci\363n de).15 F F3 1.953(Google Earth)4.453 F F0 1.953
+(le permiten al usuario "v)4.453 F(olar")-.2 E(alrededor de la trayecto\
+ria, identi\214cando se\361ales, caminos, y otras caracter\355sticas co\
+ntenidas.)108 609.6 Q .8
+(Cuando se realiza el an\341lisis de cobertura re)108 633.6 R .801
+(gional, el archi)-.15 F -.2(vo)-.25 G F1(.kml)6.001 E F0 .801
+(generado por)3.301 F F3(SPLA)3.301 E(T!)-.95 E F0 .801
+(permitir\341 a los)3.301 F 1.173(contornos de intensidad de se\361al o\
+ de p\351rdidas por trayectoria a ser gra\214cados como capas sobre map\
+as)108 645.6 R F3 1.263(Google Earth)108 657.6 R F0 1.264
+(presentados en una manera semi-transparente.)3.763 F 1.264(El archi)
+6.264 F -.2(vo)-.25 G F1(.kml)3.964 E F0 1.264
+(generado tendr\341 el mismo)3.764 F(nombre base como el del archi)108
+669.6 Q -.2(vo)-.25 G F1(.ppm)2.7 E F0(normalmente generado.)2.5 E F4
+(DETERMIN)72 686.4 Q -.602(AC)-.219 G .036(I\323N DE LA AL).602 F .036
+(TURA DE LA ANTEN)-1.007 F 2.774(AS)-.219 G .036(OBRE EL PR)-2.774 F
+.036(OMEDIO DEL TERRENO)-.329 F F3(SPLA)108 698.4 Q(T!)-.95 E F0 1.546
+(determina la altura de la antena sobre el promedio del terreno \(HAA)
+4.045 F 1.546(T\) de acuerdo al proced-)-1.11 F 3.289
+(imiento de\214nido por la Comisi\363n Federal de Comunicaciones. P)108
+710.4 R 3.289(arte 73.313\(d\). De acuerdo a esta)-.15 F .124
+(de\214nici\363n, la ele)108 722.4 R -.25(va)-.25 G .124
+(ci\363n del terreno a lo lar).25 F .124
+(go de ocho radiales entre 2 y 16 millas \(3 y 16 Kil\363metros\) desde)
+-.18 F(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)
+2.5 E(17)171.785 E EP
+%%Page: 18 18
+%%BeginPageSetup
+BP
+%%EndPageSetup
+/F0 10/Times-Roman@0 SF(SPLA)72 48 Q 151.145(T!\(1\) KD2BD)-1.11 F
+(Softw)2.5 E 151.145(are SPLA)-.1 F(T!\(1\))-1.11 E .113(el sitio que e\
+st\341 siendo analizado es muestreado y promediado para los azimut)108
+84 R .113(cada 45 grados comenzando)5.113 F .251(con el norte v)108 96 R
+2.751(erdadero. Si)-.15 F .251(uno o mas radiales caen enteramente sobr\
+e el mar o sobre el continente fuera de)2.751 F .733
+(los Estados Unidos \(\341reas para las cuales no e)108 108 R .733
+(xisten disponibles datos topogr\341\214cos USGS\), entonces esos)-.15 F
+.169(radiales son omitidos de los c\341lculos del promedio del terreno.\
+ Si parte de los radiales se e)108 120 R .17(xtienden sobre el)-.15 F
+.841(mar o fuera de los Estados Unidos, entonces solo la parte de esos \
+radiales que caen sobre la tierra de los)108 132 R(Estados Unidos son u\
+sados en la determinaci\363n del promedio del terreno.)108 144 Q 1.075
+(Note que los datos de ele)108 168 R -.25(va)-.25 G 1.075(ciones SR).25
+F 1.075(TM, a diferencia de los antiguos datos 3-arcos se)-.6 F 1.075
+(gundos USGS, se)-.15 F -.15(ex)108 180 S .142(tienden m\341s all\341 d\
+e las fronteras de los Estados Unidos. Por esta raz\363n,).15 F .141
+(los resultados)5.142 F(HAA)5.141 E 1.621 -.74(T, n)-1.11 H 2.641(oe).74
+G(star\341n)-2.641 E .292(en \214el cumplimiento con la FCC parte 73.31\
+3\(d\) en \341reas a lo lar)108 192 R .293
+(go de la frontera de los Estados Unidos si)-.18 F(los archi)108 204 Q
+-.2(vo)-.25 G 2.5(sS).2 G(DF usados por)-2.5 E/F1 10/Times-Bold@0 SF
+(SPLA)2.5 E(T!)-.95 E F0(son deri)2.5 E -.25(va)-.25 G(dos-SR).25 E(TM.)
+-.6 E 1.499(Cuando se realiza an\341lisis punto-a-punto del terreno,)108
+228 R F1(SPLA)3.999 E(T!)-.95 E F0 1.498
+(determina la altura de la antena sobre el)3.999 F .302(promedio del)108
+240 R .303
+(terreno solo si su\214cientes datos topogr\341\214cos han sido car)
+5.302 F -.05(ga)-.18 G .303(dos por el programa para realizar).05 F .417
+(el an\341lisis punto-a-punto. En la mayor\355a de los casos, esto ser\
+\341 v)108 252 R .416(erdadero, a menos que el sitio en cuesti\363n)-.15
+F(no est\351 dentro de 10 millas de la frontera de los datos topogr\341\
+\214cos car)108 264 Q -.05(ga)-.18 G(dos en memoria.).05 E 1.334(Cuando\
+ se realiza el an\341lisis de predicci\363n de \341rea, su\214cientes d\
+atos topogr\341\214cos son normalmente car)108 288 R(-)-.2 E -.05(ga)108
+300 S 1.438(dos por).05 F F1(SPLA)3.938 E(T!)-.95 E F0 1.438(para reali\
+zar los c\341lculos del promedio del terreno. Bajo esas condiciones,)
+3.938 F F1(SPLA)3.937 E(T!)-.95 E F0(pro)108 312 Q -.15(ve)-.15 G .566(\
+er\341 la altura de la antena sobre el promedio del terreno, como tambi\
+\351n el promedio del terreno sobre).15 F .104(el ni)108 324 R -.15(ve)
+-.25 G 2.604(ld).15 G .104(el mar para los azimut de 0, 45, 90, 135, 18\
+0, 225, 270, y 315 grados, e incluir\341 dicha informaci\363n)-2.604 F
+.583(en el reporte de sitio generado. Si uno o m\341s de los ocho radia\
+les caen sobre el mar o sobre re)108 336 R .584(giones para)-.15 F .989
+(las cuales no e)108 348 R .989(xisten datos SDF disponibles,)-.15 F F1
+(SPLA)3.489 E(T!)-.95 E F0 3.489(reportar\341 sin)5.989 F .988
+(terreno la trayectoria de los radiales)3.489 F(afectados.)108 360 Q/F2
+10.95/Times-Bold@0 SF(RESTRINGIENDO EL T)72 376.8 Q
+(AMA\321O M\301XIMO DE UN)-.986 E 2.738(AR)-.219 G(EGI\323N AN)-2.738 E
+(ALIZAD)-.219 E(A)-.383 E F1(SPLA)108 388.8 Q(T!)-.95 E F0 .721
+(lee los archi)3.221 F -.2(vo)-.25 G 3.221(sS).2 G .722(DF de acuerdo a\
+ sus necesidades dentro de una serie de "p\341ginas" de memoria)-3.221 F
+.488(dentro de la estructura del programa. Cada "p\341gina" contiene un\
+ archi)108 400.8 R .888 -.2(vo S)-.25 H .488(DF representando una re).2
+F .488(gi\363n de)-.15 F .915(terreno de un grado por un grado.)108
+412.8 R .915(Una sentencia)5.915 F/F3 10/Times-Italic@0 SF .915
+(#de\214ne MAXP)5.915 F -.35(AG)-.9 G(ES).35 E F0 .915
+(en las primeras l\355neas del archi)3.415 F -.2(vo)-.25 G .363
+(splat.cpp con\214gura el m\341ximo n\372mero de "p\341ginas")108 424.8
+R .362(disponibles para los datos topogr\341\214cos.)5.362 F .362
+(Esto tambi\351n)5.362 F .606(con\214gura el)108 436.8 R .606
+(tama\361o m\341ximo de los mapas generados por)5.606 F F1(SPLA)3.107 E
+(T!)-.95 E F0 5.607(.P)C .607(or defecto MAXP)-5.607 F -.4(AG)-.92 G
+.607(ES es con\214gu-).4 F .766(rado a 9. Si)108 448.8 R F1(SPLA)3.266 E
+(T!)-.95 E F0 .766(produce un f)3.266 F .766(allo de se)-.1 F .766
+(gmentaci\363n al arrancar con estos par\341metros por defecto, sig-)
+-.15 F .467(ni\214ca que no hay su\214ciente memoria RAM y/\363 memoria\
+ virtual \(partici\363n sw)108 460.8 R .468(ap\) para correr)-.1 F F1
+(SPLA)2.968 E(T!)-.95 E F0(con)5.468 E 1.023(este n\372mero de MAXP)108
+472.8 R -.4(AG)-.92 G 1.023
+(ES. En situaciones donde la memoria disponible es baja, MAXP).4 F -.4
+(AG)-.92 G 1.023(ES pueden).4 F 1.031(ser reducidos a 4 con el entendim\
+iento de que esto limitar\341 grandemente la m\341xima re)108 484.8 R
+1.032(gi\363n que)-.15 F F1(SPLA)3.532 E(T!)-.95 E F0 .139
+(estar\341 habilitado a analizar)108 496.8 R 2.639(.S)-.55 G 2.639(is)
+-2.639 G 2.639(et)-2.639 G .139(iene disponible 118 me)-2.639 F -.05(ga)
+-.15 G .139(bytes \363 mas de la memoria total \(partici\363n sw).05 F
+(ap)-.1 E 1.18(sumada la RAM\), entonces MAXP)108 508.8 R -.4(AG)-.92 G
+1.181
+(ES puede ser incrementado a 16. esto permitir\341 operaciones sobre).4
+F .665(una re)108 520.8 R .664(gi\363n de 4-grados por 4-grados, lo cua\
+l es su\214ciente para alturas de antenas)-.15 F .664(que e)5.664 F .664
+(xcedan los 10,000)-.15 F(pies sobre el ni)108 532.8 Q -.15(ve)-.25 G
+2.5(ld).15 G(el mar)-2.5 E 2.5(,\363d)-.4 G
+(istancias punto-a-punto sobre las 1000 millas.)-2.5 E F2(INFORMA)72
+549.6 Q(CI\323N ADICION)-.602 E(AL)-.219 E F0 .149
+(Las \372ltimas noticias e informaci\363n respecto al programa)108 561.6
+R F1(SPLA)2.649 E(T!)-.95 E F0 .15(est\341 disponible a tra)5.149 F .15
+(v\351s de la p\341gina web)-.2 F(o\214cial localizada en:)108 573.6 Q
+F3(http://www)2.5 E(.qsl.net/kd2bd/splat.html)-.74 E F0(.)A F2 -.548(AU)
+72 590.4 S -.197(TO).548 G(RES).197 E F0(John A. Magliacane, KD2BD <)108
+602.4 Q F3(kd2bd@amsat.or)A(g)-.37 E F0(>)A(Creator)144 614.4 Q 2.5(,L)
+-.4 G(ead De)-2.5 E -.15(ve)-.25 G(loper).15 E(Doug McDonald <)108 631.2
+Q F3(mcdonald@scs.uiuc.edu)A F0(>)A(Original Longle)144 643.2 Q
+(y-Rice Model inte)-.15 E(gration)-.15 E(Ron Bentle)108 660 Q 2.5(y<)
+-.15 G F3 -.45(ro)-2.5 G(nbentle).45 E(y@earthlink.net)-.3 E F0(>)A
+(Fresnel Zone plotting and clearance determination)144 672 Q
+(KD2BD Softw)72 768 Q 107.455(are 16)-.1 F(de Septiembre de 2007)2.5 E
+(18)171.785 E EP
+%%Trailer
+end
+%%EOF
--- /dev/null
+SPLAT!(1) KD2BD Software SPLAT!(1)
+
+
+
+NOMBRE
+ splat - An RF Signal Propagation, Loss, And Terrain anal-
+ ysis tool SPLAT!
+
+ splat - Es una herramienta para el anlisis de Propagacin
+ de Seales RF, Prdidas, y caractersticas del Terreno
+
+SINOPSIS
+ splat [-t sitio_transmisor.qth] [-r sitio_receptor.qth]
+ [-c rx altura de la antena para el anlisis de cobertura
+ LOS (pies/metros) (flotante)] [-L rx altura de la antena
+ para el anlisis de cobertura Longley-Rice (pies/metros)
+ (flotante)] [-p perfil_terreno.ext] [-e perfil_eleva-
+ cion.ext] [-h perfil_altura.ext] [-H perfil_altura_normal-
+ izada.ext] [-l perfil_Longley-Rice.ext] [-o nom-
+ bre_archivo_mapa_topogrfico.ppm] [-b archivo_lmites_car-
+ tograficos.dat] [-s base_datos_sitios/ciudades.dat] [-d
+ ruta_directorio_sdf] [-m radio multiplicador tierra
+ (flotante)] [-f frequencia (MHz) para clculos de la zona
+ de Fresnel (flotante)] [-R mximo radio de covertura (mil-
+ las/kilmetros) (flotante)] [-dB mximo contorno de aten-
+ uacin a presentar sobre un mapa de prdidas por trayectoria
+ (80-230 dB)] [-fz porcentaje despejado de la zona de Fres-
+ nel (default = 60)] [-plo archivo_salida_prdi-
+ das_por_trayectoria.txt] [-pli archivo_entrada_prdi-
+ das_por_trayectoria.txt] [-udt archivo_ter-
+ reno_definido_por_el_usuario.dat] [-n] [-N] [-nf] [-ngs]
+ [-geo] [-kml] [-metric]
+
+DESCRIPCIN
+ SPLAT! es una poderosa herramienta para el anlisis de
+ terreno y propagacin RF cubriendo el espectro entre 20
+ Megahertz y 20 Gigahertz. SPLAT! es Software Libre y est
+ diseado para operar en escritorios Unix y basados en
+ Linux. La redistribucin y/ modificacin est permitida bajo
+ los trminos de la licencia pblica general GNU segn lo pub-
+ licado por la Fundacin de Software Libre, versin 2. La
+ adopcin del cdigo fuente de SPLAT! en aplicaciones propi-
+ etarias o de fuente-cerrada es una violacin de esta
+ licencia, y esta estrictamente prohibida.
+
+ SPLAT! es distribudo con la esperanza de que sea til, pero
+ SIN NINGUNA GARANTA, an la garanta implcita de COMERCIAL-
+ IZACIN de la APLICACIN PARA UN PROPSITO PARTICULAR. Vea
+ la licencia GNU para ms detalles.
+
+INTRODUCCIN
+ Las aplicaciones de SPLAT! incluyen la visualizacin,
+ diseo, y anlisis de enlaces de redes inalmbricas WAN,
+ sistemas de radio comunicaciones comerciales y aficionados
+ sobre los 20 megahertz, enlaces microonda, estudios de
+ interferencia y coordinacin de frecuencias, y determinacin
+ del contorno de cobertura de las regiones de radio y tele-
+ visin terrestres anlogas y digitales.
+
+ SPLAT! proporciona datos de ingeniera RF del sitio, tales
+ como distancias sobre el arco terrestre y azimut entre
+ sitios de transmisin y recepcin, ngulos de elevacin de la
+ antena (uptilt), ngulos de depresin (downtilt), altura de
+ la antena sobre nivel del mar, altura de la antena sobre
+ el promedio del terreno, azimut, distancias y elevaciones
+ para determinar obstrucciones, Atenuaciones de trayectoria
+ Longley-Rice, e intensidad de seal recibida, Adicional-
+ mente, los requisitos mnimos necesarios de altura de las
+ antenas para establecer trayectorias de comunicacin de
+ lnea-de-vista sin obstrucciones debido al terreno, la
+ primera zona de Fresnel, y cualquier porcentaje definido
+ por el usuario de la primera zona de Fresnel.
+
+ SPLAT! produce informes, grficos, y mapas topogrficos
+ altamente detallados y cuidadosamente descritos que pre-
+ sentan las trayectorias de lnea-de-vista, contornos
+ regionales de prdidas por trayectoria y contornos de
+ intensidad de seal a travs de los cuales se puede determi-
+ nar la prediccin del rea de cobertura de sistemas de
+ transmisores y repetidoras. Al realizar anlisis de lnea
+ de vista y prdidas Longley-Rice cuando se emplean mltiples
+ sitios de transmisores o repetidores, SPLAT! determina las
+ reas de cobertura individuales y mutuas dentro de la red
+ especificada.
+
+ Simplemente tipee splat en la consola de comandos, esto
+ retornar un resumen de las opciones de lnea de comando de
+ SPLAT!:
+
+
+
+ --==[ SPLAT! v1.2.1 Available Options...
+ ]==--
+
+ -t txsite(s).qth ( max 4 con -c, max 30 con -L)
+ -r rxsite.qth (sitio de recepcin)
+ -c grafica la cobertura del TX(s) (antena RX a X
+ pies/metros SNT)
+ -L grafica prdidas por trayectoria del TX (RX a X
+ pies/metros SNT)
+ -s nombre de archivo(s) de ciudades/sitios a importar
+ (max 5)
+ -b nombre de archivo(s) de lmites cartogrficos a importar
+ (max 5)
+ -p nombre de archivo para graficar el perfil del terreno
+ -e nombre de archivo para graficar la elevacin del ter-
+ reno
+ -h nombre de archivo para graficar la altura del terreno
+ -H nombre de archivo para graficar la altura normalizada
+ del terreno
+ -l nombre de archivo para graficar el modelo Longley-Rice
+ -o nombre de archivo para generar el mapa topogrfico
+ (.ppm)
+ -u nombre del archivo del terreno definido-por-el-usuario
+ a importar
+ -d directorio que contiene los archivos sdf (reemplaza
+ ~/.splat_path)
+ -m multiplicador del radio de la tierra
+ -n no grafica las rutas de LDV in mapas .ppm
+ -N no produce reportes innecesarios del sitio reportes
+ de obstruccin
+ -f frecuencia para el clculo de la zona de Fresnel (MHz)
+ -R modifica el rango por defecto para -c -L (millas/kil-
+ metros)
+ -db mximo contorno de prdidas por trayectoria (80-230
+ dB)
+ -nf no grafica la zona de Fresnel en los grficos de
+ altura
+ -fz porcentaje de despeje de la zona de Fresnel (default
+ = 60)
+ -ngs muestra topografa de escala de grises en blanco
+ (archivos .ppm)
+ -erp valor ERP en lugar del declarado en el archivo .lrp
+ (Watts)
+ -pli nombre del archivo de entrada de prdidas-por-trayec-
+ toria
+ -plo nombre del archivo de salida de prdidas-por-trayec-
+ toria
+ -udt nombre del archivo de entrada de terreno definido-
+ por-el-usuario
+ -kml genera archivo compatible Google Earth .kml(enlaces
+ punto-a-punto)
+ -geo genera un archivo Xastir de georeferencia .geo (con
+ salida .ppm)
+ -metric usa unidades mtricas en lugar de imperiales (I/O
+ del usuario)
+
+
+FICHEROS DE ENTRADA
+ SPLAT! es una aplicacin manejada por linea de comandos
+ terminal de textos (shell), y lee los datos de entrada a
+ travs de un nmero de ficheros de datos. Algunos archivos
+ son obligatorios para la apropiada ejecucin del programa,
+ mientras que otros son opcionales. Los archivos obligato-
+ rios incluyen los modelos topogrficos 3-arco segundo en la
+ forma de archivos de datos de SPLAT (archivos SDF),
+ archivos de localizacin del sitio (archivos QTH), y
+ archivos de parmetros para el modelo Longley-Rice
+ (archivos LRP). Los archivos opcionales incluyen archivos
+ de localizacin de ciudades/sitios, archivos de lmites car-
+ togrficos, archivos de terreno definidos por el usuario,
+ archivos de entrada de prdidas-por-trayectoria, archivos
+ de patrones de radiacin de antenas, y archivos de
+ definicin de color.
+
+FICHEROS DE DATOS SPLAT
+ SPLAT! importa los datos topogrficos desde los ficheros de
+ datos SPLAT (SDFs). Estos archivos se pueden generar desde
+ varias fuentes de informacin. En los Estados Unidos, los
+ ficheros de datos SPLAT se pueden generar a travs de la
+ U.S. Geological Survey Digital Elevation Models (DEMs)
+ usando la herramienta usgs2sdf incluida con SPLAT!. Los
+ modelos de elevacin digital USGS compatibles con esta
+ utilidad pueden ser descargados de:
+ http://edcftp.cr.usgs.gov/pub/data/DEM/250/.
+
+ Una resolucin significativamente mejor se puede obtener
+ con el uso de los modelos digitales de elevacin versin 2
+ SRTM-3. Estos modelos son el resultado de la misin
+ topografca del radar espacial Shuttle STS-99, y estn
+ disponibles para la mayora de las regiones pobladas de la
+ tierra. Los ficheros de datos SPLAT pueden ser generados
+ desde los datos SRTM usando la herramienta incluida
+ srtm2sdf. Los archivo SRTM-3 versin 2 se pueden obtener a
+ travs de FTP annimo desde:
+ ftp://e0srp01u.ecs.nasa.gov:21/srtm/version2/
+
+ La utilidad strm2sdf tambin puede ser usada para convertir
+ los datos SRTM 3-arco segundo en formato Band Interleaved
+ by Line (.BIL) para usar con SPLAT!. Estos datos estn
+ disponibles va web en: http://seamless.usgs.gov/web-
+ site/seamless/
+
+ los datos Band Interleaved by Line deben ser descargados
+ en una manera especfica para ser compatible con srtm2sdf y
+ SPLAT!. por favor consulte la documentacin srtm2sdf's para
+ instrucciones sobre la descarga de datos topogrficos .BIL
+ a travs del Sitio Web USGS's Seamless.
+
+ A pesar de la exactitud ms alta que los datos SRTM ofre-
+ cen, existen algunos vacos en los conjuntos de datos.
+ Cuando se detectan estos vacos, la utilidad srtm2sdf los
+ substituye por los datos encontrados en los archivos SDF
+ existentes (que presumiblemente fueron creados de datos
+ anteriores de la USGS con la utilidad usgs2sdf). Si los
+ datos SDF, USGS-derivados no estn disponibles, los vacos
+ se reemplazan con el promedio de los pixeles adyacentes, o
+ reemplazo directo.
+
+ Los ficheros de datos de SPLAT contienen valores enteros
+ de las elevaciones topogrficas (en metros) referenciados
+ al nivel del mar para regiones de la tierra de 1-grado por
+ 1-grado con una resolucin de 3-arco segundos. Los archivos
+ SDF pueden ser ledos desde el formato estndar (.sdf) gen-
+ erado por las utilidades usgs2sdf y srtm2sdf, en formato
+ comprimido bzip2 (.sdf .bz2). Puesto que los archivos sin
+ comprimir se pueden procesar ligeramente ms rpido que los
+ archivos comprimidos, SPLAT! busca los datos SDF necesar-
+ ios en formato sin comprimir primero. Si los datos sin
+ comprimir no pueden ser localizados, SPLAT! entonces busca
+ los datos en formato comprimido bzip2. Si tampoco se
+ pueden encontrar los archivos SDF comprimidos para la
+ regin solicitada, SPLAT! asume que la regin es el ocano, y
+ asignar una elevacin del nivel del mar a estas reas.
+
+ Esta caracterstica de SPLAT! permite realizar el anlisis
+ de trayectorias no solamente sobre la tierra, sino tambin
+ entre las reas costeras no representadas por los datos del
+ Modelo de Elevacin Digital. Sin embargo, este compor-
+ tamiento de SPLAT! resalta la importancia de tener todos
+ los archivos SDF requeridos para la regin a ser analizada,
+ para as obtener resultados significativos.
+
+ARCHIVOS DE LOCALIZACIN DEL SITIO (QTH)
+ SPLAT! SPLAT! importa la informacin de la localizacin de
+ los sitios del transmisor y del receptor analizados por el
+ programa de los archivos ASCII que tienen una extensin
+ .qth. Los archivos QTH contienen el nombre del sitio, la
+ latitud del sitio (positiva al norte del ecuador, negativa
+ al sur), la longitud del sitio (en grados oeste W de 0 a
+ 360 grados), y; La altura de la antena del sitio sobre el
+ nivel del suelo (AGL), cada uno separado por un caracter
+ de salto-de-lnea. La altura de la antena se asume a ser
+ especificada en pies a menos que sea seguida por la letra
+ m o de la palabra meters en maysculas minsculas. La
+ informacin de la latitud y de la longitud se puede expre-
+ sar en formato decimal (74.6889) en formato grados, min-
+ utos, segundos (DMS) (74 41 20.0).
+
+ Por ejemplo, un archivo de localizacin de sitio que
+ describa la estacin de televisin WNJT-DT, Trenton, NJ
+ (wnjt-dt.qth) se puede leer como sigue:
+
+
+ WNJT-DT
+ 40.2828
+ 74.6864
+ 990.00
+
+
+ Cada sitio de transmisor y receptor analizado por SPLAT!
+ debe ser representado por su propio archivo de la local-
+ izacin de sitio (QTH).
+
+ARCHIVOS DE PARMETROS LONGLEY-RICE (LRP)
+ Los archivos de datos de parmetros Longley-Rice son
+ requeridos por SPLAT! para determinar ls prdidas por
+ trayectoria RF ya sea en el modo punto-a-punto prediccin
+ de rea. Los datos de parmetros para el modelo Longley-Rice
+ desde archivos que tienen el mismo nombre base del archivo
+ QTH del sitio del transmisor, pero con extensin .lrp. Los
+ Archivos SPLAT! LRP comparte el siguiente formato (wnjt-
+ dt.lrp):
+
+
+ 15.000 ; Earth Dielectric Constant (Relative per-
+ mittivity)
+ 0.005 ; Earth Conductivity (Siemens per meter)
+ 301.000 ; Atmospheric Bending Constant (N-units)
+ 647.000 ; Frequency in MHz (20 MHz to 20 GHz)
+ 5 ; Radio Climate (5 = Continental Temper-
+ ate)
+ 0 ; Polarization (0 = Horizontal, 1 = Verti-
+ cal)
+ 0.50 ; Fraction of situations (50% of loca-
+ tions)
+ 0.90 ; Fraction of time (90% of the time)
+ 46000.0 ; ERP in Watts (optional)
+
+
+ Si un archivo LRP correspondiente al archivo QTH del sitio
+ de transmisin no puede ser encontrado, SPLAT! explorar el
+ directorio de trabajo actual buscando el archivo
+ "splat.lrp". Si este archivo tampoco puede ser encontrado,
+ entonces los parmetros por defecto enumerados arriba sern
+ asignados por SPLAT! y un archivo correspondiente
+ "splat.lrp" conteniendo estos parmetros por defecto ser
+ escrito al directorio actual de trabajo. El archivo
+ "splat.lrp" generado se puede editar de acuerdo a las
+ necesidades del usuario.
+
+ Las constantes dielctricas tpicas de la tierra y sus val-
+ ores de conductividad son los siguientes:
+
+
+ Dielectric Constant Conductiv-
+ ity
+ Salt water : 80 5.000
+ Good ground : 25 0.020
+ Fresh water : 80 0.010
+ Marshy land : 12 0.007
+ Farmland, forest : 15 0.005
+ Average ground : 15 0.005
+ Mountain, sand : 13 0.002
+ City : 5 0.001
+ Poor ground : 4 0.001
+
+
+ Los cdigos de Clima de Radio usados por SPLAT! son los
+ siguientes:
+
+
+ 1: Equatorial (Congo)
+ 2: Continental Subtropical (Sudan)
+ 3: Maritime Subtropical (West coast of Africa)
+ 4: Desert (Sahara)
+ 5: Continental Temperate
+ 6: Maritime Temperate, over land (UK and west
+ coasts of US & EU)
+ 7: Maritime Temperate, over sea
+
+
+ El clima templado continental es comn a las grandes masas
+ de la tierra en la zona templada, tal como los Estados
+ Unidos. Para trayectorias inferiores a 100 kilmetros, es
+ poca la diferencia entre los climas templados continen-
+ tales y martimos.
+
+ Los parmetros sptimo y octavo en el archivo .lrp corre-
+ sponden al anlisis estadstico proporcionado por el modelo
+ Longley-Rice. En este ejemplo, SPLAT! devolver la mxima
+ prdida de trayectoria que ocurre el 50% del tiempo (frac-
+ cin del tiempo) en el 90% de las situaciones (fraccin de
+ situaciones). Esto es a menudo denotado como F(50,90) en
+ los estudios Longley_Rice. En los Estados Unidos un crite-
+ rio F(50,90) es tpicamente usado para televisin digital
+ (8-level VSB modulation), mientras que F(50,50) es usado
+ para radiodifusin analgica (VSB-AM+NTSC).
+
+ Para mayor informacin de esos parmetros, puede visitar:
+ http://flattop.its.bldrdoc.gov/itm.html and
+ http://www.softwright.com/faq/engineering/prop_long-
+ ley_rice.html
+
+ El parmetro final en el archivo .lrp corresponde a la
+ potencia efectiva radiada, y es opcional. Si esta es
+ incluida en el archivo seal y los contornos de niveles de
+ intensidad de campo cuando se realicen los estudios Long-
+ ley-rice. Si el parmetro es omitido, se computan las prdi-
+ das por trayectoria en su lugar. El ERP provisto en el
+ archivo .lrp puede ser invalidado usando la opcin SPLAT!
+ de lnea-de-comando -erp sin tener que editar el archivo
+ .lrp para conseguir el mismo resultado.
+
+ARCHIVOS DE LOCALIZACIN DE CIUDADES
+ Los nombres y las localizaciones de ciudades, sitios de la
+ torre, u otros puntos de inters se pueden importar y
+ trazar en los mapas topogrficos generados por SPLAT!.
+ SPLAT! importa los nombres de ciudades y localizaciones de
+ los archivos ASCII que contienen el nombre, latitud y lon-
+ gitud de la localizacin de inters. Cada campo es separado
+ por una coma. Cada expediente es separado por un caracter
+ de salto-de-linea. Al igual que con los archivos .qth, la
+ informacin de la latitud y la longitud se puede ingresar
+ en formato decimal en formato de grados, minutos, segun-
+ dos (DMS).
+
+ Por ejemplo (cities.dat):
+
+ Teaneck, 40.891973, 74.014506
+ Tenafly, 40.919212, 73.955892
+ Teterboro, 40.859511, 74.058908
+ Tinton Falls, 40.279966, 74.093924
+ Toms River, 39.977777, 74.183580
+ Totowa, 40.906160, 74.223310
+ Trenton, 40.219922, 74.754665
+
+
+ Un total de cinco ficheros de datos separados de ciudades
+ se pueden importar a la vez, y no hay lmite al tamao de
+ estos archivos. SPLAT! lee datos de las ciudades en base
+ a "primero ingresada primero servida", y traza solamente
+ las localizaciones cuyas anotaciones no estn en conflicto
+ con anotaciones de las localizaciones ledas anteriormente
+ durante en el archivo actual de datos de ciudades, en
+ archivo previos. Este comportamiento en SPLAT! reduce al
+ mnimo el alboroto al generar los mapas topogrficos, pero
+ tambin determina que por mandato las localizaciones impor-
+ tantes estn puestas al principio del primer fichero de
+ datos de ciudades, y las localizaciones de menor importan-
+ cia sean colocadas a continuacin en la lista o en los
+ ficheros de datos subsecuentes.
+
+ Los ficheros de datos de las ciudades se pueden generar
+ manualmente usando cualquier editor de textos, importar de
+ otras fuentes, o derivar de los datos disponibles de la
+ oficina de censo de los Estados Unidos, usando la her-
+ ramienta citydecoder incluida con SPLAT!. Estos datos
+ estn disponibles gratuitamente va Internet en:
+ http://www.census.gov/geo/www/cob/bdy_files.html, y deben
+ estar en formato ASCII.
+
+ARCHIVOS DE DATOS DE LIMITES CARTOGRFICOS
+ Los datos cartogrficos de lmites se pueden tambin importar
+ para trazar los lmites de las ciudades, condados, o esta-
+ dos en los mapas topogrficos generados por SPLAT!. Estos
+ datos deben estar en el formato de metadatos de archivos
+ cartogrficos de lmites ARC/INFO Ungenerate (formato
+ ASCII), y estn disponibles para los E.E.U.U..en la Oficina
+ de Censos va Internet en: http://www.cen-
+ sus.gov/geo/www/cob/co2000.html#ascii y http://www.cen-
+ sus.gov/geo/www/cob/pl2000.html#ascii. Un total de cinco
+ archivos cartogrficos separados de lmites se puede impor-
+ tar a la vez. No es necesario importar lmites de estado
+ si ya se han importado los lmites del condado.
+
+OPERACIN DEL PROGRAMA
+ SPLAT! Debido a que SPLAT! hace un uso intensivo del CPU y
+ la memoria, se invoca va lnea de comandos usando una serie
+ de opciones y argumentos, este tipo de interfaz reduce al
+ mnimo gastos indirectos y se presta a operaciones escrip-
+ tadas (batch). El uso de CPU y prioridad de memoria por
+ SPLAT! se pueden modificar con el uso de comandos nice
+ Unix.
+
+ El nmero y el tipo de opciones pasados a SPLAT! determinan
+ su modo de operacin y el mtodo de generacin de los datos
+ de salida. Casi todos los opciones de SPLAT! se pueden
+ llamar en cascada y en cualquier orden al invocar el pro-
+ grama desde la lnea de comandos.
+
+ SPLAT! opera en dos modos distintos: modo punto-a-punto, y
+ modo de prediccin del rea de cobertura, y puede ser invo-
+ cado por el usuario usando el modo de lnea de vista (LOS)
+ el modelo de propagacin sobre terreno irregular (ITM)
+ Longley-Rice. El radio de tierra verdadera, cuatro-ter-
+ cios, o cualquier otro radio de la tierra definido-por-el-
+ usuario pueden ser especificados al realizar los anlisis
+ de lnea-de-vista.
+
+ANLISIS PUNTO-A-PUNTO
+ SPLAT! puede ser utilizado para determinar si existe lnea
+ de vista entre dos localizaciones especificadas realizando
+ para ello el anlisis del perfil del terreno. Por ejemplo:
+
+ splat -t tx_site.qth -r rx_site.qth
+
+ invoca un anlisis del perfil del terreno entre el trans-
+ misor especificado en tx_site.qth y el receptor especifi-
+ cado en rx_site.qth y escribe un Reporte de Obstrucciones
+ SPLAT! al directorio de trabajo actual. El reporte con-
+ tiene los detalles de los sitios del transmisor y del
+ receptor, e identifica la localizacin de cualquier
+ obstruccin detectada a lo largo de la trayectoria de lnea-
+ de-vista. Si una obstruccin puede ser despejada levantando
+ la antena de recepcin a una mayor altitud, SPLAT! indicar
+ la altura mnima de la antena requerida para que exista
+ lnea-de-vista entre las localizaciones del transmisor y el
+ receptor especificadas. Observe que las unidades imperi-
+ ales (millas, pies) se usan por defecto, a menos que se
+ use la opcin -metric en la orden SPLAT! de lnea de coman-
+ dos.
+
+ splat -t tx_site.qth -r rx_site.qth -metric
+
+ Si la antena se debe levantar una cantidad significativa,
+ esta determinacin puede tomar una cierta cantidad de
+ tiempo. Observe que los resultados proporcionados son el
+ mnimo necesario para que exista una trayectoria de la
+ lnea-de-vista, y en el caso de este simple ejemplo, no
+ considera los requisitos de la zona de Fresnel.
+
+ Las extensiones qth son asumidas por SPLAT! para los
+ archivos QTH, y son opcionales cuando se especifican los
+ argumentos -t y -r en la lnea de comandos. SPLAT! lee
+ automticamente todos los ficheros de datos de SPLAT nece-
+ sarios para el anlisis del terreno entre los sitios
+ especificados. SPLAT! busca primero los archivos SDF
+ necesarios en el directorio de trabajo actual. Si estos
+ archivos no se encuentran, SPLAT! entonces busca en la
+ ruta especificada por la opcin -d:
+
+ splat -t tx_site -r rx_site -d /cdrom/sdf/
+
+ Una ruta a un directorio externo puede ser especificada
+ creando el archivo ".splat_path" en el directorio de tra-
+ bajo del usuario. Este archivo $HOME/.splat_path debe con-
+ tener una sola lnea de texto ASCII en la que indique la
+ ruta completa del directorio que contiene todos los
+ archivos SDF.
+
+ /opt/splat/sdf/
+
+ Y puede ser generado usando cualquier editor de texto.
+
+ Un grfico que muestre el perfil del terreno en funcin de
+ la distancia, partiendo desde el receptor, entre las
+ localizaciones del transmisor y receptor se puede generar
+ adicionando la opcin -p:
+
+ splat -t tx_site -r rx_site -p terrain_profile.png
+
+ SPLAT! invoca al programa gnuplot cuando genera los grfi-
+ cos. La extensin del nombre del archivo especificado a
+ SPLAT! determina el formato del grfico a ser producido
+ .png generar un archivo de grfico PNG a color con una res-
+ olucin de 640x480, mientras que .ps o .postscript generarn
+ archivos de salida postscritp. La salida en formatos como
+ GIF, Adobe Illustrator, AutoCAD dxf, LaTex, y muchos otros
+ estn disponibles. Por favor consulte gnuplot, y la docu-
+ mentacin de gnuplot para detalles de todos los formatos de
+ salida soportados.
+
+ En el lado del receptor un grfico de elevaciones en
+ funcin de la distancia determinado por el ngulo de incli-
+ nacin debido al terreno entre el receptor y el transmisor
+ se puede generar usando la opcin -e:
+
+ splat -t tx_site -r rx_site -e elevation_profile.png
+
+ El grfico producido usando esta opcin ilustra los ngulos
+ de elevacin y depresin resultado del terreno entre la
+ localizacin del receptor y el sitio del transmisor desde
+ la perspectiva del receptor. Un segundo trazo es dibu-
+ jado entre el lado izquierdo del grfico (localizacin del
+ receptor) y la localizacin de la antena que transmite a la
+ derecha. Este trazo ilustra el ngulo de elevacin
+ requerido para que exista una trayectoria de lnea-de-
+ vista entre el receptor y transmisor. Si la traza inter-
+ seca el perfil de elevacin en cualquier punto del grfico,
+ entonces esto es una indicacin que bajo las condiciones
+ dadas no existe una trayectoria de lnea-de-vista, y las
+ obstrucciones se pueden identificar claramente en el
+ grfico en los puntos de interseccin.
+
+ Un grfico ilustrando la altura del terreno referenciado a
+ la trayectoria de lnea-de-vista entre el transmisor y el
+ receptor se puede generar usando la opcin -h:
+
+ splat -t tx_site -r rx_site -h height_profile.png
+
+ La altura del terreno normalizada a las alturas de las
+ antenas del transmisor y receptor pueden ser obtenidas con
+ la opcin -H:
+
+ splat -t tx_site -r rx_site -H normalized_height_pro-
+ file.png
+
+ El contorno de curvatura de la Tierra tambin es graficada
+ en este modo.
+
+ La primera Zona de Fresnel, y el 60% de la primera Zona de
+ Fresnel puede ser adicionada al grfico de perfiles de
+ altura con la opcin -f, y especificando una frecuencia (en
+ MHz) a la cual la Zona de Fresnel ser modelada:
+
+ splat -t tx_site -r rx_site -f 439.250 -H normal-
+ ized_height_profile.png
+
+ Zonas de despeje de la zona de Fresnel distintas al 60%
+ pueden ser especificadas usando la opcin -fz como sigue:
+
+ splat -t tx_site -r rx_site -f 439.250 -fz 75 -H
+ height_profile2.png
+
+ Un grfico que muestre las prdidas de trayectoria Longley-
+ Rice se puede dibujar usando la opcin -l:
+
+ splat -t tx_site -r rx_site -l path_loss_profile.png
+
+ Como antes, adicionando la opcin -metric se forza al
+ grfico a usar unidades de medida mtrica.
+
+ Al realizar un anlisis punto-a-punto, un reporte SPLAT! de
+ anlisis de trayectoria es generado en la forma de un
+ archivo de texto con una extensin de archivo .txt. El
+ reporte contiene azimut y distancias entre el transmisor y
+ receptor, as mismo cuando se analizan las perdidas por
+ espacio-libre y trayectoria Longley-Rice. El modo de
+ propagacin para la trayectoria est dado como Lnea-de-
+ Vista, Horizonte Simple, Horizonte Doble, Difraccin domi-
+ nante, Troposcatter dominante.
+
+ Distancias y localizaciones para identificar las
+ obtrucciones a lo largo de la trayectoria entre el trans-
+ misor y el receptor tambin se proveen. Si la potencia
+ efectiva radiada del transmisor es especificada en el
+ archivo .lrp del transmisor correspondiente, entonces la
+ prediccin de intensidad de seal y voltaje de antena en la
+ localizacin de recepcin tambin se provee en el reporte de
+ anlisis de trayectoria.
+
+ Para determinar la relacin seal-a-ruido (SNR) en el sitio
+ remoto donde el ruido (trmico) aleatorio de Johnson es el
+ el factor limitante primario en la recepcin:
+
+ SNR=T-NJ-L+G-NF
+
+ donde T es la potencia ERP del transmisor en dBW en la
+ direccin del recedptor, NJ es el ruido de Johnson en dBW
+ (-136 dBW para un canal de TV de 6 MHz), L es las prdidas
+ por trayectoria provistas por SPLAT! en dB (como un nmero
+ positivo), G es la ganancia de la antena receptora en dB
+ referenciada a un radiador isotrpico, y NF es la figura de
+ ruido en el receptor en dB.
+
+ T puede ser computado como sigue:
+
+ T=TI+GT
+
+ donde TI es la cantidad actual de potencia RF entregada a
+ la antena transmisora en dBW, GT es la ganancia de la
+ antena transmisora (referenciada a una isotrpica) en la
+ direccin del receptor ( al horizonte si el receptor est
+ sobre el horizonte).
+
+ Para calcular cuanta mas seal est disponible sobre el
+ mnimo necesario para conseguir una especfica relacin seal-
+ a-ruido:
+
+ Signal_Margin=SNR-S
+
+ donde S es la mnima relacin SNR deseada (15.5 dB para ATSC
+ (8-level VSB) DTV, 42 dB para televisin analgica NTSC).
+
+ Un mapa topogrfico puede ser generado por SPLAT! para
+ visualizar la trayectoria entre el transmisor y el recep-
+ tor desde otra perspectiva. Los mapas topogrficos genera-
+ dos por SPLAT! presentan las elevaciones usando una escala
+ de grises logartmica, con las elevaciones ms altas repre-
+ sentadas a travs de capas ms brillantes de gris. El rango
+ dinmico de la imagen es escalada entre las elevaciones ms
+ altas y ms bajas presentes en el mapa. La nica excepcin de
+ esto es al nivel del mar, el cual se representa usando el
+ color azul.
+
+ La salida topogrfica se puede especificar usando la opcin
+ -o:
+
+ splat -t tx_site -r rx_site -o topo_map.ppm
+
+ La extensin .ppm del archivo de salida es asumida por
+ SPLAT!, y es opcional.
+
+ En este ejemplo, topo_map.ppm ilustrar las localizaciones
+ de los sitios especificados del transmisor y del receptor.
+ Adems, la trayectoria entre los dos sitios ser dibujada
+ sobre las localizaciones para las cuales existe una
+ trayectoria sin obstculo hacia el transmisor con una
+ altura de la antena de recepcin igual a la del sitio del
+ receptor (especificado en rx_site.qth).
+
+ Puede ser deseable poblar el mapa topogrfico con nombres y
+ localizaciones de ciudades, sitios de torres, o de otras
+ localizaciones importantes. Un archivo de ciudades se
+ puede pasar a SPLAT! usando la opcin -s:
+
+ splat -t tx_site -r rx_site -s cities.dat -o topo_map
+
+ Hasta cinco archivos separados pueden ser pasados a SPLAT!
+ a la vez luego de la opcin -s.
+
+ Lmites de estados y ciudades pueden ser adicionados al
+ mapa especificando hasta cinco archivos de lmites cartogr-
+ ficos de Censo Bureu de los U.S. usando la opcin -b:
+
+ splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map
+
+ En situaciones donde mltiples sitios de transmisores estn
+ en uso, se pueden pasar a SPLAT! hasta cuatro localiza-
+ ciones simultneas para sus anlisis:
+
+ splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p
+ profile.png
+
+ En este ejemplo, SPLAT! genera cuatro reportes separados
+ de obstruccin y de perfiles de terreno . Un simple mapa
+ topogrfico puede ser especificado usando la opcin -o, y
+ las trayectorias de lnea de vista entre cada transmisor y
+ el sitio indicado del receptor ser producido en el mapa,
+ cada uno en su propio color. La trayectoria entre el
+ primer transmisor especificado al receptor ser verde, la
+ trayectoria entre el segundo transmisor y el receptor ser
+ cyan, la trayectoria entre el tercer transmisor y el
+ receptor ser violeta, y la trayectoria entre el cuarto
+ transmisor y el receptor ser siena.
+
+ Los mapas topogrficos generados por SPLAT! son imgenes
+ TrueColor PixMap Portables de 24-bit (PPM) y pueden ser
+ vistos, corregidos, o convertidos a otros formatos grficos
+ usando populares programas de imgenes tales como xv, The
+ GIMP, ImageMagick, and XPaint. El formato PNG es alta-
+ mente recomendado para el almacenamiento comprimido sin
+ prdidas de los archivos topogrficos de salida generados
+ por SPLAT!. La utilidad de lnea de comandos ImageMagick's
+ convierte fcilmente los archivos grficos SPLAT! PPM al
+ formato PNG:
+
+ convert splat_map.ppm splat_map.png
+
+ Otra utilidad de de lnea de comandos excelente para con-
+ vertir archivos PPM a PNG es wpng, y est disponible en:
+ http://www.libpng.org/pub/png/book/sources.html. Como
+ recurso adicional, los archivos PPM pueden ser comprimidos
+ usando la utilidad bzip2, y ser ledos directamente en este
+ formato por The GIMP.
+
+ La opcin -ngs asigna a todo el terreno el color blanco, y
+ puede ser usada cuando se quiere generar mapas desprovis-
+ tos de terreno
+
+ splat -t tx_site -r rx_site -b co34_d00.dat -ngs -o
+ white_map
+
+ El archivo imagen .ppm resultante puede ser convertido al
+ formato .png con un fondo transparente usando la utilidad
+ convert de ImageMagick's.
+
+ convert -transparent "#FFFFFF" white_map.ppm transpar-
+ ent_map.png
+
+DETERMINANDO LA COBERTURA REGIONAL
+ SPLAT! puede analizar un sitio de transmisor repetidora,
+ redes de sitios, y predecir la cobertura regional para
+ cada sitio especificado. En este modo SPLAT! puede generar
+ un mapa topogrfico presentando la lnea-de-vista geomtrica
+ del rea de cobertura de los sitios, basados en la local-
+ izacin de cada sitio y la altura de la antena receptora
+ que se desea comunicar con el sitio en cuestin. Un anli-
+ sis regional puede ser realizado por SPLAT! usando la
+ opcin -c como sigue:
+
+ splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o
+ tx_coverage
+
+ En este ejemplo, SPLAT! genera un mapa topogrfico llamado
+ tx_coverage.ppm que ilustra la prediccin de cobertura
+ regional de lnea-de-vista del tx_site a las estaciones
+ receptoras que tienen una antena de 30 pies de altura
+ sobre el nivel del terreno (AGL). Si la opcin -metric es
+ usada, el argumento que sigue a la opcin -c es interpre-
+ tada en metros, en lugar de pies. El contenido de
+ cities.dat son dibujados sobre el mapa, como tambin los
+ lmites cartogrficos contenidos en el archivo co34_d00.dat.
+
+ Cuando se grafica las trayectorias de lnea-de-vista y las
+ reas de cobertura regional, SPLAT! por defecto no consid-
+ era los efectos de la flexin atmosfrica. Sin embargo esta
+ caracterstica puede ser modificada usando el multiplicador
+ de radio de la tierra con la opcin (-m):
+
+ splat -t wnjt-dt -c 30.0 -m 1.333 -s cities.dat -b coun-
+ ties.dat -o map.ppm
+
+ Un radio multiplicador de 1.333 instruye a SPLAT! a usar
+ el modelo de "cuatro-tercios" para el anlisis de propa-
+ gacin de lnea de vista. Cualquier multiplicador del radio
+ de la tierra apropiado puede ser seleccionado por el
+ usuario.
+
+ Cuandorealiza un anlisis regional, SPLAT! genera un
+ reporte para cada estacin analizada. Los reportes de sitio
+ SPLAT! contienen detalles de la localizacin geogrfica del
+ sitio, su altura sobre el nivel del mar, la altura de la
+ antena sobre el promedio del terreno, y la altura del
+ promedio del terreno calculada en las direcciones de los
+ azimut de 0, 45, 90, 135, 180, 225, 270, y 315 grados.
+
+DETERMINANDO MLTIPLES REGIONES DE COBERTURA DE LDV
+ SPLAT! tambin puede presentar reas de cobertura de lnea-
+ de-vista hasta para cuatro sitios de transmisores separa-
+ dos sobre un mapa topogrfico comn. Por ejemplo:
+
+ splat -t site1 site2 site3 site4 -c 10.0 -metric -o net-
+ work.ppm
+
+ Grafica las coberturas regionales de lnea de vista del
+ site1 site2 site3 y site4 basado en una antena receptora
+ localizada a 10.0 metros sobre el nivel del terreno. Un
+ mapa topogrfico entonces es escrito al archivo net-
+ work.ppm. El rea de cobertura de lnea-de-vista del trans-
+ misor es graficada como sigue en los colores indicados
+ (junto con sus valores RGB correspondientes en decimal):
+
+ site1: Green (0,255,0)
+ site2: Cyan (0,255,255)
+ site3: Medium Violet (147,112,219)
+ site4: Sienna 1 (255,130,71)
+
+ site1 + site2: Yellow (255,255,0)
+ site1 + site3: Pink (255,192,203)
+ site1 + site4: Green Yellow (173,255,47)
+ site2 + site3: Orange (255,165,0)
+ site2 + site4: Dark Sea Green 1 (193,255,193)
+ site3 + site4: Dark Turquoise (0,206,209)
+
+ site1 + site2 + site3: Dark Green (0,100,0)
+ site1 + site2 + site4: Blanched Almond (255,235,205)
+ site1 + site3 + site4: Medium Spring Green (0,250,154)
+ site2 + site3 + site4: Tan (210,180,140)
+
+ site1 + site2 + site3 + site4: Gold2 (238,201,0)
+
+
+ Si se generan archivos .qth separados, cada uno represen-
+ tando una localizacin de un sitio comn, pero con difer-
+ entes alturas de antena, SPLAT! puede generar un mapa
+ topogrfico sencillo que ilustra la cobertura regional
+ desde las estaciones (hasta cuatro) separadas por la
+ altura en un nica torre.
+
+ANALISIS DE PRDIDAS POR TRAYECTORIA LONGLEY-RICE
+ Si la opcin -c se reemplaza por la opcin -L, se puede
+ generar un mapa de prdidas de trayectorias Longley-Rice:
+
+ splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o
+ path_loss_map
+
+ En este modo, SPLAT! genera un mapa multicolor que ilustra
+ los niveles de seal esperados (prdidas por trayectoria) en
+ las reas alrededor del transmisor. Una leyenda en la parte
+ inferior del mapa relaciona cada color con sus respectivas
+ prdidas por trayectoria especficas en decibeles intensidad
+ de seal en decibeles sobre un microvoltio por metro
+ (dBuV/m).
+
+ El rango de anlisis Longley-Rice puede modificado a un
+ valor especfico-de-usuario con la opcin -R. El argumento
+ debe ser dado en millas ( kilmetros si la opcin -metric es
+ usada). Si se especifica un rango mayor que el mapa
+ topogrfico generado, SPLAT! realizar los clculos de perdi-
+ das Longley-Rice de trayectoria entre todas las cuatro
+ esquinas del rea del mapa de prediccin.
+
+ La opcin -db permite limitar el mximo de perdidas de la
+ regin a ser graficada en el mapa. Prdidas de trayectoria
+ entre 80 y 230 dB pueden ser especificadas usando esta
+ opcin. Por ejemplo si las perdidas por debajo de -140 dB
+ son irrelevantes al anlisis que se est realizando,
+ entonces las prdidas por trayectoria a ser graficadas por
+ SPLAT! pueden ser limitadas a la regin de atenuacin del
+ contorno de 140 dB como sigue:
+
+ splat -t wnjt-dt -L 30.0 -s cities.dat -b co34_d00.dat -db
+ 140 -o plot.ppm
+
+PARMETROS PARA LA DEFINICIN DE COLOR DEL CONTORNO DE LA SEAL
+ Los colores usados para ilustrar los contornos de
+ intensidad de seal y de prdidas por trayectoria en la gen-
+ eracin de mapas de mapa de cobertura en SPLAT! pueden ser
+ adaptados por el usuario creando o modificando los archivo
+ de definicin de color SPLAT!. Los ardchivos de definicin
+ de color SPLAT! tienen el mismo nombre base que el del
+ archivo .qth del transmisor, pero llevan las extensiones
+ .lcf y .scf.
+
+ Cuando un anlisis regional Longley-Rice es realizado y el
+ ERP del transmisor no se ha especificado es cero, un
+ archivo de definicin de color de prdidas por trayectoria
+ .lcf correspondiente al sitio del transmisor (.qth) es
+ ledo por SPLAT! desde el directorio de trabajo actual. Si
+ el archivo
+ .lcf correspondiente al sitio del transmisor no se
+ encuentra, entonces un archivo por defecto para edicin
+ manual por el usuario es automticamente generado por
+ SPLAT!. Si el ERP del transmisor es especificado, entonces
+ un mapa de intensidad de seal es generado y un archivo de
+ definicin de color de intensidad de seal es ledo, o gener-
+ ado si no est disponible en el directorio de trabajo
+ actual.
+
+ Un archivo de definicin de color de prdidas por trayecto-
+ ria posee la siguiente estructura: (wnjt-dt.lcf):
+
+
+ ; SPLAT! Auto-generated Path-Loss Color Definition
+ ("wnjt-dt.lcf") File
+ ;
+ ; Format for the parameters held in this file is as fol-
+ lows:
+ ;
+ ; dB: red, green, blue
+ ;
+ ; ...where "dB" is the path loss (in dB) and
+ ; "red", "green", and "blue" are the corresponding RGB
+ color
+ ; definitions ranging from 0 to 255 for the region speci-
+ fied.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour
+ regions
+ ; may be defined in this file.
+ ;
+ ;
+ 80: 255, 0, 0
+ 90: 255, 128, 0
+ 100: 255, 165, 0
+ 110: 255, 206, 0
+ 120: 255, 255, 0
+ 130: 184, 255, 0
+ 140: 0, 255, 0
+ 150: 0, 208, 0
+ 160: 0, 196, 196
+ 170: 0, 148, 255
+ 180: 80, 80, 255
+ 190: 0, 38, 255
+ 200: 142, 63, 255
+ 210: 196, 54, 255
+ 220: 255, 0, 255
+ 230: 255, 194, 204
+
+
+ Si la prdida por trayectoria es menor que 80 dB, el color
+ Rojo (RGB = 255, 0, 0) es asignado a la regin. Si la
+ prdida-por-trayectoria es mayor o igual a 80 dB, pero
+ menor que 90 dB, entonces Naranja Oscuro (255, 128, 0) es
+ asignado a la regin. Naranja (255, 165, 0) es asignado a
+ regiones que tienen una prdida por trayectoria mayor o
+ igual a 90 dB, pero menor que 100 dB, y as en adelante. El
+ terreno en escala de grises es presentado por debajo del
+ contorno de prdidas por trayectoria de 230 dB.
+
+ El archivo SPLAT! de definicin de color de intensidad de
+ seal comparte una estructura muy similar. structure
+ (wnjt-dt.scf):
+
+
+ ; SPLAT! Auto-generated Signal Color Definition ("wnjt-
+ dt.scf") File
+ ;
+ ; Format for the parameters held in this file is as fol-
+ lows:
+ ;
+ ; dBuV/m: red, green, blue
+ ;
+ ; ...where "dBuV/m" is the signal strength (in dBuV/m)
+ and
+ ; "red", "green", and "blue" are the corresponding RGB
+ color
+ ; definitions ranging from 0 to 255 for the region speci-
+ fied.
+ ;
+ ; The following parameters may be edited and/or expanded
+ ; for future runs of SPLAT! A total of 32 contour
+ regions
+ ; may be defined in this file.
+ ;
+ ;
+ 128: 255, 0, 0
+ 118: 255, 165, 0
+ 108: 255, 206, 0
+ 98: 255, 255, 0
+ 88: 184, 255, 0
+ 78: 0, 255, 0
+ 68: 0, 208, 0
+ 58: 0, 196, 196
+ 48: 0, 148, 255
+ 38: 80, 80, 255
+ 28: 0, 38, 255
+ 18: 142, 63, 255
+ 8: 140, 0, 128
+
+
+ Si la intensidad de seal es mayor o igual a 128 db sobre 1
+ microvoltio por metro (dBuV/m), el color Rojo (255, 0, 0)
+ es presentado para la regin. Si la intensidad de seal es
+ mayor o igual a 118 dbuV/m, pero menor que 128 dbuV/m,
+ entonces el color naranja (255, 165, 0) es presentado y
+ asi en adelante. El terreno en escala de grises es pre-
+ sentado para regiones con intensidad de seal menores que 8
+ dBuV/m.
+
+ Los contornos de intensidad de seal para algunos servicios
+ de radiodifusin comunes en VHF y UHF en los Estados Unidos
+ son los siguientes:
+
+
+ Analog Television Broadcasting
+ ------------------------------
+ Channels 2-6: City Grade: >= 74 dBuV/m
+ Grade A: >= 68 dBuV/m
+ Grade B: >= 47 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 77 dBuV/m
+ Grade A: >= 71 dBuV/m
+ Grade B: >= 56 dBuV/m
+ --------------------------------------------
+ Channels 14-69: Indoor Grade: >= 94 dBuV/m
+ City Grade: >= 80 dBuV/m
+ Grade A: >= 74 dBuV/m
+ Grade B: >= 64 dBuV/m
+
+ Digital Television Broadcasting
+ -------------------------------
+ Channels 2-6: City Grade: >= 35 dBuV/m
+ Service Threshold: >= 28 dBuV/m
+ --------------------------------------------
+ Channels 7-13: City Grade: >= 43 dBuV/m
+ Service Threshold: >= 36 dBuV/m
+ --------------------------------------------
+ Channels 14-69: City Grade: >= 48 dBuV/m
+ Service Threshold: >= 41 dBuV/m
+
+ NOAA Weather Radio (162.400 - 162.550 MHz)
+ ------------------------------------------
+ Reliable: >= 18 dBuV/m
+ Not reliable: < 18 dBuV/m
+ Unlikely to receive: < 0 dBuV/m
+
+ FM Radio Broadcasting (88.1 - 107.9 MHz)
+ ----------------------------------------
+ Analog Service Contour: 60 dBuV/m
+ Digital Service Contour: 65 dBuV/m
+
+
+
+PARMETROS PARA PATRONES DE RADIACIN DE ANTENAS
+ Los patrones de voltaje de campo normalizado para planos
+ verticales y horizontales de antenas transmisoras son
+ importados automticamente dentro de SPLAT! cuando se real-
+ izan los anlisis de cobertura Longley-Rice. Los datos de
+ los patrones de antena son ledos de un par de archivos que
+ tienen el mismo nombre base que el transmisor y los
+ archivos LRP, pero con extensiones .az y .el, para los
+ patrones de azimut y elevacin respectivamente. Especifica-
+ ciones acerca de la rotacin del patrn (si existe) e incli-
+ nacin mecnica y direccin de la inclinacin (si existe) tam-
+ bin son contenidos dentro de los archivos de patrones de
+ radiacin de las antenas.
+
+ Por ejemplo las primeras pocas lneas de un archivo de
+ patrn de azimut SPLAT! podran aparecer como sigue
+ (kvea.az):
+
+ 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
+
+
+ La primera lnea de el archivo .az especifica la cantidad
+ de rotacin del patrn de azimut (medido en grados desde el
+ norte verdadero en sentido horario) a ser aplicado por
+ SPLAT! a los datos contenidos en el archivo .az. Esto es
+ seguido por el correspondiente azimut (0 a 360 grados) y
+ su asociado patrn de campo normalizado (0.000 a 1.000)
+ separado por un espacio en blanco.
+
+ La estructura del archivo del patrn de elevacin SPLAT! es
+ ligeramente diferente. La primera lnea del archivo .el
+ especifica la cantidad de elevacin mecnica aplicada a la
+ antena. Note que una elevacin hacia abajo (bajo el hori-
+ zonte) es expresada como un ngulo positivo, mientras que
+ hacia arriba (sobre el horizonte) es expresada como un
+ ngulo negativo. Estos datos son seguidos por la direccin
+ del azimut de la elevacin, separado por un espacio en
+ blanco.
+
+ El remanente del archivo consiste en los valores de los
+ ngulos de elevacin y su correspondiente patrn de radiacin
+ de voltaje normalizado (0.000 a 1.000) separados por un
+ espacio en blanco. Los ngulos de elevacin deben ser
+ especificados sobre un rango de -10 a +90 grados. Igual
+ que la notacin en la elevacin mecnica, ngulos de elevacin
+ negativa son usados para representar elevaciones sobre el
+ horizonte,
+ mientras que los ngulos positivos representan elevaciones
+ bajo el horizonte.
+
+ Por ejemplo las primeras pocas lneas de un archivo patrn
+ de elevacin SPLAT! podra aparecer como sigue (kvea.el):
+
+ 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
+
+
+ En este ejemplo, la antena es mecanicamente inclinada
+ hacia abajo 1.1 grados hacia un azimut de 130 grados
+
+ Para mejores resultados, la resolucin de los datos de
+ patrones de radiacin debera ser especificados lo mas cerca
+ posibles a los grados azimut, y la resolucin de datos del
+ patrn de elevacin deveran ser especificados lo mas cerca
+ posible a 0.01 grados. Si los datos del patrn especificado
+ no alcanzan este nivel de resolucin, SPLAT! interpolar los
+ valores provistos para determinar los datos en la resolu-
+ cin requerida, aunque esto puede resultar en una prdida en
+ exactitud.
+
+IMPORTANDO Y EXPORTANDO DATOS DEL CONTORNO REGIONAL DE PRDIDAS
+ POR TRAYECTORIA
+ Realizar un anlisis de cobertura Longley-Rice puede ser un
+ proceso que consume mucho tiempo, especialmente si el
+ anlisis es repetido varias veces para descubrir cuales son
+ los efectos que los cambios a los patrones de radiacin de
+ las antenas hacen a la prediccin del rea de cobertura
+
+ Este proceso puede ser apresurado al exportar los datos
+ del contorno regional de prdidas por trayectoria a un
+ archivo de salida, modificar externamente los datos de
+ prdida por trayectoria para incorporar los efectos de los
+ patrones de antena, y entonces importar nuevamente los
+ datos de prdidas por trayectoria modificados dentro de
+ SPLAT! para rapidamente producir un mapa revisado de prdi-
+ das por trayectoria.
+
+ Por ejemplo un archivo de salida de prdidas por trayecto-
+ ria puede ser generado por SPLAT! para un sitio de
+ recepcin a 30 pies sobre el nivel del terreno, con un
+ radio de 50 millas alrededor del sitio de transmisin para
+ prdidas por trayectoria mximas de 140 dB, usando la sigu-
+ iente sintaxis:
+
+ splat -t kvea -L 30.0 -R 50.0 -db 140 -plo pathloss.dat
+
+ Los archivos de salida por prdidas por trayectoria SPLAT!
+ a menudo exceden los 100 megabytes de tamao. Contienen la
+ informacin referentes a los lmites de la regin que
+ describen seguido por latitudes (grados norte), longitudes
+ (grados oeste), azimut, elevaciones(a la primera obstruc-
+ cin), y figuras de prdidas por trayectoria(dB) para una
+ serie de puntos especficos que abarca la regin que rodea
+ al sitio de transmisin. Las primeras pocas lneas de un
+ archivo de salida de prdidas por trayectoria SPLAT! tiene
+ la siguiente apariencia (pathloss.dat):
+
+
+ 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
+
+
+ No es poco comn para los archivos SPLAT! de prdidas por
+ trayectoria que contengan tanto como 3 millones o ms de
+ lneas de datos. Si el archivo es procesado, comentarios
+ pueden ser puestos con un caracter de punto y coma. El
+ editor de texto vim ha probado ser capaz de editar
+ archivos de este tamao.
+
+ Note que al igual que el caso de los archivos de patrones
+ de antena, ngulos de elevacin negativos se refieren a
+ inclinaciones hacia arriba (sobre el horizonte), mientras
+ que ngulos positivos se refieren a inclinaciones hacia
+ abajo (bajo el horizonte). Esos ngulos se refieren a la
+ elevacin para la antena receptora en la altura sobre el
+ nivel del terreno especificada usando la opcin -L si la
+ trayectoria entre el transmisor y el receptor no tiene
+ obstrucciones. Si la trayectoria entre el transmisor y el
+ receptor est obstruida, entonces el ngulo a la primera
+ obstruccin es retornado por SPLAT!. Esto es porque el
+ modelo Longley-Rice considera la energa que alcanza un
+ punto distante sobre una trayectoria obstruida como un
+ derivado de la energa dispersada de la punta de la primera
+ instruccin, solamente. Puesto que la energa no puede
+ alcanzar directamente la localizacin obstruida, el actual
+ ngulo de elevacin a ese punto es irrelevante.
+
+ Cuando se modifican los archivos SPLAT! de prdidas por
+ trayectoria para reflejar datos de patrones de antena,
+ solo la ltima columna (path loss) deberan ser enmendados
+ para reflejar la ganacia de antena normalizada en los ngu-
+ los de elevacin y azimut especificados en el archivo. (Por
+ ahora, programas y scripts capaces de realizar esta
+ operacin son dejados como tarea al usuario.)
+
+ Los mapas modificados de prdidas por trayectoria pueden
+ ser importados nuevamente a SPLAT! para generar mapas de
+ cobertura revisados.
+
+ splat -t kvea -pli pathloss.dat -s city.dat -b county.dat
+ -o map.ppm
+
+ Los archivos SPLAT! de prdidas por trayectoria tambin
+ pueden ser usados para guiar estudios de cobertura o
+ interferencia fuera de SPLAT!.
+
+ARCHIVOS DE ENTRADA DE TERRENO DEFINIDOS POR EL USUARIO
+ Un archivo de terreno definido por el usuario es un
+ archivo de texto generado-por-el-usuario que contiene lat-
+ itudes, longitudes, y alturas sobre el nivel de la tierra
+ de caractersticas de terreno especfica que se cree son de
+ importancia para el anlisis que SPLAT! est desarrollando,
+ pero perceptiblemente ausentes de los archivos SDF que
+ estn siendo usados. Un archivo de terreno definido-por-el-
+ usuario es importado dentro de un anlisis de SPLAT!
+ usando la opcin -udt:
+
+ splat -t tx_site -r rx_site -udt udt_file.txt -o map.ppm
+
+ Un archivo de terreno definido-por-el-usuario tiene la
+ siguiente apariencia y estructura:
+
+
+ 40.32180556, 74.1325, 100.0 meters
+ 40.321805, 74.1315, 300.0
+ 40.3218055, 74.1305, 100.0 meters
+
+
+ La altura del terreno es interpretada en pies sobre el
+ nivel del suelo a menos que sea seguido por la palabra
+ meters, y es adicionado en la parte superior de el terreno
+ especificado en los datos SDF para la localizacin especi-
+ ficada. Debe saber que las caractersticas especificadas en
+ los archivos de terreno especificados-por-el-usuario sern
+ interpretados como 3-arco segundos en latitud y longitud.
+ Caractersticas descritas en el archivo de terreno
+ definido-por-el-usuario que traslapen las caractersticas
+ previamente definidas en el archivo son ignoradas por
+ SPLAT!.
+
+GENERACIN DE MAPAS TOPOGRFICOS SIMPLES
+ En ciertas ocasiones puede ser deseable generar un mapa
+ topogrfico de una regin sin graficar reas de cobertura,
+ trayectorias de lnea-de-vista, o generar reportes de
+ obstrucciones. Existen varias maneras de hacer esto. Si
+ se desea generar un mapa topogrfico ilustrando la local-
+ izacin de un sitio del transmisor y receptor con un breve
+ reporte de texto describiendo las localizaciones y distan-
+ cias entre los sitios, entonces, entonces se debe invocar
+ la opcin -n como sigue:
+
+ splat -t tx_site -r rx_site -n -o topo_map.ppm
+
+ Si no se desea un reporte de texto, entonces debe usar la
+ opcin -N:
+
+ splat -t tx_site -r rx_site -N -o topo_map.ppm
+
+ Si se desea un mapa topogrfico centrado cerca de un sitio
+ para un radio mnimo especificado, un comando similar al
+ siguiente puede ser utilizado:
+
+ splat -t tx_site -R 50.0 -s NJ_Cities -b NJ_Counties -o
+ topo_map.ppm
+
+ donde -R especifica el mnimo radio de el mapa en millas (
+ kilmetros si la opcin -metric es usada). Note que el nom-
+ bre del sitio_tx y la localizacin no son presentadas en
+ este ejemplo. Si se desea presentar esta informacin, sim-
+ plemente cree un archivo de ciudades SPLAT! con la opcin
+ (-s) y adicinele a las opciones de la lnea-de-comandos
+ ilustradas arriba. Si la opcin -o y el archivo de salida
+ son omitidos en esa operacin, la salida topogrfica es
+ escrita a un archivo por defecto llamado tx_site.ppm en el
+ directorio de trabajo actual.
+
+GENERACIN DE ARCHIVOS DE GEOREFERENCIA
+ Los mapas topogrficos, de cobertura (-c), y contornos de
+ prdidas por trayectoria (-L) generados por SPLAT! pueden
+ ser importados dentro del programa Xastir (X Amateur Sta-
+ tion Tracking and Information Reporting), generando un
+ archivo de georeferencia usando la opcin SPLAT! -geo:
+
+ splat -t kd2bd -R 50.0 -s NJ_Cities -b NJ_Counties -geo -o
+ map.ppm
+
+ El archivo de georeferencia creado tendr el mismo nombre
+ base que el archivo-o especificado, pero con extensin
+ .geo, y permite la apropiada interpretacin y presentacin
+ de los grficos .ppm SPLAT! en el programa Xastir.
+
+GENERACION DE ARCHIVOS KML GOOGLE MAP
+ Archivos Keyhole Markup Language compatibles con Google
+ Earth pueden ser generados por SPLAT! cuando se realizan
+ anlisis punto-a-punto invocando la opcin -kml:
+
+ splat -t wnjt-dt -r kd2bd -kml
+
+ El archivo KML generado tendr la misma estructura que el
+ nombre del Reporte de Obstrucciones para los sitios del
+ transmisor y receptor dados, excepto que tendr una
+ extensin .kml.
+
+ Una vez cargado dentro del Google Earth (Archivo -->
+ Abrir), el archivo KLM exhibir las localizaciones de los
+ sitios de transmisin y recepcin en el mapa. Los puntos de
+ vista de la imagen sern desde la posicin del sitio de
+ transmisin mirando hacia la localizacin del receptor. La
+ trayectoria punto-a-punto entre los sitios ser presentada
+ como una lnea blanca, mientras que la trayectoria de
+ linea-de-vista RF ser presentada en verde. Las herramien-
+ tas de navegacin de Google Earth le permiten al usuario
+ "volar" alrededor de la trayectoria, identificando seales,
+ caminos, y otras caractersticas contenidas.
+
+ Cuando se realiza el anlisis de cobertura regional, el
+ archivo .kml generado por SPLAT! permitir a los contornos
+ de intensidad de seal o de prdidas por trayectoria a ser
+ graficados como capas sobre mapas Google Earth presentados
+ en una manera semi-transparente. El archivo .kml generado
+ tendr el mismo nombre base como el del archivo .ppm nor-
+ malmente generado.
+
+DETERMINACIN DE LA ALTURA DE LA ANTENA SOBRE EL PROMEDIO DEL TER-
+ RENO
+ SPLAT! determina la altura de la antena sobre el promedio
+ del terreno (HAAT) de acuerdo al procedimiento definido
+ por la Comisin Federal de Comunicaciones. Parte 73.313(d).
+ De acuerdo a esta definicin, la elevacin del terreno a lo
+ largo de ocho radiales entre 2 y 16 millas (3 y 16 Kilmet-
+ ros) desde el sitio que est siendo analizado es muestreado
+ y promediado para los azimut cada 45 grados comenzando
+ con el norte verdadero. Si uno o mas radiales caen enter-
+ amente sobre el mar o sobre el continente fuera de los
+ Estados Unidos (reas para las cuales no existen
+ disponibles datos topogrficos USGS), entonces esos radi-
+ ales son omitidos de los clculos del promedio del terreno.
+ Si parte de los radiales se extienden sobre el mar o fuera
+ de los Estados Unidos, entonces solo la parte de esos
+ radiales que caen sobre la tierra de los Estados Unidos
+ son usados en la determinacin del promedio del terreno.
+
+ Note que los datos de elevaciones SRTM, a diferencia de
+ los antiguos datos 3-arcos segundos USGS, se extienden ms
+ all de las fronteras de los Estados Unidos. Por esta razn,
+ los resultados HAAT, no estarn en fiel cumplimiento con
+ la FCC parte 73.313(d) en reas a lo largo de la frontera
+ de los Estados Unidos si los archivos SDF usados por
+ SPLAT! son derivados-SRTM.
+
+ Cuando se realiza anlisis punto-a-punto del terreno,
+ SPLAT! determina la altura de la antena sobre el promedio
+ del terreno solo si suficientes datos topogrficos han
+ sido cargados por el programa para realizar el anlisis
+ punto-a-punto. En la mayora de los casos, esto ser ver-
+ dadero, a menos que el sitio en cuestin no est dentro de
+ 10 millas de la frontera de los datos topogrficos cargados
+ en memoria.
+
+ Cuando se realiza el anlisis de prediccin de rea, sufi-
+ cientes datos topogrficos son normalmente cargados por
+ SPLAT! para realizar los clculos del promedio del terreno.
+ Bajo esas condiciones, SPLAT! proveer la altura de la
+ antena sobre el promedio del terreno, como tambin el
+ promedio del terreno sobre el nivel del mar para los
+ azimut de 0, 45, 90, 135, 180, 225, 270, y 315 grados, e
+ incluir dicha informacin en el reporte de sitio generado.
+ Si uno o ms de los ocho radiales caen sobre el mar o sobre
+ regiones para las cuales no existen datos SDF disponibles,
+ SPLAT! reportar sin terreno la trayectoria de los radi-
+ ales afectados.
+
+RESTRINGIENDO EL TAMAO MXIMO DE UNA REGIN ANALIZADA
+ SPLAT! lee los archivos SDF de acuerdo a sus necesidades
+ dentro de una serie de "pginas" de memoria dentro de la
+ estructura del programa. Cada "pgina" contiene un archivo
+ SDF representando una regin de terreno de un grado por un
+ grado. Una sentencia #define MAXPAGES en las primeras
+ lneas del archivo splat.cpp configura el mximo nmero de
+ "pginas" disponibles para los datos topogrficos. Esto
+ tambin configura el tamao mximo de los mapas generados
+ por SPLAT!. Por defecto MAXPAGES es configurado a 9. Si
+ SPLAT! produce un fallo de segmentacin al arrancar con
+ estos parmetros por defecto, significa que no hay sufi-
+ ciente memoria RAM y/ memoria virtual (particin swap) para
+ correr SPLAT! con este nmero de MAXPAGES. En situaciones
+ donde la memoria disponible es baja, MAXPAGES pueden ser
+ reducidos a 4 con el entendimiento de que esto limitar
+ grandemente la mxima regin que SPLAT! estar habilitado a
+ analizar. Si se tiene disponible 118 megabytes mas de la
+ memoria total (particin swap sumada la RAM), entonces MAX-
+ PAGES puede ser incrementado a 16. esto permitir opera-
+ ciones sobre una regin de 4-grados por 4-grados, lo cual
+ es suficiente para alturas de antenas que excedan los
+ 10,000 pies sobre el nivel del mar, distancias punto-a-
+ punto sobre las 1000 millas.
+
+INFORMACIN ADICIONAL
+ Las ltimas noticias e informacin respecto al programa
+ SPLAT! est disponible a travs de la pgina web oficial
+ localizada en: http://www.qsl.net/kd2bd/splat.html.
+
+AUTORES
+ John A. Magliacane, KD2BD <kd2bd@amsat.org>
+ Creator, Lead Developer
+
+ Doug McDonald <mcdonald@scs.uiuc.edu>
+ Original Longley-Rice Model integration
+
+ Ron Bentley <ronbentley@earthlink.net>
+ Fresnel Zone plotting and clearance determination
+
+
+
+
+KD2BD Software 16 de Septiembre de 2007 SPLAT!(1)
+++ /dev/null
-SPLAT!(1) KD2BD Software SPLAT!(1)
-
-
-NOMBRE
-SPLAT! es una herramienta para el análisis de Propagación de Señales RF, Pérdidas, y características del Terreno (RF Signal Propagation, Loss, And Terrain analysis tool).
-
-
-SINOPSIS
-
-splat [-t txsite(s).qth] [-r rxsite.qth] [-c grafica área(s) de cobertura del TX(s) con una antena RX a X pies sobre el nivel del terreno] [-L altura de la antena receptora para el análisis de cobertura Longley-Rice (pies/metros)(flotante)] [-p perfil_terreno.ext] [-e perfil_elevación.ext] [-h perfil_altura.ext] [-H perfil_altura_normalizada.ext] [-l perfil_Longley-rice.ext] [-o nombrearchivo_mapa_topografico.ppm] [-b nombrearchivo_limites_cartograficos.dat] [-s basedatos_sitio/ciudad.dat] [-d path_directorio_sdf] [-m multiplicador del radio de la tierra (flotante)] [-f frecuencia (MHz) para los cálculos de la zona de Fresnel (flotante)] [-R radio máximo de cobertura (millas/kilómetros) (flotante)] [-dB máximo contorno de atenuación a ser presentado sobre un mapa de pérdidas por trayectoria (80-230 dB)] [-nf no graficar las zonas de Fresnel en los gráficos de altura] [-plo archivosalida_perdidas_por_trayectoria.txt] [-pli archivoentrada_pérdidas_por_trayectoria.txt] [-udt archivo_terreno_definido_por_usuario.txt] [-n] [-N] [-geo] [-kml] [-metric]
-
-
-DESCRIPCIÓN
-SPLAT! es una poderosa herramienta para el análisis de terreno y propagación RF cubriendo el espectro entre 20 Megahertz y 20 Gigahertz. SPLAT! es Software Libre y está diseñado para operar en escritorios Unix y basados en Linux. La redistribución y/ó modificación está permitida bajo los términos de la licencia pública general GNU según lo publicado por la Fundación de Software Libre, versión 2 ó superiores. La adopción del código fuente de SPLAT! en aplicaciones propietarias o de fuente-cerrada es una violación de esta licencia, y esta estrictamente prohibida.
-
-SPLAT! se distribuye con la esperanza de que sea útil, pero SIN NINGUNA GARANTÍA, aún la garantía implícita de COMERCIALIZACIÓN o de la APLICACIÓN PARA UN PROPÓSITO PARTICULAR. Vea la licencia GNU para más detalles.
-
-INTRODUCCIÓN
-Las aplicaciones de SPLAT! incluyen la visualización, diseño, y análisis de enlaces de redes inalámbricas WAN, sistemas de radio comunicaciones comerciales y aficionados sobre los 20 megahertz, enlaces microonda, estudios de interferencia y coordinación de frecuencias, y determinación del contorno de cobertura de las regiones de radio y televisión terrestres análogas y digitales.
-
-SPLAT! proporciona datos de ingeniería RF del sitio, tales como; distancias sobre el arco terrestre y azimut entre sitios de transmisión y recepción, ángulos de elevación de la antena (uptilt), ángulos de depresión (downtilt), altura de la antena sobre nivel del mar, altura de la antena sobre el promedio del terreno, azimut y distancias para determinar obstrucciones, Atenuaciones de trayectoria Longley-Rice , y requisitos mínimos necesarios de altura de las antenas para establecer trayectorias de comunicación de línea-de-vista sin obstrucciones debido al terreno, la primera zona de Fresnel, y el 60% de la primera zona de Fresnel.
-
-SPLAT! produce informes, gráficos, y mapas topográficos altamente detallados y cuidadosamente descritos que presentan las trayectorias de línea-de-vista, contornos regionales de pérdidas por trayectoria para determinar la predicción del área de cobertura de sistemas de transmisores y repetidoras. Al realizar análisis de línea de vista cuando se emplean múltiples sitios de transmisores o repetidores, SPLAT! determina las áreas individuales y mutuas de cobertura dentro de la red especificada.
-
-Simplemente tipee splat en la consola de comandos, esto retornará un resumen de las opciones de comando de SPLAT!
-
- --==[ SPLAT! v1.2.0 Available Options... ]==--
-
- -t txsite(s).qth (sitio de transmisión, max of 4)
- -r rxsite.qth (sitio de recepción)
- -c grafica área(s) de cobertura del TX(s) con una antena RX a X pies sobre el nivel promedio del terreno
- -L grafica las pérdidas por trayectoria desde el sitio de transmisión (TX) y una antena receptora (RX) a X pies/metros sobre el nivel promedio del terreno AGL
- -s nombres de archivos(s) de ciudades/sitios para importar (máximo 5)
- -b nombres de archivos(s) de límites cartográficos para importar (máximo 5)
- -p nombre de archivo para graficar el perfil del terreno
- -e nombre de archivo para graficar la elevación del terreno
- -h nombre de archivo para graficar la altura del terreno
- -H nombre de archivo para graficar la altura normalizada del terreno
- -l nombre de archivo para graficar el modelo Longley-Rice
- -o nombre de archivo para generar el mapa topográfico (.ppm)
- -u nombre del archivo del terreno definido-por-el-usuario a importar
- -d ruta al directorio que contiene los archivos sdf (reemplaza al declarado en el archivo ~/.splat_path)
- -n no analisis, breve reporte
- -N no análisis, no reporte
- -m multiplicador del radio de la tierra
- -f frecuencia para el cálculo de la zona de Fresnel (MHz)
- -R modifica el rango por defecto para -c ó -L (millas/kilómetros)
- -db Contorno máximo de pérdidas a ser presentado en el mapa de pérdidas por trayectoria (80-230 dB)
- -nf no grafica la zona de Fresnel en los gráficos de altura
- -plo nombre del archivo de salida de pérdidas-por-trayectoria
- -pli nombre del archivo de entrada de pérdidas-por-trayectoria
- -udt nombre del archivo de entrada de terreno definido-por-el-usuario
- -geo genera un archivo Xastir de georeferencia .geo (con salida .ppm)
- -kml genera un archivo Google Earth .kml (para enlaces punto-a-punto)
- -metric emplea unidades métricas en lugar de las imperiales para todas las I/O del usuario
-
-
-FICHEROS DE ENTRADA
-SPLAT! es una aplicación manejada por linea de comandos ó terminal de textos (shell), y lee los datos de entrada a través de un número de ficheros de datos. Algunos archivos son obligatorios para la apropiada ejecución del programa, mientras que otros son opcionales. Los archivos obligatorios incluyen los modelos topográficos 3-arco segundo en la forma de archivos de datos de SPLAT (archivos SDF), archivos de localización del sitio (archivos QTH), y archivos de parámetros para el modelo Longley-Rice (archivos LRP). Los archivos opcionales incluyen archivos de localización de ciudades/sitios, archivos de límites cartográficos, archivos de terreno definidos por el usuario, archivos de entrada de pérdidas-por-trayectoria, y archivos de patrones de radiación de antenas.
-
-FICHEROS DE DATOS SPLAT
-SPLAT! importa los datos topográficos desde los ficheros de datos SPLAT (SDFs). Estos archivos se pueden generar desde varias fuentes de información. En los Estados Unidos, los ficheros de datos SPLAT se pueden generar a través de la U.S. Geological Survey Digital Elevation Models (DEMs) usando la herramienta usgs2sdf incluida con SPLAT!. Los modelos de elevación digital USGS compatibles con esta utilidad pueden ser descargados de: http://edcftp.cr.usgs.gov/pub/data/DEM/250/.
-
-Una resolución significativamente mejor se puede obtener con el uso de los modelos digitales de elevación versión 2 SRTM-3. Estos modelos son el resultado de la misión topografíca del radar espacial Shuttle STS-99, y están disponibles para la mayoría de las regiones pobladas de la tierra. Los ficheros de datos SPLAT pueden ser generados desde los datos SRTM usando la herramienta incluida srtm2sdf. Los archivo SRTM-3 versión 2 se pueden obtener a través de FTP anónimo desde: ftp://e0srp01u.ecs.nasa.gov:21/srtm/version2/
-
-A pesar de la exactitud más alta que los datos SRTM ofrecen, existen algunos vacíos en los conjuntos de datos. Cuando se detectan estos vacíos, la utilidad srtm2sdf los substituye por los datos encontrados en los archivos SDF existentes (que presumiblemente fueron creados de datos anteriores de la USGS con la utilidad usgs2sdf). Si los datos SDF, USGS-derivados no están disponibles, los vacíos se reemplazan con el promedio de los pixeles adyacentes, o reemplazo directo.
-
-Los ficheros de datos de SPLAT contienen valores enteros de las elevaciones topográficas (en metros) referidos al nivel del mar para regiones de la tierra de 1-grado por 1-grado con una resolución de 3-arco segundos. Los archivos SDF pueden ser leídos desde el formato estándar (sdf) generado por las utilidades usgs2sdf y srtm2sdf, ó en formato comprimido bzip2 (.sdf .bz2). Puesto que los archivos sin comprimir se pueden procesar ligeramente más rápido que los archivos comprimidos, SPLAT! busca los datos SDF necesarios en formato sin comprimir primero. Si los datos sin comprimir no pueden ser localizados, SPLAT entonces busca los datos en formato comprimido bzip2. Si tampoco se pueden encontrar los archivos SDF comprimidos para la región solicitada, SPLAT! asume que la región es el océano, y asignará una elevación del nivel del mar a estas áreas.
-
-Esta característica de SPLAT! permite realizar el análisis de trayectorias no solamente sobre la tierra, sino también entre las áreas costeras no representadas por los datos del Modelo de Elevación Digital. ¡Este comportamiento de SPLAT! resalta la importancia de tener todos los archivos SDF requeridos para la región a ser analizada, para así obtener resultados significativos.
-
-ARCHIVOS DE LOCALIZACIÓN DEL SITIO (QTH)
-SPLAT! importa la información de la localización de los sitios del transmisor y del receptor analizados por el programa de los archivos ASCII que tienen una extensión .qth. Los archivos QTH contienen:
-
-El nombre del sitio
-La latitud del sitio (positiva al norte del ecuador, negativa al sur)
-La longitud del sitio (en grados oeste W de 0 a 360 grados), y;
-La altura de la antena del sitio sobre el nivel del suelo (AGL).
-
-Un caracter de salto-de-linea separa cada campo. La altura de la antena se asume a ser especificada en pies a menos que sea seguida por la letra m o de la palabra meters en mayúsculas ó minúsculas. La información de la latitud y de la longitud se puede expresar en formato decimal (74.6889) ó en formato grados, minutos, segundos (DMS) (74 41 20.0).
-
-Por ejemplo, un archivo de localización de sitio que describía la estación de televisión WNJT, Trenton, NJ (wnjt.qth) se puede leer como sigue:
-
- WNJT
- 40.2833
- 74.6889
- 990.00
-
-ó en formato de grados, minutos, segundos (DMS) (corazon.qth).
-
-Cerro Corazón
--1 -8 -11.0
-79 03 40
-40 m
-
-Cada sitio de transmisor y receptor analizado por SPLAT! debe ser representado por su propio archivo de la localización de sitio (QTH).
-
-SPLAT! importa los datos de parámetros para el modelo Longley-Rice desde los archivos que tienen el mismo nombre base del archivo QTH del sitio del transmisor, pero con una extensión .lrp proporcionando así una correlación simple y exacta entre estos conjuntos de datos asociados. El formato para los archivos de parámetros para el modelo Longley-Rice es como sigue (wnjt.lrp):
-
-15.000 ; Constante Dieléctrica de la Tierra (Permitividad Relativa)
-0.005 ; Conductividad de la Tierra (Siemens por metro)
-301.000 ; Constante de deflexión Atmosférica (N-unidades)
-700.000 ; Frecuencia en MHz (20 MHz to 20 GHz)
-5 ; Clima de Radio (5 = Continental Templado)
-0 ; Polarización (0 = Horizontal, 1 = Vertical)
-0.5 ; Fracción de situaciones (50% de localizaciones)
-0.5 ; Fracción de tiempo (50% de tiempo)
-
-Si el archivo LRP correspondiente al archivo QTH del sitio de transmisión no puede ser encontrado, SPLAT! explorará el directorio de trabajo actual buscando el archivo "splat.lrp". ¡Si este archivo tampoco puede ser encontrado, entonces los parámetros por defecto enumerados arriba serán asignados por SPLAT! y un archivo correspondiente "splat.lrp" que contiene estos datos será escrito al directorio de trabajo actual. El archivo "splat.lrp" se puede editar de acuerdo a las necesidades del usuario.
-
-Las constantes dieléctricas típicas de la tierra y sus valores de conductividad son los siguientes:
-
- Constante Dieléctrica Conductividad
- Salt water : 80 5.000
- Good ground : 25 0.020
- Fresh water : 80 0.010
- Marshy land : 12 0.007
- Farmland, forest : 15 0.005
- Average ground : 15 0.005
- Mountain, sand : 13 0.002
- City : 5 0.001
- Poor ground : 4 0.001
-
- Los códigos de Clima de Radio usados por SPLAT! son los siguientes:
-
- 1: Equatorial (Congo)
- 2: Continental Subtropical (Sudan)
- 3: Maritime Subtropical (West coast of Africa)
- 4: Desert (Sahara)
- 5: Continental Temperate
- 6: Maritime Temperate, over land (UK and west coasts of US & EU)
- 7: Maritime Temperate, over sea
-
-El clima templado continental es común a las grandes masas de la tierra en la zona templada, tal como los Estados Unidos. Para trayectorias inferiores a 100 kilómetros, es poca diferencia entre los climas templados continentales y marítimos.
-
-Los dos parámetros finales en el archivo .lrp corresponden al análisis estadístico proporcionado por el modelo Longley-Rice. En este ejemplo, SPLAT! devolverá la máxima pérdida de trayectoria que ocurre el 50% del tiempo (fracción del tiempo) en el 50% de las situaciones (fracción de situaciones). En los Estados Unidos utilice una fracción de 0.97 del parámetro de tiempo para televisión digital, y 0.50 para analógica. Se asumen antenas isotrópicas.
-
-Para mayor información de esos parámetros, puede visitar: http://flattop.its.bldrdoc.gov/itm.html y
-http://www.softwright.com/faq/engineering/prop_longley_rice.html
-
-ARCHIVOS DE LOCALIZACIÓN DE CIUDADES
-Los nombres y las localizaciones de ciudades, sitios de la torre, u otros puntos del interés se pueden importar y trazar en los mapas topográficos generados por SPLAT!. SPLAT! importa los nombres de ciudades y localizaciones de los archivos ASCII que contienen:
-
-El nombre de la localización, la latitud de la localización, y la longitud de la localización
-
-Cada campo es separado por una coma. Cada expediente es separado por un caracter de salto-de-linea. Al igual que con los archivos .qth, la información de la latitud y la longitud se puede ingresar en formato decimal ó en formato de grados, minutos, segundos (DMS).
-
-Por ejemplo en formato decimal (cities.dat):
-
-Teaneck, 40.891973, 74.014506
-Tenafly, 40.919212, 73.955892
-Teterboro, 40.859511, 74.058908
-Tinton Falls, 40.279966, 74.093924
-Toms River, 39.977777, 74.183580
-Totowa, 40.906160, 74.223310
-Trenton, 40.219922, 74.754665
-
-
-Un total de cinco ficheros de datos separados de ciudades se pueden importar a la vez, y no hay límite al tamaño de estos archivos. SPLAT! lee datos de las ciudades en base a "primero ingresada primero servida", y traza solamente las localizaciones cuyas anotaciones no estén en conflicto con anotaciones de las localizaciones trazadas anteriormente durante la ejecución de SPLAT!. Este comportamiento en SPLAT! reduce al mínimo el alboroto al generar los mapas topográficos, pero también determina que por mandato las localizaciones importantes estén puestas al principio del primer fichero de datos de ciudades, y las localizaciones de menor importancia sean colocadas a continuación en la lista o en los ficheros de datos subsecuentes.
-
-Los ficheros de datos de las ciudades se pueden generar manualmente usando cualquier editor de textos, importar de otras fuentes, o derivar de los datos disponibles de la oficina de censo de los Estados Unidos, usando la herramienta incluida con SPLAT! citydecoder. Estos datos están disponibles gratuitamente vía Internet en: http://www.census.gov/geo/www/cob/bdy_files.html, y deben estar en formato ASCII.
-
-
-ARCHIVOS DE DATOS DE LIMITES CARTOGRÁFICOS
-Los datos cartográficos de límites se pueden también importar para trazar los límites de las ciudades, condados, o estados en los mapas topográficos generados por SPLAT!. Estos datos deben estar en el formato de metadatos de archivos cartográficos de límites ARC/INFO Ungenerate (formato ASCII), y están disponibles para los E.E.U.U..en la Oficina de Censos vía Internet en: http://www.census.gov/geo/www/cob/co2000.html#ascii y http://www.census.gov/geo/www/cob/pl2000.html#ascii. Un total de cinco archivos cartográficos separados de límites se puede importar a la vez. No es necesario importar límites de estado si ya se han importado los límites del condado.
-
-OPERACIÓN DEL PROGRAMA
-Debido a que SPLAT! hace un uso intensivo del CPU y la memoria, SPLAT! se invoca vía línea de comandos usando una serie de opciones y argumentos, este tipo de interfaz reduce al mínimo gastos indirectos y se presta a operaciones escriptadas. El uso de CPU y memoria por SPLAT! se pueden modificar con el uso de comandos Unix.
-
-El número y el tipo de opciones pasados a SPLAT! determinan su modo de operación y el método de generación de los datos de salida. Casi todos los opciones de SPLAT! se pueden conectar en cascada y en cualquier orden al invocar el programa desde la línea de comandos.
-
-SPLAT! funciona en dos modos distintos: modo punto-a-punto, y modo de predicción del área de cobertura, y puede ser invocado por el usuario usando el modo de línea de vista (LOS) ó el modelo Longley-Rice de propagación sobre terreno irregular (ITM).
-
-El radio de tierra verdadera, cuatro-tercios, o cualquier otro radio de la tierra pueden ser especificados al realizar los análisis de línea-de-vista.
-
-
-ANÁLISIS PUNTO-A-PUNTO
-SPLAT! puede ser utilizado para determinar si existe línea de vista entre dos localizaciones especificadas realizando para ello el análisis del perfil del terreno. Por ejemplo:
-
-splat -t tx_site.qth -r rx_site.qth
-
-invoca un análisis del perfil del terreno entre el transmisor especificado en tx_site.qth y el receptor especificado en rx_site.qth, y escribe un Reporte de Obstrucciones SPLAT! al directorio de trabajo actual. El reporte contiene los detalles de los sitios del transmisor y del receptor, e identifica la localización de cualquier obstrucción detectada a lo largo de la trayectoria de línea-de-vista. Si una obstrucción puede ser despejada levantando la antena de recepción a una mayor altitud, SPLAT! indicará la altura mínima de la antena requerida para que exista línea-de-vista entre las localizaciones del transmisor y el receptor especificadas. Observe que las unidades imperiales (millas, pies) se usan por defecto, a menos que se use la opción -metric en la orden SPLAT! de línea de comandos.
-
-splat -t tx_site.qth -r rx_site.qth -metric
-
-Si la antena se debe levantar una cantidad significativa, esta determinación puede tomar una cierta cantidad de tiempo. Observe que los resultados proporcionados son el mínimo necesario para que exista una trayectoria de la línea de vista, y en el caso de este simple ejemplo, no considera los requisitos de la zona de Fresnel.
-
-Las extensiones .qth son asumidas por SPLAT! para los archivos QTH, y son opcionales al invocar el programa. ¡SPLAT! lee automáticamente todos los ficheros de datos de SPLAT necesarios para el análisis del terreno entre los sitios especificados. SPLAT! busca primero los archivos SDF necesarios en el directorio de trabajo actual. Si estos archivos no se encuentran, SPLAT! entonces busca en la ruta especificada por la opción – d:
-
-splat -t tx_site -r rx_site -d /cdrom/sdf/
-
-Una ruta a un directorio externo puede ser especificada creando el archivo ".splat_path" en el directorio de trabajo del usuario. Este archivo $HOME/.splat_path debe contener una sola línea de texto ASCII en la que indique la ruta completa del directorio que contiene todos los archivos SDF.
-
-/opt/splat/sdf/
-
-Y puede ser generado usando cualquier editor de texto.
-
-Un gráfico que muestre el perfil del terreno en función de la distancia, partiendo desde el receptor, entre las localizaciones del transmisor y receptor se puede generar adicionando la opción -p:
-
- splat -t tx_site -r rx_site -p terrain_profile.png
-
-SPLAT! invoca al programa gnuplot cuando genera los gráficos. La extensión del nombre del archivo especificado por SPLAT! determina el formato del gráfico a ser producido .png generará un archivo de gráfico PNG a color con una resolución de 640x480, mientras que .ps o .postscript generarán archivos de salida postscritp. La salida en formatos como GIF, Adobe Illustrator, AutoCAD dxf, LaTex, y muchos otros están disponibles. Por favor consulte gnuplot, y la documentación de gnuplot para detalles de todos los formatos de salida soportados.
-
-En el lado del receptor un gráfico de elevaciones en función de la distancia determinado por el ángulo de inclinación debido al terreno entre el receptor y el transmisor se puede generar usando la opción -e:
-
-splat -t tx_site -r rx_site -e elevation_profile.png
-
-El gráfico producido usando la opción -e ilustra los ángulos de elevación y depresión resultado del terreno entre la localización del receptor y el sitio del transmisor desde la perspectiva del receptor. Un segundo trazo es dibujado entre el lado izquierdo del gráfico (localización del receptor) y la localización de la antena que transmite a la derecha. Este trazo ilustra el ángulo de elevación requerido para que exista una trayectoria de línea de vista entre el receptor y transmisor. Si la traza interseca el perfil de elevación en cualquier punto del gráfico, entonces esto es una indicación que bajo las condiciones dadas no existe una trayectoria de línea-de-vista, y las obstrucciones se pueden identificar claramente en el gráfico en los puntos de intersección.
-
-Un gráfico ilustrando la altura del terreno referenciado a la trayectoria de línea de vista entre el transmisor y el receptor se puede generar usando la opción -h:
-
-splat -t tx_site -r rx_site -h height_profile.png
-
-La altura del terreno normalizada a las alturas de las antenas del transmisor y receptor pueden ser obtenidas con la opción -H:
-
-splat -t tx_site -r rx_site -H normalized_height_profile.png
-
-El contorno de curvatura de la tierra también es graficada en este modo.
-
-La primera Zona de Fresnel, y el 60% de la primera Zona de Fresnel puede ser adicionada al gráfico de perfiles de altura con la opción -f, y especificando una frecuencia (en MHz) a la cual la Zona de Fresnel será modelada:
-
-splat ‐t tx_site ‐r rx_site ‐f 439.250 ‐H normalized_height_profile.png
-
-
-Un gráfico que muestre las pérdidas de trayectoria Longley-Rice se puede dibujar usando la opción -l :
-
-splat -t tx_site -r rx_site -l path_loss_profile.png
-
-Como antes, adicionando la opción -metric se forza al gráfico a usar unidades de medida métrica.
-
-Al realizar el perfil de las pérdida de trayectoria, un Reporte de las Pérdidas por Trayectoria del Modelo Longley-Rice es generado por SPLAT! en un archivo de texto con extensión .lro . El informe contiene el azimut y las distancias entre el transmisor y el receptor, así como la pérdida de trayectoria Longley-Rice para varias distancias entre el transmisor y el receptor. El modo de propagación para los puntos a lo largo de la trayectoria se da como Línea-de-Vista, Horizonte Simple, Horizonte Doble, Difracción dominante, y Troposcatter dominante.
-
-Para determinar la relación señal-a-ruido (SNR) en el sitio remoto donde el ruido (térmico) aleatorio de Johnson es el el factor limitante primario en la recepción:
-
- SNR=T-NJ-L+G-NF
-
-donde T es la potencia ERP del transmisor en dBW, NJ es el ruido de Johnson en dBW (-136 dBW para un canal de TV de 6 Mhz), L es las pérdidas de trayectoria proporcionadas por SPLAT! en dB (como un número positivo), G es la ganancia de la antena receptora en dB referenciada a un radiador isotrópico, y NF es la figura de ruido en el receptor en dB.
-
-T puede ser computado como sigue:
-
-T=TI+GT
-
-donde TI es la cantidad actual de potencia RF entregada a la antena transmisora en dBW, GT es la ganancia de la antena transmisora (referenciada a una isotrópica) en la dirección del receptor (ó al horizonte si el receptor está sobre el horizonte.
-
-Para calcular cuanta mas señal está disponible sobre el mínimo necesario para conseguir una específica relación señal-a-ruido:
-
-Signal_Margin=SNR-S
-
-donde S es la mínima relación SNR deseada (15.5 dB para ATSC DTV, 42 dB para televisión analógica NTSC).
-
-Un mapa topográfico puede ser generado por SPLAT! para visualizar la trayectoria entre el transmisor y el receptor desde otra perspectiva. Los mapas topográficos generados por SPLAT! presenta las elevaciones usando una escala de grises logarítmica, con las elevaciones más altas representadas a través de capas más brillantes de gris. El rango dinámico de la imagen es escalada entre las elevaciones más altas y más bajas presentes en el mapa. La única excepción de esto es al nivel del mar, el cual se representa usando el color azul.
-
-La salida topográfica se puede especificar usando la opción -o :
-
-splat -t tx_site -r rx_site -o topo_map.ppm
-
-La extensión .ppm del archivo de salida es asumida por SPLAT!, y es opcional.
-
-En este ejemplo, topo_map.ppm ilustrará las localizaciones de los sitios especificados del transmisor y del receptor. Además, la trayectoria entre los dos sitios será dibujada sobre las localizaciones para las cuales existe una trayectoria sin obstáculo hacia el transmisor con una altura de la antena de recepción igual a la del sitio del receptor (especificado en rx_site.qth).
-
-Puede ser deseable poblar el mapa topográfico con nombres y localizaciones de ciudades, sitios de torres, o de otras localizaciones importantes. ¡Un archivo de ciudades se puede pasar a SPLAT! usando la opción -s :
-
-splat -t tx_site -r rx_site -s cities.dat -o topo_map
-
-Hasta cinco archivos separados pueden ser pasados a SPLAT! a la vez luego de la opción -s .
-
-Límites de estados y ciudades pueden ser adicionados al mapa especificando hasta cinco archivos de límites cartográficos de Censo Bureu de los U.S. usando el switch -b :
-
-splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map
-
-En situaciones donde múltiples sitios de transmisores están en uso, se pueden pasar a SPLAT! hasta cuatro localizaciones simultáneas para sus análisis:
-
-splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p profile.png
-
-En este ejemplo, SPLAT! genera cuatro reportes separados de obstrucción y de perfiles de terreno . Un simple mapa topográfico puede ser especificado usando la opción -o , y las trayectorias de línea de vista entre cada transmisor y el sitio indicado del receptor será producido en el mapa, cada uno en su propio color. La trayectoria entre el primer transmisor especificado al receptor será verde, la trayectoria entre el segundo transmisor y el receptor será cyan, la trayectoria entre el tercer transmisor y el receptor será violeta, y la trayectoria entre el cuarto transmisor y el receptor será siena.
-
-Los mapas topográficos generados por SPLAT! son imágenes TrueColor PixMap Portables de 24-bit (PPM) y pueden ser vistos, corregidos, o convertidos a otros formatos gráficos usando populares programas de imágenes tales como xv, The GIMP, ImageMagick, y XPaint. El formato png es altamente recomendado para el almacenamiento comprimido sin pérdidas de los archivos topográficos de salida generados por SPLAT!. La utilidad de línea de comandos ImageMagick's convierte fácilmente los archivos gráficos SPLAT! PPM al formato PNG:
-
-convert splat_map.ppm splat_map.png
-
-Otra utilidad de de línea de comandos excelente para convertir archivos PPM a PNG es wpng, y está disponible en: http://www.libpng.org/pub/png/book/sources.html . Como recurso adicional, los archivos PPM pueden ser comprimidos usando la utilidad bzip2, y ser leídos directamente en este formato por The GIMP.
-
-DETERMINANDO LA COBERTURA REGIONAL
-SPLAT! puede analizar un sitio de transmisor o repetidora, ó redes de sitios, y predecir la cobertura regional para cada sitio especificado. En este modo SPLAT! puede generar un mapa topográfico presentando la geometría del área de cobertura de línea de vista de los sitios, basados en la localización de cada sitio y la altura de la antena receptora que se desea comunicar con el sitio en cuestión. SPLAT! se swichea desde el modo de análisis punto-a-punto al modo de predicción de cobertura cuando se invoca la opción -c como sigue:
-
-splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o tx_coverage
-
-En este ejemplo, SPLAT! genera un mapa topográfico llamado tx_coverage.ppm que ilustra la predicción de cobertura regional de línea de vista del tx_site a las estaciones receptoras que tienen una antena de 30 pies de altura sobre el nivel del terreno (AGL). Si la opción -metric es usada, el argumento que sigue a la opción -c es interpretada en metros, en lugar de pies. El contenido de cities.dat son dibujados sobre el mapa, como también los límites cartográficos contenidos en el archivo co34_d00.dat .
-
-Cuando se grafica las trayectorias de línea-de-vista y las áreas de cobertura regional, SPLAT! por defecto no considera los efectos de la flexión atmosférica. Sin embargo esta característica puede ser modificada usando el multiplicador de radio de la tierra con la opción -m .
-
-splat -t wnjt -c 30.0 -m 1.333 -s cities.dat -b counties.dat -o map.ppm
-
-Un radio multiplicador de 1.333 instruye a SPLAT! a usar el modelo de “cuatro-tercios” para el análisis de propagación de línea de vista. Cualquier multiplicador del radio de la tierra apropiado puede ser seleccionado por el usuario.
-
-Cuando SPLAT! es invocado en el modo de predicción de cobertura, genera un reporte para cada estación analizada. Los reportes de sitio SPLAT! contienen detalles de la localización geográfica del sitio, su altura sobre el nivel del mar, la altura de la antena sobre el promedio del terreno, y la altura del promedio del terreno calculada en las direcciones de los azimut de 0, 45, 90, 135, 180, 225, 270, y 315 grados.
-
-
-DETERMINANDO REGIONES MÚLTIPLES DE COBERTURA
-SPLAT! también puede presentar áreas de cobertura de línea-de-vista hasta para cuatro sitios de transmisores separados sobre un mapa topográfico común. Por ejemplo:
-
-splat -t site1 site2 site3 site4 -c 10.0 -metric -o network.ppm
-
-Grafica las coberturas regionales de línea de vista del site1 site2 site3 site4 basado en una antena receptora localizada a 10.0 metros sobre el nivel del terreno. Un mapa topográfico entonces es escrito al archivo network.ppm . El área de cobertura de línea de vista del transmisor es graficada como sigue en los colores indicados junto con sus valores RGB correspondientes en decimal.
-
- site1: Green (0,255,0)
- site2: Cyan (0,255,255)
- site3: Medium Violet (147,112,219)
- site4: Sienna 1 (255,130,71)
-
- site1 + site2: Yellow (255,255,0)
- site1 + site3: Pink (255,192,203)
- site1 + site4: Green Yellow (173,255,47)
- site2 + site3: Orange (255,165,0)
- site2 + site4: Dark Sea Green 1 (193,255,193)
- site3 + site4: Dark Turquoise (0,206,209)
-
- site1 + site2 + site3: Dark Green (0,100,0)
- site1 + site2 + site4: Blanched Almond (255,235,205)
- site1 + site3 + site4: Medium Spring Green (0,250,154)
- site2 + site3 + site4: Tan (210,180,140)
-
- site1 + site2 + site3 + site4: Gold2 (238,201,0)
-
-Si se generan archivos .qth separados, cada uno representando una localización de un sitio común, pero con diferentes alturas de antena, SPLAT! puede generar un mapa topográfico sencillo que ilustra la cobertura regional desde las estaciones (hasta cuatro) separadas por la altura en un única torre.
-
-
-ANALISIS DE PÉRDIDAS POR TRAYECTORIA LONGLEY-RICE
-Si la opción -c se reemplaza por la opción -L, se puede generar un mapa de pérdidas de trayectorias Longley-Rice:
-
-splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -o path_loss_map
-
-En este modo, SPLAT! genera un mapa multicolor que ilustra los niveles de señal esperados (pérdidas por trayectoria) en las áreas alrededor del transmisor. Una leyenda en la parte inferior del mapa relaciona cada color con sus respectivas pérdidas por trayectoria específicas en decibeles.
-
-El rango de análisis puede modificado con la opción -R . El argumento debe ser dado en millas (ó kilómetros si la opción -metric es usada). Si se especifica un rango mayor que el mapa topográfico generado, SPLAT! realizará los cálculos de perdidas Longley-Rice de trayectoria entre todas las cuatro esquinas del área del mapa de predicción.
-
-La opción -db permite limitar el máximo de perdidas de la región a ser graficada en el mapa. Pérdidas de trayectoria entre 80 y 230 dB pueden ser especificadas usando esta opción. Por ejemplo si las perdidas por debajo de -140 dB son irrelevantes al análisis que se está realizando, entonces las pérdidas a ser graficadas por SPLAT! pueden ser limitadas a la región de atenuación del contorno de 140 dB como sigue:
-
-splat -t wnjt -L 30.0 -s cities.dat -b co34_d00.dat -db 140 -o plot.ppm
-
-
-PARÁMETROS PARA PATRONES DE RADIACIÓN DE ANTENAS
-Los patrones de voltaje de campo normalizado para planos verticales y horizontales de antenas transmisoras son importados automáticamente dentro de SPLAT! cuando se realizan los análisis de cobertura Longley-Rice. Los datos de los patrones de antena son leídos de un par de archivos que tienen el mismo nombre base que el transmisor y los archivos LRP, pero con extensiones .az y .el, para los patrones de azimut y elevación respectivamente. Especificaciones acerca de la rotación del patrón (si existe) e inclinación mecánica y dirección de la inclinación (si existe) también son contenidos dentro de los archivos de patrones de radiación de las antenas.
-
-Por ejemplo las primeras pocas líneas de un archivo de patrón de azimut SPLAT! podrían aparece como sigue (kvea.az):
-
- 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
-
-La primera línea de el archivo .az especifica la cantidad de rotación del patrón de azimut (medido en grados desde el norte verdadero en sentido horario) a ser aplicado por SPLAT! a los datos contenidos en el archivo .az . Esto es seguido por el correspondiente azimut (0 a 360 grados) y su asociado patrón de campo normalizado (0.000 a 1.000) separado por un espacio en blanco.
-
-La estructura del archivo del patrón de elevación SPLAT! es ligeramente diferente. La primera línea del archivo .el especifica la cantidad de elevación mecánica aplicada a la antena. Note que una elevación hacia abajo (bajo el horizonte) es expresada como un ańgulo positivo, mientras que hacia arriba (sobre el horizonte) es expresada como un ángulo negativo. Estos datos son seguidos por la dirección del azimut de la elevación, separado por un espacio en blanco.
-
-El remanente del archivo consiste en los valores de los ángulos de elevación y su correspondiente patrón de radiación de voltaje normalizado (0.000 a 1.000) separados por un espacio en blanco. Los ángulos de elevación deben ser especificados sobre un rango de -10 a +90 grados. Igual que la notación en la elevación mecánica, ángulos de elevación negativa son usados para representar elevaciones sobre el horizonte, mientras que los ángulos positivos representan elevaciones bajo el horizonte.
-
-Por ejemplo las primeras pocas líneas de un archivo patrón de elevación SPLAT! podría aparecer como sigue (kvea.el):
-
- 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
-
-En este ejemplo, la antena es mecanicamente inclinada hacia abajo 1.1 grados hacia un azimut de 130 grados
-
-Para mejores resultados, la resolución de los datos de patrones de radiación debería ser especificados lo mas cerca posibles a los grados azimut, y la resolución de datos del patrón de elevación deverían ser especificados lo mas cerca posible a 0.01 grados. Si los datos del patrón especificado no alcanzan este nivel de resolución, SPLAT! interpolará los valores provistos para determinar los datos en la resolución requerida, aunque esto puede resultar en una pérdida en exactitud.
-
-
-IMPORTANDO Y EXPORTANDO DATOS DEL CONTORNO REGIONAL DE PÉRDIDAS POR TRAYECTORIA
-
-Realizar un análisis de cobertura Longley-Rice puede ser un proceso que consuma mucho tiempo, especialmente si el análisis es repetido varias veces para descubrir cuales son los efectos que los cambios a los patrones de radiación de las antenas hacen a la predicción del área de cobertura
-
-Este proceso puede ser apresurado al exportar los datos del contorno regional de pérdidas por trayectoria a un archivo de salida, modificar externamente los datos de pérdida por trayectoria para incorporar los efectos de los patrones de antena, y entonces importar nuevamente los datos de pérdidas por trayectoria modificados dentro de SPLAT! para rapidamente producir un mapa revisado de pérdidas por trayectoria.
-
-Por ejemplo un archivo de salida de pérdidas por trayectoria puede ser generado por SPLAT! para un sitio de recepción a 30 pies sobre el nivel del terreno, con un radio de 50 millas alrededor del sitio de transmisión para pérdidas por trayectoria máximas de 140 dB, usando la siguiente sintaxis:
-
- splat ‐t kvea ‐L 30.0 ‐R 50.0 ‐db 140 ‐plo pathloss.dat
-
-Los archivos de salida por pérdidas por trayectoria a menudo exceden los 100 megabytes de tamaño. Contienen la información referentes a los límites de la región que describen seguido por latitudes (grados norte), longitudes(grados oeste), azimut, elevaciones(a la primera obstrucción), y figuras de pérdidas por trayectoria(dB) para una serie de puntos específicos que abarca la región que rodea al sitio de transmisión. Las primeras pocas líneas de un archivo de salida de pérdidas por trayectoria SPLAT! tiene la siguiente apariencia (pathloss.dat):
-
- 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
-
-
-No es poco común para los archivos SPLAT! de pérdidas por trayectoria que contengan tanto como 3 millones o más de líneas de datos. Si el archivo es procesado, comentarios pueden ser puestos con un caracter de punto y coma. El editor de texto vim ha probado ser capaz de editar archivos de este tamaño.
-
-Note que al igual que el caso de los archivos de patrones de antena, ángulos de elevación negativos se refieren a inclinaciones hacia arriba (sobre el horizonte), mientras que ángulos positivos se refieren a inclinaciones hacia abajo (bajo el horizonte). Esos ángulos se refieren a la elevación para la antena receptora en la altura sobre el nivel del terreno especificada usando la opción -L si la trayectoria entre el transmisor y el receptor no tiene obstrucciones. Si la trayectoria entre el transmisor y el receptor está obstruida, entonces el ángulo a la primera obstrucción es retornado por SPLAT!. Esto es porque el modelo Longley-Rice considera la energía que alcanza un punto distante sobre una trayectoria obstruida como un derivado de la energía dispersada de la punta de la primera instrucción, solamente. Puesto que la energía no puede alcanzar directamente la localización obstruida, el actual ángulo de elevación a ese punto es irrelevante.
-
-Cuando se modifican los archivos SPLAT! de pérdidas por trayectoria para reflejar datos de patrones de antena, solo la última columna (path loss) deberían ser enmendados para reflejar la ganacia de antena normalizada en los ángulos de elevación y azimut especificados en el archivo. (Por ahora, programas y scripts capaces de realizar esta operación son dejados como tarea al usuario.)
-
-Los mapas modificados de pérdidas por trayectoria pueden ser importados nuevamente a SPLAT! para generar mapas de cobertura revisados.
-
-splat ‐t kvea ‐pli pathloss.dat ‐s city.dat ‐b county.dat ‐o map.ppm
-
-Los archivos SPLAT! de pérdidas por trayectoria también pueden ser usados para guiar estudios de cobertura o interferencia fuera de SPLAT!
-
-ARCHIVOS DE ENTRADA DE TERRENO DEFINIDOS POR EL USUARIO
-Un archivo de terreno definido por el usuario es un archivo de texto generado-por-el-usuario que contiene latitudes, longitudes, y alturas sobre el nivel de la tierra de características de terreno específica que se cree son de importancia para el análisis que SPLAT! está desarrollando, pero perceptiblemente ausentes de los archivos SDF que están siendo usados. Un archivo de terreno definido-por-el-usuario es importado dentro de un análisis de SPLAT! usando la opción -udt :
-
-splat ‐t tx_site ‐r rx_site ‐udt udt_file.txt ‐o map.ppm
-
-Un archivo de terreno definido-por-el-usuario tiene la siguiente apariencia y estructura:
-
- 40.32180556, 74.1325, 100.0 meters
- 40.321805, 74.1315, 300.0
- 40.3218055, 74.1305, 100.0 meters
-
-La altura del terreno es interpretada en pies sobre el nivel del suelo a menos que sea seguido por la palabra meters, y es adicionado en la parte superior de el terreno especificado en los datos SDF para la localización especificada.
-
-Debe saber que las características especificadas en los archivos de terreno especificados-por-el-usuario serán interpretados como 3-arco segundos en latitud y longitud. Características descritas en el archivo de terreno definido-por-el-usuario que traslapen las características previamente definidas en el archivo son ignoradas por SPLAT!
-
-GENERACIÓN DE MAPAS TOPOGRÁFICOS SIMPLES
-En ciertas ocasiones puede ser deseable generar un mapa topográfico de una región sin graficar áreas de cobertura, trayectorias de línea-de-vista, o generar reportes de obstrucciones. Existen varias maneras de hacer esto. Si se desea generar un mapa topográfico ilustrando la localización de un sitio del transmisor y receptor con un breve reporte de texto describiendo las localizaciones y distancias entre los sitios, entonces, entonces se debe invocar la opción -n como sigue:
-
-splat -t tx_site -r rx_site -n -o topo_map.ppm
-
-Si no se desea un reporte de texto, entonces debe usar la opción -N :
-
-splat -t tx_site -r rx_site -N -o topo_map.ppm
-
-Si se omite la opción -o y el nombre del archivo de salida cuando se usan las opciones -n ó -N , la salida será escrita a un archivo por defecto llamado map.ppm en el directorio actual de trabajo.
-
-DETERMINACIÓN DE LA ALTURA DE LA ANTENA SOBRE EL PROMEDIO DEL TERRENO
-SPLAT! determina la altura de la antena sobre el promedio del terreno (HAAT) de acuerdo al procedimiento definido por la Comisión Federal de Comunicaciones. Parte 73.313(d). De acuerdo a esta definición, la elevación del terreno a lo largo de ocho radiales entre 2 y 16 millas (3 y 16 Kilómetros) desde el sitio que está siendo analizado es muestreado y promediado para los azimut cada 45 grados comenzando con el norte verdadero. Si uno o mas radiales caen enteramente sobre el mar o sobre el continente fuera de los Estados Unidos (áreas para las cuales no existen disponibles datos topográficos USGS), entonces esos radiales son omitidos de los cálculos del promedio del terreno. Si parte de los radiales se extienden sobre el mar o fuera de los Estados Unidos, entonces solo la parte de esos radiales que caen sobre la tierra de los Estados Unidos son usados en la determinación del promedio del terreno.
-
-Note que los datos de elevaciones SRTM, a diferencia de los antiguos datos 3-arcos segundos USGS, se extienden más allá de las fronteras de los Estados Unidos. Por esta razón, los resultados HAAT, no estarán en fiel cumplimiento con la FCC parte 73.313(d) en áreas a lo largo de la frontera de los Estados Unidos si los archivos SDF usados por SPLAT! son derivados-SRTM.
-
-Cuando se realiza análisis punto-a-punto del terreno, SPLAT! determina la altura de la antena sobre el promedio del terreno solo si suficientes datos topográficos han sido cargados por el programa para realizar el análisis punto-a-punto. En la mayoría de los casos, esto será verdadero, a menos que el sitio en cuestión no esté dentro de 10 millas de la frontera de los datos topográficos cargados en memoria.
-
-Cuando se realiza el análisis de predicción de área, suficientes datos topográficos son normalmente cargados por SPLAT! para realizar los cálculos del promedio del terreno. Bajo esas condiciones, SPLAT! proveerá la altura de la antena sobre el promedio del terreno, como también el promedio del terreno sobre el nivel del mar para los azimut de 0, 45, 90, 135, 180, 225, 270, y 315 grados, e incluirá dicha información en el reporte de sitio generado. Si uno o más de los ocho radiales caen sobre el mar o sobre regiones para las cuales no existen datos SDF disponibles, SPLAT! reportará sin terreno la trayectoria de los radiales afectados.
-
-RESTRINGIENDO EL TAMAÑO MÁXIMO DE UNA REGIÓN ANALIZADA
-SPLAT! lee los archivos SDF de acuerdo a sus necesidades dentro de una serie de “ranuras” de memoria dentro de la estructura del programa. Cada “ranura” contiene un archivo SDF representando una región de terreno de un grado por un grado.
-
-Una sentencia #define MAXSLOTS en las primeras líneas del archivo splat.cpp configura el máximo número de “ranuras” disponibles para los datos topográficos. Esto también configura el tamaño máximo de los mapas generados por SPLAT!. Por defecto MAXSLOTS es configurado a 9. Si SPLAT! produce un fallo de segmentación al arrancar con estos parámetros por defecto, significa que no hay suficiente memoria RAM y/ó memoria virtual (partición swap) para correr SPLAT! con este número de MAXSLOTS. En situaciones donde la memoria disponible es baja, MAXSLOTS pueden ser reducidos a 4 con el entendimiento de que esto limitará grandemente la máxima región que SPLAT! estará habilitado a analizar. Si se tiene disponible 118 megabytes ó mas de la memoria total (partición swap sumada la RAM), entonces MAXSLOTS puede ser incrementado a 16. esto permitirá operaciones sobre una región de 4-grados por 4-grados, lo cual es suficiente para alturas de antenas que excedan los 10,000 pies sobre el nivel del mar, ó distancias punto-a-punto sobre las 1000 millas.
-
-GENERACIÓN DE ARCHIVOS DE GEOREFERENCIA
-Los mapas topográficos, de cobertura (-c), y contornos de pérdidas por trayectoria (-L) generados por SPLAT! pueden ser importados dentro del programa Xastir (X Amateur Station Tracking and Information Reporting), generando un archivo de georeferencia usando la opción SPLAT -geo:
-
-splat ‐t kd2bd ‐R 50.0 ‐s NJ_Cities ‐b NJ_Counties ‐geo ‐o map.ppm
-
-El archivo de georeferencia creado tendrá el mismo nombre base que el archivo -o especificado, pero con extensión .geo, y permite la apropiada interpretación y presentación de los gráficos .ppm SPLAT! en el programa Xastir.
-
-GENERACION DE ARCHIVOS KML GOOGLE MAP
-Archivos Keyhole Markup Language compatibles con Google Earth pueden ser generados por SPLAT! cuando se realizan análisis punto-a-punto invocando la opción -kml :
-
-splat ‐t wnjt ‐r kd2bd ‐kml
-
-El archivo KML generado tendrá la misma estructura que el nombre del Reporte de Obstrucciones para los sitios del transmisor y receptor dados, excepto que tendrá una extensión .kml .
-
-Una vez cargado dentro del Google Earth (Archivo --> Abrir), el archivo KLM exhibirá las localizaciones de los sitios de transmisión y recepción en el mapa. Los puntos de vista de la imagen serán desde la posición del sitio de transmisión mirando hacia la localización del receptor. La trayectoria punto-a-punto entre los sitios será presentada como una línea blanca, mientras que la trayectoria de linea-de-vista RF será presentada en verde. Las herramientas de navegación de Google Earth la permiten al usuario "volar" alrededor de la trayectoria, identificando señales, caminos, y otras características contenidas.
-
-
-INFORMACIÓN ADICIONAL
-Invocar SPLAT! sin ningún argumento desplegará todas las opciones de línea de comando disponibles del programa con una breve descripción de cada una de ellas.
-
-Las últimas noticias e información respecto al programa SPLAT! está disponible a través de la página web oficial localizada en: http://www.qsl.net/kd2bd/splat.html.
-
-AUTORES
- John A. Magliacane, KD2BD <kd2bd@amsat.org>
- Creator, Lead Developer
-
- Doug McDonald <mcdonald@scs.uiuc.edu>
- Longley-Rice Model integration
-
- Ron Bentley <ronbentley@earthlink.net>
- Fresnel Zone plotting and clearance determination
-
-KD2BD Software 20 December 2006 SPLAT!(1)
-
-
-Traducción del manual al español por Charles Escobar (chescobar@gmail.com)
+++ /dev/null
-SPLAT!(1) KD2BD Software SPLAT!(1)
-
-
-
-NAME
- splat - An RF Signal Propagation, Loss, And Terrain analy-
- sis tool
-
-SYNOPSIS
- splat [-t transmitter_site.qth] [-r receiver_site.qth]
- [-c rx antenna height for LOS coverage analysis
- (feet/meters) (float)] [-L rx antenna height for Longley-
- Rice coverage analysis (feet/meters) (float)] [-p ter-
- rain_profile.ext] [-e elevation_profile.ext] [-h
- height_profile.ext] [-H normalized_height_profile.ext] [-l
- Longley-Rice_profile.ext] [-o topographic_map_file-
- name.ppm] [-b cartographic_boundary_filename.dat] [-s
- site/city_database.dat] [-d sdf_directory_path] [-m earth
- radius multiplier (float)] [-f frequency (MHz) for Fresnel
- zone calculations (float)] [-R maximum coverage radius
- (miles/kilometers) (float)] [-dB maximum attenuation con-
- tour to display on path loss maps (80-230 dB)] [-nf do not
- plot Fresnel zones in height plots] [-plo path_loss_out-
- put_file.txt] [-pli path_loss_input_file.txt] [-udt
- user_defined_terrain_file.dat] [-n] [-N] [-geo] [-kml]
- [-metric]
-
-DESCRIPTION
- SPLAT! is a powerful terrestrial RF propagation and ter-
- rain analysis tool covering the spectrum between 20 MHz
- and 20 GHz. SPLAT! 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 SPLAT! source code in pro-
- prietary or closed-source applications is a violation of
- this license, and is strictly forbidden.
-
- SPLAT! 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.
-
-INTRODUCTION
- Applications of SPLAT! 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
- interference studies, and the determination of analog and
- digital terrestrial radio and television contour regions.
-
- SPLAT! 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, 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.
-
- SPLAT! 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,
- SPLAT! determines individual and mutual areas of coverage
- within the network specified.
-
- Simply typing splat on the command line will return a sum-
- mary of SPLAT!'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
-
-
-INPUT FILES
- SPLAT! 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 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.
-
-SPLAT DATA FILES
- SPLAT! imports topographic data in the form of SPLAT Data
- Files (SDFs). These files may be generated from a number
- of information sources. In the United States, SPLAT Data
- Files can be generated through U.S. Geological Survey
- Digital Elevation Models (DEMs) using the usgs2sdf utility
- included with SPLAT!. USGS Digital Elevation Models com-
- patible with this utility may be downloaded from:
- http://edcftp.cr.usgs.gov/pub/data/DEM/250/.
-
- 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
- srtm2sdf utility. SRTM-3 Version 2 data may be obtained
- through anonymous FTP from:
- ftp://e0srp01u.ecs.nasa.gov:21/srtm/version2/
-
- Despite the higher accuracy that SRTM data has to offer,
- some voids in the data sets exist. When voids are
- detected, the srtm2sdf utility replaces them with corre-
- sponding data found in existing SDF files (that were pre-
- sumably created from earlier USGS data through the
- usgs2sdf utility). If USGS-derived SDF data is not avail-
- able, voids are handled through adjacent pixel averaging,
- or direct replacement.
-
- 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 (.sdf) as generated by the usgs2sdf and
- srtm2sdf utilities, or in bzip2 compressed format
- (.sdf.bz2). Since uncompressed files can be processed
- slightly faster than files that have been compressed,
- SPLAT! searches for needed SDF data in uncompressed format
- first. If uncompressed data cannot be located, SPLAT!
- then searches for data in bzip2 compressed format. If no
- compressed SDF files can be found for the region
- requested, SPLAT! assumes the region is over water, and
- will assign an elevation of sea-level to these areas.
-
- This feature of SPLAT! 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 SPLAT! underscores the impor-
- tance of having all the SDF files required for the region
- being analyzed if meaningful results are to be expected.
-
-SITE LOCATION (QTH) FILES
- SPLAT! imports site location information of transmitter
- and receiver sites analyzed by the program from ASCII
- files having a .qth 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), each separated by a sin-
- gle line-feed character. The antenna height is assumed to
- be specified in feet unless followed by the letter m or
- the word meters 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-
- mat (74 41 20.0).
-
- For example, a site location file describing television
- station WNJT, Trenton, NJ (wnjt.qth) might read as fol-
- lows:
-
- WNJT
- 40.2833
- 74.6889
- 990.00
-
- Each transmitter and receiver site analyzed by SPLAT! must
- be represented by its own site location (QTH) file.
-
-LONGLEY-RICE PARAMETER (LRP) FILES
- Longley-Rice parameter data files are required for SPLAT!
- 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 (wnjt.lrp):
-
- 15.000 ; Earth Dielectric Constant (Relative per-
- mittivity)
- 0.005 ; Earth Conductivity (Siemens per meter)
- 301.000 ; Atmospheric Bending Constant (N-units)
- 700.000 ; Frequency in MHz (20 MHz to 20 GHz)
- 5 ; Radio Climate (5 = Continental Temper-
- ate)
- 0 ; Polarization (0 = Horizontal, 1 = Verti-
- cal)
- 0.5 ; Fraction of situations (50% of loca-
- tions)
- 0.5 ; Fraction of time (50% of the time)
-
- If an LRP file corresponding to the tx_site QTH file can-
- not be found, SPLAT! scans the current working directory
- for the file "splat.lrp". If this file cannot be found,
- then the default parameters listed above will be assigned
- by SPLAT! and a corresponding "splat.lrp" file containing
- this data will be written to the current working direc-
- tory. "splat.lrp" can then be edited by the user as
- needed.
-
- Typical Earth dielectric constants and conductivity values
- are as follows:
-
- Dielectric Constant Conductiv-
- ity
- Salt water : 80 5.000
- Good ground : 25 0.020
- Fresh water : 80 0.010
- Marshy land : 12 0.007
- Farmland, forest : 15 0.005
- Average ground : 15 0.005
- Mountain, sand : 13 0.002
- City : 5 0.001
- Poor ground : 4 0.001
-
- Radio climate codes used by SPLAT! are as follows:
-
- 1: Equatorial (Congo)
- 2: Continental Subtropical (Sudan)
- 3: Maritime Subtropical (West coast of Africa)
- 4: Desert (Sahara)
- 5: Continental Temperate
- 6: Maritime Temperate, over land (UK and west
- coasts of US & EU)
- 7: Maritime Temperate, over sea
-
- The Continental Temperate climate is common to large land
- masses in the temperate zone, such as the United States.
- For paths shorter than 100 km, there is little difference
- between Continental and Maritime Temperate climates.
-
- The final two parameters in the .lrp file correspond to
- the statistical analysis provided by the Longley-Rice
- model. In this example, SPLAT! will return the maximum
- path loss occurring 50% of the time (fraction of time) in
- 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:
- http://flattop.its.bldrdoc.gov/itm.html and
- http://www.softwright.com/faq/engineering/prop_long-
- ley_rice.html
-
-CITY LOCATION FILES
- The names and locations of cities, tower sites, or other
- points of interest may be imported and plotted on topo-
- graphic maps generated by SPLAT!. SPLAT! imports the
- names of cities and locations from ASCII files containing
- 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 .qth files, latitude and longitude information
- may be entered in either decimal or degree, minute, second
- (DMS) format.
-
- For example (cities.dat):
-
- Teaneck, 40.891973, 74.014506
- Tenafly, 40.919212, 73.955892
- Teterboro, 40.859511, 74.058908
- Tinton Falls, 40.279966, 74.093924
- Toms River, 39.977777, 74.183580
- Totowa, 40.906160, 74.223310
- Trenton, 40.219922, 74.754665
-
- A total of five separate city data files may be imported
- at a time, and there is no limit to the size of these
- files. SPLAT! 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 read
- earlier in the current city data file, or in previous
- files. This behavior minimizes clutter in SPLAT! 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
- available from the U.S. Census Bureau using the cityde-
- coder utility included with SPLAT!. Such data is avail-
- able free of charge via the Internet at: http://www.cen-
- sus.gov/geo/www/cob/bdy_files.html, and must be in ASCII
- format.
-
-CARTOGRAPHIC BOUNDARY DATA FILES
- Cartographic boundary data may also be imported to plot
- the boundaries of cities, counties, or states on topo-
- graphic maps generated by SPLAT!. 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:
- http://www.census.gov/geo/www/cob/co2000.html#ascii and
- http://www.census.gov/geo/www/cob/pl2000.html#ascii. 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.
-
-PROGRAM OPERATION
- SPLAT! is invoked via the command-line using a series of
- switches and arguments. Since SPLAT! is a CPU and memory
- intensive application, this type of interface minimizes
- overhead and lends itself well to scripted (batch) opera-
- tions. SPLAT!'s CPU and memory scheduling priority may be
- modified through the use of the Unix nice command.
-
- The number and type of switches passed to SPLAT! determine
- its mode of operation and method of output data genera-
- tion. Nearly all of SPLAT!'s switches may be cascaded in
- any order on the command line when invoking the program.
-
- SPLAT! operates in two distinct modes: point-to-point
- mode, and area prediction mode. 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.
-
-POINT-TO-POINT ANALYSIS
- SPLAT! 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 line-of-sight terrain analysis between the
- transmitter specified in tx_site.qth and receiver speci-
- fied in rx_site.qth using a True Earth radius model, and
- writes a SPLAT! 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, SPLAT! 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 -metric switch is added to SPLAT!'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 minimum 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.
-
- qth extensions are assumed by SPLAT! for QTH files, and
- are optional when specifying -t and -r arguments on the
- command-line. SPLAT! automatically reads all SPLAT Data
- Files necessary to conduct the terrain analysis between
- the sites specified. SPLAT! searches for the required
- SDF files in the current working directory first. If the
- needed files are not found, SPLAT! then searches in the
- path specified by the -d 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 of last resort
- to all the SDF files. The path in the $HOME/.splat_path
- 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
- receiver can be generated by adding the -p switch:
-
- splat -t tx_site -r rx_site -p terrain_profile.png
-
- SPLAT! invokes gnuplot when generating graphs. The file-
- name extension specified to SPLAT! determines the format
- of the graph produced. .png will produce a 640x480 color
- PNG graphic file, while .ps or .postscript will produce
- postscript output. Output in formats such as GIF, Adobe
- Illustrator, AutoCAD dxf, LaTeX, and many others are
- available. Please consult gnuplot, and gnuplot'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
- the receiver can be generated by using the -e switch:
-
- 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
- from the perspective of the receiver's location. A second
- 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
- 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
- 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
- generated using the -h switch:
-
- 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 -H
- 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 first Fresnel Zone, and 60% of the first Fresnel Zone
- can be added to height profile graphs by adding the -f
- 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 -l switch:
-
- splat -t tx_site -r rx_site -l path_loss_profile.png
-
- As before, adding the -metric 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 SPLAT! in the form of a
- text file with a .lro 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 Line-of-Sight, Single Horizon, Double Hori-
- zon, Diffraction Dominant, and Troposcatter Dominant.
-
- To determine the signal-to-noise (SNR) ratio at remote
- location where random Johnson (thermal) noise is the pri-
- mary limiting factor in reception:
-
- SNR=T-NJ-L+G-NF
-
- where T is the ERP of the transmitter in dBW in the direc-
- tion of the receiver, NJ is Johnson Noise in dBW (-136 dBW
- for a 6 MHz television channel), L is the path loss pro-
- vided by SPLAT! in dB (as a positive number), G is the
- receive antenna gain in dB over isotropic, and NF is the
- receiver noise figure in dB.
-
- T may be computed as follows:
-
- T=TI+GT
-
- where TI is actual amount of RF power delivered to the
- transmitting antenna in dBW, GT is the transmitting
- antenna gain (over isotropic) in the direction of the
- receiver (or the horizon if the receiver is over the hori-
- zon).
-
- To compute how much more signal is available over the min-
- imum to necessary to achieve a specific signal-to-noise
- ratio:
-
- Signal_Margin=SNR-S
-
- where S 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 SPLAT! to visualize
- the path between the transmitter and receiver sites from
- yet another perspective. Topographic maps generated by
- SPLAT! display elevations using a logarithmic grayscale,
- with higher elevations represented through brighter shades
- of gray. The dynamic range of the image is scaled between
- the highest and lowest elevations present in the map. The
- only exception to this is sea-level, which is represented
- using the color blue.
-
- Topographic output is invoked using the -o switch:
-
- splat -t tx_site -r rx_site -o topo_map.ppm
-
- The .ppm extension on the output filename is assumed by
- SPLAT!, and is optional.
-
- In this example, topo_map.ppm will illustrate the loca-
- tions of the transmitter and receiver sites specified. In
- addition, the great circle path between the two sites will
- be drawn over locations for which an unobstructed path
- exists to the transmitter at a receiving antenna height
- equal to that of the receiver site (specified in
- rx_site.qth).
-
- It may desirable to populate the topographic map with
- names and locations of cities, tower sites, or other
- important locations. A city file may be passed to SPLAT!
- using the -s switch:
-
- splat -t tx_site -r rx_site -s cities.dat -o topo_map
-
- Up to five separate city files may be passed to SPLAT! at
- a time following the -s switch.
-
- County and state boundaries may be added to the map by
- specifying up to five U.S. Census Bureau cartographic
- boundary files using the -b switch:
-
- splat -t tx_site -r rx_site -b co34_d00.dat -o topo_map
-
- In situations where multiple transmitter sites are in use,
- as many as four site locations may be passed to SPLAT! at
- a time for analysis:
-
- splat -t tx_site1 tx_site2 tx_site3 tx_site4 -r rx_site -p
- profile.png
-
- In this example, four separate terrain profiles and
- obstruction reports will be generated by SPLAT!. A single
- topographic map can be specified using the -o switch, and
- line-of-sight paths between each transmitter and the
- receiver site indicated will be produced on the map, each
- in its own color. The path between the first transmitter
- specified to the receiver will be in green, the path
- between the second transmitter and the receiver will be in
- cyan, the path between the third transmitter and the
- receiver will be in violet, and the path between the
- fourth transmitter and the receiver will be in sienna.
-
- SPLAT! 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 xv, The GIMP, ImageMagick,
- and XPaint. PNG format is highly recommended for lossless
- compressed storage of SPLAT! generated topographic output
- files. ImageMagick's command-line utility easily converts
- SPLAT!'s PPM files to PNG format:
-
- convert splat_map.ppm splat_map.png
-
- Another excellent PPM to PNG command-line utility is
- available at:
- http://www.libpng.org/pub/png/book/sources.html. As a
- last resort, PPM files may be compressed using the bzip2
- utility, and read directly by The GIMP in this format.
-
-REGIONAL COVERAGE ANALYSIS
- SPLAT! can analyze a transmitter or repeater site, or net-
- work of sites, and predict the regional coverage for each
- site specified. In this mode, SPLAT! 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
- with the site in question. SPLAT! switches from point-to-
- point analysis mode to area prediction mode when the -c
- switch is invoked as follows:
-
- splat -t tx_site -c 30.0 -s cities.dat -b co34_d00.dat -o
- tx_coverage
-
- In this example, SPLAT! generates a topographic map called
- tx_coverage.ppm that illustrates the predicted line-of-
- sight regional coverage of tx_site to receiving locations
- having antennas 30.0 feet above ground level (AGL). If
- the -metric switch is used, the argument following the -c
- switch is interpreted as being in meters, rather than in
- feet. The contents of cities.dat are plotted on the map,
- as are the cartographic boundaries contained in the file
- co34_d00.dat.
-
- When plotting line-of-sight paths and areas of regional
- coverage, SPLAT! by default does not account for the
- effects of atmospheric bending. However, this behavior
- may be modified by using the Earth radius multiplier (-m)
- switch:
-
- 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 SPLAT! to
- use the "four-thirds earth" model for line-of-sight propa-
- gation analysis. Any appropriate earth radius multiplier
- may be selected by the user.
-
- When invoked in area prediction mode, SPLAT! generates a
- site report for each station analyzed. SPLAT! 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
- 315 degrees azimuth.
-
-DETERMINING MULTIPLE REGIONS OF LOS COVERAGE
- SPLAT! 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 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 10.0
- meters above ground level. A topographic map is then
- written to the file network.ppm. The line-of-sight cover-
- age area of the transmitters are plotted as follows in the
- colors indicated (along with their corresponding RGB val-
- ues in decimal):
-
- site1: Green (0,255,0)
- site2: Cyan (0,255,255)
- site3: Medium Violet (147,112,219)
- site4: Sienna 1 (255,130,71)
-
- site1 + site2: Yellow (255,255,0)
- site1 + site3: Pink (255,192,203)
- site1 + site4: Green Yellow (173,255,47)
- site2 + site3: Orange (255,165,0)
- site2 + site4: Dark Sea Green 1 (193,255,193)
- site3 + site4: Dark Turquoise (0,206,209)
-
- site1 + site2 + site3: Dark Green (0,100,0)
- site1 + site2 + site4: Blanched Almond (255,235,205)
- site1 + site3 + site4: Medium Spring Green (0,250,154)
- site2 + site3 + site4: Tan (210,180,140)
-
- site1 + site2 + site3 + site4: Gold2 (238,201,0)
-
- If separate .qth files are generated, each representing a
- common site location but a different antenna height, a
- single topographic map illustrating the regional coverage
- from as many as four separate locations on a single tower
- may be generated by SPLAT!.
-
-LONGLEY-RICE PATH LOSS ANALYSIS
- If the -c switch is replaced by a -L 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, SPLAT! 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 -R switch. The argument must be
- given in miles (or kilometers if the -metric switch is
- used). If a range wider than the generated topographic
- map is specified, SPLAT! will perform Longley-Rice path
- loss calculations between all four corners of the area
- prediction map.
-
- The -db 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, SPLAT!'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
-
-
-ANTENNA RADIATION PATTERN PARAMETERS
- Normalized field voltage patterns for a transmitting
- antenna's horizontal and vertical planes are imported
- automatically into SPLAT! 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 .az and .el 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 SPLAT! antenna pattern files.
-
- For example, the first few lines of a SPLAT! azimuth pat-
- tern file might appear as follows (kvea.az):
-
- 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 .az file specifies the amount of
- azimuthal pattern rotation (measured clockwise in degrees
- from True North) to be applied by SPLAT! to the data con-
- tained in the .az 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 SPLAT! elevation pattern files is
- slightly different. The first line of the .el file speci-
- fies the amount of mechanical beam tilt applied to the
- antenna. Note that a downward tilt (below the horizon) is
- expressed as a positive angle, while an upward tilt (above
- the horizon) is expressed as a negative angle. 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,
- negative elevation angles are used to represent elevations
- above the horizon, while positive angles represents eleva-
- tions below the horizon.
-
- For example, the first few lines a SPLAT! elevation pat-
- tern file might appear as follows (kvea.el):
-
- 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, SPLAT! will
- interpolate the values provided to determine the data at
- the required resolution, although this may result in a
- loss in accuracy.
-
-
-IMPORTING AND EXPORTING REGIONAL PATH LOSS CONTOUR DATA
- 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 SPLAT! to rapidly produce a
- revised path loss map.
-
- For example, a path loss output file can be generated by
- SPLAT! 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
-
- SPLAT! 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 SPLAT! path loss output file take on the fol-
- lowing appearance (pathloss.dat):
-
- 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 SPLAT! 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 vim 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 -L switch if 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
- SPLAT!. 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 SPLAT! path loss files to reflect antenna
- pattern data, only the last column (path loss) 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 SPLAT!
- for generating revised coverage maps:
-
- splat -t kvea -pli pathloss.dat -s city.dat -b county.dat
- -o map.ppm
-
- SPLAT! path loss files can also be used for conducting
- coverage or interference studies outside of SPLAT!.
-
-USER-DEFINED TERRAIN INPUT FILES
- 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 SPLAT! analysis being conducted, but
- noticeably absent from the SDF files being used. A user-
- defined terrain file is imported into a SPLAT! analysis
- using the -udt 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 meters, and
- is added on top of 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 SPLAT!.
-
-SIMPLE TOPOGRAPHIC MAP GENERATION
- 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
- between the sites, the -n switch should be invoked as fol-
- lows:
-
- splat -t tx_site -r rx_site -n -o topo_map.ppm
-
- If no text report is desired, then the -N switch is used:
-
- splat -t tx_site -r rx_site -N -o topo_map.ppm
-
- 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 -metric switch is used).
-
- If the -o switch and output filename are omitted in these
- operations, topographic output is written to a file named
- map.ppm in the current working directory by default.
-
-GEOREFERENCE FILE GENERATION
- Topographic, coverage (-c), and path loss contour (-L)
- maps generated by SPLAT! may be imported into Xastir (X
- Amateur Station Tracking and Information Reporting) soft-
- ware by generating a georeference file using SPLAT!'s -geo
- 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 -o file specified, but have a .geo extension,
- and permit proper interpretation and display of SPLAT!'s
- .ppm graphics in Xastir software.
-
-GOOGLE MAP KML FILE GENERATION
- Keyhole Markup Language files compatible with Google Earth
- may be generated by SPLAT! when performing point-to-point
- analyses by invoking the -kml 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 .kml
- extension.
-
- Once loaded into Google Earth (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. Google Earth's navigation tools allow
- the user to "fly" around the path, identify landmarks,
- roads, and other featured content.
-
-DETERMINATION OF ANTENNA HEIGHT ABOVE AVERAGE TERRAIN
- SPLAT! determines antenna height above average terrain
- (HAAT) according to the procedure defined by Federal Com-
- munications Commission Part 73.313(d). According to this
- definition, terrain elevations along eight radials between
- 2 and 10 miles (3 and 16 kilometers) from the site being
- analyzed are sampled and averaged for each 45 degrees of
- azimuth starting with True North. If one or more radials
- 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.
-
- 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 SPLAT! are
- SRTM-derived.
-
- When performing point-to-point terrain analysis, SPLAT!
- 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
- data in memory.
-
- When performing area prediction analysis, enough topogra-
- phy data is normally loaded by SPLAT! to perform average
- terrain calculations. Under such conditions, SPLAT! 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, SPLAT!
- reports No Terrain for the radial paths affected.
-
-RESTRICTING THE MAXIMUM SIZE OF AN ANALYSIS REGION
- SPLAT! 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 #define MAXSLOTS
- statement in the first several lines of splat.cpp sets the
- maximum number of "slots" available for holding topography
- data. It also sets the maximum size of the topographic
- maps generated by SPLAT!. MAXSLOTS is set to 9 by
- default. If SPLAT! 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 SPLAT! 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 SPLAT! 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.
-
-ADDITIONAL INFORMATION
- The latest news and information regarding SPLAT! software
- is available through the official SPLAT! software web page
- located at: http://www.qsl.net/kd2bd/splat.html.
-
-AUTHORS
- John A. Magliacane, KD2BD <kd2bd@amsat.org>
- Creator, Lead Developer
-
- Doug McDonald <mcdonald@scs.uiuc.edu>
- Longley-Rice Model integration
-
- Ron Bentley <ronbentley@earthlink.net>
- Fresnel Zone plotting and clearance determination
-
-
-
-
-KD2BD Software 20 December 2006 SPLAT!(1)
install_man()
{
- cp docs/man/splat.1 /usr/local/man/man1/splat.1
+ cp docs/english/man/splat.1 /usr/local/man/man1/splat.1
echo "man page installed!"
}
-/****************************************************************************
-* *
-* This file was obtained from ftp://flattop.its.bldrdoc.gov/itm/ITMDLL.cpp *
-* on Jan. 10, 2004 and is public domain. It was modified by J. D. McDonald *
-* to remove Microsoft Windows dll-isms and to correct one case where a *
-* compiler found an ambguity in overloaded calls. It was further modified *
-* by John A. Magliacane to remove unused variables, unneeded #includes, *
-* and to replace pow() statements with explicit multiplications wherever *
-* possible to increase execution speed and improve accuracy. *
-* *
-****************************************************************************/
+/*****************************************************************************\
+ * *
+ * The following code was derived from public domain ITM code available *
+ * at ftp://flattop.its.bldrdoc.gov/itm/ITMDLL.cpp that was released on *
+ * June 26, 2007. It was modified to remove Microsoft Windows "dll-isms", *
+ * redundant and unnecessary #includes, redundant and unnecessary { }'s, *
+ * to initialize uninitialized variables, type cast some variables, *
+ * re-format the code for easier reading, and to replace pow() function *
+ * calls with explicit multiplications wherever possible to increase *
+ * execution speed and improve computational accuracy. *
+ * *
+\*****************************************************************************/
+
// *************************************
// C++ routines for this program are taken from
#include <assert.h>
#include <string.h>
-#define THIRD (1.0/3.0)
+#define THIRD (1.0/3.0)
using namespace std;
struct tcomplex
-{ double tcreal;
+{
+ double tcreal;
double tcimag;
};
struct prop_type
-{ double aref;
+{
+ double aref;
double dist;
double hg[2];
double wn;
};
struct propv_type
-{ double sgc;
+{
+ double sgc;
int lvar;
int mdvar;
int klim;
};
struct propa_type
-{ double dlsa;
+{
+ double dlsa;
double dx;
double ael;
double ak1;
double FORTRAN_DIM(const double &x, const double &y)
{
- /* This performs the FORTRAN DIM function. Result is x-y
- if x is greater than y; otherwise result is 0.0 */
+ // This performs the FORTRAN DIM function.
+ // result is x-y if x is greater than y; otherwise result is 0.0
if (x>y)
return x-y;
a=6.02+9.11*sqrt(v2)-1.27*v2;
else
a=12.953+4.343*log(v2);
+
return a;
}
double fht(const double& x, const double& pk)
{
double w, fhtv;
-
if (x<200.0)
{
w=-log(pk);
- /* if (pk<1e-5 || x*pow(w,3.0) > 5495.0) */
- if (pk<1.0e-5 || x*w*w*w > 5495.0)
+ /* if (pk < 1e-5 || x*pow(w,3.0) > 5495.0 ) */
+
+ if (pk < 1e-5 || (x*w*w*w) > 5495.0 )
{
fhtv=-117.0;
if (x>1.0)
fhtv=17.372*log(x)+fhtv;
}
+
else
fhtv=2.5e-5*x*x/pk-8.686*w-15.0;
}
fhtv=(1.0-w)*fhtv+w*(17.372*log(x)-117.0);
}
}
+
return fhtv;
}
double a[5]={25.0, 80.0, 177.0, 395.0, 705.0};
double b[5]={24.0, 45.0, 68.0, 80.0, 105.0};
double q, x;
- double h0fv, temp;
int it;
+ double h0fv;
it=(int)et;
q=et-it;
/* x=pow(1.0/r,2.0); */
-
- temp=1.0/r;
- x=temp*temp;
-
+ x=(1.0/r);
+ x*=x;
h0fv=4.343*log((a[it-1]*x+b[it-1])*x+1.0);
if (q!=0.0)
double ahd(double td)
{
int i;
- double a[3]={ 133.4, 104.6, 71.8};
- double b[3]={0.332e-3, 0.212e-3, 0.157e-3};
- double c[3]={ -4.343, -1.086, 2.171};
+ double a[3] = { 133.4, 104.6, 71.8};
+ double b[3] = {0.332e-3, 0.212e-3, 0.157e-3};
+ double c[3] = { -4.343, -1.086, 2.171};
if (td<=10e3)
i=0;
return a[i]+b[i]*td+c[i]*log(td);
}
-double adiff(double d, prop_type &prop, propa_type &propa)
+double adiff( double d, prop_type &prop, propa_type &propa)
{
complex<double> prop_zgnd(prop.zgndreal,prop.zgndimag);
static double wd1, xd1, afo, qk, aht, xht;
adiffv=0.0;
}
- else
+ else
{
th=propa.tha+d*prop.gme;
ds=d-propa.dla;
return adiffv;
}
-double ascat( double d, prop_type &prop, propa_type &propa)
+double ascat( double d, prop_type &prop, propa_type &propa)
{
static double ad, rr, etq, h0s;
double h0, r1, r2, z0, ss, et, ett, th, q;
q=mymin(mymax(0.1,q),10.0);
z0=(d-ad)*(d+ad)*th*0.25/d;
/* et=(etq*exp(-pow(mymin(1.7,z0/8.0e3),6.0))+1.0)*z0/1.7556e3; */
-
temp=mymin(1.7,z0/8.0e3);
temp=temp*temp*temp*temp*temp*temp;
et=(etq*exp(-temp)+1.0)*z0/1.7556e3;
h0=FORTRAN_DIM(h0,0.0);
if (et<1.0)
- {
- /* h0=et*h0+(1.0-et)*4.343*log(pow((1.0+1.4142/r1)*(1.0+1.4142/r2),2.0)*(r1+r2)/(r1+r2+2.8284)); */
-
- temp=((1.0+1.4142/r1)*(1.0+1.4142/r2));
- h0=et*h0+(1.0-et)*4.343*log((temp*temp)*(r1+r2)/(r1+r2+2.8284));
- }
+ h0=et*h0+(1.0-et)*4.343*log(pow((1.0+1.4142/r1) *(1.0+1.4142/r2),2.0)*(r1+r2)/(r1+r2+2.8284));
if (h0>15.0 && h0s>=0.0)
h0=h0s;
h0s=h0;
th=propa.tha+d*prop.gme;
/* ascatv=ahd(th*d)+4.343*log(47.7*prop.wn*pow(th,4.0))-0.1*(prop.ens-301.0)*exp(-th*d/40e3)+h0; */
- ascatv=ahd(th*d)+4.343*log(47.7*prop.wn*(th*th*th*th))-0.1*(prop.ens-301.0)*exp(-th*d/40e3)+h0;
+
+ ascatv=ahd(th*d)+4.343*log(47.7*prop.wn*th*th*th*th)-0.1*(prop.ens-301.0)*exp(-th*d/40e3)+h0;
+
}
return ascatv;
}
-double qerfi(double q)
+double qerfi (double q)
{
double x, t, v;
double c0=2.515516698;
return v;
}
-void qlrps(double fmhz, double zsys, double en0, int ipol, double eps, double sgm, prop_type &prop)
+void qlrps( double fmhz, double zsys, double en0, int ipol, double eps, double sgm, prop_type &prop)
+
{
double gma=157e-9;
prop.zgndimag=prop_zgnd.imag();
}
-double abq_alos (complex<double> r)
+double abq_alos(complex<double> r)
{
return r.real()*r.real()+r.imag()*r.imag();
}
q=3.14-2.4649/q;
alosv=(-4.343*log(abq_alos(complex<double>(cos(q),-sin(q))+r))-alosv)*wls+alosv;
+ }
- }
return alosv;
}
for (int j=0; j<2; ++j)
{
if (kst[j]<=0)
- prop.he[j]=prop.hg[j];
+ prop.he[j]=prop.hg[j];
else
{
q=4.0;
prop.mdp=1;
propv.lvar=mymax(propv.lvar,3);
-
+
if (mdvarx>=0)
{
propv.mdvar=mdvarx;
}
}
-void freds_lrprop (double d, prop_type &prop, propa_type &propa)
+void lrprop (double d, prop_type &prop, propa_type &propa) // PaulM_lrprop
{
- /* freds_lrprop */
-
- static bool wlos, wscat;
- static double dmin, xae;
- complex<double> prop_zgnd(prop.zgndreal,prop.zgndimag);
- double a0, a1, a2, a3, a4, a5, a6;
- double d0, d1, d2, d3, d4, d5, d6;
- double q;
- int j;
-
- if (prop.mdp!=0)
- {
- for (j=0; j<2; ++j)
- propa.dls[j]=sqrt(2.0*prop.he[j]/prop.gme);
-
- propa.dlsa=propa.dls[0]+propa.dls[1];
- propa.dla=prop.dl[0]+prop.dl[1];
- propa.tha=mymax(prop.the[0]+prop.the[1],-propa.dla*prop.gme);
- wlos=false;
- wscat=false;
-
- if (prop.wn<0.838 || prop.wn>210.0)
- prop.kwx=mymax(prop.kwx,1);
-
- for (j=0; j<2; ++j)
- if (prop.hg[j]<1.0 || prop.hg[j]>1000.0)
- prop.kwx=mymax(prop.kwx,1);
-
- for (j=0; j<2; ++j)
- if (abs(prop.the[j]) >200e-3 || prop.dl[j]<0.1*propa.dls[j] || prop.dl[j]>3.0*propa.dls[j])
- prop.kwx=mymax(prop.kwx,3);
-
- if (prop.ens < 250.0 || prop.ens > 400.0 || prop.gme < 75e-9 || prop.gme > 250e-9 || prop_zgnd.real() <= abs(prop_zgnd.imag()) || prop.wn < 0.419 || prop.wn > 420.0)
- prop.kwx=4;
-
- for (j=0; j<2; ++j)
- if (prop.hg[j]<0.5 || prop.hg[j]>3000.0)
- prop.kwx=4;
-
- dmin=abs(prop.he[0]-prop.he[1])/200e-3;
- q=adiff(0.0,prop,propa);
- xae=pow(prop.wn*prop.gme*prop.gme,-THIRD);
- d3=mymax(propa.dlsa,1.3787*xae+propa.dla);
- d4=d3+2.7574*xae;
- a3=adiff(d3,prop,propa);
- a4=adiff(d4,prop,propa);
- propa.emd=(a4-a3)/(d4-d3);
- propa.aed=a3-propa.emd*d3;
-
- if (prop.mdp==0)
- prop.dist=0;
-
- else if (prop.mdp>0)
- {
- prop.mdp=0;
- prop.dist=0;
- }
-
- if ((prop.dist>0.0) || (prop.mdp<0.0))
- {
- if (prop.dist>1000e3)
- prop.kwx=mymax(prop.kwx,1);
-
- if (prop.dist<dmin)
- prop.kwx=mymax(prop.kwx,3);
-
- if (prop.dist<1e3 || prop.dist>2000e3)
- prop.kwx=4;
- }
- }
-
- else
- {
- prop.dist=d;
-
- if (prop.dist>0.0)
- {
- if (prop.dist>1000e3)
- prop.kwx=mymax(prop.kwx,1);
-
- if (prop.dist<dmin)
- prop.kwx=mymax(prop.kwx,3);
-
- if (prop.dist<1e3 || prop.dist>2000e3)
- prop.kwx=4;
- }
- }
-
- if (prop.dist<propa.dlsa)
- {
- if (!wlos)
- {
- /* Coefficients for the line-of-sight range */
-
- q=alos(0.0,prop,propa);
- d2=propa.dlsa;
- a2=propa.aed+d2*propa.emd;
- d0=1.908*prop.wn*prop.he[0]*prop.he[1];
-
- if (propa.aed>=0.0)
- {
- d0=mymin(d0,0.5*propa.dla);
- d1=d0+0.25*(propa.dla-d0);
- }
-
- else
- d1=mymax(-propa.aed/propa.emd,0.25*propa.dla);
-
- a1=alos(d1,prop,propa);
-
- if (d0<d1)
- {
- a0=alos(d0,prop,propa);
- q=log(d2/d0);
- propa.ak2=mymax(0.0,((d2-d0)*(a1-a0)-(d1-d0)*(a2-a0))/((d2-d0)*log(d1-d0)-(d1-d0)*q));
-
- if (propa.ak2<=0.0 && propa.aed<0.0)
- {
- propa.ak2=0.0;
- propa.ak1=(a2-a1)/(d2-d1);
-
- if (propa.ak1<=0.0)
- propa.ak2=propa.emd;
- }
-
- else
- {
- propa.ak1=(a2-a0-propa.ak2*q)/(d2-d0);
-
- if (propa.ak1<0.0)
- {
- propa.ak1=0.0;
- propa.ak2=FORTRAN_DIM(a2,a0)/q;
-
- if (propa.ak2<=0.0)
- propa.ak1=propa.emd;
- }
- }
- propa.ael=a2-propa.ak1*d2-propa.ak2*log(d2);
- wlos=true;
- }
- }
-
- if (prop.dist>0.0)
- prop.aref=propa.ael+propa.ak1*prop.dist+propa.ak2*log(prop.dist);
- }
-
- else
- {
- if (!wscat)
- {
- q=ascat(0.0,prop,propa);
- d5=propa.dla+200e3;
- d6=d5+200e3;
- a6=ascat(d6,prop,propa);
- a5=ascat(d5,prop,propa);
-
- if (a5>=1000.0)
- {
- propa.ems=propa.emd;
- propa.aes=propa.aed;
- propa.dx=10e6;
- }
-
- else
- {
- propa.ems=(a6-a5)/200e3;
- propa.dx=mymax(propa.dlsa,mymax(propa.dla+0.3*xae*log(47.7*prop.wn),(a5-propa.aed-propa.ems*d5)/(propa.emd-propa.ems)));
- propa.aes=(propa.emd-propa.ems)*propa.dx+propa.aed;
- }
-
- wscat=true;
- }
-
- if (prop.dist<=propa.dx)
- prop.aref=propa.aed+propa.emd*prop.dist;
- else
- prop.aref=propa.aes+propa.ems*prop.dist;
- }
-
- prop.aref=FORTRAN_DIM(prop.aref,0.0);
-}
-
-void lrprop (double d, prop_type &prop, propa_type &propa)
-{
- /* PaulM_lrprop */
static bool wlos, wscat;
static double dmin, xae;
complex<double> prop_zgnd(prop.zgndreal,prop.zgndimag);
int j;
if (prop.mdp!=0)
- {
+ {
for (j=0; j<2; j++)
propa.dls[j]=sqrt(2.0*prop.he[j]/prop.gme);
prop.kwx=mymax(prop.kwx,1);
for (j=0; j<2; j++)
- if (abs(prop.the[j]) >200e-3 || prop.dl[j]<0.1*propa.dls[j] || prop.dl[j]>3.0*propa.dls[j] )
+ if (abs(prop.the[j]) >200e-3 || prop.dl[j]<0.1*propa.dls[j] || prop.dl[j]>3.0*propa.dls[j])
prop.kwx=mymax(prop.kwx,3);
if (prop.ens < 250.0 || prop.ens > 400.0 || prop.gme < 75e-9 || prop.gme > 250e-9 || prop_zgnd.real() <= abs(prop_zgnd.imag()) || prop.wn < 0.419 || prop.wn > 420.0)
+
prop.kwx=4;
for (j=0; j<2; j++)
- if (prop.hg[j]<0.5 || prop.hg[j]>3000.0)
- prop.kwx=4;
+
+ if (prop.hg[j]<0.5 || prop.hg[j]>3000.0)
+ {
+ prop.kwx=4;
+ }
dmin=abs(prop.he[0]-prop.he[1])/200e-3;
q=adiff(0.0,prop,propa);
- /* xae=pow(prop.wn*pow(prop.gme,2.),-THIRD); -- JDM made argument 2 a double */
- xae=pow(prop.wn*(prop.gme*prop.gme),-THIRD); /* No 2nd pow() */
+ /* xae=pow(prop.wn*pow(prop.gme,2),-THIRD); */
+ xae=pow(prop.wn*prop.gme*prop.gme,-THIRD);
d3=mymax(propa.dlsa,1.3787*xae+propa.dla);
d4=d3+2.7574*xae;
a3=adiff(d3,prop,propa);
if (propa.ak1<0.0)
{
propa.ak1=0.0;
- propa.ak2=FORTRAN_DIM(a2,a0)/q;
+ propa.ak2=FORTRAN_DIM(a2,a0)/q;
if (propa.ak2==0.0)
propa.ak1=propa.emd;
}
}
-
- else
- {
- propa.ak2=0.0;
- propa.ak1=(a2-a1)/(d2-d1);
-
- if (propa.ak1<=0.0)
- propa.ak1=propa.emd;
- }
}
-
- else
+
+ if (!wq)
{
- propa.ak1=(a2-a1)/(d2-d1);
+ propa.ak1=FORTRAN_DIM(a2,a1)/(d2-d1);
propa.ak2=0.0;
- if (propa.ak1<=0.0)
+ if (propa.ak1==0.0)
propa.ak1=propa.emd;
}
if (prop.dist>0.0)
prop.aref=propa.ael+propa.ak1*prop.dist+propa.ak2*log(prop.dist);
-
}
if (prop.dist<=0.0 || prop.dist>=propa.dlsa)
{
- if(!wscat)
+ if (!wscat)
{
q=ascat(0.0,prop,propa);
d5=propa.dla+200e3;
{
propa.ems=(a6-a5)/200e3;
propa.dx=mymax(propa.dlsa,mymax(propa.dla+0.3*xae*log(47.7*prop.wn),(a5-propa.aed-propa.ems*d5)/(propa.emd-propa.ems)));
+
propa.aes=(propa.emd-propa.ems)*propa.dx+propa.aed;
}
prop.aref=mymax(prop.aref,0.0);
}
-double curve (double const &c1, double const &c2, double const &x1,
- double const &x2, double const &x3, double const &de)
+double curve (double const &c1, double const &c2, double const &x1, double const &x2, double const &x3, double const &de)
{
/* return (c1+c2/(1.0+pow((de-x2)/x3,2.0)))*pow(de/x1,2.0)/(1.0+pow(de/x1,2.0)); */
+
double temp1, temp2;
temp1=(de-x2)/x3;
return (c1+c2/(1.0+temp1))*temp2/(1.0+temp2);
}
-double avar(double zzt, double zzl, double zzc, prop_type &prop, propv_type &propv)
+double avar(double zzt, double zzl, double zzc,prop_type &prop, propv_type &propv)
{
- static int kdv;
- static double dexa, de, vmd, vs0, sgl, sgtm, sgtp, sgtd, tgtd,
- gm, gp, cv1, cv2, yv1, yv2, yv3, csm1, csm2, ysm1, ysm2,
- ysm3, csp1, csp2, ysp1, ysp2, ysp3, csd1, zd, cfm1, cfm2,
- cfm3, cfp1, cfp2, cfp3;
+ static int kdv;
+ static double dexa, de, vmd, vs0, sgl, sgtm, sgtp, sgtd, tgtd, gm, gp, cv1, cv2, yv1, yv2, yv3, csm1, csm2, ysm1, ysm2, ysm3, csp1, csp2, ysp1, ysp2, ysp3, csd1, zd, cfm1, cfm2, cfm3, cfp1, cfp2, cfp3;
double bv1[7]={-9.67,-0.62,1.26,-9.21,-0.62,-0.39,3.15};
double bv2[7]={12.7,9.19,15.5,9.05,9.19,2.86,857.9};
double bfp3[7]={0.0,2.00,0.0,1.79,2.00,0.0,0.0};
static bool ws, w1;
double rt=7.8, rl=24.0, avarv, q, vs, zt, zl, zc;
- double sgt, yr, temp1, temp2;
+ double sgt, yr;
int temp_klim=propv.klim-1;
if (propv.lvar>0)
default:
if (propv.klim<=0 || propv.klim>7)
{
- propv.klim=5;
- temp_klim=4;
+ propv.klim = 5;
+ temp_klim = 4;
prop.kwx=mymax(prop.kwx,2);
}
- cv1=bv1[temp_klim];
- cv2=bv2[temp_klim];
- yv1=xv1[temp_klim];
- yv2=xv2[temp_klim];
- yv3=xv3[temp_klim];
+ cv1 = bv1[temp_klim];
+ cv2 = bv2[temp_klim];
+ yv1 = xv1[temp_klim];
+ yv2 = xv2[temp_klim];
+ yv3 = xv3[temp_klim];
csm1=bsm1[temp_klim];
csm2=bsm2[temp_klim];
ysm1=xsm1[temp_klim];
else
{
/* vs0=pow(5.0+3.0*exp(-de/100e3),2.0); */
- temp1=(5.0+3.0*exp(-de/100e3));
- vs0=temp1*temp1;
-
+ vs0=(5.0+3.0*exp(-de/100e3));
+ vs0*=vs0;
}
propv.lvar=0;
sgt=sgtd+tgtd/zt;
/* vs=vs0+pow(sgt*zt,2.0)/(rt+zc*zc)+pow(sgl*zl,2.0)/(rl+zc*zc); */
-
- temp1=sgt*zt;
- temp2=sgl*zl;
-
- vs=vs0+(temp1*temp1)/(rt+zc*zc)+(temp2*temp2)/(rl+zc*zc);
+ vs=vs0+(sgt*zt*sgt*zt)/(rt+zc*zc)+(sgl*zl*sgl*zl)/(rl+zc*zc);
if (kdv==0)
{
return avarv;
}
-void hzns (double pfl[], prop_type &prop)
+void hzns(double pfl[], prop_type &prop)
{
bool wq;
int np;
}
void z1sq1 (double z[], const double &x1, const double &x2, double& z0, double& zn)
+
{
double xn, xa, xb, x, a, b;
int n, ja, jb;
double qtile (const int &nn, double a[], const int &ir)
{
- double q=0.0, r; /* q initialization -- KD2BD */
- int m, n, i, j, j1=0, i0=0, k; /* more initializations -- KD2BD */
+ double q=0.0, r; /* Initializations by KD2BD */
+ int m, n, i, j, j1=0, i0=0, k; /* Initializations by KD2BD */
bool done=false;
bool goto10=true;
if (i>n)
i=n;
-
j=j1;
while (j>=m && a[j]<=q)
}
else
- done=true;
+ done=true;
}
return q;
return d1thxv;
}
-void qlrpfl(double pfl[], int klimx, int mdvarx, prop_type &prop, propa_type &propa, propv_type &propv)
+void qlrpfl (double pfl[], int klimx, int mdvarx, prop_type &prop, propa_type &propa, propv_type &propv)
{
int np, j;
- double xl[2], q, za, zb, temp;
+ double xl[2], q, za, zb;
prop.dist=pfl[0]*pfl[1];
np=(int)pfl[0];
if (q<=prop.dist)
{
/* q=pow(prop.dist/q,2.0); */
- temp=prop.dist/q;
- q=temp*temp;
+ q=((prop.dist/q)*(prop.dist/q));
for (j=0; j<2; j++)
{
{
q=sqrt(2.0*prop.he[j]/prop.gme);
prop.the[j]=(0.65*prop.dh*(q/prop.dl[j]-1.0)-2.0*prop.he[j])/q;
- }
+ }
}
else
//********************************************************
void point_to_point(double elev[], double tht_m, double rht_m, double eps_dielect, double sgm_conductivity, double eno_ns_surfref, double frq_mhz, int radio_climate, int pol, double conf, double rel, double &dbloss, char *strmode, int &errnum)
+{
+ // pol: 0-Horizontal, 1-Vertical
+ // radio_climate: 1-Equatorial, 2-Continental Subtropical, 3-Maritime Tropical,
+ // 4-Desert, 5-Continental Temperate, 6-Maritime Temperate, Over Land,
+ // 7-Maritime Temperate, Over Sea
+ // conf, rel: .01 to .99
+ // elev[]: [num points - 1], [delta dist(meters)], [height(meters) point 1], ..., [height(meters) point n]
+ // errnum: 0- No Error.
+ // 1- Warning: Some parameters are nearly out of range.
+ // Results should be used with caution.
+ // 2- Note: Default parameters have been substituted for impossible ones.
+ // 3- Warning: A combination of parameters is out of range.
+ // Results are probably invalid.
+ // Other- Warning: Some parameters are out of range.
+ // Results are probably invalid.
-/******************************************************************************
+ prop_type prop;
+ propv_type propv;
+ propa_type propa;
- pol:
- 0-Horizontal, 1-Vertical
+ double zsys=0;
+ double zc, zr;
+ double eno, enso, q;
+ long ja, jb, i, np;
+ double dkm, xkm;
+ double fs;
- radio_climate:
- 1-Equatorial, 2-Continental Subtropical,
- 3-Maritime Tropical, 4-Desert, 5-Continental Temperate,
- 6-Maritime Temperate, Over Land, 7-Maritime Temperate,
- Over Sea
+ prop.hg[0]=tht_m;
+ prop.hg[1]=rht_m;
+ propv.klim=radio_climate;
+ prop.kwx=0;
+ propv.lvar=5;
+ prop.mdp=-1;
+ zc=qerfi(conf);
+ zr=qerfi(rel);
+ np=(long)elev[0];
+ dkm=(elev[1]*elev[0])/1000.0;
+ xkm=elev[1]/1000.0;
+ eno=eno_ns_surfref;
+ enso=0.0;
+ q=enso;
+
+ if (q<=0.0)
+ {
+ /* ja = 3.0 + 0.1 * elev[0]; */
+ ja=(long)(3.0+0.1* elev[0]);
- conf, rel: .01 to .99
+ jb=np-ja+6;
- elev[]: [num points - 1], [delta dist(meters)],
- [height(meters) point 1], ..., [height(meters) point n]
+ for (i=ja-1; i<jb; ++i)
+ zsys+=elev[i];
- errnum: 0- No Error.
- 1- Warning: Some parameters are nearly out of range.
- Results should be used with caution.
- 2- Note: Default parameters have been substituted for
- impossible ones.
- 3- Warning: A combination of parameters is out of range.
- Results are probably invalid.
- Other- Warning: Some parameters are out of range.
- Results are probably invalid.
+ zsys/=(jb-ja+1);
+ q=eno;
+ }
-*****************************************************************************/
+ propv.mdvar=12;
+ qlrps(frq_mhz,zsys,q,pol,eps_dielect,sgm_conductivity,prop);
+ qlrpfl(elev,propv.klim,propv.mdvar,prop,propa,propv);
+ fs=32.45+20.0*log10(frq_mhz)+20.0*log10(prop.dist/1000.0);
+ q=prop.dist-propa.dla;
+
+ if (int(q)<0.0)
+ strcpy(strmode,"Line-Of-Sight Mode");
+
+ else
+ {
+ if (int(q)==0.0)
+ strcpy(strmode,"Single Horizon");
+
+ else if (int(q)>0.0)
+ strcpy(strmode,"Double Horizon");
+
+ if (prop.dist<=propa.dlsa || prop.dist <= propa.dx)
+ strcat(strmode,", Diffraction Dominant");
+
+ else if (prop.dist>propa.dx)
+ strcat(strmode, ", Troposcatter Dominant");
+ }
+
+ dbloss=avar(zr,0.0,zc,prop,propv)+fs;
+ errnum=prop.kwx;
+}
+
+void point_to_pointMDH (double elev[], double tht_m, double rht_m, double eps_dielect, double sgm_conductivity, double eno_ns_surfref, double frq_mhz, int radio_climate, int pol, double timepct, double locpct, double confpct, double &dbloss, int &propmode, double &deltaH, int &errnum)
{
+ // pol: 0-Horizontal, 1-Vertical
+ // radio_climate: 1-Equatorial, 2-Continental Subtropical, 3-Maritime Tropical,
+ // 4-Desert, 5-Continental Temperate, 6-Maritime Temperate, Over Land,
+ // 7-Maritime Temperate, Over Sea
+ // timepct, locpct, confpct: .01 to .99
+ // elev[]: [num points - 1], [delta dist(meters)], [height(meters) point 1], ..., [height(meters) point n]
+ // propmode: Value Mode
+ // -1 mode is undefined
+ // 0 Line of Sight
+ // 5 Single Horizon, Diffraction
+ // 6 Single Horizon, Troposcatter
+ // 9 Double Horizon, Diffraction
+ // 10 Double Horizon, Troposcatter
+ // errnum: 0- No Error.
+ // 1- Warning: Some parameters are nearly out of range.
+ // Results should be used with caution.
+ // 2- Note: Default parameters have been substituted for impossible ones.
+ // 3- Warning: A combination of parameters is out of range.
+ // Results are probably invalid.
+ // Other- Warning: Some parameters are out of range.
+ // Results are probably invalid.
+
+ prop_type prop;
+ propv_type propv;
+ propa_type propa;
+ double zsys=0;
+ double ztime, zloc, zconf;
+ double eno, enso, q;
+ long ja, jb, i, np;
+ double dkm, xkm;
+ double fs;
+
+ propmode=-1; // mode is undefined
+ prop.hg[0]=tht_m;
+ prop.hg[1]=rht_m;
+ propv.klim=radio_climate;
+ prop.kwx=0;
+ propv.lvar=5;
+ prop.mdp=-1;
+ ztime=qerfi(timepct);
+ zloc=qerfi(locpct);
+ zconf=qerfi(confpct);
+
+ np=(long)elev[0];
+ dkm=(elev[1]*elev[0])/1000.0;
+ xkm=elev[1]/1000.0;
+ eno=eno_ns_surfref;
+ enso=0.0;
+ q=enso;
+
+ if (q<=0.0)
+ {
+ /* ja = 3.0 + 0.1 * elev[0]; */
+ ja=(long)(3.0+0.1*elev[0]);
+ jb=np-ja+6;
+
+ for (i=ja-1; i<jb; ++i)
+ zsys+=elev[i];
+
+ zsys/=(jb-ja+1);
+ q=eno;
+ }
+
+ propv.mdvar=12;
+ qlrps(frq_mhz,zsys,q,pol,eps_dielect,sgm_conductivity,prop);
+ qlrpfl(elev,propv.klim,propv.mdvar,prop,propa,propv);
+ fs=32.45+20.0*log10(frq_mhz)+20.0*log10(prop.dist/1000.0);
+ deltaH=prop.dh;
+ q=prop.dist-propa.dla;
+
+ if (int(q)<0.0)
+ propmode=0; // Line-Of-Sight Mode
+ else
+ {
+ if (int(q)==0.0)
+ propmode=4; // Single Horizon
+
+ else if (int(q)>0.0)
+ propmode=8; // Double Horizon
+
+ if (prop.dist<=propa.dlsa || prop.dist<=propa.dx)
+ propmode+=1; // Diffraction Dominant
+
+ else if (prop.dist>propa.dx)
+ propmode+=2; // Troposcatter Dominant
+ }
+
+ dbloss=avar(ztime, zloc, zconf, prop, propv)+fs; //avar(time,location,confidence)
+ errnum=prop.kwx;
+}
+
+void point_to_pointDH (double elev[], double tht_m, double rht_m, double eps_dielect, double sgm_conductivity, double eno_ns_surfref, double frq_mhz, int radio_climate, int pol, double conf, double rel, double &dbloss, double &deltaH, int &errnum)
+{
+ // pol: 0-Horizontal, 1-Vertical
+ // radio_climate: 1-Equatorial, 2-Continental Subtropical, 3-Maritime Tropical,
+ // 4-Desert, 5-Continental Temperate, 6-Maritime Temperate, Over Land,
+ // 7-Maritime Temperate, Over Sea
+ // conf, rel: .01 to .99
+ // elev[]: [num points - 1], [delta dist(meters)], [height(meters) point 1], ..., [height(meters) point n]
+ // errnum: 0- No Error.
+ // 1- Warning: Some parameters are nearly out of range.
+ // Results should be used with caution.
+ // 2- Note: Default parameters have been substituted for impossible ones.
+ // 3- Warning: A combination of parameters is out of range.
+ // Results are probably invalid.
+ // Other- Warning: Some parameters are out of range.
+ // Results are probably invalid.
+
+ char strmode[100];
prop_type prop;
propv_type propv;
propa_type propa;
if (q<=0.0)
{
- ja=(long)(3.0+0.1*elev[0]); /* KD2BD added (long) */
+ /* ja = 3.0 + 0.1 * elev[0]; */
+ ja=(long)(3.0+0.1*elev[0]);
+
jb=np-ja+6;
for (i=ja-1; i<jb; ++i)
qlrps(frq_mhz,zsys,q,pol,eps_dielect,sgm_conductivity,prop);
qlrpfl(elev,propv.klim,propv.mdvar,prop,propa,propv);
fs=32.45+20.0*log10(frq_mhz)+20.0*log10(prop.dist/1000.0);
+ deltaH=prop.dh;
q=prop.dist-propa.dla;
if (int(q)<0.0)
strcat(strmode, ", Troposcatter Dominant");
}
- dbloss=avar(zr,0.0,zc,prop,propv)+fs;
+ dbloss=avar(zr,0.0,zc,prop,propv)+fs; //avar(time,location,confidence)
errnum=prop.kwx;
}
+
//********************************************************
//* Area Mode Calculations *
//********************************************************
// pol: 0-Horizontal, 1-Vertical
// TSiteCriteria, RSiteCriteria:
// 0 - random, 1 - careful, 2 - very careful
-
// radio_climate: 1-Equatorial, 2-Continental Subtropical, 3-Maritime Tropical,
// 4-Desert, 5-Continental Temperate, 6-Maritime Temperate, Over Land,
// 7-Maritime Temperate, Over Sea
// ModVar: 0 - Single: pctConf is "Time/Situation/Location", pctTime, pctLoc not used
- // 1 - Individual: pctTime is "Situation/Location", pctConf is "Confidence", pctLoc not used
- // 2 - Mobile: pctTime is "Time/Locations (Reliability)", pctConf is "Confidence", pctLoc not used
- // 3 - Broadcast: pctTime is "Time", pctLoc is "Location", pctConf is "Confidence"
+ // 1 - Individual: pctTime is "Situation/Location", pctConf is "Confidence", pctLoc not used
+ // 2 - Mobile: pctTime is "Time/Locations (Reliability)", pctConf is "Confidence", pctLoc not used
+ // 3 - Broadcast: pctTime is "Time", pctLoc is "Location", pctConf is "Confidence"
// pctTime, pctLoc, pctConf: .01 to .99
// errnum: 0- No Error.
// 1- Warning: Some parameters are nearly out of range.
kst[0]=(int)TSiteCriteria;
kst[1]=(int)RSiteCriteria;
- zt=qerfi(pctTime/100.0);
- zl=qerfi(pctLoc/100.0);
- zc=qerfi(pctConf/100.0);
+ zt=qerfi(pctTime);
+ zl=qerfi(pctLoc);
+ zc=qerfi(pctConf);
eps=eps_dielect;
sgm=sgm_conductivity;
eno=eno_ns_surfref;
prop.dh=deltaH;
prop.hg[0]=tht_m;
prop.hg[1]=rht_m;
- /* propv.klim = (__int32) radio_climate; -KD2BD replaced below */
+ /* propv.klim = (__int32) radio_climate; */
propv.klim=(long)radio_climate;
prop.ens=eno;
prop.kwx=0;
fs=32.45+20.0*log10(frq_mhz)+20.0*log10(prop.dist/1000.0);
xlb=fs+avar(zt, zl, zc, prop, propv);
dbloss=xlb;
-
+
if (prop.kwx==0)
errnum=0;
else
errnum=prop.kwx;
}
+
+double ITMAreadBLoss(long ModVar, double deltaH, double tht_m, double rht_m, double dist_km, int TSiteCriteria, int RSiteCriteria, double eps_dielect, double sgm_conductivity, double eno_ns_surfref, double frq_mhz, int radio_climate, int pol, double pctTime, double pctLoc, double pctConf)
+{
+ char strmode[200];
+ int errnum;
+ double dbloss;
+
+ area(ModVar,deltaH,tht_m,rht_m,dist_km,TSiteCriteria,RSiteCriteria, eps_dielect,sgm_conductivity,eno_ns_surfref, frq_mhz,radio_climate,pol,pctTime,pctLoc, pctConf,dbloss,strmode,errnum);
+
+ return dbloss;
+}
+
+double ITMVersion()
+{
+ return 7.0;
+}
+
+++ /dev/null
-15.000 ; Earth Dielectric Constant (Relative permittivity)
-0.005 ; Earth Conductivity (Siemens per meter)
-301.000 ; Atmospheric Bending Constant (N-units)
-300.000 ; Frequency in MHz (20 MHz to 20 GHz)
-5 ; Radio Climate (5 = Continental Temperate)
-0 ; Polarization (0 = Horizontal, 1 = Vertical)
-0.5 ; Fraction of situations (50% of locations)
-0.5 ; Fraction of time (50% of the time)
-
-This file contains Longley-Rice path loss parameters used
-by SPLAT! Anything after the 8th line is ignored by the
-program. Comments are allowed following each element of
-numeric data. No blank lines are allowed at the top.
-
-Earth dielectric constants and conductivity values are as follows:
-
- Dielectric Constant Conductivity
- Salt water : 80 5.000
- Good ground : 25 0.020
- Fresh water : 80 0.010
- Marshy land : 12 0.007
- Farmland, forest : 15 0.005
- Average ground : 15 0.005
- Mountain, sand : 13 0.002
- City : 5 0.001
- Poor ground : 4 0.001
-
-Radio climate codes are defined as follows:
-
- 1: Equatorial (Congo)
- 2: Continental Subtropical (Sudan)
- 3: Maritime Subtropical (West coast of Africa)
- 4: Desert (Sahara)
- 5: Continental Temperate
- 6: Maritime Temperate, over land (UK and west coasts of US & EU)
- 7: Maritime Temperate, over sea
-
-The Continental Temperate climate (5) is common to large land masses in
-the temperate zone, such as the United States. For paths shorter than
-100 km, there is little difference between Continental and Martitime
-Temperate climates.
-
-The final two parameters in the .lrp file correspond to the statistical
-analysis provided by the Longley-Rice model. In this example, SPLAT!
-will return the maximum path loss occurring 50% of the time (fraction
-of time) in 50% of situations (fraction of situations). Use a fraction
-of time of 0.97 for digital television, 0.50 for analog. Isotropic
-antennas are assumed. A tuned half-wave dipole has a gain of 2.14 dB
-above that of an isotropic antenna.
-
-Edit these parameters as required and save the result ("Save As")
-to a filename with an extension of ".lrp" in the directory normally
-used for .qth files (current working directory is assumed). The
-base of the filename MUST match the base of the corresponding
-SPLAT! transmitter site QTH filename for proper correlation
-between data sets. In other words:
-
- wnjt.qth <--- TX site data for WNJT
- wnjt.lrp <--- Corresponding Longly-Rice parameters for WNJT
-
-If an LRP file corresponding to the tx_site QTH file cannot be
-found, SPLAT! scans the current working directory for "splat.lrp".
-If this file cannot be found, then the default parameters listed
-above are assigned by SPLAT!, and a "splat.lrp" file containing
-these parameters is written to the current working directory.
-
-For further information on Longley-Rice model parameters, see:
-
- http://elbert.its.bldrdoc.gov/itm.html
- http://www.softwright.com/faq/engineering/prop_longley_rice.html
-
-Also consult SPLAT!'s documentation for more information.
--- /dev/null
+15.000 ; Earth Dielectric Constant (Relative permittivity)
+0.005 ; Earth Conductivity (Siemens per meter)
+301.000 ; Atmospheric Bending Constant (N-units)
+646.000 ; Frequency in MHz (20 MHz to 20 GHz)
+5 ; Radio Climate (5 = Continental Temperate)
+0 ; Polarization (0 = Horizontal, 1 = Vertical)
+0.5 ; Fraction of situations (50% of locations)
+0.5 ; Fraction of time (50% of the time)
+46000.0 ; Effective Radiated Power in Watts (optional)
+
+This file contains Longley-Rice path loss parameters used
+by SPLAT! Anything after the 9th line is ignored by the
+program. Comments are allowed following each element of
+numeric data. No blank lines are allowed at the top.
+
+Earth dielectric constants and conductivity values are as follows:
+
+ Dielectric Constant Conductivity
+ Salt water : 80 5.000
+ Good ground : 25 0.020
+ Fresh water : 80 0.010
+ Marshy land : 12 0.007
+ Farmland, forest : 15 0.005
+ Average ground : 15 0.005
+ Mountain, sand : 13 0.002
+ City : 5 0.001
+ Poor ground : 4 0.001
+
+Radio climate codes are defined as follows:
+
+ 1: Equatorial (Congo)
+ 2: Continental Subtropical (Sudan)
+ 3: Maritime Subtropical (West coast of Africa)
+ 4: Desert (Sahara)
+ 5: Continental Temperate
+ 6: Maritime Temperate, over land (UK and west coasts of US & EU)
+ 7: Maritime Temperate, over sea
+
+The Continental Temperate climate (5) is common to large land masses in
+the temperate zone, such as the United States. For paths shorter than
+100 km, there is little difference between Continental and Martitime
+Temperate climates.
+
+The 7th and 8th parameters in the .lrp file correspond to the statistical
+analysis provided by the Longley-Rice model. In this example, SPLAT!
+will return the maximum path loss occurring 50% of the time (fraction
+of time) in 50% of situations (fraction of situations). Use a fraction
+of time of 0.90 for digital television, 0.50 for analog.
+
+Edit these parameters as required and save the result ("Save As")
+to a filename with an extension of ".lrp" in the directory normally
+used for .qth files (current working directory is assumed). The
+base of the filename MUST match the base of the corresponding
+SPLAT! transmitter site QTH filename for proper correlation
+between data sets. In other words:
+
+ wnjt-dt.qth <--- TX site data for WNJT-DT
+ wnjt-dt.lrp <--- Corresponding Longly-Rice parameters for WNJT-DT
+
+If an LRP file corresponding to the tx_site QTH file cannot be
+found, SPLAT! scans the current working directory for "splat.lrp".
+If this file cannot be found, then default parameters similar to
+those listed above are assigned by SPLAT!, and a "splat.lrp" file
+containing those parameters is written to the current working directory.
+
+For further information on Longley-Rice model parameters, see:
+
+ http://elbert.its.bldrdoc.gov/itm.html
+ http://www.softwright.com/faq/engineering/prop_longley_rice.html
+
+Also consult SPLAT!'s documentation for more information.
+
--- /dev/null
+0
+0 0.49
+1 0.5
+2 0.51
+3 0.52
+4 0.53
+5 0.54
+6 0.55
+7 0.56
+8 0.58
+9 0.59
+10 0.6
+11 0.62
+12 0.63
+13 0.65
+14 0.67
+15 0.68
+16 0.7
+17 0.72
+18 0.73
+19 0.75
+20 0.77
+21 0.79
+22 0.8
+23 0.82
+24 0.83
+25 0.85
+26 0.86
+27 0.87
+28 0.88
+29 0.89
+30 0.9
+31 0.91
+32 0.92
+33 0.92
+34 0.93
+35 0.93
+36 0.93
+37 0.93
+38 0.92
+39 0.92
+40 0.91
+41 0.91
+42 0.9
+43 0.89
+44 0.88
+45 0.87
+46 0.86
+47 0.85
+48 0.84
+49 0.82
+50 0.82
+51 0.81
+52 0.8
+53 0.8
+54 0.79
+55 0.79
+56 0.79
+57 0.8
+58 0.8
+59 0.81
+60 0.82
+61 0.84
+62 0.85
+63 0.87
+64 0.88
+65 0.9
+66 0.91
+67 0.93
+68 0.94
+69 0.95
+70 0.96
+71 0.97
+72 0.98
+73 0.98
+74 0.99
+75 0.99
+76 0.99
+77 0.98
+78 0.98
+79 0.97
+80 0.96
+81 0.95
+82 0.94
+83 0.93
+84 0.92
+85 0.91
+86 0.9
+87 0.89
+88 0.88
+89 0.88
+90 0.87
+91 0.87
+92 0.87
+93 0.87
+94 0.88
+95 0.88
+96 0.89
+97 0.9
+98 0.91
+99 0.92
+100 0.93
+101 0.94
+102 0.95
+103 0.96
+104 0.97
+105 0.98
+106 0.99
+107 0.99
+108 1
+109 1
+110 1
+111 1
+112 1
+113 0.99
+114 0.99
+115 0.98
+116 0.97
+117 0.96
+118 0.95
+119 0.94
+120 0.93
+121 0.92
+122 0.91
+123 0.9
+124 0.89
+125 0.88
+126 0.88
+127 0.87
+128 0.87
+129 0.87
+130 0.87
+131 0.88
+132 0.88
+133 0.89
+134 0.9
+135 0.91
+136 0.92
+137 0.93
+138 0.94
+139 0.95
+140 0.96
+141 0.97
+142 0.98
+143 0.98
+144 0.99
+145 0.99
+146 0.99
+147 0.98
+148 0.98
+149 0.97
+150 0.96
+151 0.95
+152 0.94
+153 0.93
+154 0.91
+155 0.9
+156 0.88
+157 0.87
+158 0.85
+159 0.84
+160 0.82
+161 0.81
+162 0.8
+163 0.8
+164 0.79
+165 0.79
+166 0.79
+167 0.8
+168 0.8
+169 0.81
+170 0.82
+171 0.82
+172 0.84
+173 0.85
+174 0.86
+175 0.87
+176 0.88
+177 0.89
+178 0.9
+179 0.91
+180 0.91
+181 0.92
+182 0.92
+183 0.93
+184 0.93
+185 0.93
+186 0.93
+187 0.92
+188 0.92
+189 0.91
+190 0.9
+191 0.89
+192 0.88
+193 0.87
+194 0.86
+195 0.85
+196 0.83
+197 0.82
+198 0.8
+199 0.79
+200 0.77
+201 0.75
+202 0.73
+203 0.72
+204 0.7
+205 0.68
+206 0.67
+207 0.65
+208 0.63
+209 0.62
+210 0.6
+211 0.59
+212 0.58
+213 0.56
+214 0.55
+215 0.54
+216 0.53
+217 0.52
+218 0.51
+219 0.5
+220 0.49
+221 0.48
+222 0.47
+223 0.47
+224 0.46
+225 0.45
+226 0.44
+227 0.43
+228 0.42
+229 0.4
+230 0.39
+231 0.38
+232 0.37
+233 0.35
+234 0.34
+235 0.33
+236 0.32
+237 0.3
+238 0.29
+239 0.28
+240 0.26
+241 0.25
+242 0.24
+243 0.23
+244 0.22
+245 0.21
+246 0.2
+247 0.2
+248 0.19
+249 0.19
+250 0.18
+251 0.18
+252 0.18
+253 0.18
+254 0.18
+255 0.18
+256 0.18
+257 0.18
+258 0.18
+259 0.17
+260 0.17
+261 0.17
+262 0.17
+263 0.17
+264 0.17
+265 0.17
+266 0.16
+267 0.16
+268 0.16
+269 0.16
+270 0.16
+271 0.16
+272 0.16
+273 0.16
+274 0.16
+275 0.16
+276 0.16
+277 0.17
+278 0.17
+279 0.17
+280 0.17
+281 0.18
+282 0.18
+283 0.18
+284 0.18
+285 0.18
+286 0.19
+287 0.19
+288 0.19
+289 0.19
+290 0.19
+291 0.19
+292 0.19
+293 0.19
+294 0.19
+295 0.18
+296 0.18
+297 0.18
+298 0.18
+299 0.18
+300 0.17
+301 0.17
+302 0.17
+303 0.17
+304 0.16
+305 0.16
+306 0.16
+307 0.16
+308 0.16
+309 0.16
+310 0.16
+311 0.16
+312 0.16
+313 0.16
+314 0.16
+315 0.17
+316 0.17
+317 0.17
+318 0.17
+319 0.17
+320 0.17
+321 0.17
+322 0.18
+323 0.18
+324 0.18
+325 0.18
+326 0.18
+327 0.18
+328 0.18
+329 0.18
+330 0.18
+331 0.19
+332 0.19
+333 0.2
+334 0.2
+335 0.21
+336 0.22
+337 0.23
+338 0.24
+339 0.25
+340 0.26
+341 0.28
+342 0.29
+343 0.3
+344 0.32
+345 0.33
+346 0.34
+347 0.35
+348 0.37
+349 0.38
+350 0.39
+351 0.4
+352 0.42
+353 0.43
+354 0.44
+355 0.45
+356 0.46
+357 0.47
+358 0.47
+359 0.48
--- /dev/null
+ 0.0 0.0
+-10 0.04
+-9.5 0.06
+-9 0.12
+-8.5 0.16
+-8 0.17
+-7.5 0.15
+-7 0.1
+-6.5 0.05
+-6 0.04
+-5.5 0.03
+-5 0.05
+-4.5 0.16
+-4 0.29
+-3.5 0.39
+-3 0.41
+-2.8 0.39
+-2.6 0.36
+-2.4 0.31
+-2.2 0.24
+-2 0.17
+-1.8 0.11
+-1.6 0.14
+-1.4 0.24
+-1.2 0.35
+-1 0.48
+-0.8 0.59
+-0.6 0.7
+-0.4 0.8
+-0.2 0.88
+0 0.94
+0.2 0.98
+0.4 1
+0.6 1
+0.8 0.97
+1 0.92
+1.2 0.86
+1.4 0.77
+1.6 0.68
+1.8 0.58
+2 0.48
+2.2 0.38
+2.4 0.28
+2.6 0.21
+2.8 0.17
+3 0.16
+3.2 0.18
+3.4 0.21
+3.6 0.22
+3.8 0.23
+4 0.22
+4.2 0.21
+4.4 0.18
+4.6 0.16
+4.8 0.13
+5 0.12
+5.2 0.12
+5.4 0.14
+5.6 0.16
+5.8 0.18
+6 0.2
+6.2 0.21
+6.4 0.21
+6.6 0.2
+6.8 0.19
+7 0.17
+7.2 0.14
+7.4 0.11
+7.6 0.09
+7.8 0.06
+8 0.04
+8.2 0.04
+8.4 0.05
+8.6 0.06
+8.8 0.07
+9 0.07
+9.2 0.07
+9.4 0.06
+9.6 0.05
+9.8 0.04
+10 0.04
+10.2 0.04
+10.4 0.06
+10.6 0.08
+10.8 0.09
+11 0.11
+11.5 0.12
+12 0.11
+12.5 0.07
+13 0.03
+13.5 0.04
+14 0.05
+14.5 0.04
+15 0.03
+15.5 0.05
+16 0.09
+16.5 0.1
+17 0.1
+17.5 0.08
+18 0.04
+18.5 0.02
+19 0.02
+19.5 0.01
+20 0.02
+20.5 0.05
+21 0.08
+21.5 0.11
+22 0.11
+22.5 0.09
+23 0.05
+23.5 0.02
+24 0.05
+24.5 0.08
+25 0.1
+25.5 0.1
+26 0.09
+26.5 0.07
+27 0.04
+27.5 0.03
+28 0.02
+28.5 0.01
+29 0.01
+29.5 0.02
+30 0.02
+30.5 0.02
+31 0.02
+31.5 0.02
+32 0.03
+32.5 0.03
+33 0.04
+33.5 0.03
+34 0.02
+34.5 0.01
+35 0.01
+35.5 0.02
+36 0.02
+36.5 0.01
+37 0.01
+37.5 0.02
+38 0.03
+38.5 0.04
+39 0.04
+39.5 0.04
+40 0.03
+40.5 0.02
+41 0.01
+41.5 0.02
+42 0.02
+42.5 0.02
+43 0.01
+43.5 0.02
+44 0.03
+44.5 0.04
+45 0.05
+45.5 0.06
+46 0.06
+46.5 0.05
+47 0.04
+47.5 0.03
+48 0.02
+48.5 0.01
+49 0.01
+49.5 0.01
+50 0.01
+50.5 0.02
+51 0.04
+51.5 0.06
+52 0.08
+52.5 0.1
+53 0.11
+53.5 0.11
+54 0.1
+54.5 0.08
+55 0.05
+55.5 0.03
+56 0.04
+56.5 0.07
+57 0.1
+57.5 0.14
+58 0.16
+58.5 0.18
+59 0.2
+59.5 0.2
+60 0.2
+60.5 0.19
+61 0.17
+61.5 0.15
+62 0.13
+62.5 0.11
+63 0.08
+63.5 0.06
+64 0.04
+64.5 0.03
+65 0.03
+65.5 0.03
+66 0.03
+66.5 0.03
+67 0.03
+67.5 0.03
+68 0.03
+68.5 0.03
+69 0.02
+69.5 0.02
+70 0.02
+70.5 0.01
+71 0.01
+71.5 0.01
+72 0.02
+72.5 0.02
+73 0.02
+73.5 0.02
+74 0.02
+74.5 0.02
+75 0.02
+75.5 0.02
+76 0.02
+76.5 0.02
+77 0.02
+77.5 0.01
+78 0.01
+78.5 0.01
+79 0.01
+79.5 0.01
+80 0.01
+80.5 0.01
+81 0.01
+81.5 0.01
+82 0
+82.5 0
+83 0
+83.5 0
+84 0
+84.5 0
+85 0
+85.5 0
+86 0
+86.5 0
+87 0
+87.5 0
+88 0
+88.5 0
+89 0
+89.5 0
+90 0
--- /dev/null
+15.000 ; Earth Dielectric Constant (Relative permittivity)
+0.005 ; Earth Conductivity (Siemens per meter)
+301.000 ; Atmospheric Bending Constant (N-Units)
+605.000 ; Frequency in MHz (20 MHz to 20 GHz)
+5 ; Radio Climate
+0 ; Polarization (0 = Horizontal, 1 = Vertical)
+0.50 ; Fraction of situations
+0.90 ; Fraction of time
+650000 ; ERP in watts
+
+Please consult SPLAT! documentation for the meaning and use of this data.
--- /dev/null
+WNJU-DT
+40 48 8.0
+74 14 47.0
+98.5 meters
+
--- /dev/null
+; SPLAT! Auto-generated Signal Color Definition ("wnju-dt.scf") File
+;
+; Format for the parameters held in this file is as follows:
+;
+; dBuV/m: red, green, blue
+;
+; ...where "dBuV/m" is the signal strength (in dBuV/m) and
+; "red", "green", and "blue" are the corresponding RGB color
+; definitions ranging from 0 to 255 for the region specified.
+;
+; The following parameters may be edited and/or expanded
+; for future runs of SPLAT! A total of 32 contour regions
+; may be defined in this file.
+;
+;
+108: 255, 0, 0 ; City Grade +60dB
+ 98: 255, 165, 0 ; City Grade +50dB
+ 88: 255, 206, 0 ; City Grade +40dB
+ 78: 255, 255, 0 ; City Grade +30dB
+ 68: 184, 255, 0 ; City Grade +20dB
+ 58: 0, 255, 0 ; City Grade +10dB
+ 48: 0, 208, 0 ; City Grade
+ 41: 0, 196, 196 ; Service Threshold
+++ /dev/null
-char smallfont[10][9][7] = {
- { {0,1,1,1,1,1}, /* 0 */
- {1,1,0,0,0,1,1},
- {1,1,0,0,1,1,1},
- {1,1,0,1,1,1,1},
- {1,1,0,1,0,1,1},
- {1,1,1,1,0,1,1},
- {1,1,1,0,0,1,1},
- {1,1,0,0,0,1,1},
- {0,1,1,1,1,1} },
- { {0,0,0,1}, /* 1 */
- {0,0,1,1},
- {1,1,1,1},
- {0,0,1,1},
- {0,0,1,1},
- {0,0,1,1},
- {0,0,1,1},
- {0,0,1,1},
- {1,1,1,1,1,1} },
- { {0,1,1,1,1}, /* 2 */
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {0,0,0,0,1,1},
- {0,0,0,1,1},
- {0,0,1,1},
- {0,1,1},
- {1,1,0,0,1,1},
- {1,1,1,1,1,1} },
- { {0,1,1,1,1}, /* 3 */
- {1,1,0,0,1,1},
- {0,0,0,0,1,1},
- {0,0,0,0,1,1},
- {0,0,0,1,1},
- {0,0,0,0,1,1},
- {0,0,0,0,1,1},
- {1,1,0,0,1,1},
- {0,1,1,1,1} },
- { {0,0,0,0,1,1}, /* 4 */
- {0,0,0,1,1,1},
- {0,0,1,1,1,1},
- {0,1,1,0,1,1},
- {1,1,1,1,1,1,1},
- {0,0,0,0,1,1},
- {0,0,0,0,1,1},
- {0,0,0,0,1,1},
- {0,0,0,1,1,1,1} },
- { {1,1,1,1,1,1}, /* 5 */
- {1,1},
- {1,1},
- {1,1},
- {1,1,1,1,1},
- {0,0,0,0,1,1},
- {0,0,0,0,1,1},
- {1,1,0,0,1,1},
- {0,1,1,1,1} },
- { {0,0,1,1,1}, /* 6 */
- {0,1,1},
- {1,1},
- {1,1},
- {1,1,1,1,1},
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {0,1,1,1,1} },
- { {1,1,1,1,1,1,1}, /* 7 */
- {1,1,0,0,0,1,1},
- {1,1,0,0,0,1,1},
- {0,0,0,0,0,1,1},
- {0,0,0,0,1,1},
- {0,0,0,1,1},
- {0,0,1,1},
- {0,0,1,1},
- {0,0,1,1} },
- { {0,1,1,1,1}, /* 8 */
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {0,1,1,1,1},
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {0,1,1,1,1} },
- { {0,1,1,1,1}, /* 9 */
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {1,1,0,0,1,1},
- {0,1,1,1,1,1},
- {0,0,0,1,1},
- {0,0,0,1,1},
- {0,0,1,1},
- {0,1,1,1} } };
-
+++ /dev/null
-Begin3
-Title: SPLAT!
-Version: 1.2.0b
-Entered-date: 15MAR07
-Description: SPLAT! is a terrestrial RF propagation analysis tool for
- the spectrum between 20 MHz and 20 GHz. SPLAT! provides
- site engineering data such as the great circle distances
- and bearings between sites, antenna elevation angles
- (uptilt), depression angles (downtilt), antenna height
- above mean sea level, antenna height above average
- terrain, bearings and distances to known obstructions,
- path loss based on the Longley-Rice Irregular Terrain
- Model, and minimum antenna height requirements needed to
- establish first Fresnel zone clearance and line-of-sight
- RF paths absent of obstructions due to terrain. SPLAT!
- 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. Applications of SPLAT! include
- site engineering, wireless network design, amateur
- radio communications, frequency coordination,
- communication system design, and terrestrial
- television and radio broadcasting. SPLAT! requires
- gnuplot version 3.7, libbzip-1.0.1 or later, and
- zlib, as well as an application capable of displaying
- PPM graphic files (xv, ImageMagick, xpaint, The GIMP, etc.).
-Keywords: Terrain analysis, site engineering, Longley-Rice path
- loss, TV/FM radio broadcasting, TV/FM radio reception,
- amateur radio, wireless WAN analysis and design
-Author: kd2bd@amsat.org (John A. Magliacane) (Creator, Lead Developer)
- mcdonald@scs.uiuc.edu (Doug McDonald) (L-R Model Integration)
- ronbentley@earthlink.net (Ron Bentley) (Fresnel Zone Plotting)
-Maintained-by: kd2bd@amsat.org (John A. Magliacane)
-Primary-site: ftp.ibiblio.org /pub/Linux/apps/ham/splat-1.2.0b.tar.gz
-Original-site: http://www.qsl.net/kd2bd/splat.html
-Platforms: Linux/Unix
-Copying-policy: GPL
-End
--- /dev/null
+Begin3
+Title: SPLAT!
+Version: 1.2.1
+Entered-date: 19OCT07
+Description: SPLAT! is a terrestrial RF propagation analysis tool for
+ the spectrum between 20 MHz and 20 GHz. SPLAT! provides
+ site engineering data such as the great circle distances
+ and bearings between sites, antenna elevation angles
+ (uptilt), depression angles (downtilt), antenna height
+ above mean sea level, antenna height above average
+ terrain, bearings and distances to known obstructions,
+ path loss and signal strength based on the Longley-Rice
+ Irregular Terrain Model, and minimum antenna height
+ requirements needed to establish first Fresnel zone
+ clearance and line-of-sight RF paths absent of obstructions
+ due to terrain. SPLAT! 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.
+ Applications of SPLAT! include site engineering, wireless
+ network design, amateur radio communications, frequency
+ coordination, communication system design, and terrestrial
+ television and radio broadcasting. SPLAT! requires
+ gnuplot version 3.7, libbzip-1.0.1 or later, and
+ zlib, as well as an application capable of displaying
+ PPM graphic files (xv, ImageMagick, xpaint, The GIMP, etc.).
+Keywords: Terrain analysis, site engineering, Longley-Rice path
+ loss, signal strength contours, TV/FM radio broadcasting,
+ TV/FM radio reception, LPFM, HDTV, amateur radio, wireless
+ WAN analysis and design
+Author: kd2bd@amsat.org (John A. Magliacane) (Creator, Lead Developer)
+ mcdonald@scs.uiuc.edu (Doug McDonald) (L-R Model Integration)
+ ronbentley@embarqmail.com (Ron Bentley) (Fresnel Zone Plotting)
+Maintained-by: kd2bd@amsat.org (John A. Magliacane)
+Primary-site: ftp.ibiblio.org /pub/Linux/apps/ham/splat-1.2.1.tar.gz
+Original-site: http://www.qsl.net/kd2bd/splat.html
+Platforms: Linux/Unix
+Copying-policy: GPL
+End
-/****************************************************************************
-* SPLAT: An RF Signal Propagation Loss and Terrain Analysis Tool *
-* Last update: 15-Mar-2007 *
-*****************************************************************************
-* Project started in 1997 by John A. Magliacane, KD2BD *
-*****************************************************************************
-* *
-* Extensively modified by J. D. McDonald in Jan. 2004 to include *
-* the Longley-Rice propagation model using C++ code from NTIA/ITS. *
-* *
-* See: http://flattop.its.bldrdoc.gov/itm.html *
-* *
-*****************************************************************************
-* *
-* This program is free software; you can redistribute it and/or modify it *
-* 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. *
-* *
-* This program is distributed in the hope that it will useful, but WITHOUT *
-* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or *
-* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License *
-* for more details. *
-* *
-*****************************************************************************
- g++ -Wall -O3 -s -lm -lbz2 -fomit-frame-pointer itm.cpp splat.cpp -o splat
-*****************************************************************************/
+/****************************************************************************\
+* SPLAT!: An RF Signal Path Loss And Terrain Analysis Tool *
+******************************************************************************
+* Project started in 1997 by John A. Magliacane, KD2BD *
+* Last update: 19-Oct-2007 *
+******************************************************************************
+* Please consult the documentation for a complete list of *
+* individuals who have contributed to this project. *
+******************************************************************************
+* *
+* This program is free software; you can redistribute it and/or modify it *
+* 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. *
+* *
+* This program is distributed in the hope that it will useful, but WITHOUT *
+* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or *
+* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License *
+* for more details. *
+* *
+******************************************************************************
+* g++ -Wall -O3 -s -lm -lbz2 -fomit-frame-pointer itm.cpp splat.cpp -o splat *
+\****************************************************************************/
#include <stdio.h>
#include <math.h>
#include <bzlib.h>
#include <unistd.h>
#include "fontdata.h"
-#include "smallfont.h"
#define GAMMA 2.5
-#define MAXSLOTS 9
+#define MAXPAGES 9
#define BZBUFFER 65536
-#if MAXSLOTS==4
+#if MAXPAGES==4
#define ARRAYSIZE 4950
#endif
-#if MAXSLOTS==9
+#if MAXPAGES==9
#define ARRAYSIZE 10870
#endif
-#if MAXSLOTS==16
+#if MAXPAGES==16
#define ARRAYSIZE 19240
#endif
-#if MAXSLOTS==25
+#if MAXPAGES==25
#define ARRAYSIZE 30025
#endif
-char string[255], sdf_path[255], opened=0, *splat_version={"1.2.0b"};
+char string[255], sdf_path[255], opened=0, *splat_version={"1.2.1"};
double TWOPI=6.283185307179586, HALFPI=1.570796326794896,
PI=3.141592653589793, deg2rad=1.74532925199e-02,
EARTHRADIUS=20902230.97, METERS_PER_MILE=1609.344,
METERS_PER_FOOT=0.3048, KM_PER_MILE=1.609344, earthradius,
- max_range=0.0;
+ max_range=0.0, forced_erp=-1.0, fzone_clearance=0.6;
int min_north=90, max_north=-90, min_west=360, max_west=-1,
max_elevation=-32768, min_elevation=32768, bzerror, maxdB=230;
-unsigned char got_elevation_pattern=0, got_azimuth_pattern=0, metric=0;
+unsigned char got_elevation_pattern, got_azimuth_pattern, metric=0;
struct site { double lat;
double lon;
float alt;
char name[50];
+ char filename[255];
} site;
struct path { double lat[ARRAYSIZE];
int min_el;
short data[1200][1200];
unsigned char mask[1200][1200];
- } dem[MAXSLOTS];
+ unsigned char signal[1200][1200];
+ } dem[MAXPAGES];
struct LR { double eps_dielect;
double sgm_conductivity;
double frq_mhz;
double conf;
double rel;
+ double erp;
int radio_climate;
int pol;
float antenna_pattern[361][1001];
} LR;
+struct region { unsigned char color[32][3];
+ int level[32];
+ int levels;
+ } region;
+
double elev_l[ARRAYSIZE+10];
void point_to_point(double elev[], double tht_m, double rht_m,
return (string);
}
+int PutMask(double lat, double lon, int value)
+{
+ /* Lines, text, markings, and coverage areas are stored in a
+ mask that is combined with topology data when topographic
+ maps are generated by SPLAT!. This function sets and resets
+ bits in the mask based on the latitude and longitude of the
+ area pointed to. */
+
+ int x, y, indx;
+ char found;
+
+ for (indx=0, found=0; indx<MAXPAGES && found==0;)
+ if (lat>=(double)dem[indx].min_north && lat<=(double)dem[indx].max_north && lon>=(double)dem[indx].min_west && lon<=(double)dem[indx].max_west)
+ found=1;
+ else
+ indx++;
+
+ if (found)
+ {
+ x=(int)(1199.0*(lat-floor(lat)));
+ y=(int)(1199.0*(lon-floor(lon)));
+
+ dem[indx].mask[x][y]=value;
+
+ return (dem[indx].mask[x][y]);
+ }
+
+ else
+ return -1;
+}
+
int OrMask(double lat, double lon, int value)
{
/* Lines, text, markings, and coverage areas are stored in a
the mask based on the latitude and longitude of the area
pointed to. */
- int x, y, indx, minlat, minlon;
+ int x, y, indx;
char found;
- minlat=(int)floor(lat);
- minlon=(int)floor(lon);
-
- for (indx=0, found=0; indx<MAXSLOTS && found==0;)
- if (minlat==dem[indx].min_north && minlon==dem[indx].min_west)
+ for (indx=0, found=0; indx<MAXPAGES && found==0;)
+ if (lat>=(double)dem[indx].min_north && lat<=(double)dem[indx].max_north && lon>=(double)dem[indx].min_west && lon<=(double)dem[indx].max_west)
found=1;
else
indx++;
return (OrMask(lat,lon,0));
}
+int PutSignal(double lat, double lon, unsigned char signal)
+{
+ /* This function writes a signal level (0-255)
+ at the specified location for later recall. */
+
+ int x, y, indx;
+ char found;
+
+ for (indx=0, found=0; indx<MAXPAGES && found==0;)
+ if (lat>=(double)dem[indx].min_north && lat<=(double)dem[indx].max_north && lon>=(double)dem[indx].min_west && lon<=(double)dem[indx].max_west)
+ found=1;
+ else
+ indx++;
+
+ if (found)
+ {
+ x=(int)(1199.0*(lat-floor(lat)));
+ y=(int)(1199.0*(lon-floor(lon)));
+
+ dem[indx].signal[x][y]=signal;
+
+ return (dem[indx].signal[x][y]);
+ }
+
+ else
+ return 0;
+}
+
+unsigned char GetSignal(double lat, double lon)
+{
+ /* This function reads the signal level (0-255) at the
+ specified location that was previously written by the
+ complimentary PutSignal() function. */
+
+ int x, y, indx;
+ char found;
+
+ for (indx=0, found=0; indx<MAXPAGES && found==0;)
+ if (lat>=(double)dem[indx].min_north && lat<=(double)dem[indx].max_north && lon>=(double)dem[indx].min_west && lon<=(double)dem[indx].max_west)
+ found=1;
+ else
+ indx++;
+
+ if (found)
+ {
+ x=(int)(1199.0*(lat-floor(lat)));
+ y=(int)(1199.0*(lon-floor(lon)));
+
+ return (dem[indx].signal[x][y]);
+ }
+
+ else
+ return 0;
+}
+
double GetElevation(struct site location)
{
/* This function returns the elevation (in feet) of any location
Function returns -5000.0 for locations not found in memory. */
char found;
- int x, y, indx, minlat, minlon;
+ int x, y, indx;
double elevation;
elevation=-5000.0;
- minlat=(int)floor(location.lat);
- minlon=(int)floor(location.lon);
-
x=(int)(1199.0*(location.lat-floor(location.lat)));
y=(int)(1199.0*(location.lon-floor(location.lon)));
- for (indx=0, found=0; indx<MAXSLOTS && found==0; indx++)
+ for (indx=0, found=0; indx<MAXPAGES && found==0; indx++)
{
- if (minlat==dem[indx].min_north && minlon==dem[indx].min_west)
+ if (location.lat>=(double)dem[indx].min_north && location.lat<=(double)dem[indx].max_north && location.lon>=(double)dem[indx].min_west && location.lon<=(double)dem[indx].max_west)
{
-
elevation=3.28084*dem[indx].data[x][y];
found=1;
}
not found in memory. */
char found;
- int x, y, indx, minlat, minlon;
-
- minlat=(int)floor(lat);
- minlon=(int)floor(lon);
+ int x, y, indx;
x=(int)(1199.0*(lat-floor(lat)));
y=(int)(1199.0*(lon-floor(lon)));
- for (indx=0, found=0; indx<MAXSLOTS && found==0; indx++)
+ for (indx=0, found=0; indx<MAXPAGES && found==0; indx++)
{
- if (minlat==dem[indx].min_north && minlon==dem[indx].min_west)
+ if (lat>=(double)dem[indx].min_north && lat<=(double)dem[indx].max_north && lon>=(double)dem[indx].min_west && lon<=(double)dem[indx].max_west)
{
-
dem[indx].data[x][y]+=(short)rint(height);
found=1;
}
increment=total_distance/path_length; /* Miles per sample */
- for (distance=0, c=0; distance<=total_distance; distance+=increment)
+ for (distance=0, c=0; (distance<=total_distance && c<ARRAYSIZE); distance+=increment, c++)
{
beta=distance/3959.0;
lat2=asin(sin(lat1)*cos(beta)+cos(azimuth)*sin(beta)*cos(lat1));
lat2=lat2/deg2rad;
lon2=lon2/deg2rad;
- if (c<ARRAYSIZE)
- {
- path.lat[c]=lat2;
- path.lon[c]=lon2;
- tempsite.lat=lat2;
- tempsite.lon=lon2;
- path.elevation[c]=GetElevation(tempsite);
- path.distance[c]=distance;
- c++;
- }
+ path.lat[c]=lat2;
+ path.lon[c]=lon2;
+ tempsite.lat=lat2;
+ tempsite.lon=lon2;
+ path.elevation[c]=GetElevation(tempsite);
+ path.distance[c]=distance;
}
/* Make sure exact destination point is recorded at path.length-1 */
/* Anything else returns a 0.0 */
- if (bearing>360.0 || bearing<-90.0)
+ if (bearing>360.0 || bearing<-360.0)
bearing=0.0;
return bearing;
tempsite.lon=361.0;
tempsite.alt=0.0;
tempsite.name[0]=0;
+ tempsite.filename[0]=0;
fd=fopen(qthfile,"r");
fgets(string,49,fd);
tempsite.lon=ReadBearing(string);
+ if (tempsite.lon<0.0)
+ tempsite.lon+=360.0;
+
/* Antenna Height */
fgets(string,49,fd);
fclose(fd);
must be converted to feet before exiting. */
for (x=0; string[x]!='M' && string[x]!='m' && string[x]!=0 && x<48; x++);
+
if (string[x]=='M' || string[x]=='m')
{
string[x]=0;
string[x]=0;
sscanf(string,"%f",&tempsite.alt);
}
+
+ for (x=0; x<254 && qthfile[x]!=0; x++)
+ tempsite.filename[x]=qthfile[x];
+
+ tempsite.filename[x]=0;
}
return tempsite;
float az, xx, elevation, amplitude, rotation, valid1, valid2,
delta, azimuth[361], azimuth_pattern[361], el_pattern[10001],
elevation_pattern[361][1001], slant_angle[361], tilt,
- mechanical_tilt, tilt_azimuth, tilt_increment, sum;
+ mechanical_tilt=0.0, tilt_azimuth, tilt_increment, sum;
FILE *fd=NULL;
unsigned char read_count[10001];
rotation=0.0;
+ got_azimuth_pattern=0;
+ got_elevation_pattern=0;
+
/* Load .az antenna pattern file */
fd=fopen(azfile,"r");
dem[] structure. */
int x, y, data, indx, minlat, minlon, maxlat, maxlon;
- char found, free_slot=0, line[20], sdf_file[255],
+ char found, free_page=0, line[20], sdf_file[255],
path_plus_name[255];
FILE *fd;
/* Is it already in memory? */
- for (indx=0, found=0; indx<MAXSLOTS && found==0; indx++)
+ for (indx=0, found=0; indx<MAXPAGES && found==0; indx++)
{
if (minlat==dem[indx].min_north && minlon==dem[indx].min_west && maxlat==dem[indx].max_north && maxlon==dem[indx].max_west)
found=1;
if (found==0)
{
- for (indx=0, free_slot=0; indx<MAXSLOTS && free_slot==0; indx++)
+ for (indx=0, free_page=0; indx<MAXPAGES && free_page==0; indx++)
if (dem[indx].max_north==-90)
- free_slot=1;
+ free_page=1;
}
indx--;
- if (free_slot && found==0 && indx>=0 && indx<MAXSLOTS)
+ if (free_page && found==0 && indx>=0 && indx<MAXPAGES)
{
/* Search for SDF file in current working directory first */
if (fd!=NULL)
{
- fprintf(stdout,"Loading \"%s\" into slot %d...",path_plus_name,indx+1);
+ fprintf(stdout,"Loading \"%s\" into page %d...",path_plus_name,indx+1);
fflush(stdout);
fgets(line,19,fd);
for (y=0; y<1200; y++)
{
fgets(line,19,fd);
- sscanf(line,"%d",&data);
+ data=atoi(line);
dem[indx].data[x][y]=data;
+ dem[indx].signal[x][y]=0;
+ dem[indx].mask[x][y]=0;
if (data>dem[indx].max_el)
dem[indx].max_el=data;
stored in the first available dem[] structure. */
int x, y, data, indx, minlat, minlon, maxlat, maxlon;
- char found, free_slot=0, sdf_file[255], path_plus_name[255];
+ char found, free_page=0, sdf_file[255], path_plus_name[255], *string;
FILE *fd;
BZFILE *bzfd;
/* Is it already in memory? */
- for (indx=0, found=0; indx<MAXSLOTS && found==0; indx++)
+ for (indx=0, found=0; indx<MAXPAGES && found==0; indx++)
{
if (minlat==dem[indx].min_north && minlon==dem[indx].min_west && maxlat==dem[indx].max_north && maxlon==dem[indx].max_west)
found=1;
if (found==0)
{
- for (indx=0, free_slot=0; indx<MAXSLOTS && free_slot==0; indx++)
+ for (indx=0, free_page=0; indx<MAXPAGES && free_page==0; indx++)
if (dem[indx].max_north==-90)
- free_slot=1;
+ free_page=1;
}
indx--;
- if (free_slot && found==0 && indx>=0 && indx<MAXSLOTS)
+ if (free_page && found==0 && indx>=0 && indx<MAXPAGES)
{
/* Search for SDF file in current working directory first */
if (fd!=NULL && bzerror==BZ_OK)
{
- fprintf(stdout,"Loading \"%s\" into slot %d...",path_plus_name,indx+1);
+ fprintf(stdout,"Loading \"%s\" into page %d...",path_plus_name,indx+1);
fflush(stdout);
sscanf(BZfgets(bzfd,255),"%d",&dem[indx].max_west);
for (x=0; x<1200; x++)
for (y=0; y<1200; y++)
{
- sscanf(BZfgets(bzfd,20),"%d",&data);
+ string=BZfgets(bzfd,20);
+ data=atoi(string);
dem[indx].data[x][y]=data;
+ dem[indx].signal[x][y]=0;
+ dem[indx].mask[x][y]=0;
if (data>dem[indx].max_el)
dem[indx].max_el=data;
requested must be entirely over water. */
int x, y, indx, minlat, minlon, maxlat, maxlon;
- char found, free_slot=0;
+ char found, free_page=0;
int return_value=-1;
/* Try to load an uncompressed SDF first. */
/* Is it already in memory? */
- for (indx=0, found=0; indx<MAXSLOTS && found==0; indx++)
+ for (indx=0, found=0; indx<MAXPAGES && found==0; indx++)
{
if (minlat==dem[indx].min_north && minlon==dem[indx].min_west && maxlat==dem[indx].max_north && maxlon==dem[indx].max_west)
found=1;
if (found==0)
{
- for (indx=0, free_slot=0; indx<MAXSLOTS && free_slot==0; indx++)
+ for (indx=0, free_page=0; indx<MAXPAGES && free_page==0; indx++)
if (dem[indx].max_north==-90)
- free_slot=1;
+ free_page=1;
}
indx--;
- if (free_slot && found==0 && indx>=0 && indx<MAXSLOTS)
+ if (free_page && found==0 && indx>=0 && indx<MAXPAGES)
{
- fprintf(stdout,"Region \"%s\" assumed as sea-level into slot %d...",name,indx+1);
+ fprintf(stdout,"Region \"%s\" assumed as sea-level into page %d...",name,indx+1);
fflush(stdout);
dem[indx].max_west=maxlon;
for (y=0; y<1200; y++)
{
dem[indx].data[x][y]=0;
+ dem[indx].signal[x][y]=0;
+ dem[indx].mask[x][y]=0;
if (dem[indx].min_el>0)
dem[indx].min_el=0;
{
fgets(input,78,fd);
- fprintf(stdout,"Reading \"%s\"... ",filename);
+ fprintf(stdout,"\nReading \"%s\"... ",filename);
fflush(stdout);
while (fd!=NULL && feof(fd)==0)
city_site.lon=ReadBearing(str[2]);
city_site.alt=0.0;
+ if (city_site.lon<0.0)
+ city_site.lon+=360.0;
+
PlaceMarker(city_site);
fgets(input,78,fd);
}
fclose(fd);
- fprintf(stdout,"Done!\n");
+ fprintf(stdout,"Done!");
fflush(stdout);
}
if (pointer!=NULL)
*pointer=0;
- fprintf(stdout,"Reading \"%s\"... ",filename);
+ fprintf(stdout,"\nReading \"%s\"... ",filename);
fflush(stdout);
while (feof(fd1)==0)
latitude=ReadBearing(str[0]);
longitude=ReadBearing(str[1]);
+ if (longitude<0.0)
+ longitude+=360.0;
+
/* Remove <CR> and/or <LF> from antenna height string */
for (i=0; str[2][i]!=13 && str[2][i]!=10 && str[2][i]!=0; i++);
fclose(fd2);
close(fd);
- fprintf(stdout,"Done!\n");
+ fprintf(stdout,"Done!");
fflush(stdout);
fd1=fopen(tempname,"r");
}
else
- fprintf(stderr,"*** ERROR: \"%s\": not found!\n",filename);
+ fprintf(stderr,"\n*** ERROR: \"%s\": not found!",filename);
}
void LoadBoundaries(char *filename)
{
fgets(string,78,fd);
- fprintf(stdout,"Reading \"%s\"... ",filename);
+ fprintf(stdout,"\nReading \"%s\"... ",filename);
fflush(stdout);
do
fclose(fd);
- fprintf(stdout,"Done!\n");
+ fprintf(stdout,"Done!");
fflush(stdout);
}
else
- fprintf(stderr,"*** ERROR: \"%s\": not found!\n",filename);
+ fprintf(stderr,"\n*** ERROR: \"%s\": not found!",filename);
}
-void ReadLRParm(char *txsite_filename)
+char ReadLRParm(struct site txsite, char forced_read)
{
/* This function reads Longley-Rice parameter data for the
transmitter site. The file name is the same as the txsite,
except the filename extension is .lrp. If the needed file
is not found, then the file "splat.lrp" is read from the
- current working directory. Failure to load this file will
- result in the default parameters hard coded into this
- function to be used and written to "splat.lrp". */
+ current working directory. Failure to load this file under
+ a forced_read condition will result in the default parameters
+ hard coded into this function to be used and written to
+ "splat.lrp". */
double din;
- char filename[255], string[80], *pointer=NULL;
+ char filename[255], string[80], *pointer=NULL, return_value=0;
int iin, ok=0, x;
FILE *fd=NULL, *outfile=NULL;
- /* Default parameters in case things go bad */
+ /* Default parameters */
- LR.eps_dielect=15.0;
- LR.sgm_conductivity=0.005;
- LR.eno_ns_surfref=301.0;
- LR.frq_mhz=300.0;
- LR.radio_climate=5;
+ LR.eps_dielect=0.0;
+ LR.sgm_conductivity=0.0;
+ LR.eno_ns_surfref=0.0;
+ LR.frq_mhz=0.0;
+ LR.radio_climate=0;
LR.pol=0;
- LR.conf=0.50;
- LR.rel=0.50;
+ LR.conf=0.0;
+ LR.rel=0.0;
+ LR.erp=0.0;
- /* Modify txsite filename to one with a .lrp extension. */
+ /* Generate .lrp filename from txsite filename. */
- strncpy(filename,txsite_filename,255);
-
- for (x=0; filename[x]!='.' && filename[x]!=0 && filename[x]!='\n' && x<249; x++);
+ for (x=0; txsite.filename[x]!='.' && txsite.filename[x]!=0 && x<250; x++)
+ filename[x]=txsite.filename[x];
filename[x]='.';
filename[x+1]='l';
ok=sscanf(string,"%lf", &din);
}
- fclose(fd);
-
if (ok)
{
LR.rel=din;
- LoadPAT(filename);
+ din=0.0;
+ return_value=1;
+
+ if (fgets(string,80,fd)!=NULL)
+ {
+ pointer=strchr(string,':');
+
+ if (pointer!=NULL)
+ *pointer=0;
+
+ if (sscanf(string,"%lf", &din))
+ LR.erp=din;
+ }
}
+
+ fclose(fd);
+
+ if (forced_erp!=-1.0)
+ LR.erp=forced_erp;
+
+ if (ok)
+ LoadPAT(filename);
}
- if (fd==NULL)
+ if (fd==NULL && forced_read)
{
- /* Create a "splat.lrp" file since one
- could not be successfully loaded. */
+ /* Assign some default parameters
+ for use in this run. */
+
+ LR.eps_dielect=15.0;
+ LR.sgm_conductivity=0.005;
+ LR.eno_ns_surfref=301.0;
+ LR.frq_mhz=300.0;
+ LR.radio_climate=5;
+ LR.pol=0;
+ LR.conf=0.50;
+ LR.rel=0.50;
+ LR.erp=0.0;
+
+ /* Write them to a "splat.lrp" file. */
outfile=fopen("splat.lrp","w");
fprintf(outfile,"%d\t; Radio Climate\n",LR.radio_climate);
fprintf(outfile,"%d\t; Polarization (0 = Horizontal, 1 = Vertical)\n", LR.pol);
fprintf(outfile,"%.2f\t; Fraction of situations\n",LR.conf);
- fprintf(outfile, "%.2f\t; Fraction of time\n",LR.rel);
+ fprintf(outfile,"%.2f\t; Fraction of time\n",LR.rel);
+ fprintf(outfile,"%.2f\t; Transmitter Effective Radiated Power in Watts (optional)\n",LR.erp);
fprintf(outfile,"\nPlease consult SPLAT! documentation for the meaning and use of this data.\n");
fclose(outfile);
- fprintf(stderr,"\n%c*** There were problems reading your \"%s\" file! ***\nA \"splat.lrp\" file was written to your directory with default data.\n",7,filename);
+ return_value=1;
+
+ fprintf(stderr,"\n\n%c*** There were problems reading your \"%s\" file! ***\nA \"splat.lrp\" file was written to your directory with default data.\n",7,filename);
}
- if (fd==NULL || ok==0)
+ else if (forced_read==0)
+ return_value=0;
+
+ if (forced_read && (fd==NULL || ok==0))
+ {
+ LR.eps_dielect=15.0;
+ LR.sgm_conductivity=0.005;
+ LR.eno_ns_surfref=301.0;
+ LR.frq_mhz=300.0;
+ LR.radio_climate=5;
+ LR.pol=0;
+ LR.conf=0.50;
+ LR.rel=0.50;
+ LR.erp=0.0;
+
fprintf(stderr,"Longley-Rice default parameters have been assumed for this analysis.\n");
+
+ return_value=1;
+ }
+
+ return (return_value);
}
void PlotPath(struct site source, struct site destination, char mask_value)
}
}
-void PlotLRPath(struct site source, struct site destination, FILE *fd)
+void PlotLRPath(struct site source, struct site destination, unsigned char mask_value, FILE *fd)
{
/* This function plots the RF path loss between source and
destination points based on the Longley-Rice propagation
model, taking into account antenna pattern data, if available. */
+ int x, y, ifs, ofs, errnum;
char block=0, strmode[100];
- int x, y, errnum;
double loss, azimuth, pattern=0.0,
- source_alt, dest_alt, source_alt2, dest_alt2,
- cos_xmtr_angle, cos_test_angle=0.0, test_alt,
- elevation, distance=0.0, four_thirds_earth;
+ xmtr_alt, dest_alt, xmtr_alt2, dest_alt2,
+ cos_rcvr_angle, cos_test_angle=0.0, test_alt,
+ elevation=0.0, distance=0.0, four_thirds_earth,
+ field_strength=0.0;
struct site temp;
ReadPath(source,destination);
/* Process this point only if it
has not already been processed. */
- if (GetMask(path.lat[y],path.lon[y])==0)
+ if ((GetMask(path.lat[y],path.lon[y])&248)!=(mask_value<<3))
{
distance=5280.0*path.distance[y];
- source_alt=four_thirds_earth+source.alt+path.elevation[0];
+ xmtr_alt=four_thirds_earth+source.alt+path.elevation[0];
dest_alt=four_thirds_earth+destination.alt+path.elevation[y];
dest_alt2=dest_alt*dest_alt;
- source_alt2=source_alt*source_alt;
+ xmtr_alt2=xmtr_alt*xmtr_alt;
/* Calculate the cosine of the elevation of
the receiver as seen by the transmitter. */
- cos_xmtr_angle=((source_alt2)+(distance*distance)-(dest_alt2))/(2.0*source_alt*distance);
+ cos_rcvr_angle=((xmtr_alt2)+(distance*distance)-(dest_alt2))/(2.0*xmtr_alt*distance);
+
+ if (cos_rcvr_angle>1.0)
+ cos_rcvr_angle=1.0;
+
+ if (cos_rcvr_angle<-1.0)
+ cos_rcvr_angle=-1.0;
if (got_elevation_pattern || fd!=NULL)
{
- /* If no antenna elevation pattern is available, and
- no output file is designated, the following code
- that determines the elevation angle to the first
- obstruction along the path is bypassed. */
+ /* Determine the elevation angle to the first obstruction
+ along the path IF elevation pattern data is available
+ or an output (.plo) file has been designated. */
for (x=2, block=0; (x<y && block==0); x++)
{
distance=5280.0*path.distance[x];
+
test_alt=four_thirds_earth+path.elevation[x];
/* Calculate the cosine of the elevation
angle of the terrain (test point)
as seen by the transmitter. */
- cos_test_angle=((source_alt2)+(distance*distance)-(test_alt*test_alt))/(2.0*source_alt*distance);
+ cos_test_angle=((xmtr_alt2)+(distance*distance)-(test_alt*test_alt))/(2.0*xmtr_alt*distance);
+
+ if (cos_test_angle>1.0)
+ cos_test_angle=1.0;
+
+ if (cos_test_angle<-1.0)
+ cos_test_angle=-1.0;
/* Compare these two angles to determine if
an obstruction exists. Since we're comparing
the cosines of these angles rather than
the angles themselves, the sense of the
following "if" statement is reversed from
- what it would be if the angles themselves
+ what it would be if the angles themselves
were compared. */
- if (cos_xmtr_angle>cos_test_angle)
+ if (cos_rcvr_angle>cos_test_angle)
block=1;
}
- /* At this point, we have the elevation angle
- to the first obstruction (if it exists). */
+ if (block)
+ elevation=((acos(cos_test_angle))/deg2rad)-90.0;
+ else
+ elevation=((acos(cos_rcvr_angle))/deg2rad)-90.0;
}
/* Determine attenuation for each point along the
LR.radio_climate, LR.pol, LR.conf, LR.rel, loss,
strmode, errnum);
- if (block)
- elevation=((acos(cos_test_angle))/deg2rad)-90.0;
-
- else
- elevation=((acos(cos_xmtr_angle))/deg2rad)-90.0;
-
temp.lat=path.lat[y];
temp.lon=path.lon[y];
azimuth=(Azimuth(source,temp));
- if (fd!=NULL)
- {
- /* Write path loss data to output file */
+ /* Write path loss data to output file */
- fprintf(fd,"%.7f, %.7f, %.3f, %.3f, %.2f\n",path.lat[y], path.lon[y], azimuth, elevation, loss);
- }
+ if (fd!=NULL)
+ fprintf(fd,"%.7f, %.7f, %.3f, %.3f, %.2f",path.lat[y], path.lon[y], azimuth, elevation, loss);
/* Integrate the antenna's radiation
pattern into the overall path loss. */
{
pattern=20.0*log10(pattern);
loss-=pattern;
+
+ if (fd!=NULL && (got_elevation_pattern || got_azimuth_pattern))
+ fprintf(fd,", %.2f",loss);
}
}
- if (loss>225.0)
- loss=225.0;
+ if (LR.erp!=0.0)
+ {
+ field_strength=(137.26+(20.0*log10(LR.frq_mhz))-loss)+(10.0*log10(LR.erp/1000.0));
+
+ ifs=100+(int)rint(field_strength);
- if (loss<75.0)
- loss=75.0;
+ if (ifs<0)
+ ifs=0;
- loss-=75.0;
- loss/=10.0;
- loss+=1.0;
+ if (ifs>255)
+ ifs=255;
+
+ ofs=GetSignal(path.lat[y],path.lon[y]);
+
+ if (ofs>ifs)
+ ifs=ofs;
+
+ PutSignal(path.lat[y],path.lon[y],(unsigned char)ifs);
- OrMask(path.lat[y],path.lon[y],((unsigned char)(loss))<<3);
- }
+ if (fd!=NULL)
+ fprintf(fd,", %.3f",field_strength);
+ }
+
+ else
+ {
+ if (loss>255)
+ ifs=255;
+ else
+ ifs=(int)rint(loss);
+
+ ofs=GetSignal(path.lat[y],path.lon[y]);
+
+ if (ofs<ifs && ofs!=0)
+ ifs=ofs;
+
+ PutSignal(path.lat[y],path.lon[y],(unsigned char)ifs);
+ }
+
+ if (fd!=NULL)
+ {
+ if (block)
+ fprintf(fd," *");
- else if (GetMask(path.lat[y],path.lon[y])==0 && path.distance[y]>max_range)
- OrMask(path.lat[y],path.lon[y],1);
+ fprintf(fd,"\n");
+ }
+
+ /* Mark this point as being analyzed */
+
+ PutMask(path.lat[y],path.lon[y],(GetMask(path.lat[y],path.lon[y])&7)+mask_value<<3);
+ }
}
}
is later invoked. */
float lat, lon, one_pixel;
- static unsigned char mask_value;
+ static unsigned char mask_value=1;
int z, count;
struct site edge;
unsigned char symbol[4], x;
- /* Initialize mask_value */
-
- if (mask_value!=8 && mask_value!=16 && mask_value!=32)
- mask_value=1;
-
one_pixel=1.0/1200.0;
symbol[0]='.';
count=0;
- fprintf(stdout,"\nComputing line-of-sight coverage of %s with an RX antenna\nat %.2f %s AGL:\n\n 0%c to 25%c ",source.name,metric?altitude*METERS_PER_FOOT:altitude,metric?"meters":"feet",37,37);
+ fprintf(stdout,"\n\nComputing line-of-sight coverage of \"%s\" with an RX antenna\nat %.2f %s AGL...\n\n 0%c to 25%c ",source.name,metric?altitude*METERS_PER_FOOT:altitude,metric?"meters":"feet",37,37);
fflush(stdout);
/* 18.75=1200 pixels/degree divided by 64 loops
topographic map based on a receiver located at
the specified altitude (in feet AGL). Results
are stored in memory, and written out in the form
- of a topographic map when the WritePPMLR() function
- is later invoked. */
+ of a topographic map when the WritePPMLR() or
+ WritePPMSS() functions are later invoked. */
int z, count;
struct site edge;
float lat, lon, one_pixel;
- unsigned char symbol[4], x;
+ unsigned char x, symbol[4];
+ static unsigned char mask_value=1;
FILE *fd=NULL;
one_pixel=1.0/1200.0;
count=0;
- fprintf(stdout,"\nComputing Longley-Rice coverage of %s ", source.name);
+ fprintf(stdout,"\n\nComputing Longley-Rice contours of \"%s\" ", source.name);
- fprintf(stdout,"out to a radius\nof %.2f %s with an RX antenna at %.2f %s AGL:\n\n 0%c to 25%c ",metric?max_range*KM_PER_MILE:max_range,metric?"kilometers":"miles",metric?altitude*METERS_PER_FOOT:altitude,metric?"meters":"feet",37,37);
+ fprintf(stdout,"out to a radius\nof %.2f %s with an RX antenna at %.2f %s AGL...\n\n 0%c to 25%c ",metric?max_range*KM_PER_MILE:max_range,metric?"kilometers":"miles",metric?altitude*METERS_PER_FOOT:altitude,metric?"meters":"feet",37,37);
fflush(stdout);
if (plo_filename[0]!=0)
edge.lon=lon;
edge.alt=altitude;
- PlotLRPath(source,edge,fd);
+ PlotLRPath(source,edge,mask_value,fd);
count++;
if (count==z)
edge.lon=min_west;
edge.alt=altitude;
- PlotLRPath(source,edge,fd);
+ PlotLRPath(source,edge,mask_value,fd);
count++;
if (count==z)
edge.lon=lon;
edge.alt=altitude;
- PlotLRPath(source,edge,fd);
+ PlotLRPath(source,edge,mask_value,fd);
count++;
if (count==z)
edge.lon=max_west;
edge.alt=altitude;
- PlotLRPath(source,edge,fd);
+ PlotLRPath(source,edge,mask_value,fd);
count++;
if (count==z)
fprintf(stdout,"\nDone!\n");
fflush(stdout);
+
+ if (mask_value<30)
+ mask_value++;
}
-void WritePPM(char *filename, unsigned char geo)
+void LoadSignalColors(struct site xmtr)
{
- /* This function generates a topographic map in Portable Pix Map
- (PPM) format based on logarithmically scaled topology data,
- as well as the content of flags held in the mask[][] array.
- The image created is rotated counter-clockwise 90 degrees
- from its representation in dem[][] so that north points
- up and east points right in the image generated. */
-
- char mapfile[255], geofile[255];
- unsigned char found, mask;
- unsigned width, height, output;
- int indx, x, y, x0=0, y0=0, minlat, minlon;
- float lat, lon, one_pixel, conversion, one_over_gamma;
- FILE *fd;
+ int x, y, ok, val[4];
+ char filename[255], string[80], *pointer=NULL;
+ FILE *fd=NULL;
- one_pixel=1.0/1200.0;
- one_over_gamma=1.0/GAMMA;
- conversion=255.0/pow((double)(max_elevation-min_elevation),one_over_gamma);
+ for (x=0; xmtr.filename[x]!='.' && xmtr.filename[x]!=0 && x<250; x++)
+ filename[x]=xmtr.filename[x];
- width=(unsigned)(1200*ReduceAngle(max_west-min_west));
- height=(unsigned)(1200*ReduceAngle(max_north-min_north));
+ filename[x]='.';
+ filename[x+1]='s';
+ filename[x+2]='c';
+ filename[x+3]='f';
+ filename[x+4]=0;
- if (filename[0]==0)
- strncpy(mapfile, "map.ppm\0",8);
- else
- {
- for (x=0; filename[x]!='.' && filename[x]!=0 && x<250; x++)
- {
- mapfile[x]=filename[x];
- geofile[x]=filename[x];
- }
+ /* Default values */
+
+ region.level[0]=128;
+ region.color[0][0]=255;
+ region.color[0][1]=0;
+ region.color[0][2]=0;
+
+ region.level[1]=118;
+ region.color[1][0]=255;
+ region.color[1][1]=165;
+ region.color[1][2]=0;
+
+ region.level[2]=108;
+ region.color[2][0]=255;
+ region.color[2][1]=206;
+ region.color[2][2]=0;
+
+ region.level[3]=98;
+ region.color[3][0]=255;
+ region.color[3][1]=255;
+ region.color[3][2]=0;
+
+ region.level[4]=88;
+ region.color[4][0]=184;
+ region.color[4][1]=255;
+ region.color[4][2]=0;
+
+ region.level[5]=78;
+ region.color[5][0]=0;
+ region.color[5][1]=255;
+ region.color[5][2]=0;
+
+ region.level[6]=68;
+ region.color[6][0]=0;
+ region.color[6][1]=208;
+ region.color[6][2]=0;
+
+ region.level[7]=58;
+ region.color[7][0]=0;
+ region.color[7][1]=196;
+ region.color[7][2]=196;
+
+ region.level[8]=48;
+ region.color[8][0]=0;
+ region.color[8][1]=148;
+ region.color[8][2]=255;
+
+ region.level[9]=38;
+ region.color[9][0]=80;
+ region.color[9][1]=80;
+ region.color[9][2]=255;
+
+ region.level[10]=28;
+ region.color[10][0]=0;
+ region.color[10][1]=38;
+ region.color[10][2]=255;
+
+ region.level[11]=18;
+ region.color[11][0]=142;
+ region.color[11][1]=63;
+ region.color[11][2]=255;
+
+ region.level[12]=8;
+ region.color[12][0]=140;
+ region.color[12][1]=0;
+ region.color[12][2]=128;
+
+ region.levels=13;
+
+ fd=fopen("splat.scf","r");
- mapfile[x]='.';
- geofile[x]='.';
- mapfile[x+1]='p';
- geofile[x+1]='g';
- mapfile[x+2]='p';
- geofile[x+2]='e';
- mapfile[x+3]='m';
- geofile[x+3]='o';
- mapfile[x+4]=0;
- geofile[x+4]=0;
- }
+ if (fd==NULL)
+ fd=fopen(filename,"r");
- if (geo)
+ if (fd==NULL)
{
- fd=fopen(geofile,"wb");
+ fd=fopen(filename,"w");
- fprintf(fd,"FILENAME\t%s\n",mapfile);
- fprintf(fd,"#\t\tX\tY\tLong\t\tLat\n");
- fprintf(fd,"TIEPOINT\t0\t0\t%d.000\t\t%d.000\n",(max_west<180?-max_west:360-max_west),max_north);
- fprintf(fd,"TIEPOINT\t%u\t%u\t%d.000\t\t%d.000\n",width-1,height-1,(min_west<180?-min_west:360-min_west),min_north);
- fprintf(fd,"IMAGESIZE\t%u\t%u\n",width,height);
- fprintf(fd,"#\n# Auto Generated by SPLAT! v%s\n#\n",splat_version);
+ fprintf(fd,"; SPLAT! Auto-generated Signal Color Definition (\"%s\") File\n",filename);
+ fprintf(fd,";\n; Format for the parameters held in this file is as follows:\n;\n");
+ fprintf(fd,"; dBuV/m: red, green, blue\n;\n");
+ fprintf(fd,"; ...where \"dBuV/m\" is the signal strength (in dBuV/m) and\n");
+ fprintf(fd,"; \"red\", \"green\", and \"blue\" are the corresponding RGB color\n");
+ fprintf(fd,"; definitions ranging from 0 to 255 for the region specified.\n");
+ fprintf(fd,";\n; The following parameters may be edited and/or expanded\n");
+ fprintf(fd,"; for future runs of SPLAT! A total of 32 contour regions\n");
+ fprintf(fd,"; may be defined in this file.\n;\n;\n");
+
+ for (x=0; x<region.levels; x++)
+ fprintf(fd,"%3d: %3d, %3d, %3d\n",region.level[x], region.color[x][0], region.color[x][1], region.color[x][2]);
fclose(fd);
}
- fd=fopen(mapfile,"wb");
-
- fprintf(fd,"P6\n%u %u\n255\n",width,height);
-
- fprintf(stdout,"\nWriting \"%s\" (%ux%u pixmap image)... ",mapfile,width,height);
- fflush(stdout);
-
- for (y=0, lat=((double)max_north)-one_pixel; y<(int)height; y++, lat-=one_pixel)
+ else
{
- minlat=(int)floor(lat);
+ x=0;
+ fgets(string,80,fd);
- for (x=0, lon=((double)max_west)-one_pixel; x<(int)width; x++, lon-=one_pixel)
+ while (x<32 && feof(fd)==0)
{
- if (lon<0.0)
- lon+=360.0;
+ pointer=strchr(string,';');
- minlon=(int)floor(lon);
+ if (pointer!=NULL)
+ *pointer=0;
- for (indx=0, found=0; indx<MAXSLOTS && found==0;)
- if (minlat==dem[indx].min_north && minlon==dem[indx].min_west)
- found=1;
- else
- indx++;
+ ok=sscanf(string,"%d: %d, %d, %d", &val[0], &val[1], &val[2], &val[3]);
- if (found)
+ if (ok==4)
{
- x0=(int)(1199.0*(lat-floor(lat)));
- y0=(int)(1199.0*(lon-floor(lon)));
+ for (y=0; y<4; y++)
+ {
+ if (val[y]>255)
+ val[y]=255;
- mask=dem[indx].mask[x0][y0];
+ if (val[y]<0)
+ val[y]=0;
+ }
+
+ region.level[x]=val[0];
+ region.color[x][0]=val[1];
+ region.color[x][1]=val[2];
+ region.color[x][2]=val[3];
+ x++;
+ }
- if (mask&2)
- /* Text Labels: Red */
- fprintf(fd,"%c%c%c",255,0,0);
+ fgets(string,80,fd);
+ }
- else if (mask&4)
- /* County Boundaries: Light Cyan */
- fprintf(fd,"%c%c%c",128,128,255);
+ fclose(fd);
+ region.levels=x;
+ }
+}
- else switch (mask&57)
- {
- case 1:
- /* TX1: Green */
- fprintf(fd,"%c%c%c",0,255,0);
- break;
+void LoadLossColors(struct site xmtr)
+{
+ int x, y, ok, val[4];
+ char filename[255], string[80], *pointer=NULL;
+ FILE *fd=NULL;
- case 8:
- /* TX2: Cyan */
- fprintf(fd,"%c%c%c",0,255,255);
- break;
+ for (x=0; xmtr.filename[x]!='.' && xmtr.filename[x]!=0 && x<250; x++)
+ filename[x]=xmtr.filename[x];
- case 9:
- /* TX1 + TX2: Yellow */
- fprintf(fd,"%c%c%c",255,255,0);
- break;
+ filename[x]='.';
+ filename[x+1]='l';
+ filename[x+2]='c';
+ filename[x+3]='f';
+ filename[x+4]=0;
- case 16:
- /* TX3: Medium Violet */
- fprintf(fd,"%c%c%c",147,112,219);
- break;
+ /* Default values */
+
+ region.level[0]=80;
+ region.color[0][0]=255;
+ region.color[0][1]=0;
+ region.color[0][2]=0;
+
+ region.level[1]=90;
+ region.color[1][0]=255;
+ region.color[1][1]=128;
+ region.color[1][2]=0;
+
+ region.level[2]=100;
+ region.color[2][0]=255;
+ region.color[2][1]=165;
+ region.color[2][2]=0;
+
+ region.level[3]=110;
+ region.color[3][0]=255;
+ region.color[3][1]=206;
+ region.color[3][2]=0;
+
+ region.level[4]=120;
+ region.color[4][0]=255;
+ region.color[4][1]=255;
+ region.color[4][2]=0;
+
+ region.level[5]=130;
+ region.color[5][0]=184;
+ region.color[5][1]=255;
+ region.color[5][2]=0;
+
+ region.level[6]=140;
+ region.color[6][0]=0;
+ region.color[6][1]=255;
+ region.color[6][2]=0;
+
+ region.level[7]=150;
+ region.color[7][0]=0;
+ region.color[7][1]=208;
+ region.color[7][2]=0;
+
+ region.level[8]=160;
+ region.color[8][0]=0;
+ region.color[8][1]=196;
+ region.color[8][2]=196;
+
+ region.level[9]=170;
+ region.color[9][0]=0;
+ region.color[9][1]=148;
+ region.color[9][2]=255;
+
+ region.level[10]=180;
+ region.color[10][0]=80;
+ region.color[10][1]=80;
+ region.color[10][2]=255;
+
+ region.level[11]=190;
+ region.color[11][0]=0;
+ region.color[11][1]=38;
+ region.color[11][2]=255;
+
+ region.level[12]=200;
+ region.color[12][0]=142;
+ region.color[12][1]=63;
+ region.color[12][2]=255;
+
+ region.level[13]=210;
+ region.color[13][0]=196;
+ region.color[13][1]=54;
+ region.color[13][2]=255;
+
+ region.level[14]=220;
+ region.color[14][0]=255;
+ region.color[14][1]=0;
+ region.color[14][2]=255;
+
+ region.level[15]=230;
+ region.color[15][0]=255;
+ region.color[15][1]=194;
+ region.color[15][2]=204;
+
+ region.levels=16;
+
+ fd=fopen("splat.lcf","r");
+
+ if (fd==NULL)
+ fd=fopen(filename,"r");
+
+ if (fd==NULL)
+ {
+ fd=fopen(filename,"w");
+
+ fprintf(fd,"; SPLAT! Auto-generated Path-Loss Color Definition (\"%s\") File\n",filename);
+ fprintf(fd,";\n; Format for the parameters held in this file is as follows:\n;\n");
+ fprintf(fd,"; dB: red, green, blue\n;\n");
+ fprintf(fd,"; ...where \"dB\" is the path loss (in dB) and\n");
+ fprintf(fd,"; \"red\", \"green\", and \"blue\" are the corresponding RGB color\n");
+ fprintf(fd,"; definitions ranging from 0 to 255 for the region specified.\n");
+ fprintf(fd,";\n; The following parameters may be edited and/or expanded\n");
+ fprintf(fd,"; for future runs of SPLAT! A total of 32 contour regions\n");
+ fprintf(fd,"; may be defined in this file.\n;\n;\n");
+
+ for (x=0; x<region.levels; x++)
+ fprintf(fd,"%3d: %3d, %3d, %3d\n",region.level[x], region.color[x][0], region.color[x][1], region.color[x][2]);
+
+ fclose(fd);
+ }
+
+ else
+ {
+ x=0;
+ fgets(string,80,fd);
+
+ while (x<32 && feof(fd)==0)
+ {
+ pointer=strchr(string,';');
+
+ if (pointer!=NULL)
+ *pointer=0;
+
+ ok=sscanf(string,"%d: %d, %d, %d", &val[0], &val[1], &val[2], &val[3]);
+
+ if (ok==4)
+ {
+ for (y=0; y<4; y++)
+ {
+ if (val[y]>255)
+ val[y]=255;
+
+ if (val[y]<0)
+ val[y]=0;
+ }
+
+ region.level[x]=val[0];
+ region.color[x][0]=val[1];
+ region.color[x][1]=val[2];
+ region.color[x][2]=val[3];
+ x++;
+ }
+
+ fgets(string,80,fd);
+ }
+
+ fclose(fd);
+ region.levels=x;
+ }
+}
+
+void WritePPM(char *filename, unsigned char geo, unsigned char kml, unsigned char ngs)
+{
+ /* This function generates a topographic map in Portable Pix Map
+ (PPM) format based on logarithmically scaled topology data,
+ as well as the content of flags held in the mask[][] array.
+ The image created is rotated counter-clockwise 90 degrees
+ from its representation in dem[][] so that north points
+ up and east points right in the image generated. */
+
+ char mapfile[255], geofile[255], kmlfile[255];
+ unsigned char found, mask;
+ unsigned width, height, terrain;
+ int indx, x, y, x0=0, y0=0;
+ double lat, lon, one_pixel, conversion, one_over_gamma; /* USED to be float... */
+ FILE *fd;
+
+ one_pixel=1.0/1200.0;
+ one_over_gamma=1.0/GAMMA;
+ conversion=255.0/pow((double)(max_elevation-min_elevation),one_over_gamma);
+
+ width=(unsigned)(1200*ReduceAngle(max_west-min_west));
+ height=(unsigned)(1200*ReduceAngle(max_north-min_north));
+
+ if (filename[0]==0)
+ strncpy(filename, "map.ppm\0",8);
+
+ for (x=0; filename[x]!='.' && filename[x]!=0 && x<250; x++)
+ {
+ mapfile[x]=filename[x];
+ geofile[x]=filename[x];
+ kmlfile[x]=filename[x];
+ }
+
+ mapfile[x]='.';
+ geofile[x]='.';
+ kmlfile[x]='.';
+ mapfile[x+1]='p';
+ geofile[x+1]='g';
+ kmlfile[x+1]='k';
+ mapfile[x+2]='p';
+ geofile[x+2]='e';
+ kmlfile[x+2]='m';
+ mapfile[x+3]='m';
+ geofile[x+3]='o';
+ kmlfile[x+3]='l';
+ mapfile[x+4]=0;
+ geofile[x+4]=0;
+ kmlfile[x+4]=0;
+
+ if (kml==0 && geo)
+ {
+ fd=fopen(geofile,"wb");
+
+ fprintf(fd,"FILENAME\t%s\n",mapfile);
+ fprintf(fd,"#\t\tX\tY\tLong\t\tLat\n");
+ fprintf(fd,"TIEPOINT\t0\t0\t%d.000\t\t%d.000\n",(max_west<180?-max_west:360-max_west),max_north);
+ fprintf(fd,"TIEPOINT\t%u\t%u\t%d.000\t\t%d.000\n",width-1,height-1,(min_west<180?-min_west:360-min_west),min_north);
+ fprintf(fd,"IMAGESIZE\t%u\t%u\n",width,height);
+ fprintf(fd,"#\n# Auto Generated by SPLAT! v%s\n#\n",splat_version);
+
+ fclose(fd);
+ }
+
+ if (kml && geo==0)
+ {
+ fd=fopen(kmlfile,"wb");
+
+ fprintf(fd,"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n");
+ fprintf(fd,"<kml xmlns=\"http://earth.google.com/kml/2.1\">\n");
+ fprintf(fd," <Folder>\n");
+ fprintf(fd," <name>SPLAT!</name>\n");
+ fprintf(fd," <description>Line-of-Sight Overlay</description>\n");
+ fprintf(fd," <GroundOverlay>\n");
+ fprintf(fd," <name>SPLAT! Line-of-Sight Overlay</name>\n");
+ fprintf(fd," <description>SPLAT! Coverage</description>\n");
+ fprintf(fd," <Icon>\n");
+ fprintf(fd," <href>%s</href>\n",mapfile);
+ fprintf(fd," </Icon>\n");
+ fprintf(fd," <opacity>128</opacity>\n");
+ fprintf(fd," <LatLonBox>\n");
+ fprintf(fd," <north>%.5f</north>\n",(double)max_north-one_pixel);
+ fprintf(fd," <south>%.5f</south>\n",(double)min_north);
+ fprintf(fd," <east>%.5f</east>\n",((double)min_west<180.0?(double)-min_west:360.0-(double)min_west));
+ fprintf(fd," <west>%.5f</west>\n",(((double)max_west-one_pixel)<180.0?-((double)max_west-one_pixel):(360.0-(double)max_west-one_pixel)));
+ fprintf(fd," <rotation>0.0</rotation>\n");
+ fprintf(fd," </LatLonBox>\n");
+ fprintf(fd," </GroundOverlay>\n");
+ fprintf(fd," </Folder>\n");
+ fprintf(fd,"</kml>\n");
+
+ fclose(fd);
+ }
+
+ fd=fopen(mapfile,"wb");
+
+ fprintf(fd,"P6\n%u %u\n255\n",width,height);
+ fprintf(stdout,"\nWriting \"%s\" (%ux%u pixmap image)... ",mapfile,width,height);
+ fflush(stdout);
+
+ for (y=0, lat=(double)max_north-one_pixel; y<(int)height; y++, lat=(double)max_north-(one_pixel*(double)y))
+ {
+ for (x=0, lon=(double)max_west-one_pixel; x<(int)width; x++, lon=(double)max_west-(one_pixel*(double)x))
+ {
+ if (lon<0.0)
+ lon+=360.0;
+
+ for (indx=0, found=0; indx<MAXPAGES && found==0;)
+ if (lat>=(double)dem[indx].min_north && lat<(double)dem[indx].max_north && LonDiff(lon,(double)dem[indx].min_west)>=0.0 && LonDiff(lon,(double)dem[indx].max_west)<0.0)
+ found=1;
+ else
+ indx++;
+
+ if (found)
+ {
+ x0=(int)(1199.0*(lat-floor(lat)));
+ y0=(int)(1199.0*(lon-floor(lon)));
+
+ mask=dem[indx].mask[x0][y0];
+
+ if (mask&2)
+ /* Text Labels: Red */
+ fprintf(fd,"%c%c%c",255,0,0);
+
+ else if (mask&4)
+ /* County Boundaries: Light Cyan */
+ fprintf(fd,"%c%c%c",128,128,255);
+
+ else switch (mask&57)
+ {
+ case 1:
+ /* TX1: Green */
+ fprintf(fd,"%c%c%c",0,255,0);
+ break;
+
+ case 8:
+ /* TX2: Cyan */
+ fprintf(fd,"%c%c%c",0,255,255);
+ break;
+
+ case 9:
+ /* TX1 + TX2: Yellow */
+ fprintf(fd,"%c%c%c",255,255,0);
+ break;
+
+ case 16:
+ /* TX3: Medium Violet */
+ fprintf(fd,"%c%c%c",147,112,219);
+ break;
case 17:
/* TX1 + TX3: Pink */
break;
default:
- /* Water: Medium Blue */
- if (dem[indx].data[x0][y0]==0)
- fprintf(fd,"%c%c%c",0,0,170);
+ if (ngs) /* No terrain */
+ fprintf(fd,"%c%c%c",255,255,255);
else
{
- /* Elevation: Greyscale */
- output=(unsigned)(0.5+pow((double)(dem[indx].data[x0][y0]-min_elevation),one_over_gamma)*conversion);
- fprintf(fd,"%c%c%c",output,output,output);
+ /* Sea-level: Medium Blue */
+ if (dem[indx].data[x0][y0]==0)
+ fprintf(fd,"%c%c%c",0,0,170);
+ else
+ {
+ /* Elevation: Greyscale */
+ terrain=(unsigned)(0.5+pow((double)(dem[indx].data[x0][y0]-min_elevation),one_over_gamma)*conversion);
+ fprintf(fd,"%c%c%c",terrain,terrain,terrain);
+ }
}
}
}
fflush(stdout);
}
-void WritePPMLR(char *filename, unsigned char geo)
+void WritePPMLR(char *filename, unsigned char geo, unsigned char kml, unsigned char ngs, struct site *xmtr, unsigned char txsites)
{
/* This function generates a topographic map in Portable Pix Map
(PPM) format based on the content of flags held in the mask[][]
90 degrees from its representation in dem[][] so that north
points up and east points right in the image generated. */
- char mapfile[255], geofile[255];
- unsigned width, height, output;
+ char mapfile[255], geofile[255], kmlfile[255], color=0;
+ unsigned width, height, red, green, blue, terrain=0;
unsigned char found, mask, cityorcounty;
- int indx, x, y, t, t2, x0, y0, minlat, minlon, loss;
- float lat, lon, one_pixel, conversion, one_over_gamma;
+ int indx, x, y, z, colorwidth, x0, y0, loss, level,
+ hundreds, tens, units, match;
+ double lat, lon, one_pixel, conversion, one_over_gamma;
FILE *fd;
one_pixel=1.0/1200.0;
width=(unsigned)(1200*ReduceAngle(max_west-min_west));
height=(unsigned)(1200*ReduceAngle(max_north-min_north));
- if (filename[0]==0)
- strncpy(mapfile, "map.ppm\0",8);
- else
- {
- for (x=0; filename[x]!='.' && filename[x]!=0 && x<250; x++)
- {
- mapfile[x]=filename[x];
- geofile[x]=filename[x];
- }
+ LoadLossColors(xmtr[0]);
- mapfile[x]='.';
- geofile[x]='.';
- mapfile[x+1]='p';
- geofile[x+1]='g';
- mapfile[x+2]='p';
- geofile[x+2]='e';
- mapfile[x+3]='m';
- geofile[x+3]='o';
- mapfile[x+4]=0;
- geofile[x+4]=0;
- }
+ if (filename[0]==0)
+ strncpy(filename, xmtr[0].filename,254);
- if (geo)
+ for (x=0; filename[x]!='.' && filename[x]!=0 && x<250; x++)
+ {
+ mapfile[x]=filename[x];
+ geofile[x]=filename[x];
+ kmlfile[x]=filename[x];
+ }
+
+ mapfile[x]='.';
+ geofile[x]='.';
+ kmlfile[x]='.';
+ mapfile[x+1]='p';
+ geofile[x+1]='g';
+ kmlfile[x+1]='k';
+ mapfile[x+2]='p';
+ geofile[x+2]='e';
+ kmlfile[x+2]='m';
+ mapfile[x+3]='m';
+ geofile[x+3]='o';
+ kmlfile[x+3]='l';
+ mapfile[x+4]=0;
+ geofile[x+4]=0;
+ kmlfile[x+4]=0;
+
+ if (kml==0 && geo)
{
fd=fopen(geofile,"wb");
fclose(fd);
}
- fd=fopen(mapfile,"wb");
+ if (kml && geo==0)
+ {
+ fd=fopen(kmlfile,"wb");
+
+ fprintf(fd,"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n");
+ fprintf(fd,"<kml xmlns=\"http://earth.google.com/kml/2.1\">\n");
+ fprintf(fd,"<!-- Generated by SPLAT! Version %s -->\n",splat_version);
+ fprintf(fd," <Folder>\n");
+ fprintf(fd," <name>SPLAT!</name>\n");
+ fprintf(fd," <description>%s Transmitter Path Loss Overlay</description>\n",xmtr[0].name);
+ fprintf(fd," <GroundOverlay>\n");
+ fprintf(fd," <name>SPLAT! Path Loss Overlay</name>\n");
+ fprintf(fd," <description>SPLAT! Coverage</description>\n");
+ fprintf(fd," <Icon>\n");
+ fprintf(fd," <href>%s</href>\n",mapfile);
+ fprintf(fd," </Icon>\n");
+ fprintf(fd," <opacity>128</opacity>\n");
+ fprintf(fd," <LatLonBox>\n");
+ fprintf(fd," <north>%.5f</north>\n",(double)max_north-one_pixel);
+ fprintf(fd," <south>%.5f</south>\n",(double)min_north);
+ fprintf(fd," <east>%.5f</east>\n",((double)min_west<180.0?(double)-min_west:360.0-(double)min_west));
+ fprintf(fd," <west>%.5f</west>\n",(((double)max_west-one_pixel)<180.0?-((double)max_west-one_pixel):(360.0-(double)max_west-one_pixel)));
+ fprintf(fd," <rotation>0.0</rotation>\n");
+ fprintf(fd," </LatLonBox>\n");
+ fprintf(fd," </GroundOverlay>\n");
+
+ for (x=0; x<txsites; x++)
+ {
+ fprintf(fd," <Placemark>\n");
+ fprintf(fd," <name>%s</name>\n",xmtr[x].name);
+ fprintf(fd," <visibility>1</visibility>\n");
+ fprintf(fd," <Style>\n");
+ fprintf(fd," <IconStyle>\n");
+ fprintf(fd," <Icon>\n");
+ fprintf(fd," <href>root://icons/palette-5.png</href>\n");
+ fprintf(fd," <x>224</x>\n");
+ fprintf(fd," <y>224</y>\n");
+ fprintf(fd," <w>32</w>\n");
+ fprintf(fd," <h>32</h>\n");
+ fprintf(fd," </Icon>\n");
+ fprintf(fd," </IconStyle>\n");
+ fprintf(fd," </Style>\n");
+ fprintf(fd," <Point>\n");
+ fprintf(fd," <extrude>1</extrude>\n");
+ fprintf(fd," <altitudeMode>relativeToGround</altitudeMode>\n");
+ fprintf(fd," <coordinates>%f,%f,%f</coordinates>\n",(xmtr[x].lon<180.0?-xmtr[x].lon:360.0-xmtr[x].lon), xmtr[x].lat, xmtr[x].alt);
+ fprintf(fd," </Point>\n");
+ fprintf(fd," </Placemark>\n");
+ }
+
+ fprintf(fd," </Folder>\n");
+ fprintf(fd,"</kml>\n");
+
+ fclose(fd);
+ }
- fprintf(fd,"P6\n%u %u\n255\n",width,height+30);
+ fd=fopen(mapfile,"wb");
- fprintf(stdout,"\nWriting \"%s\" (%ux%u pixmap image)... ",mapfile,width,height+30);
+ fprintf(fd,"P6\n%u %u\n255\n",width,(kml?height:height+30));
+ fprintf(stdout,"\nWriting \"%s\" (%ux%u pixmap image)... ",mapfile,width,(kml?height:height+30));
fflush(stdout);
- for (y=0, lat=((double)max_north)-one_pixel; y<(int)height; y++, lat-=one_pixel)
+ for (y=0, lat=(double)max_north-one_pixel; y<(int)height; y++, lat=(double)max_north-(one_pixel*(double)y))
{
- minlat=(int)floor(lat);
-
- for (x=0, lon=((double)max_west)-one_pixel; x<(int)width; x++, lon-=one_pixel)
+ for (x=0, lon=(double)max_west-one_pixel; x<(int)width; x++, lon=(double)max_west-(one_pixel*(double)x))
{
if (lon<0.0)
lon+=360.0;
- minlon=(int)floor(lon);
-
- for (indx=0, found=0; indx<MAXSLOTS && found==0;)
- if (minlat==dem[indx].min_north && minlon==dem[indx].min_west)
+ for (indx=0, found=0; indx<MAXPAGES && found==0;)
+ if (lat>=(double)dem[indx].min_north && lat<(double)dem[indx].max_north && LonDiff(lon,(double)dem[indx].min_west)>=0.0 && LonDiff(lon,(double)dem[indx].max_west)<0.0)
found=1;
else
indx++;
+
if (found)
{
x0=(int)(1199.0*(lat-floor(lat)));
y0=(int)(1199.0*(lon-floor(lon)));
mask=dem[indx].mask[x0][y0];
- loss=70+(10*(int)((mask&248)>>3));
+ loss=(dem[indx].signal[x0][y0]);
cityorcounty=0;
- if (mask&2)
+ match=255;
+
+ red=0;
+ green=0;
+ blue=0;
+
+ if (loss<=region.level[0])
+ match=0;
+ else
+ {
+ for (z=1; (z<region.levels && match==255); z++)
+ {
+ if (loss>=region.level[z-1] && loss<region.level[z])
+ match=z;
+ }
+ }
+
+ if (match<region.levels)
{
- /* Text Labels - Black or Red */
+ red=region.color[match][0];
+ green=region.color[match][1];
+ blue=region.color[match][2];
- if ((mask&120) && (loss<=90))
- fprintf(fd,"%c%c%c",0,0,0);
- else
- fprintf(fd,"%c%c%c",255,0,0);
+ color=1;
+ }
- cityorcounty=1;
+ if ((mask&2) && (kml==0))
+ {
+ /* Text Labels: Red or otherwise */
+
+ if (red>=180 && green<=75 && blue<=75 && loss!=0)
+ fprintf(fd,"%c%c%c",255^red,255^green,255^blue);
+ else
+ fprintf(fd,"%c%c%c",255,0,0);
+
+ cityorcounty=1;
}
- else if (mask&4)
+ else if ((mask&4) && (kml==0))
{
/* County Boundaries: Black */
if (cityorcounty==0)
{
- if (loss>maxdB)
-
- { /* Display land or sea elevation */
-
- if (dem[indx].data[x0][y0]==0)
- fprintf(fd,"%c%c%c",0,0,170);
+ if (loss>maxdB || loss==0)
+ {
+ if (ngs) /* No terrain */
+ fprintf(fd,"%c%c%c",255,255,255);
else
{
- /* Elevation: Greyscale */
- output=(unsigned)(0.5+pow((double)(dem[indx].data[x0][y0]-min_elevation),one_over_gamma)*conversion);
- fprintf(fd,"%c%c%c",output,output,output);
+ /* Display land or sea elevation */
+
+ if (dem[indx].data[x0][y0]==0)
+ fprintf(fd,"%c%c%c",0,0,170);
+ else
+ {
+ terrain=(unsigned)(0.5+pow((double)(dem[indx].data[x0][y0]-min_elevation),one_over_gamma)*conversion);
+ fprintf(fd,"%c%c%c",terrain,terrain,terrain);
+ }
}
}
- else switch (loss)
+ else
{
- /* Plot signal loss in color */
-
- case 80:
- fprintf(fd,"%c%c%c",255,0,0);
- break;
-
- case 90:
- fprintf(fd,"%c%c%c",255,128,0);
- break;
-
- case 100:
- fprintf(fd,"%c%c%c",255,165,0);
- break;
-
- case 110:
- fprintf(fd,"%c%c%c",255,206,0);
- break;
-
- case 120:
- fprintf(fd,"%c%c%c",255,255,0);
- break;
-
- case 130:
- fprintf(fd,"%c%c%c",184,255,0);
- break;
-
- case 140:
- fprintf(fd,"%c%c%c",0,255,0);
- break;
-
- case 150:
- fprintf(fd,"%c%c%c",0,208,0);
- break;
-
- case 160:
- fprintf(fd,"%c%c%c",0,196,196);
- break;
-
- case 170:
- fprintf(fd,"%c%c%c",0,148,255);
- break;
-
- case 180:
- fprintf(fd,"%c%c%c",80,80,255);
- break;
-
- case 190:
- fprintf(fd,"%c%c%c",0,38,255);
- break;
-
- case 200:
- fprintf(fd,"%c%c%c",142,63,255);
- break;
-
- case 210:
- fprintf(fd,"%c%c%c",196,54,255);
- break;
-
- case 220:
- fprintf(fd,"%c%c%c",255,0,255);
- break;
-
- case 230:
- fprintf(fd,"%c%c%c",255,194,204);
- break;
+ /* Plot path loss in color */
- default:
+ if (red!=0 || green!=0 || blue!=0)
+ fprintf(fd,"%c%c%c",red,green,blue);
- if (dem[indx].data[x0][y0]==0)
- fprintf(fd,"%c%c%c",0,0,170);
- else
+ else /* terrain / sea-level */
{
- /* Elevation: Greyscale */
- output=(unsigned)(0.5+pow((double)(dem[indx].data[x0][y0]-min_elevation),one_over_gamma)*conversion);
- fprintf(fd,"%c%c%c",output,output,output);
+ if (dem[indx].data[x0][y0]==0)
+ fprintf(fd,"%c%c%c",0,0,170);
+ else
+ {
+ /* Elevation: Greyscale */
+ terrain=(unsigned)(0.5+pow((double)(dem[indx].data[x0][y0]-min_elevation),one_over_gamma)*conversion);
+ fprintf(fd,"%c%c%c",terrain,terrain,terrain);
+ }
}
}
}
}
}
- /* Display legend along bottom of image */
+ if (kml==0 && color)
+ {
+ /* Display legend along bottom of image */
- x0=width/16;
+ colorwidth=(int)rint((float)width/(float)region.levels);
- for (y0=0; y0<30; y0++)
- {
- for (indx=0; indx<16; indx++)
+ for (y0=0; y0<30; y0++)
{
- for (x=0; x<x0; x++)
+ for (x0=0; x0<(int)width; x0++)
{
- t=indx;
- t2=indx+8;
+ indx=x0/colorwidth;
+ x=x0%colorwidth;
+ level=region.level[indx];
+
+ hundreds=level/100;
+
+ if (hundreds>0)
+ level-=(hundreds*100);
+
+ tens=level/10;
+
+ if (tens>0)
+ level-=(tens*10);
+
+ units=level;
- if (y0>=10 && y0<=18)
+ if (y0>=8 && y0<=23)
{
- if (t2>9)
+ if (hundreds>0)
{
- if (x>=11 && x<=17)
- if (smallfont[t2/10][y0-10][x-11])
- t=255;
+ if (x>=11 && x<=18)
+ if (fontdata[16*(hundreds+'0')+(y0-8)]&(128>>(x-11)))
+ indx=255;
}
- if (x>=19 && x<=25)
- if (smallfont[t2%10][y0-10][x-19])
- t=255;
+ if (tens>0 || hundreds>0)
+ {
+ if (x>=19 && x<=26)
+ if (fontdata[16*(tens+'0')+(y0-8)]&(128>>(x-19)))
+ indx=255;
+ }
- if (x>=27 && x<=33)
- if (smallfont[0][y0-10][x-27])
- t=255;
+ if (x>=27 && x<=34)
+ if (fontdata[16*(units+'0')+(y0-8)]&(128>>(x-27)))
+ indx=255;
+
+ if (x>=42 && x<=49)
+ if (fontdata[16*('d')+(y0-8)]&(128>>(x-42)))
+ indx=255;
+
+ if (x>=50 && x<=57)
+ if (fontdata[16*('B')+(y0-8)]&(128>>(x-50)))
+ indx=255;
}
- switch (t)
+ if (indx>region.levels)
+ fprintf(fd,"%c%c%c",0,0,0);
+ else
{
- case 0:
- fprintf(fd,"%c%c%c",255,0,0);
- break;
+ red=region.color[indx][0];
+ green=region.color[indx][1];
+ blue=region.color[indx][2];
- case 1:
- fprintf(fd,"%c%c%c",255,128,0);
- break;
+ fprintf(fd,"%c%c%c",red,green,blue);
+ }
+ }
+ }
+ }
- case 2:
- fprintf(fd,"%c%c%c",255,165,0);
- break;
+ fclose(fd);
+ fprintf(stdout,"Done!\n");
+ fflush(stdout);
+}
- case 3:
- fprintf(fd,"%c%c%c",255,206,0);
- break;
+void WritePPMSS(char *filename, unsigned char geo, unsigned char kml, unsigned char ngs, struct site *xmtr, unsigned char txsites)
+{
+ /* This function generates a topographic map in Portable Pix Map
+ (PPM) format based on the signal strength values held in the
+ signal[][] array. The image created is rotated counter-clockwise
+ 90 degrees from its representation in dem[][] so that north
+ points up and east points right in the image generated. */
- case 4:
- fprintf(fd,"%c%c%c",255,255,0);
- break;
+ char mapfile[255], geofile[255], kmlfile[255], color=0;
+ unsigned width, height, terrain, red, green, blue;
+ unsigned char found, mask, cityorcounty;
+ int indx, x, y, z=1, x0, y0, signal, level, hundreds,
+ tens, units, match, colorwidth;
+ double lat, lon, one_pixel, conversion, one_over_gamma;
+ FILE *fd;
- case 5:
- fprintf(fd,"%c%c%c",184,255,0);
- break;
+ one_pixel=1.0/1200.0;
+ one_over_gamma=1.0/GAMMA;
+ conversion=255.0/pow((double)(max_elevation-min_elevation),one_over_gamma);
- case 6:
- fprintf(fd,"%c%c%c",0,255,0);
- break;
+ width=(unsigned)(1200*ReduceAngle(max_west-min_west));
+ height=(unsigned)(1200*ReduceAngle(max_north-min_north));
- case 7:
- fprintf(fd,"%c%c%c",0,208,0);
- break;
+ LoadSignalColors(xmtr[0]);
- case 8:
- fprintf(fd,"%c%c%c",0,196,196);
- break;
+ if (filename[0]==0)
+ strncpy(filename, xmtr[0].filename,254);
- case 9:
- fprintf(fd,"%c%c%c",0,148,255);
- break;
+ for (x=0; filename[x]!='.' && filename[x]!=0 && x<250; x++)
+ {
+ mapfile[x]=filename[x];
+ geofile[x]=filename[x];
+ kmlfile[x]=filename[x];
+ }
+
+ mapfile[x]='.';
+ geofile[x]='.';
+ kmlfile[x]='.';
+ mapfile[x+1]='p';
+ geofile[x+1]='g';
+ kmlfile[x+1]='k';
+ mapfile[x+2]='p';
+ geofile[x+2]='e';
+ kmlfile[x+2]='m';
+ mapfile[x+3]='m';
+ geofile[x+3]='o';
+ kmlfile[x+3]='l';
+ mapfile[x+4]=0;
+ geofile[x+4]=0;
+ kmlfile[x+4]=0;
+
+ if (geo && kml==0)
+ {
+ fd=fopen(geofile,"wb");
- case 10:
- fprintf(fd,"%c%c%c",80,80,255);
- break;
+ fprintf(fd,"FILENAME\t%s\n",mapfile);
+ fprintf(fd,"#\t\tX\tY\tLong\t\tLat\n");
+ fprintf(fd,"TIEPOINT\t0\t0\t%d.000\t\t%d.000\n",(max_west<180?-max_west:360-max_west),max_north);
+ fprintf(fd,"TIEPOINT\t%u\t%u\t%d.000\t\t%.3f\n",width-1,height+29,(min_west<180?-min_west:360-min_west),(double)(min_north-0.025));
+ fprintf(fd,"IMAGESIZE\t%u\t%u\n",width,height+30);
+ fprintf(fd,"#\n# Auto Generated by SPLAT! v%s\n#\n",splat_version);
- case 11:
- fprintf(fd,"%c%c%c",0,38,255);
- break;
+ fclose(fd);
+ }
- case 12:
- fprintf(fd,"%c%c%c",142,63,255);
- break;
+ if (kml && geo==0)
+ {
+ fd=fopen(kmlfile,"wb");
+
+ fprintf(fd,"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n");
+ fprintf(fd,"<kml xmlns=\"http://earth.google.com/kml/2.1\">\n");
+ fprintf(fd,"<!-- Generated by SPLAT! Version %s -->\n",splat_version);
+ fprintf(fd," <Folder>\n");
+ fprintf(fd," <name>SPLAT!</name>\n");
+ fprintf(fd," <description>%s Transmitter Coverage Overlay</description>\n",xmtr[0].name);
+ fprintf(fd," <GroundOverlay>\n");
+ fprintf(fd," <name>SPLAT! Signal Strength Overlay</name>\n");
+ fprintf(fd," <description>SPLAT! Coverage</description>\n");
+ fprintf(fd," <Icon>\n");
+ fprintf(fd," <href>%s</href>\n",mapfile);
+ fprintf(fd," </Icon>\n");
+ fprintf(fd," <opacity>128</opacity>\n");
+ fprintf(fd," <LatLonBox>\n");
+ fprintf(fd," <north>%.5f</north>\n",(double)max_north-one_pixel);
+ fprintf(fd," <south>%.5f</south>\n",(double)min_north);
+ fprintf(fd," <east>%.5f</east>\n",((double)min_west<180.0?(double)-min_west:360.0-(double)min_west));
+ fprintf(fd," <west>%.5f</west>\n",(((double)max_west-one_pixel)<180.0?-((double)max_west-one_pixel):(360.0-(double)max_west-one_pixel)));
+ fprintf(fd," <rotation>0.0</rotation>\n");
+ fprintf(fd," </LatLonBox>\n");
+ fprintf(fd," </GroundOverlay>\n");
- case 13:
- fprintf(fd,"%c%c%c",196,54,255);
- break;
+ for (x=0; x<txsites; x++)
+ {
+ fprintf(fd," <Placemark>\n");
+ fprintf(fd," <name>%s</name>\n",xmtr[x].name);
+ fprintf(fd," <visibility>1</visibility>\n");
+ fprintf(fd," <Style>\n");
+ fprintf(fd," <IconStyle>\n");
+ fprintf(fd," <Icon>\n");
+ fprintf(fd," <href>root://icons/palette-5.png</href>\n");
+ fprintf(fd," <x>224</x>\n");
+ fprintf(fd," <y>224</y>\n");
+ fprintf(fd," <w>32</w>\n");
+ fprintf(fd," <h>32</h>\n");
+ fprintf(fd," </Icon>\n");
+ fprintf(fd," </IconStyle>\n");
+ fprintf(fd," </Style>\n");
+ fprintf(fd," <Point>\n");
+ fprintf(fd," <extrude>1</extrude>\n");
+ fprintf(fd," <altitudeMode>relativeToGround</altitudeMode>\n");
+ fprintf(fd," <coordinates>%f,%f,%f</coordinates>\n",(xmtr[x].lon<180.0?-xmtr[x].lon:360.0-xmtr[x].lon), xmtr[x].lat, xmtr[x].alt);
+ fprintf(fd," </Point>\n");
+ fprintf(fd," </Placemark>\n");
+ }
- case 14:
- fprintf(fd,"%c%c%c",255,0,255);
- break;
+ fprintf(fd," </Folder>\n");
+ fprintf(fd,"</kml>\n");
+
+ fclose(fd);
+ }
+
+ fd=fopen(mapfile,"wb");
+
+ fprintf(fd,"P6\n%u %u\n255\n",width,(kml?height:height+30));
+ fprintf(stdout,"\nWriting \"%s\" (%ux%u pixmap image)... ",mapfile,width,(kml?height:height+30));
+ fflush(stdout);
+
+ for (y=0, lat=(double)max_north-one_pixel; y<(int)height; y++, lat=(double)max_north-(one_pixel*(double)y))
+ {
+ for (x=0, lon=(double)max_west-one_pixel; x<(int)width; x++, lon=(double)max_west-(one_pixel*(double)x))
+ {
+ if (lon<0.0)
+ lon+=360.0;
+
+ for (indx=0, found=0; indx<MAXPAGES && found==0;)
+ if (lat>=(double)dem[indx].min_north && lat<(double)dem[indx].max_north && LonDiff(lon,(double)dem[indx].min_west)>=0.0 && LonDiff(lon,(double)dem[indx].max_west)<0.0)
+ found=1;
+ else
+ indx++;
+
+ if (found)
+ {
+ x0=(int)(1199.0*(lat-floor(lat)));
+ y0=(int)(1199.0*(lon-floor(lon)));
+
+ mask=dem[indx].mask[x0][y0];
+ signal=(dem[indx].signal[x0][y0])-100;
+ cityorcounty=0;
+
+ match=255;
+
+ red=0;
+ green=0;
+ blue=0;
+
+ if (signal>=region.level[0])
+ match=0;
+ else
+ {
+ for (z=1; (z<region.levels && match==255); z++)
+ {
+ if (signal<region.level[z-1] && signal>=region.level[z])
+ match=z;
+ }
+ }
+
+ if (match<region.levels)
+ {
+ red=region.color[match][0];
+ green=region.color[match][1];
+ blue=region.color[match][2];
+
+ color=1;
+ }
+
+ if ((mask&2) && (kml==0))
+ {
+ /* Text Labels: Red or otherwise */
+
+ if (red>=180 && green<=75 && blue<=75)
+ fprintf(fd,"%c%c%c",255^red,255^green,255^blue);
+ else
+ fprintf(fd,"%c%c%c",255,0,0);
+
+ cityorcounty=1;
+ }
+
+ else if ((mask&4) && (kml==0))
+ {
+ /* County Boundaries: Black */
- case 255:
- /* Black */
fprintf(fd,"%c%c%c",0,0,0);
- break;
- default:
- fprintf(fd,"%c%c%c",255,194,204);
+ cityorcounty=1;
+ }
+
+ if (cityorcounty==0)
+ {
+ if (dem[indx].signal[x0][y0]==0)
+ {
+ if (ngs)
+ fprintf(fd,"%c%c%c",255,255,255);
+ else
+ {
+ /* Display land or sea elevation */
+
+ if (dem[indx].data[x0][y0]==0)
+ fprintf(fd,"%c%c%c",0,0,170);
+ else
+ {
+ terrain=(unsigned)(0.5+pow((double)(dem[indx].data[x0][y0]-min_elevation),one_over_gamma)*conversion);
+ fprintf(fd,"%c%c%c",terrain,terrain,terrain);
+ }
+ }
+ }
+
+ else
+ {
+ /* Plot field strength regions in color */
+
+ if (red!=0 || green!=0 || blue!=0)
+ fprintf(fd,"%c%c%c",red,green,blue);
+
+ else /* terrain / sea-level */
+ {
+ if (ngs)
+ fprintf(fd,"%c%c%c",255,255,255);
+ else
+ {
+ if (dem[indx].data[x0][y0]==0)
+ fprintf(fd,"%c%c%c",0,0,170);
+ else
+ {
+ /* Elevation: Greyscale */
+ terrain=(unsigned)(0.5+pow((double)(dem[indx].data[x0][y0]-min_elevation),one_over_gamma)*conversion);
+ fprintf(fd,"%c%c%c",terrain,terrain,terrain);
+ }
+ }
+ }
+ }
+ }
+ }
+
+ else
+ {
+ /* We should never get here, but if */
+ /* we do, display the region as black */
+
+ fprintf(fd,"%c%c%c",0,0,0);
+ }
+ }
+ }
+
+ if (kml==0 && color)
+ {
+ /* Display legend along bottom of image */
+
+ colorwidth=(int)rint((float)width/(float)region.levels);
+
+ for (y0=0; y0<30; y0++)
+ {
+ for (x0=0; x0<(int)width; x0++)
+ {
+ indx=x0/colorwidth;
+ x=x0%colorwidth;
+ level=region.level[indx];
+
+ hundreds=level/100;
+
+ if (hundreds>0)
+ level-=(hundreds*100);
+
+ tens=level/10;
+
+ if (tens>0)
+ level-=(tens*10);
+
+ units=level;
+
+ if (y0>=8 && y0<=23)
+ {
+ if (hundreds>0)
+ {
+ if (x>=5 && x<=12)
+ if (fontdata[16*(hundreds+'0')+(y0-8)]&(128>>(x-5)))
+ indx=255;
+ }
+
+ if (tens>0 || hundreds>0)
+ {
+ if (x>=13 && x<=20)
+ if (fontdata[16*(tens+'0')+(y0-8)]&(128>>(x-13)))
+ indx=255;
+ }
+
+ if (x>=21 && x<=28)
+ if (fontdata[16*(units+'0')+(y0-8)]&(128>>(x-21)))
+ indx=255;
+
+ if (x>=36 && x<=43)
+ if (fontdata[16*('d')+(y0-8)]&(128>>(x-36)))
+ indx=255;
+
+ if (x>=44 && x<=51)
+ if (fontdata[16*('B')+(y0-8)]&(128>>(x-44)))
+ indx=255;
+
+ if (x>=52 && x<=59)
+ if (fontdata[16*('u')+(y0-8)]&(128>>(x-52)))
+ indx=255;
+
+ if (x>=60 && x<=67)
+ if (fontdata[16*('V')+(y0-8)]&(128>>(x-60)))
+ indx=255;
+
+ if (x>=68 && x<=75)
+ if (fontdata[16*('/')+(y0-8)]&(128>>(x-68)))
+ indx=255;
+
+ if (x>=76 && x<=83)
+ if (fontdata[16*('m')+(y0-8)]&(128>>(x-76)))
+ indx=255;
+ }
+
+ if (indx>region.levels)
+ fprintf(fd,"%c%c%c",0,0,0);
+ else
+ {
+ red=region.color[indx][0];
+ green=region.color[indx][1];
+ blue=region.color[indx][2];
+
+ fprintf(fd,"%c%c%c",red,green,blue);
}
}
}
{
if (metric)
fprintf(fd,"%f\t%f\n",KM_PER_MILE*path.distance[x],METERS_PER_FOOT*path.elevation[x]);
-
else
fprintf(fd,"%f\t%f\n",path.distance[x],path.elevation[x]);
}
else if (strncmp(ext,"ps",2)==0)
strncpy(term,"postscript enhanced color\0",26);
- fprintf(stdout,"Writing \"%s.%s\"...",filename,ext);
- fflush(stdout);
-
fd=fopen("splat.gp","w");
fprintf(fd,"set grid\n");
fprintf(fd,"set autoscale\n");
{
unlink("splat.gp");
unlink("profile.gp");
- fprintf(stdout," Done!\n");
+
+ fprintf(stdout,"\nTerrain plot written to: \"%s.%s\"",filename,ext);
fflush(stdout);
}
else if (strncmp(ext,"ps",2)==0)
strncpy(term,"postscript enhanced color\0",26);
- fprintf(stdout,"Writing \"%s.%s\"...",filename,ext);
- fflush(stdout);
-
fd=fopen("splat.gp","w");
fprintf(fd,"set grid\n");
unlink("profile.gp");
unlink("reference.gp");
- fprintf(stdout," Done!\n");
+ fprintf(stdout,"\nElevation plot written to: \"%s.%s\"",filename,ext);
fflush(stdout);
}
fd4=fopen("fresnel_pt_6.gp", "wb");
}
- for (x=0; x<path.length; x++)
+ for (x=0; x<path.length-1; x++)
{
remote.lat=path.lat[x];
remote.lon=path.lon[x];
if (f)
{
d1=5280.0*path.distance[x];
- f_zone=-1*sqrt(lambda*d1*(d-d1)/d);
- fpt6_zone=0.6*f_zone;
+ f_zone=-1.0*sqrt(lambda*d1*(d-d1)/d);
+ fpt6_zone=f_zone*fzone_clearance;
}
if (n)
else if (strncmp(ext,"ps",2)==0)
strncpy(term,"postscript enhanced color\0",26);
- fprintf(stdout,"Writing \"%s.%s\"...",filename,ext);
- fflush(stdout);
-
fd=fopen("splat.gp","w");
dheight=maxheight-minheight;
fprintf(fd,"set output \"%s.%s\"\n",filename,ext);
if (f)
- fprintf(fd,"plot \"profile.gp\" title \"Point-to-Point Profile\" with lines, \"reference.gp\" title \"Line of Sight Path\" with lines, \"curvature.gp\" axes x1y2 title \"Earth's Curvature Contour\" with lines, \"fresnel.gp\" axes x1y1 title \"First Fresnel Zone (%.3f MHz)\" with lines, \"fresnel_pt_6.gp\" title \"60%% of First Fresnel Zone\" with lines\n",f);
+ fprintf(fd,"plot \"profile.gp\" title \"Point-to-Point Profile\" with lines, \"reference.gp\" title \"Line of Sight Path\" with lines, \"curvature.gp\" axes x1y2 title \"Earth's Curvature Contour\" with lines, \"fresnel.gp\" axes x1y1 title \"First Fresnel Zone (%.3f MHz)\" with lines, \"fresnel_pt_6.gp\" title \"%.0f%% of First Fresnel Zone\" with lines\n",f,fzone_clearance*100.0);
else
fprintf(fd,"plot \"profile.gp\" title \"Point-to-Point Profile\" with lines, \"reference.gp\" title \"Line Of Sight Path\" with lines, \"curvature.gp\" axes x1y2 title \"Earth's Curvature Contour\" with lines\n");
unlink("fresnel_pt_6.gp");
}
- fprintf(stdout," Done!\n");
+ fprintf(stdout,"\nHeight plot written to: \"%s.%s\"",filename,ext);
fflush(stdout);
}
fprintf(stderr,"\n*** ERROR: Error occurred invoking gnuplot!\n");
}
-void GraphLongley(struct site source, struct site destination, char *name)
+void ObstructionAnalysis(struct site xmtr, struct site rcvr, double f, FILE *outfile)
{
- /* This function invokes gnuplot to generate an appropriate
- output file indicating the Longley-Rice model loss between
- the source and destination locations. "filename" is the
- name assigned to the output file generated by gnuplot.
- The filename extension is used to set gnuplot's terminal
- setting and output file type. If no extension is found,
- .png is assumed. */
-
- int x, y, z, errnum, errflag=0;
+ /* Perform an obstruction analysis along the
+ path between receiver and transmitter. */
+
+ int x;
+ struct site site_x;
+ double h_r, h_t, h_x, h_r_orig, cos_tx_angle, cos_test_angle,
+ cos_tx_angle_f1, cos_tx_angle_fpt6, d_tx, d_x,
+ h_r_f1, h_r_fpt6, h_f, h_los, lambda=0.0;
+ char string[255], string_fpt6[255], string_f1[255];
+
+ ReadPath(xmtr,rcvr);
+ h_r=GetElevation(rcvr)+rcvr.alt+earthradius;
+ h_r_f1=h_r;
+ h_r_fpt6=h_r;
+ h_r_orig=h_r;
+ h_t=GetElevation(xmtr)+xmtr.alt+earthradius;
+ d_tx=5280.0*Distance(rcvr,xmtr);
+ cos_tx_angle=((h_r*h_r)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r*d_tx);
+ cos_tx_angle_f1=cos_tx_angle;
+ cos_tx_angle_fpt6=cos_tx_angle;
+
+ if (f)
+ lambda=9.8425e8/(f*1e6);
+
+ /* At each point along the path calculate the cosine
+ of a sort of "inverse elevation angle" at the receiver.
+ From the antenna, 0 deg. looks at the ground, and 90 deg.
+ is parallel to the ground.
+
+ Start at the receiver. If this is the lowest antenna,
+ then terrain obstructions will be nearest to it. (Plus,
+ that's the way SPLAT!'s original los() did it.)
+
+ Calculate cosines only. That's sufficient to compare
+ angles and it saves the extra computational burden of
+ acos(). However, note the inverted comparison: if
+ acos(A) > acos(B), then B > A. */
+
+ for (x=path.length-1; x>0; x--)
+ {
+ site_x.lat=path.lat[x];
+ site_x.lon=path.lon[x];
+ site_x.alt=0.0;
+
+ h_x=GetElevation(site_x)+earthradius;
+ d_x=5280.0*Distance(rcvr,site_x);
+
+ /* Deal with the LOS path first. */
+
+ cos_test_angle=((h_r*h_r)+(d_x*d_x)-(h_x*h_x))/(2.0*h_r*d_x);
+
+ if (cos_tx_angle>cos_test_angle)
+ {
+ if (h_r==h_r_orig)
+ fprintf(outfile,"Between %s and %s, SPLAT! detected obstructions at:\n\n",rcvr.name,xmtr.name);
+
+ if (site_x.lat>=0.0)
+ {
+ if (metric)
+ fprintf(outfile,"\t%.4f N, %.4f W, %5.2f kilometers, %6.2f meters AMSL\n",site_x.lat, site_x.lon, KM_PER_MILE*(d_x/5280.0), METERS_PER_FOOT*(h_x-earthradius));
+ else
+ fprintf(outfile,"\t%.4f N, %.4f W, %5.2f miles, %6.2f feet AMSL\n",site_x.lat, site_x.lon, d_x/5280.0, h_x-earthradius);
+ }
+
+ else
+ {
+ if (metric)
+ fprintf(outfile,"\t%.4f S, %.4f W, %5.2f kilometers, %6.2f meters AMSL\n",-site_x.lat, site_x.lon, KM_PER_MILE*(d_x/5280.0), METERS_PER_FOOT*(h_x-earthradius));
+ else
+
+ fprintf(outfile,"\t%.4f S, %.4f W, %5.2f miles, %6.2f feet AMSL\n",-site_x.lat, site_x.lon, d_x/5280.0, h_x-earthradius);
+ }
+ }
+
+ while (cos_tx_angle>cos_test_angle)
+ {
+ h_r+=1;
+ cos_test_angle=((h_r*h_r)+(d_x*d_x)-(h_x*h_x))/(2.0*h_r*d_x);
+ cos_tx_angle=((h_r*h_r)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r*d_tx);
+ }
+
+ if (f)
+ {
+ /* Now clear the first Fresnel zone... */
+
+ cos_tx_angle_f1=((h_r_f1*h_r_f1)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r_f1*d_tx);
+ h_los=sqrt(h_r_f1*h_r_f1+d_x*d_x-2*h_r_f1*d_x*cos_tx_angle_f1);
+ h_f=h_los-sqrt(lambda*d_x*(d_tx-d_x)/d_tx);
+
+ while (h_f<h_x)
+ {
+ h_r_f1+=1;
+ cos_tx_angle_f1=((h_r_f1*h_r_f1)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r_f1*d_tx);
+ h_los=sqrt(h_r_f1*h_r_f1+d_x*d_x-2*h_r_f1*d_x*cos_tx_angle_f1);
+ h_f=h_los-sqrt(lambda*d_x*(d_tx-d_x)/d_tx);
+ }
+
+ /* and clear the 60% F1 zone. */
+
+ cos_tx_angle_fpt6=((h_r_fpt6*h_r_fpt6)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r_fpt6*d_tx);
+ h_los=sqrt(h_r_fpt6*h_r_fpt6+d_x*d_x-2*h_r_fpt6*d_x*cos_tx_angle_fpt6);
+ h_f=h_los-fzone_clearance*sqrt(lambda*d_x*(d_tx-d_x)/d_tx);
+
+ while (h_f<h_x)
+ {
+ h_r_fpt6+=1;
+ cos_tx_angle_fpt6=((h_r_fpt6*h_r_fpt6)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r_fpt6*d_tx);
+ h_los=sqrt(h_r_fpt6*h_r_fpt6+d_x*d_x-2*h_r_fpt6*d_x*cos_tx_angle_fpt6);
+ h_f=h_los-fzone_clearance*sqrt(lambda*d_x*(d_tx-d_x)/d_tx);
+ }
+ }
+ }
+
+ if (h_r>h_r_orig)
+ {
+ if (metric)
+ sprintf(string,"\nAntenna at %s must be raised to at least %.2f meters AGL\nto clear all obstructions detected by SPLAT!\n",rcvr.name, METERS_PER_FOOT*(h_r-GetElevation(rcvr)-earthradius));
+ else
+ sprintf(string,"\nAntenna at %s must be raised to at least %.2f feet AGL\nto clear all obstructions detected by SPLAT!\n",rcvr.name, h_r-GetElevation(rcvr)-earthradius);
+ }
+
+ else
+ sprintf(string,"\nNo obstructions to LOS path due to terrain were detected by SPLAT!\n");
+
+ if (f)
+ {
+ if (h_r_fpt6>h_r_orig)
+ {
+ if (metric)
+ sprintf(string_fpt6,"\nAntenna at %s must be raised to at least %.2f meters AGL\nto clear %.0f%c of the first Fresnel zone.\n",rcvr.name, METERS_PER_FOOT*(h_r_fpt6-GetElevation(rcvr)-earthradius),fzone_clearance*100.0,37);
+
+ else
+ sprintf(string_fpt6,"\nAntenna at %s must be raised to at least %.2f feet AGL\nto clear %.0f%c of the first Fresnel zone.\n",rcvr.name, h_r_fpt6-GetElevation(rcvr)-earthradius,fzone_clearance*100.0,37);
+ }
+
+ else
+ sprintf(string_fpt6,"\n%.0f%c of the first Fresnel zone is clear.\n",fzone_clearance*100.0,37);
+
+ if (h_r_f1>h_r_orig)
+ {
+ if (metric)
+ sprintf(string_f1,"\nAntenna at %s must be raised to at least %.2f meters AGL\nto clear the first Fresnel zone.\n",rcvr.name, METERS_PER_FOOT*(h_r_f1-GetElevation(rcvr)-earthradius));
+
+ else
+ sprintf(string_f1,"\nAntenna at %s must be raised to at least %.2f feet AGL\nto clear the first Fresnel zone.\n",rcvr.name, h_r_f1-GetElevation(rcvr)-earthradius);
+
+ }
+
+ else
+ sprintf(string_f1,"\nThe first Fresnel zone is clear.\n\n");
+ }
+
+ fprintf(outfile,"%s",string);
+
+ if (f)
+ {
+ fprintf(outfile,"%s",string_f1);
+ fprintf(outfile,"%s",string_fpt6);
+ }
+}
+
+void PathReport(struct site source, struct site destination, char *name, char graph_it)
+{
+ /* This function writes a SPLAT! Path Report (name.txt) to
+ the filesystem. If (graph_it == 1), then gnuplot is invoked
+ to generate an appropriate output file indicating the Longley-Rice
+ model loss between the source and destination locations.
+ "filename" is the name assigned to the output file generated
+ by gnuplot. The filename extension is used to set gnuplot's
+ terminal setting and output file type. If no extension is
+ found, .png is assumed. */
+
+ int x, y, z, errnum;
char filename[255], term[30], ext[15], strmode[100],
report_name[80], block=0;
double maxloss=-100000.0, minloss=100000.0, loss, haavt,
angle1, angle2, azimuth, pattern=1.0, patterndB=0.0,
total_loss=0.0, cos_xmtr_angle, cos_test_angle=0.0,
source_alt, test_alt, dest_alt, source_alt2, dest_alt2,
- distance, elevation, four_thirds_earth;
+ distance, elevation, four_thirds_earth, field_strength,
+ free_space_loss=0.0, voltage;
FILE *fd=NULL, *fd2=NULL;
- sprintf(report_name,"%s-to-%s.lro",source.name,destination.name);
+ sprintf(report_name,"%s-to-%s.txt",source.name,destination.name);
four_thirds_earth=EARTHRADIUS*(4.0/3.0);
fd2=fopen(report_name,"w");
- fprintf(fd2,"\n\t--==[ SPLAT! v%s Longley-Rice Model Path Loss Report ]==--\n\n",splat_version);
- fprintf(fd2,"Analysis of RF path conditions between %s and %s:\n",source.name, destination.name);
- fprintf(fd2,"\n-------------------------------------------------------------------------\n\n");
+ fprintf(fd2,"\n\t\t--==[ SPLAT! v%s Path Analysis ]==--\n\n",splat_version);
+ fprintf(fd2,"-------------------------------------------------------------------------\n\n");
fprintf(fd2,"Transmitter site: %s\n",source.name);
if (source.lat>=0.0)
pattern=(double)LR.antenna_pattern[(int)rint(azimuth)][x];
patterndB=20.0*log10(pattern);
-
- fprintf(fd2,"Antenna pattern between %s and %s: %.3f (%.2f dB)\n",source.name, destination.name, pattern, patterndB);
-
}
if (metric)
else
fprintf(fd2,"Depression angle to %s: %+.4f degrees\n",destination.name,angle1);
- if (angle1!=angle2)
+ if ((angle2-angle1)>0.0001)
{
if (angle2<0.0)
fprintf(fd2,"Depression");
else
fprintf(fd2,"Depression angle to %s: %+.4f degrees\n",source.name,angle1);
- if (angle1!=angle2)
+ if ((angle2-angle1)>0.0001)
{
if (angle2<0.0)
fprintf(fd2,"Depression");
fprintf(fd2,"\n-------------------------------------------------------------------------\n\n");
- fprintf(fd2,"Longley-Rice path calculation parameters used in this analysis:\n\n");
- fprintf(fd2,"Earth's Dielectric Constant: %.3lf\n",LR.eps_dielect);
- fprintf(fd2,"Earth's Conductivity: %.3lf\n",LR.sgm_conductivity);
- fprintf(fd2,"Atmospheric Bending Constant (N): %.3lf\n",LR.eno_ns_surfref);
- fprintf(fd2,"Frequency: %.3lf (MHz)\n",LR.frq_mhz);
- fprintf(fd2,"Radio Climate: %d (",LR.radio_climate);
-
- switch (LR.radio_climate)
+ if (LR.frq_mhz>0.0)
{
- case 1:
- fprintf(fd2,"Equatorial");
- break;
+ fprintf(fd2,"Longley-Rice path calculation parameters used in this analysis:\n\n");
+ fprintf(fd2,"Earth's Dielectric Constant: %.3lf\n",LR.eps_dielect);
+ fprintf(fd2,"Earth's Conductivity: %.3lf Siemens/meter\n",LR.sgm_conductivity);
+ fprintf(fd2,"Atmospheric Bending Constant (N-units): %.3lf ppm\n",LR.eno_ns_surfref);
+ fprintf(fd2,"Frequency: %.3lf MHz\n",LR.frq_mhz);
+ fprintf(fd2,"Radio Climate: %d (",LR.radio_climate);
- case 2:
- fprintf(fd2,"Continental Subtropical");
- break;
+ switch (LR.radio_climate)
+ {
+ case 1:
+ fprintf(fd2,"Equatorial");
+ break;
- case 3:
- fprintf(fd2,"Maritime Subtropical");
- break;
+ case 2:
+ fprintf(fd2,"Continental Subtropical");
+ break;
- case 4:
- fprintf(fd2,"Desert");
- break;
+ case 3:
+ fprintf(fd2,"Maritime Subtropical");
+ break;
- case 5:
- fprintf(fd2,"Continental Temperate");
- break;
+ case 4:
+ fprintf(fd2,"Desert");
+ break;
- case 6:
- fprintf(fd2,"Martitime Temperate, Over Land");
- break;
+ case 5:
+ fprintf(fd2,"Continental Temperate");
+ break;
- case 7:
- fprintf(fd2,"Maritime Temperate, Over Sea");
- break;
+ case 6:
+ fprintf(fd2,"Martitime Temperate, Over Land");
+ break;
- default:
- fprintf(fd2,"Unknown");
- }
-
- fprintf(fd2,")\nPolarization: %d (",LR.pol);
-
- if (LR.pol==0)
- fprintf(fd2,"Horizontal");
-
- if (LR.pol==1)
- fprintf(fd2,"Vertical");
-
- fprintf(fd2,")\nFraction of Situations: %.1lf%c\n",LR.conf*100.0,37);
- fprintf(fd2,"Fraction of Time: %.1lf%c\n",LR.rel*100.0,37);
- fprintf(fd2,"\n-------------------------------------------------------------------------\n\n");
-
- fprintf(fd2,"Analysis Results:\n\n");
-
- ReadPath(source, destination); /* source=TX, destination=RX */
-
- /* Copy elevations along path into the elev_l[] array. */
-
- for (x=0; x<path.length; x++)
- elev_l[x+2]=path.elevation[x]*METERS_PER_FOOT;
-
- if (metric)
- fprintf(fd2,"Distance (km)");
- else
- fprintf(fd2,"Distance (mi)");
-
- fprintf(fd2,"\tLoss (dB)\tErrnum\tComment\n\n");
-
- fd=fopen("profile.gp","w");
-
- azimuth=rint(Azimuth(source,destination));
-
- for (y=2; y<(path.length-1); y++) /* path.length-1 avoids LR error */
- {
- distance=5280.0*path.distance[y];
- source_alt=four_thirds_earth+source.alt+path.elevation[0];
- dest_alt=four_thirds_earth+destination.alt+path.elevation[y];
- dest_alt2=dest_alt*dest_alt;
- source_alt2=source_alt*source_alt;
-
- /* Calculate the cosine of the elevation of
- the receiver as seen by the transmitter. */
-
- cos_xmtr_angle=((source_alt2)+(distance*distance)-(dest_alt2))/(2.0*source_alt*distance);
-
- if (got_elevation_pattern)
- {
- /* If an antenna elevation pattern is available, the
- following code determines the elevation angle to
- the first obstruction along the path. */
-
- for (x=2, block=0; x<y && block==0; x++)
- {
- distance=5280.0*(path.distance[y]-path.distance[x]);
- test_alt=four_thirds_earth+path.elevation[x];
-
- /* Calculate the cosine of the elevation
- angle of the terrain (test point)
- as seen by the transmitter. */
-
- cos_test_angle=((source_alt2)+(distance*distance)-(test_alt*test_alt))/(2.0*source_alt*distance);
-
- /* Compare these two angles to determine if
- an obstruction exists. Since we're comparing
- the cosines of these angles rather than
- the angles themselves, the sense of the
- following "if" statement is reversed from
- what it would be if the angles themselves
- were compared. */
-
- if (cos_xmtr_angle>cos_test_angle)
- block=1;
- }
+ case 7:
+ fprintf(fd2,"Maritime Temperate, Over Sea");
+ break;
- /* At this point, we have the elevation angle
- to the first obstruction (if it exists). */
+ default:
+ fprintf(fd2,"Unknown");
}
- /* Determine path loss for each point along the
- path using Longley-Rice's point_to_point mode
- starting at x=2 (number_of_points = 1), the
- shortest distance terrain can play a role in
- path loss. */
-
- elev_l[0]=y-1; /* (number of points - 1) */
-
- /* Distance between elevation samples */
- elev_l[1]=METERS_PER_MILE*(path.distance[y]-path.distance[y-1]);
+ fprintf(fd2,")\nPolarization: %d (",LR.pol);
- point_to_point(elev_l, source.alt*METERS_PER_FOOT,
- destination.alt*METERS_PER_FOOT, LR.eps_dielect,
- LR.sgm_conductivity, LR.eno_ns_surfref, LR.frq_mhz,
- LR.radio_climate, LR.pol, LR.conf, LR.rel, loss,
- strmode, errnum);
+ if (LR.pol==0)
+ fprintf(fd2,"Horizontal");
- if (block)
- elevation=((acos(cos_test_angle))/deg2rad)-90.0;
- else
- elevation=((acos(cos_xmtr_angle))/deg2rad)-90.0;
-
- /* Integrate the antenna's radiation
- pattern into the overall path loss. */
+ if (LR.pol==1)
+ fprintf(fd2,"Vertical");
- x=(int)rint(10.0*(10.0-elevation));
+ fprintf(fd2,")\nFraction of Situations: %.1lf%c\n",LR.conf*100.0,37);
+ fprintf(fd2,"Fraction of Time: %.1lf%c\n",LR.rel*100.0,37);
- if (x>=0 && x<=1000)
+ if (LR.erp!=0.0)
{
- pattern=(double)LR.antenna_pattern[(int)azimuth][x];
+ fprintf(fd2,"Transmitter ERP: ");
- if (pattern!=0.0)
- patterndB=20.0*log10(pattern);
- }
+ if (LR.erp<1.0)
+ fprintf(fd2,"%.1lf milliwatts\n",1000.0*LR.erp);
- else
- patterndB=0.0;
+ if (LR.erp>=1.0 && LR.erp<10.0)
+ fprintf(fd2,"%.1lf Watts\n",LR.erp);
- total_loss=loss-patterndB;
+ if (LR.erp>=10.0 && LR.erp<10.0e3)
+ fprintf(fd2,"%.0lf Watts\n",LR.erp);
- if (metric)
- {
- fprintf(fd,"%f\t%f\n",KM_PER_MILE*(path.distance[path.length-1]-path.distance[y]),total_loss);
- fprintf(fd2,"%7.2f\t\t%7.2f\t\t %d\t%s\n",KM_PER_MILE*path.distance[y],total_loss, errnum, strmode);
+ if (LR.erp>=10.0e3)
+ fprintf(fd2,"%.3lf kilowatts\n",LR.erp/1.0e3);
}
- else
- {
- fprintf(fd,"%f\t%f\n",path.distance[path.length-1]-path.distance[y],total_loss);
- fprintf(fd2,"%7.2f\t\t%7.2f\t\t %d\t%s\n",path.distance[y],total_loss, errnum, strmode);
- }
+ fprintf(fd2,"\n-------------------------------------------------------------------------\n\n");
- errflag|=errnum;
+ fprintf(fd2,"Summary for the link between %s and %s:\n\n",source.name, destination.name);
- if (total_loss>maxloss)
- maxloss=total_loss;
+ if (patterndB!=0.0)
+ fprintf(fd2,"%s antenna pattern towards %s: %.3f (%.2f dB)\n", source.name, destination.name, pattern, patterndB);
- if (total_loss<minloss)
- minloss=total_loss;
- }
-
- fclose(fd);
-
- fprintf(fd2,"\nLongley-Rice path loss between %s and %s is %.2f dB.\n",source.name, destination.name, loss);
-
- if (patterndB!=0.0)
- fprintf(fd2,"Total path loss including TX antenna pattern is %.2f dB.\n",total_loss);
+ ReadPath(source, destination); /* source=TX, destination=RX */
- if (errflag)
- {
- fprintf(fd2,"\nNotes on \"errnum\":\n\n");
- fprintf(fd2," 0: No error. :-)\n");
- fprintf(fd2," 1: Warning! Some parameters are nearly out of range.\n");
- fprintf(fd2," Results should be used with caution.\n");
- fprintf(fd2," 2: Note: Default parameters have been substituted for impossible ones.\n");
- fprintf(fd2," 3: Warning! A combination of parameters is out of range.\n");
- fprintf(fd2," Results are probably invalid.\n");
- fprintf(fd2," Other: Warning! Some parameters are out of range.\n");
- fprintf(fd2," Results are probably invalid.\n\nEnd of Report\n");
- }
+ /* Copy elevations along path into the elev_l[] array. */
- fprintf(stdout,"Longley-Rice path loss between %s and %s is %.2f dB.\n",source.name, destination.name, loss);
+ for (x=0; x<path.length; x++)
+ elev_l[x+2]=path.elevation[x]*METERS_PER_FOOT;
- if (patterndB!=0.0)
- fprintf(stdout,"Total path loss including TX antenna pattern is %.2f dB.\n",total_loss);
+ fd=fopen("profile.gp","w");
- fprintf(stdout,"Path Loss Report written to: \"%s\"\n",report_name);
- fflush(stdout);
-
- fclose(fd2);
+ azimuth=rint(Azimuth(source,destination));
- if (name[0]==0)
- {
- /* Default filename and output file type */
-
- strncpy(filename,"loss\0",5);
- strncpy(term,"png\0",4);
- strncpy(ext,"png\0",4);
- }
-
- else
- {
- /* Grab extension and terminal type from "name" */
-
- for (x=0; name[x]!='.' && name[x]!=0 && x<254; x++)
- filename[x]=name[x];
-
- if (name[x]=='.')
+ for (y=2; y<(path.length-1); y++) /* path.length-1 avoids LR error */
{
- for (y=0, z=x, x++; name[x]!=0 && x<254 && y<14; x++, y++)
- {
- term[y]=tolower(name[x]);
- ext[y]=term[y];
- }
+ distance=5280.0*path.distance[y];
+ source_alt=four_thirds_earth+source.alt+path.elevation[0];
+ dest_alt=four_thirds_earth+destination.alt+path.elevation[y];
+ dest_alt2=dest_alt*dest_alt;
+ source_alt2=source_alt*source_alt;
- ext[y]=0;
- term[y]=0;
- filename[z]=0;
- }
+ /* Calculate the cosine of the elevation of
+ the receiver as seen by the transmitter. */
- else
- { /* No extension -- Default is png */
+ cos_xmtr_angle=((source_alt2)+(distance*distance)-(dest_alt2))/(2.0*source_alt*distance);
- filename[x]=0;
- strncpy(term,"png\0",4);
- strncpy(ext,"png\0",4);
- }
- }
+ if (got_elevation_pattern)
+ {
+ /* If an antenna elevation pattern is available, the
+ following code determines the elevation angle to
+ the first obstruction along the path. */
- /* Either .ps or .postscript may be used
- as an extension for postscript output. */
+ for (x=2, block=0; x<y && block==0; x++)
+ {
+ distance=5280.0*(path.distance[y]-path.distance[x]);
+ test_alt=four_thirds_earth+path.elevation[x];
- if (strncmp(term,"postscript",10)==0)
- strncpy(ext,"ps\0",3);
+ /* Calculate the cosine of the elevation
+ angle of the terrain (test point)
+ as seen by the transmitter. */
- else if (strncmp(ext,"ps",2)==0)
- strncpy(term,"postscript enhanced color\0",26);
+ cos_test_angle=((source_alt2)+(distance*distance)-(test_alt*test_alt))/(2.0*source_alt*distance);
- fprintf(stdout,"Writing \"%s.%s\"...",filename,ext);
- fflush(stdout);
+ /* Compare these two angles to determine if
+ an obstruction exists. Since we're comparing
+ the cosines of these angles rather than
+ the angles themselves, the sense of the
+ following "if" statement is reversed from
+ what it would be if the angles themselves
+ were compared. */
- fd=fopen("splat.gp","w");
+ if (cos_xmtr_angle>cos_test_angle)
+ block=1;
+ }
- fprintf(fd,"set grid\n");
- fprintf(fd,"set yrange [%2.3f to %2.3f]\n", minloss, maxloss);
- fprintf(fd,"set encoding iso_8859_1\n");
- fprintf(fd,"set term %s\n",term);
- fprintf(fd,"set title \"SPLAT! Loss Profile Along Path Between %s and %s (%.2f%c azimuth)\"\n",destination.name, source.name, Azimuth(destination,source),176);
+ /* At this point, we have the elevation angle
+ to the first obstruction (if it exists). */
+ }
- if (metric)
- fprintf(fd,"set xlabel \"Distance Between %s and %s (%.2f kilometers)\"\n",destination.name,source.name,KM_PER_MILE*Distance(destination,source));
- else
- fprintf(fd,"set xlabel \"Distance Between %s and %s (%.2f miles)\"\n",destination.name,source.name,Distance(destination,source));
+ /* Determine path loss for each point along the
+ path using Longley-Rice's point_to_point mode
+ starting at x=2 (number_of_points = 1), the
+ shortest distance terrain can play a role in
+ path loss. */
- if (got_azimuth_pattern || got_elevation_pattern)
- fprintf(fd,"set ylabel \"Total Path Loss (including TX antenna pattern) (dB)");
- else
- fprintf(fd,"set ylabel \"Longley-Rice Path Loss (dB)");
+ elev_l[0]=y-1; /* (number of points - 1) */
- fprintf(fd,"\"\nset output \"%s.%s\"\n",filename,ext);
- fprintf(fd,"plot \"profile.gp\" title \"Path Loss\" with lines\n");
+ /* Distance between elevation samples */
+ elev_l[1]=METERS_PER_MILE*(path.distance[y]-path.distance[y-1]);
- fclose(fd);
-
- x=system("gnuplot splat.gp");
+ point_to_point(elev_l, source.alt*METERS_PER_FOOT,
+ destination.alt*METERS_PER_FOOT, LR.eps_dielect,
+ LR.sgm_conductivity, LR.eno_ns_surfref, LR.frq_mhz,
+ LR.radio_climate, LR.pol, LR.conf, LR.rel, loss,
+ strmode, errnum);
- if (x!=-1)
- {
- unlink("splat.gp");
- unlink("profile.gp");
- unlink("reference.gp");
+ if (block)
+ elevation=((acos(cos_test_angle))/deg2rad)-90.0;
+ else
+ elevation=((acos(cos_xmtr_angle))/deg2rad)-90.0;
- fprintf(stdout," Done!\n");
- fflush(stdout);
- }
+ /* Integrate the antenna's radiation
+ pattern into the overall path loss. */
- else
- fprintf(stderr,"\n*** ERROR: Error occurred invoking gnuplot!\n");
-}
+ x=(int)rint(10.0*(10.0-elevation));
-void ObstructionReport(struct site xmtr, struct site rcvr, char report, double f)
-{
- int x;
- struct site site_x;
- double h_r, h_t, h_x, h_r_orig, cos_tx_angle, cos_test_angle,
- cos_tx_angle_f1, cos_tx_angle_fpt6, haavt, d_tx, d_x,
- h_r_f1, h_r_fpt6, h_f, h_los, lambda=0.0, azimuth,
- pattern, patterndB, distance, angle1, angle2;
- char report_name[80], string[255], string_fpt6[255],
- string_f1[255];
- FILE *fd;
+ if (x>=0 && x<=1000)
+ {
+ pattern=(double)LR.antenna_pattern[(int)azimuth][x];
- sprintf(report_name,"%s-to-%s.txt",xmtr.name,rcvr.name);
+ if (pattern!=0.0)
+ patterndB=20.0*log10(pattern);
+ }
- for (x=0; report_name[x]!=0; x++)
- if (report_name[x]==32 || report_name[x]==17 || report_name[x]==92 || report_name[x]==42 || report_name[x]==47)
- report_name[x]='_';
+ else
+ patterndB=0.0;
- fd=fopen(report_name,"w");
+ total_loss=loss-patterndB;
- fprintf(fd,"\n\t\t--==[ SPLAT! v%s Obstruction Report ]==--\n\n",splat_version);
- fprintf(fd,"Analysis of great circle path between %s and %s:\n",xmtr.name, rcvr.name);
- fprintf(fd,"\n-------------------------------------------------------------------------\n\n");
- fprintf(fd,"Transmitter site: %s\n",xmtr.name);
+ if (metric)
+ fprintf(fd,"%f\t%f\n",KM_PER_MILE*(path.distance[path.length-1]-path.distance[y]),total_loss);
+ else
+ fprintf(fd,"%f\t%f\n",path.distance[path.length-1]-path.distance[y],total_loss);
- if (xmtr.lat>=0.0)
- {
- fprintf(fd,"Site location: %.4f North / %.4f West",xmtr.lat, xmtr.lon);
- fprintf(fd, " (%s N / ", dec2dms(xmtr.lat));
- }
+ if (total_loss>maxloss)
+ maxloss=total_loss;
- else
- {
- fprintf(fd,"Site location: %.4f South / %.4f West",-xmtr.lat, xmtr.lon);
- fprintf(fd, " (%s S / ", dec2dms(xmtr.lat));
- }
+ if (total_loss<minloss)
+ minloss=total_loss;
+ }
- fprintf(fd, "%s W)\n", dec2dms(xmtr.lon));
+ fclose(fd);
- if (metric)
- {
- fprintf(fd,"Ground elevation: %.2f meters AMSL\n",METERS_PER_FOOT*GetElevation(xmtr));
- fprintf(fd,"Antenna height: %.2f meters AGL / %.2f meters AMSL\n",METERS_PER_FOOT*xmtr.alt, METERS_PER_FOOT*(xmtr.alt+GetElevation(xmtr)));
- }
+ distance=Distance(source,destination);
- else
- {
- fprintf(fd,"Ground elevation: %.2f feet AMSL\n",GetElevation(xmtr));
- fprintf(fd,"Antenna height: %.2f feet AGL / %.2f feet AMSL\n",xmtr.alt, xmtr.alt+GetElevation(xmtr));
- }
- haavt=haat(xmtr);
+ if (distance!=0.0)
+ {
+ free_space_loss=36.6+(20.0*log10(LR.frq_mhz))+(20.0*log10(distance));
- if (haavt>-4999.0)
- {
- if (metric)
- fprintf(fd,"Antenna height above average terrain: %.2f meters\n",METERS_PER_FOOT*haavt);
- else
- fprintf(fd,"Antenna height above average terrain: %.2f feet\n",haavt);
- }
+ fprintf(fd2,"Free space path loss: %.2f dB\n",free_space_loss);
+ }
- pattern=1.0;
- patterndB=0.0;
- distance=Distance(xmtr,rcvr);
- azimuth=Azimuth(xmtr,rcvr);
- angle1=ElevationAngle(xmtr,rcvr);
- angle2=ElevationAngle2(xmtr,rcvr,earthradius);
+ fprintf(fd2,"Longley-Rice path loss: %.2f dB\n",loss);
- if (got_azimuth_pattern || got_elevation_pattern)
- {
- x=(int)rint(10.0*(10.0-angle2));
+ if (free_space_loss!=0.0)
+ fprintf(fd2,"Attenuation due to effects of terrain: %.2f dB\n",loss-free_space_loss);
- if (x>=0 && x<=1000)
- pattern=(double)LR.antenna_pattern[(int)rint(azimuth)][x];
+ if (patterndB!=0.0)
+ fprintf(fd2,"Total path loss including %s antenna pattern: %.2f dB\n",source.name,total_loss);
- if (pattern!=1.0)
+ if (LR.erp!=0.0)
{
- fprintf(fd,"Antenna pattern toward %s: %.3f",rcvr.name,pattern);
- patterndB=20.0*log10(pattern);
- fprintf(fd," (%.2f dB)\n",patterndB);
+ field_strength=(137.26+(20.0*log10(LR.frq_mhz))-total_loss)+(10.0*log10(LR.erp/1000.0));
+ fprintf(fd2,"Field strength at %s: %.2f dBuV/meter\n", destination.name,field_strength);
+ voltage=(pow(10.0,field_strength/20.0)*39.52726907)/LR.frq_mhz;
+ fprintf(fd2,"Voltage produced by a terminated 50 ohm 0 dBd gain antenna: %.2f uV\n",voltage);
+ voltage=(pow(10.0,field_strength/20.0)*48.41082007)/LR.frq_mhz;
+ fprintf(fd2,"Voltage produced by a terminated 75 ohm 0 dBd gain antenna: %.2f uV\n",voltage);
}
- }
-
- if (metric)
- fprintf(fd,"Distance to %s: %.2f kilometers\n",rcvr.name,KM_PER_MILE*distance);
-
- else
- fprintf(fd,"Distance to %s: %.2f miles\n",rcvr.name,distance);
-
- fprintf(fd,"Azimuth to %s: %.2f degrees\n",rcvr.name,azimuth);
-
- if (angle1>=0.0)
- fprintf(fd,"Elevation angle to %s: %+.4f degrees\n",rcvr.name,angle1);
-
- else
- fprintf(fd,"Depression angle to %s: %+.4f degrees\n",rcvr.name,angle1);
-
- if (angle1!=angle2)
- {
- if (angle2<0.0)
- fprintf(fd,"Depression");
- else
- fprintf(fd,"Elevation");
-
- fprintf(fd," angle to the first obstruction: %+.4f degrees\n",angle2);
- }
-
- fprintf(fd,"\n-------------------------------------------------------------------------\n\n");
-
- /* Receiver */
-
- fprintf(fd,"Receiver site: %s\n",rcvr.name);
-
- if (rcvr.lat>=0.0)
- {
- fprintf(fd,"Site location: %.4f North / %.4f West",rcvr.lat, rcvr.lon);
- fprintf(fd, " (%s N / ", dec2dms(rcvr.lat));
- }
-
- else
- {
- fprintf(fd,"Site location: %.4f South / %.4f West",-rcvr.lat, rcvr.lon);
- fprintf(fd, " (%s S / ", dec2dms(rcvr.lat));
- }
-
- fprintf(fd, "%s W)\n", dec2dms(rcvr.lon));
-
- if (metric)
- {
- fprintf(fd,"Ground elevation: %.2f meters AMSL\n",METERS_PER_FOOT*GetElevation(rcvr));
- fprintf(fd,"Antenna height: %.2f meters AGL / %.2f meters AMSL\n",METERS_PER_FOOT*rcvr.alt, METERS_PER_FOOT*(rcvr.alt+GetElevation(rcvr)));
- }
-
- else
- {
- fprintf(fd,"Ground elevation: %.2f feet AMSL\n",GetElevation(rcvr));
- fprintf(fd,"Antenna height: %.2f feet AGL / %.2f feet AMSL\n",rcvr.alt, rcvr.alt+GetElevation(rcvr));
- }
- haavt=haat(rcvr);
+ fprintf(fd2,"Mode of propagation: %s\n",strmode);
- if (haavt>-4999.0)
- {
- if (metric)
- fprintf(fd,"Antenna height above average terrain: %.2f meters\n",METERS_PER_FOOT*haavt);
- else
- fprintf(fd,"Antenna height above average terrain: %.2f feet\n",haavt);
+ fprintf(fd2,"\n-------------------------------------------------------------------------\n\n");
}
- azimuth=Azimuth(rcvr,xmtr);
- angle1=ElevationAngle(rcvr,xmtr);
- angle2=ElevationAngle2(rcvr,xmtr,earthradius);
-
- if (metric)
- fprintf(fd,"Distance to %s: %.2f kilometers\n",xmtr.name,KM_PER_MILE*distance);
- else
- fprintf(fd,"Distance to %s: %.2f miles\n",xmtr.name,distance);
-
- fprintf(fd,"Azimuth to %s: %.2f degrees\n",xmtr.name,azimuth);
-
- if (angle1>=0.0)
- fprintf(fd,"Elevation to %s: %+.4f degrees\n",xmtr.name,angle1);
-
- else
- fprintf(fd,"Depression angle to %s: %+.4f degrees\n",xmtr.name,angle1);
-
- if (angle1!=angle2)
- {
- if (angle2<0.0)
- fprintf(fd,"Depression");
- else
- fprintf(fd,"Elevation");
+ fprintf(stdout,"\nPath Loss Report written to: \"%s\"\n",report_name);
+ fflush(stdout);
- fprintf(fd," angle to the first obstruction: %+.4f degrees\n",angle2);
+ ObstructionAnalysis(source, destination, LR.frq_mhz, fd2);
- }
+ fclose(fd2);
- fprintf(fd,"\n-------------------------------------------------------------------------\n\n");
+ /* Skip plotting the graph if ONLY a path-loss report is needed. */
- if (report=='y')
+ if (graph_it)
{
- /* Generate profile of the terrain. Create the path
- from transmitter to receiver because that's the
- way the original los() function did it, and going
- the other way can yield slightly different results. */
-
- ReadPath(xmtr,rcvr);
- h_r=GetElevation(rcvr)+rcvr.alt+earthradius;
- h_r_f1=h_r;
- h_r_fpt6=h_r;
- h_r_orig=h_r;
- h_t=GetElevation(xmtr)+xmtr.alt+earthradius;
- d_tx=5280.0*Distance(rcvr,xmtr);
- cos_tx_angle=((h_r*h_r)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r*d_tx);
- cos_tx_angle_f1=cos_tx_angle;
- cos_tx_angle_fpt6=cos_tx_angle;
-
- if (f)
- lambda=9.8425e8/(f*1e6);
-
- /* At each point along the path calculate the cosine
- of a sort of "inverse elevation angle" at the receiver.
- From the antenna, 0 deg. looks at the ground, and 90 deg.
- is parallel to the ground.
-
- Start at the receiver. If this is the lowest antenna,
- then terrain obstructions will be nearest to it. (Plus,
- that's the way the original los() did it.)
-
- Calculate cosines only. That's sufficient to compare
- angles and it saves the extra computational burden of
- acos(). However, note the inverted comparison: if
- acos(A) > acos(B), then B > A. */
-
- for (x=path.length-1; x>0; x--)
+ if (name[0]==0)
{
- site_x.lat=path.lat[x];
- site_x.lon=path.lon[x];
- site_x.alt=0.0;
-
- h_x=GetElevation(site_x)+earthradius;
- d_x=5280.0*Distance(rcvr,site_x);
-
- /* Deal with the LOS path first. */
-
- cos_test_angle=((h_r*h_r)+(d_x*d_x)-(h_x*h_x))/(2.0*h_r*d_x);
-
- if (cos_tx_angle>cos_test_angle)
- {
- if (h_r==h_r_orig)
- fprintf(fd,"SPLAT! detected obstructions at:\n\n");
-
- if (site_x.lat>=0.0)
- {
- if (metric)
- fprintf(fd,"\t%.4f N, %.4f W, %5.2f kilometers, %6.2f meters AMSL\n",site_x.lat, site_x.lon, KM_PER_MILE*(d_x/5280.0), METERS_PER_FOOT*(h_x-earthradius));
- else
- fprintf(fd,"\t%.4f N, %.4f W, %5.2f miles, %6.2f feet AMSL\n",site_x.lat, site_x.lon, d_x/5280.0, h_x-earthradius);
- }
-
- else
- {
- if (metric)
- fprintf(fd,"\t%.4f S, %.4f W, %5.2f kilometers, %6.2f meters AMSL\n",-site_x.lat, site_x.lon, KM_PER_MILE*(d_x/5280.0), METERS_PER_FOOT*(h_x-earthradius));
- else
-
- fprintf(fd,"\t%.4f S, %.4f W, %5.2f miles, %6.2f feet AMSL\n",-site_x.lat, site_x.lon, d_x/5280.0, h_x-earthradius);
- }
- }
+ /* Default filename and output file type */
- while (cos_tx_angle>cos_test_angle)
- {
- h_r+=1;
- cos_test_angle=((h_r*h_r)+(d_x*d_x)-(h_x*h_x))/(2.0*h_r*d_x);
- cos_tx_angle=((h_r*h_r)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r*d_tx);
- }
-
- if (f)
- {
- /* Now clear the first Fresnel zone, but don't
- clutter the obstruction report. */
-
- cos_tx_angle_f1=((h_r_f1*h_r_f1)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r_f1*d_tx);
- h_los=sqrt(h_r_f1*h_r_f1+d_x*d_x-2*h_r_f1*d_x*cos_tx_angle_f1);
- h_f=h_los-sqrt(lambda*d_x*(d_tx-d_x)/d_tx);
-
- while (h_f<h_x)
- {
- h_r_f1+=1;
- cos_tx_angle_f1=((h_r_f1*h_r_f1)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r_f1*d_tx);
- h_los=sqrt(h_r_f1*h_r_f1+d_x*d_x-2*h_r_f1*d_x*cos_tx_angle_f1);
- h_f=h_los-sqrt(lambda*d_x*(d_tx-d_x)/d_tx);
- }
-
- /* And clear the 60% F1 zone. */
-
- cos_tx_angle_fpt6=((h_r_fpt6*h_r_fpt6)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r_fpt6*d_tx);
- h_los=sqrt(h_r_fpt6*h_r_fpt6+d_x*d_x-2*h_r_fpt6*d_x*cos_tx_angle_fpt6);
- h_f=h_los-0.6*sqrt(lambda*d_x*(d_tx-d_x)/d_tx);
-
- while (h_f<h_x)
- {
- h_r_fpt6+=1;
- cos_tx_angle_fpt6=((h_r_fpt6*h_r_fpt6)+(d_tx*d_tx)-(h_t*h_t))/(2.0*h_r_fpt6*d_tx);
- h_los=sqrt(h_r_fpt6*h_r_fpt6+d_x*d_x-2*h_r_fpt6*d_x*cos_tx_angle_fpt6);
- h_f=h_los-0.6*sqrt(lambda*d_x*(d_tx-d_x)/d_tx);
- }
- }
- }
-
- if (h_r>h_r_orig)
- {
- if (metric)
- sprintf(string,"\nAntenna at %s must be raised to at least %.2f meters AGL\nto clear all obstructions detected by SPLAT!\n",rcvr.name, METERS_PER_FOOT*(h_r-GetElevation(rcvr)-earthradius));
- else
- sprintf(string,"\nAntenna at %s must be raised to at least %.2f feet AGL\nto clear all obstructions detected by SPLAT!\n",rcvr.name, h_r-GetElevation(rcvr)-earthradius);
+ strncpy(filename,"loss\0",5);
+ strncpy(term,"png\0",4);
+ strncpy(ext,"png\0",4);
}
else
- sprintf(string,"\nNo obstructions to LOS path due to terrain were detected by SPLAT!\n");
-
- if (f)
{
- if (h_r_fpt6>h_r_orig)
- {
- if (metric)
- sprintf(string_fpt6,"\nAntenna at %s must be raised to at least %.2f meters AGL\nto clear 60%c of the first Fresnel zone.\n",rcvr.name, METERS_PER_FOOT*(h_r_fpt6-GetElevation(rcvr)-earthradius),37);
-
- else
- sprintf(string_fpt6,"\nAntenna at %s must be raised to at least %.2f feet AGL\nto clear 60%c of the first Fresnel zone.\n",rcvr.name, h_r_fpt6-GetElevation(rcvr)-earthradius,37);
- }
+ /* Grab extension and terminal type from "name" */
- else
- sprintf(string_fpt6,"\n60%c of the first Fresnel zone is clear.\n",37);
-
- if (h_r_f1>h_r_orig)
- {
- if (metric)
- sprintf(string_f1,"\nAntenna at %s must be raised to at least %.2f meters AGL\nto clear the first Fresnel zone.\n",rcvr.name, METERS_PER_FOOT*(h_r_f1-GetElevation(rcvr)-earthradius));
+ for (x=0; name[x]!='.' && name[x]!=0 && x<254; x++)
+ filename[x]=name[x];
- else
- sprintf(string_f1,"\nAntenna at %s must be raised to at least %.2f feet AGL\nto clear the first Fresnel zone.\n",rcvr.name, h_r_f1-GetElevation(rcvr)-earthradius);
+ if (name[x]=='.')
+ {
+ for (y=0, z=x, x++; name[x]!=0 && x<254 && y<14; x++, y++)
+ {
+ term[y]=tolower(name[x]);
+ ext[y]=term[y];
+ }
+ ext[y]=0;
+ term[y]=0;
+ filename[z]=0;
}
else
- sprintf(string_f1,"\nThe first Fresnel zone is clear.\n\n");
+ { /* No extension -- Default is png */
+
+ filename[x]=0;
+ strncpy(term,"png\0",4);
+ strncpy(ext,"png\0",4);
+ }
}
- }
-
- fprintf(fd,"%s",string);
- if (f)
- {
- fprintf(fd,"%s",string_f1);
- fprintf(fd,"%s",string_fpt6);
- }
+ /* Either .ps or .postscript may be used
+ as an extension for postscript output. */
- fclose(fd);
+ if (strncmp(term,"postscript",10)==0)
+ strncpy(ext,"ps\0",3);
- /* Display report summary on terminal */
+ else if (strncmp(ext,"ps",2)==0)
+ strncpy(term,"postscript enhanced color\0",26);
- /* Line-of-sight status */
+ fd=fopen("splat.gp","w");
- fprintf(stdout,"%s",string);
+ fprintf(fd,"set grid\n");
+ fprintf(fd,"set yrange [%2.3f to %2.3f]\n", minloss, maxloss);
+ fprintf(fd,"set encoding iso_8859_1\n");
+ fprintf(fd,"set term %s\n",term);
+ fprintf(fd,"set title \"SPLAT! Loss Profile Along Path Between %s and %s (%.2f%c azimuth)\"\n",destination.name, source.name, Azimuth(destination,source),176);
- if (f)
- {
- /* Fresnel zone status */
+ if (metric)
+ fprintf(fd,"set xlabel \"Distance Between %s and %s (%.2f kilometers)\"\n",destination.name,source.name,KM_PER_MILE*Distance(destination,source));
+ else
+ fprintf(fd,"set xlabel \"Distance Between %s and %s (%.2f miles)\"\n",destination.name,source.name,Distance(destination,source));
- fprintf(stdout,"%s",string_f1);
- fprintf(stdout,"%s",string_fpt6);
- }
+ if (got_azimuth_pattern || got_elevation_pattern)
+ fprintf(fd,"set ylabel \"Total Path Loss (including TX antenna pattern) (dB)");
+ else
+ fprintf(fd,"set ylabel \"Longley-Rice Path Loss (dB)");
- fprintf(stdout, "\nObstruction report written to: \"%s\"\n",report_name);
+ fprintf(fd,"\"\nset output \"%s.%s\"\n",filename,ext);
+ fprintf(fd,"plot \"profile.gp\" title \"Path Loss\" with lines\n");
- fflush(stdout);
+ fclose(fd);
+
+ x=system("gnuplot splat.gp");
+
+ if (x!=-1)
+ {
+ unlink("splat.gp");
+ unlink("profile.gp");
+ unlink("reference.gp");
+
+ fprintf(stdout,"Path loss plot written to: \"%s.%s\"\n",filename,ext);
+ fflush(stdout);
+ }
+
+ else
+ fprintf(stderr,"\n*** ERROR: Error occurred invoking gnuplot!\n");
+ }
+
+ if (x!=-1)
+ unlink("profile.gp");
}
void SiteReport(struct site xmtr)
fprintf(fd,"\n---------------------------------------------------------------------------\n\n");
fclose(fd);
- fprintf(stdout,"\nSite analysis report written to: \"%s\"\n",report_name);
+ fprintf(stdout,"\nSite analysis report written to: \"%s\"",report_name);
}
void LoadTopoData(int max_lon, int min_lon, int max_lat, int min_lat)
/* This function loads the SDF files required
to cover the limits of the region specified. */
- int x, y, width, ymin, ymax;
+ int x, y, width, ymin, ymax;
width=ReduceAngle(max_lon-min_lon);
int LoadPLI(char *filename)
{
+ /* This function reads a SPLAT! path-loss output
+ file (-plo) for analysis and/or map generation. */
+
int error=0, max_west, min_west, max_north, min_north;
char string[80], *pointer=NULL;
double latitude=0.0, longitude=0.0, azimuth=0.0, elevation=0.0,
fprintf(stdout,"\nReading \"%s\"... ",filename);
fflush(stdout);
- fscanf(fd,"%lf, %lf, %lf, %lf, %lf",&latitude, &longitude, &azimuth, &elevation, &loss);
+ fgets(string,78,fd);
+ sscanf(string,"%lf, %lf, %lf, %lf, %lf",&latitude, &longitude, &azimuth, &elevation, &loss);
while (feof(fd)==0)
{
- if (loss>225.0)
- loss=225.0;
-
- if (loss<75.0)
- loss=75.0;
-
- loss-=75.0;
- loss/=10.0;
- loss+=1.0;
+ if (loss>255.0)
+ loss=255.0;
if (loss<=(double)maxdB)
- OrMask(latitude,longitude,((unsigned char)(loss))<<3);
+ PutSignal(latitude,longitude,((unsigned char)round(loss)));
- fscanf(fd,"%lf, %lf, %lf, %lf, %lf",&latitude, &longitude, &azimuth, &elevation, &loss);
+ fgets(string,78,fd);
+ sscanf(string,"%lf, %lf, %lf, %lf, %lf",&latitude, &longitude, &azimuth, &elevation, &loss);
}
fclose(fd);
fclose(fd);
- fprintf(stdout, "KML file written to: \"%s\"\n",report_name);
+ fprintf(stdout, "\nKML file written to: \"%s\"",report_name);
fflush(stdout);
}
rxlat, rxlon, txlat, txlon, west_min, west_max,
north_min, north_max;
- unsigned char coverage=0, LRmap=0, ext[20], terrain_plot=0,
- elevation_plot=0, height_plot=0,
+ unsigned char coverage=0, LRmap=0, terrain_plot=0,
+ elevation_plot=0, height_plot=0, map=0, nf=0,
longley_plot=0, cities=0, bfs=0, txsites=0,
- count, report='y', norm=0, topomap=0, geo=0,
- kml=0;
+ norm=0, topomap=0, geo=0, kml=0, pt2pt_mode=0,
+ area_mode=0, max_txsites, ngs=0, nolospath=0,
+ nositereports=0;
char mapfile[255], header[80], city_file[5][255],
elevation_file[255], height_file[255],
longley_file[255], terrain_file[255],
string[255], rxfile[255], *env=NULL,
- txfile[255], map=0, boundary_file[5][255],
+ txfile[255], boundary_file[5][255],
udt_file[255], rxsite=0, plo_filename[255],
- pli_filename[255], nf=0;
+ pli_filename[255], ext[20];
double altitude=0.0, altitudeLR=0.0, tx_range=0.0,
rx_range=0.0, deg_range=0.0, deg_limit,
deg_range_lon, er_mult, freq=0.0;
- struct site tx_site[4], rx_site;
+ struct site tx_site[32], rx_site;
FILE *fd;
if (argc==1)
{
fprintf(stdout,"\n\t\t --==[ SPLAT! v%s Available Options... ]==--\n\n",splat_version);
- fprintf(stdout," -t txsite(s).qth (max of 4)\n");
+ fprintf(stdout," -t txsite(s).qth (max of 4 with -c, max of 30 with -L)\n");
fprintf(stdout," -r rxsite.qth\n");
fprintf(stdout," -c plot coverage of TX(s) with an RX antenna at X feet/meters AGL\n");
fprintf(stdout," -L plot path loss map of TX based on an RX at X feet/meters AGL\n");
fprintf(stdout," -s filename(s) of city/site file(s) to import (5 max)\n");
- fprintf(stdout," -b filename(s) of cartographic boundary file(s) to import (max of 5)\n");
+ fprintf(stdout," -b filename(s) of cartographic boundary file(s) to import (5 max)\n");
fprintf(stdout," -p filename of terrain profile graph to plot\n");
fprintf(stdout," -e filename of terrain elevation graph to plot\n");
fprintf(stdout," -h filename of terrain height graph to plot\n");
fprintf(stdout," -o filename of topographic map to generate (.ppm)\n");
fprintf(stdout," -u filename of user-defined terrain file to import\n");
fprintf(stdout," -d sdf file directory path (overrides path in ~/.splat_path file)\n");
- fprintf(stdout," -n no analysis, brief report\n");
- fprintf(stdout," -N no analysis, no report\n");
fprintf(stdout," -m earth radius multiplier\n");
+ fprintf(stdout," -n do not plot LOS paths in .ppm maps\n");
+ fprintf(stdout," -N do not produce unnecessary site or obstruction reports\n");
fprintf(stdout," -f frequency for Fresnel zone calculation (MHz)\n");
fprintf(stdout," -R modify default range for -c or -L (miles/kilometers)\n");
fprintf(stdout," -db maximum loss contour to display on path loss maps (80-230 dB)\n");
fprintf(stdout," -nf do not plot Fresnel zones in height plots\n");
- fprintf(stdout," -plo filename of path-loss output file\n");
+ fprintf(stdout," -fz Fresnel zone clearance percentage (default = 60)\n");
+ fprintf(stdout," -ngs display greyscale topography as white in .ppm files\n");
+ fprintf(stdout," -erp override ERP in .lrp file (Watts)\n");
fprintf(stdout," -pli filename of path-loss input file\n");
+ fprintf(stdout," -plo filename of path-loss output file\n");
fprintf(stdout," -udt filename of user defined terrain input file\n");
+ fprintf(stdout," -kml generate Google Earth (.kml) compatible output\n");
fprintf(stdout," -geo generate an Xastir .geo georeference file (with .ppm output)\n");
- fprintf(stdout," -kml generate a Google Earth .kml file (for point-to-point links)\n");
fprintf(stdout," -metric employ metric rather than imperial units for all user I/O\n\n");
-
fprintf(stdout,"If that flew by too fast, consider piping the output through 'less':\n");
fprintf(stdout,"\n\tsplat | less\n\n");
fprintf(stdout,"Type 'man splat', or see the documentation for more details.\n\n");
fflush(stdout);
+
return 1;
}
y=argc-1;
+ kml=0;
+ geo=0;
metric=0;
rxfile[0]=0;
txfile[0]=0;
sdf_path[0]=0;
udt_file[0]=0;
path.length=0;
+ max_txsites=30;
LR.frq_mhz=0.0;
+ fzone_clearance=0.6;
rx_site.lat=91.0;
rx_site.lon=361.0;
+ longley_file[0]=0;
plo_filename[0]=0;
pli_filename[0]=0;
earthradius=EARTHRADIUS;
tx_site[x].lon=361.0;
}
- for (x=0; x<MAXSLOTS; x++)
+ for (x=0; x<MAXPAGES; x++)
{
dem[x].min_el=32768;
dem[x].max_el=-32768;
}
}
+ if (strcmp(argv[x],"-fz")==0)
+ {
+ z=x+1;
+
+ if (z<=y && argv[z][0] && argv[z][0]!='-')
+ {
+ sscanf(argv[z],"%lf",&fzone_clearance);
+
+ if (fzone_clearance<0.0 || fzone_clearance>100.0)
+ fzone_clearance=60.0;
+
+ fzone_clearance/=100.0;
+ }
+ }
+
if (strcmp(argv[x],"-o")==0)
{
z=x+1;
if (z<=y && argv[z][0] && argv[z][0]!='-')
{
sscanf(argv[z],"%lf",&altitude);
+ map=1;
coverage=1;
+ area_mode=1;
+ max_txsites=4;
}
}
{
strncpy(terrain_file,argv[z],253);
terrain_plot=1;
+ pt2pt_mode=1;
}
}
{
strncpy(elevation_file,argv[z],253);
elevation_plot=1;
+ pt2pt_mode=1;
}
}
{
strncpy(height_file,argv[z],253);
height_plot=1;
+ pt2pt_mode=1;
}
if (strcmp(argv[x],"-H")==0)
norm=0;
}
- if (strcmp(argv[x],"-n")==0)
- {
- report='n';
- map=1;
- }
-
- if (strcmp(argv[x],"-N")==0)
- {
- report='N';
- map=1;
- }
-
if (strcmp(argv[x],"-metric")==0)
metric=1;
if (strcmp(argv[x],"-nf")==0)
nf=1;
+ if (strcmp(argv[x],"-ngs")==0)
+ ngs=1;
+
+ if (strcmp(argv[x],"-n")==0)
+ nolospath=1;
+
+ if (strcmp(argv[x],"-N")==0)
+ {
+ nolospath=1;
+ nositereports=1;
+ }
+
if (strcmp(argv[x],"-d")==0)
{
z=x+1;
z=x+1;
- while (z<=y && argv[z][0] && argv[z][0]!='-' && txsites<4)
+ while (z<=y && argv[z][0] && argv[z][0]!='-' && txsites<30)
{
strncpy(txfile,argv[z],253);
tx_site[txsites]=LoadQTH(txfile);
if (z<=y && argv[z][0] && argv[z][0]!='-')
{
sscanf(argv[z],"%lf",&altitudeLR);
+ map=1;
+ LRmap=1;
+ area_mode=1;
if (coverage)
fprintf(stdout,"c and L are exclusive options, ignoring L.\n");
- else
- {
- LRmap=1;
- ReadLRParm(txfile);
- }
}
}
{
strncpy(longley_file,argv[z],253);
longley_plot=1;
- /* Doing this twice is harmless */
- ReadLRParm(txfile);
+ pt2pt_mode=1;
}
}
strncpy(rxfile,argv[z],253);
rx_site=LoadQTH(rxfile);
rxsite=1;
+ pt2pt_mode=1;
}
}
}
}
+ if (strcmp(argv[x],"-erp")==0)
+ {
+ z=x+1;
+
+ if (z<=y && argv[z][0] && argv[z][0]!='-')
+ {
+ sscanf(argv[z],"%lf",&forced_erp);
+
+ if (forced_erp<0.0)
+ forced_erp=-1.0;
+ }
+ }
+
if (strcmp(argv[x],"-plo")==0)
{
z=x+1;
map=0;
topomap=1;
- report='N';
}
else
{
y=LoadPLI(pli_filename);
- for (x=0; x<txsites; x++)
+ for (x=0; x<txsites && x<max_txsites; x++)
PlaceMarker(tx_site[x]);
if (rxsite)
LoadCities(city_file[x]);
}
- WritePPMLR(mapfile,geo);
+ WritePPMLR(mapfile,geo,kml,ngs,tx_site,txsites);
exit(0);
}
min_lon=(int)floor(tx_site[0].lon);
max_lon=(int)floor(tx_site[0].lon);
- for (y=0, z=0; z<txsites; z++)
+ for (y=0, z=0; z<txsites && z<max_txsites; z++)
{
txlat=(int)floor(tx_site[z].lat);
txlon=(int)floor(tx_site[z].lon);
max_lon=rxlon;
}
+
/* Load the required SDF files */
LoadTopoData(max_lon, min_lon, max_lat, min_lat);
- if (coverage | LRmap | topomap)
+ if (area_mode || topomap)
{
- if (LRmap)
- txsites=1;
-
- for (z=0; z<txsites; z++)
+ for (z=0; z<txsites && z<max_txsites; z++)
{
/* "Ball park" estimates used to load any additional
SDF files required to conduct this analysis. */
deg_range=max_range/69.0;
/* Prevent the demand for a really wide coverage
- from allocating more slots than are available
+ from allocating more "pages" than are available
in memory. */
- switch (MAXSLOTS)
+ switch (MAXPAGES)
{
case 2: deg_limit=0.25;
break;
if (deg_range_lon>deg_limit)
deg_range_lon=deg_limit;
-
north_min=(int)floor(tx_site[z].lat-deg_range);
north_max=(int)floor(tx_site[z].lat+deg_range);
LoadTopoData(max_lon, min_lon, max_lat, min_lat);
}
-
+
if (udt_file[0])
LoadUDT(udt_file);
- if (mapfile[0] && topomap==0)
- map=1;
-
- if (freq==0.0 && nf==0)
- freq=LR.frq_mhz;
-
- else if (nf==1)
- freq=0.0;
-
- if (coverage | LRmap)
- {
- for (x=0; x<txsites; x++)
- {
- if (coverage)
- PlotCoverage(tx_site[x],altitude);
-
- if (LRmap)
- PlotLRMap(tx_site[x],altitudeLR,plo_filename);
-
- PlaceMarker(tx_site[x]);
-
- if (report!='N')
- SiteReport(tx_site[x]);
- }
- map=1;
- }
+ /***** Let the SPLATting begin! *****/
- if (coverage==0 && LRmap==0)
+ if (pt2pt_mode)
{
PlaceMarker(rx_site);
- for (x=0; x<txsites; x++)
+ if (longley_plot)
{
- PlaceMarker(tx_site[x]);
+ /* Grab extension to determine graphic file type */
- if (report=='y')
- {
- switch (x)
- {
- case 0:
- PlotPath(tx_site[x],rx_site,1);
- break;
-
- case 1:
- PlotPath(tx_site[x],rx_site,8);
- break;
+ for (x=0; longley_file[x]!='.' && longley_file[x]!=0 && x<80; x++);
- case 2:
- PlotPath(tx_site[x],rx_site,16);
- break;
+ if (longley_file[x]=='.')
+ {
+ ext[0]='.';
+ for (y=1, z=x, x++; longley_file[x]!=0 && x<253 && y<14; x++, y++)
+ ext[y]=longley_file[x];
- case 3:
- PlotPath(tx_site[x],rx_site,32);
- }
+ ext[y]=0;
+ longley_file[z]=0;
}
- if (report!='N')
- ObstructionReport(tx_site[x],rx_site,report,freq);
-
- if (kml)
- WriteKML(tx_site[x],rx_site);
- }
- }
-
- if (map | topomap)
- {
- if (bfs)
- {
- for (x=0; x<bfs; x++)
- LoadBoundaries(boundary_file[x]);
- }
-
- if (cities)
- {
- for (x=0; x<cities; x++)
- LoadCities(city_file[x]);
+ else
+ {
+ ext[0]=0; /* No extension */
+ longley_file[x]=0;
+ }
}
- if (LRmap)
- WritePPMLR(mapfile,geo);
- else
- WritePPM(mapfile,geo);
- }
-
- if (terrain_plot)
- {
- if (txsites>1)
+ if (terrain_plot)
{
for (x=0; terrain_file[x]!='.' && terrain_file[x]!=0 && x<80; x++);
ext[0]=0; /* No extension */
terrain_file[x]=0;
}
-
- for (count=0; count<txsites; count++)
- {
- sprintf(string,"%s-%c%s%c",terrain_file,'1'+count,ext,0);
- GraphTerrain(tx_site[count],rx_site,string);
- }
}
- else
- GraphTerrain(tx_site[0],rx_site,terrain_file);
- }
-
- if (elevation_plot)
- {
- if (txsites>1)
+ if (elevation_plot)
{
for (x=0; elevation_file[x]!='.' && elevation_file[x]!=0 && x<80; x++);
ext[0]=0; /* No extension */
elevation_file[x]=0;
}
-
- for (count=0; count<txsites; count++)
- {
- sprintf(string,"%s-%c%s%c",elevation_file,'1'+count,ext,0);
- GraphElevation(tx_site[count],rx_site,string);
- }
}
- else
- GraphElevation(tx_site[0],rx_site,elevation_file);
- }
-
- if (height_plot)
- {
- if (txsites>1)
+ if (height_plot)
{
for (x=0; height_file[x]!='.' && height_file[x]!=0 && x<80; x++);
ext[0]=0; /* No extension */
height_file[x]=0;
}
-
- for (count=0; count<txsites; count++)
- {
- sprintf(string,"%s-%c%s%c",height_file,'1'+count,ext,0);
- GraphHeight(tx_site[count],rx_site,string,freq,norm);
- }
}
- else
- GraphHeight(tx_site[0],rx_site,height_file,freq,norm);
- }
-
- if (longley_plot)
- {
- if (txsites>1)
+ for (x=0; x<txsites && x<4; x++)
{
- for (x=0; longley_file[x]!='.' && longley_file[x]!=0 && x<80; x++);
+ PlaceMarker(tx_site[x]);
- if (longley_file[x]=='.') /* extension */
+ if (nolospath==0)
{
- ext[0]='.';
- for (y=1, z=x, x++; longley_file[x]!=0 && x<253 && y<14; x++, y++)
- ext[y]=longley_file[x];
+ switch (x)
+ {
+ case 0:
+ PlotPath(tx_site[x],rx_site,1);
+ break;
- ext[y]=0;
- longley_file[z]=0;
+ case 1:
+ PlotPath(tx_site[x],rx_site,8);
+ break;
+
+ case 2:
+ PlotPath(tx_site[x],rx_site,16);
+ break;
+
+ case 3:
+ PlotPath(tx_site[x],rx_site,32);
+ }
}
+ if (nositereports==0)
+ SiteReport(tx_site[x]);
+
+ if (kml)
+ WriteKML(tx_site[x],rx_site);
+
+ if (txsites>1)
+ sprintf(string,"%s-%c%s%c",longley_file,'1'+x,ext,0);
else
+ sprintf(string,"%s%s%c",longley_file,ext,0);
+
+ if (nositereports==0)
{
- ext[0]=0; /* No extension */
- longley_file[x]=0;
+ if (longley_file[0]==0)
+ {
+ ReadLRParm(tx_site[x],0);
+ PathReport(tx_site[x],rx_site,string,0); }
+
+ else
+ {
+ ReadLRParm(tx_site[x],1);
+ PathReport(tx_site[x],rx_site,string,longley_file[0]);
+ }
+ }
+
+ if (terrain_plot)
+ {
+ if (txsites>1)
+ sprintf(string,"%s-%c%s%c",terrain_file,'1'+x,ext,0);
+ else
+ sprintf(string,"%s%s%c",terrain_file,ext,0);
+
+ GraphTerrain(tx_site[x],rx_site,string);
+ }
+
+ if (elevation_plot)
+ {
+ if (txsites>1)
+ sprintf(string,"%s-%c%s%c",elevation_file,'1'+x,ext,0);
+ else
+ sprintf(string,"%s%s%c",elevation_file,ext,0);
+
+ GraphElevation(tx_site[x],rx_site,string);
+ }
+
+ if (height_plot)
+ {
+ if (freq==0.0 && nf==0)
+ freq=LR.frq_mhz;
+
+ if (txsites>1)
+ sprintf(string,"%s-%c%s%c",height_file,'1'+x,ext,0);
+ else
+ sprintf(string,"%s%s%c",height_file,ext,0);
+
+ GraphHeight(tx_site[x],rx_site,string,freq,norm);
}
+ }
+ }
+
+ if (area_mode && topomap==0)
+ {
+ for (x=0; x<txsites && x<max_txsites; x++)
+ {
+ if (coverage)
+ PlotCoverage(tx_site[x],altitude);
+
+ else if (ReadLRParm(tx_site[x],1))
+ PlotLRMap(tx_site[x],altitudeLR,plo_filename);
+
+ SiteReport(tx_site[x]);
+ }
+ }
+
+ if (map || topomap)
+ {
+ /* Label the map */
- for (count=0; count<txsites; count++)
+ if (cities)
+ {
+ if (kml==0)
{
- sprintf(string,"%s-%c%s%c",longley_file,'1'+count,ext,0);
- GraphLongley(tx_site[count],rx_site,string);
+ for (x=0; x<txsites && x<max_txsites; x++)
+ PlaceMarker(tx_site[x]);
}
+
+ for (y=0; y<cities; y++)
+ LoadCities(city_file[y]);
+ }
+
+ /* Load city and county boundary data files */
+
+ if (bfs)
+ {
+ for (y=0; y<bfs; y++)
+ LoadBoundaries(boundary_file[y]);
}
+ /* Plot the map */
+
+ if (coverage || pt2pt_mode || topomap)
+ WritePPM(mapfile,geo,kml,ngs);
+
else
- GraphLongley(tx_site[0],rx_site,longley_file);
+ {
+ if (LR.erp==0.0)
+ WritePPMLR(mapfile,geo,kml,ngs,tx_site,txsites);
+ else
+ WritePPMSS(mapfile,geo,kml,ngs,tx_site,txsites);
+ }
}
+ printf("\n");
+
+ /* That's all, folks! */
+
return 0;
}
-
+++ /dev/null
-15.000 ; Earth Dielectric Constant (Relative permittivity)
-0.005 ; Earth Conductivity (Siemens per meter)
-301.000 ; Atmospheric Bending Constant (N-Units)
-300.000 ; Frequency in MHz (20 MHz to 20 GHz)
-5 ; Radio Climate
-0 ; Polarization (0 = Horizontal, 1 = Vertical)
-0.50 ; Fraction of situations
-0.50 ; Fraction of time
-
-Please consult SPLAT! documentation for the meaning and use of this data.
================
Utilities for use with SPLAT! software are found under the
-splat-1.1.1/utils directory. They include the following:
+splat-1.2.1/utils directory. They include the following:
srtm2sdf
In all cases, SDF files are written into the current working directory.
+The srtm2sdf utility may also be used to convert 3-arc second SRTM data
+in Band Interleaved by Line (.BIL) format for use with SPLAT! This data
+is available via the web at: http://seamless.usgs.gov/website/seamless/
+
+Once the region of the world has been selected at this site, select the
+"Define Download Area By Coordinates" button under "Downloads". Proceed
+to request the download of the region(s) desired in 1 degree by 1 degree
+regions only, and make sure bounding coordinates entered fall exactly on
+whole numbers of latitude and longitude (no decimal fractions of a degree).
+
+Select the "Add Area" button at the bottom.
+
+On the next screen, select "Modify Data Request". On the subsequent screen,
+de-select the National Elevation Dataset (NED) format and select "SRTM 3 arc
+sec - Shuttle Radar Topography Mission [Finished]". Change the format from
+ArcGrid to BIL, and from HTML to TXT.
+
+Select the "Save Changes and Return To Summary" button.
+
+Select the "Download" button, and save the file once it has been sent to
+your web browser.
+
+Uncompressing the file will generate a directory containing all files
+contained within the downloaded archive. Move into the directory and
+invoke srtm2sdf as described above with the filename having the .bil
+extension given as its argument. Finally, move or copy the generated
+.sdf file to your SPLAT! working directory.
+
usgs2sdf
========
---
John A. Magliacane, KD2BD
-March 2006
+August 2007
#!/bin/bash
#
# Simple shell script for building SPLAT! and associated utilities.
-# Written by John A. Magliacane, KD2BD May 2002. Updated February 2006.
+# Written by John A. Magliacane, KD2BD May 2002. Updated October 2007.
#
build_citydecoder()
build_srtm2sdf()
{
echo -n "Compiling srtm2sdf... "
+<<<<<<< build
cc -Wall -O3 -lbz2 -fomit-frame-pointer srtm2sdf.c -o srtm2sdf
+=======
+ cc -Wall -O3 -s -fomit-frame-pointer srtm2sdf.c -lbz2 -o srtm2sdf
+>>>>>>> 1.1.1.4
echo "Done!"
}
}
if [ $# == "0" ]; then
- echo "Usage: build { citydecoder, usgs2sdf, fontdata, all }"
+ echo "Usage: build { citydecoder, srtm2sdf, usgs2sdf, fontdata, all }"
else
if [ $1 == "citydecoder" ]; then
echo "Usage: build { citydecoder, srtm2sdf, usgs2sdf, fontdata, all }"
fi
fi
-
-/************************************************************\
- ** Created originally by Jonathan Naylor, G4KLX **
- ** Later embellished by John Magliacane, KD2BD to **
- ** detect and handle voids found in the SRTM data **
- ************************************************************
- ** Compile like this: **
- ** cc -Wall -O3 -s -lbz2 srtm2sdf.c -o srtm2sdf **
- ** Last modification: 18-Mar-2006 **
-\************************************************************/
+/**************************************************************\
+ ** Created originally by Jonathan Naylor, G4KLX **
+ ** Later embellished by John Magliacane, KD2BD to **
+ ** detect and handle voids found in the SRTM data **
+ ** and to handle SRTM data in .BIL as well as .HGT format. **
+ **************************************************************
+ ** Compile like this: **
+ ** cc -Wall -O3 -s -lbz2 srtm2sdf.c -o srtm2sdf **
+ ** Last modification: 23-Sep-2007 **
+\**************************************************************/
#include <stdio.h>
#include <stdlib.h>
#define BZBUFFER 65536
-char sdf_filename[25], sdf_path[255], replacement_flag, opened=0;
-int srtm[1201][1201], usgs[1200][1200], max_north, max_west,
- min_north, min_west, merge=0, min_elevation, bzerror;
+char sdf_filename[25], sdf_path[255], replacement_flag, opened=0,
+ hgt=0, bil=0;
+
+int srtm[1201][1201], usgs[1200][1200], max_north, max_west,
+ min_north, min_west, merge=0, min_elevation, bzerror;
int ReadSRTM(char *filename)
{
- int x, y, infile, byte, bytes_read;
+ int x, y, infile, byte=0, bytes_read;
unsigned char error, buffer[2];
- char north[3], west[4], *base=NULL;
+ char north[3], west[4], *base=NULL, blw_filename[255];
+ double cell_size, deg_north, deg_west;
+ FILE *fd=NULL;
if (strstr(filename, ".zip")!=NULL)
{
}
- if (strstr(filename, ".hgt")==NULL)
+ if (strstr(filename, ".tgz")!=NULL)
+ {
+ fprintf(stderr, "*** Error: \"%s\" must be uncompressed\n",filename);
+ return -1;
+
+ }
+
+ if ((strstr(filename, ".hgt")==NULL) && (strstr(filename, ".bil")==NULL))
{
- fprintf(stderr, "*** Error: \"%s\" does not have the correct extension (.hgt)\n",filename);
+ fprintf(stderr, "*** Error: \"%s\" does not have the correct extension (.hgt or .bil)\n",filename);
return -1;
}
+ if (strstr(filename, ".hgt")!=NULL)
+ hgt=1;
+
+ if (strstr(filename, ".bil")!=NULL)
+ bil=1;
+
base=strrchr(filename, '/');
-
+
if (base==NULL)
base=filename;
else
base+=1;
- north[0]=base[1];
- north[1]=base[2];
- north[2]=0;
+ if (hgt)
+ {
+ /* We obtain coordinates from the base of the .HGT filename */
+
+ north[0]=base[1];
+ north[1]=base[2];
+ north[2]=0;
- west[0]=base[4];
- west[1]=base[5];
- west[2]=base[6];
- west[3]=0;
+ west[0]=base[4];
+ west[1]=base[5];
+ west[2]=base[6];
+ west[3]=0;
- if ((base[0]!='N' && base[0]!='S') || (base[3]!='W' && base[3]!='E'))
- {
- fprintf(stderr, "*** Error: \"%s\" doesn't look like a valid SRTM filename.\n", filename);
- return -1;
+ if ((base[0]!='N' && base[0]!='S') || (base[3]!='W' && base[3]!='E'))
+ {
+ fprintf(stderr, "*** Error: \"%s\" doesn't look like a valid .hgt SRTM filename.\n", filename);
+ return -1;
+ }
+
+ max_west=atoi(west);
+
+ if (base[3]=='E')
+ max_west=360-max_west;
+
+ min_west=max_west-1;
+
+ if (max_west==360)
+ max_west=0;
+
+ if (base[0]=='N')
+ min_north=atoi(north);
+ else
+ min_north=-atoi(north);
+
+ max_north=min_north+1;
}
- max_west=atoi(west);
+ if (bil)
+ {
+ /* We obtain .BIL file coordinates
+ from the corresponding .BLW file */
- if (base[3]=='E')
- max_west=360-max_west;
+ strncpy(blw_filename,filename,250);
+ x=strlen(filename);
- min_west=max_west-1;
+ if (x>3)
+ {
+ blw_filename[x-2]='l';
+ blw_filename[x-1]='w';
+ blw_filename[x]=0;
- if (max_west==360)
- max_west=0;
+ fd=fopen(blw_filename,"rb");
- if (base[0]=='N')
- min_north=atoi(north);
- else
- min_north=-atoi(north);
+ if (fd!=NULL)
+ {
+ fscanf(fd,"%lf",&cell_size);
+
+ if ((cell_size<0.0008) || (cell_size>0.0009))
+ {
+ printf("\n*** .BIL file's cell size is incompatible with SPLAT!!\n");
+ exit(1);
+ }
+
+ fscanf(fd,"%lf",°_west);
+ fscanf(fd,"%lf",°_west);
+ fscanf(fd,"%lf",°_west);
+
+ fscanf(fd,"%lf",°_west);
+
+ fscanf(fd,"%lf",°_north);
+
+ fclose(fd);
+ }
+
+ min_north=(int)(deg_north);
+ max_north=min_north+1;
+
+ if (deg_west<0.0)
+ deg_west=-deg_west;
+ else
+ deg_west=360.0-deg_west;
+
+ min_west=(int)(deg_west);
+
+ if (min_west==360)
+ min_west=0;
- max_north=min_north+1;
+ max_west=min_west+1;
+ }
+ }
infile=open(filename, O_RDONLY);
if (bytes_read==2)
{
- byte=buffer[1]+(buffer[0]<<8);
+ if (bil)
+ {
+ /* "little-endian" structure */
+
+ byte=buffer[0]+(buffer[1]<<8);
- if (buffer[0]&128)
- byte-=0x10000;
+ if (buffer[1]&128)
+ byte-=0x10000;
+ }
+
+ if (hgt)
+ {
+ /* "big-endian" structure */
+
+ byte=buffer[1]+(buffer[0]<<8);
+
+ if (buffer[0]&128)
+ byte-=0x10000;
+ }
/* Flag problem elevations here */
+ if (byte<-32768)
+ byte=-32768;
+
+ if (byte>32767)
+ byte=32767;
+
if (byte<=min_elevation)
replacement_flag=1;
if (error)
{
fprintf(stderr,"\n*** Error: Premature EOF detected while reading \"%s\"! :-(\n",filename);
- return -1;
}
close(infile);
{
sscanf(argv[z],"%d",&min_elevation);
- if (min_elevation<-32768)
+ if (min_elevation<-32767)
min_elevation=0;
}
}
projects / debian / splat / commitdiff