mapbox / osm-bright

A Carto template for OpenStreetMap data
BSD 3-Clause "New" or "Revised" License
698 stars 225 forks source link

Building with imposm did not create planet_osm_* tables #97

Closed laidig closed 9 years ago

laidig commented 9 years ago

I followed the instructions in the tutorial, and when I run tilemill, it can't access planet_osm_polygons.

Looking over the console, no planet_osm* tables are mentioned. Was imposm supposed to create this table?

~/Downloads$ imposm -U user -d osm -m ../osm_bright/mapbox-osm-bright-5f237ac/imposm-mapping.py --read --write --optimize --deploy-production-tables new-york_new-york.osm.pbf loading ../osm_bright/mapbox-osm-bright-5f237ac/imposm-mapping.py as mapping password for user at localhost: [14:23:43] ## reading new-york_new-york.osm.pbf [14:23:43] coords: 5144k nodes: 102k ways: 734k relations: 5k (estimated) [14:27:26] coords: 8216k nodes: 18k ways: 1355k relations: 3k [14:27:29] reading took 3 m 45s [... [14:42:33] ## optimizing tables Clustering table osm_new_mainroads Clustering table osm_new_buildings Clustering table osm_new_mainroads_gen1 Clustering table osm_new_mainroads_gen0 Clustering table osm_new_amenities Clustering table osm_new_waterareas_gen1 Clustering table osm_new_waterareas_gen0 Clustering table osm_new_motorways_gen0 Clustering table osm_new_aeroways Clustering table osm_new_motorways Clustering table osm_new_transport_points Clustering table osm_new_railways_gen0 Clustering table osm_new_railways_gen1 Clustering table osm_new_landusages Clustering table osm_new_waterways Clustering table osm_new_railways Clustering table osm_new_motorways_gen1 Clustering table osm_new_waterareas Clustering table osm_new_places Clustering table osm_new_admin Clustering table osm_new_barrierways Clustering table osm_new_minorroads Clustering table osm_new_barrierpoints Clustering table osm_new_landusages_gen1 Clustering table osm_new_landusages_gen0 Vacuum analyze [14:49:31] optimizing took 6 m 57s [14:49:31] imposm took 25m 47s

laidig commented 9 years ago

Closing because I think stackexchange is a better place for an answer.