Remember the Confederation Country Cabinet project that I made a small contribution to this spring?

Well I was delighted to receive a copy of the book that Brenda Whiteway arranged to have produced by the talented Judy Gaudet that details the genesis and execution of the cabinet. As someone whose head was deep inside the project for many months, the greatest role the book plays is allowing me insight to the other artists who were busy making their contributions at the same time.

Like Joe McAskill, the woodworker who brought the cabinet itself to life:

And Brenda herself, who not only spun flax into linen, but who actually grew the flax herself:

There’s a story about each of the potters who crafted drinking vessels – one per Father of Confederation – along with a photo of each:

And an embarrassing number of photos of me at the printing press:

The book is available for purchase online and you can also preview the entire thing there in its full-colour 30 page glory. Because it’s a “print on demand” project, there are absolutely no economies of scale to the printing, so it’s not an inexpensive tract. But as a result you can order it in any of hardcover, hardcover with dust jacket or soft cover.

Here’s what page 3 of The Charlottetown Guardian looked like on May 3, 1922:

In amongst the ads for “barefoot sandals” and an 8-year old Clyde Mare and Navy Cut Cigarettes was the end of the report from the Provincial Legislature that started on page 1 under the headline “Lively Debate on Women’s Franchise Resolutions.”

Those resolutions involved the extension of the right to vote to women, the heart of which came in the preamble:

RESOLVED – That it is expedient to introduce a bill to extend the franchise to women; And that the qualification of male and female voter should be the same.

After some of that “lively debate,” much of which appears to have been taken up with procedural questions cloaking misgivings by men about women have the right to vote, the resolution passed:

And that was it. There was no further mention of this dramatic change in that day’s paper, nor in the next day’s paper nor in the day after that. “The motion was further suppored by Messrs. W.B. Butler, and W.H. Dennis, and carried.” That was it.

If you visit WhatsMyLot.com and you happen to be on Prince Edward Island with a device – a desktop, a laptop, a mobile phone, a tablet – that knows its own location, the little app you find there will tell you which of the township lots originally set out by Samuel Holland in 1765 you happen to be standing in.

Here’s what it looks like when I call it up on my phone here in my office in Charlottetown:

If I tap on the map icon, I see my township – Charlottetown Royalty, in this case – highlighted, and a marker showing my current location:

If you leave the app running on your device and go for a ride in the countryside, as you cross lot boundaries you’ll see the lot number update as you drive (once you’ve loaded the app, you don’t need to have Internet connectivity for it to work: all of the logic of finding your location and identifying your lot happens on the device, using JavaScript).

The app also remembers which lots you’ve visited, colouring the lots red as you visit them. Collect all 67 (plus 3 royalties), and you win the Island!

This is just an alpha release of the app, to receive feedback in advance of packaging it up for the various app stores in preparation for the 250th anniversary of Holland’s survey next year.  So, please provide feedback.

Spotted at the Trinity-Clifton United Church manse fence yesterday around dusk.

Download the ESRI Shapefile version of the lots from the PEI GIS Catalog and open the resulting lot_township_polygon.shp in QGIS.

In QGIS, right-click on the layer in the layer browser, and select:

• Format: ESRI Shapefile
• Save as (filename): pei-lots-wgs84.shp
• Encoding: System
• CRS: Selected CRS (then click Browse below, and select WGS 84)

Your “Save vector layer as…” dialog should look something like this:

Close and reopen QGIS and open the newly-created pei-lots-wgs84.shp file, which should look like this:

If you save this as a GEOJSON file at this point, because it’s a very-detailed map the size of the file will be multi-megabytes.  We want to create a smaller file, by simplifying the geometer of the lots.

To do this, select Vector menu > Geometry tools > Simplify geometries in QGIS, enter a new file name, pei-lots-wgs84-simplified.shp, using the default tolerance of 0.0001 and click OK to process.

The result will be a new, simpified Shapefile that you can now export to a GeoJSON file; load the new, simplified layer, then right-click on the layer in the layer browser, and select:

• Format: GeoJSON
• Save as (filename): lots.geojson
• Encoding: System
• CRS: Layer CRS

You can load the resulting GeoJSON file into geojson.io – it’s about 1.9MB.

Here’s a snippet from The Guardian, September 14, 1914, showing the September 1914 tide predictions for Charlottetown and highlighting the high tide times for this day, 100 years ago:

Here’s a snippet from The Old Farmer’s Almanac Tide Predictions Calculator showing the predicted tides for September 14, 1914:

