If there's an active attribute join, normally the field names end up with a qualifier to say which table/feature class they come from.
If you look at Line 32 and Line 33, they each show the qualified names, where the bit before the dot is the source and the bit after the dot is the field name. Given we're working with joined data, this is as I'd expect.
What's weird here is your printout from Lines 25–28, though. Based on the documentation, I thought field.name would produce the full qualified name and field.baseName would provide the unqualified name. Based on your printout, that's either not correct, or you somehow don't have a join active at that point in the code.
The other issue I see is that the Near_X field referenced in Line 33 doesn't appear in your printout—with or without the qualified prefix. Line 32 is similar, but not entirely. Compare the field name there against the lats entry in your printout. The former has a dot separating the source and the field name; the latter has an underscore.
To troubleshoot this, I would recommend temporarily removing the Calculate_Field portion and anything after it from your script—but remember to save a copy of that code elsewhere, though!
Then, manually open the attribute table or fields view and see what field names (not aliases) are being displayed.
You could also try adding a printout before the join, as well, and comparing the two printout results.
------------------------------
M Reed
"The pessimist may be right oftener than the optimist, but the optimist has more fun, and neither can stop the march of events anyhow." — Lazarus Long, in Time Enough for Love, by Robert A. Heinlein
If this post or another helped you out, please consider giving the post(s) a Kudo or marking them as the Solution. ESRI Staff use both of these features to help keep track of posts on these forums.
