Dear all,
[1] http://wiki.openstreetmap.org/wiki/Overpass_turbo/Polygon_Features
I have now adopted this list. Thus, there are now much more areas available
from overpass-api.de. The rambler instance has not been enlarged so far, but
will follow in a couple of days.
Cheers,
Roland
On 23.03.2013 02:13, Paul Norman wrote:
The canonical list of areas is all polygon entries in
http://svn.openstreetmap.org/applications/utils/export/osm2pgsql/default.sty
le
Anything with those tags will be considered an area by the osm2pgsql style
used for rendering tile.osm.org, which is
Am 23.03.2013, 02:13 Uhr, schrieb Paul Norman penor...@mac.com:
The canonical list of areas is all polygon entries in
http://svn.openstreetmap.org/applications/utils/export/osm2pgsql/default.sty
le
I came up with a more elaborate area-detection algorithm for
overpass-turbo [1], which
Am 24.03.2013, 15:40 Uhr, schrieb Tobias Knerr o...@tobias-knerr.de:
The wiki actually offers machine readable templates on the Key:* and
Tag:* pages with boolean flags such as onWay and onArea, which are
currently parsed by Taginfo and offered though the Taginfo API. Without
doubt there are
On 24.03.2013 17:01, Martin Raifer wrote:
The wiki (and thus also taginfo) has information about where a tag can
be used on, but not whether the tag defines an area or not. See the
following examples:
* natural=cliff has onWay=true and onArea=true and defines a way as an
area, if the way
2013/3/24 Tobias Knerr o...@tobias-knerr.de:
On 24.03.2013 17:01, Martin Raifer wrote:
* natural=cliff has onWay=true and onArea=true and defines a way as an
area, if the way forms a closed loop.
Well, the first example is the one that contradicts my expectations. I
assumed the general rule
There is an example of a line/area from indoor maps. In working in my
real job we model walls either as a line or an area, depending on the
resolution of the building source. A closed way can form an area-type
wall or it can form a line-type wall closed around a room or a
building.
I expect the
Am 23/mar/2013 um 02:13 schrieb Paul Norman penor...@mac.com:
The canonical list of areas is all polygon entries in
http://svn.openstreetmap.org/applications/utils/export/osm2pgsql/default.sty
le
Anything with those tags will be considered an area by the osm2pgsql style
used for
Hi all,
as of now, Overpass API has limited support for area queries: There is a
whitelist¹ of cases where relations and closed ways are treated as
areas. Most of the time it requires a name in addition to certain other
tags. Specifically, I stumbled upon the limitation that closed ways with
a
On 22 Mar 2013, at 19:58, Tobias Knerr o...@tobias-knerr.de wrote:
Hi all,
as of now, Overpass API has limited support for area queries: There is a
whitelist¹ of cases where relations and closed ways are treated as
areas. Most of the time it requires a name in addition to certain other
There seems to be a polygon search which lets you specify an arbitrary
bounding polygon. This should have the same function as a search for a
closed way, given the proper polygon coordinates. This means either
you can create the polygon yourself based on the coordinates of the
way or it ought to
Hi all,
Why just building=yes? I do my best to be more descriptive on the type of
building that it is, such as whether it is residential, industrial,
commercial, retail etc.
Thank you for the feedback. This helps to make a more complete list of tags.
So I assume a better criterion would be
On 22.03.2013 21:41, Dave Sutter wrote:
There seems to be a polygon search which lets you specify an arbitrary
bounding polygon. This should have the same function as a search for a
closed way, given the proper polygon coordinates. This means either
you can create the polygon yourself based on
Hi all,
I'm also curious about the motivation for considering only a strictly
limited subset of the areas in the database in the first place.
Presumably this is because maintaining a large number of areas would be
detrimental to performance?
First of all, thank you for taking it here. This
I like GeoJSON since it is JSON, which I find convenient, and it is a
standard. All the same, most vector rendering on clients is done using
the path formalism which doesn't distinguish between areas and lines
outside of applying the style to the geometry. It is kind of a shame
to have to worry
From: Roland Olbricht [mailto:roland.olbri...@gmx.de]
Subject: Re: [OSM-talk] Area tags in Overpass API
The reason to choose objects with name was that all use cases so far
have been variations of the question Where am I?. And without a name
or other distinctive tag value, the area has been
16 matches
Mail list logo
