Zip Codes (5-digit). The dataset polygons represent location and attributes of zip codes, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Zip Codes were identified from public records (US Postal Service) and created selecting arcs from the street centerlines and vector property map.

MassGIS had received quarterly updates of these data as part of its license for the HERE (Navteq) core map release (streets and related data); however, that license has expired. These ZIP Code boundaries are aligned to the street centerlines of the Q2 2018 HERE product (with a release date of April 1, 2018) and use a then-recent USPS source file.In March 2024, MassGIS modified the boundaries for all ZIP Code areas in Boston based on the U.S. Postal Service's ZIP Code Look Up by Address website. MassGIS also added polygons for ZIP Codes 02199 and 02203.Five-digit ZIP Codes were developed by the USPS and first introduced in 1963 for efficient mail delivery (the term ZIP stands for Zone Improvement Plan) but are difficult to map with complete certainty. In most cases, addresses in close proximity to each other are grouped in the same ZIP Code, which gives the appearance that ZIP Codes are defined by a clear geographic boundary. However, even when ZIP Codes appear to be geographically grouped, a clear ZIP Code boundary cannot always be drawn because ZIP Codes are only assigned to a point of delivery and not the spaces between delivery points. In areas without a regular postal route or no mail delivery, ZIP Codes may not be defined or have unclear boundaries.The USPS does not maintain an official ZIP Code map. The Census Bureau and many other commercial services will interpolate the data to create polygons to represent the approximate area covered by a ZIP code, but none of these maps are official or entirely accurate. Please see this good discussion of the issues of mapping ZIP Codes.See full metadata.Map service also available.

Please note: this data is live (updated nightly) to reflect the latest changes in the City's systems of record.Overview of the Data:This dataset is a polygon feature layer with the boundaries of all tax parcels owned by the City of Rochester. This includes all public parks, and municipal buildings, as well as vacant land and structures currently owned by the City. The data includes fields with features about each property including property type, date of sale, land value, dimensions, and more.About City Owned Properties:The City's real estate inventory is managed by the Division of Real Estate in the Department of Neighborhood and Business Development. Properties like municipal buildings and parks are expected to be in long term ownership of the City. Properties such as vacant land and vacant structures are ones the City is actively seeking to reposition for redevelopment to increase the City's tax base and economic activity. The City acquires many of these properties through the tax foreclosure auction process when no private entity bids the minimum bid. Some of these properties stay in the City's ownership for years, while others are quickly sold to development partners. For more information please visit the City's webpage for the Division of Real Estate: https://www.cityofrochester.gov/realestate/Data Dictionary: SBL: The twenty-digit unique identifier assigned to a tax parcel. PRINTKEY: A unique identifier for a tax parcel, typically in the format of “Tax map section – Block – Lot". Street Number: The street number where the tax parcel is located. Street Name: The street name where the tax parcel is located. NAME: The street number and street name for the tax parcel. City: The city where the tax parcel is located. Property Class Code: The standardized code to identify the type and/or use of the tax parcel. For a full list of codes, view the NYS Real Property System (RPS) property classification codes guide. Property Class: The name of the property class associated with the property class code. Property Type: The type of property associated with the property class code. There are nine different types of property according to RPS: 100: Agricultural 200: Residential 300: Vacant Land 400: Commercial 500: Recreation & Entertainment 600: Community Services 700: Industrial 800: Public Services 900: Wild, forested, conservation lands and public parks First Owner Name: The name of the property owner of the vacant tax parcel. If there are multiple owners, then the first one is displayed. Postal Address: The USPS postal address for the vacant landowner. Postal City: The USPS postal city, state, and zip code for the vacant landowner. Lot Frontage: The length (in feet) of how wide the lot is across the street. Lot Depth: The length (in feet) of how far the lot goes back from the street. Stated Area: The area of the vacant tax parcel. Current Land Value: The current value (in USD) of the tax parcel. Current Total Assessed Value: The current value (in USD) assigned by a tax assessor, which takes into consideration both the land value, buildings on the land, etc. Current Taxable Value: The amount (in USD) of the assessed value that can be taxed. Tentative Land Value: The current value (in USD) of the land on the tax parcel, subject to change based on appeals, reassessments, and public review. Tentative Total Assessed Value: The preliminary estimate (in USD) of the tax parcel’s assessed value, which includes tentative land value and tentative improvement value. Tentative Taxable Value: The preliminary estimate (in USD) of the tax parcel’s value used to calculate property taxes. Sale Date: The date (MM/DD/YYYY) of when the vacant tax parcel was sold. Sale Price: The price (in USD) of what the vacant tax parcel was sold for. Book: The record book that the property deed or sale is recorded in. Page: The page in the record book where the property deed or sale is recorded in. Deed Type: The type of deed associated with the vacant tax parcel sale. RESCOM: Notes whether the vacant tax parcel is zoned for residential or commercial use. R: Residential C: Commercial BISZONING: Notes the zoning district the vacant tax parcel is in. For more information on zoning, visit the City’s Zoning District map. OWNERSHIPCODE: Code to note type of ownership (if applicable). Number of Residential Units: Notes how many residential units are available on the tax parcel (if applicable). LOW_STREET_NUM: The street number of the vacant tax parcel. HIGH_STREET_NUM: The street number of the vacant tax parcel. GISEXTDATE: The date and time when the data was last updated. SALE_DATE_datefield: The recorded date of sale of the vacant tax parcel (if available). Source: This data comes from the department of Neighborhood and Business Development, Bureau of Real Estate.

