Re: [OSM-dev] osmarender patch - Better support for non-english/multi-lang areas

2009-03-12 Thread Dave Stubbs
2009/3/12 Eddy Petrișor eddy.petri...@gmail.com: Tal a scris: On Wed, Mar 11, 2009 at 7:37 PM, Andy Allan gravityst...@gmail.com wrote: On Wed, Mar 11, 2009 at 12:33 PM, Tal tal@gmail.com wrote: 2. Support making one tag be exactly the same as another tag using the following construct:  

[OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Grant Slater
Dear all The API downtime scheduled for the 0.6 API transition has been postponed due to delays acquiring the new database server. The re-scheduled API downtime for the 0.6 API upgrade is now the weekend of the 17-20th April 2009. Original announcement...

Re: [josm-dev] Add nodes functionality changed?

2009-03-12 Thread Martin Koppenhoefer
2009/3/10 Dirk Stöcker openstreet...@dstoecker.de: You have 3 ways to replace this: a) Press ESC instead of Shift b) Press U instead of Shift c) Double-Click to end drawing a node. For me your comments really look like I want my old way and don't even want to try others. actually for me

Re: [josm-dev] Add nodes functionality changed?

2009-03-12 Thread Stefan Breunig
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So far, only 4 people are complaining. Doesn't sound heavily used to me. About shift: Try to create a perfect T crossing with the joining way ( | ) ending *near* a node but not on one. Your joining way will look something like this \ or this /, but

Re: [josm-dev] Add nodes functionality changed?

2009-03-12 Thread Andy Robinson (blackadder-lists)
I was unaware of any proposed change on this too. I was sitting quiet as the problem and responses were provided in the list here. Basically I had the same view as David did but can see that function is provided now differently, which is fine, but if you need to count numbers complaining you can

Re: [josm-dev] Add nodes functionality changed?

2009-03-12 Thread Dirk Stöcker
On Thu, 12 Mar 2009, Martin Koppenhoefer wrote: actually for me this is valid, I was (am still) quite used to shift-usage (don't forget that adding POIs is one of our main business, that's why I doubt that just 1% users used shift that was Speaking of this. When I change stuff adding POI's is

Re: [josm-dev] Add nodes functionality changed?

2009-03-12 Thread Russ Nelson
Stefan Breunig writes: So far, only 4 people are complaining. Doesn't sound heavily used to me. Oh, I thought that proper functionality was going to be restored, so I didn't bother complaining. :-) I can see that the functionality is still there -- just hit escape between every click -- but

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Stefan de Konink
Grant Slater wrote: The API downtime scheduled for the 0.6 API transition has been postponed due to delays acquiring the new database server. So it is impossible to buy a machine for 15k? Only one response: wow! Stefan ___ dev mailing list

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Grant Slater
Stefan de Konink wrote: Grant Slater wrote: The API downtime scheduled for the 0.6 API transition has been postponed due to delays acquiring the new database server. So it is impossible to buy a machine for 15k? Only one response: wow! Took awhile to get all the quotes in and then asked for

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Grant Slater
Claudomiro Nascimento Junior wrote: Can you bring joy to our hearts describing the winning specs? Full spec here: http://wiki.openstreetmap.org/wiki/Servers/smaug Summary: 2x Intel Xeon Processor E5420 Quad Core 32GB ECC (max 128GB) 2x 73GB SAS 15k 10x 450GB SAS 15k (expensive, but stupidly

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Grant Slater
Stefan de Konink wrote: Maybe a stupid question; but is your database server able to exploit the above configuration? Especially related to your processor choice. Yes, the disks are _currently_ over spec'ed, but not for 6 month's time. Replacing the hardware for the central database server is

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Matt Amos
On Fri, Mar 13, 2009 at 1:21 AM, Stefan de Konink ste...@konink.de wrote: Grant Slater wrote: Summary: 2x Intel Xeon Processor E5420 Quad Core 32GB ECC (max 128GB) 2x 73GB SAS 15k 10x 450GB SAS 15k (expensive, but stupidly low latency) IPMI + KVM Maybe a stupid question; but is your

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Stefan de Konink
Grant Slater wrote: Large imports in the pipeline. Partitioning is a scalable solution to that, not buying new hardware. Now it is nice you put 32GB (extra expensive) memory in there, but most likely your hot performance would be far better with more (cheap) memory than more disks. At the

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Stefan de Konink
Matt Amos wrote: At the time I wrote my paper on OSM Dec2008, there was about 72GB of CSV data. Thus with lets say 128GB you will have your entire database *IN MEMORY* no fast disks required. in 8Gb kits? that would be *extra* expensive (about £8,680 according to froogle). Some people are

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Stefan de Konink
Stefan de Konink wrote: Wow... (serious wow) I have never seen the database THAT expanded unless I was using an XML database. And now I think of it; that is probably because *I* wasn't able to download the history tables. That makes sense; but does it make sense to have the history tables at

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Iván Sánchez Ortega
El Viernes, 13 de Marzo de 2009, Stefan de Konink escribió: [...] Therefore your seek times will only decrease if you can search on the individual disk not as a combined pair. I actually wonder what the DB performance could be with some of those new shiny SSD drives... (And how expensive

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Grant Slater
Stefan de Konink wrote: Stefan de Konink wrote: Wow... (serious wow) I have never seen the database THAT expanded unless I was using an XML database. And now I think of it; that is probably because *I* wasn't able to download the history tables. That makes sense; but does it make sense

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Grant Slater
Stefan de Konink wrote: Iván Sánchez Ortega wrote: El Viernes, 13 de Marzo de 2009, Stefan de Konink escribió: [...] Therefore your seek times will only decrease if you can search on the individual disk not as a combined pair. I actually wonder what the DB performance could be with some of

Re: [OSM-dev] 0.6 move and downtime (re-scheduled)

2009-03-12 Thread Stefan de Konink
Grant Slater wrote: But as detailed below by Stefan, the internal block fragmentation is a serious issue, which needs to be fixed first. I am also still very sceptical about SSD MTBF on DB server load levels. Write 1 bit = Full SSD block write. Big community site in NL reported less than a

Re: [josm-dev] Add nodes functionality changed?

2009-03-12 Thread Dirk Stöcker
On Thu, 12 Mar 2009, Russ Nelson wrote: Stefan Breunig writes: So far, only 4 people are complaining. Doesn't sound heavily used to me. Oh, I thought that proper functionality was going to be restored, so I didn't bother complaining. :-) I can see that the functionality is still there --

Re: [josm-dev] Add nodes functionality changed?

2009-03-12 Thread David Earl
On 12/03/2009 17:58, Dirk Stöcker wrote: Press ESCAPE the whole time like you did for shift. Using ESCAPE as a modifier is very unconventional. Pressing it and releasing it first has a very different feel to using a key as a modifier. I think the use to which the shift has been usurped is

Re: [josm-dev] Add nodes functionality changed?

2009-03-12 Thread Stefan Breunig
Oh, I thought that proper functionality was going to be restored, so I didn't bother complaining. :-) Does anyone actually read my mails? It's really annoying to repeat over and over again just because you can't take 10 minutes and read this thread and see that your complaints are unreasoned.