Skip to content

Commit 71d6de6

Browse files
author
Steve Chilton
committed
add three addr: lines
1 parent cb22845 commit 71d6de6

1 file changed

Lines changed: 98 additions & 95 deletions

File tree

default.style

Lines changed: 98 additions & 95 deletions
Original file line numberDiff line numberDiff line change
@@ -1,95 +1,98 @@
1-
# This is the style file that matches the old version of osm2pgsql, which
2-
# did not make distinctions between tags for nodes and for ways. There are a
3-
# number of optimisations that can be applied here. Firstly, certain tags
4-
# only apply to only nodes or only ways. By fixing this we reduce the amount
5-
# of useless data loaded into the DB, which is a good thing. Possible
6-
# optimisations for the future:
7-
8-
# 1. Generate this file directly from the mapnik XML config, so it's always
9-
# optimal
10-
11-
# 2. Extend it so it can understand that highway=tertiary is for ways and
12-
# highway=bus_stop is for nodes
13-
14-
# Flags field isn't used much yet, expect if it contains the text "polygon"
15-
# it indicates the shape is candidate for the polygon table. In the future I
16-
# would like to be able to add directives like "nocache" which tells
17-
# osm2pgsql that it is unlikely this node will be used by a way and so it
18-
# doesn't need to be stored (eg coastline nodes). While in essence an
19-
# optimisation hack, for --slim mode it doesn't matter if you're wrong, but
20-
# in non-slim you might break something!
21-
22-
# Also possibly an ignore flag, for things like "note" and "source" which
23-
# can simply be deleted. (In slim mode this is, does not apply to non-slim
24-
# obviously)
25-
26-
# OsmType Tag DataType Flags
27-
node,way note text delete # These tags can be long but are useless for rendering
28-
node,way source text delete # This indicates that we shouldn't store them
29-
30-
node,way access text linear
31-
node,way admin_level text linear
32-
node,way aerialway text linear
33-
node,way aeroway text polygon
34-
node,way amenity text nocache,polygon
35-
node,way area text # hard coded support for area=1/yes => polygon is in osm2pgsql
36-
node,way barrier text linear
37-
node,way bicycle text nocache
38-
node,way bridge text linear
39-
node,way boundary text linear
40-
node,way building text polygon
41-
node,way cutting text linear
42-
node,way disused text linear
43-
node ele text linear
44-
node,way embankment text linear
45-
node,way foot text linear
46-
node,way highway text linear
47-
node,way historic text polygon
48-
node,way horse text linear
49-
node,way junction text linear
50-
node,way landuse text polygon
51-
node,way layer text linear
52-
node,way learning text linear
53-
node,way leisure text polygon
54-
node,way man_made text polygon
55-
node,way military text polygon
56-
node,way motorcar text linear
57-
node,way name text linear
58-
node,way natural text polygon # natural=coastline tags are discarded by a hard coded rule in osm2pgsql
59-
node,way oneway text linear
60-
node poi text
61-
node,way power text polygon
62-
node,way power_source text linear
63-
node,way place text linear
64-
node,way railway text linear
65-
node,way ref text linear
66-
node,way religion text nocache
67-
node,way residence text linear
68-
node,way route text linear
69-
node,way sport text polygon
70-
node,way tourism text polygon
71-
way tracktype text linear
72-
node,way tunnel text linear
73-
node,way waterway text polygon
74-
node,way width text linear
75-
node,way wood text linear
76-
node,way z_order int4 linear # This is calculated during import
77-
way way_area real # This is calculated during import
78-
79-
# If you're interested in bicycle routes, you may want the following fields
80-
# To make these work you need slim mode or the necessary data won't be remembered.
81-
#way lcn_ref text linear
82-
#way rcn_ref text linear
83-
#way ncn_ref text linear
84-
#way lcn text linear
85-
#way rcn text linear
86-
#way ncn text linear
87-
#way lwn_ref text linear
88-
#way rwn_ref text linear
89-
#way nwn_ref text linear
90-
#way lwn text linear
91-
#way rwn text linear
92-
#way nwn text linear
93-
#way route_pref_color text linear
94-
#way route_name text linear
95-
1+
# This is the style file that matches the old version of osm2pgsql, which
2+
# did not make distinctions between tags for nodes and for ways. There are a
3+
# number of optimisations that can be applied here. Firstly, certain tags
4+
# only apply to only nodes or only ways. By fixing this we reduce the amount
5+
# of useless data loaded into the DB, which is a good thing. Possible
6+
# optimisations for the future:
7+
8+
# 1. Generate this file directly from the mapnik XML config, so it's always
9+
# optimal
10+
11+
# 2. Extend it so it can understand that highway=tertiary is for ways and
12+
# highway=bus_stop is for nodes
13+
14+
# Flags field isn't used much yet, expect if it contains the text "polygon"
15+
# it indicates the shape is candidate for the polygon table. In the future I
16+
# would like to be able to add directives like "nocache" which tells
17+
# osm2pgsql that it is unlikely this node will be used by a way and so it
18+
# doesn't need to be stored (eg coastline nodes). While in essence an
19+
# optimisation hack, for --slim mode it doesn't matter if you're wrong, but
20+
# in non-slim you might break something!
21+
22+
# Also possibly an ignore flag, for things like "note" and "source" which
23+
# can simply be deleted. (In slim mode this is, does not apply to non-slim
24+
# obviously)
25+
26+
# OsmType Tag DataType Flags
27+
node,way note text delete # These tags can be long but are useless for rendering
28+
node,way source text delete # This indicates that we shouldn't store them
29+
30+
node,way access text linear
31+
node,way addr:flats text polygon
32+
node,way addr:housenumber text linear
33+
node,way addr:interpolation text linear
34+
node,way admin_level text linear
35+
node,way aerialway text linear
36+
node,way aeroway text polygon
37+
node,way amenity text nocache,polygon
38+
node,way area text # hard coded support for area=1/yes => polygon is in osm2pgsql
39+
node,way barrier text linear
40+
node,way bicycle text nocache
41+
node,way bridge text linear
42+
node,way boundary text linear
43+
node,way building text polygon
44+
node,way cutting text linear
45+
node,way disused text linear
46+
node ele text linear
47+
node,way embankment text linear
48+
node,way foot text linear
49+
node,way highway text linear
50+
node,way historic text polygon
51+
node,way horse text linear
52+
node,way junction text linear
53+
node,way landuse text polygon
54+
node,way layer text linear
55+
node,way learning text linear
56+
node,way leisure text polygon
57+
node,way man_made text polygon
58+
node,way military text polygon
59+
node,way motorcar text linear
60+
node,way name text linear
61+
node,way natural text polygon # natural=coastline tags are discarded by a hard coded rule in osm2pgsql
62+
node,way oneway text linear
63+
node poi text
64+
node,way power text polygon
65+
node,way power_source text linear
66+
node,way place text linear
67+
node,way railway text linear
68+
node,way ref text linear
69+
node,way religion text nocache
70+
node,way residence text linear
71+
node,way route text linear
72+
node,way sport text polygon
73+
node,way tourism text polygon
74+
way tracktype text linear
75+
node,way tunnel text linear
76+
node,way waterway text polygon
77+
node,way width text linear
78+
node,way wood text linear
79+
node,way z_order int4 linear # This is calculated during import
80+
way way_area real # This is calculated during import
81+
82+
# If you're interested in bicycle routes, you may want the following fields
83+
# To make these work you need slim mode or the necessary data won't be remembered.
84+
#way lcn_ref text linear
85+
#way rcn_ref text linear
86+
#way ncn_ref text linear
87+
#way lcn text linear
88+
#way rcn text linear
89+
#way ncn text linear
90+
#way lwn_ref text linear
91+
#way rwn_ref text linear
92+
#way nwn_ref text linear
93+
#way lwn text linear
94+
#way rwn text linear
95+
#way nwn text linear
96+
#way route_pref_color text linear
97+
#way route_name text linear
98+

0 commit comments

Comments
 (0)