Comparing the two you can see that the high tide times predicted in The Guardian 1914 were 3:39 a.m. and 6:30 p.m.; the Almanac’s modern-day calculation puts these at 3:28 a.m. and 6:34 a.m., a different of 11 minutes and 4 minutes respectively. The Guardian predicted high tide height of 7.3 feet and 5.9 feet; the Almanac predicts 7.77 feet and 6.85 feet; not the same, but certainly in the same ballpark.

Although most every day of my working life for the past 18 years has, in one way or another, been steeped in the Moon and the Sun and the tides and the planets and the weather in one way or another, it never ceases to amaze me that the forces of nature have such a rhythm that they can be predicted not only a month in advance, but from a distance of 100 years.

A few days ago I spotted an intriguing photo on Instagram, taken by the inimitable Tristan Gray (who, among other things, might be PEI’s most attentive restaurant worker), of a new PEI Brewing Company – Receiver Coffee mashup, “Coffee Stout”:

While I’m a regular consumer of Receiver’s coffee, I’m not a beer drinker, and so I haven’t paid much attention to the PEI Brewing Company, something not aided by its remote location in Charlottetown’s industrial suburbs.

But I liked the product design, and was curious about what the result of coffee + beer would be like, and so I decided to incorporate a visit to the company’s beer store on a cycle ride out to the University of PEI last night.

I turned to Google Maps for some guidance on the best cycle route and how long it would take to get out there, assuming that it might take 20 or 30 minutes to cycle so far out into the hinterland of the city. To my surprise, Google said 8 minutes:

I balked: there’s no way it was only going to take 8 minutes to cycle that far. So I started the stopwatch on my phone as I headed out the door. And I stopped the stopwatch on arriving at the Brewing Company, Here’s what it looked like:

Eight minutes and five seconds. Amazing.

This simply serves to confirm the existence of the Charlottetown proximity-estimation-distortion-field when it comes to walking and cycling: we all grossly overestimate the time and distance between downtown and anything north of Euston Street. The notion, for example, of walking (Google says 51 minutes) or cycling (15 minutes) up to the Charlottetown Mall, would be considered by most here to be completely absurd, and akin to, say, walking to Moncton.

I bundled my beer into my bicycle basket and headed through the People’s Cemetery to St. Peters Road, then along Belvedere to the university, where I took in a lecture by Doug Sobey on the pre-settlement history of Prince Edward Island’s forests (it was fascinating, and incorporated the best use of PowerPoint I’ve ever seen).

When I emerged into the night at lecture’s end it was raining. Fortunately I was wearing my rain coast – the same German one that kept me partially dry during the Incident at Bukovel – and my bicycle was wearing its very-bright MEC lights, so I was able to almost-pleasantly cycle down the Confederation Trail to home. I arrived 15 minutes later a little soggy by happy in the new realization that everything is closer than I think.

Thanks to Keir at Spry Point, I’ve had the loan of a Grid Insight AMRUSB-1 for the last week. I connected it to as Raspberry Pi, wrote some code to take meter readings it received and archive them and then left it running here in my downtown Charlottetown office for a week.

The code got gradually less buggy over the week: when I first started running my archiving daemon it wouldn’t run for longer an a couple of hours, something I traced back to a combination of a flaky USB wifi dongle and lack of proper exception handling in my code. In its current state I’ve had the daemon running problem-free for more than 24 hours.

From the afternoon of September 7 to the morning of September 12 I archived 2,901 readings; of these, 1,018 were unique (the AMRUSB-1 simply readings broadcast readings, whether there’s been a change in reading or not, and my code simply archives everything).

The AMRUSB-1 received readings from 68 unique meters:

• 51 meters of type 7 (electric meter)
• 8 meters of type 8 (electric meter)
• 4 meters of type 13 (water meter)

The number of readings from any one meter ranged from 1 to 397; because the frequency of updating is likely the same across meters, the variation, I am assuming, is because distant meters were received less often.

The meter with the highest number of readings archived – 397 – is a water meter; it started off the week with a reading of 25,965 and ended with a reading of 26,005, a delta of 40; assuming the units are m³ (which is how it’s explained here for manual meter reading), that’s consumption of 40 m³, or 40,000 litres. Which seems like an awful lot of water – 8,000 litres a day. I wonder whose meter that is.

Poking around the basement of my office building, I found the water meter, with an Itron ERT device strapped to it, with the meter serial number printed on the outside:

My archive had 60 readings for that meter, starting the week with 88,771 and ending the week with 88,865. Comparing this reading to the current reading on the analog meter:

