[Tilesathome] t at h, my plans/priorities

Frederik Ramm frederik at remote.org
Mon Aug 6 10:38:12 BST 2007


Hi,

> So say that you upload z12-15 on an area that someone has already  
> uploaded
> z12-17.  And let's say that this metainfo is stored under the  
> database key
> "x,y,12", i.e. it's tied to the top-level tile.*
[...]
> * Alternatively, you can store meta-info under the key "x,y,z1,z2"  
> which has a
> similar set of problems

That's what I was proposing to do. You'd then have two metadata  
records in the db, one for z12-17 (older) and one for z12-15 (newer)  
and on lookup you need to grab the newest applicable. A nightly  
cleanup job could mop up those records that are completely  
"overshadowed" by newer ones, or you could do this upon insert.

I don't see too much database effort with that but maybe I am  
overlooking something?

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00.09' E008°23.33'






More information about the Tilesathome mailing list