VCGI E911 address points import

From OpenStreetMap Wiki
Jump to navigation Jump to search

VCGI E911 address points import is an import of Emergency 911 addresses dataset which is maintained and made available by the Vermont Center for Geographic Information. The dataset covers the U.S. state of Vermont. The import is under way (as of March 2025).

The initial plan is to start small, and minimize risk by working on a town by town basis.

Goals

The goal is to import missing Vermont addresses.

Schedule

2021-07 assessment and manual entry of VCGI address data
2022-09 Public planning starts
2022-10 creation of street expansion script and generation of draft OSM data files
2025-03 Beginning the initial imports via JOSM for towns that use consistent postal communities for their addresses. Using account Adam Franco-Import

Import Data

Background

Data source site: https://geodata.vermont.gov/datasets/VCGI::vt-data-e911-site-locations-address-points-1/about
Data license: VCGI has stated the data has been made public with the intent for to be used in projects like OSM. An employee (J. McMullen) responded to an inquiry about data licensing on 2018-10-08, "The data that is post [sic] to the VCGI data warehouse is considered public data. There are no licensing restrictions on that data. Its posted to hopefully make every one else’s data better and at the same time making ours more accurate." Esri has evaluated the data set (listed here) and found it compatible with OSM, and includes the address points in the RapiD editor.

OSM Data Files

Import Type

Data imports will be done manually with JOSM.

Data Preparation

Data Reduction & Simplification

For the scope of this import project, we will work on towns that have less than 100 existing OSM addresses. Addresses that already exists in OSM will manually removed from the import data. As progress is made, the plan is develop a script that will help with the matching process, but ultimately every address will be manually, and individually be removed from the import data.

If a reliable script is made, an update to this project proposal will be made. The Vermont mapping and Import communities will be notified for project review and approval.

Tagging Plans

The following tags will be included for each node:

OSM tag VCGI source
addr:city TOWNNAME
addr:housenumber HOUSE_NUMBER
addr:street PD + SN + ST + SD PD = Prefix Direction, SN = Street Name, ST = Street Type, SD = Suffix Direction
addr:postcode ZIP
addr:state "VT" for all nodes
ref:vcgi:esiteid ESITEID Unique ID from VCGI to facilitate tracking and future updates
source "VCGI/E911_address_points"

Data Transformation

VCGI data is all uppercase and includes abbreviations in street names. A script has been written that Title Cases the elements makes the following transformations.

Street name suffixes (eg. Ave., St., Rd.) are expanded using this list.

Street names that include "U.S. Route" will be transformed from "US ROUTE #" to, "U.S. Route #".

Addresses on Vermont state routes will be transformed from "VT ROUTE #" to "Vermont Route #".

VCGI addresses that don't have a house number, or a house number of 0 are excluded.

Through testing of the script, several other custom "text cleanups" have been incorporated. As new exceptions are encountered, these transformations will continue to grow. See comments in the script for further details.

Data Merge Workflow

Team Approach

Preliminary work is being done by OSM user jared and Adam Franco with review from others on the #local-vermont Slack channel

Workflow

  • Town priorities will be made. Towns with a small number of address points, and few existing OSM address nodes will be worked on first. The plan is to never commit a changeset larger than a town. Most towns are relatively small, but if the process is successful, and larger towns are going to be imported, it is possible that they would be broken up into smaller import files.
  • For each town, an OSM file will be generated using E911 addresses from VCGI,
    • Address point data (primarily street name) will be transformed, and expanded to meet OSM standards.
    • This initial town OSM file will be conflated against existing OSM address data and sorted into several buckets:
      • no-match: to be reviewed and imported
      • tag-conflicts: to be reviewed and manually fixed if needed
      • review-distance: addresses that already exist in OSM, but significantly far from the E911 location
      • review-multiples: addresses that already exist in OSM multiple times. This is often the case if both a business and a building are tagged with the same address. These are not necessarily errors, but might be worth reviewing.
      • matches: to be skipped as the address already exists in OSM close to the E911 location.
  • A visual check in JOSM will be made to make sure the address nodes visually look reasonable (eg. confirm the points all fall within the town boundary and are on or very near to their associated buildings).
  • OSM files will be made available in advance to give others the opportunity to inspect
  • Once everything looks good, the changeset will be committed through JOSM. The preliminary import user will be "jared-import".
  • Progress updates will be provided here, and on the #local-vermont Slack channel so that others can keep an eye out for any issues

