Re: [OSM-dev] Ways with 40k nodes, was: osmosis pgsql schema

On Fri, Oct 31, 2008 at 12:55 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Andy Allan wrote: >> No, hang on, that would be daft. I'd be better off making subtrees >> limited to about 1000 nodes or thereabouts, to improve the efficiency >> of partial checkouts. So then I would have sensibly siz

Re: [OSM-dev] Ways with 40k nodes, was: osmosis pgsql schema

On Fri, Oct 31, 2008 at 2:53 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> quick question: if your schema used ordered relations instead of ways, >> do you have an unordered relation type as well? > > That is a client rendering issue. The order

Re: [OSM-dev] Ways with 40k nodes, was: osmosis pgsql schema

On Fri, Oct 31, 2008 at 3:19 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> would you represent a Y-shaped road as three relations, then? one for >> the left fork, one for the right stem as a way-relation, then another >> to group them toget

Re: [OSM-dev] Ways with 40k nodes, was: osmosis pgsql schema

On Fri, Oct 31, 2008 at 4:06 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> i don't understand what you mean by a pyramid shape. the relations >> would be returned in the same order, regardless of the role tag, >> right? and you're not

Re: [OSM-dev] HEADS UP osmosis pgsql schema users Was: psql osmosis simple shema / smallint out of range

On Mon, Nov 3, 2008 at 6:47 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote: > If the only thing that connects two objects is that they have a common > property, I'd say a relation is not the way to model that. i think you're right. mathematically speaking, set membership by shared properties and expl

Re: [OSM-dev] arbitrariness of relations [was: HEADS UP osmosis pgsql schema users]

On Tue, Nov 4, 2008 at 3:58 PM, Roland Olbricht <[EMAIL PROTECTED]> wrote: > Thus, the following things happen > - people convert data from one representation to another, while other people > just convert it the other way back - looks a little bit like an edit war > - a lot of code in any piece o

Re: [OSM-dev] The wiki defines the database (was: relations)

On Tue, Nov 4, 2008 at 10:46 PM, Erik Johansson <[EMAIL PROTECTED]> wrote: > COn Tue, Nov 4, 2008 at 6:16 PM, Richard Fairhurst <[EMAIL PROTECTED]> wrote: >> The people doing the "defining" are, in many cases, not the ones who >> are doing the mapping. There are plenty of people voting on things >>

[OSM-dev] Relation bounding boxes

what is the bounding box of a relation? i ask because i'm trying to implement the last bit of the changeset bounding box handling code. bounding boxes for nodes and ways are simple, but there are several plausible and possibly useful ways of dealing with relations: 1) adding or removing nodes or

Re: [OSM-dev] Relation bounding boxes

On Wed, Nov 5, 2008 at 10:20 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> >> what is the bounding box of a relation? > > I like your idea 1 best: awesome, although that is the most complicated method :-) its implemented in the code now and ther

Re: [OSM-dev] XML Schema

On Fri, Nov 7, 2008 at 12:36 PM, Hugh Barnes <[EMAIL PROTECTED]> wrote: > Does this still need doing? (I'll help) Do we literally intend to use XML > Schema (count me out if so) or do we mean just a schema for the XML (small > "s") ? yes, it still needs doing. i think it means schema with a small

Re: [OSM-dev] BUG: unescaped & in osm xml files

On Mon, Nov 10, 2008 at 3:30 PM, Rene Wunderlich <[EMAIL PROTECTED]> wrote: > i found follow XML bug in the osm xml files > > timestamp="2008-07-14T21:31:30Z"> > > the & is not escaped to & at Tileset (12,2234,1419) around 48.25,16.39 how are you downloading this file? i found that the following

[OSM-dev] new in api 0.6 today

there's a new migration in the api 0.6 branch to add "close time" and number-of-elements support for changesets. this allows the server to enforce the limits on the duration and size of changesets as mentioned on the wiki [1]. all the auto-closing stuff has been implemented and some of it has been

Re: [OSM-dev] Lean and mean Tile- and XML-API-Server

On Fri, Nov 21, 2008 at 1:07 AM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Stefan Keller wrote: >> Would'nt it be worthwhile to rewrite everything in a single well known >> language (like Ruby or Java)? iirc, the only thing in a "weird" language is osmxapi which, as you point out, is written i

Re: [OSM-dev] Lean and mean Tile- and XML-API-Server

On Fri, Nov 21, 2008 at 11:45 AM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> >> "premature optimisation is the root of all evil" ;-) > > A premature optimisation would be starting with integers, C, and more. premature optimisation would

