That would make sense indeed. But then if this is confirmed to be a wanted behavior, then we should document it explicitely somewhere
Thanks to all for your help and advice! Stéphane -- "Le mot progrès n'aura aucun sens tant qu'il y aura des enfants malheureux" -- Albert Einstein "A journey does not need reasons. Before long, it proves to be reason enough in itself. One thinks that one is going to make a journey, yet soon it is the journey that makes or unmakes you." -- Nicolas Bouvier Photos de voyages, photos de montagne: http://www.henriod.info On Thu, Sep 6, 2012 at 11:33 AM, sly (sylvain letuffe) <li...@letuffe.org>wrote: > hi, > > > but is it a bug? or am I missing the good reason why there is this factor > > 100? > > I searched the source code to find the reason why there is a x100 on > coordinate, but couldn't find where it's done. > But my guess is that for performance reasons, the field to store x/y was > chosen to be an integer instead of a float. And because rounding a > spherical > mercator to the unit would loose sub meter precision, it was stored as > multiplied by 100 for ~cm accuracy > > -- > sly > qui suis-je : http://sly.letuffe.org > email perso : sylvain chez letuffe un point org > > _______________________________________________ > dev mailing list > dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/dev >
_______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