About this mapMap created in January 2021 that shows all of the 5-digit postal ZIP codes that are contained within or otherwise intersect with the City of Rochester, NY's borders.Data Dictionaries:To view the data dictionaries for the layers in this map, click on the desired layer for more information.

The dataset contains the metadata provided on the NYC Honorary Street Names Map. The dataset will include City Council Introduction Number, the local law enactment number and date, category of change, borough, new name of the street or intersection, present name, limits, zip code, Introduced by Council Member(s), Biographical information of the individual, Notes, Longitude and Latitude coordinates.

Street_NoNum_and_ZipCode_Composite uses the NYS Streets and Zipcode boundaries to return a match within the street segment. Any address that does not successfully geocode to the first composite can then be run through the second composite locator (Street_NoNum_and_ZipCode_Composite). Recognizing that hits from this locator will not be spatially accurate. This composite locator is made up of the following locators.Locator NameSource DataDescription4A_SS_NoNum_ZipNameNYS Street SegmentsNYS Street Segments dataset using the postal zip code name for the City name in the locator. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.4B_SS_NoNum_CTNameNYS Street SegmentsNYS Street Segments dataset using the city or town name is used for the city name in the locator. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.4C_SS_NoNum_PlaceNameNYS Street SegmentsNYS Street Segments dataset using the alternate place name is used for the city name in the locator. This field is populated using the NYS Villages and Indian Reservations, the Census Designated Places and Alternate Acceptable Zip Code Names from the USPS. These areas do not exist everywhere so there will be a limited number of segments with this attribute. The location is placed on a street segment with the matching name. Please note this may or may not be the correct street segment.5_ZipCodePtsZip Code boundariesPoint placed at the centroid of the Zip Code boundaries. Currently, the geocoding service will return all of the results when using the Find Tool within ArcGIS. The user will then be responsible for choosing which of the results they want to keep. The SAM Address Points are the most accurate data available and should be picked anytime a result is returned from one of the SAM address point locators. If the geocoding service is used in the ESRI batch tool, the locator will return a Match from the first locator it comes to in the cascading order. If there are multiple locators with the same score or within the same locator the first result is returned and it is coded as a Tie.The locators will output a field named 'User_fld' which should be used in conjunction with the Loc_Name field. When the Loc_Name field contains one of the Address Point locators (1A, 1B or 1C) this field will contain either a 1,2,3,4 or a 5. When the Loc_Name field contains anything other than the Address Point locators, the 'User_fld' will either be NULL or "0". The numeric values correspond with the type of Address Point that was located:RooftopPrimary Structure EntranceDrivewayParcel CentroidMiscellaneous

