I would prefer to keep the source tag with the object. Within a changeset I will often have some roads where source is GPS, have traced some buildings from bing, and added a few pub/shop names where source is survey
Phil -- Sent from my Nokia N9 On 28/09/2012 8:55 Shaun McDonald wrote: I know. My thinking is that the source tag would be better placed on the changeset rather than polluting the whole db with source tags and source tags for each and every tag on each object which is starting to happen. You can then use the changeset info to synthesise the source info down to the tag and geometry. Shaun On 28 Sep 2012, at 08:47, Richard Mann <richard.mann.westoxf...@gmail.com> wrote: They're not allowed to. The licence requires them to put it on the object. On Fri, Sep 28, 2012 at 8:35 AM, Shaun McDonald <sh...@shaunmcdonald.me.uk> wrote: On 28 Sep 2012, at 06:25, THEVENON Julien <julien_theve...@yahoo.fr> wrote: > > > > > > ------------------------------ > Le jeu. 27 sept. 2012 20:18 HAEC, Sarah Hoffmann a écrit : > >>> This is the real problem for us. >> >> For the sake of completeness: planetwide there are currently >> 152 million objects. Which means 1/6th of the planet consists of >> French buildings. Now, there is a real problem. >> > Hi Sara, > > concerning problem of disk usage by french cadastre data do you have some > information?particulary do you know how is it stored in database? > to be allowed to use cadastre data we have to add a source key which is long > about 40 characters to each way drawn thanks cadastre data due to legal > agreement with french office goverment providing cadastre data. > do you know is this key is duplicatd for each building in the database or if > there is a smart storage? if not it would be interesting to know which part > of the size is for the key itself and which part is for the geometry. I think > that for buildings composed of one way and 4 nodes the space required by the > could be greater than for geometry. > if this is the case there is perhaps a way to factorise the source key and > dramatically reduce disk usage. The way to reduce the disk space for stuff imported in the future is to store that source once on the changeset instead. Shaun _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
