Montgomery County Planning Department of the Maryland National Capital Park and Planning Commission (M-NCPPC) 1993 - 2000 SDE.HYDRO_LINE vector digital data SDE.HYDRO_LINE withheld The data set contains hydrographic features as identified from the development of planimetric mapping from aerial photography as part of the GeoMaP initiative. It contains attribute which identify the specific features as well as a GeoMaP feature code assignment. Useful for reference of data for hydrographic features. en 2/2014 ground condition Complete Portions of county annually updated, countywide update cycle is based on a 5 year cycle -77.539563 -76.881771 39.362047 38.932517 1159770.678695 1345762.396773 461454.229071 617449.085606 Maryland Spatial Data Clearinghouse Places lake pond river stream single line stream hidden hydro reservoir hydro base map hydrography hydrography data hydrography file planimetric planimetric data Maryland Spatial Data Clearinghouse Places Montgomery County Maryland For the MC:MAPS Consortium (M-NCPPC, DIST, Montgomery College, Montgomery County Public Schools and WSSC) unrestricted use within their agency/department. Use outside the MC:MAPS Consortium is governed by copyright laws, GIS Data Products License and GIS Data Products Sales Agreement (an inter-agency agreement governing GIS sales throughout Montgomery County). GIS Data Products License Agreement: Limited to a specific project. Incorporating any MC:MAPS GIS data requires placement of the following in a conspicuous location on the face of the document: "The planimetric information shown on this plan is based on copyrighted GIS Data from M-NCPPC, and may not be copied or reproduced without express written permission from M-NCPPC." Warranties: MC:MAPS makes no warranty , express or implied, and disclaims all implied warranties of merchantability, integration, title and fitness of the GIS Data for a particular purpose. Liabilities: In no event will MC:MAPS be liable, whether in contract, tort (including negligence) or otherwise, for any direct, indirect, incidental or consequential damages including lost savings or profit, attorney's fees, lost data or business interruption even if MC:MAPS is notified in advance of such possibility. This includes damages incurred by customer or any third party. GIS Data Products Sales Agreement: Copying charge- A copying charge of $10 per tile will be collected for any GIS data request submitted by a business entity, under contract with a Consortium agency, who does not have that request filled by that agency. In addition, a signed Licensing Agreement and a letter from the agency, on the agency's letterhead, must accompany the data request at the time the request is submitted. 501(c)(3) organizations- Organizations with a 501(c)(3) status can purchase GIS data at a 50% reduced fee. These organizations will need to supply proper identification of their organization's status when submitting their data request. A signed Licensing Agreement must be submitted with the data request. John Schlee The Maryland National Capital Park and Planning Commission GIS Database Manager mailing and physical address
8787 Georgia Avenue
Silver Spring Maryland 20910-3760 USA (301) 495-4703 john.schlee@mncppc-mc.org ESRI ArcCatalog 9.3.1.4000 Feature Class Geography and attributes verified by M-NCPPC CONTROL PHOTOGRAPHS All control points to be used in aerial triangulation shall be pin-pricked and symbolized on the image side and symbolized, labeled, and diagrammed on the reverse side of one set of photo-controlled contact prints of the aerial negatives. DIGITIZING PRODUCTION REQUIREMENTS The following compilation requirements were adhered to by the Contractor. 1) Edgematching - All digitized map sheets must be both visual and coordinate-edgematched with adjacent sheets. No edgematch tolerance will be allowed. The coordinate edgematch must be 100% precise at double precision values. Attributes for adjoining features must also be identical. 2) Common Boundaries - All graphic features that share a common boundary must have the exact same digital representation of that boundary in all layers. 3) Point Duplication - No duplication of points that occur within a data string is permitted. 4) Connectivity - Where graphic elements visually meet, they must also digitally meet. All confluences of line, area, and polygon data must be exact mathematically; that is, no "overshoots", "undershoots", or "offsets" are permitted. Lines that connect polygons must intersect those polygons precisely; that is, every end point must be an intersection point of the respective polygon. 5) Line Quality - A high quality cartographic appearance shall be achieved. Transitions from straight line to curvilinear line segments shall be smooth, and without angular inflections at the point of intersection. The digital representation must not contain extraneous data at a non-visible level. There should be no jags or hooks or zero length segments. Curvilinear graphic features should be smooth with a minimum number of points. When appropriate, line smoothing programs should be used to minimize the angular inflection in curvilinear lines. Any lines that are straight, or should be straight, should be digitized using only two points that represent the beginning and ending points of the line. 6) Segmentation - The digital representation of linear elements must reflect the visual network structure of the data type. An element should not be broken or segmented unless that segmentation reflects a visual or attribute code characteristic, or unless the break is forced by database limitations. 7) Area and Polygon Closure and Centroids - For area features being digitized, the last coordinate pair must be exactly (mathematically) equal to the first coordinate pair. No line or polygon shall cross itself, or any other digitized feature, except to join at an actual confluence. All digitized features that are continuous across map boundaries shall be edited to effect smooth, continuous lines. 8) Point Criteria - All point features shall be digitized as a single x,y coordinate pair at the visual center of that graphic feature. 9) Features that cross map sheet or model boundaries shall not have duplicate data points at those boundaries except where those boundaries coincide with delivery areas. Post-processing procedures shall be utilized as necessary to minimize data redundancies. 10) No map sheet borders shall be provided as continuous polygons for deliveries of a single coverage. 11) Coverage shall be provided for tiles even if no data exists for a tile. 12) Each coverage must be free of node and arc intersect errors. Each polygon coverage must have one unique label per polygon and be free of label errors. ANNOTATION AND TITLING Annotation and titling shall be optimized initially for the production of hard copy maps at a standard scale of 1" = 200'. The location of labels and titling shall be coordinated with the referenced physical features being mapped. Titling of continuous features, such as streets, rivers, and other boundaries, shall be placed and repeated so as to occur at least once on each map sheet on which the feature referenced appears. Annotation shall be sized and oriented so as to be legible and readable when plotted at 1" = 200' scale and shall be right reading, or if a linear feature, along the feature. Wherever possible, overwriting of other map features shall be avoided. The orientation of characters in annotation shall follow the accepted rules of cartographic production to assure high quality, readability, aesthetic character, and permit crisp reproduction for either display or plotting. Generally, annotations for point and area features will be oriented horizontally and be right reading. Annotation for linear features should follow the contour of the line with appropriate spacing and offsets. Annotation for roads or power lines will run parallel to the centerline of those features. Some of the annotation to be included are: Font selection, sizing, and orientation of all labeling shall be such that plot sheets will contain all specified details in a clearly legible form, optimized for a scale of 1" = 200' and clearly legible at scales ranging from 1" = 100' to 1" = 400'. ACCEPTANCE CHECKS Arc/INFO data will be subjected to a series of inspections that may include the following: - Mounting, manipulation, and display of data on M-NCPPC's GIS system - Comparison of data and file content with orthophotos and previous planimetric and topographic mapping - Comparison of data and file content with database design specifications - Checks to verify data redundancies, label errors, topological gaps, and overruns - Field checks to ensure compliance with accuracy standards - Edgematching - Attribute and annotation correctness - Other checks against specifications as may be appropriate. Automated quality control AMLs will be used to check for errors and inconsistencies in digital data files. Error reports shall be developed which show at a minimum that the database adheres to the following standards: - Coverage names are valid (100 percent) - Precision and projection are correct (100 percent) - Polygon coverages were cleaned and built with specified tolerance (100 percent) - Feature codes are valid for a coverage (100 percent) - All features have a feature code (100 percent) Project Report Topographic Verification Montgomery County MD Aerial Photography Project FY93, FY94, FY95 Planimetric data shall be compiled in accordance with the ASPRS Accuracy Standards for large-scale Class 1 maps. This means that the limiting RMS error for all well-defined points shall be 1.0' on the ground. 2.5 Within 5 feet Project Report Topographic Verification Montgomery County MD Aerial Photography Project FY93, FY94, FY95 2.5 Within 5 feet Photogrammitricly delineated feature. 1991 Metadata imported. withheld 20040920 Dataset copied. withheld 20050407 Dataset copied. withheld 20050429 Dataset copied. withheld 20051215 Dataset copied. withheld 20060501 Dataset copied. withheld 20060602 Dataset copied. withheld 20060605 Dataset copied. withheld 20061205 Dataset copied. withheld 20070717 Dataset copied. withheld 20070719 Dataset copied. withheld 20090804 18195000 Dataset copied. withheld 20100304 17045800 coordinate pair 0.000093 0.000093 survey feet Lambert Conformal Conic 38.300000 39.450000 -77.000000 37.666667 1312333.333333 0.000000 North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 GCS_North_American_1983 NAD_1983_StatePlane_Maryland_FIPS_1900_Feet Explicit elevation coordinate included with horizontal coordinates 1.000000 SDE.HYDRO_LINE Arc Attribute Table for plan-hydro Info, ESRI Feature Class 50687 SHAPE OBJECTID OID 4 10 0 Feature geometry. ESRI Coordinates defining the features. OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. FTR_CODE String 7 0 0 FTR_CODE User-assigned feature ID Internal coordinate feature management computed by ArcInfo. Positive real numbers that are automatically generated and can be modified by the user. NAME String 35 0 0 NAME Feature Code WSSC, Data Catalog (GIS), Rev.1:July 1995 0500421 Lake/Pond M-NCPPC 0500412 River/Stream M-NCPPC 0500413 Single Line Stream M-NCPPC 0500415 Hidden Hydro M-NCPPC 0500101 Reservoir M-NCPPC SOURCE_DATE Date 36 0 0 SOURCE_DATE Annotationa labeling features. WSSC, Data Catalog (GIS), Rev. 1: July 1995 Lake M-NCPPC Pond M-NCPPC River M-NCPPC Stream M-NCPPC Single Line Stream M-NCPPC Hidden Hydro M-NCPPC Hidden Hydro M-NCPPC Hidden Hydro M-NCPPC Reservoir M-NCPPC UPDATE_DATE Date 36 0 0 UPDATE_DATE UPDATE_METHOD String 2 0 0 UPDATE_METHOD Shape Geometry 4 0 0 Feature geometry. ESRI Coordinates defining the features. Shape COMMENTS String 128 0 0 Feature geometry. ESRI Coordinates defining the features. COMMENTS UPDATE_STATUS String 1 0 0 UPDATE_STATUS SEQ_NUM SmallInteger 2 5 0 SEQ_NUM WSNAME String 25 0 0 WSNAME SUBWSNAME String 25 0 0 SUBWSNAME USE_DESIG String 5 0 0 USE_DESIG UPDATE_STAFF_ID String 10 0 0 UPDATE_STAFF_ID SHAPE.LEN Double 0 0 0 Length of feature in internal units. ESRI Positive real numbers that are automatically generated. plan_hydro.pat Polygon Attribute Table for plan-hydro. Info, ESRI FID Internal feature number. Internal coordinate feature management computed by ArcInfo. Sequential unique whole numbers that are automatically generated. Shape Feature geometry. Internal coordinate feature management computed by ArcInfo. Coordinates defining the features. AREA Holds the area of the polygon. Internal coordinate feature management computed by ArcInfo. Coordinates defining the features. PERIMETER Holds the perimeter of a polygon. Internal coordinate feature management computed by ArcInfo. Coordinates defining the features. PLAN_HYDRO# Internal sequence number of a polygon. Internal coordinate feature management computed by ArcInfo. Positive Real Numbers Coordinate Management Info, ESRI PLAN_HYDRO-ID User-assigned feature ID for each polygon. Internal coordinate feature management computed by ArcInfo. Positive real numbers that are automatically generated and can be modified by the user. FTR-CODE Feature Code. WSSC, Data Catalog (GIS), Rev.1: July 1995 0500421 Lake/Pond M-NCPPC 0500412 River/Stream M-NCPPC 0500413 Single Line Stream M-NCPPC 0500415 Hidden Hydro M-NCPPC 0500101 Reservoir M-NCPPC NAME Annotations labeling features. WSSC, Data Catalog (GIS), Rev. 1: July 1995 Hidden Hydro M-NCPPC Single Line Stream M-NCPPC River M-NCPPC Stream M-NCPPC Pond M-NCPPC Lake M-NCPPC Reservoir M-NCPPC plan_hydro.nat Node attribute table for plan-hydro. Info, ESRI FID Internal feature number. Internal coordinate feature management computed by ArcInfo. Sequential unique whole numbers that are automatically generated. Shape Feature geometry. Internal coordinate feature management computed by ArcInfo. Coordinates defining the features. ARC# Internal sequence number of one of the arcs that connects at the node location. Internal coordinate feature management computed by ArcInfo. Sequential unique whole numbers that are automatically generated. PLAN_HYDRO# Internal sequence number of the node. Internal coordinate feature management computed by ArcInfo. Positive Real Numbers Coordinate Management Info, ESRI PLAN_HYDRO-ID User-assigned feature ID for each node. Internal coordinate feature management computed by ArcInfo. Positive real numbers that are automatically generated and can be modified by the user. John Schlee The Maryland National Capital Park and Planning Commission GIS Database Manager mailing and physical address
8787 Georgia Avenue
Silver Spring Maryland 20910-3760 USA (301) 495-4703 john.schlee@mncppc-mc.org Hydro On maps: "NOTE: this map was compiled by digitizing tax maps prepared by the State of Maryland Department of Assessments and Taxation. Property lines are compiled from deed descriptions and subdivision plats, and should not be interpreted as actual field surveys. The record plat or survey should be reviewed if more property specific information is required. Use of this map, other than for general planning purposes, is not recommended. Please report any errors or omissions to the mapping/graphics section of the Montgomery County Planning Department, (301) 495-4700." GIS Data Products License Agreement Warranties Section: MC:Maps makes no warranty, express or implied, and disclaims all implied warranties of merchantability, integration, title, and fitness of the GIS data for a particular purpose. Liabilities Section: In no event will MC:MAPS be liable, whether in contract, tort (including negligence) or otherwise, for any direct, indirect, incidental or consequential damages including lost savings or profit, attorney's fees, lost data or business interruption even if MC:MAPS is notified in advance of such possibility. This includes damages incurred by customer or any third party. 20140210 John Schlee The Maryland National Capital Park and Planning Commission GIS Database Manager mailing and physical address
8787 Georgia Avenue
Silver Spring Maryland 20910-3760 USA (301) 495-4703 john.schlee@mncppc-mc.org FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile en http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile 20150302 16060800 FALSE 20140210 16541300 20140210 16542300 1.0 ESRI ArcCatalog 9.3.1.4000 SDE.HYDRO_LINE 1159770.678695 1345762.396773 617449.085606 461454.229071 1 -77.539563 -76.881771 39.362047 38.932517 1 ISO 19115 Geographic Information - Metadata DIS_ESRI1.0 dataset 002 withheld Feature Class Vector Simple Polyline FALSE 50687 TRUE FALSE 1 1 5.000000 FALSE 3 String 50687 NAD_1983_StatePlane_Maryland_FIPS_1900_Feet 50687 20140210