Skip to content

Commit

Permalink
Simplified from list of lists to list of objects
Browse files Browse the repository at this point in the history
  • Loading branch information
@doorleyr
doorleyr committed Apr 23, 2020
1 parent af3e13b commit 0fa176a
Showing 1 changed file with 13 additions and 29 deletions.
42 changes: 13 additions & 29 deletions docs/md/Land-Use-Types.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Each type consists of a dictionary of attributes. The mnimum attributes contined

## Attribute Examples

A single grid-cell may contain multiple LBCS and multiple NAICS on different floors or even on the same floor. Therefore, the value of each attribute is formatted as a list of lists. The upper-most list represents groups of floors. Each lower-level list represents the mix of uses within that floor-group. For example, the following represents the NAICS attribute for a grid cell where:
A single grid-cell may contain multiple LBCS and multiple NAICS on different floors or even on the same floor. Therefore, the value of each attribute is formatted as a list of objects. The object in the list represents a grouping of floors starting with the lower-most floors. Each object contains the mix of uses within that floor-group. For example, the following represents the NAICS attribute for a grid cell where:
- the lower 30% of floors are devoted to a mix of "541310" (architectural services) and "541330" (engineering services).
- the upper 70% of floors and devoted to a mix of "23" (Construction), "42" (Wholesale) and "61" (Education).

Expand All @@ -17,29 +17,18 @@ A single grid-cell may contain multiple LBCS and multiple NAICS on different flo
"P": 0.3,
"use": [
{
"P": 0.5,
"use": "541310"
},
{
"P": 0.5,
"use": "541330"
"0.5": "541310",
"0.5": "541330"
}
]
},
{
"P": 0.7,
"use": [
{
"P": 0.3,
"use": "23"
},
{
"P": 0.4,
"use": "42"
},
{
"P": 0.3,
"use": "61"
"0.3": "23",
"0.4": "42",
"0.3": "61"
}
]
}
Expand All @@ -49,7 +38,7 @@ A single grid-cell may contain multiple LBCS and multiple NAICS on different flo

The number of floors is independent of the type and specified separately by the user. Therefore, if the user assigns 10 floors to this grid cell, the lower 2 floors will be a mix of 541310 and 541330 and the upper 10 floors will be a mix of 23, 42 and 61.

In most cases, the type specification will not require such a detailed level of partitioning of types. If for example, the grid cell has only a single usage type, the same data format will be used but the upper and lower level list will have length of 1. For example, the following represents the NAICS attribute for a grid cell solely devoted to "54" (Professional, Scientific and Technical Services).
In most cases, the type specification will not require such a detailed level of partitioning of types. If for example, the grid cell has only a single usage type, the same data format will be used but the list will only contain 1 object of length 1. For example, the following represents the NAICS attribute for a grid cell solely devoted to "54" (Professional, Scientific and Technical Services).

```json
{
Expand All @@ -58,8 +47,7 @@ In most cases, the type specification will not require such a detailed level of
"P": 1,
"use": [
{
"P": 1,
"use": "54"
"1": "54"
}
]
}
Expand All @@ -81,8 +69,7 @@ Below are some examples of CityScope types. These can be copy and pasted or modi
"P": 1,
"use": [
{
"P": 1,
"use": "1120"
"1": "1120"
}
]
}
Expand All @@ -97,8 +84,7 @@ Below are some examples of CityScope types. These can be copy and pasted or modi
"P": 0.1,
"use": [
{
"P": 1,
"use": "4451"
"1": "4451"
}
]
},
Expand All @@ -112,17 +98,15 @@ Below are some examples of CityScope types. These can be copy and pasted or modi
"P": 0.1,
"use": [
{
"P": 1,
"use": "2150"
"1": "2150"
}
]
},
{
"P": 1,
"P": 0.9,
"use": [
{
"P": 1,
"use": "1120"
"1": "1120"
}
]
}
Expand Down

1 comment on commit 0fa176a

@MarkusElKatsha
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello Ronan - The above is great!

I have a few questions/comments. Please note the following:

  1. Comment: should a type include information about utilization or capacity (in the same way we use S, M, or L on the Volpe table)? I do not think it should be S,M,L, but we could use a person/meter or some scale factor to add to the definition of components within a type. IE: For a given land-use, we need to outline how they are aggregated? Is it 1 unit or 3 units/floor.

  2. Comment: there will never be an economic activity without a land-use, but there can be land-uses without economic activity. Would it be better to format or organize the data in a way that associates a NICS code of each land-use, when a NICS code is available?

  3. Question: what does the "P" above each land-use mean?

Please sign in to comment.