Layer: Building Address Points (ID: 0)

Name: Building Address Points

Display Field: ROADNAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><A href="https://www.grantspassoregon.gov/DocumentCenter/View/39/Title-6---Grants-Pass-Uniform-Traffic-Code--PDF?bidId=" STYLE="text-decoration:underline;">Chapter 6.40 "Street Numbering" </A>of Grants Pass Municipal Code, explains the process of adding new addresses within the city limits. Also for further detail please review the following:1. <A href="http://meadow.spatialfocus.com/address_standard/" STYLE="text-decoration:underline;">http://meadow.spatialfocus.com/address_standard/</A>2. <A href="https://www.oregon.gov/geo/Pages/addressing-standard.aspx" STYLE="text-decoration:underline;">https://www.oregon.gov/geo/Pages/addressing-standard.aspx </A>a. <A href="https://www.oregon.gov/geo/Documents/Introduction%20-%20Address%20Standard.pdf" STYLE="text-decoration:underline;">Intro</A>b. <A href="https://www.oregon.gov/geo/Documents/Content%20-%20Address%20Standard.pdf" STYLE="text-decoration:underline;">Content</A>c. <A href="https://www.oregon.gov/geo/Documents/Class%20-%20Address%20Standard.pdf" STYLE="text-decoration:underline;">Class</A>d. <A href="https://www.oregon.gov/geo/Documents/Quality%20-%20Address%20Standard.pdf" STYLE="text-decoration:underline;">Quality</A>e. <A href="https://www.oregon.gov/geo/Documents/Exchange%20-%20Address%20Standard.pdf" STYLE="text-decoration:underline;">Exchange</A>f. <A href="https://www.oregon.gov/geo/Documents/Reference%20-%20Address%20Standard.pdf" STYLE="text-decoration:underline;">Reference</A>g. <A href="https://www.oregon.gov/geo/Documents/Appendix%20-%20Address%20Standard.pdf" STYLE="text-decoration:underline;">Appendix</A><A href="https://www.grantspassoregon.gov/475/GIS-Division" STYLE="text-decoration:underline;">City of Grants Pass GIS Website</A>Un-adopted and unofficial but important to the process see guideline below: <A href="https://www.vox.com/2016/11/14/13275486/streets-roads-avenues-names-reasons" STYLE="text-decoration:underline;">https://www.vox.com/2016/11/14/13275486/streets-roads-avenues-names-reasons</A>Street Naming<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>These are meant to be minimum standards.</LI><LI>The main objective is to provide clear street names for citizens and for emergency dispatch and to minimize the possibility of emergency personnel being unable to find a location.</LI><LI>Cardinal directions cannot be used in the name. Directions are used only to designate the portion of an existing road. (Not acceptable – North Road, East Fort Road, Northstar Drive.)</LI><LI>Road names should be unique and not repeated in the County from this point forward, with the exception of continuation of existing streets.</LI><LI>Homonyms for road names are not acceptable.</LI><LI>Street names cannot contain any punctuation or special characters. Only alphabetical symbols A through Z, and numbers 0 through 9 and blank spaces may be used in street names.</LI><LI>No more than 13 characters and spaces may be used including suffix.</LI><LI>Anytime that a street makes a directional change of approximately ninety degrees, the street name shall change. </LI><LI>Existing street names shall continue across intersections and roundabouts.</LI><LI>All roads that serve two or more properties shall be named regardless of whether the ownership is public or private.</LI><LI>No two roads shall be given the same name (e.g. Brookside Drive and Brookside Lane.)</LI><LI>No two roads should have similar sounding names (e.g. Beech Drive and Peach Drive.)</LI><LI>No street name shall be approved if it is similar to or pronounced the same as the name of any other street within the City County.</LI><LI>A street name should be appropriate, easy to read (so that children can use the name in an emergency situation), and should add to community pride by promoting local heritage, history and traditions and reflect local geography and character.</LI><LI>Names with the same theme (i.e. flowers, states) are suggested for naming streets in an entire subdivision, as a means of general identification.</LI><LI>Names tending to be confused as homonyms, having the same or similar pronunciation but with different spellings, are discouraged within a municipality, zip code, or emergency service zone area (e.g. Smith, Smythe, or Smythe; Ellis or Allice; Allen or Alan).</LI><LI>Names of which may be offensive (slang, double meanings, etc) shall be avoided.</LI><LI>Use of frivolous or complicated words, or unconventional spellings in road names is discouraged.</LI><LI>Avoid the use of standard suffixes of directional suffixes or prefixes as road/street names (e.g. North Blvd, Court St, Avenue of Pines).</LI><LI>Avoid family names or individual names, especially living persons or politicians.</LI><LI>When naming new streets, duplication of names must be avoided with a municipality, postal zip code and emergency service zone area.</LI><LI>Roads, which pass through, more than one municipality should bear the same name throughout the county wherever possible. Street and roadway name changes will only occur at street intersections.</LI><LI>New streets will be named during the subdivision process.</LI><LI>Private lanes, which are not owned or maintained by a municipality, shall be named when there is more than one addressable building located on the road. </LI></UL>Street Suffixes<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>The following table of suffixes are the only ones that can be used to new street names: <UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Avenue– Ave – A roadway or thoroughfare that is continuous and not limited to a single subdivision.</LI><LI>Boulevard– Blvd – Street with a landscaped median dividing the roadway.</LI><LI>Circle – Cir – Discouraged but allowed, at the discretion of the local jurisdiction.</LI><LI>Drive – Dr – A curvilinear street that would be a main through street.</LI><LI>Lane – Ln – Minor street within a subdivision.</LI><LI>Parkway – Pkwy – A thoroughfare designated as a collector or arterial, with a median reflecting the parkway character implied in the name.</LI><LI>Place – Pl – Permanently dead-end street, terminating in a cul-de-sac, or short through street, not longer than 660 feet in length.</LI><LI>Road – Rd – A designated thoroughfare.</LI><LI>Street – St – The common or default suffix.</LI><LI>Way – Way – A curvilinear street.</LI><LI>The following suffixes are suggested for naming a type of roadway.</LI><LI>Alley – Aly – A narrow lane between or behind a row of buildings.</LI><LI>Avenue – Ave – A roadway or thoroughfare in a densely populated area</LI><LI>Boulevard – Blvd – A street with a median reflecting the boulevard character</LI><LI>Circle – Cir – A cul de sac or looped street that begins and circles back to terminate on the same road</LI><LI>Court –Ct – A permanently closed street, not exceeding 1,000 feet, such as a cul-de-sac</LI><LI>Drive –Dr – A curvilinear street</LI><LI>Highway –Hwy – A primary state or federal route, suitable for heavy traffic volume</LI><LI>Lane –Ln – A minor dead-end street or private lane</LI><LI>Parkway –Pkwy – A road with a median reflecting parkway character</LI><LI>Pike –Pike – A primary state or federal route, suitable for heavy traffic volume</LI><LI>Road –Rd – A common roadway, usually in less densely populated areas</LI><LI>Street –St – A common roadway, usually in more densely populated areas</LI><LI>Way –Way – A minor roadway</LI></UL></LI><LI>Streets running East and West are Avenues.</LI><LI>Streets running North and South are Streets.</LI><LI>Streets running East and West connecting with a North-South street should be a Drive.</LI><LI>Streets running North and South and connecting with a North-South street should be a Way.</LI><LI>Horseshoe-shaped streets beginning and ending within a major block, or dead end streets should be a “circle”. It is suggested that the term “circle” should be used sparingly. If at all possible, a Way or Drive should be used except in the case of absolute necessity.</LI></UL>Numbering<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Numbers should not be duplicated for 5 blocks. (For example, first house 1901; next street, first house 1903; 1905; 1907, etc.)</LI><LI>North and West – even.</LI><LI>South and East – odd.</LI><LI>The number assigned to each structure shall be that of the numbered interval falling closest to the front door. If the front door cannot be seen form the main road, the number shall be that of the interval falling closest to the driveway of said structure.</LI><LI>Every structure with more than one principle use or occupancy shall have a separate number for each use or occupancy.</LI><LI>Apartments will have one road number with an apartment number, such as 235 Maple Dr, Apt 201.</LI><LI>When assigning numbers to corner lots, use the front door. When the front door is obscured or if the structure is best reached for emergency purposes by the driveway, assign he property number based on where the driveway falls on the road.</LI><LI>Houses or trailers behind other houses or trailers facing the road, sharing a common driveway, should be numbered following the rules for distance and direction herein. Use of hyphenated, alphanumeric or fractional number is discouraged (e.g. 254A, 254 ½, 254-3).</LI><LI>Apartments and other multi-tenant structures should be numbered with the main building and then assigned apartment numbers as secondary location indicators (e.g. 202 Main St, Apt 303). If possible, use apartment numbers to indicate the floor location (e.g. Apt 303 is the third apartment on the third floor).</LI><LI>Manufactured Home Park should be numbered just like apartments unless already marked. The difference would be that individual mobile homes would be designated as lots or spaces instead of apartments (e.g. 334 Elm St, Lot 23). An alternative is to name the road(s) in the park and number the homes as single family dwellings following the rules for distance and direction herein.</LI><LI>When assigning numbers, the middle of the structure should determine the address assigned. Structures should always be numbered according to the road they face, not where the driveway enters the road or the mailbox is. An exception to this is when the structure is obscured or if the structure is best reached for emergency purposes by the driveway. In such cases, the address should be assigned where the driveway falls on the road.</LI></UL>Goals<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>The primary goal of this policy is to provide emergency service agencies with a complete set of addresses, so that emergency victims can be located with greatest efficiency. Secondary goals include:<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>To improve the quality of life for residents through easier delivery of mail and services.</LI><LI>To project a positive and progressive image to residents, prospective residents and developers and </LI><LI>To promote the local tourist industry by making it easier for visitors to locate the attractions of Jo Co?Enforcement<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI></LI></UL></LI></UL></LI></UL></DIV></DIV></DIV>

