Andrew M. Bishop a...@gedanken.demon.co.uk wrote:
If using the standard toolchain of osm2psql, postgresql and mapnik
what is the minimum software versions that are needed to continue
creating maps after ids reach 2^31-1?
osm2pgsql supports 64bit id space already for a long time. But since
On 08.02.2013 06:59, Ilya Zverev wrote:
Though I fail to understand what would be broken if you continue to use
32-bit osm2pgsql. Indices, maybe.
don't be confused by the term 32-bit. It is required that the software
can handle 64-bit data types for processing the node id. In postgresql
it
A while ago I announced that I have newly compiled windows versions of
osm2pgsql (Intel C++ Compiler XE 13.0, MS Visual Studio 2010). After my
last build someone added the no_fork option (thanks!) which made my life
easier. Compared to the master version, I basically only needed to
remove the
Stephan Knauss wrote:
could you give details about a use case where mapnik needs the
osm_id?
The official styles do not contain a reference to osm_id, it's an
internal thing in the database.
Or is it going into using osm directly as a datasource instead of
postrgres?
While it is possible
Stephan Knauss o...@stephans-server.de writes:
On 06.02.2013 21:25, Andrew M. Bishop wrote:
Does anybody know if there is a released version of Mapnik that
supports ids up to (2^32)-1 rather than requiring an unreleased 64-bit
version?
could you give details about a use case where mapnik
Andrew M. Bishop wrote:
If using the standard toolchain of osm2psql, postgresql and mapnik
what is the minimum software versions that are needed to continue
creating maps after ids reach 2^31-1?
I doubt that mapnik's handling of 32bit ids would in any way affect OSM
rendering. So you can
FYI, I have dubbed this the N2B (Node 2 Billion(ish)) problem :)
Just think what would happen if we could get 1/1000th the media
coverage of Y2K...
Toby
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
From: Ilya Zverev [mailto:zve...@textual.ru]
Subject: Re: [OSM-dev] Reminder: Node 32-bit exhaustion
Well, you've got less than 24 hours to update your osm2pgsql.
http://textual.ru/64/ shows that there are 1.3 million nodes left, and
for the last two days nearly 1.5 million nodes were added
Andrew M. Bishop wrote:
Since 2^31 nodes will make older versions of some software unusable
and 2^32 nodes will make other versions unusable it would be helpful
to have a wiki page to record this information. I think that most
useful would be a table of the minimum version of each piece of
Stephan Knauss o...@stephans-server.de wrote:
How do I find out how many bits my server OS has?
A portable ANSI C code for bitsize detection would be this one:
#include stdio.h
#include stdint.h
int main() {
printf(%d\n,8*sizeof(uintptr_t));
return(0);
}
I'm using the size of an unsigned
Ilya Zverev zve...@textual.ru writes:
Andrew M. Bishop wrote:
Since 2^31 nodes will make older versions of some software unusable
and 2^32 nodes will make other versions unusable it would be helpful
to have a wiki page to record this information. I think that most
useful would be a table
On 06.02.2013 21:25, Andrew M. Bishop wrote:
Does anybody know if there is a released version of Mapnik that
supports ids up to (2^32)-1 rather than requiring an unreleased 64-bit
version?
could you give details about a use case where mapnik needs the osm_id?
The official styles do not
On Mon, Feb 04, 2013 at 06:34:46PM -0800, Paul Norman wrote:
As of right now, we are 5.31 million nodes away from hitting our 2^31th
node. This is likely to cause some software to break. Hopefully everything
major has been tested, but if you haven't checked your software now would be
a good
Paul Norman penor...@mac.com writes:
As of right now, we are 5.31 million nodes away from hitting our 2^31th
node. This is likely to cause some software to break. Hopefully everything
major has been tested, but if you haven't checked your software now would be
a good time to do so. I think
Hello Andrew,
On 05.02.2013 21:13, Andrew M. Bishop wrote:
Since 2^31 nodes will make older versions of some software unusable
and 2^32 nodes will make other versions unusable it would be helpful
to have a wiki page to record this information. I think that most
useful would be a table of the
On Wed, Feb 6, 2013 at 7:13 AM, Andrew M. Bishop
a...@gedanken.demon.co.uk wrote:
Since 2^31 nodes will make older versions of some software unusable
and 2^32 nodes will make other versions unusable it would be helpful
to have a wiki page to record this information. I think that most
useful
On 06.02.2013 00:17, Steve Bennett wrote:
I might be pointing out the obvious here, but isn't the bigger risk
that some software will fail silently rather than catastrophically?
Like, an editor tries to save node 2^32+100, and saves it as 100, or
something?
It is, but API requires you to
As of right now, we are 5.31 million nodes away from hitting our 2^31th
node. This is likely to cause some software to break. Hopefully everything
major has been tested, but if you haven't checked your software now would be
a good time to do so. I think coastcheck will break in substantial
Paul,
Thanks for the reminder, though you may want to check your math here.
Ether the nodes per day is off or the expected exhaustion date is off!
Skye Book
On Feb 4, 2013, at 9:36 PM, Paul Norman penor...@mac.com wrote:
As of right now, we are 5.31 million nodes away from hitting our 2^31th
19 matches
Mail list logo