Re: [OSM-dev] Lean and mean Tile- and XML-API-Server

On Fri, Nov 21, 2008 at 2:06 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> On Fri, Nov 21, 2008 at 11:45 AM, Stefan de Konink <[EMAIL PROTECTED]> >> wrote: >>> Matt Amos wrote: >>>> >>>> "premature optimisat

Re: [OSM-dev] Lean and mean Tile- and XML-API-Server

On Fri, Nov 21, 2008 at 2:22 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> ah well, thats the price you pay for being able to easily write code >> without having to manage memory manually (or stick shared_ptr<> all >> over the place). the

Re: [OSM-dev] Lean and mean Tile- and XML-API-Server

On Fri, Nov 21, 2008 at 3:42 PM, Dave Stubbs <[EMAIL PROTECTED]> wrote: > 2008/11/21 Stefan de Konink <[EMAIL PROTECTED]>: >> Don't waste your time on a language that does 90% for you >> sadly has no compiler to native machine code. i'd have said the same thing about javascript a couple of years a

Re: [OSM-dev] Lean and mean Tile- and XML-API-Server

On Fri, Nov 21, 2008 at 4:37 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> On Fri, Nov 21, 2008 at 3:42 PM, Dave Stubbs <[EMAIL PROTECTED]> >> wrote: >>> 2008/11/21 Stefan de Konink <[EMAIL PROTECTED]>: >>>> >>

Re: [OSM-dev] Lean and mean Tile- and XML-API-Server

On Fri, Nov 21, 2008 at 5:42 PM, Dave Stubbs <[EMAIL PROTECTED]> wrote: > This isn't about being lazy, this is about getting things done in a > tractable amount of time, and putting in the effort where it's most > worth it. thats what i call laziness! laziness is often *good* for programmers (as l

Re: [OSM-dev] Lean and mean Tile- and XML-API-Server

On Fri, Nov 21, 2008 at 7:53 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> and ensure that no functionality is lost (e.g: user diaries, comments, >> friends, etc...). i don't use these features, but there are people who >> like them. >

Re: [OSM-dev] Data corruption :) II

On Mon, Nov 24, 2008 at 12:42 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Minutely diffs work perfect. The NL crew is already creating a minutely > diff tile cache invalidator; where statitics were already implemented. http://svn.openstreetmap.org/applications/utils/export/tile_expiry/ chee

Re: [OSM-dev] Data corruption :) II

On Mon, Nov 24, 2008 at 2:50 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> On Mon, Nov 24, 2008 at 12:42 PM, Stefan de Konink <[EMAIL PROTECTED]> >> wrote: >>> >>> Minutely diffs work perfect. The NL crew is already creating a mi

Re: [OSM-dev] 0.5 API: /api/0.5/user/preferences, values truncated to 256 chars

On Tue, Nov 25, 2008 at 5:48 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Shaun McDonald wrote: >> Considering that no one until now has started using preferences, can >> this wait until API 0.6? > > Some people are really eager to postpone everything that sounds > 'reasonable' to 0.6 is relea

Re: [OSM-dev] 0.5 API: /api/0.5/user/preferences, values truncated to 256 chars

On Tue, Nov 25, 2008 at 6:34 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> >> do you think it would be motivating for all the >> volunteers working on the editor and server code if we set a deadline? > > I think so; it would make people live

Re: [OSM-dev] 0.5 API: /api/0.5/user/preferences, values truncated to 256 chars

On Tue, Nov 25, 2008 at 7:04 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Matt Amos wrote: >> i think the problem might be *agreeing* about the deadline in the >> first place :-) > > Then it might be better to never use any argument as 'wait till 0.6' bec

Re: [OSM-dev] Data corruption :) II

On Wed, Nov 26, 2008 at 7:54 AM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Then let me even get a better proposal; A second machines will be > installed that has enforced foreign keys. This second machine will produce > the planet. And will directly trigger events upon corruption so the main >

Re: [OSM-dev] Data corruption :) II

On Wed, Nov 26, 2008 at 12:27 PM, Dave Stubbs <[EMAIL PROTECTED]> wrote: > 2008/11/26 Matt Amos <[EMAIL PROTECTED]>: >> what would be ideal is a check like "node_id references >> way_nodes.node_id check way_nodes.visible = 1", but i can't find any >

