olt
commented
11 years ago The import should be finished. PostGIS failed during the optimization process. I think the reason is that Imposm3 doesn't clip the OSM data to the valid EPSG:3857 boundary (which only goes to -85S/+85N). I'll create a new ticket for that.
Imported whole planet today. Last entry was below:
[Sep 14 17:31:26] Importing OSM data took: 5h50m35.894984255s [Sep 14 17:31:30] [PostGIS] Indexing osm_aeroways on geohash took: 3.462870059s [Sep 14 17:31:40] [PostGIS] Clustering osm_aeroways on geohash took: 9.913250879s [Sep 14 17:31:52] [PostGIS] Indexing osm_amenities on geohash took: 12.778158795s [Sep 14 17:31:58] [PostGIS] Indexing osm_housenumbers_interpolated on geohash took: 32.316584666s [Sep 14 17:32:11] [PostGIS] Clustering osm_amenities on geohash took: 18.777732759s [Sep 14 17:32:38] [PostGIS] Clustering osm_housenumbers_interpolated on geohash took: 39.538955536s [Sep 14 17:33:11] [PostGIS] Indexing osm_admin on geohash took: 1m44.931192332s [Sep 14 17:33:11] [PostGIS] Indexing osm_barrierpoints on geohash took: 33.368876128s [Sep 14 17:33:32] [PostGIS] Clustering osm_barrierpoints on geohash took: 20.554198242s [Sep 14 17:33:37] [PostGIS] Indexing osm_places on geohash took: 5.018755772s [Sep 14 17:33:37] [PostGIS] Clustering on geometry took: 2m10.798900936s [Sep 14 17:33:37] pq: S:"ERROR" C:"XX000" M:"transform: couldn't project point (-0.00460936 nan 0): failed to load NAD27-83 correction file (-38)" H:"PostGIS was unable to transform the point because either no grid shift files were found, or the point does not lie within the range for which the grid shift is defined. Refer to the ST_Transform() section of the PostGIS manual for details on how to configure PostGIS to alter this behaviour." F:"lwgeom_transform.c" L:"1058" R:"transform_point"
Is import successfully finished or not?