[TinyOWS-dev] Some thoughts and question

[Nicklas Avén]

Great Olivier :-)

Sorry I haven't answerd your previous post, but I intended to work
through my answer more than I had time too.ot had time to sit down
experimenting again. 

But I will. I have some idea about setting up a test server with quite
huge datasets.
Seving TMS through mapproxy or something similar from mapserver. And
then, when the user wants to edit, he gets a wfs layer from tinyows from
only that extent, layed over the tiles. 

I have also thought about the possibility to only request the one
geometry that the user wants to edit. Would that be possible? 

Then, about getting attribute information from the tables, why not take
the user input point or box from information tool and query postis
directly? 

With this upset, the PostGIS server will get a lot of work when seeding
the tiles. Then it has a lot extra capacity to deliver wfs-services
through tinywfs and answer attribute questions when mapproxy or some
other tilecahce handles the most common panning and zooming. 

It is from this perspective it is nice if tinyows can pick out the very
extent or even the very exact geometry that the user wants.

I will get back after some testing. 


Here is also a very interesting blog post about different payloads with
different formats:
http://www.tokumine.com/2010/09/20/gis-data-payload-sizes/


Regards
Nicklas



On Wed, 2011-03-02 at 01:27 +0100, Olivier Courtin wrote:
> On Feb 20, 2011, at 9:20 PM, Nicklas Avén wrote:
> 
> Nicklas,
> 
> > My layer was quite big, about 400 mb as shape-file
> > with 1.6 million polygons. When I made a getcapabilities request the
> > server started to calculate the extent of the whole layer which takes
> > some time.
> 
> I've rewrited the SQL query related to this feature.
> and added an estimated_extent option (default is now true)
> 
> The performance increase is huge on big layers, for GetCapabilities  
> request.
> 
> Thanks a lot for this report !
> 
> Commited as r352.
> 
> --
> Olivier
> _______________________________________________
> TinyOWS-dev mailing list
> TinyOWS-dev at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/tinyows-dev
>