The OPrognose ZIP file is imported using the HUMBLE Exchange server. Below a description how the Exchange Server is handling the OPrognose XML file.
The ZIP file contains a XML file. The name of the XML file muse be equal to the name of the ZIP file.
1 - ZIP File is extracted
...
The OPO Record is read and a mapping is done as described below here.
...
OPrognose XML tag
...
Type of mapping
...
HUMBLE Field
...
Description
...
n.a.
...
Fixed mappings
...
country_id = 528 (NL)
law_country_id = 528 (NL)
status_id = '1'
...
obj_plaats
...
Direct mapping
...
city
...
obj_bouwjaar
...
Direct mapping
...
buildyear
...
obj_grondm2
...
Direct mapping
...
surface_area
...
obj_renojaar
...
Direct mapping
...
year
...
obj_inspectie
...
Direct mapping
...
inspection_date
...
obj_type
...
Functional mapping
...
label
...
Converts the field obj_type but first removes special characters. When Empty value ‘Niet gevuld in O-Prognose’
...
obj_adres
...
Functional mapping
...
street
...
This method will strip the field <obj_adres> into two Humble Fields street and house_number The address is divided by each space character. The last part will be the house_number, the rest is the street part
...
obj_adres
...
Functional mapping
...
house_number
...
See above
...
obj_memoxxx fields
...
Functional mapping
...
remark
...
Gets all the available and nit empty <obj_memoxxx> fields and concatenate them to one result. The remark length has a maximum of 512 characters in HUMBLE and the result will be truncated if necessary
...
Functional mapping
...
short_label
...
A new code is generated by default for each location of type Building. Code like ‘G-000001’
...
obj_grondm2
...
Functional mapping
...
surface_area
...
Integer value for the obj_grondm2
...
obj_postcode
...
Functional mapping
...
zipcode
...
Remove all spaces from the field obj_postcode
...
obj_code
...
Functional mapping
...
search_label
...
The original reference
...
obj_code
...
Functional mapping
...
reference
...
The original reference
...
obj_foto,obj_foto2,
obj_foto,obj_foto4
...
Image mapping
...
Added as separate images within HUMBLE. Images are related to the location (building)
3 - <OPE> Element record
Each OPE record is read and mapped (see description below) and related to the location (building)
...
OPrognose Field
...
Type of mapping
...
HUMBLE Field
...
3 - <OPE> Element record
Each OPE record is read and a mapping is performed as described here
The new HUMBLE Asset is related to the location (building)
4 - <OPH> Handeling record
This is a very special one. In OPrognose every handeling can be an other type of Activity in HUMBLE
Records with <han_type> B are converted into Defects. Mapping is described here
Records with <han_type> H are converted into MYP activities type ‘Vervangen’. Mapping is described here
Records with <han_type> O are converted into MYP activities type ‘Vervangen’. Mapping is described here
Records with <han_type> B and Cyclus = 0 are converted into MYP activities type ‘Correctief’. Mapping is described here
Records with <han_type> B and Cyclus > 0 are converted into MYP activities type ‘Preventief’. Mapping is described here