Conflation

As described in the workflow above, the initial town OSM file will be conflated against existing OSM address data and sorted into several buckets, each of which will be handled separately.

See also

The preliminary import plan was shared with the #local-vermont Slack channel on 2022-09-14. An update was posted at the beginning of import on 2025-03-05.

The imports-us mailing list was notified on September 17, 2022 (link).

Import process

Over 50,000 VCGI address points have already been added manually using RapiD. The data is considered highly accurate.

Initial imports will be kept small enough that data can be manually inspected to confirm that transformations were done properly. Points will be verified in JOSM to make sure alignment is accurate.

OSM files will be made available to other contributors for verification. Conflated files for review are available at https://github.com/JaredOSM/vermont-address-import/tree/main/data_files_to_import/conflated

As QA issues are found in initial small imports, this section will be expanded.

Comparing E911 addresses to existing OSM addresses in JOSM

Tutorial: Using the JOSM Conflation plugin to add 1500 addresses in 10 minutes

  1. Open JOSM and install the "conflation" plugin.
  2. Load the existing OSM addresses for a town in JOSM using an Overpass Query (see below)
  3. Add the following JOSM filters to ensure that the conflation plugin is only matching objects with addresses or building, not random nodes on nearby features
    1. (type:node AND ("addr:street"= OR untagged)) OR highway=*
    2. natural=* OR landuse=* OR boundary=* OR waterway=*
    3. type:relation
  4. Open the import project's .osm file for the town in JOSM as a new layer
  5. In the Conflation plugin's dialog, select the existing (filtered) objects as the subject and the import's as the reference and have it look for matches.
  6. Compare the conflicts and missing addresses, looking for issues like invalid name conversions or other problems.
    1. Go through the Conflation plugin's "Matches" first.
      1. The matches where the distance is greater than 10m are often either an outbuilding matching when the main building hasn't been mapped or horribly drawn/aligned buildings. You can add/fix these and then re-conflate or manually copy the address points into the data layer.
      2. In dense down-towns with multiple addresses per building, you may need to copy the source address node and paste it in its original position in the data layer.
    2. The Conflation plugin's "Reference Only" list may be spot checked, but can be bulk-conflated. This will result in stand-alone address points where buildings haven't been mapped yet and also on new lots where there is not yet construction. Some of these may also be address points in parks, solar fields, and other infrastructure points.
  7. Upload your data layer and include the tag <code>#vt-e911-address-import</code> in the comment.

Conflate existing address points with existing buildings

Previous imports and building mapping activity may have not conflated address points with buildings.

In general we want to keep stand alone address points when there are multiple per building. As well it is appropriate mapping to have stand alone nodes for businesses, shops, and amenities within the building outline, whether or not those businesses occupy the entire building or not.

To find un-conflated address points:

1. Load building ways and nodes with addresses into JOSM: 

[out:xml][timeout:90];
(
  area["ISO3166-2"="US-VT"]["admin_level"="4"]["boundary"="administrative"]->.state;
  area["name"="Middlebury"]["admin_level"="8"]["boundary"="administrative"]->.city;
  way["building"](area.city)(area.state)->.buildings;
  node["addr:street"](area.buildings)(area.city)(area.state);
);
(._;>;);
out meta;

2. Add a filter (inverted) in JOSM to select only the address nodes that aren't amenities or shops as we would expect extra nodes for those even in buildings that have addresses. 

type:node AND "addr:street" AND  -shop AND -amenity AND -office

3. Enable the above filter and select all, then add to the Todo list

4. Disable the filter to see context and work through the Todo list. Note that you may need to download data around a building to see extra context as we only downloaded a sparse data set.

For stand-alone address nodes where the building is the only thing it is likely to apply to, conflate it with the building by deleting it and copying its tags to the building way with Shift + R.

Leave stand-alone address nodes if there is a reasonable reason to do so. Examples:

  • Multiple addresses for the single building.
  • The address applying to a not-yet-mapped site like like a cluster of self-storage buildings (rather than to a particular building itself).
  • The address applying to a not-yet-mapped building nearby.

