Changes between Version 5 and Version 6 of ExtendedRegions


Ignore:
Timestamp:
11/12/12 08:01:13 (12 years ago)
Author:
jesseeichar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ExtendedRegions

    v5 v6  
    2020 * Add optional geometry for each region (in addition to bbox)
    2121 * integrate into !XmlSearch and Csw so that the region id can be used to look up the geometry of the region for a spatial filter
    22  * Add a configurable strategy object for that allows the region implementation to be easily pluggable.  For example it might be based on a table in the database or wfs
     22 * Add a configurable strategy object for that allows the region implementation to be easily pluggable.  For example it might be based on a table in the rdf file or wfs
    2323
    2424=== Proposal Type ===
    … …  
    5151  * Example Response:
    5252{{{
    53 <response>
    54   <record>
    55     <id>338</id>
     53<regions>
     54  <region id="338" hasGeom="false" categoryId="continent">
    5655    <north>38.2</north>
    5756    <south>-34.6</south>
    … …  
    7271      <ita>Africa</ita>
    7372    </label>
    74     <category>continent</category>
    75     <hasGeom>false</hasGeom>
     73    <category>
     74         <fre>Continent</fre>
     75         <eng>Continent</eng>
     76    </category>
    7677  </record>
    7778</response>
    … …  
    8586{{{
    8687<regions count="1">
    87   <region>
    88     <id>country.1</id>
     88  <region id="country.1" hasGeom="true" categoryId="country">
    8989    <label>
    9090      <eng>France</eng>
    9191    </label>
     92    <category>
     93         <fre>Pays</fre>
     94         <eng>Country</eng>
     95    </category>
    9296  </region>
    9397</regions>
    … …  
    9599 * !GetGeom - will return the geometry for the region. If the geometry does not have a geometry then the bbox will be used to construct a polygon.
    96100  * Params
    97    * id - required (if multiple are provided then multiple geometries will be returned)
     101   * id - required
    98102   * simplified - optional (if present and true then the geometry will be a simplified version.  Some implementations may ignore this hint and return full geometry)
    99103  * Example Response:
    100104{{{
    101 <response>
    102   <geom id="2"> MULTIPOLYGON (((30 20, 10 40, 45 40, 30 20)), ((15 5, 40 10, 10 20, 5 10, 15 5)))</geom>
    103   <geom id="3"> MULTIPOLYGON (((30 20, 10 40, 45 40, 30 20)), ((15 5, 40 10, 10 20, 5 10, 15 5)))</geom>
    104 </response>
     105  MULTIPOLYGON (((30 20, 10 40, 45 40, 30 20)), ((15 5, 40 10, 10 20, 5 10, 15 5)))
    105106}}}
     107 * !GetMap - return a rendering of the geometry as a png.  If no background is specified the image will be a transparent png
     108  * id - required
     109  * srs - (optional) default is EPSG:4326 otherwise it is the project to use when rendering the image
     110  * width - (optional) width of the image that is created.  Only one of width and height are permitted
     111  * height - (optional) height of the image that is created.  Only one of width and height are permitted
     112  * background - URL for loading a background image for regions.   A WMS Getmap request is the typical example.  The URL must be parameterized with the following parameters:
     113   * minx
     114   * maxx
     115   * miny
     116   * maxy
     117   * width
     118   * height
     119   * srs (Optional)
    106120
    107121The !XmlSearch API will be modified so the geom parameter can either be WKT or have the form: region:id, where id is the id of the region to use as a geometry.  If the region has a geometry then that geometry will be loaded otherwise the bbox will be used to create a polygon geometry.