This is the official Street Centerline dataset for the County of Sacramento and the incorporated cities within. The Street Range Index table is a distinct list of street names within the Centerline dataset along with the existing address range for each street by zip code.The Street Name Index table is a distinct list of street names within the Centerline dataset.

The Street_and_Address_Composite will return a geographic coordinate when a street address is entered. A user can enter an address either manually or by bulk input from a database or other source.The geocoder returns a coordinate pair and standardized address for each input address it is able to match. The NYS ITS Geospatial Services geocoder uses a series of combinations of reference data and configuration parameters to optimize both the likelihood of a match and the quality of the results. The reference data supporting the geocoder is stored in Federal Geographic Data Committee (FGDC) standard.The first composite locator (Street_and_Address_Composite) is made up of the following set of locators which are most likely to return a high quality hit. The locators are listed in the order in which they will be accessed along with a brief description of the locator's source data. These six locators will generate the majority of the results when geocoding addresses.Locator NameSource DataDescription1A_SAM_AP_ZipNameSAM Address PointsSAM address points using the postal zip code name for the city name in the locator.1B_SAM_AP_CTNameSAM Address PointsSAM address points. The city or town name is used for the city name in the locator.1C_SAM_AP_PlaceNameSAM Address PointsSAM address points. The city name is populated using the NYS Villages and Indian Reservations, the Census Designated Places and Alternate Acceptable Zip Code Names from the USPS. These names do not exist everywhere so there will be a limited number of points in this locator.3A_SS_ZipNameNYS Street SegmentsNYS Street Segments dataset using the postal zip code name for the city name in the locator. The location is interpolated from an address range on the street segment. The city name can be different for the left and right sides of the streets.3B_SS_CTNameNYS Street SegmentsNYS Street Segments using the city or town name for the city name in the locator. The location is interpolated from an address range on the street segment.3C_SS_PlaceNameNYS Street SegmentsNYS Street Segments using an alternate place name for the city field. This field is populated using the NYS Villages and Indian Reservations, the Census Designated Places and Alternate Acceptable Zip Code Names from the USPS. These areas do not exist everywhere so there will be a limited number of segments with this attribute. The location is interpolated from an address range on the street segment.For more information about the geocoding service, please visit: https://gis.ny.gov/address-geocoder.For documentation on how to add these locators to ArcGIS, please reference Adding the Statewide Geocoding Web Service. If you would like these locators to be your default locators in ArcGIS, copy DefaultLocators.xml to C:\Users<username>\AppData\Roaming\ESRI\Desktop10.X\Locators, where

This is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. In 1993 - the Maryland Department of Planning and the Maryland State Highway Administration entered into a Data Base Usage Agreement with Bell Atlantic and Data Chromatics - Inc. to develop an enhanced street address map for Maryland. ZIP Code boundary area files were one of the products derived from this partnership. The resulting boundary area files were intended to improve the cartographic quality and accuracy of the ZIP code boundary area files derived from the U.S. Census Bureau's post 1990 Census TIGER\Line Files (based on the Census Bureau's ZIP code tabulation areas - ZCTAs). Subsequent iterative improvements to the ZIP Code boundary area files have been made using premise address information associated with mapped parcel records as provided in the Maryland Department of Planning's MdProperty View GIS tax map and parcel record DVD product. The resulting files are meant to serve as a good approximation"" of ZIP codes as polygons (which in reality they are not) but are not official ZIP Code maps and are not meant to be a substitute for any products offered by the U.S. Postal Service - the official source for ZIP code information. While there are no restrictions on their use we do recommend that they are best used with MdProperty View and that MDP makes no guarantee or warranty regarding the files. Last Updated: 2012Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively the ""Data"") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

