REGARDING IMPLEMENTATION OF POLYGON STORAGE
To implement the concept of georeferenced polygons one must to establish the geopoints that serve as vortices (line endpoints) around the polygon (on the perimeter / path / track) and save them in order, repeating the first geopoint at the end to close the polygon.
One critical decision in mapmaking is determining what parsing format will be used to store geodata (kml, txt, gpx, for example). Some apps render many of these formats, others only a few, some export to various formats, other only to one or two of them.
I very much like GPS Trackmaker as a free conversion / mapping / downloading tool. Their premium solution is great, too.
In this case, i chose
TXT files because they are very readable, though they offer infinitely less features and control than, say, kml.
If you examine a polygon parsed for
TXT map rendering, you will find something like:
notice that your first geopoint ends with
1 but all others end with
0. every new polygon starts with a
1. if your txt file comprises multiple polygons, it might read
REGARDING HOW YOU OBTAIN THE DATA
I recommend that you request the info from the Canada Post directly. You will probably receive a list of street / road addresses, which will then have to be converted to geopoints. You might be able to get away with getting the data from a Google API, but it is certainly irregular and you don't want to have a commercially useless list of geopoints, do you?
So you probably use opensource / community developed Nominatim 's API and batch convert. Please read their terms of service, too!