Database-reload

[matthijsmelissen]

This is a pull-request against the lua branch

This is a new version of #2105. No changes except for dropping some commented lines.

This PR proposes a database-reload. It changes the documentation on the use of
osm2pgsql, and adds a .lua file for preprocessing.

This database import aims to be backwards compatible with older versions of
the style.

This resolves (at least part of) #1504.

Hstore

Adding the hstore option to osm2pgsql allows the database to use all keys.

This PR proposes using hstore for new keys, and using traditional columns for
old keys. This allows us to stay compatible with old versions of the style.

According to @pnorman's benchmarks,
using hstore without dropping columns would lead to a 9% size increase and a
0.38% speed decrease. Given the benefits of having all columns available, I
would consider this acceptable.

Make polygon/linestring decision based on value

This is based on the following unmerged PR to osm2pgsql:
osm2pgsql-dev/osm2pgsql#346

It makes the polygon/linestring decision based on the tag value, in addition to
the tag key. In particular, highway=services and junction=yes are now treated as
polygon, while leisure=track, man_made=embankment, man_made=breakwater,
man_made=groyne, natural=cliff, natural=tree_row, historic=citywalls,
waterway=derelict_canal, waterway=ditch, waterway=drain, waterway=river,
waterway=stream, waterway=wadi, waterway=weir, power=line, and power=minor_line
are now treated as linestring.

This resolves #1362, resolves #137, resolves #268, and resolves #892.

Rendering order

The new .lua file creates a osmcarto_z_order value in the database, which stores
the rendering order we use. This will allow us to simplify the road queries.

This resolves #59.

Import ele on buildings

This resolves #101.

Delete more meta-tags from imports

The .lua file drops some more meta-information from imports that is of no
need for rendering.

This is based on the following unmerged PR to osm2pgsql:

• Add more tags from imports to list of deleted tags osm2pgsql-dev/osm2pgsql#532

[matthijsmelissen]

Woops, pull request against the wrong branch, fixed in #2128.

[dieterdreist]

sent from a phone

Il giorno 16 mag 2016, alle ore 02:39, math1985 [email protected] ha scritto:

leisure=track, man_made=embankment, man_made=breakwater,
man_made=groyne, natural=cliff, natural=tree_row, historic=citywalls,
waterway=derelict_canal, waterway=ditch, waterway=drain, waterway=river,
waterway=stream, waterway=wadi, waterway=weir, power=line, and power=minor_line
are now treated as linestring.

is there an override (area=yes) to treat them as polygons where applicable?
I d expect leisure=track, man_made=breakwater, waterway=weir, man_made=embankment, historic=citywalls and maybe others, to be (sometimes) mapped (and valid) as polygons.

[matthijsmelissen]

is there an override (area=yes) to treat them as polygons where applicable?

Yes, area=yes can be used to override these (just like for highway tags)