Mapnik renders only points L(

Mapnik renders only points :frowning: Why?

Map example:

http://phoenix.novsu.ac.ru/image.png (5000x10000)

Can anyone faced with similar problems? Below are a few information for diagnostics:

List of the tables:


gis=# \d+
                           List of relations
 Schema |        Name        | Type  | Owner |    Size    | Description
--------+--------------------+-------+-------+------------+-------------
 public | geometry_columns   | table | root  | 8192 bytes |
 public | planet_osm_line    | table | root  | 0 bytes    |
 public | planet_osm_nodes   | table | root  | 1384 kB    |
 public | planet_osm_point   | table | root  | 104 kB     |
 public | planet_osm_polygon | table | root  | 0 bytes    |
 public | planet_osm_rels    | table | root  | 24 kB      |
 public | planet_osm_roads   | table | root  | 0 bytes    |
 public | planet_osm_ways    | table | root  | 1752 kB    |
 public | spatial_ref_sys    | table | root  | 2944 kB    |

planet_osm_line, planet_osm_polygon, planet_osm_roads - empty tables. Perhaps it’s necessary? I Could not find the information about database structure.

osm2pgsql output (seems good):


#osm2pgsql -c -s -d gis map_novgorod.osm
osm2pgsql SVN version 0.69-exported

Using projection SRS 900913 (Spherical Mercator)
Setting up table: planet_osm_point
NOTICE:  table "planet_osm_point_tmp" does not exist, skipping
Setting up table: planet_osm_line
NOTICE:  table "planet_osm_line_tmp" does not exist, skipping
Setting up table: planet_osm_polygon
NOTICE:  table "planet_osm_polygon_tmp" does not exist, skipping
Setting up table: planet_osm_roads
NOTICE:  table "planet_osm_roads_tmp" does not exist, skipping
Mid: pgsql, scale=100, cache=800MB, maxblocks=102401*8192
Setting up table: planet_osm_nodes
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_nodes_pkey" for table "planet_osm_nodes"
Setting up table: planet_osm_ways
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_ways_pkey" for table "planet_osm_ways"
Setting up table: planet_osm_rels
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_rels_pkey" for table "planet_osm_rels"

Reading in file: map_novgorod.osm
WARNING: Found Out of order node 281917304 (2372461,888) - this will impact the cache efficiency
Processing: Node(33k) Way(8k) Relation(0k)
Node stats: total(33064), max(840236497)
Way stats: total(8868), max(70417731)
Relation stats: total(37), max(409962)

Going over pending ways
processing way (3k)

Going over pending relations

node cache: stored: 7535(22.79%), storage efficiency: 0.43%, hit rate: 22.35%
Stopping table: planet_osm_nodes
Stopping table: planet_osm_ways
Committing transaction for planet_osm_roads
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Stopped table: planet_osm_nodes
Building index on table: planet_osm_ways
Sorting data and creating indexes for planet_osm_line
Sorting data and creating indexes for planet_osm_roads
Sorting data and creating indexes for planet_osm_polygon
Stopping table: planet_osm_rels
Building index on table: planet_osm_rels
Stopped table: planet_osm_rels
Completed planet_osm_line
Committing transaction for planet_osm_point
Completed planet_osm_roads
Sorting data and creating indexes for planet_osm_point
Completed planet_osm_polygon
Completed planet_osm_point
Stopped table: planet_osm_ways

osm.xml: http://phoenix.novsu.ac.ru/osm.xml (~350Кб)
map: http://phoenix.novsu.ac.ru/map_novgorod.osm (~8Мб)

I’m not sure those line/polygon/road entries should be 0. Mine looks like:


gis=# \d+
                            List of relations
 Schema |        Name        | Type  | Owner  |    Size    | Description 
--------+--------------------+-------+--------+------------+-------------
 public | geometry_columns   | table | pberck | 8192 bytes | 
 public | planet_osm_line    | table | pberck | 940 MB     | 
 public | planet_osm_nodes   | table | pberck | 2734 MB    | 
 public | planet_osm_point   | table | pberck | 262 MB     | 
 public | planet_osm_polygon | table | pberck | 1098 MB    | 
 public | planet_osm_rels    | table | pberck | 221 MB     | 
 public | planet_osm_roads   | table | pberck | 122 MB     | 
 public | planet_osm_ways    | table | pberck | 5274 MB    | 
 public | spatial_ref_sys    | table | pberck | 8192 bytes | 
(9 rows)

-peter

I am facing the same problem can anybody help…please
my---- planet_osm_line, planet_osm_polygon, planet_osm_roads tables are also empty exactly the same problem as above

Did you run _int.sql as part of the db initialisation? And postgis is loaded?

codenet and fast, I’m experiencing the exact same problem. Did you resolve your issues? Ldp, yes postgis is loaded. Note the geometry_columns and spatial_ref_sys tables codenet references, I have the same and they are populated with correct data, further all the postgis functions are there.

An example of the osm2pgsql command I run:

./osm2pgsql -d -E EPSG:4326 -p osm -v -c alabama.osm.bz2

And I get points… nada on anything else. I’ve done this in the past (1.5yr ago) and have seen success, I don’t know what is different this time around.

maps=# \d+
List of relations
Schema | Name | Type | Owner | Size | Description
--------±---------------------------------±---------±---------±-----------±------------
public | geometry_columns | table | postgres | 8192 bytes |
public | land | table | postgres | 152 MB |
public | land_gid_seq | sequence | postgres | 8192 bytes |
public | lines_whistler_blackcomb | table | postgres | 280 kB |
public | lines_whistler_blackcomb_gid_seq | sequence | postgres | 8192 bytes |
public | osm_line | table | postgres | 0 bytes |
public | osm_point | table | postgres | 6696 kB |
public | osm_polygon | table | postgres | 0 bytes |
public | osm_roads | table | postgres | 0 bytes |
public | spatial_ref_sys | table | postgres | 2960 kB |
public | state_borders | table | postgres | 8192 bytes |
public | state_borders_gid_seq | sequence | postgres | 8192 bytes |

Try -l instead of -E EPSG:4326. -l is the same thing, but I think I’ve read about someone else where -E didn’t quite work.

If that’s the case, it will need to be fixed in osm2pgsql.

I resolved the problem by compiling and installing libgeos-dev direct from the source (latest version)