Downloadable data

Importing a .csv file that uses UTF-8 character encoding into Excel

Follow the steps outlined below to use Microsoft Excel to open a .csv file that uses UTF-8 character encoding.

  1. Open Microsoft Excel.
  2. Click on the Data menu bar option.
  3. Click on the From Text icon.
  4. Navigate to the location of the file that you want to import.  Click on the filename and then click on the Import button.  The Text Import Wizard - Step 1 or 3 window will now appear on the screen.
  5. Choose the file type that best describes your data - Delimited.
  6. Choose 65001: Unicode (UTF-8) from the drop-down list that appears next to File origin.
  7. Click on the Next button to display the Text Import Wizard - Step 2 or 3 window.
  8. Place a checkmark next to the delimiter that was used in the file you wish to import into Microsoft Excel.  The Data preview window will show you how your data will appear based on the delimiter that you chose.
  9. Click on the Next button to display the Text Import Wizard - Step 3 of 3.
  10. Choose the appropriate data format for each column of data that you want to import.  You also have the option to not import one or more columns of data if you want.
  11. Click on the Finish button to finish importing your data into Microsoft Excel.

Data definitions - Metadata

Infrastructure Pipeline data columns
No Column Name Title and Label Used in the Pipeline Type Description
1 PrimaryKey N/A - not displayed. Text. Constrained to 10 characters. Alphanumeric code assigned to the project by Infracom. Does not change if the project changes its name and remains essentially the same project in scope. ParentProjectIDs are retired permanently and not re-used if a project is cancelled.
2 DateUpdated Date updated. Datetime year, month and day in YYYY-MM-DD format. Date of the latest update to the project.
3 ProcuringOrganisation Organisation Text. Enclosed in standard double-quotes as some organisation names may include commas; comma is used as the delimiter in the CSV for download. Full legal name of the organisation managing the procurement process for infrastructure projects.
4 ProjectName Project Text. Enclosed in standard double-quotes as some names may include commas; comma is used as the delimiter in the CSV for download. Project name as supplied by the procuring organisation. May have been modified slightly by Infracom to expand on acronyms or abbreviations that may be unfamiliar outside the procuring organisation.
5 ProjectShortDescription N/A - displayed without a label on project detail pages. Text. Enclosed in standard double-quotes as some descriptions may include commas; comma is used as the delimiter in the CSV for download. Short paragraph supplied by the procuring organisation.
6 ParentProjectID N/A - not displayed. Text. Constrained to 10 characters. If a project or programme of work has sub-projects the PrimaryKey of the parent project will be identified in this column.
7 ProjectStatus Project status Text. Options are: Early Planning; In Planning; In Procurement; Under Construction; Complete.
8 FundingStatus N/A - not displayed. Text. Options are: Funded for delivery, Funding source to be confirmed, Funding source confirmed
9 ProcurementType N/A - not displayed. Text. Options are: To be determined, Open, Selective, Limited, Direct
10 ProcurementMethod Procurement method Text. Options are: To be determined; Design and construct; Construct only; Public Private Partnership; Other.
11 ProjectRegion Region Text. Regions as defined by local government authorities. The Nationwide option is selected if a project spans multiple regions. Options are: Nationwide; Northland; Auckland; Waikato; Bay of Plenty; Gisborne; Hawkes Bay; Taranaki; Manawatu - Whanganui; Wellington; Marlborough; Tasman; West Coast; Canterbury; Otago; Southland; Other (not in NZ territory).
12 ProjectSector Sector Text. Sector terms have been chosen by Infracom.  
13 EstimatedProjectValueRange Cost range Text. Options are: < 5 Million; 5 - 25 Million; 25 - 50 Million; 50 - 100 Million; 100 - 250 Million; 250 - 500 Million; 500 Million - 1 Billion; 1 Billion +.
14 EstimatedQuarterBusinessCaseStart Business case (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring organisation is not yet able to break down the project dates for the three phases.
15 EstimatedQuarterBusinessCaseCompletion Business case (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring organisation is not yet able to break down the project dates for the three phases.
16 EstimatedQuarterProcurementStart Procurement (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring organisation is not yet able to break down the project dates for the three phases.
17 EstimatedQuarterProcurementCompletion Procurement (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring organisation is not yet able to break down the project dates for the three phases.
18 EstimatedQuarterConstructionStart Construction (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring organisation is not yet able to break down the project dates for the three phases.
19 EstimatedQuarterConstructionCompletion Construction (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring organisation is not yet able to break down the project dates for the three phases.
20 EstimatedQuarterProjectRangeStart Phases undetermined (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring organisation has been able to break down the project dates into three phases.
21 EstimatedQuarterProjectRangeCompletion Phases undetermined (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring organisation has been able to break down the project dates into three phases.
22 ProjectInfoURL Project info URL Text. URI or URL supplied by a procuring organisation for more information about either a. the specific project, b. the organisation's infrastructure and procurement plans or c. the procuring organisation.
23 EstimatedProjectValueNote N/A - not displayed. Text. A procuring organisation may supply information to explain why a project value fits within a particular range.