[
https://issues.apache.org/jira/browse/OFBIZ-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624079#action_12624079
]
David E. Jones commented on OFBIZ-1923:
---------------------------------------
For the Container entity: a Facility may not move but a Container typically
will. Whatever is done, the geoPointId should not be on the Container itself. I
would recommend just not worrying about it at this point because Containers
aren't used much in OFBiz yet. Also, when a Container is in a Facility you can
look up the geoPointId of the Facility. Otherwise, you would need a
ContainerGeoPoint entity to keep track of a series of points over time like the
others.
On a side note, wasn't a big point of all of this to have a lat/long on a
postal address? I don't see anything like that in this data model patch, so I'm
not sure what you're thinking along those lines. I'd recommend adding a
geoPointId to the PostalAddress entity (and not the ContactMech entity as this
does not apply to all ContactMechs).
-David
> Add geolocation to data model.
> ------------------------------
>
> Key: OFBIZ-1923
> URL: https://issues.apache.org/jira/browse/OFBIZ-1923
> Project: OFBiz
> Issue Type: New Feature
> Components: accounting, framework, party, product
> Affects Versions: SVN trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Fix For: SVN trunk
>
> Attachments: GeopointDataModel.patch, GeopointDataModel.patch,
> GeopointDataModel.patch
>
>
> The attached patch is enhancing the current data model following last David's
> suggestion after some exchanges on dev ML. I just added a geoPointId to
> Container.
> I finally used float for latitude, longitude and elevation, instead of
> creating a new degree field type (numeric 18,6).
> Any comments are welcome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
