DOCSLIB.ORG

2. Part 2: Address Data Content

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
2. Part 2: Address Data Content Federal Geographic Data Committee FGDC Document Number FGDC-STD-016-2011 United States Thoroughfare, Landmark, and Postal Address Data Standard 2. Part 2: Address Data Content 2.1 Introduction 2.1.1 Purpose The content part defines address elements, their attributes, and address reference system elements. 2.1.2 Organization The address elements are presented first, grouped according to the major components of an address, followed by the attributes, which are grouped by subject, and lastly the address reference system elements. The Table Of Elements And Attributes immediately following this introduction lists elements and attributes in the order they are presented. 2.1.3 Simple Elements, Complex Elements, and Attributes The content part defines simple elements, complex elements, and attributes. 1. Simple elements are address components or address reference system components that are defined independently of all other elements 2. Complex elements are formed from two or more simple or other complex elements 3. Attributes provide descriptive information, including geospatial information, about an address, an address reference system, or a specific element thereof. Appendix C: Table of Element Relationships lists the relations between simple and complex elements. 2.1.4 Element and Attribute Definitions and Descriptions Each data element is defined and described by giving its: 1. Element name: The name of the element. 2. Other common names for this element: Common words or phrases having the same or similar meaning as the element name. Note: * "(USPS)" indicates terms used in USPS Publication 28. * "(Census TIGER)" indicates terms found in U.S. Census Bureau TIGER\Line Shapefile documentation. * Part 6 gives complete citations for both documents. 3. Definition: The meaning of the element. 16 Federal Geographic Data Committee FGDC Document Number FGDC-STD-016-2011 United States Thoroughfare, Landmark, and Postal Address Data Standard 4. Syntax: (For complex elements only) What component elements are required or permitted to construct the element, and the order in which they must appear. (For syntax notation, see below, "Notation for Constructing Complex Elements.") 5. Definition Source: The source of the definition ("New" indicates that the definition is original.) 6. Data Type: Whether the element is a characterString, date, dateTime, integer, real, or geometric (point, MultiCurve, or MultiSurface) (see "Element and Attribute Data Types" below for definitions) 7. Existing Standards for this Element: Other standards that govern this element (if any). 8. Domain of Values for this Element: The range or set of values (if any) to which the element is restricted. 9. Source of Values: The source (if any) for the domain of values. 10. How Defined: How the domain of values is defined. 11. Example: Illustrative examples of the element. 12. Notes/Comments: Notes and comments giving further explanation about the element. 13. XML Tag: The XML tag for the element. 14. XML Model: XML model of the element. 15. XML Example: The XML model applied to a specific example of the element. 16. XML Notes: Explanatory notes about the XML model. 17. Quality Measures: Quality tests applied to the class. 18. Quality Notes: Explanatory notes about the quality measures applied to this element. 2.1.5 Element and Attribute Data Types Elements and attributes are either non--geometric, geometric, or abstract. Non-geometric data types include characterString, date, dateTime, integer, and real. Geometric data types include point, MultiCurve, and MultiSurface. The abstract data type, as used in this standard, aggregates multiple elements of different data types, geometric and non-geometric. The non-geometric data types are defined in the FGDC's "Framework Data Content Standard Part 0: Base Document" (section 7.8.2.2 (Table 4 - CodeList for DataType)) as follows: 1. characterString: "A CharacterString is an arbitrary-length sequence of characters including accents and special characters from repertoire of one of the adopted character sets" 17 Federal Geographic Data Committee FGDC Document Number FGDC-STD-016-2011 United States Thoroughfare, Landmark, and Postal Address Data Standard 2. date: "Values for year, month, and day" 3. dateTime: "A combination of year, month, and day and hour, minute, and second" 4. integer: "Any member of the set of positive whole numbers, negative whole numbers and zero" 5. real: "Real numbers are all numbers that can be written as a possibly never repeating decimal fraction" The geometric data types are defined in the Open Geospatial Consortium's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" Version: 3.2.1. (see Part 6 for a complete citation): 1. Point: "...a single coordinate tuple." (Sec. 10.3.1) 2. MultiCurve: "...a list of curves. The order of the elements is significant and shall be preserved..." (Sec. 11.3.3.1). (The MultiCurve replaced the MultiLinestring datatype defined in GML version 3.0) 3. MultiSurface: "...a list of surfaces. The order of the elements is significant and shall be preserved..." (Sec 11.3.4.1). (The MultiSurface replaced the MultiPolygon datatype defined in GML version 3.0) The abstract data type is defined in the FGDC's "Framework Data Content Standard Part 0: Base Document" (Annex B.2.2) as a "class, or other classifier, that cannot be directly instantiated." The abstract data type (used in this standard for the complex element Address Reference System) may aggregate multiple elements of different data types, geometric and non-geometric. 2.1.6 Notation for Constructing Complex Elements The following notation is used to show how complex elements are constructed from simple or other complex elements: {} enclose the name of an element. * indicates that the element is required to create the complex element. Otherwise the element may be omitted when desired. + indicates "and" (concatenation), with a space implied between each component unless stated otherwise. 2.1.7 XML and GML Standard XML models and examples conform to the W3C XML Core Working Group's "Extensible Markup Language (XML) 1.0" (see Appendix A for a complete citation). Geometry elements are defined and implemented following OGC's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" Version: 3.2.1. 18 Federal Geographic Data Committee FGDC Document Number FGDC-STD-016-2011 United States Thoroughfare, Landmark, and Postal Address Data Standard Table of Elements and Attributes Category Group Element Name Simple/Complex Definition Address Elements Address Number Elements Address Number S The portion of the Complete Prefix Address Number which precedes the Address Number itself. Address Number S The numeric identifier for a land parcel, house, building, or other location along a thoroughfare or within a community. Address Number S The portion of the Complete Suffix Address Number which follows the Address Number itself. Complete C An Address Number, alone or Address Number with an Address Number Prefix and/or Address Number Suffix, which identifies a location along a thoroughfare or within a community. Street Name Elements Street Name Pre S A word or phrase in a Modifier Complete Street Name that 1. Precedes and modifies the Street Name, but is separated from it by a Street Name Pre Type or a Street Name Pre Directional or both, or 2. Is placed outside the Street Name so that the Street Name can be used in creating a sorted (alphabetical or alphanumeric) list of street names. Street Name S A word preceding the street Predirectional name that indicates the directional taken by the thoroughfare from an arbitrary starting point or line, 19 Federal Geographic Data Committee FGDC Document Number FGDC-STD-016-2011 United States Thoroughfare, Landmark, and Postal Address Data Standard Category Group Element Name Simple/Complex Definition or the sector where it is located. Street Name S A word or phrase that Pretype precedes the Street Name and identifies a type of thoroughfare in a Complete Street Name. Separator S A symbol, word, or phrase Element used as a separator between components of a complex element or class. The separator is required for Intersection Addresses and for Two Number Address Ranges, and it may be used in constructing a Complete Street Name. Street Name S The portion of the Complete Street Name that identifies the particular thoroughfare (as opposed to the Street Name Pre Modifier, Street Name Post Modifier, Street Name Pre Directional, Street Name Post Directional, Street Name Pre Type, Street Name Post Type, and Separator Element (if any) in the Complete Street Name.) Street Name S A word or phrase that follows Posttype the Street Name and identifies a type of thoroughfare in a Complete Street Name. Street Name S A word following the street Postdirectional name that indicates the directional taken by the thoroughfare from an arbitrary starting point or line, or the sector where it is located. Street Name Post S A word or phrase in a Modifier Complete Street Name that follows and modifies the Street Name, but is separated 20 Federal Geographic Data Committee FGDC Document Number FGDC-STD-016-2011 United States Thoroughfare, Landmark, and Postal Address Data Standard Category Group Element Name Simple/Complex Definition from it by a Street Name Post Type or a Street Name Post Directional or both. Complete Street C Official name of a street as Name assigned by a governing authority, or an alternate (alias) name that is used and recognized. Intersection Corner Element Corner Of S A directional word describing a
Load more

