[mapserver-dev] FW: [OSGeo-Discuss] OSGeo has been accepted at Google Summer of Code!

[Olivier Courtin]

> Selon Olivier Courtin <olivier.courtin at oslandia.com>:
> 
>> WFS and Filter Encoding are really closes to SQL concepts (in fact it's just
>> a Web Service API in front of a Spatial Database)
>> 
>> So i don't think that using OGR will bring us all the expressivity of plain SQL.
> 
> I don't see a problem here. OGR justs forwards SQL requests to the RDBMS own SQL
> engine when it is available (otherwise OGR has its own generic simplistic SQL
> engine, but without any spatial support currently, other than bounding box
> intersection through the SetSpatialFilter() API). So if you target OGR backends
> that are RDBMS with SQL/MM support, that should be OK. The part that translates
> Filter Encoding to SQL/MM would be done in a generic way in TinyOWS.

Well it shows that i don't know OGR deeper enough ! 

Do you have a vision of FE support in OGR ?
(i.e 1.0, 1.1 and 2.0 versions ?, partial or full ?, is there also a way to add new 
SQL functions mapping ?)  


>> And also maybe we will loose a bit of performances rather than a direct
>> database
>> access.
> 
> Hum, we are talking about client/servers that interact through the Web, so I
> doubt the OGR overhead makes a significant difference.

It had to be benched :)

--
Olivier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20120321/572b7146/attachment-0001.html