<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Does anyone use a fixed width format for your addressing? in 911 GIS Questions</title>
    <link>https://community.esri.com/t5/911-gis-questions/does-anyone-use-a-fixed-width-format-for-your/m-p/839763#M528</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chris offers sage advice. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have to ask: are storing address points and are you geocoding against them?&amp;nbsp; I do nothing but geocoding for 9-1-1 and for that application parsing is the only way to go.&amp;nbsp; Also, it is my understanding that the latest iteration of ESRI locators do not perform addressing standardization as they used (ie 9.3 locators) so that my influence your decision as well; it makes a big difference if you will be passing on geocoded information to outside applications as is the case with some 9-1-1 Computer Aided Dispatch (the &lt;EM&gt;other&lt;/EM&gt; CAD) software packages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So back to what Chris said; it depends on how you are using the data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Aug 2015 23:15:08 GMT</pubDate>
    <dc:creator>JoeBorgione</dc:creator>
    <dc:date>2015-08-14T23:15:08Z</dc:date>
    <item>
      <title>Does anyone use a fixed width format for your addressing?</title>
      <link>https://community.esri.com/t5/911-gis-questions/does-anyone-use-a-fixed-width-format-for-your/m-p/839761#M526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I curious to know what is the benefit of that format compare to the parsed format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fixed format :&lt;/P&gt;&lt;TABLE border="1" class="jiveBorder" style="border: 1px solid rgb(198, 198, 198); width: 100%;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH style="text-align: left; background-color: #f2f2f2; color: #505050; padding: 6px;" valign="middle"&gt;&lt;STRONG&gt;Address&lt;/STRONG&gt;&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 6px;"&gt;HAVENBROOK DR 909&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 6px;"&gt;J R HAWKINS RD 5301&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 6px;"&gt;MARQUIS CIR W 2705&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parsed format:&lt;/P&gt;&lt;TABLE border="1" class="jiveBorder" style="border: 1px solid rgb(198, 198, 198); width: 100%;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH style="text-align: left; background-color: #f2f2f2; color: #505050; padding: 6px;" valign="middle"&gt;&lt;STRONG&gt;Number&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: left; background-color: #f2f2f2; color: #505050; padding: 6px;" valign="middle"&gt;&lt;STRONG&gt;Dir&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: left; background-color: #f2f2f2; color: #505050; padding: 6px;" valign="middle"&gt;&lt;STRONG&gt;Street&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: left; background-color: #f2f2f2; color: #505050; padding: 6px;" valign="middle"&gt;&lt;STRONG&gt;Type&lt;/STRONG&gt;&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 6px;"&gt;909&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;HAVENBROOK&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;DR&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 6px;"&gt;5301&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;J R HAWKINS&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;RD&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 6px;"&gt;2705&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;W&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;MARQUIS&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;CIR&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 6px;"&gt;&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;&lt;/TD&gt;&lt;TD style="padding: 6px;"&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2015 15:29:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/911-gis-questions/does-anyone-use-a-fixed-width-format-for-your/m-p/839761#M526</guid>
      <dc:creator>SarawutTangadunrat</dc:creator>
      <dc:date>2015-08-14T15:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: Does anyone use a fixed width format for your addressing?</title>
      <link>https://community.esri.com/t5/911-gis-questions/does-anyone-use-a-fixed-width-format-for-your/m-p/839762#M527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As far as best practices, addresses are messy. It really depends on how you're using them... The fixed format provides easier editing - if you're just storing addresses to print on letters, or something, this would probably be ok. It keeps the table thinner/smaller, too, depending on the datatype of the field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The parsed format would make it easier to analyze and search; additionally, you can apply fk constraints and indexing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are dealing with international addresses, that's another ball of wax - I would check-out &lt;A href="http://www.endswithsaurus.com/2009/07/lesson-in-address-storage.html" title="http://www.endswithsaurus.com/2009/07/lesson-in-address-storage.html"&gt;EndsWithSaurus...: A lesson in address storage&lt;/A&gt;&amp;nbsp; if it applies to you. Here's some info on US addresses - &lt;A href="http://pe.usps.gov/text/pub28/welcome.htm" title="http://pe.usps.gov/text/pub28/welcome.htm"&gt;http://pe.usps.gov/text/pub28/welcome.htm&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additional info on best practices:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://stackoverflow.com/questions/310540/best-practices-for-storing-postal-addresses-in-a-database-rdbms" title="http://stackoverflow.com/questions/310540/best-practices-for-storing-postal-addresses-in-a-database-rdbms"&gt;http://stackoverflow.com/questions/310540/best-practices-for-storing-postal-addresses-in-a-database-rdbms&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One thing is for sure, make sure you carefully choose how you architect your db now, otherwise you may be hurting later.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2015 20:32:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/911-gis-questions/does-anyone-use-a-fixed-width-format-for-your/m-p/839762#M527</guid>
      <dc:creator>ChrisSmith7</dc:creator>
      <dc:date>2015-08-14T20:32:17Z</dc:date>
    </item>
    <item>
      <title>Re: Does anyone use a fixed width format for your addressing?</title>
      <link>https://community.esri.com/t5/911-gis-questions/does-anyone-use-a-fixed-width-format-for-your/m-p/839763#M528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chris offers sage advice. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have to ask: are storing address points and are you geocoding against them?&amp;nbsp; I do nothing but geocoding for 9-1-1 and for that application parsing is the only way to go.&amp;nbsp; Also, it is my understanding that the latest iteration of ESRI locators do not perform addressing standardization as they used (ie 9.3 locators) so that my influence your decision as well; it makes a big difference if you will be passing on geocoded information to outside applications as is the case with some 9-1-1 Computer Aided Dispatch (the &lt;EM&gt;other&lt;/EM&gt; CAD) software packages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So back to what Chris said; it depends on how you are using the data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2015 23:15:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/911-gis-questions/does-anyone-use-a-fixed-width-format-for-your/m-p/839763#M528</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2015-08-14T23:15:08Z</dc:date>
    </item>
  </channel>
</rss>

