Querying runway lengrh from the database - sorry I missed this proposal. I see three problems:
What about small airport next to big one - how it should be guessed who operates which runways? As both are mapped as nodes it is necessary to guess. Writing query to calculate it is not trivial (for start - runway may be segmented and consist of multiple ways). It is possible that such query will be too expensive to run it as it would degrade performance of rendering server. 2015-01-03 14:54 GMT+01:00 Christoph Hormann <chris_horm...@gmx.de>: > On Saturday 03 January 2015, Mateusz Konieczny wrote: > > - introducing new key that would allow to decide whatever > > airport is important or not > > Independent from this particular problem manually tagging importance > ratings is a really bad idea. Importance of a feature is nearly always > a multi-criterion quantity. To make such a rating verifiable would > require to have a recipe to calculate it from other observable facts - > and then it is better to tag these facts rather than the combined > rating calculated from them. > > As i have said on github the runway length would be a fairly good > criterion for importance and it is very widely available already (35551 > nodes aeroway=aerodrome with 31752 ways aeroway=runway). The problem > here is not having this information mapped i think but querying it from > the rendering database. > > -- > Christoph Hormann > http://www.imagico.de/ > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