This dataset is the Maryland ZIP codes based on the most current MD PropertyView data. In 1993, the Maryland Department of Planning and the Maryland State Highway Administration entered into a Data Base Usage Agreement with Bell Atlantic and Data Chromatics, Inc. to develop an enhanced street address map for Maryland. Zip Code boundary area files were one of the products derived from this partnership. The resulting boundary area files were intended to improve the cartographic quality and accuracy of the zip code boundary area files derived from the U.S. Census Bureau's post 1990 Census TIGER\Line Files (based on the Census Bureau's zip code tabulation areas, ZCTAs). Subsequent iterative improvements to the Zip Code boundary area files have been made using premise address information associated with mapped parcel records as provided in the Maryland Department of Planning's MdProperty View GIS product. The resulting files are meant to serve as a "good approximation" of zip codes as polygons (which in reality they are not) but are not official Zip Code maps and are not meant to be a substitute for any products offered by the U.S. Postal Service, the official source for zip code information. While there are no restrictions on their use we do recommend that they are best used with MdProperty View and that MDP makes no guarantee or warranty regarding the files. For information on the date of the data to each jurisdiction's corresponding MdProperty View edition, see the production schedule located here: https://res1planningd-o-tmarylandd-o-tgov.vcapture.xyz/Documents/OurProducts/PropertyMapProducts/Sched.pdf.

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

Our extensive database contains approximately 800,000 active rental property listings from across the United States. Updated daily, this comprehensive collection provides real estate professionals, investors, and property managers with valuable market intelligence and business opportunities. Database Contents

Property Addresses: Complete location data including street address, city, state, ZIP code Listing Dates: Original listing date and most recent update date Availability Status: Currently available, pending, or recently rented properties Geographic Coverage: Properties spanning all 50 states and major metropolitan areas

Applications & Uses

Market Analysis: Track rental pricing trends across different regions and property types Investment Research: Identify high-opportunity markets with favorable rental conditions Lead Generation: Connect with property owners potentially needing management services Competitive Intelligence: Monitor listing volumes, vacancy rates, and market saturation Business Development: Target specific neighborhoods or property categories for expansion

File Format & Delivery

Organized in easy-to-use CSV format for seamless integration with data analysis tools Accessible through secure download portal or API connection Daily updates ensure you're working with the most current market information Custom filtering options available to narrow results by location, date range, or other criteria

Data Quality

Rigorous validation processes to ensure address accuracy Duplicate listing detection and removal Regular verification of active status Standardized format for consistent analysis

Subscription Benefits

Access to historical listing archives for trend analysis Advanced search capabilities to target specific property characteristics Regular market reports summarizing key trends and opportunities Custom data exports tailored to your specific business needs

AK ~ 1,342 listings AL ~ 6,636 listings AR ~ 4,024 listings AZ ~ 25,782 listings CA ~ 102,833 listings CO ~ 14,333 listings CT ~ 10,515 listings DC ~ 1,988 listings DE ~ 1,528 listings FL ~ 152,258 listings GA ~ 28,248 listings HI ~ 3,447 listings IA ~ 4,557 listings ID ~ 3,426 listings IL ~ 42,642 listings IN ~ 8,634 listings KS ~ 3,263 listings KY ~ 5,166 listings LA ~ 11,522 listings MA ~ 53,624 listings MD ~ 12,124 listings ME ~ 1,754 listings MI ~ 12,040 listings MN ~ 7,242 listings MO ~ 10,766 listings MS ~ 2,633 listings MT ~ 1,953 listings NC ~ 22,708 listings ND ~ 1,268 listings NE ~ 1,847 listings NH ~ 2,672 listings NJ ~ 31,286 listings NM ~ 2,084 listings NV ~ 13,111 listings NY ~ 94,790 listings OH ~ 15,843 listings OK ~ 5,676 listings OR ~ 8,086 listings PA ~ 37,701 listings RI ~ 4,345 listings SC ~ 8,018 listings SD ~ 1,018 listings TN ~ 15,983 listings TX ~ 132,620 listings UT ~ 3,798 listings VA ~ 14,087 listings VT ~ 946 listings WA ~ 15,039 listings WI ~ 7,393 listings WV ~ 1,681 listings WY ~ 730 listings

