territory inventorires all cuttings (administrative, postal) for a country, with theirs relations
(country, ID, parent ID) can define a territory with (level, code and others)-properties
the built-in procedure has to follow an UP-DOWN way
first, create the country, and next go down through the hierarchy (level by level)
for France, the lowest level is equivalent to a postal zone, combining zipcode and municipality (well-known as ZA, ie 'Zone Adresse')
the geometry are supplied by IGN for administrative cuttings
we have to calculate the postal side, beginning by ZA, and next benefitting of PostGIS union operation for supra cuttings
BUT id_territory has to be invariant, due to attachment of addresses : changes must be done by updates, especially the lowest level (ZA)
this ticket is too ambitious from scratch!
back to COM_CP based level (because of unknown old municipalities, from ZA-id)
need code review:
territory inventorires all cuttings (administrative, postal) for a country, with theirs relations (country, ID, parent ID) can define a territory with (level, code and others)-properties
the built-in procedure has to follow an UP-DOWN way first, create the country, and next go down through the hierarchy (level by level) for France, the lowest level is equivalent to a postal zone, combining zipcode and municipality (well-known as ZA, ie 'Zone Adresse')
the geometry are supplied by IGN for administrative cuttings we have to calculate the postal side, beginning by ZA, and next benefitting of PostGIS union operation for supra cuttings
BUT id_territory has to be invariant, due to attachment of addresses : changes must be done by updates, especially the lowest level (ZA)
this ticket is too ambitious from scratch!