Skip to content

Instantly share code, notes, and snippets.

@maptastik maptastik/index.html
Created Nov 14, 2014

Embed
What would you like to do?
<!DOCTYPE html>
<html>
<head>
<style id="jsbin-css">
body {
font-family: 'Open Sans', sans-serif;
color: #ffffff;
background-color: #27ae60;
}
.center {
text-align: center;
}
.new-language{
font-weight: bold;
}
.stricken {
text-decoration: line-through;
}
.disclaimer {
font-size: 10px;
}
.none {
list-style-type: none;
}
.decimal {
list-style-type: decimal;
}
.disc {
list-style-type: disc;
}
.lower-alpha {
list-style-type: lower-alpha;
}
.lower-roman {
list-style-type: lower-roman;}
</style>
</head>
<body>
<h2 class="center">CITY OF GEORGETOWN ORDINANCE NO. 2003-24</h2>
<h4 class="center">AN ORDINANCE RELATED TO THE AMENDMENT OF THE GEORGETOWN/SCOTT COUNTY SUBDIVISION &amp; DEVELOPMENT REGULATIONS REGARDING ARTICLE V &amp; VII – SPECIFICATIONS FOR DIGITAL SUBMITTALS FOR SUBDIVISION PLATS AND DEVELOPMENT PLANS &amp; REQUIREMENTS FOR CONTENT AND FORMAT</h4>
<p><strong>WHEREAS:</strong> The existing Subdivision &amp; Development Regulations requirements are not satisfying the community’s needs. The regulation requirements must be updated to reflect the current professional thinking, computerized mapping and best management practices to address continuous updates of the Geographic Information System. The purpose of these specifications is to form a standardized approach to the way a digital drawing submittal is collected, retrieved, stored and analyzed, affording the Georgetown-Scott County Planning Commission office the ability to share data among multiple agencies and to reduce redundancy. This new requirement will allow the Geographic Information System (GIS) to be as current as possible, making the information more valuable to all the agencies involved.</p>
<p><strong>WHEREAS:</strong> The Georgetown -Scott County Planning Commission (GSCPC) will require subdivision plats and development plans to be submitted in digital format upon adoption and publication. This requirement will call for delivery of the digital submittal at the final recording of the plat and certification of the plan. This requirement is in addition to the existing requirements outlined in the Subdivision and Development Regulations for Georgetown, Sadieville, Stamping Ground, and Scott County, Kentucky .</p>
<p>The intent of a digital submittal requirement is to enable the required hard copy and the digital submission to be produced from the same digital data without any modification by the firms submitting the data or the GSCPC staff. The digital submittal is not required to have engineering notes or engineering stamp/certification per 201 KAR 18:102 as it relates to KRS 322.340.</p>
<p>A basis of structure is required, such as layer elements and the use of the same geographic/geodetic base by the firms and GSCPC. However, there are no database linkage requirements. The digital submittal structure requirements are subject to change.</p>
<p>The hard copy will continue to be the official document.</p>
<p>The intent of this proposed ordinance is to provide an appropriate means to maintain the integrity and accuracy of the existing computerized database and base mapping within the Geographic Information System. </p>
<p><strong>WHEREAS:</strong> This proposed amendment to the Georgetown-Scott County Subdivision &amp; Development Regulations has been submitted to the citizens through a properly advertised public hearing before the Georgetown-Scott County Planning and Zoning Commission conducted at their August 8, 2002, and September 12, 2002, public meeting and re-reviewed at the Commission’s July 10, 2003, public meeting. The Commission voted unanimously to recommend the adoption of this amendment to the City Council of Georgetown;</p>
<h4>NOW, THEREFORE, BE IT ORDAINED BY THE COUNCIL FOR THE CITY OF GEORGETOWN, KENTUCKY, as follows:</h4>
<h4> SECTION ONE: NEW PROVISIONS.</h4>
<p>[New language is <span class="new-language">bold</span>. Language which is unchanged is not marked. Superseded language is shown as <span class="stricken">stricken</span>.]</p>
<ol class="decimal">
<li>
<ul class="none">
<li>A-E: unchanged</li>
<li>F: unchanged
<ol class="decimal">
<li>unchanged</li>
<li>unchanged</li>
<li>unchanged</li>
<li>unchanged</li>
<li>unchanged</li>
<li> Location and type of existing and new monuments and pins, which shall be placed at the intersection of property lines, the intersection of property lines, the intersection of street center lines, changes in street direction, and the intersections and angles of the development boundary.
<p class="disclaimer">Note: All survey information shall be to the “Minimum Standards of Practice for Land Surveying In Kentucky ”</p>
</li>
<li class="new-language">Requested Information <span class="stricken">(not required)</span>
<ol class="lower-alpha">
<li class="new-language">Digital Submittals of Plans and Plats in accordance with Article VII – Section 720</li>
</ol>
</li>
</ol>
</li>
</ul>
</li>
<li>THE SUBDIVISION &amp; DEVELOPMENT REGULATIONS, ARTICLE VII, is amended to include :
<p class="disclaimer">[New language is <span class="new-language">bold</span>. Language which is unchanged is not marked. Superseded language is shown as <span class="stricken">stricken</span>.]</p>
<h4 class="center">SECTION 720</h4>
<h4 class="center">CONTENT &amp; FORMAT REQUIREMENTS FOR SUBDIVISION PLATS AND DEVELOPMENT PLANS IN DIGITAL FORM</h4>
<ol class="decimal;">
<li>PURPOSE:
<p>The purpose is to describe the minimum content and format of digital files of subdivision plats and development plans before they are officially filed. This requirement does not include minor plats and/or boundary line adjustments.</p>
<p>Submittals of preliminary and construction plans for the subdivision plat or development plan are an optional delivery (requested), but not required.</p>
<p>This document applies to subdivision plats and development plans that are being officially filed.</p>
</li>
<li>SUPPORTED CAD DRAWING FILE FORMATS
<p>MicroStation&reg; stores its drawing in a design file format with the .DGN extension. The GSCPC will accept files generated by MicroStation&reg; up to Release MJ.</p>
<p>AutoCADâ stores its drawing in a proprietary drawing file format with the .DWG extension. The GSCPC will accept files generated by AutoCAD&reg; Release 14 and higher.</p>
<p>In addition to .DWG files, AutoCAD&reg; supports DXF (Drawing Interchange file) format, an industry standard interchange file format used to transfer data between CAD and GIS applications. However, when using this format the information put into the drawing may not completely transfer as it was drawn. The GSCPC will accept files generated by AutoCAD&reg; DXF.</p>
<p>The preferred format for digital submissions to the GIS office will be .DWG. The GSCPC may waive or adjust this requirement as specified herein.</p>
<p>File names will be eight or more characters, alpha-numeric, followed by the drawing software's extension.</p>
<p>The GIS softwares, ArcInfo and ArcView, can read the .DGN, .DWG, and .DXF file formats.</p>
</li>
<li>DATA LAYERING &amp; SUBMISSION REQUIREMENTS
<ol class="lower-alpha;">
<li><strong>Data Feature/Layer Requirement:</strong>
<ol class="decimal;">
<li class="new-language">Parcel Line – required to be snapped at common/shared feature.</li>
<li class="new-language">Buildings – required to be “closed” with closed command as performed by AutoCAD or similar software.</li>
</ol>
</li>
<li class="new-language">Annotation Requirement: Annotation submitted digitally will be identical to annotation submitted on the hard copy maps. The section on Data Layering Requirements defines requirements for submission of annotation.</li>
<li class="new-language">Coordinates Displayed as Text Requirement: When displaying x and y (and z) coordinates, the whole number for the coordinate will be shown to two (2) decimal positions, i.e., no constants will be applied.</li>
<li> The layer names must be identifiable by another person. For example, layer names created like the following are acceptable mon_pnt, lot_num, drng_area, ex_row, san_lin, swr_txt, wtr_lin.</li>
<li>Each layer must have only its element on it. For example, a water line must be on a water line layer versus the stormwater line or right-of-way line layers. In addition, with Microstation&reg;, each layer number needs to have a layer name associated with it. Or with other CAD software, the layer names must be identifiable like mon_pnt, lot_num, drng_area, ex_row, san_lin, swr_txt, wtr_lin.</li>
<li>All External reference files (xref) must be "bound" into the <span class="stricken">.DWG</span> CAD file prior to submittal <span class="new-language">or included with the submittal.</span></li>
<li>Public domain and custom AutoCAD&reg; (.shx) fonts are permitted in the drawing files only if the latest copies of each of these fonts are provided to the Georgetown-Scott County Planning Commission with the submittal of the .DWG file.</li>
<li>Text for any layer will be on its own layer. The layer name is requested to end in "txt." </li>
<li>The following table displays the data features, elements and requirements <span class="stricken">needed</span> <span class="new-language">REQUIRED</span> in a digital submittal. Additional layers are encouraged.
<ul class="none">
<li>
<table>
<thead>
<tr>
<th>Category</th>
<th>Data Feature/Layer</th>
<th>Element</th>
<th>**Preliminary** Plan or Plat Requirements</th>
<th>Final Plan or Plat Requirements</th>
</tr>
</thead>
<tbody>
<tr>
<td>Basic</td>
<td>Address Numbers</td>
<td>Text</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Basic</td>
<td>Bearings</td>
<td>Text</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Basic</td>
<td>Street Names</td>
<td>Text</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Basic</td>
<td>Structure (Buildings)</td>
<td><span class="stricken">Line,</span> Polygon</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Boundary</td>
<td>City Limits (Annexations)</td>
<td>Line <span class="new-language">or</span> Polygon</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Monument</td>
<td>Monument (Control and others)</td>
<td>Point symbol</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Monument</td>
<td>Monument Description (x,y,z)</td>
<td>Text</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Parcel</td>
<td>Boundary/Lot Lines</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Parcel</td>
<td>Building Set Back Line</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Parcel</td>
<td>Lot Numbers</td>
<td>Text</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Parcel</td>
<td>Starting Point of Legal Description</td>
<td>Text</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Street</td>
<td>Centerline</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Street</td>
<td>Curb Line</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Street</td>
<td>Right of Way</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Street</td>
<td>Street Name (proposed to, accepted by GSCPC)</td>
<td>Text</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Drainage Area</td>
<td>Polygon</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Drainage Easements</td>
<td>Line or Polygon</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Drainage Basins (retention/detention)</td>
<td>Polygon</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Existing Easements</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Sanitary Easements</td>
<td>Line or Polygon</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Sanitary Sewer Main</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Sanitary Sewer Manhole</td>
<td>Point <span class="new-language">symbol</span></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Stormwater Catch Basins</td>
<td>Point <span class="new-language">symbol</span></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Stormwater Mains</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Utility/Street Poles</td>
<td>Point <span class="new-language">symbol</span></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Utility Easements</td>
<td>Line or Polygon</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Water Hydrants</td>
<td>Point <span class="new-language">symbol</span></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Water Mains</td>
<td>Line</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Utilities</td>
<td>Water Meter</td>
<td>Point <span class="new-language">symbol</span></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Vegetation</td>
<td>Trees</td>
<td>Point <span class="new-language">symbol</span></td>
<td>X</td>
<td>X</td>
</tr>
</tbody>
</table>
</li>
<li>
<p>Key:</p>
<table>
<tbody>
<tr>
<td>Category</td>
<td>Broad groups of data to help organize this table</td>
</tr>
<tr>
<td>Data Feature/Layer</td>
<td>Layers that are required for delivery in digital submittal</td>
</tr>
<tr>
<td>Element</td>
<td>The symbol <span class="new-language">that</span> the element <span class="stricken">should be</span> <span class="new-language">typically</span> should be drawn with.</td>
</tr>
<tr>
<td>**Preliminary** Plan or Plat Requirement (Requested, not required)</td>
<td>This column indicates <span class="stricken">if the preliminary plan or plat needs this layer for GSCPC approval</span> <span class="new-language">the preferred layers requested for preliminary plan or plat approval by GSCPC.</span></td>
</tr>
<tr>
<td>Final Plan or Plat Requirement</td>
<td>This column indicates if the final plan or plat <span class="stricken">needs</span> <span class="new-language">shall have</span> this layer for GSCPC approval.</td>
</tr>
</tbody>
</table>
</li>
</ul>
</li>
</ol>
</li>
<li>MEDIA REQUIREMENTS
<ol class="lower-alpha">
<li>The following media are considered acceptable for digital submission of subdivision plats and development plans.
<table>
<tbody>
<tr>
<td>DOS 3.5"</td>
<td>DSHD diskettes</td>
<td>(1.44mb)</td>
</tr>
<tr>
<td>CD-R</td>
<td>Data disk</td>
<td>(650 - 700 MB)</td>
</tr>
</tbody>
</table>
<p>Files requiring less than one diskette for transmission will be written to diskette using the Copy Command in Windows or Windows NT.</p>
<p>Files requiring more than one diskette for transmission will be written to diskette using WinZip, to a tape using the Tape Backup utility, or onto a CD-R.</p>
<p>The software name and version used to create the copied data will appear on the diskette or CD label (see item (b) below.)</p>
<p>No other files will exist on the media.</p>
<p>No additional information will exist in the file aside from data being specifically transmitted to the GSCPC office.</p>
</li>
<li>All media will be submitted with labels indicating the following data (see example) and will be signed by the firm's authorized agent submitting the map. The purpose of the signature is to verify the transmittal of the data, not professional responsibility for the data. It is understood by GSCPC that the digital data is not a certified, legal document (201 KAR 18:102 as it relates to KRS 322.340). It is the responsibility of the GSCPC staff to refer to the recorded map for the corrected information.
<p>Example:</p>
<table>
<tbody>
<tr>
<td><span class="new-language">Project or</span> Subdivision Name:</td>
<td>Big Tree Acres</td>
</tr>
<tr>
<td>File Name:</td>
<td>bigtreacrs.dwg</td>
</tr>
<tr>
<td>Date:</td>
<td>July 1, 1998</td>
</tr>
<tr>
<td>Company Name:</td>
<td>Jones &amp; Associates, Inc.</td>
</tr>
<tr>
<td>LS / PE:</td>
<td>John Doe</td>
</tr>
<tr>
<td>Reg. No.:</td>
<td>L.S. 7801</td>
</tr>
<tr>
<td>Format:</td>
<td>DWG/DXF/DOS/4 Backup</td>
</tr>
<tr>
<td>Signature:</td>
<td>John Doe</td>
</tr>
</tbody>
</table>
</li>
<li>The media delivered to GSCPC can be returned upon request.</li>
<li>MEDIA SUBMISSION TIMELINE
<p>The digital file must be submitted at the time the GSCPC certifies the <span class="new-language">plat</span>/plan for recording in the County Clerk's Office.</p>
</li>
</ol>
</li>
<li>CONVENTIONAL HARD COPY SUBMISSION REQUIREMENTS
<p>The following requirements pertain to hard copy maps that are submitted in conjunction with a digital submittal. In order to facilitate the map checking process and to enable direct correlation between the hard copy map and the digital submission, the following points should be noted.</p>
<ul class="disc">
<li>Any distance, on or internal to, the boundary of the map must meet National Map Accuracy Standards.</li>
<li>The following convention for symbolization of monumentation is the preferred and recommended convention. Three monument symbols will be used.
<ul class="none">
<li>Control points - represented by a solid triangle</li>
<li>Found monuments - represented by a solid circle</li>
<li>Set Monuments - represented by a solid square</li>
</ul>
</li>
<p>A control or set monument description (x, y, and z) will be called out separately as required <span class="new-language">by the Kentucky State Plane Coordinate System North Zone NAD 1983 in U.S. survey feet (see also Section 7.b.)</span></p>
</ul>
</li>
<li>DATA INTEGRITY REQUIREMENTS
<p>The following requirements pertain to the mathematical integrity of the geometric data.</p>
<ul class="none">
<li>REQUIRED STANDARD: The requirement is to follow the 201 KAR 18.150 "The Standards of Practice for Professional Land Surveyors," Section 7, Measurement Specifications, (6) Table of Specifications by Class: Classification of Surveys, or current edition (latest).</li>
<li>RECOMMENDED STANDARDS:
<ol class="lower-alpha">
<li>The maximum error allowable between theoretically coincident points will be 9 mm (.03 feet).</li>
<li>The maximum error allowable between points on line and the line will be 6 mm (.02 feet).</li>
<li>The difference between distances calculated by inverting between the coordinates of points in the digital submission and the annotated distances shall not exceed 3 mm (.01 feet).</li>
<li>The difference in seconds between bearings calculated by inverting between the coordinates of points in the digital submission and the annotated bearings shall not exceed the maximum of (1031/dist (ft), 1").
<p>Examples:</p>
<table>
<thead>
<tr>
<th>Distance</th>
<th>Allowable Error in Bearing (seconds)</th>
</tr>
</thead>
<tbody>
<tr>
<td>50</td>
<td>21</td>
</tr>
<tr>
<td>100</td>
<td>11</td>
</tr>
<tr>
<td>200</td>
<td>6</td>
</tr>
<tr>
<td>1200</td>
<td>1</td>
</tr>
<tr>
<td>5000</td>
<td>1</td>
</tr>
</tbody>
</table>
</li>
<span class="stricken">
<li>Boundaries will be transmitted as closed figure. For example in a DWG file, a boundary would be represented as one polyline such as series of lines, rather than arcs and curves, then closed using the "close" command.</li>
<li>Annotation submitted digitally will be identical to annotation submitted on the hard copy maps. The section on Data Layering Requirements defines requirements for submission of annotation.</li>
<li>When displaying x and y (and z) coordinates, the whole number for the coordinate will be shown to two (2) decimal positions, i.e., no constants will be applied. </li>
</span>
</ol>
</li>
</ul>
</li>
<li>TIES TO HORIZONTAL CONTROL
<p>GSCPC will provide a DWG file of the control monument locations and point identification text. A control monument book of the monuments located in Scott County is available for viewing in the GSCPC office. These monuments use the horizontal datum NAD83 and vertical datum 1929 unless otherwise noted.</p>
<ol class="lower-alpha">
<li>The surveyor or engineer will be required to reference horizontal control monuments in accordance with the Subdivision and Development Regulations. Coordinates for these control monuments shall be shown on the digital file as required by the Data Layering and Submission Requirements section of this document.
<ol class="decimal">
<li>In areas where the minimum control monuments are not available, the use of two (2) boundary monuments located in opposite sides of the plan/plat can be referenced for horizontal control and x/y position.</li>
<li>Upon review with the surveyor/engineer, GSCPC may waive this requirement.</li>
</ol>
</li>
<li>The boundary of the submitted plan shall be tied into the Kentucky State Plane Coordinate System North Zone NAD 1983 in U.S. survey feet in at least two (2) locations or on opposite sides of the subdivision boundary as agreed upon by GSCPC staff.</li>
<li>The basis of bearings of the plat shall be the Kentucky State Plane Coordinate System North Zone NAD 1983 in U.S. survey feet, or latest revision of adjustment in at least two locations, preferably on opposite sides of the subdivision boundary as mutually agreed upon by the GSCPC staff.</li>
<li>If the boundary of the development is a parcel or lot of a plat already tied to the Kentucky State Plane Coordinate System North Zone NAD 1983, the requirements of paragraph (c) shall be waived with the stipulation that the surveyor or engineer be required to show existing monumentation and coordinates on the plan/plat.</li>
</ol>
</li>
<li>CHECKING OF DIGITAL DATA
<ol class="lower-alpha">
<li>The digital data will be checked for the following criteria:
<ol class="lower-roman">
<li>Identifiable layer names</li>
<li>Closure or the geometry of the <span class="stricken">boundary</span> <span class="new-language">features in the submittal</span></li>
<li>Verification that digital and hard copy maps are consistent</li>
<li>Correct geographic /geodetic position, i.e. correct coordinate system</li>
</ol>
</li>
<li>The developer will be given ten (10) working days from the day of notification of errors to correct and resubmit the corrected digital file.</li>
</ol>
<p>Once the digital data is corrected, resubmitted, and verified to be in accordance with the "Specifications for Digital Submittals and Requirements for Content and Format" document through the GSCPC's GIS Office, GSCPC staff will be issued a copy of the plat generated by the digital submittal. GSCPC staff will check it against the hard copy received to verify they coincide, and then proceed with the process of ensuring the information complies with the <em>Subdivision and Development Regulations for Georgetown , Sadieville, Stamping Ground, and Scott County, Kentucky</em> and make a recommendation to the Planning Commission</p>
</li>
<li>ADJUSTMENTS TO THESE REQUIREMENTS
<ol class="lower-alpha">
<li>The Georgetown-Scott County Planning Commission may waive or adjust requirements specified herein, upon a finding that the strict adherence of the requirements does not apply or is contrary to the long-term maintenance of the GIS of Georgetown and Scott County.</li>
<li>The GSCPC staff may upon review of the subdivision or development require submittal of the 'as-built' in accordance with these regulations based on minor or major amendments.</li>
<li><span class="stricken">Nine months from date of adoption, GSCPC staff will perform an audit of these requirements to monitor compliance and overall effectiveness and make amendments as needed.</span></li>
</ol>
</li>
</ol>
</li>
</ol>
<h4>SECTION TWO: EFFECTIVE DATE:</h4>
<p>This Ordinance shall take effect upon passage and publication.</p>
<p>The original ordinance was introduced and read for the first time at the Council’s regular meeting October 1, 2002, and for the second time, adopted and approved, at the Council’s regular meeting October 17, 2002 .</p>
<p>The foregoing Ordinance was introduced and read for the first time at the Council’s regular meeting August 7, 2003, and for the second time, adopted and approved, at the Council’s regular meeting August 21, 2003.</p>
<p>APPROVED BY: EVERETTE VARNEY, MAYOR</p>
<p>ATTESTED BY: SUE LEWIS, CLERK</p>
<script id="jsbin-source-css" type="text/css">body {
font-family: 'Open Sans', sans-serif;
color: #ffffff;
background-color: #27ae60;
}
.center {
text-align: center;
}
.new-language{
font-weight: bold;
}
.stricken {
text-decoration: line-through;
}
.disclaimer {
font-size: 10px;
}
.none {
list-style-type: none;
}
.decimal {
list-style-type: decimal;
}
.disc {
list-style-type: disc;
}
.lower-alpha {
list-style-type: lower-alpha;
}
.lower-roman {
list-style-type: lower-roman;}</script>
</body>
</html>
body {
font-family: 'Open Sans', sans-serif;
color: #ffffff;
background-color: #27ae60;
}
.center {
text-align: center;
}
.new-language{
font-weight: bold;
}
.stricken {
text-decoration: line-through;
}
.disclaimer {
font-size: 10px;
}
.none {
list-style-type: none;
}
.decimal {
list-style-type: decimal;
}
.disc {
list-style-type: disc;
}
.lower-alpha {
list-style-type: lower-alpha;
}
.lower-roman {
list-style-type: lower-roman;}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.