Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Look at landuse / natural values for displaying relation summaries #2424

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Comments

@openstreetmap-trac
Copy link

Reporter: Vid the Kid
[Submitted to the original trac issue database at 12.35pm, Saturday, 7th November 2009]

Here's an area I've been working on lately: [http://www.openstreetmap.org/?lat=40&lon=-83&zoom=12]. I've been basically filling the map with landuse=* and natural=* areas, based on Yahoo! imagery. Rather than having a bunch of closed ways that overlap and share nodes, it seems to be a time saver to use multipolygon relations -- not to mention producing data that's more elegant. And some people may call me crazy for trying to do something so complicated in Potlatch, but that's what I'm doing.

The problem is that I can wind up with several multipolygon relations loaded at a time, all of which have only the tags "type=multipolygon" and "landuse=" or "natural=". And unless I actually open up the relation tag editor, Potlatch refers to each of these relations as simply "multipolygon".

I haven't studied ActionScript before, but it looks a lot like several other languages I've worked with. So I'm going to attach here a replacement I've come up with for some functions in relation.as. This should make it a little more intuitive to work with multipolygon relations that have tags "place=", "amenity=", "leisure=", "landuse=", or "natural=". (These are the types of multipolygon features that seem to me most likely to share their outer ways with other features, and therefore have the tagging on the relation rather than the ways.) This will be especially helpful for relations that don't have "name=" or "ref=" tags, which is quite possible of "landuse=" and "natural=*" multipolygons.

@openstreetmap-trac
Copy link
Author

Author: Richard
[Added to the original trac issue at 12.49am, Monday, 9th November 2009]

Makes a lot of sense - and thank you for the patch! Will be in the next version.

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

No branches or pull requests

1 participant