Recommended publications
  • Geoplace Data Entry Conventions and Best Practice for Streets
    GeoPlace Data Entry Conventions and Best Practice for Streets A Reference Manual DEC-Streets Version 4.1 June 2019 The DEC-Streets version 4.1 is the reference document for the NSG User, street works and Statutory Undertaker communities. DCA-DEC-CG [email protected] Page intentionally blank © GeoPlace™ LLP GeoPlace Data Entry Conventions and Best Practice for Streets (DEC-Streets) Version 4.1, June 2019 Page 2 of 223 Contents Contents Contents ______________________________________________________________________ 3 List of Tables ______________________________________________________________________ 9 List of Figures _____________________________________________________________________10 Related Documents ________________________________________________________________12 Document History _________________________________________________________________13 Policy changes in DEC-Streets Consultation Version 4.1 ____________________________________15 Items under review ________________________________________________________________16 1. Foreword _____________________________________________________________17 2. About this Reference Manual _____________________________________________19 2.1 Introduction ___________________________________________________________19 2.2 Copyright ______________________________________________________________20 2.3 Evaluation criteria _______________________________________________________20 2.4 Definitions used throughout this Reference Manual ____________________________20 2.5 Alphabet, Punctuation and
    [Show full text]
  • Traffic Engineering Standards
    TRAFFIC ENGINEERING STANDARDS PHILADELPHIA STREETS DEPARTMENT Carlton Williams Commissioner Richard J. Montanez, P.E. Deputy Commissioner of Transportation Patrick O’Donnell Director of Transportation Operations Kasim Ali, P.E. Chief Traffic Engineer Traffic Engineering Standards 1994, rev2018 TABLE OF CONTENTS SECTION TOPIC SUBSECTION 0 Preface General Standards 0.1 Authority 0.2 Engineering Details 0.3 Definitions 0.4 Deviation from Standards 0.5 Revision Schedule and Notice 0.6 1 Traffic Impact Studies Functional Classification 1.1 Criteria 1.2 Format Requirements 1.3 2 Intersection Design Warrants 2.1 Channelized Right Turn 2.2 Unconventional Intersection Treatments 2.3 3 Data Collection Volumes 3.1 Traffic Count Collection 3.2 Crashes 3.3 4 Software Turning Plans/Templates 4.1 Capacity Analysis 4.2 5 Signal & Interconnect Plan Layout & Permitting Survey Information 5.1 Utility Information Required 5.2 Additional (Other) Information 5.3 Traffic Signal Plan Requirements 5.4 Fiber Optic Interconnect Plan Info 5.5 Professional Engineer Required 5.6 Drawing Scale 5.7 Approval Block 5.8 Application Required 5.9 6 Traffic Signal Hardware Standard Coating Colors 6.1 Mast Arm 6.2 C-Post 6.3 D-Pole 6.4 Pedestal Pole 6.5 Signal Heads 6.6 Conduit 6.7 Junction Boxes 6.8 Wiring 6.9 Controller 6.10 Actuation 6.11 Page 2 of 64 Traffic Engineering Standards 1994, rev2018 SECTION TOPIC SUBSECTION Pedestrian Push Buttons 6.12 Pre-Emption & Priority Detection 6.13 Electrical Service Connection 6.14 7 Traffic Signal Programming Movement, Sequence & Timing
    [Show full text]
  • Transit First Analysis of SEPTA Route 34
    The Delaware Valley Regional Planning Commission is dedicated to uniting the region’s elected officials, planning professionals, and the public with a common vision of making a great region even greater. Shaping the way we live, work, and play, DVRPC builds consensus on improving transportation, promoting smart growth, protecting the environment, and enhancing the economy. We serve a diverse region of nine counties: Bucks, Chester, Delaware, Montgomery, and Philadelphia in Pennsylvania; and Burlington, Camden, Gloucester, and Mercer in New Jersey. DVRPC is the federally designated Metropolitan Planning Organization for the Greater Philadelphia Region — leading the way to a better future. The symbol in our logo is adapted from the official DVRPC seal and is designed as a stylized image of the Delaware Valley. The outer ring symbolizes the region as a whole while the diagonal bar signifies the Delaware River. The two adjoining crescents represent the Commonwealth of Pennsylvania and the State of New Jersey. DVRPC is funded by a variety of funding sources including federal grants from the U.S. Department of Transportation’s Federal Highway Administration (FHWA) and Federal Transit Administration (FTA), the Pennsylvania and New Jersey departments of transportation, as well as by DVRPC’s state and local member governments. The authors, however, are solely responsible for the findings and conclusions herein, which may not represent the official views or policies of the funding agencies. DVRPC fully complies with Title VI of the Civil Rights Act of 1964 and related statutes and regulations in all programs and activities. DVRPC’s website may be translated into Spanish, Russian, and Traditional Chinese online by visiting www.dvrpc.org.
    [Show full text]
  • Massgis Address Standard
    An Address Standard for Massachusetts Municipalities Issued by: Bureau of Geographic Information (MassGIS) Office of Information Technology (MassIT) Commonwealth of Massachusetts Version 1.0 December 2016 PREFACE What is this document about? Addresses identify locations where people live and work and play. Accurate, consistent, and complete addressing supports better communications, easier travel, and more efficient delivery of goods and services; it may even save lives by expediting emergency response. This standard provides guidance on how addresses should be assigned and how they should be stored and managed using computer software. Who is the intended audience? The intended audience is staff in local government who are involved in address assignment or who use addresses in their daily work, as well as the vendors that provide them with services and software. How does this standard apply to my municipality? Every municipality is different, so different parts of the standard will be relevant depending on what the municipality is interested in doing, and what resources it has available. The scenarios below are intended to help you decide what portions of this document will be most useful to you. Scenario What you should read #1. A largely rural town with addresses recorded in written form or in Sections 1, 2, 3 simple spreadsheet format and an informal process for maintaining Sections 4.1 – 4.3 and sharing address information. Optionally, Sections 6.1 - 6.4.6, 6.5 #2. Same as #1 but with a larger population and/or an urban center Sections 1, 2, 3 and a government with individual departments interested in Section 4 managing addresses in software used for permitting or licensing Sections 5.1 – 5.3 activities.
    [Show full text]
  • Pennsylvania Postal Historian
    FEBRUARY 2004 Whole No. 158 Vol. 32, No. 1 PENNSYLVANIA POSTAL HISTORIAN THE BULLETIN OF THE PENNSYLVANIA POSTAL HISTORY SOCIETY Inside this issue: The Ordinance of 1856 and the Renumbering of Philadelphia Street Addresses CAMERON COUNTY – LAND OF THE SINNEMAHONING Part 3, Discontinued Post Offices on Portage Creek and on Driftwood Branch of the Sinnemahoning Baltimore Freight Money Letter Returned to Philadelphia as a Private Ship Letter Stampless Covers from Linwood or Linwood Station? Remailed Postcard Engenders New EKU for Collingdale, Pa. Doane PENNSYLVANIA POSTAL HISTORIAN The Bulletin of the Pennsylvania Postal History Society ISSN – 0894 – 0169 Est. 1974 PENNSYLVANIA POSTAL HISTORIAN The bulletin of the Pennsylvania Postal History Society Published quarterly by the PPHS for its members Volume 32 No. 1 (Whole No. 158) February 2004 APS Affiliate No. 50 Member of the Pennsylvania Federation of Museums and Historical Organizations www.PaPHS.org The PPHS is a non-profit , educational organization whose purposes are to cultivate and to promote the study of the postal history of Pennsylvania, to encourage the acquisition and preservation of material relevant and necessary to that study, and to publish and to support the publication of such knowledge for the benefit of the public. The views expressed by contributors are their own and not necessarily those of the PPHS, its Directors, Officers, or Members. Comments and criticisms are invited. Please direct your correspondence to the Editor. OFFICERS and DIRECTORS APPOINTED OFFICERS OFFICERS President Richard Leiby, Jr. Historian Editor Norman Shachat 1774 Creek View Dr. 382 Tall Meadow Lane Fogelsville, PA 18051 Yardley, Pa 19067 Secretary Norman Shachat Auctioneer Robert McKain 382 Tall Meadow Lane 2337 Giant Oaks Drive Yardley, PA 19067 Pittsburgh, PA 15241 Treasurer Richard Colberg Publicity Donald W.
    [Show full text]
  • Dakota County Uniform Street Naming and Addressing System Procedural Manual
    DAKOTA COUNTY UNIFORM STREET NAMING AND ADDRESSING SYSTEM PROCEDURAL MANUAL SECTION 1.00 DEFINITIONS 1.01 "COUNTY" means Dakota County, Minnesota. 1.02 "COUNTY BOARD" means the Dakota County Board of Commissioners. 1.03 "COUNTY HIGHWAY" has the meaning given to it in Minn. Stat. § 160.02, subd. 17 as may be amended. 1.04 "MUNICIPALITY" means a city or township located in Dakota County, Minnesota. 1.05 "PARTICIPATING MUNICIPALITY" means a municipality that has adopted the USNAS for use within its boundaries. 1.06 "STATE CAPITOL" means the Minnesota State Capitol located in St. Paul, Minnesota. 1.07 "USNAS" means the Dakota County Uniform Street Naming and Addressing System Procedural Manual. SECTION 2.00 PURPOSE The USNAS sets forth a logical system for naming streets and assigning addresses in certain areas of the county. The USNAS defines techniques whereby a given address describes a unique location within the system. The USNAS is for use by the county and participating municipalities. The purpose of the USNAS is to establish a uniform system for naming streets and assigning numbers to dwellings, principal buildings, and businesses to facilitate emergency services, deliveries, and to provide the general advantages of a uniform system. SECTION 3.00 ADMINISTRATION Unless otherwise agreed to between the county and a participating municipality, each city or township that adopts this procedural manual shall be responsible for the administration of the USNAS within its boundaries. The county has sole authority to name and number all county highways. SECTION 4.00 METHODOLOGY The county street naming and addressing system is based upon an imaginary grid system with an x and y-axis.
    [Show full text]
  • Name & Address Formatting
    NAME & ADDRESS FORMATTING Please follow the guidelines below when formatting attributes. Again, name is the only required attribute but please add the address of the physical location of the structure if you are able to find it from an authoritative source. A road name only or nearby intersection is also acceptable if you are unable to confirm the physical address (e.g., South Howard Court, or South Howard Court and Bluebird Lane). If the optional attributes have been filled out, please verify them. If you are a Peer Reviewer or an Advanced Editor, we would like you to make the attributes as consistent as possible. For example, if you are checking all of the fire stations within an entity, such as the Denver Fire Department, please format all of the names in the same way as they are found on the official website. NOTE: If you find inconsistencies in names between authoritative websites (e.g., a county website and a fire station website), please pick one source and format all of the features according to that source. Also please make sure feature names are not generic, such as "U.S. Post Office" or "Fire Station." Each feature should have their location incorporated into its name. For Post Offices, this can be found on the USPS.com search engine. TOP THINGS TO LOOK FOR AND CORRECT: ABBREVIATIONS: Example: Preferred: 23rd St. 23rd Street Denver FD Denver Fire Department Martin HS Martin High School Ellis Elem. Ellis Elementary School CAPITALIZATION: Example: Preferred: Denver fire department Denver Fire Department Mcleary or Mcmillan McLeary or McMillan ANDERSON ELEMENTARY SCHOOL Anderson Elementary School Knox drive Knox Drive NAMING CONSISTENCY: Example: Preferred: FIRE STATIONS: Denver Fire Department Station 23 Denver Fire Department Station 23 Denver Fire Department 24 Denver Fire Department Station 24 Denver FD, Station 1 Denver Fire Department Station 1 POST OFFICES: Westminster (Harris Park) Westminster Post Office Harris Park Station Harris Park Station Westminster Post Office Harris Park Station U.S.
    [Show full text]
  • Publication 28 Contents
    Contents 1 Introduction. 1 11 Background . 1 111 Purpose . 1 112 Scope . 1 113 Additional Benefits . 1 12 Overview . 2 121 Address and List Maintenance . 2 122 List Correction. 2 123 Updates. 2 124 Address Output . 3 125 Deliverability . 3 13 Address Information Systems Products and Services . 3 2 Postal Addressing Standards . 5 21 General . 5 211 Standardized Delivery Address Line and Last Line. 5 212 Format . 5 213 Secondary Address Unit Designators . 6 214 Attention Line . 7 215 Dual Addresses . 7 22 Last Line of the Address. 8 221 City Names . 8 222 Punctuation . 8 223 Spelling of City Names . 8 224 Format . 9 225 Military Addresses. 9 226 Preprinted Delivery Point Barcodes . 9 23 Delivery Address Line . 10 231 Components . 10 232 Street Name . 10 233 Directionals . 11 234 Suffixes . 13 235 Numeric Street Names . 13 236 Corner Addresses . 14 237 Highways. 14 238 Military Addresses. 14 239 Department of State Addresses . 15 June 2020 i Postal Addressing Standards 24 Rural Route Addresses. 15 241 Format . 15 242 Leading Zero . 16 243 Hyphens . 16 244 Designations RFD and RD . 16 245 Additional Designations . 16 246 ZIP+4. 16 25 Highway Contract Route Addresses . 17 251 Format . 17 252 Leading Zero . 17 253 Hyphens . 17 254 Star Route Designations . 17 255 Additional Designations . 18 256 ZIP+4. 18 26 General Delivery Addresses . 18 261 Format . 18 262 ZIP Code or ZIP+4 . 18 27 United States Postal Service Addresses . 19 271 Format . 19 272 ZIP Code or ZIP+4 . 19 28 Post Office Box Addresses. 19 281 Format . 19 282 Leading Zero .
    [Show full text]
  • Benjamin S. Anderson House Year Built: 1901 Street & Number: 4211 Brooklyn Avenue NE Assessor’S File No.: 114200-0950 Original Owner: Benjamin S
    Name: Benjamin S. Anderson House Year Built: 1901 Street and Number: 4211 Brooklyn Avenue NE Assessor's File No. 114200-0950 Legal Description: Lot 10, Block 10, Brooklyn Addition to Seattle, according to the plat recorded in Volume 7 of Plats, Page 32, in King County, Washington. Plat Name: Brooklyn Addition Block: 10 Lot: 10 Present Use: Rooming house Present Owner: Internos Properties LLC Original Owner: Benjamin S. Anderson Original Use: Single family house Architect: Unknown Builder: Unknown Submitted by: David Peterson / Historic Resource Consulting Date: January 25, 2019 301 Union Street #115 Seattle WA 98111 Ph: 206-376-7761 / [email protected] Reviewed by: Date: (Historic Preservation Officer) Benjamin S. Anderson House 4211 Brooklyn Avenue NE Seattle Landmarks Preservation Board January 25, 2019 David Peterson historic resource consulting 301 Union Street #115 Seattle WA 98111 P:206-376-7761 [email protected] 4211 Brooklyn Avenue NE Seattle Landmark Nomination INDEX I. Introduction 3 II. Building information 3 III. Architectural description 4 A. Site and neighborhood context B. Building description C. Summary of primary alterations IV. Historical context 7 A. The development of the neighborhood B. The development of the subject building, and building owners C. The Victorian Italianate style V. Bibliography and sources 13 VI. List of Figures 15 Illustrations 17 - 48 Historic King County Tax Assessor residential property record sheets Following Survey Following David Peterson historic resource consulting – Seattle Landmark Nomination – Benjamin S. Anderson House – January 25, 2019 2 I. INTRODUCTION This report was written at the request of The Standard at Seattle LLC, a development company, in order to ascertain its historic nature prior to a proposed major alteration to the property.
    [Show full text]
  • Governmentality, the Grid, and the Beginnings of a Critical Spatial History of the Geo-Coded World”
    The Pennsylvania State University The Graduate School College of Earth and Mineral Sciences GOVERNMENTALITY, THE GRID, AND THE BEGINNINGS OF A CRITICAL SPATIAL HISTORY OF THE GEO-CODED WORLD A Thesis in Geography by Reuben S. Rose-Redwood © 2006 Reuben S. Rose-Redwood Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy May 2006 The thesis of Reuben S. Rose-Redwood was reviewed and approved* by the following: James P. McCarthy Assistant Professor of Geography Thesis Adviser Chair of Committee Melissa W. Wright Associate Professor of Geography Daniel L. Purdy Associate Professor of German and Slavic Languages and Literatures Jeremy S. Packer Assistant Professor of Film/Video and Media Studies Roger M. Downs Professor of Geography Head of the Department of Geography * Signatures are on file in the Graduate School ABSTRACT In many cities and towns throughout the world today, the numbering of houses has become such a commonplace practice of local government that its everydayness makes it hard for urban inhabitants to even imagine living without these inscriptions that make up the abstract spaces of everyday life. Yet, as a spatial practice, house numbering is a comparatively recent phenomenon, which did not become widespread until the second half of the eighteenth century. So taken-for-granted has the house number become that few geographers have examined the history of house numbering from a critical perspective. This is particularly surprising given the recent interest in understanding the intersecting “axes” of knowledge, power, and the production of space. Drawing upon extensive archival research, this study brings together the theoretical insights of governmentality studies and Marxian geography to explore the history of house numbering in U.S.
    [Show full text]
  • LOCATION REFERENCING SYSTEM Introduction & Technical Manual
    LLOOCCAATTIIOONN RREEFFEERREENNCCIINNGG SSYYSSTTEEMM IInnttrroodduuccttiioonn && TTeecchhnniiccaall MMaannuuaall 22001188 EEddiittiioonn Roadway Inventory & Testing Unit Asset Management Division Pennsylvania Department of Transportation LOCATION REFERENCING SYSTEM Introduction & Technical Manual 2018 Edition Please direct questions or comments regarding this manual, the Location Referencing System, or any other related topic, to: Janice Arellano, P.E. Chief, Roadway Inventory & Testing Unit Pennsylvania Department of Transportation 907 Elmerton Avenue – BOMO Annex Harrisburg, PA 17110 Telephone: 717-787-7294 FAX: 717-705-8921 Email: [email protected] Contents 1 Introduction LRS Overview ...................................................................................................................................................... 2 LRS History ....................................................................................................................................................... 3 LRS SLD’s .............................................................................................................................................................. 4 2 LRS Routing & Segmentation LRS Key ............................................................................................................................................................. 6 State Routes (SR’s) .............................................................................................................................. 7 Non-tolled Pennsylvania Turnpike
    [Show full text]
  • {PDF} Numerical Street
    NUMERICAL STREET PDF, EPUB, EBOOK Antonia Pesenti,Hilary Bell | 32 pages | 01 Jun 2016 | NewSouth Publishing | 9781742232287 | English | Sydney, NSW, Australia Numerical Street by Hilary Bell Numerical Street continues this exploration. Alphabetical Sydney is also available from all good bookstores and from NewSouth here. See the Koskela website for more info. Antonia Pesenti architect and illustrator and Hilary Bell playwright and author are creators of the picture books 'Alphabetical Sydney' and 'Numerical Street'. NewSouth Publishing. Counting curiosities on Numerical Street Pesenti and Bell. Articles Shop Contact. Numerical Street. Photos: Antonia Pesenti. The illustrations in the book are based on real shops and businesses and often real signs photographed in streets all over Sydney, as well as Melbourne, Batemans Bay, Braidwood and the Blue Mountains. Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Other editions. Enlarge cover. Error rating book. Refresh and try again. Open Preview See a Problem? Details if other :. Thanks for telling us about the problem. Return to Book Page. Preview — Numerical Street by Hilary Bell. Numerical Street by Hilary Bell ,. Antonia Pesenti. Count as you walk up Numerical Street Every page has a numerical treat. Get your pants altered, get your keys cut, Open the book before the shops shut! Children will love counting the objects they see as they hop, skip or jump up Numerical Street — past cake shops, hair stylists, laundromats, pet stores and shoe repairers, all with their curious wares on display. Get A Copy. Hardcover , 32 pages. More Details Original Title.
    [Show full text]