source: subversion/applications/rendering/toposm/readme.txt @ 34399

Last change on this file since 34399 was 28464, checked in by ahlzen, 7 years ago

Added note in readme about development moved to github

File size: 2.2 KB
Line 
1TopOSM README
2
3Lars Ahlzen
4lars (at) ahlzen.com
5
6
7NOTE: TopOSM development has moved to GitHub:
8https://github.com/Ahlzen/TopOSM
9
10
11Requirements:
12-------------
13* Standard UN*X tools (bash, sed, awk, ...)
14* Mapnik
15* PostgreSQL
16* _int.sql (from postgresql-contrib) for PostgreSQL
17* PostGIS
18* 900913.sql projection (from osm2pgsql) for PostGIS
19* Python 2.5/2.6, with:
20  - Numpy
21  - Mapnik
22* Imagemagick
23* GDAL/OGR (including utility programs)
24* osm2pgsql (for planet import)
25* shp2pgsql (for NHD import)
26* Perrygeo DEM tools (hillshade, color-relief)
27  See: http://www.perrygeo.net/wordpress/?p=7
28* OptiPNG (for tile optimization)
29
30Data needed:
31------------
32* builtup_area.shp (from OSM svn, mapnik)
33* processed_p.shp (from OSM svn, mapnik)
34* world_bnd_m.shp (from OSM svn, mapnik)
35* USGS NED 1/3" http://openstreetmap.us/ned/13arcsec/grid/
36  (you can use the supplied get_ned script)
37* USGS NHD http://www.openstreetmap.us/nhd/
38* Planet.osm http://planet.openstreetmap.org/
39  (or other OSM data dump)
40
41Setup
42-----
43* Build/install requirements (see above).
44* Download required data sets.
45* Setup PostgreSQL with PostGIS. See OSM wiki.
46* Create a PostGIS database.
47* Modify and source set-toposm-env.
48* Run import_planet.
49* Run import_nhd.
50* Run prep_contours_table.
51
52Render an area:
53---------------
54This example will render the area UTM19T (defined in areas.py) from
55zoom level 5 through 15:
56
57$ source set-toposm-env
58$ python
59>>> import toposm
60>>> import areas
61>>> toposm.prepareData(areas.UTM19T)
62>>> toposm.renderTiles(areas.UTM19T, 5, 15)
63$ optimize_png.py tile/contours
64$ optimize_png.py tile/features
65
66
67Notes:
68------
69Make sure that you have plenty of disk space for temporary
70files and tiles, and database space for contour lines.
71
72Preprocessed data files (such as the hillshade and colormap
73images) are stored in the temp directory. Empty .shp files are also
74left here to mark areas where contours have already been imported
75into the database. NOTE: If you clear the data in this directory,
76you should also delete all data from the contours table, or you
77risk ending up with duplicated contours the next time you run
78prepareData.
79
80In TopOSM, rendering quality takes precedence over speed. You'll
81notice.
Note: See TracBrowser for help on using the repository browser.