United States Thoroughfare, Landmark, and Postal Address Data Standard (Final Draft)
AddressLifecycleStatusDateConsistencyMeasure
Download 4.55 Mb.
|
- Navigate this page:
- 4.5.4 AddressNumberFishbonesMeasure
4.5.3 AddressLifecycleStatusDateConsistencyMeasureMeasure Name AddressLifecycleStatusDateConsistencyMeasure Measure Description This measure tests the agreement of the Address Lifecycle Status with the development process. This query is far more conceptual than many others in this section of the standard for the simple reason that the development processes, and the data it generates, vary considerably from place to place. It is common to track the starting and ending dates of each Address Lifecycle Status value. Address Start Date and Address End Date are notably different, not directly attached to any given Address Lifecycle Status value. Checking the validity of any given Address Lifecycle Status requires checking both the Address Start Date and Address End Date values, and data from the development process. The query for testing records assumes a process where the issuance of a building permit describes the transition of an address from potential or proposed to active. Any given development process is likely to have a longer, more complicated list of conditions. Reports using this measure should include the final query used. Report Temporal Accuracy and/or Logical Consistency Evaluation Procedure Check entries where the Address Lifecycle Status conflicts with the Address Start Date or Address End Date, or with the development process. Refine the query as needed to track the development process as it affects Address Lifecycle Status and make sure the records are contemporaneous. Spatial Data Required None
Code Example: Testing Records SELECT
AddressID FROM
AddressPtCollection WHERE
( AddressLifecycleStatus = 'Potential' AND OR AddressStartDate IS NULL OR AddressEndDate IS NOT NULL ) ) OR ( AddressLifcycleStatus = 'Proposed' AND ( BuildingPermit IS NOT NULL OR AddressStartDate IS NULL OR AddressEndDate IS NOT NULL ) OR ( AddressLifecycleStatus = 'Active' OR AddressStartDate IS NULL OR AddressEndDate IS NOT NULL ) OR
AddressLifecycleStatus = 'Retired' AND
AddressEndDate IS NULL )
Function See Perc Conforming for the sample query. Function Parameters count_of_non_conforming_records SELECT count( * ) FROM AddressPtCollection WHERE (
AND ( BuildingPermit IS NOT NULL OR AddressStartDate IS NULL OR AddressEndDate IS NOT NULL ) )
( AddressLifcycleStatus = 'Proposed' AND ( BuildingPermit IS NOT NULL OR AddressStartDate IS NULL OR AddressEndDate IS NOT NULL ) OR ( AddressLifecycleStatus = 'Active' OR AddressStartDate IS NULL OR AddressEndDate IS NOT NULL ) OR
AddressLifecycleStatus = 'Retired' AND
AddressEndDate IS NULL ) count_of_total_records SELECT COUNT( * ) FROM AddressPtCollection Result Report Example Tested AddressLifecycleStatusDateConsistencyMeasure at 65% conformance. 4.5.4 AddressNumberFishbonesMeasureMeasure Name AddressNumberFishbonesMeasure Measure Description This measure generates lines between addressed locations and the corresponding locations along the matching Overlapping Ranges Measure to check the spatial sequence of Address Number locations. The pattern created by these lines frequently resembles a fishbone. This query is most often used where the Two Number Address Range or Four Number Address Range values are present and trusted. If those values are not present or are suspect the geocoded points may be produced without reference to the ranges. For example, points may be generated along the closest street centerline with a matching Complete Street Name value, directly opposite the addresses. This process, with the results diligently checked, allows the ranges themselves to be checked against an inventory of the address numbers actually located along the segment. In addition to checking Address Number sequence anomalies, this query can be used to fill the Related Transportation Feature ID field in the AddressPtCollection. Report Logical Consistency Evaluation Procedure Fishbones will reflect the Address Reference System applied in a given area, and the points used. Examples of addresses to check include those where: There is no fishbone This may show an address with a Complete Street Name value that doesn't match anything in the StCenterlineCollection The fishbone touches one or more other fishbones, either crossing them or intersecting in some other way Address Number values may have been assigned out of order. Another possibility, especially in more sparsely settled areas, is that the address assignment as determined by the location of the property access, and the fishbones are being drawn from buildings on the property. It's important to generate fishbones that reflect assignment practice. The fishbone crosses street centerlines There may be inconsistencies in the Complete Street Name values recorded in the AddressPtCollection and the StCenterlineCollection. The fishbone extends further than expected. In many areas fishbone lines >= 1000 feet (304.8 meters) require investigation These may indicate variations in street names that need to be resolved, especially when a fishbone crosses a jurisdiction. Alternatively, there may be segments missing or unnamed theStCenterlineCollection. Bunch at the end of a street segment, forming a bowtie These frequently indicate address ranges that inappropriately begin with zero (0).
Creating a table to hold the fishbones CREATE TABLE Fishbones ( id SERIAL PRIMARY KEY, AddressID INTEGER NOT NULL REFERENCES AddressPtCollection, RelatedTransportationFeatureID TEXT REFERENCES StCenterlineCollection, Geometry geometry )
INSERT INTO Fishbones ( AddressID, RelatedTransportationFeatureID, Geometry ) SELECT a.AddressID, b.RelatedTransportationFeatureID, ST_Makeline( a.Geometry, b.Geometry) FROM
AddressPtCollection a INNER JOIN GeocodedPtZeroOffset b ON a.AddressID = b.AddressID
See Perc Conforming for the sample query. Function Parameters count_of_non_conforming_records Many anomalous fishbones are most easily located visually. Those should be added to your FishboneAnomalies table. Create a table to hold the potential anomalies CREATE TABLE FishboneAnomalies ( id SERIAL PRIMARY KEY, AddressID TEXT, AddressNumber INTEGER, CompleteStreetName TEXT, Anomaly Text )
INSERT INTO FishboneAnomalies ( AddressID, AddressNumber, CompleteStreetName, Anomaly )
a.AddressID, a.AddressNumber, a.CompleteStreetName, 'No fishbone'::TEXT as "Anomaly" FROM AddressPtCollection a LEFT JOIN Fishbones b ON a.AddressID = b.AddressID WHERE b.AddressID is null Collect addresses with fishbones that touch other fishbones Run this query for each fishbone. INSERT INTO FishboneAnomalies ( AddressID, AddressNumber, CompleteStreetName, Anomaly )
a.AddressID, a.AddressNumber, a.CompleteStreetName, 'Fishbone touches'::TEXT as "Anomaly" FROM Fishbones a INNER JOIN fishbones b ON TOUCHES( a.Geometry, b.AddressID ) WHERE a.AddressID = [ __fill in AddressID value__ ] Collect addresses with fishbones that cross centerlines INSERT INTO FishboneAnomalies ( AddressID, AddressNumber, CompleteStreetName, Anomaly )
a.AddressID, a.AddressNumber, a.CompleteStreetName, 'Fishbone touches'::TEXT as "Anomaly" FROM Fishbones a INNER JOIN StCenterlineCollection b ON CROSSES( a.Geometry, b.StCenterlineGeometry ) Collect addresses with long fishbones INSERT INTO FishboneAnomalies ( AddressID, AddressNumber, CompleteStreetName, Anomaly )
AddressID, AddressNumber, CompleteStreetName, 'Long fishbone'::TEXT as "Anomaly" FROM Fishbones WHERE ST_Length( Geometry ) >= 1000 Collect addresses with suspected bowtie fishbones INSERT INTO FishboneAnomalies ( AddressID, AddressNumber, CompleteStreetName, Anomaly )
a.AddressID, a.AddressNumber, a.CompleteStreetName, 'Bowtie fishbone'::TEXT as "Anomaly" FROM Fishbones a INNER JOIN ( SELECT
st_startpoint( Geometry ) as Geometry from
Fishbones group by
st_startpoint( Geometry ) having
count( st_startpoint( Geometry ) ) > 1 ) as b
on st_startpoint( a.Geometry ) = b.Geometry ;
After examining your results in the FishboneAnomalies and discarding those that were identified in error, count the number of non-conforming records. SELECT
COUNT(*) FROM
FishboneAnomalies count_of_total_records SELECT
COUNT(*) FROM
AddressPtCollection Result Report Example Tested AddressNumberFishbonesMeasure at 80% conformance. Directory: standards standards -> Request for proposal contract form for the transit industry standards -> Indiana Academic Standards Resource Guide Grade 8 United States History – Growth and Development (to 1877) Updated April 2016 standards -> Us history Dictionary Based on the sc state Standards standards -> Integrating Standards Education into the Business School Curriculum standards -> Use of Sprint U301 3G/4g mobile Broadband usb device Installation standards -> International organisation for standardisation organisation internationale de normalisation standards -> Standards of Excellence standards -> Common Core State Standards for Mathematics (ccssm) Download 4.55 Mb. Share with your friends:
|