Re: [OSM-dev] Data corruption :) II

On Thu, Nov 27, 2008 at 3:39 AM, Brett Henderson <[EMAIL PROTECTED]> wrote: > But I'm curious why you would ever need to know if an id has existed? to give the client the distinction between 404 not found and 410 gone. 410 implies that a history call will work, 404 implies that it won't. > I don'

Re: [OSM-dev] User authentication/Single sign on (was: Proposal for a map-bug tracker)

On Fri, Nov 28, 2008 at 11:45 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote: > A user talking to System X must be able to prove to System X that he is > OpenStreetMap user Z, without System X gaining any privileged information. better still, the user gets to say exactly what information system X can

Re: [OSM-dev] Don't worry, be happy

On Mon, Dec 1, 2008 at 6:09 PM, Joachim Zobel <[EMAIL PROTECTED]> wrote: > Am Mittwoch, den 26.11.2008, 12:54 + schrieb Matt Amos: >> > Well, as long as the API code is good, and makes this check, then >> the >> > transaction should cover it for inserts/updat

Re: [OSM-dev] API 0.6 Bugs

On Thu, Dec 4, 2008 at 11:21 AM, Shaun McDonald <[EMAIL PROTECTED]> wrote: > On 4 Dec 2008, at 11:08, Dominik Spies wrote: >> Reason is that when creating a changeset, the tag with key "comment" >> must be specified *at first*. This is not mentioned in the wiki (just >> that it has to be there), an

Re: [OSM-dev] API 0.6 Bugs

On Thu, Dec 4, 2008 at 12:39 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote: > Tom Hughes wrote: >> You can make then case sensitive in MySQL if you want > > I guess that's the key... do we want objects with a "NOTE" and a "note"? its a pity that mysql's default utf8 collation is case-insensitive by

Re: [OSM-dev] Any tile statistics (unique visitors)

On Mon, Dec 8, 2008 at 12:19 AM, Milo van der Linden <[EMAIL PROTECTED]> wrote: > I assume even Steve C had to present some sort of stats to Sunstone > Capital > > or am I mistaking? for these purposes the

Re: [OSM-dev] 0.6 database table creation script for mysql?

On Tue, Dec 9, 2008 at 5:41 PM, Maarten Deen <[EMAIL PROTECTED]> wrote: > Shaun McDonald wrote: >> For MySQL, you can setup rails api06 branch, and run rake db:migrate. and for 0.6 you can in postgres as well :-) > And to comment on rails_port_branches/api06/db/migrate/001_create_osm_db.rb in > s

Re: [OSM-dev] ROMA servers down - osmosis large way problem

On Mon, Dec 29, 2008 at 10:26 PM, Stefan de Konink wrote: > Some people wanted to limit ways/relations to 2k of nodes. If you do > allow relations to have all these extra subrelations then what are you > going to solve in the end? This is enforcing a clueless limit and not > solving the fundamenta

Re: [OSM-dev] ROMA servers down - osmosis large way problem

On Tue, Dec 30, 2008 at 1:05 PM, Stefan de Konink wrote: > Frederik Ramm wrote: >> Stefan de Konink wrote: >>> Even in 0.5 relations can be ordered using the type='...'. >> >> You're getting (more) ridiculous. >> >> What are you trying to prove here? That you're right and the rest is >> wrong? Tha

Re: [OSM-dev] ROMA servers down - osmosis large way problem

On Tue, Dec 30, 2008 at 10:18 PM, Maarten Deen wrote: > Not wanting to plead for a certain limit of nodes per way, but what would be > the technical problem with a single entity consisting of a million 2-node > ways, as opposed to a way of a million nodes? maybe we could call these 2-node ways "s

Re: [OSM-dev] ROMA servers down - osmosis large way problem

On Wed, Dec 31, 2008 at 3:30 AM, Stefan de Konink wrote: > Maybe he made a typo and ment 2k-node... but that is just me parsing the > meaning behind a message. other than the obvious fact that 10^6 * 2k has three orders of magnitude more nodes* than a 10^6 node way? cheers, matt * after mergin

Re: [OSM-dev] Ruby developers in Amsterdam

