Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 0fa176a

Browse files
committedApr 23, 2020
Simplified from list of lists to list of objects
1 parent af3e13b commit 0fa176a

File tree

1 file changed

+13
-29
lines changed

1 file changed

+13
-29
lines changed
 

Diff for: ‎docs/md/Land-Use-Types.md

+13-29
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Each type consists of a dictionary of attributes. The mnimum attributes contined
66

77
## Attribute Examples
88

9-
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:
9+
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:
1010
- the lower 30% of floors are devoted to a mix of "541310" (architectural services) and "541330" (engineering services).
1111
- the upper 70% of floors and devoted to a mix of "23" (Construction), "42" (Wholesale) and "61" (Education).
1212

@@ -17,29 +17,18 @@ A single grid-cell may contain multiple LBCS and multiple NAICS on different flo
1717
"P": 0.3,
1818
"use": [
1919
{
20-
"P": 0.5,
21-
"use": "541310"
22-
},
23-
{
24-
"P": 0.5,
25-
"use": "541330"
20+
"0.5": "541310",
21+
"0.5": "541330"
2622
}
2723
]
2824
},
2925
{
3026
"P": 0.7,
3127
"use": [
3228
{
33-
"P": 0.3,
34-
"use": "23"
35-
},
36-
{
37-
"P": 0.4,
38-
"use": "42"
39-
},
40-
{
41-
"P": 0.3,
42-
"use": "61"
29+
"0.3": "23",
30+
"0.4": "42",
31+
"0.3": "61"
4332
}
4433
]
4534
}
@@ -49,7 +38,7 @@ A single grid-cell may contain multiple LBCS and multiple NAICS on different flo
4938

5039
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.
5140

52-
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).
41+
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).
5342

5443
```json
5544
{
@@ -58,8 +47,7 @@ In most cases, the type specification will not require such a detailed level of
5847
"P": 1,
5948
"use": [
6049
{
61-
"P": 1,
62-
"use": "54"
50+
"1": "54"
6351
}
6452
]
6553
}
@@ -81,8 +69,7 @@ Below are some examples of CityScope types. These can be copy and pasted or modi
8169
"P": 1,
8270
"use": [
8371
{
84-
"P": 1,
85-
"use": "1120"
72+
"1": "1120"
8673
}
8774
]
8875
}
@@ -97,8 +84,7 @@ Below are some examples of CityScope types. These can be copy and pasted or modi
9784
"P": 0.1,
9885
"use": [
9986
{
100-
"P": 1,
101-
"use": "4451"
87+
"1": "4451"
10288
}
10389
]
10490
},
@@ -112,17 +98,15 @@ Below are some examples of CityScope types. These can be copy and pasted or modi
11298
"P": 0.1,
11399
"use": [
114100
{
115-
"P": 1,
116-
"use": "2150"
101+
"1": "2150"
117102
}
118103
]
119104
},
120105
{
121-
"P": 1,
106+
"P": 0.9,
122107
"use": [
123108
{
124-
"P": 1,
125-
"use": "1120"
109+
"1": "1120"
126110
}
127111
]
128112
}

1 commit comments

Comments
 (1)

MarkusElKatsha commented on Apr 24, 2020

@MarkusElKatsha

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.