I'm with you - i don't see Location Custom Fields as being particularly useful. I can see how it might be useful if you think a Tech might go look at the Location list and need to know something unique about a particular Location, but it does seem like it would be much more helpful if you could (optionally) display it elsewhere.
I really don't understand the point of attachments for Locations, though.
I agree. I would be better if the custom field would work with a Room (instead of a Location). We would then use that to designate Rooms with Asbestos. That way our Operations Dept would use our Help Desk. IF the Custom field would be displayed on a Ticket, the Operations crew would know there was Asbestos in the Ceiling, or Wall, or Floor tile. We would use a Custom Field for more than that as well if the custom field would be displayed on the Ticket, and could be narrowed to a Room in a location.
Custom field for only the Location is not helpful. Custom Field for a Room within a Location would be very beneficial (too us).
We use the location custom fields to define numbers assigned to different locations, those numbers can then display in tickets with that location. We depend on that number for a bunch of things so it works for us. You could use them for different TYPES of locations too, such as which stores are Superstores and which are Neighborhood stores (if for example you are Walmart using it). Really any information you'd want to track you could. The important thing to remember is that you can use action rules, tasks, approval processes and a number of other features to pull the data from location custom fields, so there are a lot of ways to use the data within the UI.