Okay, I'll bite: this looks like a fun and fairly easy conversion. This
week (probably after Wednesday evening's talk), I will:
* Get the data into a database and host on the RTH data resource [1].
* Create a Google Map plotting the crossing guard locations.
* Share the code I used to convert the data on github with a FOSS licence
so others can easily replicate it.
Kind Regards,
Ryan
[1] http://raisethehammer.org/data - each data set is available in HTML
and JSON format
Being a new addition to this list, perhaps I've missed the part where
the city has said, "Yeah, okay, have your way with the data on our web
site".
From their web site terms of use, I find :
"You may not reproduce, publish, copy, link to, frame, tag, embed,
merge, modify, recompile, license, distribute, sell, store in an
electronic retrieval system, download (except by the browser of a
single user) or transmit, in while or in part, in any form or by any
means whatsoever, be they physical, electronic or otherwise, the
Portal and/or the Content."
Which, to me says, "Hands off".
The data on RTH will be available to download in JSON format, so you
should be able to drop it easily into any other data store.
Update: I wrote a script that grabs geocodes for each location (using the
Google Maps API) and formats the whole thing into an SQL insert statement.
Here's the script (in Python) if anyone wants to play around (warning -
the script is not pretty): https://gist.github.com/879619
I've run the script myself and dumped the results into the RTH database.
As soon as I get a chance this evening, I'll expose it via the RTH data
API.
Cheers,
Ryan
* Numbers of crossing guards by ward (in decreasing order):
* ward 9 has 19 crossing guards
* ward 8 has 18 crossing guards
* ward 7 has 17 crossing guards
* ward 6 has 16 crossing guards
* ward 1 has 14 crossing guards
* ward 3 has 14 crossing guards
* ward 2 has 11 crossing guards
* ward 10 has 8 crossing guards
* ward 5 has 7 crossing guards
* ward 12 has 7 crossing guards
* ward 4 has 6 crossing guards
* ward 13 has 3 crossing guards
* ward 11 has 2 crossing guards
* ward 15 has 1 crossing guards
* Intersection types:
* 61 records do not specify intersection type
* 37 are full signal
* 18 are 3 way stops
* 10 are PPS
* 9 are 4 way stops
* 8 are mid-block crossings
* School types:
* 65 are public schools
* 17 are separate schools
* 61 are both public and separate schools
Cheers,
Ryan
Yes - lat and long for each location.
> can you share as a CSV (or any other table format)?
Sure thing. I'll post a follow-up once it's available.
> Also, wonder if you can share more on the RTH Data API?
If I can get it, I can share it. :)
Sent from my iPod
That isn't the entire story about factual data, James. "The law" as
it applies to data is evolving quickly (for law).
"Sweat of the Brow", that is, the effort expended in compiling
information, earns copyright protection in the UK.
http://en.wikipedia.org/wiki/Sweat_of_the_brow
And in the European Union, the European Database Directive gives sui
generis protection to database works even if they are not entitled to
copyright.
So, to publish Open Data, data that is really open and does not
discriminate against users in, say the UK and Europe, one needs to
publish that data with a license granting the rights to use that data
as open data.
Your rights to use published data vary by jurisdiction. Yours and the
jurisdiction of the publisher should they choose to mess with you.
;-)
It's worth encouraging Hamilton and other municipalities to take a
modern and sustainable approach with their Open Data initiatives. As
challenging as it may be to get the city to adopt an Open Data
initiative, it will be tougher to get them to change it afterwards.
Witness the failings of the Vancouver / Toronto / Edmonton / London /
Ottawa data license, and the difficulty those municipalities are
having in righting their ships. Hamilton can learn from Surrey, BC,
and adopt the ODC PDDL* for their Open Data. That insures that their
data may be used by those in any jurisdiction
First: I'm not quite sure I'm reading the City's terms of use correctly,
so I sent an email to the city manager and head of legal to ask for
clarification.
If it is indeed the city's policy that no one is allowed to link to the
city website without permission, I intend to write about it for RTH to
draw public attention to how ridiculous the city's website terms are.
If we want them to change a bad policy, publicity and public attention
are critical.
Second: IANAL but even if that is the city's terms of use, that doesn't
mean the terms are legally enforceable. The problem, in Canada, is that
there is no legislation governing the legality of various
internet-specific activities, like hyperlinking and so on. That has left
the courts to decide how to handle conflicts over what is allowed.
A case in front of the Supreme Court of Canada right now [1] turns
around whether linking to a web page constitutes citation or
republication. In this case, the plaintiff is accusing the defendant of
defamation for linking to web pages the plaintiff argues are defamatory.
[1] http://www.scc-csc.gc.ca/case-dossier/cms-sgd/sum-som-eng.aspx?cas=33412
The Supreme Court of British Columbia had decided that simply linking to
a defamatory web page does not constitute defamation, unless the link is
provided for the purpose of endorsing the defamatory material.
It seems to me that if linking = citation, a web site owner can't
legally prevent others from linking to it; whereas if linking =
republication, every link becomes a potential copyright infringement.
What a disaster that would be!
Third: in terms of linking to and using public data, another issue that
may limit the City's ability to restrict what third parties do with the
data is municipal freedom of information law [2] that asserts the right
of the public to access government information that is not specifically
exempted for reasons of privacy or has an overriding public interest.
[2]
http://www.e-laws.gov.on.ca/html/statutes/english/elaws_statutes_90m56_e.htm
It seems ridiculous from a legal standpoint that one might have to file
an FOI under MFIPPA just to publish legally public information that is
already published on a municipal website. Certainly newspapers publish
information obtained under FOI requests without legal consequence.
Information "owned" by the City of Hamilton that is not specifically
exempted from publication due to privacy issues is BY LAW accessible to
the public. I would be most surprised if a use licence on the part of
the City that tries to restrict what the public can do with public
information would hold up to a legal challenge.
Regards,
Ryan
The crossing guard data is now up on RTH:
http://raisethehammer.org/data/crossing_guards.html
The HTML view plots the crossing guard locations on a Google map,
including links to a JSON format and a CSV format so you can download it
for other uses.
Cheers,
Ryan
I had actually never coded against the google maps API before, so it was a
useful exercise. It turns out to be easier than I expected to feed
geocoding markers onto a map - I'll definitely be doing more of this in
future.
Note also that the raw data are available in JSON and CSV format, so it
should be easy to incorporate into other data stores.
Regards,
Ryan
_____________
Milton Friesen
Cardus :: research for the common good
Ingenuity Arts :: adaptive leadership
Profile
Recent Article
Adaptive Cities
Twitter: @ingenuityarts
Skype: ingenuityskype
This assumes the City even knows its own licensing terms. The current
terms bear all the signs of what is common practice on the web:
1) an organization figures it needs a terms of use
2) it hires a law firm that does not have relevant experience
3) the law firm drafts the most aggressive possible terms of use
4) the city rubberstamps the terms of use and publishes it on its site
This sort of thing happens because insufficient consideration is given
to what the license should include, and thus insufficient instructions
are given to the lawyers, and so the lawyers of course write the most
protective license possible. AOL in particular has made headlines with
its terms of service, which it has subsequently modified. The
licensing on the recent data.gc.ca had some particularly wrong-headed
clauses, and, after they were brought to his attention, Minister Day
said they will be struck. I don't believe anyone in the City has
strong feelings about its licensing terms, and I think most people are
unaware of them.
This group's reputation with the City will be more strongly affected
by other concerns, e.g.:
1) Are you reaching out to the City? Are you writing to people in
relevant positions at the City? Are you inviting the City to public
meetings? In short, are you promoting a dialogue?
2) Are you approaching the City as a friend and partner, or as an
obstacle that you must push and pressure? Is your approach to educate
people about open data to get them on your side, or to bully them with
arguments?
It's important to understand politicians. Politicians move slowly.
They like to make announcements. They like to be in control. The
approach I favor for open data groups is to prepare the terrain for
politicians. If you push them, they will push back; things will drag
out. An open data policy can be achieve without pushing, and it will
probably happen sooner without it. For example, it is better to
propose a draft motion to sympathetic councillors, who may then take
initiative in council, than to arrive a dozen strong at question
period and demand they pass a motion you prepared.
I'm in correspondence with city legal manager Peter Barkwell. He's
preparing a response/explanation of the city's TOS and will send it as
soon as he can.
Regards,
Ryan
Here's another easy conversion:
http://www.hamilton.ca/CultureandRecreation/Recreation/CentresPoolsArenas/recCenterListing.htm
Data hosted on RTH in HTML, JSON and CSV format:
http://raisethehammer.org/data/recreation_centres.html
After getting through the coding for the crossing guard data, this one
was dead easy - less than half an hour total. Other tabular HTML data on
the site will be similarly easy to convert.
Regards,
Ryan
The speed and technical ease of many of these data conversions -
particularly the low-lying fruit - weakens the claim of open data
opponents that it will be 'too costly' to undertake.
Regards,
Ryan