On Tue, Jan 13, 2009 at 12:17 PM, Frederik Ramm wrote: > One is talking to users - letting them register, write blogs, write > messages (and if the trend continues, one day they'll be able to upload > images, have multi-page user profiles and forums and a full-blown E-Mail > system all within OSM)

Re: [OSM-dev] Ruby developers in Amsterdam

On Tue, Jan 13, 2009 at 1:02 PM, Richard Fairhurst wrote: > Matt Amos wrote: >> just because we're using ruby doesn't mean we have to use >> rails+activerecord :-) > > You mean I can put all the SQL back in amf_controller and get it running at > a reasonable sp

Re: [OSM-dev] Ruby developers in Amsterdam

On Tue, Jan 13, 2009 at 1:07 PM, Frederik Ramm wrote: > Matt Amos wrote: >> >> what do you see as the benefits of an old-fashioned compiled language >> (presumably you mean C/C++/Java) over just plain ruby? just because >> we're using ruby doesn't mean we hav

Re: [OSM-dev] Ruby developers in Amsterdam

On Tue, Jan 13, 2009 at 1:53 PM, Richard Fairhurst wrote: > Matt Amos wrote: >> in which case we're trading development effort for performance. >> i think we're operating in areas constrained by the lack of >> available developers, so making the barrier to entr

Re: [OSM-dev] 'Up-to-Date', serving ondemand live Mapnik data

On Mon, Jan 19, 2009 at 8:31 AM, D Tucny wrote: > 2009/1/19 Christopher Schmidt >> Since this is not tiled at all, the performance is not likely to be great, >> but it does make an interesting demo. > > Apart from that little problem it looks pretty cool... Of course, if the > mapnik layer was ge

Re: [OSM-dev] Quad- and R-Trees

On Tue, Jan 20, 2009 at 1:57 PM, jh wrote: > Dominik Spies schrieb: >> I could not find any helpfull information regarding this. Is this >> correct? If yes why? The only reason I can imagine ist that the >> quadtree will be very unbalanced. > > Yes, but I don't think that this should pose practica

Re: [OSM-dev] API 0.6: Changeset Access

On 1/28/09, Brett Henderson wrote: > Is the bounding box info updated within the same transaction as entity > updates or can it be updated asynchronously with a separate daemon? I > remember discussions about bbox updates only occurring occasionally (ie. > the bbox is made slightly larger than ne

Re: [OSM-dev] [OSM-talk] donating read-only api-mirrors

On Fri, Feb 6, 2009 at 5:20 PM, Marcus Wolschon wrote: > On Fri, Feb 6, 2009 at 4:35 PM, Tom Hughes wrote: >> Erik Johansson wrote: >> >>> How much of the DB load comes from the read only part of the API, and >>> what if you remove the area limit on the map call? >> >> If I remove the area limit

Re: [OSM-dev] [OSM-talk] donating read-only api-mirrors

On Fri, Feb 6, 2009 at 8:32 PM, Stefan de Konink wrote: > Matthias Julius wrote: >> Is anyone relying on the ascending ID order? > > Even then; the ordering can be done in SQL. not in the two-step scheme that Matthias was suggesting. it might be possible using temporary tables, but care would be

Re: [OSM-dev] [OSM-talk] donating read-only api-mirrors

On Fri, Feb 6, 2009 at 11:47 PM, Stefan de Konink wrote: > Matt Amos wrote: >> On Fri, Feb 6, 2009 at 8:32 PM, Stefan de Konink wrote: >>> Even then; the ordering can be done in SQL. >> >> not in the two-step scheme that Matthias was suggesting. it might be >

Re: [OSM-dev] [OSM-talk] donating read-only api-mirrors

On Sat, Feb 7, 2009 at 2:51 AM, Stefan de Konink wrote: > Ok do I understand you right in best readable case want to do the following? > > SELECT * FROM nodes WHERE BBOX(...) OR id IN ( > SELECT node FROM way_nds WHERE way IN ( > SELECT way FROM way_nds WHERE node IN ( > SELECT * FROM nodes WH

Re: [OSM-dev] [OSM-talk] donating read-only api-mirrors

On Sat, Feb 7, 2009 at 4:56 AM, Stefan de Konink wrote: > Matt Amos wrote: >> indeed, with this method either the node and way IDs are cached (i.e: >> stored in memory) or the query is repeated (wasting time). > > Some databases cache their results or even complete q

Re: [OSM-dev] Massive building import - thoughts

On Sat, Feb 7, 2009 at 12:28 PM, Stefan de Konink wrote: > Frederik Ramm wrote: >> I would imagine some complaints from those users who are not interested >> in buildings, and for whom 90% of the data they download is useless >> after the import. You might have to provide filtered extracts for the

Re: [OSM-dev] OsmChange format and 0.6

On Mon, Feb 9, 2009 at 1:06 AM, Frederik Ramm wrote: >I have come across a strange logic twist and want to confuse you > with it. (Maybe it was clear to anybody anyway, don't know.) > > API 0.6 supports uploading OsmChange files, with the additional > requirement that each node/way/relation co

Re: [OSM-dev] Rantings about API 0.6

1) >> >> WTF does this happen on every object (read: node) I upload? The API already >> knows who I am the second I started to upload the diff! > > Probably the same thing that Matt Amos just posted, the individual > object processing code being re-used for each object i

Re: [OSM-dev] Rantings about API 0.6

On Tue, Feb 10, 2009 at 12:58 PM, Iván Sánchez Ortega wrote: > El Martes, 10 de Febrero de 2009, Matt Amos escribió: >> i agree. there is scope for optimisation within rails with varying >> degrees of ugliness ;-) > > Geez, this conversation is making me want to rewrite th

Re: [OSM-dev] Rantings about API 0.6

On Tue, Feb 10, 2009 at 2:11 PM, Iván Sánchez Ortega wrote: > El Martes, 10 de Febrero de 2009, Andy Robinson (blackadder-lists) escribió: >> >Geez, this conversation is making me want to rewrite the API from scratch >> >in another language. >> >> Yeah, would look a whole lot prettier in Spanish :

Re: [OSM-dev] Rantings about API 0.6

On Tue, Feb 10, 2009 at 6:50 PM, Stefan de Konink wrote: > Scott Shawcroft wrote: >> It'll be even faster when served from multiple computers. My friend and >> I are using Python, Thrift and Berkeley DB to stretch it across multiple >> boxes. It will scale better than any language rewrite. > > C

Re: [OSM-dev] Rantings about API 0.6

On Wed, Feb 11, 2009 at 11:02 AM, Raphaël Jacquot wrote: > Iván Sánchez Ortega wrote: >> WTF does this happen on every object (read: node) I upload? The API already >> knows who I am the second I started to upload the diff! > > > that's rails for you... > the thing attempts to do all the work of

Re: [OSM-dev] Rantings about API 0.6

On Wed, Feb 11, 2009 at 1:03 PM, Iván Sánchez Ortega wrote: > El Miércoles, 11 de Febrero de 2009, Raphaël Jacquot escribió: >> > Jokes aside, does your bulk importer also implement populating the >> > history tables, making sure that every node referenced by a way (and >> > every node/way/relatio

Re: [OSM-dev] Rantings about API 0.6

On Wed, Feb 11, 2009 at 1:55 PM, Iván Sánchez Ortega wrote: > For changeset timeouts: triggers, triggers, triggers. Or just initialize the > closing time of a changeset to a date in the future. the closing time trick is how the rails code works. would you also add triggers for changeset bbox upda

Re: [OSM-dev] OsmChange format and 0.6

On Thu, Feb 12, 2009 at 12:18 PM, Brett Henderson wrote: > Matt Amos wrote: >> at some point in the future it might be worth taking the changeset ID >> out of the element parsers and putting it into the controller. whether >> we want to make the change while 0.6 is so c

Re: [OSM-dev] OsmChange format and 0.6

On Sun, Feb 15, 2009 at 11:22 AM, Brett Henderson wrote: > The problem has many parallels to source code management as you've pointed > out. Using subversion as a guide may be helpful. (SNIP) From > what I can remember, ClearCase MultiSite uses branches with ownership locks > to prevent concurren

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

On Fri, Mar 13, 2009 at 1:21 AM, Stefan de Konink 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 databas

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

On Fri, Mar 13, 2009 at 8:34 AM, Florian Lohoff wrote: > So it is sensible to make it mirroring and it might even be a benefit to > do an 1 -> N mirroring. > > Rule of thumb: > >        More concurrent readers -> More spindles this is why we have ROMA/TRAPI/etc... they're able to satisy the most

Re: [OSM-dev] Improvement of tile rendering

On Tue, Mar 17, 2009 at 11:48 PM, Stefan de Konink wrote: > Dane Springmeyer wrote: >> I should stress though that Mod_tile is the optimal solution for tile >> rendering for most OSM related purposes. > > I wonder if an Apache module is able to provide caching. I doubt it can, > thus requires more

Re: [OSM-dev] Improvement of tile rendering

On Sat, Mar 21, 2009 at 1:08 AM, Udo Giacomozzi wrote: > One could even think of avoiding Mapnik completely and writing a > custom OSM renderer using AGG (which would also allow fixing the > labeling issues). In fact that would not be too hard to do (once you > understand the strange way how AGG w

Re: [OSM-dev] Google Summer of Code

On Wed, Mar 25, 2009 at 10:59 AM, Andy Allan wrote: > 2009/3/25 Iván Sánchez Ortega : >> El Miércoles, 25 de Marzo de 2009, José Ricardo escribió: >>> My interests are converging into the area of ubiquitous computing in which >>> localization plays a significant role (navigation, context awareness

Re: [OSM-dev] Google Summer of Code

On Wed, Mar 25, 2009 at 11:18 AM, Matt Amos wrote: > or even better - "improve editing support in andnav for ways/relations"* :-) /me FAIL. andnav isn't open-source, although parts of it might be re-used. cheers, matt ___ de

Re: [OSM-dev] Google Summer of Code

On Wed, Mar 25, 2009 at 11:46 AM, Matthias Brandt wrote: > Matt Amos wrote: >> /me FAIL. andnav isn't open-source > > In opposition to Vespucci. i'd been looking for that editing screenshot you have of the large edit areas - i couldn't find it and assumed it must

Re: [OSM-dev] Google Summer of Code

On Wed, Mar 25, 2009 at 12:43 PM, Matthias Brandt wrote: > Matt Amos wrote: >> looks like an excellent candidate for some help with the 0.6 API change? > > Yes, Vespucci has to be updated for API 0.6! Are you interested? yes, i'll definitely take a look a

Re: [OSM-dev] OSM Fixer [Sequal]

On Wed, Mar 25, 2009 at 4:47 PM, Stefan de Konink wrote: > Andy Allan wrote: >> On Wed, Mar 25, 2009 at 3:07 PM, Stefan de Konink wrote: >> It's a known problem with a fix on the way with 0.6. >>> Is this already checked that it will be fixed using 0.6? Since currently >>> the API doesn't se

Re: [OSM-dev] OSM Fixer [Sequal]

On Wed, Mar 25, 2009 at 7:06 PM, Stefan de Konink wrote: > Matt Amos wrote: >> the issue with things referencing deleted items should go away because >> the transactions wrap the used-by checks. > > True; But isn't Rails doing that now too? [I am talking about the

Re: [OSM-dev] GSoC Ideas

2009/3/27 Iván Sánchez Ortega : > El Jueves, 26 de Marzo de 2009, Milo van der Linden escribió: >> > You're wrong - mapnik depends on a local PostgreSQL database, not on the >> > OSM API. >> >> The current Infrastructure where hunderds of mapnik/postgresql/postgis >> servers pull data from the osm

Re: [OSM-dev] OSM Fixer [Sequal]

On Fri, Mar 27, 2009 at 3:01 PM, Stefan de Konink wrote: > Shaun McDonald wrote: >> On 27 Mar 2009, at 12:14, Rolf Bode-Meyer wrote: >> >>> 2009/3/26 Matt Amos : >>> >>>> if we were to convert all the tables to innodb we could add >>>> t

Re: [OSM-dev] OSM Fixer [Sequal]

On Fri, Mar 27, 2009 at 3:15 PM, Stefan de Konink wrote: > Matt Amos wrote: >>>> >>>> This is for the main DB server. Part of the 0.6 transition will >>>> include moving from MySQL to Postgres for the sanity of the database >>>> admins, and i

Re: [OSM-dev] Tiling the Planet and Missing Nodes

On Sat, Mar 28, 2009 at 3:24 PM, Stefan de Konink wrote: > D Tucny wrote: >> Again, this isn't so simple... doing this would remove some errors >> (deleted objects in a relation) and introduce new ones (relations that >> are missing critical components or otherwise don't make sense)... the relati

Re: [OSM-dev] Tiling the Planet and Missing Nodes

On Sat, Mar 28, 2009 at 6:15 PM, Tom Hughes wrote: > Matt Amos wrote: >> >> On Sat, Mar 28, 2009 at 3:24 PM, Stefan de Konink >> wrote: >> >>> Nothing is simple; but even in the 0.6 API there will no keyboardl/chair >>> filter. >> >>

Re: [OSM-dev] Potlatch - Richard... I know

On Tue, Mar 31, 2009 at 2:33 PM, Stefan de Konink wrote: > Marc Schütz wrote: >>> Use < as delimiter, (since it can never >>> be used in key or value tag) >> >> I'm pretty sure it can; AFAIK there are no limitations on what may occur in >> keys and values (besides NUL). > > We are running an XML

Re: [OSM-dev] Potlatch - Richard... I know

2009/3/31 Stefan de Konink : > So if I use < 'as char' to be a delimiter for the to uniquely sorted list, I > can after this operation use < 'as char' to split it? no, because the xml is decoded into k="", v="" (using C escaping). a form of escaping is already done for the nodes in 0.5 schema, b

Re: [OSM-dev] Potlatch - Richard... I know

On Tue, Mar 31, 2009 at 4:11 PM, 80n <80n...@gmail.com> wrote: > Let me see if I understand correctly what you are saying.  You think that > the currently proposed migration from the old server and old schema to the > new server with a new schema that includes some referential integrity > constrain

Re: [OSM-dev] database schema

2009/3/31 Pierre-André Jacquod : > After some mapping, I am starting to have a look at the programming side > of OSM. Just a question about the Database. awesome :-) > If I understood what I read under SVN ( > http://svn.openstreetmap.org/sites/rails_port/db/migrate/  currently > Revision 14372)

Re: [OSM-dev] 0.6 on PostgreSQL

On Tue, Mar 31, 2009 at 10:07 PM, Brett Henderson wrote: > Okay, I should have checked the source code first. > > I'm guessing I need to modify db/database.yml and set the adapter to > "pgsql".  And then compile the libmyosm library as explained in db/README. the adaptor is "postgresql", i think.

Re: [OSM-dev] [GSoC] A GPX photo stamper.

On Wed, Apr 1, 2009 at 3:26 PM, Stefan de Konink wrote: > On Wed, 1 Apr 2009, Tijs Zwinkels wrote: > >> - Any opinions about / ideas for my proposal? > > I would suggest to help around with > OpenStreetPhoto, especially the matching part > (keywords: SIFT/Histogram/Bundler) ;) maybe take a look a

Re: [OSM-dev] Fwd: [GSoC] A GPX photo stamper.

On Wed, Apr 1, 2009 at 4:23 PM, Stefan de Konink wrote: > I think stitching is something that is lets say 'available', referencing > images is too. But I would really love to see some thing like robust > automatic traffic sign recognition, or maybe even streetname OCR. > Ambitious but certainly do

Re: [OSM-dev] Memory error while converting osm to gml

2009/4/2 Stefan de Konink : > Iván Sánchez Ortega wrote: >> El Jueves, 2 de Abril de 2009, Will Nordin escribió: >>> I am trying to convert the planet-090319.osm (approx 107GB) to gml. I've >>> tried the Java and Python solutions, but both end up thorwing OutOfMemory >>> exceptions. >> >> Man, it's

Re: [OSM-dev] Memory error while converting osm to gml

2009/4/2 Stefan de Konink : > Matt Amos wrote: >> so you'd need to either store >> all the node locations in ram or some external indexed format... which >> is exactly what osm2pgsql does :-) > > mmap the node table in array index form to disk, that will work be

Re: [OSM-dev] JOSM: Several tags with same key

On Thu, Apr 2, 2009 at 10:33 PM, Stefan de Konink wrote: > Dave Stubbs wrote: >> And while currently possible in the database, it doesn't work in the >> current API, so you can't actually enter them  :-) > > Just download an object, duplicate the tag and reupload. Sounds pretty > possible to me :)

Re: [OSM-dev] JOSM: Several tags with same key

On Thu, Apr 2, 2009 at 11:35 PM, Stefan de Konink wrote: > Matt Amos wrote: >> the API uses a hash and disallows repeated tags on ways and relations. >> but it uses a list for nodes, so you can easily get duplicate tags by >> the method you describe. > > Interesting;

Re: [OSM-dev] JOSM: Several tags with same key

On Fri, Apr 3, 2009 at 7:24 AM, Stefan de Konink wrote: > D Tucny wrote: >> Then shouldn't that be two nodes? with the atm one having a layer=1 tag? >> >> Similar to having a bar above a restaurant above a bank at the same >> position but on different floors... > > There are better examples probab

Re: [OSM-dev] Fwd: [GSoC] A GPX photo stamper.

iew the sign from a relatively straight angle with a > reasonably high resolution, not too much reflection, etc) > For now I'll assume the latter case. If the performance is reasonable, we > can always scale up to the more difficult cases. > > - Tijs Zwinkels > > > On Thu, Apr

Re: [OSM-dev] JOSM: Several tags with same key

On Fri, Apr 3, 2009 at 2:05 PM, Ed Loach wrote: > I've been noticing recently how things seem to be heading. > > Before I was involved with the project there were nodes, segments > and ways. Whether there were also relations at that time I don't > know. Perhaps the same key could be used more than

Re: [OSM-dev] [GSoC] Automatic Street-Sign Detection and Reading - was: [GSoC] A GPX photo stamper.

On Fri, Apr 3, 2009 at 8:24 PM, Stefan de Konink wrote: > Tijs Zwinkels wrote: >> On Fri, Apr 3, 2009 at 8:51 PM, Stefan de Konink > > wrote: >> I'm not sure whether this is very suitable for a webapp since it might >> require quite some computation, and will generally ope

Re: [OSM-dev] JOSM: Several tags with same key

On Sat, Apr 4, 2009 at 6:10 PM, Stefan de Konink wrote: > Eddy Petrișor wrote: >> Stefan de Konink a scris: >>> Martin Koppenhoefer wrote: Of course this would be a lot of work and discussion in the community, but I think it's still not too late to do it, and it would help a lot to

Re: [OSM-dev] Memory error while converting osm to gml

2009/4/4 Martijn van Oosterhout : > Just reading this again made me realise that we could probably make > osm2pgsql faster for the common case just by forking and using > gzip/bzip2 to do the decompression in a separate process (i.e. another > CPU)... Not entirely sure how much you'd save though (I

