Good point Tristan! - I wanted the Province_Tbl to be as slim as possible, so anything there can be more than one of, in a province, should indeed go into the features table.
The Features_Tbl is supposed to contain all the stuff you can stick in a province. It will probably grow to have several fields with special values, but since each type of feature will probably have different values, my initial idea was to reuse the same fields for the same "kinds" of values to save fields.
Using a feature will require looking at the Type first, before trying to apply the processing rules. - Several smaller, dedicated tables could make for easier rules processing, but would give us a forest of tables.