I see that the digital reading needs to be divided by 10 to get a figure in m³, so the office readings are actually 8,877.1 and 8,886.5, with a delta of 9.4 m³, which is 9,400 litres, or 1,880 litres per day. Which still seems a lot, but then again this is an office building with public washrooms, multiple tenants, etc., so perhaps it’s reasonable.

This means the delta in my first example is actually only 4 m³, or 4,000 litres.

The most-frequently-archived electricity meter, with 376 readings archived, started the week with a reading of 31,890 and finished the week with the same reading, suggesting it’s either a dormant meter or one connected to something that uses less than 1 kWh of electricity in 5 days. The same thing was true of the next 3 of the other most-frequently-archived meters, each of which show less than 1 kWh of usage.

The most-frequently-archived electricity meter that actually showed usage had 169 readings archived, starting with 856213 and ending with 860676 for a delta of 4,463, which I presume is a measurement in kWh. At the rate I pay for electricity at home – 12.78 cents per kWh – that’s $570 worth of electricity, or about 5 times what our house uses in an entire month. Again, it would be interesting to know whose consumption this is.

The term of my loan is up today, so I’m returning the AMRUSB-1 with gratitude; my own replacement, purchased last week, is in transit along with 4 others that will be placed in volunteer households under the Social Consumption Project.

From yesterday’s Apple event introductory video:

From today’s visit to the Charlottetown Farmer’s Market:

It’s a challenging time for those of us who believe strongly in the value of the lower case. Surely e e cummings is unsettled in his grave.

In my continuing drive to decouple my life from Google and Dropbox et al – both to afford me more practical control and more spiritual control of my data – and spurred on by the example of my friend Ton, I’ve been migrating a lot of my digital storage and sync needs into ownCloud, a free and rather capable open source application that I run on my own server (you don’t need your own server: companies like ownCube will allow you to rent an ownCloud server).

When I first experimented with ownCloud, earlier in its development life, it was one of those “sort of works, some of the time” applications, the kind of thing you wouldn’t want to trust things like contacts, calendar and file syncing to. With version 6 and, most recently, version 7, I’ve found it to be rock-solid, and, as a result, I’ve rolled a lot of my life into it.

There are three devices in my digital life: my MacBook air, which I use primarily in the office, my iPad 2 which I use for iOS development in the office, sometimes take home, and often take on the road with me, and my Moto G Android mobile phone, which is always in my pocket.

• Sharing Files: Just like I’d use Dropbox. I have an ownCloud folder on each device, and everything I add to this folder on one device is available on all the others. There are dedicated clients for OS X, iOS and Android that enable this. I have the Android app set to automatically upload any photo I take on my phone’s camera to ownCloud, meaning that my photos are instantly synced and backed up. In addition to sharing files with myself, I can also shared them with others, either openly or with a password attached.
• Calendar Sync: I have the Calendar apps on all my devices synced via ownCloud (rather than iCloud, or Google Calendar). I add an event on one device and it appears on all the others. The syncing happens, under the hood, via CalDAV; on iOS and OS X the apps support this natively; for Android I use CalDAV-Sync.
• Contact Sync: I have the Contacts apps on all the devices synced (again, rather than via iCloud or Gmail). I add a contact on one device and it appears on all the others. The syncing happens via CardDAV; on OS X and iOS this is baked into the apps; for Android I use CardDAV Sync.
• Reminders/Tasks Sync: I have the Reminders apps on iOS and OS X and the Android Task Sync all syncing tasks/reminders to ownCloud via the Tasks app (not part of the stock ownCloud install). This is new functionality for ownCloud but it’s working just fine for me.
• Bookmarks Sync: Not a complete solution yet, but I’ve got the ownCloud Bookmarks app (again, not a part of the stock ownCloud install) syncing with the ownCloud Bookmarks app for Android; for iOS and OS X, for the time-being at least, I used the ownCloud web interface to save and recall bookmarks. I’ve replace Pinboard (and, before that, Delicious) with this, and it’s not perfect, but it’s working.
• Document Collaboration: ownCloud’s web interface allows OpenDocument word processor files to be edited in a browser, just like Google Docs (albeit, right now, without all of Google Docs’ functionality). And it allows these documents to be shared, either with other ownCloud users, or with the public, and others can make changes to the documents if you allow this. I edited a draft set of bylaws with a group of 8 people this way last week and it worked well.

Most of this has been happily chugging along since mid-May without issue. I have my ownCloud running on an Amazon EC2 instance, and I have the EBS volume where the ownCloud data is stored backed up (via this handy script) to a snapshot every night.