Loading existing OSM addresses for a town into JOSM

Use "Expert Mode" to download from an Overpass query, replacing "Middlebury" with the name of the town you are interested in. This will load all buildings and other features that have street or housenumber tags: 

[out:xml][timeout:90];
(
  area["ISO3166-2"="US-VT"]["admin_level"="4"]["boundary"="administrative"]->.state;
  area["name"="Middlebury"]["admin_level"="8"]["boundary"="administrative"]->.city;
  nwr["addr:street"](area.city)(area.state);
  nwr["addr:housenumber"](area.city)(area.state);
  nwr["building"](area.city)(area.state);
);
(._;>;);
out meta;

Accounts used for this import

Import Progress

For each town there are 4 files in data_files_to_import/conflated:

  • no-match - This is the primary file that will have the most missing addresses to import with hopefully the fewest conflicts.
  • tag-conflict - This file contains addresses that were matched, but have field conflicts with the E911 data. Often these indicate misspellings in either OSM or E911. Please use judgement and discuss if needed rather than blindly trusting E911.
  • review-distance - This file contains addresses that were matched, but are more than 100 meters from where they are located in E911. Review these.
  • matches - This file contains addresses that were determined to exist in OSM. This can be used for review if needed, but probably doesn't need to be imported since they already exist. Conflating would add the ref:vcgi:esiteid and any missing addr:state tags to the OSM object, but is not completely necessary.
  • review-multiple - This file contains addresses that were matched to multiple objects in OSM. This can be used for review if needed, but probably doesn't need to be imported since they already exist. Conflating would add the ref:vcgi:esiteid to the OSM object, but is not necessary.

There is also a final check step. For this, it may make sense to try conflating the draft file for the town from data_files_to_import/draft to identify any discrepancies.

information sign

Sign off your progress by adding {{Check yes}} --~~~~ after the item you complete

331,712 total address points in E911

Addison County ✓

19,584 address points in E911

  • ADDISON => Addison -- Uses consistent postal community.
  • BRIDPORT => Bridport -- Uses consistent postal community.
  • BRISTOL => Bristol -- Uses consistent postal community.
  • CORNWALL => Cornwall -- Uses consistent postal community. There may be a few data-entry errors in the southwest corner.
  • FERRISBURGH => -- Mixed postal communities.
  • GOSHEN => Goshen -- Uses consistent postal community.
  • GRANVILLE => Granville -- Uses consistent postal community.
  • HANCOCK => Hancock -- Uses consistent postal community.
  • LEICESTER => -- Mixed postal communities.
  • LINCOLN => Lincoln -- Uses consistent postal community.
  • MIDDLEBURY => Middlebury -- Uses consistent postal community.
  • MONKTON => -- Mixed postal communities.
  • NEW HAVEN => New Haven -- Uses consistent postal community.
  • ORWELL => -- Mixed postal communities.
  • PANTON => Panton -- Uses consistent postal community.
  • RIPTON => Ripton -- Uses consistent postal community.
  • SALISBURY => Salisbury -- Uses consistent postal community.
  • SHOREHAM => -- Mixed postal communities.
  • STARKSBORO => -- Mixed postal communities.
  • VERGENNES => Vergennes -- Uses consistent postal community.
  • WALTHAM => Waltham -- Uses consistent postal community.
  • WEYBRIDGE => Weybridge -- Uses consistent postal community.
  • WHITING => Whiting -- Uses consistent postal community.

Bennington County

21,804 address points in E911

  • ARLINGTON => Arlington -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BENNINGTON => -- Mixed postal communities. North Bennington is entered as a separate TOWNNAME in E911, but there may also be an OLD BENNINGTON postal community. Needs more research.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • DORSET => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • GLASTENBURY => Glastenbury -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • LANDGROVE => Landgrove -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • MANCHESTER => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • NORTH BENNINGTON => North Bennington -- North Bennington is a village in the Town of Bennington. E911 address points that use North Bennington as the TOWNNAME should use it as the postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • PERU => Peru -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • POWNAL => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • READSBORO => Readsboro -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • RUPERT => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SANDGATE => Sandgate -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SEARSBURG => Searsburg -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SHAFTSBURY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • STAMFORD => Stamford -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SUNDERLAND => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WINHALL => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WOODFORD => Woodford -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Caledonia County ✓