Service Item Id: 3ffc6ecee526483aa4b207525dafd3fb

Copyright Text: The City of Grants Pass and various departments maintain GIS data related to their division. For specific information pertaining to this GIS layer please contact the responsible department. For general inquiry please contact the GIS department at 541-450-6067.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 10000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

Drawing Info:

Renderer:

Simple Renderer:

Symbol:

Style:

Color:

Size:

Angle:

XOffset:

YOffset:

Outline:

Width:

Label:

Description:

Transparency:

Labeling Info:

Advanced Query Capabilities:

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
ADDRNUM ( type: esriFieldTypeString, alias: Full Address Number, length: 20 )
APARTMENT ( type: esriFieldTypeString, alias: Apartment, length: 10 )
FLOOR ( type: esriFieldTypeString, alias: Floor Number, length: 10 )
ROADPREDIR ( type: esriFieldTypeString, alias: Road Prefix, length: 2 , Coded Values: [NW: NW] , [NE: NE] , [SE: SE] , ...5 more... )
ROADNAME ( type: esriFieldTypeString, alias: Road Name, length: 50 )
ROADTYPE ( type: esriFieldTypeString, alias: Road Type, length: 10 , Coded Values: [Ave: AVE] , [Blvd: BLVD] , [Ct: CT] , ...19 more... )
ROADPOSTDIR ( type: esriFieldTypeString, alias: Post Direction, length: 2 , Coded Values: [NE: NE] , [NW: NW] , [SE: SE] , ...5 more... )
MUNICIPALITY ( type: esriFieldTypeString, alias: Municipality Name, length: 100 )
FULLADDR ( type: esriFieldTypeString, alias: Full Address, length: 125 )
PLACENAME ( type: esriFieldTypeString, alias: Place Name, length: 125 )
POINTTYPE ( type: esriFieldTypeString, alias: Location, length: 30 , Coded Values: [Vacant Parcel: Vacant Parcel] , [Building: Building] , [Condo or Unit: Condo or Unit] , ...3 more... )
CAPTUREMETH ( type: esriFieldTypeString, alias: Capture Method, length: 30 , Coded Values: [Geocoded: Geocoded] , [GPS: GPS] , [Site Visit: Site Visit] , ...2 more... )
STATUS ( type: esriFieldTypeString, alias: Status, length: 30 , Coded Values: [Current: Current] , [Pending: Pending] , [Retired: Retired] , ...2 more... )
GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
CITY ( type: esriFieldTypeString, alias: CITY, length: 100 )
STATE ( type: esriFieldTypeString, alias: STATE, length: 100 )
ZIP ( type: esriFieldTypeString, alias: ZIP, length: 50 )
SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
NOTES ( type: esriFieldTypeString, alias: NOTES, length: 250 )
TRUADDRESSNUMBER ( type: esriFieldTypeInteger, alias: Numeric Address )
MAPNUMX ( type: esriFieldTypeString, alias: MAPNUMX, length: 20 )

Supported Operations: Query Query Attachments Query Analytic Generate Renderer Return Updates

Iteminfo Thumbnail Metadata