Somehow I never got a notification for this post, so I apologies for the late reply! I'm assuming you've solved it since then, but in case you haven't, and for anyone else who stumbles on this later via Google search:
Field Name vs Field Alias
What you want in that list are the field names, because that's what SearchCursor is expecting.
Multiple Photo Fields:
This has a few components that would likely need changing, but for the most part, it'll just work. The original could also just be run once for every photo field, if you have the time. But automation is more fun. Since I can only see Field Aliases in your screenshot, I'm going to just give them placeholder names for demonstration purposes.
Let's say the field names for those fields in the screenshot are PreInstallPhoto, NewNumberPhoto, NewRadioPhoto, PostInstallPhoto, PostInstallRadioPhoto, GallonPhoto:
First, add the new values to fieldLst in Lines 14–15:
fieldLst = ['Address',
'PreInstallPhoto',
'NewNumberPhoto',
'NewRadioPhoto',
'PostInstallPhoto',
'PostInstallRadioPhoto',
'GallonPhoto'
]
Next, you need to make sure the SearchCursor can unpack them all in the same order. (Note: I moved Address to be first just to keep the photos together. What order you choose doesn't matter, so long as it's the same in both of these places.) The part you need to change would be Line 21:
for address, preInstall, newNumber, newRadio, postInstall, postRadio, gallon in cursor:
In your example, you've broken the address up into subfolders. I'm not going to go into that here for space reasons, but it can definitely be done. You'll need to add some code around Line 22 that reads the address and breaks it up into House Number & the rest of the address. This can be a little tricky if your data isn't consistent. Your screenshot shows a space between them. If that's always the first space, then you can just break it there. If not, things rapidly get complicated.
Beyond that, the folder part doesn't change, since the photos are all getting stored together. But we'll need to handle each of the filenames separately. There's a few ways to handle this, but the simplest is probably to pull this part of the script out to a separate function. Then you don't have to write it a bunch of times. This function needs to go above anything that wants to call it. I recommend inserting it between the library imports and your tool inputs. This means inserting this at around Line 3 of the original script.
Also, since you mention that some photo fields might be NULL, I added a bit at the top. Line 3 below checks if there's an actual NULL, and just bails out of the function if there is.
Since it's a string field, I also added a quick check at Lines 5–6 that's looking for a "fake NULL". This would be a field where there's just an empty string or a bunch of spaces, but no actual URL. That's a problem you can easily run into, if your dataset is set up to not allow NULLs—and sometimes even if you do allow them!
Lastly, since we added these "bail out" parts by returning something, the whole script should probably also return something upon successful completion. I just added a return None, since we don't really need it to return anything.
def ExportPhoto(folder, url):
# First, make sure you actually have a URL:
if url is None:
return None
elif isinstance(url, str):
if url = ' ' * len(url):
return None
# Next, let's get the filename of the photo from that URL
# Also, lots of urls need percent-encoded characters that will cause
# us problems, like a space becoming %20. unquote fixes that for us.
parsedURL = urllib.parse.urlparse(url)
photoName = urllib.parse.unquote(pathlib.Path(parsedURL.path).name)
# Then, we need the path to where that photo is going to be saved
photoPath = folder / photoName
# Finally, we write that photo to file
with open(photoPath, 'rb') as img:
# This downloads the photo from the URL so we can write it
with urllib.request.urlopen(url) as imgURL:
# And this actually CREATES the photo file
img.write(imgURL.read())
# Since part of the function returns a value, ALL of the function should,
# for consistency and user-friendliness.
return None
Since we're handling this in a separate function, now, you should remove the code from Lines 28–42 of the original code. Instead, we'll need to call that function for each of your photos. This goes in where you just removed the other code, so starting at Line 28.
ExportPhoto(addressDir, preInstall)
ExportPhoto(addressDir, newNumber)
ExportPhoto(addressDir, newRadio)
ExportPhoto(addressDir, postInstall)
ExportPhoto(addressDir, postRadio)
ExportPhoto(addressDir, gallon)
Lastly, your cleanup on Line 47 should match your unpacking on Line 21. So make sure your variables all match both places.
