updates rom 10-16-2017

docs/chapters/chapterI/section01.md

@@ -8,7 +8,7 @@ This document, the *Geosupport System User Programming Guide* , is a comprehensi
 
 Geosupport is installed on IBM mainframes at the city computer centers listed in [Appendix 7](/appendices/appendix07/), where it is used by most city agencies as an integral component of many of their major data processing applications.  An employee of each computer center’s custodial agency, generally a systems programmer, has been designated as the <u> Geosupport System Administrator</u> (GSA) for that computer center.  The GSA is responsible for installing or coordinating the installation of new Geosupport file releases and software versions received from GSS.  At some computer centers, the GSA makes certain customizing modifications to Geosupport during installation, such as changing the data set names (DSNs) of Geosupport files to conform to local file naming conventions.  The GSA is also the first responder for users encountering system-related Geosupport problems, and interacts with GSS staff as needed to resolve such problems.  However, the GSA is not necessarily familiar with Geosupport from a user application perspective, and is not responsible for assisting users with application-related problems or design issues.  
 
-In general, Geosupport is accessible without restriction to anyone having a valid account at any of the computer centers where it is installed; no special passwords or security procedures are required beyond the normal data center logon procedures.  In addition to running on IBM (and IBM-compatible) mainframes, GSS has developed Geosupport Desktop Edition for running in the Windows environment.  There are also several methods by which Geosupport running on a city mainframe can be accessed by applications running on other hardware platforms, including 3270 emulation and access through the city’s Intranet. Geosupport is also available via GeoX, Linux, .net and Java.  This User Programming Guide can be used when programming in any of these environments.  Also, those who are writing a PC application for the Desktop Edition should also read the *UPG Supplement.*  
+In general, Geosupport is accessible without restriction to anyone having a valid account at any of the computer centers where it is installed; no special passwords or security procedures are required beyond the normal data center logon procedures.  In addition to running on IBM (and IBM-compatible) mainframes, GSS has developed Geosupport Desktop Edition for running in the Windows environment.  There are also several methods by which Geosupport running on a city mainframe can be accessed by applications running on other hardware platforms, including 3270 emulation and access through the city’s Intranet. Geosupport is also available via GeoX, Linux, .net and Java.  This User Programming Guide can be used when programming in any of these environments.   
 
 For many user applications, only a subset of Geosupport’s functions, features and data items are relevant.  In addition, many Geosupport options have defaults which are appropriate for most applications.  Thus, even though Geosupport is a large-scale, multi-feature system, the user effort required to design an application to access it is often relatively modest.  
 

docs/chapters/chapterVII/section01.md

