Alternative configuration method

I'm really looking forward to using this module, but the current implementation method is problematic for my (and I'm assuming probably others) needs.

I have a user base of about 30 farms and growing. Each farm would like to show the correct weather for their location on their page.

Right now, to make this work - I would need to:

• Create system-wide display groups (e.g, standard & metric)
• Create a new display for each farm's location
• Configure each newly created block to only show on the correct user's page

This means I would currently need 30 displays, and I would have to configure 30 blocks. This is difficult because I would need to manually configure the weather display for each user myself as they don't have access to create new displays or to place blocks. It would also cause significant crowding of the block placement popup on the block config page.

Would it be possible to set up either of the following implementation methods instead:

Weather as a field:

• Create system-wide display groups (e.g, standard & metric)
• Add weather field to content type or user config
• User/content creator chooses display group
• User/content creator chooses Country, Place, and Displayed name - same as when creating a new display for a system-wide display group
• Weather (block) is displayed via the field

Weather via views using geofield/address field

• Add geofield or address field to content type or user config (standard/metric, other settings as well?)
• Create "weather" view to show weather info using geolocation or address field for location
• Pass field info into view via contextual filter
• Place view as block on content/user page
• Weather info is displayed via the view using contextual filter for nid, uid, etc.