Re: [OSM-talk] simplifying mapnik layout definition

2008-06-01 Thread bvh
On Tue, May 27, 2008 at 04:40:58PM +0200, Andreas Barth wrote: > (Long-run should be to use parameters IMHO, so that we can just say > "stroke-width has that size in relation to the scale" - but that's for > another day) Merkaartor has pixelsize-width = estimated-real-width * factor + offset. Thi

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-30 Thread Andreas Barth
* Andreas Barth ([EMAIL PROTECTED]) [080527 23:40]: > I have now put a bit of that stuff together. > > > All files (including sample code) is at > http://alius.ayous.org/~aba/osm-formater-1/ As I didn't get any comments, I assume that this solution doesn't fit the needs and I'll not follow it fu

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-28 Thread SteveC
On 27 May 2008, at 18:29, Robert (Jamie) Munro wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Andy Allan wrote: > | Now, if someone is volunteering to make a concise definition format > | that can be pre-processed into the mapnik XML format (or mapnik > python > | code, or even ju

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-28 Thread Beau Gunderson
What about using the Python bindings and actual Mapnik objects to create the XML file? It should be able to save an XML file, and that way you can abstract out all of the XML text from your program too... Beau On Wed, May 28, 2008 at 3:05 AM, Steve Hill <[EMAIL PROTECTED]> wrote: > On Tue, 27

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-28 Thread Steve Hill
On Tue, 27 May 2008, Andy Allan wrote: > Now, if someone is volunteering to make a concise definition format > that can be pre-processed into the mapnik XML format (or mapnik python > code, or even just read by a modified mapnik directly, or whatever) > then I'd absolutely love to SEE THE WORKING

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Robert (Jamie) Munro
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Barth wrote: | * Dave Stubbs ([EMAIL PROTECTED]) [080527 18:01]: |> I don't think inferring the LineSymbolizer is a good idea. But if you |> want to write a preprocessor to do the scale extraction I think that |> might help a lot. | | ok - thou

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Dave Stubbs
On Tue, May 27, 2008 at 6:29 PM, Robert (Jamie) Munro <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Andy Allan wrote: > | Now, if someone is volunteering to make a concise definition format > | that can be pre-processed into the mapnik XML format (or mapnik python

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Andreas Barth
* Andreas Barth ([EMAIL PROTECTED]) [080527 16:45]: > [...] I have now put a bit of that stuff together. All files (including sample code) is at http://alius.ayous.org/~aba/osm-formater-1/ I re-formated the road-sections. They now look like this: [highway] = 'primary' or [highway

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Rob
2008/5/27 Tom Hughes <[EMAIL PROTECTED]>: > Martijn van Oosterhout wrote: >> On Tue, May 27, 2008 at 7:29 PM, Robert (Jamie) Munro <[EMAIL PROTECTED]> >> wrote: >>> Here's some working code that simplifies the file: >>> sed "s/(\[bridge] = 'yes' or \[bridge]='true')/isBridge/g" osm.xml >>> >>> And

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Andreas Barth
* Robert (Jamie) Munro ([EMAIL PROTECTED]) [080527 20:07]: > If we can agree some basic ideas for how the format should work, and > what won't work, someone may come along and try to implement it. If you > just say "go away until you have finished the whole thing" every time, > it's not surprising

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Tom Hughes
Martijn van Oosterhout wrote: > On Tue, May 27, 2008 at 7:29 PM, Robert (Jamie) Munro <[EMAIL PROTECTED]> > wrote: >> Here's some working code that simplifies the file: >> sed "s/(\[bridge] = 'yes' or \[bridge]='true')/isBridge/g" osm.xml >> >> And the reverse: >> sed "s/isBridge/([bridge] = 'yes'

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Martijn van Oosterhout
On Tue, May 27, 2008 at 7:29 PM, Robert (Jamie) Munro <[EMAIL PROTECTED]> wrote: > Here's some working code that simplifies the file: > sed "s/(\[bridge] = 'yes' or \[bridge]='true')/isBridge/g" osm.xml > > And the reverse: > sed "s/isBridge/([bridge] = 'yes' or [bridge]='true')/g" I'm thinking of

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Robert (Jamie) Munro
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andy Allan wrote: | Now, if someone is volunteering to make a concise definition format | that can be pre-processed into the mapnik XML format (or mapnik python | code, or even just read by a modified mapnik directly, or whatever) | then I'd absolutely

Re: [OSM-talk] simplifying mapnik layout definition

2008-05-27 Thread Tom Hughes
In message <[EMAIL PROTECTED]> "Robert (Jamie) Munro" <[EMAIL PROTECTED]> wrote: > Here's some working code that simplifies the file: > sed "s/(\[bridge] = 'yes' or \[bridge]='true')/isBridge/g" osm.xml > > And the reverse: > sed "s/isBridge/([bridge] = 'yes' or [bridge]='true')/g" How