17,392 address points in E911.

  • BARNET => -- Mixed postal communities.
  • BURKE => -- Mixed postal communities.
  • DANVILLE => -- Mixed postal communities.
  • GROTON => Groton -- Uses consistent postal community.
  • HARDWICK => -- Mixed postal communities.
  • KIRBY => -- Mixed postal communities.
  • LYNDON => -- Mixed postal communities. Most should use Lyndonville, but some may use East Burke or Lyndon Center.
  • NEWARK => -- Mixed postal communities.
  • PEACHAM => -- Mixed postal communities.
  • RYEGATE => -- Mixed postal communities.
  • SHEFFIELD => Sheffield -- Uses consistent postal community.
  • SAINT JOHNSBURY => -- Mixed postal communities.
  • STANNARD => -- Mixed postal communities.
  • SUTTON => -- Mixed postal communities.
  • WALDEN => -- Mixed postal communities.
  • WATERFORD => Waterford -- Uses consistent postal community.
  • WHEELOCK => -- Mixed postal communities.

Chittenden County

61,626 address points in E911

  • BUELS GORE => Buel's Gore -- Uses consistent postal community. Note addition of possesive apostrophe.
  • BOLTON => -- Mixed postal communities.
    • no-match ✓ --Adamfranco (talk) 20:20, 18 March 2025 (UTC)
    • tag-conflict ✓ --Adamfranco (talk) 20:20, 18 March 2025 (UTC)
    • review-distance ✓ --Adamfranco (talk) 20:20, 18 March 2025 (UTC)
    • matches ✓ --Adamfranco (talk) 20:20, 18 March 2025 (UTC)
    • review-multiple ✓ --Adamfranco (talk) 20:20, 18 March 2025 (UTC)
    • Final check ✓ --Adamfranco (talk) 20:20, 18 March 2025 (UTC)
    • Check for single non-conflated address points ✓ --Adamfranco (talk) 19:15, 14 April 2025 (UTC)
    • Notes: The addresses on East Country Club Drive seem to be micro-mapped to individual units in OSM while E911 only has per-building address points which don't align to what has already been mapped in OSM. Additionally there are two points in E911 (57 East Country Club Drive and 68 East Country Club Drive) that overlap with buildings that have other addresses mapped in OSM. I've added these two address points as stand-alone next to the buildings so that they are searchable. This situation may require surveys or more research.
  • BURLINGTON => Burlington -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CHARLOTTE => Charlotte -- Uses consistent postal community.
  • COLCHESTER => Colchester -- Uses consistent postal community.
    • no-match ✓ --Ezekielf (talk) 03:26, 23 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 03:26, 23 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 03:26, 23 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 03:26, 23 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 03:26, 23 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 03:26, 23 March 2025 (UTC)
    • Check for single non-conflated address points
  • ESSEX JUNCTION CITY => Essex Junction -- Uses consistent postal community. Note removal of City from the name.
    • no-match ✓ --Ezekielf (talk) 20:16, 16 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 21:11, 15 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 20:01, 15 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 04:40, 16 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 20:01, 15 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 20:16, 16 March 2025 (UTC)
    • Check for single non-conflated address points
  • ESSEX TOWN => -- Mixed postal communities.
    • no-match ✓ --Ezekielf (talk) 21:05, 18 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 21:05, 18 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 21:05, 18 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 21:05, 18 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 21:05, 18 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 21:05, 18 March 2025 (UTC)
    • Check for single non-conflated address points
  • HINESBURG => Hinesburg -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • HUNTINGTON => Huntington -- Uses consistent postal community.
  • JERICHO => Jericho -- Uses consistent postal community.
    • no-match ✓ --Ezekielf (talk) 01:01, 20 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 01:01, 20 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 01:01, 20 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 01:01, 20 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 01:01, 20 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 01:01, 20 March 2025 (UTC)
    • Check for single non-conflated address points
  • MILTON => Milton -- Uses consistent postal community.
    • no-match ✓ --Ezekielf (talk) 03:00, 5 April 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 03:00, 5 April 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 03:00, 5 April 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 03:00, 5 April 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 03:00, 5 April 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 03:00, 5 April 2025 (UTC)
    • Check for single non-conflated address points
  • RICHMOND => Richmond -- Uses consistent postal community.
    • no-match ✓ --Ezekielf (talk) 04:19, 1 April 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 04:19, 1 April 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 04:19, 1 April 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 04:19, 1 April 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 04:19, 1 April 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 04:19, 1 April 2025 (UTC)
    • Check for single non-conflated address points
  • SAINT GEORGE => Saint George -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SHELBURNE => Shelburne -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SOUTH BURLINGTON => South Burlington -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • UNDERHILL => Underhill -- Uses consistent postal community.
    • no-match ✓ --Ezekielf (talk) 03:22, 31 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 03:22, 31 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 03:22, 31 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 03:22, 31 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 03:22, 31 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 03:22, 31 March 2025 (UTC)
    • Check for single non-conflated address points
  • WESTFORD => -- Mixed postal communities.
    • no-match ✓ --Ezekielf (talk) 02:47, 19 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 02:47, 19 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 02:47, 19 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 02:47, 19 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 02:47, 19 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 02:47, 19 March 2025 (UTC)
    • Check for single non-conflated address points ✓ --Adamfranco (talk) 19:15, 14 April 2025 (UTC)
  • WILLISTON => Williston -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WINOOSKI => Winooski -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Essex County ✓

