# Streets without suffixs

**URL:** <https://community.thinkgeo.com/t/streets-without-suffixs/7262>\
**Category:** Geocoding\
**Created:** [April 30, 2012, 5:39pm UTC](https://community.thinkgeo.com/t/streets-without-suffixs/7262 "2012-04-30T17:39:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://community.thinkgeo.com/u/Ryan1)\
**Post date:** [April 30, 2012, 5:39pm UTC](https://community.thinkgeo.com/t/streets-without-suffixs/7262/1 "2012-04-30T17:39:06Z")

</div>

Hi,

We've&nbsp;run&nbsp;into&nbsp;an&nbsp;issue&nbsp;where&nbsp;geocoding&nbsp;addresses&nbsp;is&nbsp;inconsistent&nbsp;if&nbsp;you&nbsp;don't&nbsp;include&nbsp;a&nbsp;suffix&nbsp;of&nbsp;the&nbsp;street.&nbsp;&nbsp;For&nbsp;most&nbsp;streets,&nbsp;everything&nbsp;works&nbsp;fine,&nbsp;but&nbsp;we&nbsp;are&nbsp;running&nbsp;into&nbsp;an&nbsp;issue&nbsp;with&nbsp;something&nbsp;like&nbsp;2300&nbsp;Tuna&nbsp;Canyon&nbsp;Rd,&nbsp;Topanga,&nbsp;CA,&nbsp;where&nbsp;if&nbsp;our&nbsp;users&nbsp;only&nbsp;search&nbsp;for&nbsp;2300&nbsp;Tuna&nbsp;Canyon,&nbsp;our&nbsp;result&nbsp;doesn't&nbsp;show&nbsp;up,&nbsp;only&nbsp;one&nbsp;for&nbsp;like&nbsp;a&nbsp;Tuna&nbsp;Road.&nbsp;&nbsp;I&nbsp;understand&nbsp;why&nbsp;this&nbsp;happens&nbsp;(the&nbsp;system&nbsp;is&nbsp;treating&nbsp;canyon&nbsp;as&nbsp;the&nbsp;suffix),&nbsp;but&nbsp;I&nbsp;think&nbsp;the&nbsp;system&nbsp;should&nbsp;ALSO&nbsp;search&nbsp;for&nbsp;roads&nbsp;that&nbsp;have&nbsp;the&nbsp;"suffix"&nbsp;in&nbsp;the&nbsp;name,&nbsp;especially&nbsp;for&nbsp;suffixs&nbsp;that&nbsp;are&nbsp;common&nbsp;like&nbsp;Canyon.&nbsp;&nbsp;If&nbsp;we&nbsp;type&nbsp;in&nbsp;Tuna&nbsp;Canyon&nbsp;Rd,&nbsp;everything&nbsp;works&nbsp;as&nbsp;expected.

I&nbsp;don't&nbsp;know&nbsp;if&nbsp;this&nbsp;is&nbsp;something&nbsp;you&nbsp;can&nbsp;add&nbsp;to&nbsp;geocoding,&nbsp;or&nbsp;if&nbsp;you&nbsp;have&nbsp;a&nbsp;workaround&nbsp;that&nbsp;will&nbsp;work&nbsp;(I&nbsp;thought&nbsp;about&nbsp;just&nbsp;appending&nbsp;rd&nbsp;to&nbsp;my&nbsp;street&nbsp;name,&nbsp;but&nbsp;I'm&nbsp;unsure&nbsp;if&nbsp;that&nbsp;will&nbsp;affect&nbsp;other&nbsp;things)

&nbsp;

Any&nbsp;help&nbsp;would&nbsp;be&nbsp;appreciated.&nbsp;&nbsp;Thanks!

.Ryan.

---

<div class="post-metadata">

**Author:** ![ThinkGeo](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/thinkgeo/32/25029_2.png) [@ThinkGeo](https://community.thinkgeo.com/u/ThinkGeo)\
**Post date:** [May 2, 2012, 1:19pm UTC](https://community.thinkgeo.com/t/streets-without-suffixs/7262/2 "2012-05-02T13:19:34Z")

</div>

Ryan,&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;think&nbsp;your&nbsp;guess&nbsp;is&nbsp;probably&nbsp;right,&nbsp;Canyon&nbsp;is&nbsp;a&nbsp;street&nbsp;type&nbsp;which&nbsp;has&nbsp;abbr&nbsp;is&nbsp;CYN,&nbsp;if&nbsp;you&nbsp;&nbsp;think&nbsp;your&nbsp;street&nbsp;type&nbsp;won’t&nbsp;be&nbsp;CYN&nbsp;or&nbsp;Canyon,&nbsp;you&nbsp;can&nbsp;use&nbsp;workaround&nbsp;below,&nbsp;you&nbsp;can&nbsp;remove&nbsp;the&nbsp;line&nbsp;“CANYON,CYN”&nbsp;from&nbsp;streettypeabbr.txt,&nbsp;it&nbsp;will&nbsp;return&nbsp;the&nbsp;correct&nbsp;result&nbsp;you&nbsp;can&nbsp;try.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks,&nbsp;  
&nbsp;James

---

<div class="post-metadata">

**Author:** ![Ryan1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://community.thinkgeo.com/u/Ryan1)\
**Post date:** [May 2, 2012, 4:17pm UTC](https://community.thinkgeo.com/t/streets-without-suffixs/7262/3 "2012-05-02T16:17:45Z")

</div>

Hi&nbsp;James,&nbsp;  
&nbsp;&nbsp;  
&nbsp;This&nbsp;will&nbsp;work&nbsp;for&nbsp;the&nbsp;case&nbsp;of&nbsp;canyon…&nbsp;&nbsp;but&nbsp;it&nbsp;is&nbsp;really&nbsp;not&nbsp;a&nbsp;solution&nbsp;that&nbsp;will&nbsp;generically&nbsp;work&nbsp;for&nbsp;a&nbsp;street&nbsp;name&nbsp;that&nbsp;legitimately&nbsp;has&nbsp;a&nbsp;word&nbsp;that&nbsp;could&nbsp;be&nbsp;a&nbsp;suffix&nbsp;as&nbsp;part&nbsp;of&nbsp;its&nbsp;name…&nbsp;in&nbsp;this&nbsp;case,&nbsp;the&nbsp;geocoder&nbsp;will&nbsp;always&nbsp;be&nbsp;broken,&nbsp;not&nbsp;returning&nbsp;the&nbsp;result&nbsp;I&nbsp;am&nbsp;looking&nbsp;for.&nbsp;&nbsp;I&nbsp;need&nbsp;a&nbsp;solution&nbsp;or&nbsp;work&nbsp;around&nbsp;that&nbsp;will&nbsp;provide&nbsp;the&nbsp;correct&nbsp;results&nbsp;for&nbsp;any&nbsp;case&nbsp;where&nbsp;this&nbsp;occurs.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks,&nbsp;  
&nbsp;.Ryan.

---

<div class="post-metadata">

**Author:** ![ThinkGeo](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/thinkgeo/32/25029_2.png) [@ThinkGeo](https://community.thinkgeo.com/u/ThinkGeo)\
**Post date:** [May 3, 2012, 12:12pm UTC](https://community.thinkgeo.com/t/streets-without-suffixs/7262/4 "2012-05-03T12:12:20Z")

</div>

Ryan,&nbsp;  
  
  
  
I&nbsp;don't&nbsp;have&nbsp;good&nbsp;solution&nbsp;for&nbsp;it&nbsp;so&nbsp;far,&nbsp;but&nbsp;if&nbsp;you&nbsp;want&nbsp;to&nbsp;work&nbsp;for&nbsp;all&nbsp;case,&nbsp;you&nbsp;can&nbsp;remove&nbsp;all&nbsp;items&nbsp;in&nbsp;streettypeabbr.txt.&nbsp;This&nbsp;file&nbsp;only&nbsp;use&nbsp;for&nbsp;the&nbsp;case&nbsp;when&nbsp;there&nbsp;are&nbsp;many&nbsp;streets&nbsp;which&nbsp;have&nbsp;the&nbsp;same&nbsp;street&nbsp;name&nbsp;but&nbsp;different&nbsp;type,&nbsp;such&nbsp;as&nbsp;1st&nbsp;road,&nbsp;1st&nbsp;street,&nbsp;1st&nbsp;ave&nbsp;etc.&nbsp;however&nbsp;you&nbsp;don't&nbsp;want&nbsp;to&nbsp;input&nbsp;the&nbsp;type&nbsp;name,&nbsp;it&nbsp;will&nbsp;return&nbsp;all&nbsp;streets&nbsp;which&nbsp;different&nbsp;type&nbsp;name.  
  
  
  
Thanks,&nbsp;  
  
James