[OSM-dev] see josm wms plugin url's

Hi List, I'm trying to use the josm wms plugin on another public wms, but do not see any images (while I can see the wms working in QGIS). Question: is there a way/option to see the wms-url the plugin is firing (would be ok for me to see it in te System.out.print)? Specially the bbox/srs stuff

Re: [OSM-dev] Proposal: Make relations ordered

Hi, > No, but the argument is actually that if it's too complicated for > potlatch then it's too complicated full-stop. If only experts end up > being able to do something then in general it won't get done. That > might be OK for the bits where there are experts, but most areas on > our map have n

Re: [OSM-dev] Proposal: Make relations ordered

On Mon, Mar 17, 2008 at 6:34 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote: > Hi, > > > > Surely one of the unwritten guiding principles of OSM is "don't make > > things complicated just to cater for a few edge cases"? > > Allowing an order in relations would not make things more complicated > fo

Re: [OSM-dev] Background

HI, >Humm... undestand, but i can make them in Google Earth , export the paths >and import into OpenStreet, right? i have some cities traced in my Google >Earth, ;) Let's put it this way: Yes, Google Earth has this feature that lets you track stuff off their aerial imagery and save it

Re: [OSM-dev] Background

Williams Farias wrote: >Sent: 17 March 2008 6:33 PM >To: dev@openstreetmap.org >Subject: Re: [OSM-dev] Background > >Hi Stefan , > >Humm... undestand, but i can make them in Google Earth , export the paths >and import into OpenStreet, right? i have some cities traced in my Google >Earth, ;) > No y

Re: [OSM-dev] Proposal: Make relations ordered

Hi, > Surely one of the unwritten guiding principles of OSM is "don't make > things complicated just to cater for a few edge cases"? Allowing an order in relations would not make things more complicated for the user, only for the writers of editors ;-) There will always be certain advanced fea

Re: [OSM-dev] Background

William, We cannot (and must not) trace from any background images that we do not have permission for since they are covered by copyright and other restricted licences. We only have permission from Yahoo! to use their imagery via their API. We must NOT add any data derived from Google, Microsoft e

Re: [OSM-dev] Background

Hi Stefan , Humm... undestand, but i can make them in Google Earth , export the paths and import into OpenStreet, right? i have some cities traced in my Google Earth, ;) thanks 2008/3/17, Stefan de Konink <[EMAIL PROTECTED]>: > > On Mon, 17 Mar 2008, Williams Farias wrote: > > > I´m a new user i

Re: [OSM-dev] Background

On Mon, 17 Mar 2008, Williams Farias wrote: > I´m a new user in OpenStreet, and i´m tracing my city in Brazil, but there > are places where the YahooMap does not zoom well so i can trace the map. My > question is: can Google Maps be placed in the "background" as an option? and > Microsoft Maps too

[OSM-dev] Background

Hello to all, I´m a new user in OpenStreet, and i´m tracing my city in Brazil, but there are places where the YahooMap does not zoom well so i can trace the map. My question is: can Google Maps be placed in the "background" as an option? and Microsoft Maps too? Google Maps in Brazil cover almost e

[OSM-dev] Background

Hello to all, I´m a new user in OpenStreet, and i´m tracing my city in Brazil, but there are places where the YahooMap does not zoom well so i can trace the map. My question is: can Google Maps be placed in the "background" as an option? Google Maps in Brazil cover almost every small cities that Y

Re: [OSM-dev] Advice sought on polygon-with-hole drawing