Re: [OSM-dev] [GSoC] Automatic Street-Sign Detection and Reading - was: [GSoC] A GPX photo stamper.

On Sat, Apr 4, 2009 at 2:38 PM, Stefan de Konink wrote: > Matt Amos wrote: >>>> >>>>    But please keep in mind that SIFT will *not* work for the typical >>>>   streetsign because SIFT looks for features, which are typically not >>>>   present

Re: [OSM-dev] JOSM: Several tags with same key

On Sat, Apr 4, 2009 at 7:40 PM, Marcus Wolschon wrote: > On Sat, Apr 4, 2009 at 8:14 PM, Matt Amos wrote: >> maybe what we need is an "amenities" tag specifically for multiple >> co-located amenities? > > I strongly disagree. > That is even harder to parse the

Re: [OSM-dev] [GSoC] Automatic Street-Sign Detection and Reading - was: [GSoC] A GPX photo stamper.

On Sat, Apr 4, 2009 at 8:00 PM, Stefan de Konink wrote: > Matt Amos wrote: >> >> On Sat, Apr 4, 2009 at 2:38 PM, Stefan de Konink wrote: >>> >>> Matt Amos wrote: >>>>>> >>>>>>   But please keep in mind that SIFT will *not* wo

Re: [OSM-dev] JOSM: Several tags with same key

