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

[suggestion] Optionnal support for relation of relation aka "super-relation" #101

Closed
sletuffe opened this issue Oct 31, 2013 · 3 comments
Closed

Comments

@sletuffe
Copy link

For some needs it could be usefull if an optionnal switch param could enable support for "super-relation" (those relation whose members are relations whose members (...) are ways) in order to have geometries for them.

Such existing relation are quite rare atm but could include :
type=route for long route made of other routes
http://www.openstreetmap.org/browse/relation/20772
Country boundaries :
http://www.openstreetmap.org/browse/relation/1111111
http://www.openstreetmap.org/browse/relation/11980

@pnorman
Copy link
Collaborator

pnorman commented Sep 23, 2014

Given the typical rendering usecase, I'm not sure that type=route superrelations gain us anything since they'd be rendered from their members anyways.

For the first boundary example, it duplicates http://www.openstreetmap.org/relation/51477, which is a conventionally represented boundary relation for Germany.

@pnorman
Copy link
Collaborator

pnorman commented Jan 11, 2015

There doesn't seem to be interest in this and it's not obvious that we should be doing it anyways, given the duplication that would then be present.

@stefanct
Copy link

I think this decision should be reconsidered. It would reduce the need to ever duplicating the same values in all members of very large relations (e.g., eurovelo bicycle routes) (or breaking the rendering as happens quite regularly if someone does not know or forgets).

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

No branches or pull requests

3 participants