GSoC denied
Tara Athan
Google Summer of Code Program for 2010. However, OSGeo was. I looked
through their project list to see if there were any suggested
developments that might be of value to us. One that caught my attention
was : make GDAL and/or OGR more thread-safe. Any thoughts on the value
of porting GDAL or OGR into clojure?
Tara
Gary Johnson
GDAL/OGR is written in ANSI C and C++. Porting it (although it is
rather large) to Clojure would be very interesting from the standpoint
of learning about geospatial algorithms. However, what you would end
up with is a Java library, since that is what Clojure compiles into.
Now, this could be very nice for someone who wanted to use GDAL/OGR
from Java. Currently, there exist Java bindings for it, but they are
only complete for the C++ part of the API. A port would make the
entire system available (and in Clojure, exceptionally thread-safe).
It should be noted though that there is a LARGE Java library called
GeoTools which provides most (if not all) of the GDAL/OGR
functionality and is the typical solution for Java geospatial
programmers. So I'm not really sure that I can recommend the port in
good faith.
Perhaps Ferdinando can weigh in with his opinion on the matter.
~Gary
Tara Athan <tara...@gmail.com> writes:
> To unsubscribe from this group, send email to aries-project+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
Tara Athan
The most promising direction at the moment is carving out a section of thinklab (core, corescience, geo, time & modelling) and preparing it for application to OSGeo for incubation (thinkGeo?). My dissertation advisor was OK on that idea, provided I also provide some new functionality, such as implementing a numerical classification type. There is some interest from our local OSGeo chapter, and I am tryig to get ahold of someone on the OSGeo incubation committee. Most likely to be interested would be Jody Garnett of geotools fame, who has recently moved from refractions in Canada to LisaSoft in oz - I've sent emails through a couple of channels- we'll see if any get through.
And then there is this geoserver keywords thing which I am going OCD on...
Tara
Gary Johnson
toolkits = Fun.
Good luck,
~Gary
Tara Athan <tara...@gmail.com> writes:
> --
> To unsubscribe, reply using "remove me" as the subject.
Ferdinando Villa
paste in - we're in touch with Markus (CC'd) as much as my scattered
response patterns allow, and he has expressed an interest in collaborating
with us in some form.
Ciao f
---
Hi Ferdinando,
Thanks for the documentation and for the chat earlier today.
I wanted to mention two additional things. The first is PelletSpatial [1] a
project that I initiated last summer and is now hosted by Clark & Parsia
that extends Pellet with qualitative spatial reasoning capabilities for RCC
[2] data represented in RDF/OWL. I'm planning to build on this project with
an ArcGIS seminar later this semester. The idea is to suggest a project that
looks into accessing quantitative ArcGIS data and transforming (part of) it
to a qualitative RCC description in RDF/OWL. This would (1) interface ArcGIS
with PelletSpatial and (2) enable the exposure of ArcGIS data on the
Semantic Web (thus, potentially make access to data easier).
The second is another idea I recently had after a soil ecology class with a
slide on the Food and Agriculture Organization of the United Nations (FAO)
[3] World Soil Classification. The official document can be found here [4].
I think, the entire (public) taxonomy and all the related information is
essentially locked up in a PDF, which I found awful. So I wrote an email to
Craig Ditzler [5], with a quick description on SW technologies and how a
soil ontology and having the knowledge more accessible etc. might be useful.
He sounded very interested and mentioned someone who was working on a
Finnish version of the taxonomy back in 2000. I have been thinking that it
might be worth spending some time this summer looking into this together
with the Finnish researcher and see if we can come of with a prototype.
Feel free to forward me any thoughts or comments you may have.
Cheers,
markus
[1] http://clarkparsia.com/pellet/spatial
[2] http://en.wikipedia.org/wiki/Region_Connection_Calculus
[3] http://en.wikipedia.org/wiki/FAO_soil_classification
[4] ftp://ftp-fc.sc.egov.usda.gov/NSSC/Soil_Taxonomy/tax.pdf
[5] http://soils.usda.gov/technical/classification/taxonomy/
---
Ferdinando Villa, Ph.D.
Research Professor, Ecoinformatics Collaboratory
Gund Institute for Ecological Economics, University of Vermont
http://ecoinformatics.uvm.edu
Tara Athan
1. use osgeo labs as a starting point towards incubation.
> I have already listed the project, and I went in today and created a page(http://wiki.osgeo.org/wiki/ThinkGeo). I don't expect much response from that, as Osgeo Labs is a fairly low-profile page on the osgeo wiki (http://wiki.osgeo.org/wiki/OSGeo_Labs)
2. consider moving to incubation once a community has formed and the community policies and infrastructure are in place.
> this is consistent with what I was expecting - there is much to be done before incubation.
3. geotools community modules are also good for the reusable part of projects.
> I have no feeling yet as to whether this is appropriate
4. ask on geotools-devel to see if there are any more suggestions.
And from the Osgeo Lab page
5. announce and discuss the project on the osgeo discuss mailing list.
>I'm not quite ready to announce on geotools-devel or osgeo discuss as I would like to spend some more time becoming familiar with these modules so I can carry on a meaningful discussion.
I understand there are some changes going on right now in these modules. I am thinking we should create a branch for thinkGeo so I am not trying to become familiar with a moving target! Will there be a version coming up soon that would be appropriate for that, or should we go back in time? At this point, I need to understand the API, not yet get into the guts of the code, so if the API is not changing too much I would prefer to branch an earlier stable version and bring in the latest developments at a later date, so I can get started.
Let me know what you think?
Also, would it be appropriate to share this mailing list with thinkGeo? If so, I would post a link to the aries-project google groups subscribe page on the thinkGeo page. The list is configured as "anyone can join", so there should be no overhead involved.
Same question on the #aries irc channel. No one but me ever goes to the channel ;/ so there seems no harm: 0+0=0
Tara
Gary Johnson
wasn't aware that you were checking in periodically on our channel. I
had suspected it would be used in an on-demand way (i.e. you email us to
set up a chat time). However, I can certainly idle in #aries during my
workdays without any extra overhead. I've always got an IRC client
running anyway. So pop in whenever.
~Gary
P.S. I'll leave a decision on which SVN version of Ferd's code is stable
to him.
Tara Athan <tara...@gmail.com> writes:
Tara Athan
revision 2704 pruned down to the 5 relevant plugins. I doubt I'll be
modifying anything anytime soon, so we should be able to create a new
branch when the current thinklab development cycle is complete.
Tara
Tara Athan
hydrologic soil group coverages (the Rest GET returns nothing). One of
the geoserver developers suggested it might be a misconfiguration of the
layer, rather than a bug in geoserver. I'm skeptical, but I can't
disprove it. So to test this, I propose to delete one of the layers and
recreate it to see if the problem is reproducible.
So unless anyone has objections I will be messing around with these
layers and changes should be expected. It's not a good idea to be using
these layers anyway until we get this issue resolved.
Tara