Hi Groza,
Good quesiton, it's rather GeoAssoc definitions that are reversed.
This was done 13 years ago by https://svn.apache.org/viewvc?view=revision&revision=1162940 (text changed
<https://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/data/DemoOrganizationData.xml?r1=1170061&r2=1170060&pathrev=1170061>)
For the data I would rather trust GeoData_US.xml which was the 1st created file
(pre-Apache era between 2001 and 2006)
If you look at https://svn.apache.org/viewvc?view=revision&revision=1170061 (text changed
<https://svn.apache.org/viewvc/ofbiz/trunk/framework/common/data/GeoData_US.xml?r1=1170061&r2=1170060&pathrev=1170061>)
You will see
<GeoAssoc geoId="USA" geoIdTo="AK" geoAssocTypeId="REGIONS"/>
Also
<GeoAssoc geoAssocTypeId="REGIONS" geoId="FRA" geoIdTo="FR-PAC"/>
was imported David "Initial OFBiz import from revision 7923 of the old svn.ofbiz.org
SVN repository."
byhttps://svn.apache.org/viewvc?view=revision&revision=418498
This region did not change since.
So I suggest to fix theGeoAssoc definitions. Actually, it's logical to have a
relation from country to regions.
HTH
Jacques
Le 10/09/2024 à 13:34, Groza Danut a écrit :
Hi all,
As stated in the entitymodel of GeoAssoc:
geoId - The enclosed geo
geoIdTo - The enclosing geo
When I look at an example(framework/common/data/GeoData_FR.xml), I see the
following data:
<GeoAssoc geoAssocTypeId="REGIONS" geoId="FRA" geoIdTo="FR-ARA"/>
<GeoAssoc geoAssocTypeId="COUNTY_SEAT" geoId="FR-PTO95" geoIdTo="FR-95"/>
Basically the id's are reversed.
- For REGIONS the geoId is the country(enclosing geo), and the geoIdTo is
the region
- For COUNTY_SEAT the geoId is the city(enclosed geo), and the geoIdTo is
the county
Is that on purpose?