5,896 address points in E911

  • AVERILL => Averill -- Uses consistent postal community.
  • AVERYS GORE => Avery's Gore -- Uses consistent postal community. Note addition of possesive apostrophe.
  • BLOOMFIELD => Bloomfield -- Uses consistent postal community.
  • BRIGHTON => -- Mixed postal communities.
  • BRUNSWICK => Brunswick -- Uses consistent postal community.
  • CANAAN => Canaan -- Uses consistent postal community. With one exception, the Beecher Falls Post office.
  • CONCORD => -- Mixed postal communities.
  • EAST HAVEN => East Haven -- Uses consistent postal community.
  • FERDINAND => Ferdinand -- Uses consistent postal community.
  • GRANBY => Granby -- Uses consistent postal community.
  • GUILDHALL => Guildhall -- Uses consistent postal community.
  • LEMINGTON => Lemington -- Uses consistent postal community.
  • LEWIS => Lewis -- Uses consistent postal community.
  • LUNENBURG => Lunenburg -- Uses consistent postal community.
  • MAIDSTONE => Maidstone -- Uses consistent postal community.
  • NORTON => Norton -- Uses consistent postal community.
  • VICTORY => Victory -- Uses consistent postal community.
  • WARNERS GRANT => Warner's Grant -- Uses consistent postal community. Note addition of possesive apostrophe.

Only 1 address!

  • WARRENS GORE => Warren's Gore -- Uses consistent postal community. Note addition of possesive apostrophe.

Franklin County

24,201address points in E911

  • BAKERSFIELD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BERKSHIRE => -- Mixed postal communities.
    • no-match ✓ --Ezekielf (talk) 20:26, 13 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 20:26, 13 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 20:26, 13 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 20:26, 13 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 20:26, 13 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 20:26, 13 March 2025 (UTC)
    • Check for single non-conflated address points
  • ENOSBURGH => -- Mixed postal communities. Most should use Enosburg Falls as the postal community, but here are some in the Northeast corner that may use Richford.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • FAIRFAX => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • FAIRFIELD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • FLETCHER => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • FRANKLIN => -- Mixed postal communities.
    • no-match ✓ --Ezekielf (talk) 03:00, 13 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 03:00, 13 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 03:00, 13 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 03:00, 13 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 03:00, 13 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 03:00, 13 March 2025 (UTC)
    • Check for single non-conflated address points
  • GEORGIA => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • HIGHGATE => -- Mixed postal communities.
    • no-match ✓ --Ezekielf (talk) 03:32, 12 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 03:32, 12 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 03:32, 12 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 03:32, 12 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 03:32, 12 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 03:32, 12 March 2025 (UTC)
    • Check for single non-conflated address points
  • MONTGOMERY => -- Mixed postal communities. Most should use Montgomery Center, but some in the northwest may use Richford.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • RICHFORD => Richford -- Uses consistent postal community.
    • no-match ✓ --Ezekielf (talk) 03:01, 15 March 2025 (UTC)
    • tag-conflict ✓ --Ezekielf (talk) 03:01, 15 March 2025 (UTC)
    • review-distance ✓ --Ezekielf (talk) 03:01, 15 March 2025 (UTC)
    • matches ✓ --Ezekielf (talk) 03:01, 15 March 2025 (UTC)
    • review-multiple ✓ --Ezekielf (talk) 03:01, 15 March 2025 (UTC)
    • Final check ✓ --Ezekielf (talk) 03:01, 15 March 2025 (UTC)
    • Check for single non-conflated address points
  • SAINT ALBANS CITY => Saint Albans -- Uses consistent postal community. Note removal of City from the name.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SAINT ALBANS TOWN => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SHELDON => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SWANTON => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Grand Isle County

