Skip to content

Relations not returning error in MGCP translation when unable to translate #4970

@brianhatchl

Description

@brianhatchl

I would expect that if the tags of a relations could not be translated to an FCODE, the translation would return the tag error=No Valid Feature Code like it does for nodes and ways. Instead, is seems the OSM tags just pass through.

I'll create a branch with a test that is failing in this scenario.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions