I've drafted a proposal for natural=rock_overhang at
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:natural%3Drock_overhang
please
provide any feedback or suggestions.
On Mon, 26 Oct 2020 at 15:10, Andrew Harvey
wrote:
> Voting is closed now with 8 yes, 8 no, 2 abstain. no clear conse
Voting is closed now with 8 yes, 8 no, 2 abstain. no clear consensus here
so marked as rejected.
Reviewing those against, a common theme is the view that amenity=shelter
should be reserved for purpose built/man made shelters and not natural
features commonly used as a place of shelter.
I'm still
On 2020-10-25 15:47, Allroads wrote:
> All landuse what is used for legally public roads, laid down in a zoning plan
> by the Government "bestemmingsplan" should be called landuse=highway no,
> because the content of a bestemmingsplan is what is politically desired and
> legally permitted, it i
as an additional datapoint
shop=ticket is the only one with significant usage: (15000)
https://taginfo.openstreetmap.org/search?q=ticket#values
From its definition, it could also not be suitable (unclear), or maybe it is?
https://wiki.openstreetmap.org/wiki/Tag%3Ashop%3Dticket
vending=admission
That is an excellent point - perhaps a better definition would say:
"A *special economic zone (SEZ)* is a government-defined area in which
business and trade laws are different."
This leaves the scope open and allows for future subtagging for future
specificity.
On Sun, Oct 25, 2020 at 10:39 AM
All landuse what is used for legally public roads, laid down in a zoning
plan by the Government "bestemmingsplan" should be called landuse=highway
no, because the content of a bestemmingsplan is what is politically desired
and legally permitted, it is a plan. Landuse is not about the zoning pla
sent from a phone
> On 25. Oct 2020, at 15:24, Brian M. Sperlongano wrote:
>
> The point is to provide a standard, non-cryptic, foundational tag for such
> areas. Perhaps future proposals might further propose tagging for which
> level of government has declared the SEZ, or the type of SEZ,
On 25-10-2020 14:55, Janko Mihelić wrote:
> Relations are definitely safer, but I wanted to add a unique name
> version for new editors that are intimidated by relations.
> Also for cases when you would have a lot of admission issuers, so we
> don't get some humongous relations. Maybe there's a ven
SEZs are certainly not de facto. By definition, they are defined by laws
that apply only to a certain area. Therefore, they are both defined by a
government, and have defined geographic limits.
As to whether an SEZ is defined by a national government, or a sub-national
government, that question
sent from a phone
> On 25. Oct 2020, at 14:41, Allroads wrote:
>
> All landuse what is used for legally public roads, laid down in a zoning plan
> by the Government "bestemmingsplan" should be called landuse=highway
no, because the content of a bestemmingsplan is what is politically desired
On Sun, Oct 25, 2020, 12:59 Martin Koppenhoefer
wrote:
> An alternative idea could be to use the type=site relation, add the ticket
> office with an appropriate role to the relation (e.g. "sells_tickets").
> Maybe the term "sells" should be omitted, because sometimes you need a
> ticket, but it i
For me, the value "parking_space" what key, single space problem must
be fixed first to say something about "street_side". As it comes to a
vote.
Could you elaborate?
amenity=parking_space can be used as usual within amenity=parking. This
of course also works with amenity=parking/parking=s
I think it would be generally useful to add this kind of information, not
only when the ticket office is spatially distant from the feature, but in
every case where a ticket is needed. An alternative idea could be to use
the type=site relation, add the ticket office with an appropriate role to
the
Am So., 25. Okt. 2020 um 05:34 Uhr schrieb Brian M. Sperlongano <
zelonew...@gmail.com>:
> A special economic zone (SEZ) is an area in which the business and trade
> laws are different from the rest of the country. Only a small number of
> these areas are mapped so far, however, estimates put the
On 24-10-2020 22:27, Allroads wrote:> Use area:highway for polygon and
parking!
I will clarify the relation of our proposal to area:highway, thanks for
pointing it out.
In brief, the two tagging methods coexist and complement each other. Our
proposal focuses on the parking-amenity (and thus ameni
On 24-10-2020 23:54, Paul Allen wrote:
> So tagging for the renderer because, in your opinion, these car parking
> areas are unimportant.
By that line of reasoning tagging highways anything other than
highway=motorway is tagging for the renderer.
I understand your concern, but no, it is not our o
16 matches
Mail list logo
