You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by Isuranga Perera <is...@gmail.com> on 2018/02/14 18:17:46 UTC
[Dev][GSoC][SIS-391] Implement OGC CSW
Hi All,
I am Isuranga Perera, a final year undergraduate from University of Colombo
School of Computing. I participated GSoC 2017 and worked on WS-Trust
implementation for WSO2 Identity Server. I am looking forward to
participate in GSoC 2018, and this project looks an exciting one for me.
As the first step I went through the developer guide[2] . Currently I'm
going through the Hao's prototype of CSW[1].
Appreciate if you can guide me through next steps of the project.
[1] https://github.com/haonguyen123/sis
[2] http://sis.apache.org/book/en/developer-guide.html
<http://sis.apache.org/book/en/developer-guide.html>
Best Regards
Isuranga Perera
Re: [GSoC][SIS-391] Implement OGC CSW
Posted by Isuranga Perera <is...@gmail.com>.
Hi Martin,
I checked with the Geotk parser. Geo-server [1] provides support for CSW
and it supports CQL/ECQL[2] filtering. So we can simply use Geotk parser or
some custom CQL parser with extended querying capabilities like GeoServer.
So appreciate you can provide some suggestions (what approach you think
suites more).
And about Soap endpoints, instead of using Java JAX-RS implementation we
can use a web services engine like Apache CXF [3] so that we can support
both rest and Soap endpoints easily. AFAIK for SOAP service WSDL First
approach will suite more. Appreciate any suggestions.
[1] https://github.com/geoserver/geoserver
[2] http://docs.geoserver.org/stable/en/user/filter/ecql_reference.html
[3] http://cxf.apache.org/
Best Regards
Isuranga Perera
On Mon, Feb 26, 2018 at 7:08 PM, Martin Desruisseaux <
martin.desruisseaux@geomatys.com> wrote:
> Hello Isuranga
>
> You are right, the prototype implementation uses a "filter" keyword
> which is not yet conform to a standard. Writing a CQL parser still need
> to be done. For this task we can either take the Geotk parser as a
> starting point [1][2] (which uses code generated by ANTLR), or we can
> write a parser manually with only a few functionalities for starting.
> Indeed, it needs to be in the project scope.
>
> The mapping from Landsat, Modis, GeoTIFF and netCDF metadata to ISO
> 19115 may not be 100% complete, but I think that their coverage are
> sufficient for this project. We may complete them if we find obvious
> holes, but that would be mostly opportunistic improvements.
>
> SOAP endpoints would be useful too.
>
> Thanks,
>
> Martin
>
> [1] https://github.com/Geomatys/geotoolkit/tree/master/
> modules/feature/geotk-feature/src/main/java/org/geotoolkit/cql
> [2] https://github.com/Geomatys/geotoolkit/blob/master/
> modules/feature/geotk-feature/src/main/antlr4/org/geotoolkit/cql/CQL.g4
>
>
> Le 24/02/2018 à 16:23, Isuranga Perera a écrit :
>
> > Hi Martin,
> >
> > I went through OGC CSW specification and Hao's and Chin's works as
> > well. Basically Hao has implemented get endpoints. So does the
> > project scope includes POST and SOAP endpoints as well?
> > If I'm not mistaken in the prototype implementation filters(e.g. east,
> > west, north and south bounds) are not yet conform to a standard query
> > language like CQL so that this task should be included in the project
> > scope. In addition to that can I know if mapping from Landsat, GeoTIFF
> > and Modis metadata to ISO 19115 implementaion is complete ( is it
> > support all informations in metadata. do I have to complete that as
> > well?).
> >
> > Appreciate if you can clarify those problems.
> >
> > Best Regards
> > Isuranga Perera
>
>
Re: [GSoC][SIS-391] Implement OGC CSW
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Hello Isuranga
You are right, the prototype implementation uses a "filter" keyword
which is not yet conform to a standard. Writing a CQL parser still need
to be done. For this task we can either take the Geotk parser as a
starting point [1][2] (which uses code generated by ANTLR), or we can
write a parser manually with only a few functionalities for starting.
Indeed, it needs to be in the project scope.
The mapping from Landsat, Modis, GeoTIFF and netCDF metadata to ISO
19115 may not be 100% complete, but I think that their coverage are
sufficient for this project. We may complete them if we find obvious
holes, but that would be mostly opportunistic improvements.
SOAP endpoints would be useful too.
Thanks,
Martin
[1] https://github.com/Geomatys/geotoolkit/tree/master/modules/feature/geotk-feature/src/main/java/org/geotoolkit/cql
[2] https://github.com/Geomatys/geotoolkit/blob/master/modules/feature/geotk-feature/src/main/antlr4/org/geotoolkit/cql/CQL.g4
Le 24/02/2018 à 16:23, Isuranga Perera a écrit :
> Hi Martin,
>
> I went through OGC CSW specification and Hao's and Chin's works as
> well. Basically Hao has implemented get endpoints. So does the
> project scope includes POST and SOAP endpoints as well?
> If I'm not mistaken in the prototype implementation filters(e.g. east,
> west, north and south bounds) are not yet conform to a standard query
> language like CQL so that this task should be included in the project
> scope. In addition to that can I know if mapping from Landsat, GeoTIFF
> and Modis metadata to ISO 19115 implementaion is complete ( is it
> support all informations in metadata. do I have to complete that as
> well?).
>
> Appreciate if you can clarify those problems.
>
> Best Regards
> Isuranga Perera
Re: [Dev][GSoC][SIS-391] Implement OGC CSW
Posted by Isuranga Perera <is...@gmail.com>.
Hi Martin,
I went through OGC CSW specification and Hao's and Chin's works as well.
Basically Hao has implemented get endpoints. So does the project scope
includes POST and SOAP endpoints as well?
If I'm not mistaken in the prototype implementation filters(e.g. east,
west, north and south bounds) are not yet conform to a standard query
language like CQL so that this task should be included in the project
scope. In addition to that can I know if mapping from Landsat, GeoTIFF and
Modis metadata to ISO 19115 implementaion is complete ( is it support all
informations in metadata. do I have to complete that as well?).
Appreciate if you can clarify those problems.
Best Regards
Isuranga Perera
On Thu, Feb 15, 2018 at 3:04 AM, Martin Desruisseaux <
martin.desruisseaux@geomatys.com> wrote:
> Hello Isuranga
>
> Welcome! The time period for student applications is from March 12 to
> March 27 [1]. In the meantime, it is a good idea to get familiar with
> the project. An important part will be the Open Geospatial Consortium
> (OGC) standards, in particular (for this project):
>
> * OGC Catalog Services 3.0 - General model
> * OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
>
> Those specifications can be freely downloaded from the OGC web site [2].
> The wikipedia article [3] is also convenient for a short introduction.
> As a next step, you can try to run Hao's prototype.
>
> Regards,
>
> Martin
>
> [1] https://developers.google.com/open-source/gsoc/timeline
> [2] http://www.opengeospatial.org/standards/cat
> [3] https://en.wikipedia.org/wiki/Catalog_Service_for_the_Web
>
>
> Le 14/02/2018 à 19:17, Isuranga Perera a écrit :
>
> > Hi All,
> >
> > I am Isuranga Perera, a final year undergraduate from University of
> Colombo
> > School of Computing. I participated GSoC 2017 and worked on WS-Trust
> > implementation for WSO2 Identity Server. I am looking forward to
> > participate in GSoC 2018, and this project looks an exciting one for me.
> >
> > As the first step I went through the developer guide[2] . Currently I'm
> > going through the Hao's prototype of CSW[1].
> >
> > Appreciate if you can guide me through next steps of the project.
> >
> > [1] https://github.com/haonguyen123/sis
> > [2] http://sis.apache.org/book/en/developer-guide.html
> >
> > Best Regards
> > Isuranga Perera
>
>
Re: [Dev][GSoC][SIS-391] Implement OGC CSW
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Hello Isuranga
Welcome! The time period for student applications is from March 12 to
March 27 [1]. In the meantime, it is a good idea to get familiar with
the project. An important part will be the Open Geospatial Consortium
(OGC) standards, in particular (for this project):
* OGC Catalog Services 3.0 - General model
* OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
Those specifications can be freely downloaded from the OGC web site [2].
The wikipedia article [3] is also convenient for a short introduction.
As a next step, you can try to run Hao's prototype.
Regards,
Martin
[1] https://developers.google.com/open-source/gsoc/timeline
[2] http://www.opengeospatial.org/standards/cat
[3] https://en.wikipedia.org/wiki/Catalog_Service_for_the_Web
Le 14/02/2018 à 19:17, Isuranga Perera a écrit :
> Hi All,
>
> I am Isuranga Perera, a final year undergraduate from University of Colombo
> School of Computing. I participated GSoC 2017 and worked on WS-Trust
> implementation for WSO2 Identity Server. I am looking forward to
> participate in GSoC 2018, and this project looks an exciting one for me.
>
> As the first step I went through the developer guide[2] . Currently I'm
> going through the Hao's prototype of CSW[1].
>
> Appreciate if you can guide me through next steps of the project.
>
> [1] https://github.com/haonguyen123/sis
> [2] http://sis.apache.org/book/en/developer-guide.html
>
> Best Regards
> Isuranga Perera