So I had an interesting scenario pop up today as I was reviewing and preparing our city boundary changes to the Census.
So when I was working through the "data cleaning" process, I was introduced to an interesting problem.
The BAS review requires to have a matching column of values between certain fields they have in their data. This lead to the discovery, after using Create Changes within their toolbox you download, that my values for their field titled: NAMELSAD are just my values of MUNI, but not exactly the same.
Hence, an opportunity was born to code using python within the Field Calculator.
What I did was say that my newly created column was equal to
!MUNI!.title()+" city" #(don't forget the space b4 city, it's important)
I appended to this topic a Snip and Sketch of the code in the Field Calculator, and I was able to quickly and easily solve one problem that helped me to finish a lot of the work more quickly. For the record, I chose MUNI_TIGER as my field name because their mapping service has the word Tiger in it...when in Rome. Ah I love mapping puns.
Hope this helps and thank you for reading!
Thanks for sharing Gabe!
© 2022 Kansas Association of Mappers | firstname.lastname@example.org | PO Box 3788 | Lawrence, KS 66046-0788 | Site Disclaimer