Difference between revisions of "ANLY482 AY2017-18T2 Group 11 Analysis Insights"
| Line 36: | Line 36: | ||
{| width=1080px cellspacing="0" cellpadding="7" | {| width=1080px cellspacing="0" cellpadding="7" | ||
| − | | style="background-color:#2B6C94; font-weight: bold; text-indent: 15px; border-left: 15px solid #4BB9FF" | <font color="#FFF" size=3 > | + | | style="background-color:#2B6C94; font-weight: bold; text-indent: 15px; border-left: 15px solid #4BB9FF" | <font color="#FFF" size=3 > Inputs/Database Tier</font> |
|} | |} | ||
<br /> | <br /> | ||
| − | <div style=" | + | <div style="padding-left:70px; text-align: justify; width:980px;"> |
| − | < | + | <p> |
| + | In order to derive the corresponding Latitude and Longitude from the customer’s postal codes, the team utilised oneMap’s API web service. Through using spatial reference code WGS84, this API web service aided the team in generating table 1 – “Address Point”, which is a geocoded table comprising of individual postal code and their respective Latitude and Longitude values. | ||
| + | </p> | ||
| + | |||
| + | <p> | ||
| + | By concatenating Table 1 with the Customer Order Details, the team obtained a combined table of “Customer Request Table” along with “Address Point”, which will then be loaded in PostgreSQL. | ||
| + | </p> | ||
| + | |||
| + | <p> | ||
| + | In addition, the team also loaded OpenStreetMap containing Singapore’s road networks into PostgreSQL. This allows the Singapore map to be populated with the road networks in Singapore as shown below. | ||
| + | </p> | ||
| + | |||
| + | <p> | ||
| + | The aforementioned procedures allow the “Street Network Map”, “Customer Request Table” and “Address Point” to be loaded within PostgreSQL. This ensures that the Input/Database Tier section of the framework discussed in Section 5.1 to be completed. | ||
| + | </p> | ||
</div> | </div> | ||
<!--- End Analysis Content --> | <!--- End Analysis Content --> | ||
| − | <!-- Start of | + | <!-- Start of Analysis Content --> |
{| width=1080px cellspacing="0" cellpadding="7" | {| width=1080px cellspacing="0" cellpadding="7" | ||
| − | | style="background-color:#2B6C94; font-weight: bold; text-indent: 15px; border-left: 15px solid #4BB9FF" | <font color="#FFF" size=3 > | + | | style="background-color:#2B6C94; font-weight: bold; text-indent: 15px; border-left: 15px solid #4BB9FF" | <font color="#FFF" size=3 > Application Tier</font> |
|} | |} | ||
<br /> | <br /> | ||
| − | <div style=" | + | <div style="padding-left:70px; text-align: justify; width:980px;"> |
| − | < | + | <p> |
| + | In order to derive the corresponding Latitude and Longitude from the customer’s postal codes, the team utilised oneMap’s API web service. Through using spatial reference code WGS84, this API web service aided the team in generating table 1 – “Address Point”, which is a geocoded table comprising of individual postal code and their respective Latitude and Longitude values. | ||
| + | </p> | ||
| + | |||
| + | <p> | ||
| + | By concatenating Table 1 with the Customer Order Details, the team obtained a combined table of “Customer Request Table” along with “Address Point”, which will then be loaded in PostgreSQL. | ||
| + | </p> | ||
| + | |||
| + | <p> | ||
| + | In addition, the team also loaded OpenStreetMap containing Singapore’s road networks into PostgreSQL. This allows the Singapore map to be populated with the road networks in Singapore as shown below. | ||
| + | </p> | ||
| + | |||
| + | <p> | ||
| + | The aforementioned procedures allow the “Street Network Map”, “Customer Request Table” and “Address Point” to be loaded within PostgreSQL. This ensures that the Input/Database Tier section of the framework discussed in Section 5.1 to be completed. | ||
| + | </p> | ||
</div> | </div> | ||
| − | <!--- End | + | <!--- End Analysis Content --> |
| + | |||
</center> | </center> | ||
<br /> | <br /> | ||
<br /> | <br /> | ||
Revision as of 23:17, 15 April 2018
| HOME | PROJECT OVERVIEW | ANALYSIS & INSIGHTS | PROJECT MANAGEMENT | DOCUMENTATION | ANLY482 MAIN |
| EDA | Model Building |
|---|
| Inputs/Database Tier |
In order to derive the corresponding Latitude and Longitude from the customer’s postal codes, the team utilised oneMap’s API web service. Through using spatial reference code WGS84, this API web service aided the team in generating table 1 – “Address Point”, which is a geocoded table comprising of individual postal code and their respective Latitude and Longitude values.
By concatenating Table 1 with the Customer Order Details, the team obtained a combined table of “Customer Request Table” along with “Address Point”, which will then be loaded in PostgreSQL.
In addition, the team also loaded OpenStreetMap containing Singapore’s road networks into PostgreSQL. This allows the Singapore map to be populated with the road networks in Singapore as shown below.
The aforementioned procedures allow the “Street Network Map”, “Customer Request Table” and “Address Point” to be loaded within PostgreSQL. This ensures that the Input/Database Tier section of the framework discussed in Section 5.1 to be completed.
| Application Tier |
In order to derive the corresponding Latitude and Longitude from the customer’s postal codes, the team utilised oneMap’s API web service. Through using spatial reference code WGS84, this API web service aided the team in generating table 1 – “Address Point”, which is a geocoded table comprising of individual postal code and their respective Latitude and Longitude values.
By concatenating Table 1 with the Customer Order Details, the team obtained a combined table of “Customer Request Table” along with “Address Point”, which will then be loaded in PostgreSQL.
In addition, the team also loaded OpenStreetMap containing Singapore’s road networks into PostgreSQL. This allows the Singapore map to be populated with the road networks in Singapore as shown below.
The aforementioned procedures allow the “Street Network Map”, “Customer Request Table” and “Address Point” to be loaded within PostgreSQL. This ensures that the Input/Database Tier section of the framework discussed in Section 5.1 to be completed.