Andy Allan [mailto:[EMAIL PROTECTED] >Sent: 17 March 2008 4:20 PM >To: Andy Robinson (blackadder) >Cc: Robert (Jamie) Munro; dev >Subject: Re: [OSM-dev] Advice sought on polygon-with-hole drawing > >On Mon, Mar 17, 2008 at 2:28 PM, Andy Robinson (blackadder) ><[EMAIL PROTECTED]> wrote: > >> >Direc

Re: [OSM-dev] Advice sought on polygon-with-hole drawing

On Mon, Mar 17, 2008 at 2:28 PM, Andy Robinson (blackadder) <[EMAIL PROTECTED]> wrote: > >Direction is important for one-way roads but shoudn't be for areas. > >Coastline is an understandable exception. > > And even that's easy for a user to swap around without realising the affect. Indeed. >

Re: [OSM-dev] Advice sought on polygon-with-hole drawing

On Mar 17, 2008, at 13:33, Andy Allan wrote: > On Fri, Mar 14, 2008 at 10:43 AM, Robert (Jamie) Munro > <[EMAIL PROTECTED]> wrote: > >> Yes. That is what I am saying. 1 simple rule: >> >> *All* areas should be colour on the right (i.e. clockwise) > No chance. This is a completely terrible idea. It

Re: [OSM-dev] Advice sought on polygon-with-hole drawing

Robert Vollmert wrote: > However, I believe it would be quite easy to make such a rule obvious > to users, by attaching a few pixels of shading to the right of ways > with area tags in the editors. I'm not sure that this would be at all easy to code (or quick to run) in Actionscript, sadly, or

Re: [OSM-dev] Advice sought on polygon-with-hole drawing

Andy Allan wrote: >Sent: 17 March 2008 12:33 PM >To: Robert (Jamie) Munro >Cc: dev >Subject: Re: [OSM-dev] Advice sought on polygon-with-hole drawing > >On Fri, Mar 14, 2008 at 10:43 AM, Robert (Jamie) Munro ><[EMAIL PROTECTED]> wrote: > >> Yes. That is what I am saying. 1 simple rule: >> >> *All

Re: [OSM-dev] Proposal: Make relations ordered

Robert (Jamie) Munro wrote: > No, XML is /very/ ordered. Imagine an xhtml page if the browser decided > to put the tags in whatever order it pleased inside the tag! Oh, so you've used Internet Explorer for Mac...? cheers Richard ___ dev mailing lis

Re: [OSM-dev] Proposal: Make relations ordered

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andy Allan wrote: | | PS Is it bad XML-foo to assume the child nodes are ordered? I wouldn't | expect an implicit ordering myself, but I'm no XML expert. No, XML is /very/ ordered. Imagine an xhtml page if the browser decided to put the tags in whate

Re: [OSM-dev] Proposal: Make relations ordered

Frederik Ramm wrote: > In this case, the idea was that the intersection is theoretically > unrestricted, you just want a way to describe the route the bus takes. > Turn restrictions don't help you there. - One example people were > mentioning is bus stops; they want to make the bus stops members o

Re: [OSM-dev] Advice sought on polygon-with-hole drawing

On Fri, Mar 14, 2008 at 10:43 AM, Robert (Jamie) Munro <[EMAIL PROTECTED]> wrote: > Yes. That is what I am saying. 1 simple rule: > > *All* areas should be colour on the right (i.e. clockwise) No chance. This is a completely terrible idea. It makes it harder for newbies, who have to know to che

Re: [OSM-dev] Proposal: Make relations ordered

Hi, > To be honest the thought of relations getting ordering fills me with > dread. Potlatch is only just about to get relations support (thanks > entirely to Dave Stubbs) in 0.8; the thought of having to redesign it > and add a load of crap to handle splitting/merging/whatever doesn't > exactly f

Re: [OSM-dev] Proposal: Make relations ordered

On Mon, Mar 17, 2008 at 11:02 AM, Richard Fairhurst <[EMAIL PROTECTED]> wrote: > Jo wrote: > > > OK, fair enough. I hope JOSM and Potlatch get around to implementing it > > sooner rather than later then. It's rather annoying to carefully define > > a route relation, knowing that it can be blown

Re: [OSM-dev] Proposal: Make relations ordered

> PS Is it bad XML-foo to assume the child nodes are ordered? I wouldn't > expect an implicit ordering myself, but I'm no XML expert. > The XML spec says that the order of element content is significant, so no problems there. The order of attributes in an element is not significant however. You

Re: [OSM-dev] Proposal: Make relations ordered

On Mon, Mar 17, 2008 at 11:02 AM, Richard Fairhurst <[EMAIL PROTECTED]> wrote: > Jo wrote: > > > OK, fair enough. I hope JOSM and Potlatch get around to implementing it > > sooner rather than later then. It's rather annoying to carefully define > > a route relation, knowing that it can be blown

Re: [OSM-dev] Proposal: Make relations ordered

Jo wrote: > OK, fair enough. I hope JOSM and Potlatch get around to implementing it > sooner rather than later then. It's rather annoying to carefully define > a route relation, knowing that it can be blown apart by people who > remerge the parts or split them in other ways. I tested this and it >

Re: [OSM-dev] Multiple layers in the database

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 bvh schrieb: | I fully support a play area. But wouldn't it be much | easier and simpler to just a have an api running on something like | port 8080 that manipulates a second database with a very limited | data set (for example a snapshot of london or

Re: [OSM-dev] Proposal: Make relations ordered

Hi, >> The API user is not concerned with the sequence numbering, he just >> uploads the sequence he wants. The numbering takes place internally. >> > So inserting a way in the middle and/or reordering ways will have > to be implemented in all the editors then. Yes, exactly like inserting a nod

[OSM-dev] Osmosis patch for filtering ways

Dear all, I recently needed to filter OSM data to only include motorways and trunk roads. Finding no easy way to achieve that in a batch run, I extended Osmosis to be able to filter ways and nodes to achieve this. Maybe the patch is of use to someone:

Re: [OSM-dev] Proposal: Make relations ordered

> Hi, > >at SOTM '07 I discussed relations with a lot of people, and some > said they think relation members should be ordered, like nodes are in > a way. I maintained that that was unnecessary because if need be, you > can always use the "role" to specify an order; and that's how it got > impl

Re: [OSM-dev] Multiple layers in the database

Robert (Jamie) Munro wrote: > Why not just upload stuff with a osimport:highway=[whatever], then it > won't be rendered on any maps. JOSM could have tools separate it into > another layer if needed, and you could select and delete either the > original or the OS layer with JOSMs search features. A

Re: [OSM-dev] Multiple layers in the database

Frederik Ramm wrote: > Of course, millions of open questions remain, e.g. will there be > features that can transcend layers, or links between them (e.g. > feature X on layer A is the same as feature Y on layer B or so). I think we should start by considering them, at a database level anyway, as

Re: [OSM-dev] Proposal: Make relations ordered

Frederik Ramm wrote: > Hi, > > >> Please think through what needs to happen when a way is split. Can the >> order be given like 10,20,30, so 15 and 25, 28 can be added in between? >> > > We don't support incremental changes to objects. When you make a > change to an object, however mino

Re: [OSM-dev] Proposal: Make relations ordered

Hi, > Please think through what needs to happen when a way is split. Can the > order be given like 10,20,30, so 15 and 25, 28 can be added in between? We don't support incremental changes to objects. When you make a change to an object, however minor, you re-upload the whole object. This is n

Re: [OSM-dev] Proposal: Make relations ordered

Frederik Ramm wrote: > Hi, > >at SOTM '07 I discussed relations with a lot of people, and some > said they think relation members should be ordered, like nodes are in > a way. I maintained that that was unnecessary because if need be, you > can always use the "role" to specify an order; and tha