RESTo - restful semantic search tool for geospatial
0 likes1,706 views
Resto is a RESTful semantic search tool designed for geospatial data, following the OGC OpenSearch extension for Earth Observation architectures. It features a PostgreSQL backend with PostGIS, allowing for metadata ingestion, resource management, and multilingual search capabilities. The system includes a query analyzer for translating natural language queries into search parameters, and provides a range of functions for collection management and resource tagging.
RESTo - restful semantic search tool for geospatial
- 1. RESTorestful semantic search tool for geospatial Jérôme Gasperi
- 2. RESTo - restful semantic search tool for geospatial is an implementation of OGC13-026 OpenSearch Extension for Earth Observation
- 3. Architecture PostgreSQL Gazetteer Collection Manager Resource Manager Query Storage Query Analyzer RESTo modules More to come... RESTo backend PostGIS hstore uses RESTofrontend mapshup iTag Core RESTo External services resto db EO collections * (*) Collections can be stored within RESTo database or in external databases PHP javascript PHP
- 4. RESTo Services Admin https POST Ingest metadata INGEST ScriptsDownload http GET THEIA metacatalog HMA catalog CEOS http GET (ATOM, GeoJSON) User http GET SEARCH (HTML)
- 5. R R Rreliablerestful responsive
- 6. Rrestful
- 7. GET / List all collections POST / Create a new collection GET /collection/$describe Describe collection OpenSearch service GET /collection Search collection POST /collection Insert a resource within collection DELETE /collection Delete collection PUT /collection Update collection GET /collection/identifier Show resource metadata GET /collection/identifier/$download Download resource product
- 8. Rresponsive
- 9. DesktopsTabletsMobiles 0 to 500 px 501 to 959 px 960 to > 1280 px
- 10. Rreliable
- 11. Time period of 1 month within a 10x10 km2 box SEARCH INGEST 0.2s 0.5s 1 000 000 SPOT DATABASENew products retrieved every 3 hours from ADS catalog Per product for a ~5000 products ingestion Order of magnitude compute on a Dual Core 2.6 GHz | 4 Go RAM | HDD 500 To
- 14. During ingestion process , resources are automatically tagged with location and land use github.com/jjrom/itag
- 15. ! Tag this footprint with continent, country and Land use ! http://goo.gl/WtbcbR iTag
- 16. Additionally, conditional ingestion rules can be defined at the collection level to provide specific tags Add tags #mh370,#plane,#malaysianairline to resources acquired between 2014, march 8th and 2014, april 14th in the south of the Indian Ocean ! http://goo.gl/W8VlPV e.g.
- 18. RESTo provides semantic search capabilities It uses a Query Analyzer to translate natural language query into a set of EO OpenSearch parameters
- 19. Query Analyzer goodies Multilingual - current languages are EN, FR, IT and DE Synonyms supported (e.g. unit «m» is «m», «meter» or «meters») Each collection can define its own dedicated keywords Automatic typing error correction using similarity Embed a Gazetteer containing ~9 000 000 toponyms
- 20. « Images of urban area in the US acquired in the last 10 days with less than 5 % of cloud cover » Example
- 21. « Images of urban area in the US acquired in the last 10 days with less than 5 % of cloud cover » Example keyword location date acquisition parameter
- 22. 2. Each search result has an « human readable url » that can be indexed by web crawler (i.e. google robots) 1. Search parameters are derived from Natural Language query 3. Keywords on resources are links to search requests : they can be indexed by web crawler…and so on Search (example)
- 23. 2. Each search result has an « human readable url » that can be indexed by web crawler (i.e. google robots) 1. Search parameters are derived from Natural Language query 3. Keywords on resources are links to search requests : they can be indexed by web crawler…and so on Search (example) http://goo.gl/GvMEHj