Grand Total ~ 977,010 listings

The GBF/dime files, (geographic base file/dual independent map encoding), are computerized versions of the Metropolitan Map Series plus street segment address ranges, zip codes, and x-y coordinate values at intersections. Each record in the file identifies a segment of a feature on a map by its node points, address, and the geographic unit identified on both sides. Records for nonstreet map features such as railroads, streams, and political boundaries are included. A set of nodes noted and nu mbered metropolitan maps corresponding to area for all areas are included. Records are provided for all streets of the urbanized area of each SMSA. Census blocks, census tracts, city ZIP, county and state codes are shown for each street segment. The data pertains to the status of the SMSA's as of 1970.

Our Europe Zip Code Database offers comprehensive postal code data for spatial analysis, including postal and administrative areas for numerous European countries. This dataset contains accurate and up-to-date information on all administrative divisions, cities, and zip codes, making it an invaluable resource for various applications such as address capture and validation, map and visualization, reporting and business intelligence (BI), master data management, logistics and supply chain management, and sales and marketing. Our location data packages are available in various formats, including CSV, optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more. Product features include fully and accurately geocoded data, multi-language support with address names in local and foreign languages, comprehensive city definitions, and the option to combine map data with UNLOCODE and IATA codes, time zones, and daylight saving times. Companies choose our location databases for their enterprise-grade service, reduction in integration time and cost by 30%, and weekly updates to ensure the highest quality.

This dataset is the Maryland ZIP codes based on the most current MD PropertyView data. In 1993, the Maryland Department of Planning and the Maryland State Highway Administration entered into a Data Base Usage Agreement with Bell Atlantic and Data Chromatics, Inc. to develop an enhanced street address map for Maryland. Zip Code boundary area files were one of the products derived from this partnership. The resulting boundary area files were intended to improve the cartographic quality and accuracy of the zip code boundary area files derived from the U.S. Census Bureau's post 1990 Census TIGER\Line Files (based on the Census Bureau's zip code tabulation areas, ZCTAs). Subsequent iterative improvements to the Zip Code boundary area files have been made using premise address information associated with mapped parcel records as provided in the Maryland Department of Planning's MdProperty View GIS product. The resulting files are meant to serve as a "good approximation" of zip codes as polygons (which in reality they are not) but are not official Zip Code maps and are not meant to be a substitute for any products offered by the U.S. Postal Service, the official source for zip code information. While there are no restrictions on their use we do recommend that they are best used with MdProperty View and that MDP makes no guarantee or warranty regarding the files. For information on the date of the data to each jurisdiction's corresponding MdProperty View edition, see the production schedule located here: https://planning.maryland.gov/Documents/OurProducts/PropertyMapProducts/Sched.pdf.

A comprehensive self-hosted geospatial database of street names, coordinates, and address data ranges for Enterprise use. The address data are georeferenced with industry-standard WGS84 coordinates (geocoding).

All geospatial data are provided in the official local languages. Names and other data in non-Roman languages are also made available in English through translations and transliterations.

Use cases for the Global Address Database (Geospatial data)

• Address capture and validation

• Parcel delivery

• Master Data Management

• Logistics and Shipping

• Sales and Marketing

Additional features

• Fully and accurately geocoded

• Multi-language support

• Address ranges for streets covered by several zip codes

• Comprehensive city definitions across countries

• Administrative areas with a level range of 0-4

• International Address Formats

For additional insights, you can combine the map data with:

