Merging of OffsetRequirements (aka OffsetTriggers) and Offsets tables

[rukayaj]

We want to record:

1. What the permit stipulated that the developer had to do
2. What the developer actually did (what was actually implemented)

I think we should try having this all in one table.

[rukayaj]

Other things discussed:

• Location description should stay with the Development table (as it's common to each development and doesn't change with each permit)
  • We need to change the offset ratio and is offset met/not met based on the first comment/issue up there ^^

[rukayaj]

So we're now no longer recording the actual biodiversity that was lost? No surely we still need to measure that. Otherwise we won't know that 500 of these protected species were destroyed, or 10 ha of this endangered ecosystem was destroyed because all the permit stipulated was e.g. that they need to provide R20k financial compensation.

[rukayaj]

Ok I think this is covered now. We now have one single table which records details about Offsets (including the offset polygon and info such as if the offset is met or not). Each offset links to its relevant permit. Multiple implementation times can be associated with each offset.

I have added a "Biodiversity" class, and two subclasses: "BiodiversityLoss" and "BiodiversityGain". Each biodiversity gain links to an offset, each biodiversity loss links to a development.