6,968 address points in E911

  • ALBURGH => Alburgh -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • GRAND ISLE => Grand Isle -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • ISLE LA MOTTE => Isle La Motte -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • NORTH HERO => North Hero -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SOUTH HERO => South Hero -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Lamoille County

14,555 address points in E911.

  • BELVIDERE => Belvidere -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CAMBRIDGE => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • EDEN => -- Mixed postal communities.
  • ELMORE => -- Mixed postal communities.
  • HYDE PARK => Hyde Park -- Uses consistent postal community.
  • JOHNSON => Johnson -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • MORRISTOWN => Morrisville -- Uses consistent postal community. Note village in postal community.
  • STOWE => Stowe -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WATERVILLE => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WOLCOTT => Wolcott -- Uses consistent postal community.

Orange County

16,980 address points in E911

  • BRADFORD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BRAINTREE => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BROOKFIELD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CHELSEA => Chelsea -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CORINTH => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • FAIRLEE => Fairlee -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • NEWBURY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • ORANGE => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • RANDOLPH => Randolph -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • STRAFFORD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • THETFORD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • TOPSHAM => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • TUNBRIDGE => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • VERSHIRE => Vershire -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WASHINGTON => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WEST FAIRLEE => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WILLIAMSTOWN => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Orleans County

18,054 address points in E911

  • ALBANY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BARTON => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BROWNINGTON => -- Mixed postal community, the northwest corner may use Newport.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CHARLESTON => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • COVENTRY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CRAFTSBURY => -- Mixed postal communities.
  • DERBY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • GLOVER => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • GREENSBORO => -- Mixed postal communities.
  • HOLLAND => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • IRASBURG => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • JAY => Jay -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • LOWELL => -- Mixed postal communities.
  • MORGAN => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • NEWPORT CITY => Newport -- Uses consistent postal community. Note removal of City from the name.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • NEWPORT TOWN => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • ORLEANS => Orleans -- Orleans is a village in the Town of Barton. E911 address points that use Orleans as the TOWNNAME should use it as the postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • TROY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WESTFIELD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WESTMORE => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Rutland County

32,415 address points in E911

  • BENSON => Benson -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BRANDON => Brandon -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CASTLETON => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CHITTENDEN => Chittenden -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CLARENDON => Clarendon -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • DANBY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • FAIR HAVEN => Fair Haven -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • HUBBARDTON => Hubbardton -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • IRA => Ira -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • KILLINGTON => Killington -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • MENDON => Mendon -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • MIDDLETOWN SPRINGS => Middletown Springs -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • MOUNT HOLLY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • MOUNT TABOR => Mount Tabor -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • PAWLET => Pawlet -- E911 TOWNNAME is differentiated between PAWLET & WEST PAWLET consistently.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • PITTSFIELD => Pittsfield -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • PITTSFORD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • POULTNEY => Poultney -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • PROCTOR => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • RUTLAND CITY => Rutland -- Uses consistent postal community. Note removal of City from the name.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • RUTLAND TOWN => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SHREWSBURY => Shrewsbury -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SUDBURY => Sudbury -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • TINMOUTH => Tinmouth -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WALLINGFORD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WELLS => Wells -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WEST HAVEN => West Haven -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WEST PAWLET => West Pawlet -- E911 TOWNNAME is differentiated between PAWLET & WEST PAWLET consistently.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WEST RUTLAND => West Rutland -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Washington County ✓

