addressfield

I am asking for input on the the best practice for having a user enter a location and then having the system geocode that location.

Addressfield + geofield + geocoder
Pros:
Addressfield allows one to enter in each part the location if they know it
It allows a developer to access each piece of the address easily
Integrates with alot of other Drupal modules

Cons:
You cannot have a piece of the address by required and the others not.
For example, I hardly ever know what the zip code of a venue or location is yet if addressfield is required, I have to enter it.

I have installed Geofield and Address Field, and I have created a content type using them.

Then I have created a view with a proximity filter, selecting 'Manually enter point as 'Source of Origin Point'.

It works fine, but I'd like to enter the source point through an AddressField instead lat/long fields.

I have been trying to create a new .inc file but I'm having problems because I have no experience with Views development.

If someone could provide me guidelines about that I will thank him.

Is modifying Geofield module the correct way or I have to create a new module?

I've been racking my brain trying to figure this out....

I have a content type (Retailer) that has multiple addresses (as you would hope one would have :)) that are defined by Addressfield. The idea here is to relate the AddressField to a Product content type where (when creating a new Product) a drop-down box would be available to choose which address the Product is at.

Hi everyone,

I'm looking for some guidance in regards to a current project i'm working on:

Details:

Display businesses for a certain city by using geo data, a proximity slider from a pre-defined center point (supplied by field in the entity, url or defined in the view) and predefined start radius (also defined in the view or by url) - closest distance to center point are displayed first - with distance to center point calculated.

Hi all