[Tilesathome] Some First Day Stats

[Dodi]

Hi,

we can have some measure to identify "too_complex_tiles", per client basis, 
for example "I have only 512 MB RAM, when downloaded osm file size is over 2 
MB it is too_complex_tile_for_me " ...

then we can split downloaded osm file using 
http://svn.openstreetmap.org/applications/utils/osm-extract/polygons/extract-polygon.pl
in bbox mode with reference integrity preserved  into 2,4,8 or 16 
horizontal stripes (based on measure)  for zoom levles  15 to 17, before 
xml2svg transformation....

t at h client calls  inkscape for z15  8-times with fullsize SVG and exports 
only one strip with full width and only 1/8 of height (same for z16, but 16 
stripes, and for z17 with 32 stripes)

while preserving current workflow, we can reduce svg by splitting 
source/downloaded osm data into stripes (of course with some border )..and 
doing xml2svg transformations for each strip...

Dodi

----- Original Message ----- 
From: "Brent Easton" <b.easton at exemail.com.au>
To: "Johan Thelmén" <jth at home.se>
Cc: <tilesathome at openstreetmap.org>
Sent: Friday, November 09, 2007 7:46 AM
Subject: Re: [Tilesathome] Some First Day Stats


Hi Johan,

That's one possiblity. Once the initial .osm file has been downloaed, the 
client could perhaps use some sort of rule of thumb to determine if it can 
attempt it.

The disadvantage of course is that the client has download the data from OSM 
before it can reject it. High resource tiles might bounce around several 
clients, all downloading the data and rejecting it before one eventually 
processes it.

Perhaps the too_complex_for_me for me response by the first client back to 
the client could include a 'complexity' rating that the server then attaches 
to the request, and then from then on, that request can only be handed out 
to 'high resource' configured clients. Perhaps the server could even record 
that in a db for future reference? (The land/sea/mixed status could be 
recorded there also???).

Just ideas to toss around,

Cheers,
Brent.



*********** REPLY SEPARATOR  ***********

On 9/11/2007 at 7:27 AM Johan Thelmén  wrote:

>fredagen den 9 november 2007 skrev Brent Easton:
>> I'm not sure how we go about fixing this. Somehow, some tilesets need to
>be indentified as
>> 'high resource' and only be distributed out to clients that indicate
>that can process these.
>> Similiarly, slients with < 1GB can usefully render many tiles, but will
>fail to render 'medium'
>> or 'high' resource tiles. It is very wasteful to even hand them out to
>low RAM clients.
>
>After the client downloads the data maybe it could estimate with current
>memory if it could render
>the tilset or otherwise hand it back to the server with error
>too_complex_for_me.
>
>-- 
>Johan Thelmén
>Sweden Falun
>
>
>-- 
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.503 / Virus Database: 269.15.26/1119 - Release Date: 8/11/2007 
>5:55 PM


____________________________________________________________
Brent Easton
Analyst/Programmer
University of Western Sydney
Email: b.easton at uws.edu.au


_______________________________________________
Tilesathome mailing list
Tilesathome at openstreetmap.org
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome