Re: [OSM-dev] Newbie question

Hi, > I've done a search for answers unsuccessfully, and while I'm a bit > reluctant to ask while people are suggesting each other smell, I'm > hoping for some non-personal advice. > > I recently added an area to the map tagged as landuse=construction. > This doesn't render in Osmarender, so I lo

Re: [OSM-dev] Newbie question

> So, at the risk I'm going to be told I smell, can anyone point a newbie to > SVN to a beginner's guide on how > to either amend and commit changes, or apply patch files? I did a quick > Google search and the first few results > I read were less then helpful. Just edit the files you've checked

Re: [OSM-dev] API 0.6: new_way

On Sun, Nov 9, 2008 at 8:00 PM, Richard Fairhurst <[EMAIL PROTECTED]> wrote: > In the way model, what does new_way do? > > I'm slightly surprised to encounter > def delete_with_history!(new_way, user) > > when I'd have expected > def delete_with_history!(changeset) > The controller receives a

Re: [OSM-dev] Newbie question

2008/11/9 Ed Loach <[EMAIL PROTECTED]>: > I've done a search for answers unsuccessfully, and while I'm a bit reluctant > to ask while people are suggesting each other smell, I'm hoping for some > non-personal advice. > > I recently added an area to the map tagged as landuse=construction. This >

[OSM-dev] Newbie question

I've done a search for answers unsuccessfully, and while I'm a bit reluctant to ask while people are suggesting each other smell, I'm hoping for some non-personal advice. I recently added an area to the map tagged as landuse=construction. This doesn't render in Osmarender, so I looked into patc

[OSM-dev] API 0.6: new_way

In the way model, what does new_way do? I'm slightly surprised to encounter def delete_with_history!(new_way, user) when I'd have expected def delete_with_history!(changeset) cheers Richard ___ dev mailing list dev@openstreetmap.org http://lists

Re: [OSM-dev] Binary OSM; the first pass encoder

Marcus Wolschon wrote: > So you are trying to bend a perfectly good communication-format into > an inperfect, mutable on-disk-format > at the expense of more space and more indirection. 1) There is something needed for first download. I think for this a binary protocol is required. You proposed a

Re: [OSM-dev] Binary OSM; the first pass encoder

Chris Browet wrote: > > Or you can leave "blanks", to be reused... > > > You are now trying to solve the fragmentation issue in every > filesystem ;) I think that blanking out the values with \0 could be > solution for it. And allow on local side to 'defrag' the file so >

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

Richard Fairhurst wrote: > Stefan de Konink wrote: > >> Go look on the same 'weekend-wiki page' for my name, hence I didn't >> want to spend 2x 150 euro to sit somewhere else programming. > > I looked. I saw this: > > "Please note that for a limited number of people (say 4-5) a > contribution

Re: [OSM-dev] Binary OSM; the first pass encoder

Richard Fairhurst wrote: > Chris Browet wrote: > >> For Merkaartor, I also implemented a Binary file format (see >> http://wiki.openstreetmap.org/index.php/Osb_spec_v2) > > Hey, how come it's suddenly _good_ to boast about a binary format? Because someone made code? + I got very upset I was una

Re: [OSM-dev] Binary OSM; the first pass encoder

Chris Browet wrote: I didn't know it was _bad_ as per anyone's opinion. Is AMF this (http://en.wikipedia.org/wiki/Action_Message_Format)? If so, looks very like transport and flash-specific, isn't it? What is (summarized) the reasoning for it to be _bad_ ? Yeah, that's it. I'm being flipp

Re: [OSM-dev] Binary OSM; the first pass encoder

2008/11/9 Stefan de Konink <[EMAIL PROTECTED]> > Chris Browet wrote: > >> UTF16 is just the default for Qt strings ;-) wchar* is UTF16, too. There >> definitely are UTF characters used, so char* is probably too restrictive, >> unless you handle UTF yourself. >> > > But like char* utfX is terminate

Re: [OSM-dev] Binary OSM; the first pass encoder

> > >> Or you can leave "blanks", to be reused... >> > > You are now trying to solve the fragmentation issue in every filesystem ;) > I think that blanking out the values with \0 could be solution for it. And > allow on local side to 'defrag' the file so that LEN \0\0\0\0 -> 0. > My concern is re

