Jo,
> Any objections?
I'm +1 on deprecating {geo:locationString?} in favour of {geo:name?}.
But I doubt on the need for {geo:geometry} parameter, defined simply
as a "Well-Known Text" expression. Well Known Text syntax [1] provides
for many geometry types: point, linestring, polygon, triangle,
polyhedralsurface, TIN, multipoint, multilinestring, multipolygon and
geometrycollection; either in 2D or 3D, and optionally with linear
referencing. I question if this expressiveness is necessary, as
probably we won't need polyhedralsuface or 3D filtering.
So I ask if it would'nt be better to add a simpler {geo:multipolygon?}
parameter, coherent with the {geo:polygon} syntax, to cover the need
you addressed in the GENESI-DR project. And get rid of unnecessary
complexity.
If the case we decide that it is worth using a 'geometry' WKT
parameter, we could explicitly state in the wiki which of the
geometric expressions are meant to be supported. For instance, 2D-only
geometries: point, linestring, polygon, multi-idem, and
geometrycollection. In this case, I propose to deprecate the
{geo:polygon} parameter, to avoid redundancy and geometry
serialization syntax incoherences across parameters.
Any other thoughts?
> I don't know how to update the page at
>
http://www.opensearch.org/Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2
If you are uncomfortable with wiki markup, send me the modifications
and I'll add them.
Cheers,
Oscar.
---
[1] HERRING, J. R. (editor) (2006) “OpenGis® Implementation
Specification for Geographic information – Simple feature access –
Part 1: Common architecture. Version 1.2.0” Open Geospatial Consortium
Inc. Ref. OGC 06-103r3. Chapter 7: Well-known Text Representation for
Geometry.
http://www.opengeospatial.org/standards/sfa#downloads
(pp.53-63)
---
2010/5/4 Jo Walsh <
meta...@gmail.com>:
> dear all,
>
> I would like to make some changes to the Draft 2 version of OpenSearch Geo
> extensions (and change the main link to the updated draft).
>
> Discussion of / background to the proposed changes is here:
>
http://unlock.posterous.com/opensearch-geospatial-in-progress
>
> In short this would involve adding the geo:geometry property and geo:name ,
> deprecating the use of geo:locationString, that would bring the whole thing
> in line with the version in the Open Geospatial Consortium CSW "part
> document".