• UNLOCODE and IATA codes (geocoded)

• Time zones and Daylight Saving Time (DST)

• Population data: Past and future trends

Data export methodology

Our location data packages are offered in CSV format. All geospatial data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our location databases

• Enterprise-grade service

• Reduce integration time and cost by 30%

• Frequent, consistent updates for the highest quality

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

description: This data set approximates polygon boundaries for zip codes within Minnesota. The polygon boundaries are approximate since the U.S. Postal Service assigns zip codes to linear features (streets), not to geographic areas. Since neither the U.S. Postal Service nor the U.S. Census Bureau maintains official zip code boundary files or maps, LMIC created this file in order to be able to map data aggregated by zip code. LMIC worked with regional post office sites to delineate areas within which letter carriers delivered mail with the same zip code.; abstract: This data set approximates polygon boundaries for zip codes within Minnesota. The polygon boundaries are approximate since the U.S. Postal Service assigns zip codes to linear features (streets), not to geographic areas. Since neither the U.S. Postal Service nor the U.S. Census Bureau maintains official zip code boundary files or maps, LMIC created this file in order to be able to map data aggregated by zip code. LMIC worked with regional post office sites to delineate areas within which letter carriers delivered mail with the same zip code.

This dataset is part of the Geographical repository maintained by Opendatasoft.This dataset contains data for zip codes 5 digits in United States of America.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 for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial 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.Processors and tools are using this data.EnhancementsAdd ISO 3166-3 codes.Simplify geometries to provide better performance across the services.Add administrative hierarchy.

This collection of computer programs and test data files was compiled by the Census Bureau for use with GEOGRAPHIC BASE FILE/DUAL INDEPENDENT MAP ENCODING (GBF/DIME), 1980 (ICPSR 8378). This collection consists of files grouped into five categories: Special Program Information Tape (SPIT) Datasets, UNIMATCH System Datasets, ADMATCH System Datasets, EASYMAP System Datasets, and EASYCORD System Datasets. Some of the capabilities of the programs in this collection include: mapping files for which complicated data manipulation is required, generating individualized lists of candidates for carpools, linking of records on the basis of street address, creating shaded area maps for statistical display, and producing a map coordinate system.

TIGER road data for the MSA. When compared to high-resolution imagery and other transportation datasets positional inaccuracies were observed. As a result caution should be taken when using this dataset. TIGER, TIGER/Line, and Census TIGER are registered trademarks of the U.S. Census Bureau. ZCTA is a trademark of the U.S. Census Bureau. The Census 2000 TIGER/Line files are an extract of selected geographic and cartographic information from the Census TIGER data base. The geographic coverage for a single TIGER/Line file is a county or statistical equivalent entity, with the coverage area based on January 1, 2000 legal boundaries. A complete set of census 2000 TIGER/Line files includes all counties and statistically equivalent entities in the United States, Puerto Rico, and the Island Areas. The Census TIGER data base represents a seamless national file with no overlaps or gaps between parts. However, each county-based TIGER/Line file is designed to stand alone as an independent data set or the files can be combined to cover the whole Nation. The Census 2000 TIGER/Line files consist of line segments representing physical features and governmental and statistical boundaries. The boundary information in the TIGER/Line files 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. The Census 2000 TIGER/Line files do NOT contain the Census 2000 urban areas which have not yet been delineated. The files contain information distributed over a series of record types for the spatial objects of a county. There are 17 record types, including the basic data record, the shape coordinate points, and geographic codes that can be used with appropriate software to prepare maps. Other geographic information contained in the files includes attributes such as feature identifiers/census feature class codes (CFCC) used to differentiate feature types, address ranges and ZIP Codes, codes for legal and statistical entities, latitude/longitude coordinates of linear and point features, landmark point features, area landmarks, key geographic features, and area boundaries. The Census 2000 TIGER/Line data dictionary contains a complete list of all the fields in the 17 record types. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.