The North Carolina State and County Boundary vector polygon data provides location information for North Carolina State and County Boundary lines derived from the best available survey and/or Geographic Information System (GIS) data. Sources for information are the North Carolina Geodetic Survey (NCGS), NC Department of Transportation (NCDOT), United States Geological Survey (USGS), and field surveys conducted by licensed surveyors in North Carolina and neighboring states that have been approved and recorded in their respective counties. North Carolina Geodetic Survey assists counties on a cooperative basis (NC General Statute 153A-18) in defining and monumenting the location of uncertain or disputed boundaries as established by law. Some counties have completed boundary surveys for at least a portion of their county boundary. However, the majority of county boundaries have not been surveyed and are represented by the best currently available data from GIS sources, including NCDOT county maps (which originally came from the USGS) and updated county parcel maps.

The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

DL-FRONT is a Deep Learning Neural Network (DLNN) that was trained to detect weather fronts using spatial grids of near-surface atmospheric variables. The dataset is composed of hourly JSON files containing geospatial vector polylines describing the locations of four types of weather fronts—cold front, warm front, stationary front, and occluded front, over the time span 1980-2018.

This dataset is the product of processing data from the National Aeronautics and Space Administration (NASA) Modern-Era Retrospective analysis for Research and Applications, Version 2 (MERRA-2). DL-FRONT processed MERRA-2 hourly data grids of instantaneous measures of air pressure reduced to mean sea level, air temperature at 2 meters, specific humidity at 2 meters, and wind velocity at 10 meters over the time span 1980 - 2018 to produce this dataset. The original MERRA-2 data were resampled at 1 degree resolution over the spatial range 31W - 171W x 10N - 77N using bicubic interpolation.

At each hourly time step the network produced a set of spatial grids with the same resolution and spatial range as the input, one for each of the five categories mentioned above. Each cell in a spatial grid for a given category records the network-assigned probability (from 0.0 to 1.0) that the cell is in a weather front boundary region of that category (or, for the "no front" category, the probability that the cell is not in any weather front boundary region).

Each probability map was then processed to obtain polyline skeletons of the weather front boundary regions found by DL-FRONT. These vector representations of the fronts were then written to JSON files—one file for each hour. Each JSON file contains one top-level object composed of name/value pairs with the names issuanceDate, validDate, ColdFronts, WarmFronts, OccludedFronts, and StationaryFronts. The name/value pairs for createDate and validDate are always present. The other name/value pairs are only present if there is corresponding data. The values for issuanceDate and validDate are UTC timestamp strings.

The ColdFronts, WarmFronts, StationaryFronts, and OccludedFronts names in the top-level object, when present, have values that are arrays. In each case, the array is composed of one or more objects. Each object represents a front of the given type. Each object is composed of five name/value pairs with the names lats, lons, cols, rows, and confidence. The value for the name confidence is a number that is the average of the values of the probability map cells intersected by the front polyline. The values associated with the names lats, lons, cols, and rows are arrays. These arrays represent the vertices of a polyline describing the location of a frontal boundary in both geospatial and grid cell coordinates.

CoastSeg: estimate of zone of potential shoreline change, California and southeast USA Atlantic (FL, GA, SC, NC), in geoJSON format.

• Data have been made by Daniel Buscombe, Marda Science.
• Data cover the shorelines of five states
• A single geoJSON file per region. Data outline the extent of potential shoreline change.
• A 30-m vector defining the average shoreline, and a 30-m vector defining the limit of erodible material, were constructed and merged, then buffered, and manually edited.
• It is designed to be used in conjunction with the program CoastSeg https://github.com/Doodleverse/CoastSeg , for masking shoreline estimates outside of reasonable spatial bounds.

This layer is a component of BaseMap.

© City of Charlotte, Mecklenburg County