<?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 Proper Case Label exceptions in Mapping Questions</title>
    <link>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138401#M1589</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have created auto labels expression for proper case for an ArcMap, Data Driven Page document. I noticed there are some exceptions where the proper case label is not accurate (e.g. Crete-monee Rd, I 355 Nb). It has been awhile since I programmed. I assume I need to add an if-else if-else loop within the For loop (see attachment) to identify the hyphen names and the highway names to rule them out either in separate loops or as exceptions to the remaining names. I could also put those two name types in separate classes of labels to make sure they appear correctly (e.g. FULLNAME like '*-*'). Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Oct 2016 16:54:40 GMT</pubDate>
    <dc:creator>GregJohnson</dc:creator>
    <dc:date>2016-10-24T16:54:40Z</dc:date>
    <item>
      <title>Proper Case Label exceptions</title>
      <link>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138401#M1589</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have created auto labels expression for proper case for an ArcMap, Data Driven Page document. I noticed there are some exceptions where the proper case label is not accurate (e.g. Crete-monee Rd, I 355 Nb). It has been awhile since I programmed. I assume I need to add an if-else if-else loop within the For loop (see attachment) to identify the hyphen names and the highway names to rule them out either in separate loops or as exceptions to the remaining names. I could also put those two name types in separate classes of labels to make sure they appear correctly (e.g. FULLNAME like '*-*'). Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Oct 2016 16:54:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138401#M1589</guid>
      <dc:creator>GregJohnson</dc:creator>
      <dc:date>2016-10-24T16:54:40Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Case Label exceptions</title>
      <link>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138402#M1590</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you're on the right track. Does your data only have a FULLNAME attribute or are the address components broken out in other attributes?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Oct 2016 18:46:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138402#M1590</guid>
      <dc:creator>MicahBabinski</dc:creator>
      <dc:date>2016-10-24T18:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Case Label exceptions</title>
      <link>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138403#M1591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Only the FULLNAME attribute.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Oct 2016 18:57:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138403#M1591</guid>
      <dc:creator>GregJohnson</dc:creator>
      <dc:date>2016-10-24T18:57:35Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Case Label exceptions</title>
      <link>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138404#M1592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't know what language applies to labelling but in fields if you use the python parser youy should be able to play with this idea&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE class="lia-code-sample line-numbers language-none"&gt;&lt;CODE&gt;&lt;SPAN class="operator token"&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;SPAN class="operator token"&gt;&amp;gt;&lt;/SPAN&gt; &lt;SPAN class="keyword token"&gt;import&lt;/SPAN&gt; string
&lt;SPAN class="operator token"&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;SPAN class="operator token"&gt;&amp;gt;&lt;/SPAN&gt; z &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; &lt;SPAN class="string token"&gt;'Crete-monee Rd, I 355 Nb'&lt;/SPAN&gt;
&lt;SPAN class="operator token"&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;SPAN class="operator token"&gt;&amp;gt;&lt;/SPAN&gt; zz &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; z&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;casefold&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;
&lt;SPAN class="operator token"&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;SPAN class="operator token"&gt;&amp;gt;&lt;/SPAN&gt; zz
&lt;SPAN class="string token"&gt;'crete-monee rd, i 355 nb'&lt;/SPAN&gt;
&lt;SPAN class="operator token"&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;SPAN class="operator token"&gt;&amp;gt;&lt;/SPAN&gt;
&lt;SPAN class="operator token"&gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;SPAN class="operator token"&gt;&amp;gt;&lt;/SPAN&gt; string&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;capwords&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;zz&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; sep&lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;" "&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;
&lt;SPAN class="string token"&gt;'Crete-monee Rd, I 355 Nb'&lt;/SPAN&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;If I am not mistaken the string module is already imported in the field calculator, if you &amp;nbsp;set the parser to python. &amp;nbsp;I ddon't if string.capwords is in there, but it might be worth a look&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Dec 2021 07:40:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138404#M1592</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2021-12-11T07:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Case Label exceptions</title>
      <link>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138405#M1593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can use&lt;A href="http://desktop.arcgis.com/en/arcmap/latest/map/working-with-text/about-building-label-expressions.htm"&gt; python in labelling&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Oct 2016 16:36:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138405#M1593</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2016-10-25T16:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: Proper Case Label exceptions</title>
      <link>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138406#M1594</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Greg,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That makes it tricky. Correcting the casing on the source data might be more worthwhile in the long term, assuming you have control over the data and can do that. Either way, you'll need to parse the components of the FULLNAME value.&amp;nbsp;Are these intersections? I was think that 'Nb' meant New Brunswick but I think it means Northbound.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming that's the case, your FULLNAME components would be (I think):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Street Name ("Crete-Monee")&lt;/P&gt;&lt;P&gt;Street Type ("Rd")&lt;/P&gt;&lt;P&gt;Highway Name ("I 355")&lt;/P&gt;&lt;P&gt;Highway Direction ("NB")&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is that correct? Assuming your data is formatted consistently with the example you gave, it would be possible to parse those components and correct them in the source data. You could use an arcpy.da.Update cursor pretty effectively to do that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some questions to consider:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you want a hyphen for interstates?&lt;/P&gt;&lt;P&gt;Are there other types of highways (non-interstates) in the data?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Oct 2016 19:20:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/mapping-questions/proper-case-label-exceptions/m-p/138406#M1594</guid>
      <dc:creator>MicahBabinski</dc:creator>
      <dc:date>2016-10-25T19:20:44Z</dc:date>
    </item>
  </channel>
</rss>

