Street Names Check
A street naming guidelines documents can be downloaded by clicking on the following link:
Street Naming Guidelines x

To add a street name or names to be checked, please enter the requested information below, then click the Add Street Name button.
 

Enter the components for proposed new street name in the boxes below:

Direc. Prefix Street Name Street Type (Suffix) Direc. Suffix



A full street name is typically composed of up to 4 parts: a directional prefix, base street name, street type (or suffix), and a directional suffix. Only the base street name and street type are required. As an example, consider the street name N Shepherd Drive. In this name, the "N" is the directional prefix, the "Shepherd" is the base street name, and the "Drive" is the street type. It is also possible that a directional suffix might fall after the street type.
In order to facilitate the best possible emergency response, no new street name can duplicate an existing street name that is already found in our City Address Point or Roads data, or a street that has been reserved by plat applicant. In addition, it is important that the base street name not contain any of the approved street types (often also called suffixes). It is also important that no proposed street name sound too much like an existing street name. This is a research tool only. Your research will not reserve any name. Only a plat approval will reserve names.
The City is providing a tool to help plat applicants conduct street name research. This tool will check a proposed street name or set of street names against all existing street names found in the City's Address Point and Roads data. Specifically, this tool performs the following four tests:
  • Do any of the words in the proposed base street name match one of the allowed street types (suffixes)? If so, the proposed name will be rated as a "Fail". Otherwise, it will be rated a "Pass".

  • Does the last portion of the last word of the proposed base street name match one of the allowed street types (suffixes)? If so, the proposed name will be rated as a "Fail". Otherwise, it will be rated a "Pass".

  • Does the proposed street name duplicate any existing street name in the city's data? If so, the proposed name will be rated as a "Fail". Otherwise, it will be rated a "Pass".

  • Does the proposed street name have any close sound-alikes relative to existing street names in the city's data? If so, the proposed name will be rated as a "Possible Fail Subject to Later Planner Review". Otherwise, it will be rated a "Pass".
The proposed name must pass each of the first 3 tests. In addition, if any sound-alikes identified are too close to the proposed street name (when said aloud), the Check-In planner will likely reject that name. That is why this test returns a Probably Fail response. The applicant might be best advised to come up with a different name rather than to try to submit a sound-alike name. It is suggested that a checked street name PDF be submitted with the initial Plat Tracker submission.

Sec. 42-133. (4) Street name suffixes shall be limited to the following uses:
  • "Court", "Circle", and "Loop" shall be used only to designate streets that terminate at a cul-de-sac or are configured as a loop street.

  • "Boulevard", "Crossing", "Crossroad", "Motorway", "Parkway", "Speedway", and "Throughway" shall be used only to designate major thoroughfares, major collector streets, collector streets or other streets designed to handle traffic volumes in excess of normal neighborhood traffic generation or that are divided streets with at least two lanes of traffic in each direction separated by a median.

  • "Bypass", "Expressway", "Freeway", and "Highway" shall be used only to designate highways or freeways subject to the jurisdiction of the state department of transportation.

  • "Avenue", "Drive", "Road", and "Street" shall be used only to designate major thoroughfares, major collector streets, collector streets or local streets.

  • "Bridge", "Fork", "Lane", "Oval", "Passage", "Path", "Place", "Trail", and "Way" shall be used only to designate collector streets or local streets.

  • "Tunnel" shall be used only to designate streets that provide underground or underwater passage.

  • A street name suffix shall not be used as part of the street name.

  • The abbreviation of a street name suffix shall be consistent with United States Postal Service postal addressing standards.
To see all of the street naming requirements pertaining to prefixes, street names, and suffixes visit Chapter 42, Sec. 42-138.
While the tool provided on this page will identify duplicate streets and sound-alikes, and include guidance as to the rejection likelihood of a proposed street name, it is possible that the Reviewing Planner of a plat application will identify additional problems in a proposed street name, so that it will be rejected as part of the plat submittal and review process.

If you require additional assistance, feel free to contact one of the individuals below.
Planning and Development Dept./Development Services
Jennifer Ostlind, Division Manager832-393-6569Jennifer.Ostlind@houstontx.gov
Hector Rodriguez, Administrative Manager832-393-6575Hector.Rodriguez@houstontx.gov
   
Technical Contact (Website and GIS)
Planning and Development Dept./Enterprise GIS832-393-6555plattrackertech@houstontx.gov
   
Street Name Questions (Addressing Team)
Chris McPhilamy, GIS Supervisor832-393-6561 (voice)Chris.McPhilamy@houstontx.gov
   
City of Houston, 611 Walker St., 6th Floor, Houston, TX 77002