2009/4/5 Pierre-André Jacquod : > among theses 431 different values, there are 25 values with ; in them, > all value (like fuel;fast_food or fuel;toilets ) being composed of > values already used normally alone as amenity. > > This is at least 6% of key/value paar showing that the mapper thing the

Re: [OSM-dev] JOSM: Several tags with same key

On Mon, Apr 6, 2009 at 8:06 AM, wrote: > On Sat, 4 Apr 2009 20:09:40 +0100, Matt Amos wrote: >> On Sat, Apr 4, 2009 at 7:40 PM, Marcus Wolschon >> wrote: >>> On Sat, Apr 4, 2009 at 8:14 PM, Matt Amos wrote: >>>> maybe what we need is an "ameniti

Re: [OSM-dev] Please advise; I really don't get how this can corrupt so badly

On Mon, Apr 6, 2009 at 1:12 PM, Dave Stubbs wrote: > So I'd just wait two weeks. It's not going to cause the world to end > in the meantime. it might. i'm sure i can think up a semi-plausible situation involving scientists at CERN being so frustrated with the broken relations they don't notice th

Re: [OSM-dev] Please advise; I really don't get how this can corrupt so badly

On Mon, Apr 6, 2009 at 5:45 PM, Ed Loach wrote: > "The current schedule foresees the final magnet being reinstalled by > the end of March 2009, with the LHC being cold and ready for > powering tests by the end of June 2009." LHC 0.6... weird ;-) cheers, matt ___

  1   2   3   4   >