Distinguishing projects: Addresses from Location

Dave,

well, i was a Location module developer (800+ commits), but the team and i had some differences about the project, so i forked. The differences are:

* Addresses focus primarily on physical addresses. Location has this AND geocoding. Its important when you run a e-Commerce site or other site that only need address and you dont want to have download updates to maintain geocoding and mapping.
* Addresses has an API that allows other modules to add new address's fields, like longitude/latitude, map, phone. Location doesnt.
* Addresses has both user and node/cck addresses. Location doesnt.
* Addresses has (only and by design) Drupal 6 code. Location has a D5 and will be ported in the future to D6.
* Addresses has 65.88 KB. Locations has 1.63 MB.
* Addresses export ALL data to Views. Location doesnt.

* Addresses DOESNT have (yet) any geocoding and mapping integration. I will do this till next year. If you need today, use Location. If you need today AND in a D6 site, there is no solution!
* Location is much more used than Addresses and has much more related modules.

regards,

massa

Automatically closed -- issue fixed for two weeks with no activity.

I guess an issue queue is not the place to do this, but tnx brmassa for this info, I had exactly the same problem (go for custom cck fields, addresses or location) and your post clarified a lot. I already found out that location while having the gmap functionality lacks good views support for each field separately.

I do however need the gmap functionality, so looking forward to your gmap integration or maybe be able to work together with location so the location's gmap marker can pick up on the addresses address fields rather then having to repeat them for the location module.

Tnx,

HnLn

How have location's recent updates affected the list in #1?

Thanks brmassa for a _simple_ address module. Like Aren, I'd be interested to hear the current status with regards to the comparison!

Updating to current version.