This makes sense indeed Roland. I vote for since I will certainly need to add some other data. This is why I thought about
extend-entity in 1st place.
I can't see any related entities yet, but this could maybe happen in future.
Waiting for other opinions...
Another point I'm interested in : is there a mean/field to relate a duplicated
order with the original one ?
Jacques
From: "RolandH" <[EMAIL PROTECTED]>
Hi Jacques,
why not a new entity, which can be connected to PostalAddress and maybe in the
future others?
Another questions comes to mind here: more than one Entity may be at the same
LatLong point.
And you're able to save additional data inside the new entity:
datasource (may be intersting when using more than one geocoder: google, yahoo)
valid from/until
just another 2 cents,
Roland
Jacques Le Roux wrote:
Hi Rob,
I tested with some commercial addresses I will need to locate (here in France) : results are not good enough... Morevover the
company I will do that for is already using (lat., long.). So I will really need them. So my question to the community remains :
PostalAddress or extend-entity ?
Thanks
Jacques
Jacques
From: "Jacques Le Roux" <[EMAIL PROTECTED]>
Thanks Rob,
This is an interesting information, I'm just discovering Google Map API and
related...
Jacques
From: "Rob Schapper" <[EMAIL PROTECTED]>
Jacques,
Wouldn't it make more sense to use the google geocode methods to get the lat/long from an address rather then store that info
in ofbiz?
Rob
On Jun 27, 2008, at 3:59 PM, Jacques Le Roux wrote:
Hi Chris,
It was a long time :o), thanks for comments
I need them to use with Google Map. To do something like
http://code.google.com/apis/maps/documentation/examples/marker-simple.html
you can see there map.setCenter(new GLatLng(37.4419, -122.1419), 13);
Hopefully I will be able to do something general enough to be reusable (should not be too hard, the tough part is already
done by
Google)
Jacques
From: "Chris Howe" <[EMAIL PROTECTED]>
I wasn't going to comment on this because I don't think I have the time available to see the discussion through to the end,
but
after reading David's "Data Model Changes Post", I'll toss my two cents about
this.
What are you wanting to ultimately do with Lat/Long? From my experience with GeoServer earlier this year, storing Lat/Long
values
is rather inconvenient when doing computations and placing points (and polygons) on Maps. It was much more convenient to
store
these points in the manner prescribed by postgis and using the methods that are provided in those kinds of packages. Also,
as far
as data modeling, it's somewhat innacurate (although depending on your application, possibly within acceptable bounds) to
refer to
an address as a point that has the specificity you'd be assigning.
Jacques Le Roux <[EMAIL PROTECTED]> wrote: Hi,
I will need to add Latitude and Longitude fields in PostalAdress. Could this
be a change commited ?
I will also need to add a type PHONE_HOTLINE in ContactMechPurposeType.
Else, of course I will use
Thanks
Jacques
