You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Eric Jacolin (JIRA)" <ji...@apache.org> on 2007/04/12 09:29:32 UTC
[jira] Created: (OFBIZ-881) GPS on physical addresses
GPS on physical addresses
-------------------------
Key: OFBIZ-881
URL: https://issues.apache.org/jira/browse/OFBIZ-881
Project: OFBiz (The Open for Business Project)
Issue Type: New Feature
Components: party
Reporter: Eric Jacolin
Priority: Minor
I need to store the GPS coordinates of my customers' physical addresses.
The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (OFBIZ-881) GPS on physical addresses
Posted by he...@free.fr.
Are you sure it's a one-one relation between postal adress and GPS coordinates.
if there are two or more buildings in a location, which GPS location do you
intend to store? the location of the entry to the "public" road or the location
of one of the buildings?
Selon "Eric Jacolin (JIRA)" <ji...@apache.org>:
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
>
> I need to store the GPS coordinates of my customers' physical addresses.
>
> The ideal way to do this would be an additional custom field "GPS" to the
> postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not
> seem to be accessible through the create/edit UI forms for postal addresses
> (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well,
> directions.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Eric Jacolin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488288 ]
Eric Jacolin commented on OFBIZ-881:
------------------------------------
True, but:
1. We do not have children "locations" entities for postal addresses, and we probably do not need them
2. The operational meaning of these GPS coordinates will be a matter of business implementation, and need not be reflected in the data model. For example we will have a business rule "the GPS coordinates are those where the customer's widget is located"
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Chris Howe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492547 ]
Chris Howe commented on OFBIZ-881:
----------------------------------
Might this be better modelled as a geoId of type GPS with a fk for this geoId value in the PostalCode entity...if this is decided upon, might it also be better to normalize the PostalCode.variousGeoId into a join table between Geo and PostalCode. Normalizing this might be helpful for data warehousing statistics.
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488341 ]
Jacques Le Roux commented on OFBIZ-881:
---------------------------------------
Eric,
Yes I guess so (perhaps precision is different though). I was just a question I don't know much about that field...
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-881) GPS on physical addresses
Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Le Roux closed OFBIZ-881.
---------------------------------
Resolution: Duplicate
Fix Version/s: SVN trunk
We came to a consensus not yet commited but hopefully "soon" (I have to create data, tests, etc.) see OFBIZ-1923
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
> Fix For: SVN trunk
>
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Chris Howe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492626 ]
Chris Howe commented on OFBIZ-881:
----------------------------------
point 1:
I don't agree with you here. The Geo entity is for "Geographical Identifications". There is no "official" demarcation on what constitutes a geoId record, thus the inclusion of the Geo.geoTypeId (and geoTypeId's relation to GeoType instead of Enum). This makes the entity flexible; flexible enough to handle GPS coordinates if need be (with the addition of additional fields - or better, additional table with primary key of geoId).
point 2:
A postal address does not equal a GPS coordinate. These are two different graphical systems and not actually attributes of one another. The best you can do to model it correctly is with a best fit relationship.
>>You would need to have valid, up-to-date lists for all the countries you're planning to input postal addresses from.
Why is that a difficult proposition? This would most likely be obtained through mashing up with external datasources (NASA World Wind, Google Earth, etc). However points of interest need a place to reside within the the application's data model.
>>Is there even any commercial ERP that achieves this?
I don't know, the sticker shock of commercial ERP kept me from evaluating them in much detail at all. Many OSS project exists soley because a commercial product didn't do something. However that should have no bearing on how to correctly model the data. While the majority of the OFBiz community is interested in ERP, the data model is intended to be generic. Generic in ERP means the ability to reuse data for more than the initial purpose that the data was recorded. In addition, a vast majority of the backwards compatibility issues stem from not modelling data generically. The generic structures usually find their way back in, but it's much more difficult to put it back than it is to have it there in the first place.
As always, this is a 'doocracy' and I have no current need to do in relation to GPS coordinates. I'm simply offering my couple of cents so that someone might be able to easily expand on whatever implementation you come up with (and thus keep as much work as possible supported going forward).
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Hederer Jean-Sébastien (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488282 ]
Hederer Jean-Sébastien commented on OFBIZ-881:
----------------------------------------------
Are you sure it's a one-one relation between postal adress and GPS coordinates.
if there are two or more buildings in a location, which GPS location do you
intend to store? the location of the entry to the "public" road or the location
of one of the buildings?
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "David E. Jones (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492641 ]
David E. Jones commented on OFBIZ-881:
--------------------------------------
This sort of discussion would probably have been better on the dev mailing list.
When looking at GPS coordinates in the past there are various places they could be used. The Geo entity is meant to be an arbitrary Geographic Boundary and does not have to (but certainly can) correspond with legal or governmental boundaries. For Geo records the most common GPS coordinate is the center coordinate.
It might make sense to have a GPS coordinate entity that is separate in order to use it for other things, but it would be best to define what those other things are and how the lat/long coordinates relate to it, then model accordingly.
For a PostalAddress I think it does make sense to have an optional lat/long coordinate pair. It would have to be optional because not all postal addresses correspond to a physical location (though many do).
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Eric Jacolin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492624 ]
Eric Jacolin commented on OFBIZ-881:
------------------------------------
Chris,
point 1:
geoIDs are for discrete lists of "official" codes (eg postcodes). GPS coordinates, though, are continuous values, attributes of postal addresses - so I don't quite get your point.
point 2:
nice in theory, seems quite impossible in practice.
You would need to have valid, up-to-date lists for all the countries you're planning to input postal addresses from.
Is there even any commercial ERP that achieves this?
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "BJ Freeman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543428 ]
BJ Freeman commented on OFBIZ-881:
----------------------------------
http://www.oasis-open.org/committees/ciq/ciq.html#6
has a universal address that can be incorporated.
see
https://issues.apache.org/jira/browse/OFBIZ-100
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Eric Jacolin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488320 ]
Eric Jacolin commented on OFBIZ-881:
------------------------------------
Jacques,
Isn't the coordinate notation independent from the navigation system used?
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Hederer Jean-Sébastien (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488306 ]
Hederer Jean-Sébastien commented on OFBIZ-881:
----------------------------------------------
My remark was just in memory of recent works on the IS for a major company that
delivers gas. GPS coordinates were attached to a building and not to a postal
address in my memory. I think attaching GPS coordinates to postal address will
cover 99,9% of the needs. There can be more than 1 building at one street
address. I have multiple business cases in mind but it's not a major case.
https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488290
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488312 ]
Jacques Le Roux commented on OFBIZ-881:
---------------------------------------
What about Galileo, okay it's future but why not thinking about it right now ?
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by he...@free.fr.
My remark was just in memory of recent works on the IS for a major company that
delivers gas. GPS coordinates were attached to a building and not to a postal
address in my memory. I think attaching GPS coordinates to postal address will
cover 99,9% of the needs. There can be more than 1 building at one street
address. I have multiple business cases in mind but it's not a major case.
Selon "Jacopo Cappellato (JIRA)" <ji...@apache.org>:
>
> [
>
https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488290
> ]
>
> Jacopo Cappellato commented on OFBIZ-881:
> -----------------------------------------
>
> I think it is a good idea, in the postal address you can specify the street
> number of the building, so I don't see issues with more than one buildings.
> And with Google Maps there could be some nice applications of them....
>
>
> > GPS on physical addresses
> > -------------------------
> >
> > Key: OFBIZ-881
> > URL: https://issues.apache.org/jira/browse/OFBIZ-881
> > Project: OFBiz (The Open for Business Project)
> > Issue Type: New Feature
> > Components: party
> > Reporter: Eric Jacolin
> > Priority: Minor
> >
> > I need to store the GPS coordinates of my customers' physical addresses.
> > The ideal way to do this would be an additional custom field "GPS" to the
> postal_address table.
> > Another possibility would be to use the DIRECTIONS field, but this does not
> seem to be accessible through the create/edit UI forms for postal addresses
> (this field does not seem to be used at all?)
> > First solution would be better, because DIRECTIONS should be used for,
> well, directions.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Commented: (OFBIZ-881) GPS on physical addresses
Posted by "Jacopo Cappellato (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488290 ]
Jacopo Cappellato commented on OFBIZ-881:
-----------------------------------------
I think it is a good idea, in the postal address you can specify the street number of the building, so I don't see issues with more than one buildings.
And with Google Maps there could be some nice applications of them....
> GPS on physical addresses
> -------------------------
>
> Key: OFBIZ-881
> URL: https://issues.apache.org/jira/browse/OFBIZ-881
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: Eric Jacolin
> Priority: Minor
>
> I need to store the GPS coordinates of my customers' physical addresses.
> The ideal way to do this would be an additional custom field "GPS" to the postal_address table.
> Another possibility would be to use the DIRECTIONS field, but this does not seem to be accessible through the create/edit UI forms for postal addresses (this field does not seem to be used at all?)
> First solution would be better, because DIRECTIONS should be used for, well, directions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.