[
https://issues.apache.org/jira/browse/OODT-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231246#comment-13231246
]
Chris A. Mattmann commented on OODT-402:
----------------------------------------
Hi Ross,
Great to hear from you! We'd be happy to have you contribute to GSoC and this
particular issue, and more broadly, in Apache OODT as a whole. I'm totally open
to you working on this issue and will be happy to mentor it.
If you have any questions, hit me up on [email protected] or
[email protected] and looking forward to working with you!
Cheers,
Chris
> Write default File Manager policy and associated RSS conf to automatically
> publish GeoRSS to Apache SIS
> -------------------------------------------------------------------------------------------------------
>
> Key: OODT-402
> URL: https://issues.apache.org/jira/browse/OODT-402
> Project: OODT
> Issue Type: Task
> Components: file manager
> Reporter: Chris A. Mattmann
> Labels: gsoc2012
> Fix For: 0.4
>
>
> Apache SIS is a spatial project in the Incubator:
> http://incubator.apache.org/sis/. It provides a location REST service, and a
> dynamic Java Quad Tree. SIS can be fed GeoRSS and then can use that
> information to drive its location service interface.
> Apache OODT and its File Manager component have the ability to manage files,
> their metadata, and to output it in RSS format. The RSS service in OODT is
> configurable, and has been used in the past to generate GeoRSS, but hasn't
> been standardized to do so yet.
> This project would involve:
> # Wire up a default GeoRSS config in the File Manager RSS service to output
> lat/lon generically from ingested files with those metadata fields.
> # Define default file manager policy for LocationAwareProducts.
> # Connect the GeoRSS output in File Manager to Apache SIS and demonstrate
> that the product can be searched and located using the Quad Tree and the
> Location Service in SIS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
