On 27/04/12 20:11, Anthony wrote:
> On Fri, Apr 27, 2012 at 3:06 PM, Tobias Knerr wrote:
>> Anthony wrote:
>> If I were writing a renderer (actually, I am), I would assume that a
>> closed way does not represent an area unless it a) has an always-area
>> tag such as landuse or b) is tagged with ar
On 4/28/2012 4:06 AM, Marl wrote:
By the way - why are you tagging railway=platform? The public transport
scheme has changed this to public_transport=platform more than a year ago.
Because old habits die hard, especially when the new standard is
convoluted as all hell.
__
It's the standard to draw a waterway in the direction of flow. I've
questioned this several times, but it's an ingrained default.
My question is more specific: what happens to a drainage canal that
reverses direction? I offer the Everglades and surrounding agricultural
land as an example. Ther
Can you give a picture of multi-lane cycleways (or coordinates, so we can
see it in aerial pics or via streetview)?
The only multi-lane cycleways I know are two-direction cycleways, where the
lines are only a suggestion. So it doesn't really matter whether it's a
two-way cycleway with one or two l
Let's consider two well known examples:
building=* => usually by default area=yes, a non-closed way may be
considered as invalid(?)
highway=* => usually by default area=no, even if a closed way
A common default value would lead to either
~56M area=yes on buildings
or
~52M area=no on highways
Interesting question.
I do have do navigable canals that can have the water flow in either
direction, under operator control. I think there must be many of them.
I so far have not bothered about the flow direction, as boat traffic goes
both ways independently of the actual flow of the water, but yo
28.04.2012 11:34, Peter Wendorff wrote:
> Let's consider two well known examples:
>
> building=* => usually by default area=yes, a non-closed way may be
> considered as invalid(?)
Yes, it would be invalid. As documented in the wiki, the building key
(ignoring building=entrance and the like) is fo
Am 28. April 2012 11:34 schrieb Peter Wendorff :
> On the other hand, a fenced field is landuse=* (and in this respect
> implicitly area=yes) and barrier=fence (and here implicitly area=no), and
> that's fine.
I'd tag the way barrier=fence and create a multipolygon for the
landuse with this way a
On 28 April 2012 11:32, Sander Deryckere wrote:
> Can you give a picture of multi-lane cycleways (or coordinates, so we can
> see it in aerial pics or via streetview)?
>
>
https://maps.google.com/maps?q=Copenhagen,+Denmark&hl=en&ll=55.671836,12.575965&spn=0.000243,0.00108&sll=49.232898,6.991044&s
28.04.2012 11:24, Nathan Edgars II wrote:
> So there are a lot of major canals that have no fixed direction. How
> should these be mapped? Is there any existing scheme that can show how
> water flows under different conditions?
We have this abandoned proposal for explicitly mapping flow directions
Am 17. Januar 2012 17:29 schrieb sylvain letuffe :
>> Last but not least I'd like to ask you for comments on 3 new values:
>> N1. a bridge made of few ropes where you walk on a rope:
>> http://bauwiki.tugraz.at/pub/Baulexikon/HaengeSeilBrueckeB/Kaiserschild_1.jpg
>> http://www.gruppenstunden-freize
On Sat, Apr 28, 2012 at 4:06 AM, Marl wrote:
> On 27/04/12 20:11, Anthony wrote:
>> On Fri, Apr 27, 2012 at 3:06 PM, Tobias Knerr wrote:
>>> Anthony wrote:
>>> If I were writing a renderer (actually, I am), I would assume that a
>>> closed way does not represent an area unless it a) has an always
On 4/28/2012 5:32 AM, Sander Deryckere wrote:
Can you give a picture of multi-lane cycleways (or coordinates, so we
can see it in aerial pics or via streetview)?
Not quite what you're looking for, but here's another weird edge case
with a "pedestrian lane" rather than a sidewalk:
http://maps.
> I think we should decide the better way to map first, and then let the
> programmers prioritize the fix. Since programmers are already
> checking for always-area, it doesn't seem like a difficult fix. Are
> patches welcome?
Patches welcome.
As programmers, we need a complete machine-readable
On Sat, Apr 28, 2012 at 6:04 AM, Tobias Knerr wrote:
> I assume that this is a misunderstanding, because I don't think anybody
> was suggesting that area=yes should be used together with tags that are
> unambiguous anyway. My suggestion, and current practice as far as I can
> tell, is:
>
> * If a
On Sat, Apr 28, 2012 at 7:38 AM, Komяpa wrote:
>> I think we should decide the better way to map first, and then let the
>> programmers prioritize the fix. Since programmers are already
>> checking for always-area, it doesn't seem like a difficult fix. Are
>> patches welcome?
>
> Patches welcome
On Sat, Apr 28, 2012 at 7:59 AM, Anthony wrote:
> Scanning the wiki it looks like usually-not-area would be less of a
> moving target. Otherwise almost every time someone adds a new amenity
> you have to add a new always-area tag. The usually-not-area would be
> junction=roundabout, barrier=*, h
> What specific program or programs are we looking at?
Any program that needs to go from OSM data model to OGC-compatible
one, having "area" object.
That basically lists any database backend (osm2pgsql, osm2sqlite,
nominatim...) and any converter like osm2shp/osm2ogr.
The list of software that dep
On Sat, Apr 28, 2012 at 8:17 AM, Komяpa wrote:
>> What specific program or programs are we looking at?
>
> Any program that needs to go from OSM data model to OGC-compatible
> one, having "area" object.
Well, my question is what program or programs are you requesting
patches for. Presumably thes
On 27.04.2012 10:12, Pieren wrote:
> You have to know anyway if your feature can be either a closed way or
> an area and therefore need some special handling in your apps.
Unfortunately, yes. I wish we already had a proper area primitive so
this whole discussion would be obsolete.
> The question
On 4/28/2012 7:59 AM, Anthony wrote:
Scanning the wiki it looks like usually-not-area would be less of a
moving target. Otherwise almost every time someone adds a new amenity
you have to add a new always-area tag. The usually-not-area would be
junction=roundabout, barrier=*, highway=pedestrian,
On Sat, Apr 28, 2012 at 9:16 AM, Tobias Knerr wrote:
> Right now, we already have to distinguish three types of tags:
> * always area
> * always way
> * way unless area=yes is present.
>
> I simply do not think that the possibility to decrease of the number of
> tags is worth introducing "area unl
Another example is amenity=marketplace. How am I supposed to know if
this is "always way", "always area", or "way unless area=yes is
present"? Which one is it?
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/t
For the barrier=city_wall I in fact see way AND area as possible:
A mid-age city wall of a bigger city may have walls of several meters
width sometimes, that include corridors, stairways and more, as another
building would.
If I map a strip of grass as an area with a width of 1m, a city wall
wi
In many European canals, the convention is for the waterway authorities
to arbitrarily define a direction so that a 'left' and 'right' bank can
be defined and the appropriate navigational marks installed. So in those
cases, where you see red on one side and green on the other, the
nominated 'di
On 28 April 2012 16:14, Malcolm Herring wrote:
> In many European canals, the convention is for the waterway authorities to
> arbitrarily define a direction so that a 'left' and 'right' bank can be
> defined and the appropriate navigational marks installed. So in those
> cases, where you see red o
On Sat, Apr 28, 2012 at 2:32 AM, Sander Deryckere wrote:
> Can you give a picture of multi-lane cycleways (or coordinates, so we can
> see it in aerial pics or via streetview)?
http://g.co/maps/eyfz7 (Westbound Hawthorne Bridge, the passing lane
for bikes is the left one; that lane ends at the to
Am 28. April 2012 16:10 schrieb Peter Wendorff :
> For the barrier=city_wall I in fact see way AND area as possible:
> A mid-age city wall of a bigger city may have walls of several meters width
> sometimes, that include corridors, stairways and more, as another building
> would.
> If I map a strip
On Sat, Apr 28, 2012 at 10:10 AM, Peter Wendorff
wrote:
> For the barrier=city_wall I in fact see way AND area as possible:
Isn't area always possible?
> I think, we should (!) introduce an area tag in the next API version, that
> allows the strict distinction between area and way by type, indep
At 2012-04-28 02:24, Nathan Edgars II wrote:
It's the standard to draw a waterway in the direction of flow. I've
questioned this several times, but it's an ingrained default.
My question is more specific: what happens to a drainage canal that
reverses direction? I offer the Everglades and surr
On Apr 28, 2012 8:43 PM, "Alan Mintz" wrote:
> oneway=no would make sense, since the (unusual) default assumption for
this type of object appears to be oneway=yes.
It's possible that there are places where the waterway is legally
restricted to travel in one direction. oneway:flow=* may be bette
31 matches
Mail list logo
