Stuart Fraser

I support addition of 1360 - agriculture - crops 1370 - livestock I support changing the current "Forestry, Unknown" to "Forestry" rather than "forestry, general".

As @johcarter says - the most straightforward and highest priority would be to add a field e.g. 'numOccupants' so that number of occupants can be assigned to a location. Models...

@aiste-kalinauskaite you make a great point -- The field NumberOfEmployees does the same thing, but the meaning is clearer with 'occupants' because most modelling of human impact outside of the...

Yes that would be a good first step, though I think the additions should follow not too far behind. Several research projects looking to make use of additional demographic factors...

Initial Proposal for review contained in the attached xlsx., comprising the addition of an occupantPeriod field in Location table to support NumOccupants, accompanying code values for occupantPeriod, and a new...

Small but crucial update in this version 2: additional row UID required. [HumanImpact_OEDAdditions_Sept2021_v2.xlsx](https://github.com/OasisLMF/OpenDataStandards/files/7133761/HumanImpact_OEDAdditions_Sept2021_v2.xlsx)

I think 'OccupantPeriod' should be in the same file as 'NumOccupants' because then you can define the number of occupants, and whether they are daytime employees or night-time residents with...

> Could you please clarify why there is a need to have two files rather than putting all fields in Loc file? > Currently any OED field if it's not...

> After more discussion, it makes sense to change the thinking around what OED is. OED should cover "all" exposure data and so can include several input files. i.e the...

Day/night would be the main use case yes. Most analysis uses nighttime population, given by census statistics. Potential for further description is useful longer term - have previously used data...