Re: [OSM-dev] Binary OSM; the first pass encoder

2008/11/9 Richard Fairhurst <[EMAIL PROTECTED]> > Chris Browet wrote: > > For Merkaartor, I also implemented a Binary file format (see > http://wiki.openstreetmap.org/index.php/Osb_spec_v2) > > > Hey, how come it's suddenly _good_ to boast about a binary format? > I didn't boast about anything. I

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

Stefan de Konink wrote: > Go look on the same 'weekend-wiki page' for my name, hence I didn't > want to spend 2x 150 euro to sit somewhere else programming. I looked. I saw this: "Please note that for a limited number of people (say 4-5) a contribution in the travel costs may be obtained via O

Re: [OSM-dev] Binary OSM; the first pass encoder

Chris Browet wrote: > 2008/11/9 Stefan de Konink <[EMAIL PROTECTED] > > > Chris Browet wrote: > > Right you are. > If I understand the concept, that would mean that once a string > appear in the "master string" file(s), it's indice cannot ever

Re: [OSM-dev] Binary OSM; the first pass encoder

2008/11/9 Stefan de Konink <[EMAIL PROTECTED]> > Chris Browet wrote: > >> Right you are. >> If I understand the concept, that would mean that once a string appear in >> the "master string" file(s), it's indice cannot ever change (otherwise, all >> the references will have to be changed, too). Do I

Re: [OSM-dev] Binary OSM; the first pass encoder

Chris Browet wrote: For Merkaartor, I also implemented a Binary file format (see http:// wiki.openstreetmap.org/index.php/Osb_spec_v2) Hey, how come it's suddenly _good_ to boast about a binary format? Steve has been on at me about how AMF is intrinsically evil since about 1673 AD. Maybe I

Re: [OSM-dev] Binary OSM; the first pass encoder

Chris Browet wrote: > Right you are. > If I understand the concept, that would mean that once a string appear > in the "master string" file(s), it's indice cannot ever change > (otherwise, all the references will have to be changed, too). Do I > understand correctly? Yup. But as you might reali

Re: [OSM-dev] Binary OSM; the first pass encoder

Chris Browet wrote: > UTF16 is just the default for Qt strings ;-) wchar* is UTF16, too. There > definitely are UTF characters used, so char* is probably too > restrictive, unless you handle UTF yourself. But like char* utfX is terminated by \0 too right? And is backwards compatible? > ATM, my

Re: [OSM-dev] Binary OSM; the first pass encoder

2008/11/9 Marcus Wolschon <[EMAIL PROTECTED]> > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Chris Browet schrieb: > > > > > > - Use separate files for strings and indices. > > > > > > Problem with this is that you will have one huge string file (if > > that's what you mean), which will

Re: [OSM-dev] Binary OSM; the first pass encoder

> >> I read it and has some valid points :) UTF16 handling is not yet my thing. >> I presume I could also implement this in my Planet extractor. Or do you >> already have a simple generator for this? >> > > UTF16 is just the default for Qt strings ;-) wchar* is UTF16, too. There > definitely are UT

Re: [OSM-dev] Binary OSM; the first pass encoder

2008/11/9 Stefan de Konink <[EMAIL PROTECTED]> > Chris Browet wrote: > >> For Merkaartor, I also implemented a Binary file format (see >> http://wiki.openstreetmap.org/index.php/Osb_spec_v2) >> > > I read it and has some valid points :) UTF16 handling is not yet my thing. > I presume I could also

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

On 9 Nov 2008, at 03:48, Simon Ward wrote: On Fri, Oct 31, 2008 at 12:02:22PM +0100, Stefan de Konink wrote: You are now basically working around the actual problem. Allowing partial ways in the editors for the current bbox. I think hacking and breaking ways is bad, duplicate information, m

Re: [OSM-dev] Binary OSM; the first pass encoder

Chris Browet wrote: > For Merkaartor, I also implemented a Binary file format (see > http://wiki.openstreetmap.org/index.php/Osb_spec_v2) I read it and has some valid points :) UTF16 handling is not yet my thing. I presume I could also implement this in my Planet extractor. Or do you already ha

Re: [OSM-dev] Binary OSM; the first pass encoder

For Merkaartor, I also implemented a Binary file format (see http://wiki.openstreetmap.org/index.php/Osb_spec_v2) Key points are: - Non lossy (it is editor oriented, rather than routing or render) - avoid tags Key/values duplication (there are 2 tables with unique string, features only holds point

Re: [OSM-dev] Social component

Frederik Ramm wrote: > ... and then there is a post from you pointing to some > git repository somewhere where you have some undocumented code that uses > some allegedly superior database system and does something with OSM data > where everything that is bad about OSM is somehow much better, "of

Re: [OSM-dev] Social component

Hi Frederik, Frederik Ramm wrote: > Stefan de Konink wrote: >> Hence my C implementation of what they are trying to build. I'll not >> start with my 0.6 until the specs are finished > > You are not, http://thuis.konink.de/api/0.5/way/7062297 Sure looks like it; mmm... WMS/WFS seems function

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

Stefan, Stefan de Konink wrote: > Hence my C implementation of what > they are trying to build. I'll not start with my 0.6 until the specs are > finished [...] You are not, at least not from what I read on the mailing lists, a contributor to the OSM code base; you are unhappy with what is th

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

Andy Allan wrote: > On Sun, Nov 9, 2008 at 12:57 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: >> Andy Allan wrote: >>> Your attitude stinks. >> Your attitude (and body) stinks more. > > [...] > >> Now go on stinking, because I >> highly doubt that you took the time to take a shower. > > Ad ho

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

On Sun, Nov 9, 2008 at 12:57 PM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Andy Allan wrote: >> >> Your attitude stinks. > > Your attitude (and body) stinks more. [...] > Now go on stinking, because I > highly doubt that you took the time to take a shower. Ad hominem attacks are pointless. I

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

Hi, Stefan de Konink wrote: > Your attitude (and body) stinks more. Someone as articulate as that should immediately made honorary chairman of the OSM foundation! Bye Frederik ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org

Re: [OSM-dev] Binary OSM; the first pass encoder

Marcus Wolschon wrote: > Stefan de Konink schrieb: >> The two problems I see; - In order to allow updates there should be >> some form of 'updatable space'. - If this space is not present it >> might be good to have one file that contains *all* strings, another >> one that contains the rest of the

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

Andy Allan wrote: > Your attitude stinks. Your attitude (and body) stinks more. I proposed the original, he was commenting on! I sat all night programming a binary encoding for OSM! Go look on the same 'weekend-wiki page' for my name, hence I didn't want to spend 2x 150 euro to sit somewhere el

Re: [OSM-dev] Binary OSM; the first pass encoder

Marcus Wolschon wrote: > cool to see some progress here. > If you decide on an index-format I can implement a DataSource for > Traveling Salesman for it (however any updates can only be appended). The two problems I see; - In order to allow updates there should be some form of 'updatable space'. -

Re: [OSM-dev] Osmosis on Australia extract

2008/11/8 Richard Chirgwin <[EMAIL PROTECTED]>: > Brett Henderson wrote: >> Perhaps the xml file has been truncated. Can you check the last lines >> of the file to make sure the xml file has been closed correctly? The >> program creating the file may have crashed half way through the file >> crea

Re: [OSM-dev] Mapnik's speed rendering slow ?

AIUI it allows you do to tricks with headers, (If-Modified-Since, Expires, etc) in ways that are harder otherwise. It also avoids needing a python interpreter in apache, which saves you quite a bit of memory. Have a nice day, On Sat, Nov 8, 2008 at 7:12 PM, sylvain letuffe <[EMAIL PROTECTED]> wro

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

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 issues, especially ones that go away when you move > to better hardware or software. Start making things scalable. Your attitude stinks. I'm

Re: [OSM-dev] Binary OSM; the first pass encoder

Hello Stefan, cool to see some progress here. If you decide on an index-format I can implement a DataSource for Traveling Salesman for it (however any updates can only be appended). Did you have a look at http://wiki.openstreetmap.org/index.php/User:MarcusWolschon%5Cosmbin_draft ? I am trying some

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

Simon Ward wrote: > I think I agree with this. Contributors or users of the data > shouldn’t > have to care at all about how big their ways (or other objects) can > be. > One of the main aims for OSM is that it is easy to contribute data, > right? Stop making it more complex by introducing a