Evil
Evil would be "Lets see where Jim in marketing has been going...." *punches in two locations (Jim's home and work) to pull up all UIDs that fit both criteria* ... *crunch crunch crunch* .... Computer dumps out the obvious handful or less of UIDs that have sipped both work and home WiFi/cell towers on a frequent basis... Ok, now pipe that UID into a mapper to show plots of where he's been. Oh look, the neighborhood strip club on Tuesdays....now where's his number. Perhaps he's willing to give us a pint on Tuesdays to keep it from the wife. Which is likely this other UID....
What is it REALLY being used for?
Phone: I'm -70db for wifi: ActionTek MAC: 00-03-04-94-90-30 (yes, fake MAC), Where am I?
GoogleServer: Likely somewhere near 37.0625,-95.677068
Phone to User: You are HERE --->
All without having to GPS (sucks battery) or actually works (if indoors or otherwise blocked). WiFi wardriving is quite low power since your antenna is technically only in receiving mode. It's sending signals that drains power. If this information is cached in advance, your phone wouldn't even have to talk to a googleserver (which is what Apple does).
As for the UID bit, it's likely to prevent people from crap-flooding their records. If they get sprayed with crap data from a single UID, they know they can just purge all data from that UID from the system. If they get sprayed with crap data from randomly-generated UIDs, they know they can disregard the RNG UIDs since they don't belong to an activated device. It's a quality assurance thing. Unfortunately, they don't purge the UID after X days/weeks/months, which is how I would have implemented the system. "Sure, we collect UIDs for data-integrity purposes, but we sanitize even those after 3 months when we have validated the quality of the associated data."