| snippet:
|
In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line Shapefiles.
Level: Owner: Updated: Frequency: |
| summary:
|
In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line Shapefiles.
Level: Owner: Updated: Frequency: |
| accessInformation:
|
U.S. Census Bureau; Prince William County Department of Information Technology (DoIT), Geographic Information Systems (GIS) Division |
| thumbnail:
|
|
| maxScale:
|
5000 |
| typeKeywords:
|
[] |
| description:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data from Census 2000. The Census Bureau creates ZCTAs for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands for the 2010 Census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. For the 2010 Census, ZCTAs should more accurately represent the actual ZIP Codes at the time of their delineation than they did for Census 2000. This is because that before the tabulation blocks, which the ZCTAs are built from, were delineated for the 2010 Census, the Census Bureau undertook the process of inserting lines that could be used as 2010 Census tabulation block boundaries, and these lines split polygons where the result would be that a significant number of addresses would occur on either one or both sides of the line associated with a single ZIP Code. Each 2010 Census tabulation block that contains addresses is assigned to a single ZCTA, usually to the ZCTA that reflects the most frequently occurring ZIP Code for the addresses within that tabulation block. As a result, ZIP Codes associated with address ranges found in the Address Ranges relationship file may not always match the ZCTA. Blocks that do not contain addresses but are completely surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. A ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks were it exists. The Census Bureau uses the addresses stored within MTDB to delineate ZCTAs, and at the time of the 2010 Census the MTDB primarily included addresses for residential or at least potentially residential structures, so ZCTAs representing only non-residential structures are infrequent. Also, in each tabulation block, if a choice existed between using a potential city-style mail delivery ZIP Code for an address or a post office box ZIP Code, the city-style mail delivery ZIP Code was preferred for the 2010 Census ZCTA delineation. The Census Bureau identifies 5-digit ZCTAs using a five-character numeric code that represents the most frequently occurring USPS ZIP Code within that ZCTA, and this code may contain leading zeros.</SPAN></P><P><SPAN>The Census Bureau's geographic identifiers and demographic data included in this feature class </SPAN><SPAN><SPAN>were selected and retrieved from the U.S. Census American Factfinder </SPAN></SPAN><SPAN>by Prince William County Department of Information Technology (DoIT), Geographic Information Systems (GIS) Division: Brian Engelmann, Demographer (x 7098).</SPAN></P></DIV></DIV></DIV> |
| licenseInfo:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source. The boundary information in the TIGER/Line Shapefiles are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions.Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.</SPAN></P><UL><LI><P><SPAN STYLE="font-size:10pt">This data is for reference purposes only and should not be used for design work. </SPAN></P></LI><LI><P><SPAN STYLE="font-size:10pt">Prince William County hereby disclaims any and all liability or responsibility for any damage, injury, loss, claim, or lawsuit arising from any error, inaccuracy or other problem with either the digital maps contained with digital data delivery or digital data delivered. The User hereby releases the County, its officers, agents and all employees and volunteers, from all liability, damage, claims, injuries or suits arising from any such error, inaccuracy or problem. Furthermore, the User agrees to indemnify and hold harmless the County and its officers, agents and all employees and volunteers, from any and all claims, liability damages, injuries and suits arising from the use of the digital maps and data therein or thereon by the User, its employees or assignees, or by any third parties. </SPAN></P></LI><LI><P><SPAN STYLE="font-size:10pt">Prince William County reserves the right to deny access to certain datasets.</SPAN></P></LI><LI><P><SPAN STYLE="font-size:10pt">The digital maps and data provided hereunder are provided ''as is'' and the County expressly disclaims all warranties, UCC and otherwise, express or implied including warranties as to accuracy of the digital maps, data and merchantability and fitness for a particular purpose, and further expressly disclaims responsibility for all incidental, consequential or special damages arising out of or in connection with the use or performance of the digital maps and data.</SPAN></P></LI><LI><P><SPAN STYLE="font-size:10pt">User acknowledges this disclaimer of warranty and expressly waives all warranties express or implied and waives any right of claim for damages incidental, consequential or special, arising out of or in connection with the use or performance of the digital maps and data.</SPAN></P></LI></UL></DIV></DIV></DIV> |
| catalogPath:
|
|
| title:
|
GISPROD.DEMOGRAPHIC.ZipCodes_10 |
| type:
|
|
| url:
|
|
| tags:
|
["Zip Code","boundaries","51","State or Equivalent Entity","ZIP Code Tabulation Area","State or equivalent entity","U.S.","VA","ZCTA","United States","Virginia","Polygon","County or Equivalent Entity","boundaries","U.S.","United States","County or equivalent entity","Prince William","51153","Polygon"] |
| culture:
|
en-US |
| name:
|
|
| guid:
|
|
| minScale:
|
500000 |
| spatialReference:
|
|