28,752 address points in E911

  • BARRE CITY => Barre -- Uses consistent postal community. Note removal of City from the name.
  • BARRE TOWN => -- Mixed postal communities.
  • BERLIN => -- Mixed postal communities.
  • CABOT => -- Mixed postal communities.
  • CALAIS => -- Mixed postal communities.
  • DUXBURY => -- Mixed postal communities.
  • EAST MONTPELIER => -- Mixed postal communities.
  • FAYSTON => -- Mixed postal communities.
  • MARSHFIELD => -- Mixed postal communities.
  • MIDDLESEX => -- Mixed postal communities.
  • MONTPELIER => Montpelier -- Mostly consistent postal community. The exception is 4 addresses on Maplewood Road that are only accessible from East Montpelier and have "East Montpelier" as their postal community.
  • MORETOWN => -- Mixed postal communities.

Still need to figure out unit numbers for 2112 River Road trailer park points, but this isn't in E911 and will require survey.

  • NORTHFIELD => -- Mixed postal communities.
  • PLAINFIELD => -- Mixed postal communities.
  • ROXBURY => Roxbury -- Uses consistent postal community.
  • WAITSFIELD => Waitsfield -- Uses consistent postal community.
  • WARREN => Warren -- Uses consistent postal community.
  • WATERBURY => -- Mixed postal communities.
  • WOODBURY => -- Mixed postal communities.
  • WORCESTER => Worcester -- Uses consistent postal community.

Windham County

29,228 address points in E911

  • ATHENS => Athens -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BELLOWS FALLS => Bellows Falls -- Bellows Falls is a village in Rockingham and any E911 address points that use BELLOWS FALLS as the TOWNNAME should use it as the postal-community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BRATTLEBORO => Brattleboro -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BROOKLINE => Brookline -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • DOVER => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • DUMMERSTON => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • GRAFTON => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • GUILFORD => Guilford -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • HALIFAX => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • JAMAICA => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • LONDONDERRY => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • MARLBORO => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • NEWFANE => Newfane -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • PUTNEY => Putney -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • ROCKINGHAM => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SAXTONS RIVER => Saxtons River -- Saxtons River is a village in the Town of Rockingham and the E911 addresses with this as TOWNNAME should all use it for the postal-community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SOMERSET => Somerset -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • STRATTON => Stratton -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • TOWNSHEND => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • VERNON => Vernon -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WARDSBORO => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WESTMINSTER => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WHITINGHAM => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WILMINGTON => Wilmington -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WINDHAM => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Windsor County

34,257 address points in E911

  • ANDOVER => -- Mixed postal community. There are several parcels in the north that may use Ludlow as the postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BALTIMORE => Baltimore -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BARNARD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BETHEL => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • BRIDGEWATER => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CAVENDISH => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • CHESTER => Chester -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • HARTFORD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • HARTLAND => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • LUDLOW => Ludlow -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • NORWICH => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • PLYMOUTH => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • POMFRET => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • READING => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • ROCHESTER => Rochester -- Uses consistent postal community.
  • ROYALTON => -- Mixed postal communities. Most use South Royalton, but some may use Bethel.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SHARON => Sharon -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • SPRINGFIELD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • STOCKBRIDGE => Stockbridge -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WEATHERSFIELD => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WEST WINDSOR => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WESTON => Weston -- Uses consistent postal community.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WINDSOR => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check
  • WOODSTOCK => -- Mixed postal communities.
    • Check for single non-conflated address points
    • no-match
    • tag-conflict
    • review-distance
    • matches
    • review-multiple
    • Final check

Progress Map

Progress so far. Updated 2025-04-15.

Vt-address-import-progress-map.jpg

Overpass Turbo query to update map: https://overpass-turbo.eu/s/22mj

Retrieved from "https://wiki.openstreetmap.org/w/index.php?title=VCGI_E911_address_points_import&oldid=2837639"