<?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 Will Public Notification mailing labels for Occupant and the TaxParcel schema be updated to include fields for Site City, Site State, and Site Zip?  in State &amp; Local Government Questions</title>
    <link>https://community.esri.com/t5/state-local-government-questions/will-public-notification-mailing-labels-for/m-p/134375#M815</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="text-align: left;"&gt;I downloaded the Public Notification files on May 18, 2016.&amp;nbsp; After setting up everything and testing it using the provided sample Naperville Illinois data, I discovered that the labels for "Occupant" pull the values for City ST Zip from the Owner postal mailing City ST Zip fields.&amp;nbsp; This creates incorrect mailing labels.&amp;nbsp; Parcels frequently are owned by people/companies located in other cities.&amp;nbsp;&amp;nbsp; Occupant mailing labels need to have the local SITE City, SITE State, and SITE Zip.&amp;nbsp; The TaxParcel XML schema doesn't have these three fields, but needs to have them.&amp;nbsp; For example, in the Naperville sample data, parcels 0704401022 and 0703301007 are owned by Keystone Property Group with a postal mailing address of 1 Presidential Blv, Bala Cynwyd, PA 19004.&amp;nbsp; The Occupant mailing labels have the local street on W Diehl Rd (that's correct) and should have Naperville IL and a local zip code, but instead the Occupant label has the City ST Zip as:&amp;nbsp; Bala Cynwyd PA 19004.&amp;nbsp; (Additional problem with the Occupant labels: the City is on one line, the State is on another, and the Zip is on yet another.) &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Jun 2016 22:12:17 GMT</pubDate>
    <dc:creator>ValerieJohnson</dc:creator>
    <dc:date>2016-06-13T22:12:17Z</dc:date>
    <item>
      <title>Will Public Notification mailing labels for Occupant and the TaxParcel schema be updated to include fields for Site City, Site State, and Site Zip?</title>
      <link>https://community.esri.com/t5/state-local-government-questions/will-public-notification-mailing-labels-for/m-p/134375#M815</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="text-align: left;"&gt;I downloaded the Public Notification files on May 18, 2016.&amp;nbsp; After setting up everything and testing it using the provided sample Naperville Illinois data, I discovered that the labels for "Occupant" pull the values for City ST Zip from the Owner postal mailing City ST Zip fields.&amp;nbsp; This creates incorrect mailing labels.&amp;nbsp; Parcels frequently are owned by people/companies located in other cities.&amp;nbsp;&amp;nbsp; Occupant mailing labels need to have the local SITE City, SITE State, and SITE Zip.&amp;nbsp; The TaxParcel XML schema doesn't have these three fields, but needs to have them.&amp;nbsp; For example, in the Naperville sample data, parcels 0704401022 and 0703301007 are owned by Keystone Property Group with a postal mailing address of 1 Presidential Blv, Bala Cynwyd, PA 19004.&amp;nbsp; The Occupant mailing labels have the local street on W Diehl Rd (that's correct) and should have Naperville IL and a local zip code, but instead the Occupant label has the City ST Zip as:&amp;nbsp; Bala Cynwyd PA 19004.&amp;nbsp; (Additional problem with the Occupant labels: the City is on one line, the State is on another, and the Zip is on yet another.) &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Jun 2016 22:12:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/state-local-government-questions/will-public-notification-mailing-labels-for/m-p/134375#M815</guid>
      <dc:creator>ValerieJohnson</dc:creator>
      <dc:date>2016-06-13T22:12:17Z</dc:date>
    </item>
  </channel>
</rss>

