On Wed, 12 Nov 2008, Tomas Kolda wrote:
> So once more. It was just note between float and int
Ok :) I understood. But a argumented foundation of the claims next to 'it
works better on embedded' doesn't seem wrong to me.
Stefan
___
dev mailing l
On Tue, Nov 11, 2008 at 10:12:30AM +, Dave Stubbs wrote:
> You may not be meaning it like this, however it doesn't come across as
> constructive criticism, but as a collection of insulting comments. And
> you just compounded it.
Ok, people were offended. Consider this a public apology to all
I'm not so good in English, so maybe you do not understand my note. I
like koeficient 1e7, because it is human readable form of coordinate
13.5 -> 13500. I do not want to use (2^32/360).
I just react to difference between float and int. float has only 24 bits
of significant which will resu
On Wed, 12 Nov 2008, Tomas Kolda wrote:
> Integer has better precision if you are far from zero, because floats
> use only 24 bits for significant, other bits is for sign and exponent.
> So 32 bit integer is better if you know extends (-180, 180). Min
> and max of int is -2.1e9 to 2.1e9. So i
Integer has better precision if you are far from zero, because floats
use only 24 bits for significant, other bits is for sign and exponent.
So 32 bit integer is better if you know extends (-180, 180). Min
and max of int is -2.1e9 to 2.1e9. So if you multiply longitude and
latitude by 1e7
Hello Robert,
as far as I understand it the OSM-databases store the location
in long integers anyway. Thus there is no precision to be gained
from using floats. You only loose storage-space, computation-time
and native functionality on platforms that do not have native floating-
points (like many
hello,
im wondering if anyone here is familiar with rendering osm through
mapnik?Particularly, anyone knows how to render circles? is it through
node-ways or
it can be done through the rules?
___
dev mailing list
dev@openstreetmap.org
http://lists.openst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan de Konink wrote:
> At #osm-nl we ar discussing the float -> long thing. I used floats
> because it (obviously) allows more precision, but I agree on some points
> mentioned before.
Floats only allow more precision as the location being consid
Dirk-Lüder Kreie wrote:
> What do you use to calculate the maxX (trivial) and maxY coordinates
> for the tiles?
> There might be a hidden rounding error.
>
> All projection code used for [EMAIL PROTECTED] is in svn:
> http://svn.openstreetmap.org/applications/rendering/tilesAtHome/lib/tahproject.p
As of now it also supports ordered relations so make sure you update svn
or download the latest version 0.29.4.
Brett Henderson wrote:
> Hi All,
>
> Osmosis is now API 0.6 ready. Preferably use the version in svn,
> although the latest interim version is currently linked to from the
> API 0.6
> Hi recently I've uploaded all the borders for Italy as written here:
> http://wiki.openstreetmap.org/index.php/Italian_Borders
Thank you, that's great. I've just checked the data and there's not even a
single bug in the data.
> now I would like to do the opposite, so being able to obtain a lis
On Tue, Nov 11, 2008 at 1:15 AM, Simon Ward <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 09, 2008 at 10:30:25AM +, Andy Allan wrote:
>> On Sun, Nov 9, 2008 at 3:48 AM, Simon Ward <[EMAIL PROTECTED]> wrote:
>>
>> > Stop making it more complex by introducing arbitrary limits
>> > because of technical
12 matches
Mail list logo
