[
https://issues.apache.org/jira/browse/OFBIZ-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623823#action_12623823
]
David E. Jones commented on OFBIZ-1923:
---------------------------------------
For the PartyGeoPoint and FixedAssetGeoPoint entities they should have a type
one relationship to each other record they refer to, in this case both the
Party entity (which you have) and the GeoPoint entity (which you don't have).
On a side note: this is why I'm a little picky about who makes data model
changes... they aren't too complex but for anyone that hasn't done them a fair
amount it is easy to miss things, and once the entities are used becomes
difficult to fix. In any case, these are looking pretty good, so great job on
your efforts here.
> 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
>
>
> 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.
