Re: [OSM-dev] Polygon relationificator - CGAL?

2009-09-14 Thread Ben Supnik
Hi Frederik, QPL is GPL incompatible? Doh! I was unaware of this...I was aware that CGAL is at least contagiously copy-left...not something I terribly like. My thought though is that for a stand-alone tool this is not necessarily a deal-breaker. cheers ben Frederik Ramm wrote: > Hi, > > Be

Re: [OSM-dev] Polygon relationificator - CGAL?

2009-09-14 Thread Frederik Ramm
Hi, Ben Supnik wrote: > I figure this is as good of a time as any to plug CGAL...it's a hard > core open source comp-geom lib: Great piece of software, but it is worth noting that CGAL has a license issue. Parts of it are LGPL (which is ok) but some of the more interesting bits are under a fri

Re: [OSM-dev] Wiki: Renaming the API pages

2009-09-14 Thread Lars Francke
> Is the old page redirecting to the new page? All old pages should redirect to their new versions, yes: http://wiki.openstreetmap.org/wiki/OSM_Protocol_Version_0.3 http://wiki.openstreetmap.org/wiki/OSM_Protocol_Version_0.4 http://wiki.openstreetmap.org/wiki/OSM_Protocol_Version_0.5 http://wiki.o

Re: [OSM-dev] Wiki: Renaming the API pages

2009-09-14 Thread Shaun McDonald
On 14 Sep 2009, at 19:26, Lars Francke wrote: +1 This has needed a tidyup for a long time. I'm done with this change. I have renamed every relevant page to "API v0.x" and "API changes between v0.x and v0.y" and I tried to correct every link to point to the new name. I might have missed some r

Re: [OSM-dev] Polygon relationificator - CGAL?

2009-09-14 Thread Ben Supnik
Hi Guys, Iván Sánchez Ortega wrote: > P.S.: Remind me to take a course in computational geometry. I'm feeling like > I > need it. I figure this is as good of a time as any to plug CGAL...it's a hard core open source comp-geom lib: http://www.cgal.org/ in my work with OSM (exporting all road

Re: [OSM-dev] Wiki: Renaming the API pages

2009-09-14 Thread Lars Francke
> +1 > This has needed a tidyup for a long time. I'm done with this change. I have renamed every relevant page to "API v0.x" and "API changes between v0.x and v0.y" and I tried to correct every link to point to the new name. I might have missed some references but...it should work, because the old

Re: [OSM-dev] Polygon relationificator

2009-09-14 Thread Emilie Laffray
2009/9/14 Frederik Ramm > Ian, > > > This feature could be added, but could you draw a couple pictures to > > explain what you mean? What happens with the graph edges inside the > > multipolygon? Since they aren't really polygons, do they belong in a > > multipolygon relation? Maybe I'm not corre

Re: [OSM-dev] Polygon relationificator

2009-09-14 Thread Iván Sánchez Ortega
El Lunes, 14 de Septiembre de 2009, Frederik Ramm escribió: > [...] The goal is to split up the polygons into their border lines, and then > create OSM multipolygon relations where the border consists of several of > those lines, and every line is used by two adjacent polygons [...] *AT LEAST* t

Re: [OSM-dev] Recursive relations

2009-09-14 Thread Andrew M. Bishop
Shaun McDonald writes: > On 13 Sep 2009, at 10:56, Andrew M. Bishop wrote: > >> In OSM a relation can contain other relations but it seems that there >> is nothing to check that a relation doesn't contain itself. I can't >> think of any legitimate reason that it should be allowed though. > From

Re: [OSM-dev] Polygon relationificator

2009-09-14 Thread Frederik Ramm
Ian, > This feature could be added, but could you draw a couple pictures to > explain what you mean? What happens with the graph edges inside the > multipolygon? Since they aren't really polygons, do they belong in a > multipolygon relation? Maybe I'm not correctly interpreting what you meant.

Re: [OSM-dev] Polygon relationificator

2009-09-14 Thread Iván Sánchez Ortega
El Lunes, 14 de Septiembre de 2009, Ian Dees escribió: > This feature could be added, but could you draw a couple pictures to > explain what you mean? What happens with the graph edges inside the > multipolygon? Since they aren't really polygons, do they belong in a > multipolygon relation? Maybe I

Re: [OSM-dev] JAVA-Lib similar OpenLayers

2009-09-14 Thread Stefano Salvador
> does anybody know an JAVA-Library with similar features like OpenLayers > Javascript-Lib? > I would like to enhance our Java-Client to get maps from WMS-Servers. > Thanks for your effort. I don't know if it fills your needs but take a look to this software: http://www.geomajas.org/ Bye, Stef

Re: [OSM-dev] Polygon relationificator

2009-09-14 Thread Ian Dees
2009/9/14 Iván Sánchez Ortega > > You can see where this goes. If the input polygons are non-overlapping and > adjacent, I could redraw the edges of the polygons as graph edges, put a > graph node whenever three (or more) polygons touch each other, and then > apply > some graph theory to convert

Re: [OSM-dev] Polygon relationificator

2009-09-14 Thread Frederik Ramm
Hi, Iván Sánchez Ortega wrote: > You can see where this goes. If the input polygons are non-overlapping and > adjacent, I could redraw the edges of the polygons as graph edges, put a > graph node whenever three (or more) polygons touch each other, and then apply > some graph theory to convert e

[OSM-dev] Polygon relationificator

2009-09-14 Thread Iván Sánchez Ortega
Hi all, During the imports support group conference call, the question of import tools was raised. I can't quite recall everyone's point of view, but I think that the general idea was "the more tools, the better". I'm all for an unix-like approach: lots of small specialised tools, that work

Re: [OSM-dev] Taxi to Lisbon

2009-09-14 Thread Maarten Deen
On Sun, Sep 13, 2009 at 10:37 PM, Claudius Henrichs wrote: > I've set up a wiki page [1] with some impressive routing results on OSM > data compared to Google. For example we can already route from Teheran, > Iran to Lisbon, Portugal and to New Delhi, India. Or you can hail a cab > in Mexico City

Re: [OSM-dev] broken utf8 in minute changeset 200907140650

2009-09-14 Thread Richard Fairhurst
On 09/09/2009 17:43, Eddy Petrișor wrote: > It looks like the cursor moves with the same ammount of positions as > bytes encoding the UTF-8 character. I wouldn't be surprised at all. I'm a little loth to spend time on fine-tuning something, with the risk of introducing more bugs, that Adobe real