Re: [OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-02-02 Thread Frederik Ramm
Hi, Jonathan-David SCHRODER wrote: > As to precision issue, someone earlier on this list told (using the ruby > code as a prof) that the rails port would allow to store vector data > with integer precision up to 7cm without modifying anything to the rails > port (and for JOSM I don't know). I

Re: [OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-02-02 Thread Jonathan-David SCHRODER
Hi !! On Wed, Feb 3, 2010 at 1:45 AM, Frederik Ramm wrote: > Hi, > > > Jonathan-David SCHRODER wrote: > >> for the render_expired.c program (;-) ).. >> > > Uh-oh, that's my nasty little secret I believe. > > render_expired is more or less a version of render_list, but it processes > an expiry li

Re: [OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-02-02 Thread Frederik Ramm
Hi, Jonathan-David SCHRODER wrote: > for the render_expired.c program (;-) ).. Uh-oh, that's my nasty little secret I believe. render_expired is more or less a version of render_list, but it processes an expiry list coming from osm2pgsql. Because osm2pgsql has no knowledge about meta tiles, th

Re: [OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-02-02 Thread Jonathan-David SCHRODER
Hi, for the render_expired.c program (;-) ).. maximum zoom values all equal 18 and are hardcoded this namely also concerns the twopow[18] array thus the following macros give a segfault if all values 18 are replaced by something > 18 ; but it works ok for values <= 18 (tested with 16) #define TILE

Re: [OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-01-22 Thread Lennard
Jonathan-David SCHRODER wrote: > for our project (Geopard) which does indoor & outdoor mapping, we need > zoom levels up to 24 or so. > mod_tile's svn's render_config.h defines a constand #define MAX_ZOOM 18 > (and also MIN_ZOOM) > but this constant is used in only 2 or so files and the rest of

Re: [OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-01-21 Thread Jonathan-David SCHRODER
Hello, in mod_tile's Makefile, target install doesn't depend on make's defaut target (all).. so doing make install, doesn't run make (all)... this should be corrected : - install: ${DESTDIR}/etc/renderd.conf + install: all ${DESTDIR}/etc/renderd.conf Thanks in advance, Jonathan On Thu, Jan 21, 2

Re: [OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-01-21 Thread Jonathan-David SCHRODER
Hello, for our project (Geopard) which does indoor & outdoor mapping, we need zoom levels up to 24 or so. mod_tile's svn's render_config.h defines a constand #define MAX_ZOOM 18 (and also MIN_ZOOM) but this constant is used in only 2 or so files and the rest of max zoom values are hardcoded (just g

Re: [OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-01-15 Thread Jonathan-David SCHRODER
in renderd.conf we a same thing as in render_config.h ; - renderd.conf [mapnik] plugins_dir=/usr/local/lib64/mapnik/input font_dir=/usr/local/lib64/mapnik/fonts font_dir_recurse=1 -- render_config.h --

[OSM-dev] mod_tile svn's project variables 1)hardcoded 2)in many files

2010-01-15 Thread Jonathan-David SCHRODER
Hello, this relates to a feature request as to mod tile concering path variables. I stumbled upon this because I need to edit several files before starting to compile. In mod_tiles from http://svn.openstreetmap.org/applications/utils/mod_tile many paths are hardcoded in separate files it would be