The largest lists on nl-wiki where around 1200 or 1600 monuments (400-600kb)> with on a regular computer loading times form 30-100 sec. I tried once to make the list from amsterdam as 1 to split it up (7000 monuments). But every time you tried visiting it your browsers crashed. The lines for the tables in the dutch wiki where generated with a robot. Then we had them sorted by city, and with a little programm we generated the municipality lists. Then by hand we putted them al in lists on the dutch wiki. Taking around 10-30 minutes per list. Mainly al the links from the cityarticles and redirects took the most time. After that loads of people have filled in missing information. Building dates and Object descriptions. http://nl.wikipedia.org/wiki/Gebruiker:Rudolphous/RijksmonumentenTeller there you can find a counter which collects the data from the lists, so that you can see where there is work to be done. (at bottom of the page is most interessting data. If you have any questions about dutch structure of lists, or how we tackled other problems on the dutch project: feel free to ask. 

Mvg, 

Bas(vb)

> From: lodewijk@effeietsanders.org
> Date: Sat, 12 Feb 2011 22:50:19 +0100
> To: wikilovesmonuments@lists.wikimedia.org
> Subject: Re: [Wiki Loves Monuments] Working on Spain lists
>
> Hi,
>
> if it is possible to create it, it is impossible to load it without
> craching your browser.
>
> In NL we split up the table to a municipality level, and where
> possible even further. In some cities we even ended up on street
> level. As long as there is a good category and linking structure, that
> should be doable and scalable. Does that answer your question?
>
> Lodewijk
>
> 2011/2/12 Tomasz Ganicz <polimerek@gmail.com>:
> > 2011/2/12 Lodewijk <lodewijk@effeietsanders.org>:
> >> Hi,
> >>
> >> I dont know if this is in scope with Commons - but if it is, be bold
> >> and do it there (I'll leave that question to the commons specialists).
> >> Otherwise you could of course do the same taking one language as core
> >> project and copying it to the others from there - but I can imagine
> >> that is politically sensitive.
> >>
> >> I would suggest to add some more information in the templates, even
> >> though you dont have that info yet. For example: year that the
> >> building was built, architect and address. If you dont have the info,
> >> leave it blank, but then people can add the info if they like.
> >>
> >
> > I am just wondering if it is technically possible to create a
> > wiki-table with 60 000 entries (or more - as in Germany as I remember
> > the list has 250 000 + entries) - and even if it is technically
> > possible - effective maintaining and browsing such a table is going to
> > be really hard...  I guess - if geotagging is available it would be
> > more clever to organise a POI-style data-base which could be used as a
> > slice on Google maps and/or OSM. One could then choose of his/her
> > starting point and see on the map all monuments.
> >
> >
> > --
> > Tomek "Polimerek" Ganicz
> > http://pl.wikimedia.org/wiki/User:Polimerek
> > http://www.ganicz.pl/poli/
> > http://www.cbmm.lodz.pl/work.php?id=29&title=tomasz-ganicz
> >
> > _______________________________________________
> > Wiki Loves Monuments mailing list
> > WikiLovesMonuments@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments
> > http://www.wikilovesmonuments.eu
> >
>
> _______________________________________________
> Wiki Loves Monuments mailing list
> WikiLovesMonuments@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments
> http://www.wikilovesmonuments.eu