Update 'README.md'
This commit is contained in:
parent
bc6621f889
commit
a63c580db2
123
README.md
123
README.md
|
|
@ -17,10 +17,10 @@ The following dataset contains the collection of buildings in the geojson format
|
||||||
|
|
||||||
## List of dataset changes
|
## List of dataset changes
|
||||||
1. Removed redundant building footprint vertices
|
1. Removed redundant building footprint vertices
|
||||||
2. Removed duplicate buildings
|
2. Removed duplicate buildings (condominium unit duplicates)
|
||||||
3.
|
3. Append building's district - "ADMIN_BOUNDARY"
|
||||||
4.
|
4. Append building centroid - "CENTROID"
|
||||||
5.
|
5. Remove buildings with 9999 year of construction
|
||||||
6.
|
6.
|
||||||
7.
|
7.
|
||||||
8.
|
8.
|
||||||
|
|
@ -78,119 +78,8 @@ Ville-Marie: 8371 buildings
|
||||||
1. "ID_UEV": unique building identifier
|
1. "ID_UEV": unique building identifier
|
||||||
2. "ANNEE_CONS": year of construction
|
2. "ANNEE_CONS": year of construction
|
||||||
3. "CODE_UTILI": building usage type
|
3. "CODE_UTILI": building usage type
|
||||||
4. "ADMIN_BOUNDARY": adminstrative boundary the building belongs to
|
4. "CENTROID": longitude, latitude of building centroid
|
||||||
|
5. "ADMIN_BOUNDARY": adminstrative boundary the building belongs to
|
||||||
|
|
||||||
Yes, these file also contains meta data information available for understanding what different attributes means. the same can be accessed through:
|
|
||||||
1. For 3D building multipatches: donnees.montreal.ca/ville-de-montreal/batiment-3d-2016-maquette-citygml-lod2-avec-textures2#territories
|
|
||||||
2. For building use, and other semantic data: https://donnees.montreal.ca/ville-de-montreal/unites-evaluation-fonciere
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If No, whether the user created one? Or is there any source to understand the data (if the info is available)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Any psuedonames are used to represent the data attribites? If so, info is available explaining this psuedonames are available?
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
***********************************
|
|
||||||
Data available (mandatory)
|
|
||||||
***********************************
|
|
||||||
Not applicable
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
For example:
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Time stamp: Unix/Epoch time. Date format: MM/DD/YYYY HH:MM or YYYY-MM-DD HH:MM:SS or..... (This is an important info for processing the dataset later)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Weather related data - Solar radiaition (Unit), Outdoor Temperature (Unit), Wind Speed (Unit), etc.,...
|
|
||||||
(If possible information on whether weather parameters are measured from a local weather location or from indvidual homes could be helpful)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Energy related data - For example Plug load (Unit), Lighting Load (Unit), HVAC (Unit). Please provide whether the data available is the total energy data or sub-metered data
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Gas measurement data
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Hot water data, etc....
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
***********************************
|
|
||||||
Missing values (mandatory)
|
|
||||||
***********************************
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Yes, these dataset contiains many missing values which are currently empty cells, but work is going on to either remove the empty columns or change them with NA
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Missing value format in the dataset: 'Na' or 'NaN' or '-99' or any other formats
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Continously missing values or sparsely missing values or No missing values
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
***********************************
|
|
||||||
Data Cleaning (If it is processed dataset, it is mandatory to provide this info)
|
|
||||||
***********************************
|
|
||||||
Whether missing values are processed?
|
|
||||||
If so, what is the technique (Moving average, any machine learning techniques, etc...)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Any date/data is excluded because of continously missing values?
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
***********************************
|
|
||||||
Data processing (If it is processed dataset, it is mandatory to provide this info)
|
|
||||||
***********************************
|
|
||||||
Any information related to data aggregation (example: minutes to hour), data transformation (example: min-max, Z-transformation), outlier detection (example: inter-quartile range, etc..)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
***********************************
|
|
||||||
Supporting data (optional)
|
|
||||||
***********************************
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Any other information that can be useful to the new users. For example
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
There is one other zip file with supporting information in. This includes:
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- documents that detail measurements and data visualisation (one per house)
|
|
||||||
- appliance details, images and inventory
|
|
||||||
- document that describes the data processing methods and a zip file of the Octave functions used
|
|
||||||
- document that details the measurement device calibration
|
|
||||||
- floor plans, dimensions and PIR/DOR locations
|
|
||||||
- house construction
|
|
||||||
- house occupant details
|
|
||||||
- installation data and meter readings
|
|
||||||
- a spreadsheet that details all measurements taken on the project (used to create the device ID in the header files)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**********************************
|
**********************************
|
||||||
Alert/Caution (Mandatory)
|
Alert/Caution (Mandatory)
|
||||||
|
|
|
||||||
Reference in New Issue
Block a user