This is a little off topic geographically (by a province) but I
thought I would post it for interest and to illustrate that not all
use of open data has to be in the form of "apps".
The other day I was producing some land suitability ratings for the
agricultural area of Alberta and realized that all of the "inputs"
were open data.
The soil/landscape information is open data from:
http://www1.agric.gov.ab.ca/$department/deptdocs.nsf/all/sag3252?opendocument
The climate information is open data from:
http://www.ales.ualberta.ca/rr/Research/ClimateChange/ClimateDataforAlberta.aspx
(and thanks to Dr. Andreas Hamann - University of Alberta - for
facilitating the use of this data).
The models are based on the information in the open publication at:
http://sis2.agr.gc.ca/cansis/publications/manuals/1995-6/intro.html
A very quick image of the results are show at URL:
http://xspatial.com/sites/default/files/image/ALSRS_Image1.jpg
Basically, the greener and darker, the better. The white area is not
considered agricultural and has no data.
These ratings can be used for land use planning, land value
assessment, and also climate change scenarios (since climate is an
input).
Perhaps this will stimulate some other ideas on open data use.
... gerry tychon
That is a really good point and suitable for discussion. All of these
sources were posted to the web prior to much discussion of open data
and the best way to present it -- the web is floating in this kind of
information. Maybe some "legal types" have a more educated opinion but
I have been informed that if you want to retain "rights" (e.g., in my
case software) then you need to have an upfront license that the user
agrees to othewise you are in a very difficult position trying to
enforce "rights" after the fact. Having said that, I think it is
better for terms of use to be explicit rather than implicit. Other
than a few government organizations and groups such as ourselves most
people have a poor understanding of what issues are involved with open
data.
... gerry tychon
--
www.eaves.ca
@daeaves
Sent from my iPhone
If the hack starts to grow then I think it becomes the serious issue
that Herb has pointed out. And you'd really need to consider how much
you rely on it.
But I'd encourage people to hack on data they think is open, even if
it's not explicitly so. This pushes boundaries a bit and lets us act
_as if_ herb's hope of "open by default" is true today.
Thinking about this in light of Recollect, I regularly consume
non-explicitly licensed schedule and geo data from municipalities in
the form of their Garbage schedule and zones. I think this is okay,
at least okay enough for me to keep doing until it becomes an issue.
That's a personal/team decision, others will likely come to different
conclusions given different projects and datasets.
--
Dictated but not read.
Twitter: @lukec