File: opensearch.rst

package info (click to toggle)
pycsw 2.6.0%2Bdfsg-1
  • links: PTS, VCS
  • area: non-free
  • in suites: bullseye
  • size: 10,980 kB
  • sloc: xml: 38,300; python: 11,330; makefile: 179; sh: 3
file content (30 lines) | stat: -rw-r--r-- 1,410 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
.. _opensearch:

OpenSearch Support
==================

pycsw supports the `OGC OpenSearch Geo and Time Extensions 1.0`_ standard via the following conformance classes:

- Core (GeoSpatial Service) ``{searchTerms}``, ``{geo:box}``, ``{startIndex}``, ``{count}``
- Temporal Search core ``{time:start}``, ``{time:end}``

OpenSearch support is enabled by default.  HTTP requests must be specified with ``mode=opensearch`` in the base URL for OpenSearch requests, e.g.:

.. code-block:: bash

  http://localhost/pycsw/csw.py?mode=opensearch&service=CSW&version=2.0.2&request=GetCapabilities

This will return the Description document which can then be `autodiscovered <https://github.com/dewitt/opensearch/blob/master/opensearch-1-1-draft-6.md#Autodiscovery>`_.

.. _`OGC OpenSearch Geo and Time Extensions 1.0`: http://www.opengeospatial.org/standards/opensearchgeo

OpenSearch Temporal Queries
---------------------------

By default, pycsw's OpenSearch temporal support will query the Dublin Core ``dc:date`` property.  To
enable temporal extent search, set ``profiles=apiso`` which will query the temporal extents of
a metadata record (``apiso:TempExtent_begin`` and ``apiso:TempExtent_end``).

At the HTTP API level, time is supported via one of ``time=t1/t2`` or ``start=t1&stop=t2``.  If the
``time`` parameter is present, it will override either/both of the ``start`` and ``stop`` parameters
respectively.