Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In relation_member mapping is applied to member, not relation #129

Closed
andreynovikov opened this issue Dec 2, 2016 · 3 comments · Fixed by #146
Closed

In relation_member mapping is applied to member, not relation #129

andreynovikov opened this issue Dec 2, 2016 · 3 comments · Fixed by #146

Comments

@andreynovikov
Copy link

Documentation says that mapping is done on relation tags, but when I try to use type: [building] mapping it produces empty table. But when I change it to building: [__any__] mapping it produces table that contains all the buildings found in relations. But this is not what I want as it also contains all multipolygons.

@andreynovikov
Copy link
Author

No, I'm wrong. But I still fail to import building relation members. Investigating it further...

@andreynovikov
Copy link
Author

andreynovikov commented Dec 2, 2016

Ok, the title is incorrect but the bug exists. Trying to import the mapping:

tables:
  building_parts:   
    type: relation_member
    columns:         
      - name: osm_id 
        type: id
      - name: member
        type: member_id
      - name: role   
        type: member_role
      - name: type   
        key: type
        type: string
    mapping:         
      type: [building]

produces empty table unless I add:

tags:
  load_all: true
```

@olt
Copy link
Member

olt commented May 15, 2017

load_all: true is no longer needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants