imposm using osm-bright mapping roads view fields missing
- Dominant language
- CartoCSS
- Stars
- 703
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
Not sure if this is the right place to ask but I'm using the osm-bright (https://github.com/mapbox/osm-bright/blob/master/imposm-mapping.py) mapping file when importing but the osm_roads view doesn't get built with the layer or access columns
roads = UnionView(
name = 'roads',
fields = (
('bridge', 0),
('ref', None),
('tunnel', 0),
('oneway', 0),
('layer', 0),
('z_order', 0),
('access', None),
),
mappings = [motorways, mainroads, minorroads, railways],
)
I also noticed that roads_gen0 and roads_gen1 don't have a access column even though the mapping specifies access in their fields. Subsequently when I run TileMill against the OSM Bright project SQL queries fail. Anyone run across this problem? Is this a problem with imposm or osm-bright?
Thanks
Ted
Contributor guide
Research direction
Start with imposm-mapping.py and compare the roads UnionView fields with the generated osm_roads, roads_gen0, and roads_gen1 views. Reproduce the import and then run the OSM Bright TileMill SQL queries to determine whether the missing layer and access columns originate in the mapping or in imposm. Done means the expected columns are present and the queries no longer fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100