Postal_Code_Master table

From CCMDB Wiki
Jump to navigation Jump to search

Postal_Code_Master table in Centralized_data.mdb is used by query NDC_Bad_Postal_Code to detect by exclusion Postal Code entries that are likely invalid.

The table on its own would be about 71MB, (30MB with all extra info stripped out) which is why the check was not included in CCMDB.accdb.

Data Structure

field type description
PCODE text(6) the postal code
rhaname text(17) name of regional health authority that the postal code is in
CA_name text(22)
NC_Name text(27)
latitude number(single)
longitude number(single)
province text(4)
town text(40)

Contents

This is the table that postal codes get checked again. It includes the MB RHA that a postal code is affiliated with. For the MB component we imported a version provided by Marc Silva to p:Julie Mojica 2016-09-08. The country-wide component was based on an older table I think we go it from Stats Can.

The contents are a mix of what we have received from various sources, and of what Pagasa adds when she finds a code that hasn't been listed before.

This data is not available form the Government of Canada, but a regularly updated file is available from here:

Data Integrity Checks

JALT
  • Management of this table has always been driven only by resolving inconsistencies query NDC_Bad_Postal_Code, and there have not been cross checks for this table itself. We found 2025-06 that there were inconsistencies between postal codes and province entries in this table, and Pagasa found duplicate postal codes. Also, we do not have a central process to update postal codes as new ones are added to the system. Do we need a formal process? Is the current ad-hoc process enough. Or do we need a decision on allowing these inconsistencies and just documenting them? Ttenbergen 15:55, 24 June 2025 (CDT)
  • SMW


  • Cargo


  • Categories

Log

  • 2022-08-?? - made field sizes smaller / more appropriate recently, removed duplicating/unused fields

Related articles

Related articles: