Hi Fernando,
your proposal sounds quite interesting for implementing MARMOTTA-584 for
Google Summer of Code!
I just miss some more details about the deliverables and scheduling of
your proposal. Remember you can update it until the call closes (Friday
2015-03-27 at 19:00 UTC).
Nice to see such kind of valuable contribution coming this summer :-)
Cheers,
On 26/03/15 18:02, fernando baculima wrote:
This is my proposal for this project to implemente GeoSPARQL.
*Materialization of Triplets*
Advantages
· Fast GeoSPARQL query
Disadvantages
· Materialization is a large process
· The materialization requires more storage capacity than traditional
strategies
· Implies native tools, operators handling (postgresql)
*Native support and query translation*
In this case, the GeoSPARQL query is translated to spatial operators and
executed by native tools (GeoTools).
Advantages
· Direct comparison
· Optimal storage
· There is no need to manipulate the native functionality
Disadvantages
· Slow GeoSPARQL querying
*GeoSPARQL for KIWI*
· Implementation of operators in an incremental way
*Test*
· Test suite to validate the proposed approach
*Documentation*
· Full documentation of the whole process
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: [email protected]
w: http://redlink.co