@@ -32,7 +32,7 @@ Geosupport processes street configurations based on a simplified model of the ci
 [http://www1.nyc.gov/site/planning/data-maps/open-data.page#lion](http://www1.nyc.gov/site/planning/data-maps/open-data.page#lion)
 
 ![FigureVII-1 <>](/img/figureVII-1.png "Figure VII-1")
-<div class="img_tagline"> Figure VII-1: Single Line and double-Line Maps Contrasted </div>
+<div class="img_tagline"> Figure VII-1: Single Line and Double-Line Maps Contrasted </div>
 
 
 

docs/chapters/chapterVII/section03.md

@@ -1,6 +1,6 @@
 <h2>VII.3 Three-Street Configurations - Concepts and Terminology</h2>
 
-There are many applications in which geographic locations to be processed are identified in terms of an ‘on’ street between two cross streets.  Geosupport can process several types of such locations, namely street segments, blockfaces and street stretches.  We refer generically to all these types of locations as three-street configurations.
+There are many applications in which geographic locations to be processed are identified in terms of an ‘on’ street between two cross streets.  Geosupport can process several types of such locations, namely street segments, blockfaces and street stretches.  We refer generically to all these types of locations as <u>three-street configurations</u>.
 
 This section introduces concepts and terminology needed to discuss three-street configurations.  The three succeeding sections discuss the Geosupport functions that process the various types of three-street configurations:
 
@@ -28,25 +28,18 @@ Every street stretch is composed of a set of one or more street segments, which
 
 Some examples of street stretches and segments follow.
 
- <div class="textWithImage">
-
 <div class="imageWithFigure">
-<img src="../../../img/figureVII-12.png" alt="FigureVII-12" />
+<img class="smallImg" src="../../../img/figureVII-12.png" alt="FigureVII-12" />
 <p class="img_tagline">Figure V11-12: Street Stretch</p>
-</div>
-
-* The stretch of Madison Avenue between East 51st Street and East 52nd Street in Manhattan (see Figure VII-12) is a street segment.  The stretch of Madison Avenue between East 51st Street and East 54th Street is not a segment because its delimiting nodes are not consecutive along the ‘on’ street; it is a stretch consisting of three segments.
-
-</div>
-
 
 
- <div class="textWithImage" id="lincolnCenter" >
+* The stretch of Madison Avenue between East 51st Street and East 52nd Street in Manhattan (see Figure VII-12) is a street segment.  The stretch of Madison Avenue between East 51st Street and East 54th Street is not a segment because its delimiting nodes are not consecutive along the ‘on’ street; it is a stretch consisting of three segments.
 
+<div id="lincolnCenter">
 <div class="imageWithFigure">
-<img src="../../../img/figureVII-13.png" alt="FigureVII-13" />
-<p class="img_tagline">FigureV11-13: Street Stretch <br> Containing Gap</p>
-</div>
+<img class="smallImg" src="../../../img/figureVII-13.png" alt="FigureVII-13" />
+<p class="img_tagline">FigureV11-13: Street Stretch <br class="removeBr"> Containing Gap</p>
+
 
 * An example of a street stretch that is not connected is Manhattan’s West 64th Street between Central Park West and West End Avenue (see Figure VII-13).  West 64th Street has a gap (does not exist) between Columbus Avenue and Amsterdam Avenue, where it is interrupted by Lincoln Center.  As a result, the stretch in question consists of two sub-stretches that are not connected to each other.
 
@@ -74,8 +67,8 @@ For features that have no addresses, such as all railroad tracks and some highwa
 A blockface is a continuous frontage of a physical city block along one street, ignoring the presence of any bending points or other intervening nodes.  That is, the portions of a street frontage of a block that lie on both sides of a bending point are considered to be parts of the same blockface.
 
 <div class="imageWithFigure">
-<img src="../../../img/figureVII-14.png" alt="FigureVII-14" />
-<p class="img_tagline">FigureV11-14: Block with Four <br>Blockfaces</p>
+<img class="smallImg" src="../../../img/figureVII-14.png" alt="FigureVII-14" />
+<p class="img_tagline">FigureV11-14: Block with Four <br class="removeBr">Blockfaces</p>
 </div>
 
 For example, the Manhattan block bounded by Madison
@@ -86,16 +79,11 @@ and Park Avenues and East 51st and East 52nd Streets has the following four bloc
 * The west side of Park Avenue between East 51st and   East 52nd Streets
 * The north side of East 51st Street between Madison and Park Avenues
 
-An example of a stretch with a bending point in Manhattan is Commerce Street between Bedford and Barrow Streets (see Figure VII-4).  Both sides of this stretch are single blockfaces, even though the stretch consists of two segments connected at the bending point.
-
-## <span id="chapterVII.3.4"><u>T-Intersections</u></span>
-
-
-
- <div class="textWithImage">
+An example of a stretch with a bending point in Manhattan is Commerce Street between Bedford and Barrow Streets (see Figure VII-4).  Both sides of this stretch are single blockfaces, even though the stretch consists of two segments connected at the bending point.  
 
+## <span id="chapterVII.3.4"><u>T-Intersections</u></span>  
 <div class="imageWithFigure">
-<img src="../../../img/figureVII-15.png" alt="FigureVII-15" />
+<img class="smallImg" src="../../../img/figureVII-15.png" alt="FigureVII-15" />
 <p class="img_tagline">Figure VII-15: T-Intersection</p>
 </div>
 
@@ -105,23 +93,16 @@ A street stretch, and in particular a street segment, is considered to comprise
 
 An example of a T-intersection in Manhattan is the intersection of Fifth Avenue and East 41st Street (Figure VII-15).  Because of the presence of the New York Public Library main building along the west side of Fifth Avenue between West 40th and West 42nd Streets, there are no cross streets on the west side of Fifth Avenue where it intersects with East 41st Street.  The long blockface on the west side of Fifth Avenue encompasses two segments, each consisting of a portion of this long blockface facing a shorter entire blockface on the east side of Fifth Avenue.
 
- <div class="textWithImage">
-
 <div class="imageWithFigure">
-<img src="../../../img/figureVII-16.png" alt="FigureVII-16" />
-<p class="img_tagline">Figure V11-16: Two Consecutive <br> T- Intersections </p>
+<img class="smallImg" src="../../../img/figureVII-16.png" alt="FigureVII-16" />
+<p class="img_tagline">Figure V11-16: Two Consecutive <br class="removeBr"> T- Intersections </p>
 </div>
 
 It is possible for a street to have T-intersections at several consecutive nodes.  An example in Manhattan is the three-segment stretch of Lexington Avenue between East 42nd and East 45th Streets (Figure VII-16).  Because of the presence of the Grand Central Terminal complex on the west side of Lexington Avenue, East 43rd Street and East 44th Street intersect Lexington Avenue only on its east side, forming two consecutive T-intersections along Lexington Avenue.  As a result, the west side of this stretch is a single long blockface, which faces three shorter blockfaces on the east side of Lexington Avenue.
 
-</div>
-
-<div class="textWithImage">
-
 <div class="imageWithFigure">
-<img src="../../../img/figureVII-16.png" alt="FigureVII-16" />
-<p class="img_tagline">Figure VII-17: T-Intersections on <br> Alternating Sides of street </p>
-</div>
+<img class="smallImg" src="../../../img/figureVII-16.png" alt="FigureVII-16" />
+<p class="img_tagline">Figure VII-17: T-Intersections on <br class="removeBr"> Alternating Sides of street </p>
 
 When a street has consecutive T-intersections at which the cross streets are on alternating sides of the ‘on’ street, then long blockfaces on both sides of the ‘on’ street face each other in overlapping fashion, forming segments both sides of which consist of portions of those long blockfaces.  Union Avenue in Staten Island is an example (Figure VII-17).  Note that Union Avenue between Leyden Avenue and Walloon Street is a street segment, because the two delimiting intersections are consecutive along Union Avenue, even though the cross streets are on opposite sides of the ‘on’ street. </div>  
 <br>

docs/chapters/chapterVII/section04.md

@@ -11,7 +11,7 @@ Function 3 is designed to accept as input portions of a street that are, loosely
 The following examples illustrate the types of input data acceptable and not acceptable to Function 3.  For the Lexington Avenue examples (in Manhattan), see Figure VII-16.  For the Union Avenue examples (in Staten Island), see Figure VII-17.  For the Commerce Street examples (in Manhattan), see Figure VII-4.  For the Croes Avenue example (in the Bronx), see Figure VII-3.
 
 
-## <p class="center" id="chapterVII.4.1"><b>Input Data Examples for Function 3</b></p>
+## <p id="chapterVII.4.1"><b>Input Data Examples for Function 3</b></p>
 
 | Input ‘On’ Street | One Cross Str. | Other Cross Str. | Fn 3 Action | Reason for Action |
 | :------------- | :------------- | :------------- | :------------- | :------------- |
@@ -33,19 +33,17 @@ The following examples illustrate the types of input data acceptable and not acc
 | Commerce Street | Barrow Street | Bedford Street | Accepted | Both sides are single entire blockfaces |
 | Croes Avenue | Watson Avenue | Dead End | Accepted | Single entire segment |
 
-<b><u>Function 3 Input Data Specification and Validation</u></b>
+## <u>Function 3 Input Data Specification and Validation</u>
 
 Applications pass an input stretch to Function 3 by specifying three input streets, consisting of the ‘on’ street and two cross streets, in the appropriate WA1 input fields.  The input cross streets, but not the ‘on’ street, may be pseudo-streets or intersection names.  The input cross streets may be specified in either order.  As with all Geosupport street input, the three input streets to a Function 3 call are specified in the form of either street names or street codes.
 
 If either or both of the delimiting intersections of the input stretch has more than one cross street, the stretch may be specified using any of those cross streets.  For example, the segment of Chambers Street illustrated in Figure VII-11 may be specified either as ‘Chambers Street between Church Street and West Broadway’, or as ‘Chambers Street between Church Street and Hudson Street’.
 
-A successful two-work-area call to Function 3 signifies that the three input streets form a combination of an ‘on’ street and two cross streets that specify either a valid street segment or a valid street stretch at least one side of which is a single entire blockface.
-
-  <div class="textWithImage">
+A successful two-work-area call to Function 3 signifies that the three input streets form a combination of an ‘on’ street and two cross streets that specify either a valid street segment or a valid street stretch at least one side of which is a single entire blockface.  
 
 <div class="imageWithFigure">
-<img src="../../../img/figureVII-18.png" alt="FigureVII-18" />
-<p class="img_tagline">FigureVII-18: Ambiguous <br> Segment Specification </p>
+<img class="smallImg" src="../../../img/figureVII-18.png" alt="FigureVII-18" />
+<p class="img_tagline">FigureVII-18: Ambiguous <br class="removeBr"> Segment Specification </p>
 </div>
 
 ## <span id="chapterVII.4.2"><u>Ambiguous Function 3 Input Data</u></span>
@@ -55,14 +53,10 @@ Some combinations of an ‘on’ street and two cross streets are ambiguous as F
 Function 3 rejects such ambiguous input.  Unlike Function 2, which provides a means (compass direction input) for users to specify unambiguously an intersection of two streets that intersect in two different places, Geosupport provides the user with no recourse when Function 3 rejects an input stretch specification as ambiguous.
 
 
-</div>
-
 ## <span id="chapterVII.4.3"><u>Function 3 Output Data</u></span>
 
 If a two-work-area call to Function 3 is successful, information about both sides of the input stretch is returned in WA2.  (Note that the long WA2 option is available for the MSW Function 3.  [See Section II.5](/chapters/chapterII/section05/).)  Some of the data items apply to both the left and right sides of the segment, e.g. the ‘on’ street name and street code, segment length, ‘From’ node (COW only), ‘To’ node (COW only), etc.  Many of the data items in Function 3’s WA2 (both regular and long) are paired, with one item for the left side of the ‘on’ street and another item of the same type for the right side.  For example, there are fields for left and right ZIP code, for left and right 2010 census tract, and for left and right address ranges (each range consisting of a ‘from’ house number and a ‘to’ house number).  Other examples exist in the COW WA2 for Function 3, e.g. fields for  left and right Elections District (ED), for left and right Assembly District (AD), and for left and right Blockface ID (in COW Function 3 Extended).  As explained in [Chapter VII.3](/chapters/chapterVII/section03/), left and right are determined by the ‘on’ street’s logical direction, and therefore are independent of the order in which the user specifies the input cross streets.
 
-
-
 In the case of an input stretch encompassing more than one segment (the T-intersection and bend cases), the values of the WA2 items that Function 3 returns for the side of the street comprising more than one blockface are as follows.  The low and high house number values that are returned correspond to the entire stretch.  The values that are returned for all other side-related items correspond to the ‘last’ (relative to the stretch’s logical direction) blockface.  For example, consider Fifth Avenue in Manhattan between East 40 and East 42 Streets (see Figure VII-15).  Since the direction of increasing addresses along Fifth Avenue is from south to north, that is also Fifth Avenue’s logical direction.  It follows that the right side of the given stretch is the east side.  It consists of two blockfaces.  Relative to the logical direction, the ‘last’ of these blockfaces is the one between East 41 and East 42 Streets.  Accordingly, the right address range that is returned in WA2, consisting of the right low house number and the right high house number, corresponds to the entire right side of Fifth Avenue between East 40 and East 42 Streets.  The values returned for all other items for the right side of the input stretch correspond to the ‘last’ blockface, the one between East 41 and East 42 Streets.  The data returned represents two segments, but only one Segment ID is capable of being returned in the regular Function 3 WA2; consequently only the Segment ID with the lowest value is returned in the regular Function 3 WA2.  COW Function 3 is capable of returning all the Segment IDs that exist in the returned segment.  (See discussion of Auxiliary Segment Switch below.)  If the user requests Fifth Avenue between East 40th street and East 41st Street, the segment ID returned will be 00034174.  If the user requests Fifth Avenue between East 41st Street and East 42nd Street, the Segment ID returned will be 00034176.  However if the user requests Fifth Avenue between East 40th Street and East 42nd Street, which represents two segments, (and the Auxiliary Segment Option is not requested) the segment ID returned will be 00034174, which is numerically the lower of the two numbers.
 
 A COW Function 3 call may return, at the user’s option, all the Segment IDs (up to 70) of the segments that comprise the generated output segment.  To request this data, <u>the Auxiliary Segment Switch (AUXSEG a.k.a. SEGAUX)</u> in the COW WA1 must be set to ‘Y’.  This will result in all the Segment IDs (up to 70) being returned in a 500-byte area appended to the COW Function 3 WA2.

docs/css/main.css

@@ -278,6 +278,13 @@ img[alt^="GoatFunction_medium"] {
 .topVerticalTD {
   vertical-align:top !important;
 }
+.widthTD{
+  width: 180px !important;
+}
+.widthTDsmall{
+  width: 145px !important;
+}
+
 
 
 .bordered-table, .bordered-table th, .bordered-table td {

docs/css/pdf.css

@@ -162,12 +162,13 @@ img[alt^="GoatFunction_medium"] {
 /*.textWithImage {
   margin-top: 5em;
 }*/
-.topMargin {
+/*deleted to style pdf -ch7.2*/
+/*.topMargin {
   margin-top: 11em;
 }
 .topMargin u {
   font-size: 26px;
-}
+}*/
 #lincolnCenter {
   margin-top: 10em;
   margin-bottom: 6em;
@@ -258,3 +259,12 @@ a {
   color: #0a0101 !important;
   text-decoration: none !important;
 }
+
+.smallImg {
+  height: 250px;
+  width: 60%;
+}
+
+.removeBr {
+  display: none !important;
+}