The tag socket::output has been used 5000 times, so I think it's
best to describe existing usage on the wiki. The current usage is to
tag the units, which are almost always kW:
socket:type2:output has been used 3663 times, and the majority (>70%)
are tagged with 22kW, 22 kW, 43kW and 11 kW - they
I got the information about the origin of the dispute about
highway=bus_stop next to or on the way from this page:
https://wiki.openstreetmap.org/wiki/Talk:Tag:highway%3Dbus_stop#Contradictions_in_the_wiki
"In the early days of OSM, the bus stops were mapped beside the street
simply because the p
transit forum the PT schema has become so convoluted even
> those who helped create it are baffled. At least one is advocating its
> removal.
>
> It's time for the PT schema to be redacted.
>
> DaveF
>
>
>
> On 29/07/2019 15:29, Joseph Eisenberg wrote:
>> I
-1 to a site relation for an area with a defined outer boundary.
Relation = boundary (and =multipolygon) works fine for defining an area,
and you can make holes to exclude at my “outparcels” or villages which are
not part of the official protected area.
Mappers don’t need to add things to relatio
Ok, it's clear that these tags are not deprecated.
Are they "in use" then?
According to https://taghistory.raifer.tech they've both increased in
number by about 3500 features in the past 12 months. In comparison,
disused:shop=* has been added about 3000 times in the same time
period.
On 7/29/19,
I read up on the rather exhausting history of public transport tagging.
The strange thing is that the approved proposal which introduced
public_transport=* and the current public_transport pages suggest
using bus=yes only for public_transport=stop_position. In contrast,
public_transport=platform d
https://wiki.openstreetmap.org/wiki/Tag:abandoned=yes
On Mon, Jul 29, 2019 at 9:07 PM Paul Allen wrote:
>
> On Mon, 29 Jul 2019 at 07:24, Joseph Eisenberg
> wrote:
>>
>>
>> I see that there was just a mention added that landuse=quarry plus
>> disused=yes might be more sensible
>> By the way, it seems the wiki does not show "statuses" correctly for
>> historic page revisions: it shows a status (the current one?) where there is
>> none set in the template, and it shows statuses that haven't been in
>> existence when the revision was published.
>
>
This might be related
I agree; I spent a few minutes trying to improve the page a bit.
However, I don't see much benefit from mapping private household
satellite antennas: the dishes in the linked picture above are only 90
cm across, and they are on just about every house.
Maybe there are more useful things to map in
In Italy, are all of the trees with designation=natural_monument the
officially protected ones, or are there others that are old or historic but
not official?
On Mon, Jul 29, 2019 at 6:29 PM Martin Koppenhoefer
wrote:
> Am Mo., 29. Juli 2019 um 11:11 Uhr schrieb Joseph Eisenb
gt;
>> On 29. Jul 2019, at 08:13, Joseph Eisenberg
>> wrote:
>>
>> Someone needs to check how denotation=cluster is
>> actually used now days.
>
>
> this tag was introduced through an automated edit many years ago with the
> reasoning that natural=tree shoul
I was going to fix the status of abandoned=yes which is currently
incorrectly listed as "obsolete". I thought it was probably
deprecated, since the wiki page was deleted when Key:abandoned:*
(namespaced) was made in 2015, but it's still used 40,000 times.
The key disused (mainly disused=yes) is al
I looked into this myself, back when I noticed that some large dishes
were mistagged as radio telescopes.
For huge communications dishes, there is tower:construction=dish to be
used with man_made=tower and we even have a satellite-dish style
rendering for this at Openstreetmap-carto, for some reas
needs to check how denotation=cluster is
actually used now days.
Joseph
On 7/29/19, Warin <61sundow...@gmail.com> wrote:
> On 29/07/19 15:26, Joseph Eisenberg wrote:
>> I've edited the page:
>>
>> 1) I reworded some of the helpful changes that Mateusz Konieczny
I've edited the page:
1) I reworded some of the helpful changes that Mateusz Konieczny just
made, for better English style.
2) I've removed the implication that de facto / approved are
"recommended" and that "deprecated" / "discardable" etc. are "not
recommended".
I also removed the suggestion t
“how can a protected_AREA be anything but an area?”
Right. Please don’t add area=yes to these features.
This tag is only needed for features that can be either a linear feature OR
an area, for example barrier=hedge.
(Mapping large protected areas mapped as closed ways to relations of
type=bounda
at meet all 4 criteria are probably as good as the average "Approved" tag
- Joseph
On 7/28/19, Christoph Hormann wrote:
> On Sunday 28 July 2019, Joseph Eisenberg wrote:
>>
>> Christoph, do you have any ideas about how we could be more inclusive
>> and make it easier
While admin_level is numeric, they numbers are already widely known,
so it would be fine to reuse the tag admin_level=4 to specify the
administrative level of a certain protected area, I think, especially
if the operator=* is not the same.
> 'strict_nature_reserve', 'wilderness_area',
'national_pa
I think Christoph brings up a very good point.
If I understand correctly, he wasn't accusing the new page of saying
"this is the right way to use statuses", since it just describes and
explains how the current "status" feature is currently used.
But rather, he was saying that by just describing t
Correction: obsolete is only used 6 times with tags and 0 keys at the
moment, but "discardable" is also used with 7 keys in addition to 1
tag, so that's 8 times.
The "discardable" status is clearly different from "deprecated" as you
mentioned.
>> Perhaps there should be a wiki page created that d
orted
since the proposal was just approved.
Perhaps there should be a wiki page created that described the process
for deprecating a tag and when to change the status?
Joseph
On 7/28/19, Martin Koppenhoefer wrote:
>> On 27. Jul 2019, at 16:19, Joseph Eisenberg
>> wrote:
>> Please tak
I didn’t realize that all of the protect_class>6 values were invented for
osm. In that case, I see no reason to use any values for protect_class
above 7.
None of the higher values is used very frequently, and it’s impossible for
me to remember which each one means, especially the values from 21 to
12:10 AM Joseph Eisenberg
> wrote:
> > For your New York State park examples, protect_class=21 might be the
> best option, so go ahead and add this tagging, in addition to tagging any
> specific areas within that qualify as a leisure=park or nature_reserve
> >
> > But many
Please take a minute to review the new page
https://wiki.openstreetmap.org/wiki/Approval_status
I've made this page, based on the existing list of definitions for the
values of the "status" field in the ValueDescription and
KeyDescription boxes - that's the word "approved", "rejected", "de
facto",
It's fine that some training and knowledge is required to properly tag
features in OSM. For example, it takes some experience or wiki
research to learn the difference between natural=heath (dwarf shrubs)
and natural=scrub (shurbland), or wetland=bog and wetland=marsh.
However, a mapper who visits
Well a parking garage may not really be "indoor", but it's certainly
"inside of a building" according to the database model, since the
garage will be mapped as a building=*
So what's important is how we may the lack of walls.
I agree with the earlier suggestion by Tobias to add wall=no for
clarit
The feature man_made=offshore_platform was created as a wiki page and
then added to Map features, apparently without discussion, at some
point in the past.
It didn't have a very complete wiki page, but it looks like this is
mainly meant for offshore oil and gas drilling/production platforms -
I've
Would you suggest removing both man_made=snow_net and
man_made=snow_fence from the curated list in Map Features?
Joseph
On Fri, Jul 26, 2019 at 9:39 PM Martin Koppenhoefer
wrote:
>
> I agree that these are likely always barriers and would be more consistently
> tagged under the "barrier" key. A
Two tags were added to the Map Features page a while back, but don't
appear to have been discussed in a proposal.
man_made=snow_fence is used for fences that help prevent avalanches in
steep slopes with heavy snowfall. This tag has been used almost 3000
timeshttps://wiki.openstreetmap.org/wiki/Tag
MRI at least
>> instead
>>
>> All the best
>>
>> François
>>
>> Le jeu. 11 juil. 2019 à 21:10, Mark Herringer a
>> écrit :
>>
>>> The intention of the tag is to specify physical equipment
>>> (health_amenity:type=MRI)
A natural=volcano is suppose to be a volcanic vent, usually found at the
center of a crater.
While it’s common to misuse this tag to mark the highest peak of a mountain
of volcanic origin, it would be best to use it for the actual center of the
volcanic vent, and use natural=peak for the high poin
The voting period has ended for
Proposed_features/Tag:waterway=tidal_channel with 17 votes to approve
and none in opposition.
The wiki page for the approved feature is located at
Tag:waterway=tidal_channel:
https://wiki.openstreetmap.org/wiki/Tag:waterway%3Dtidal_channel and
I've added the tag to
Kevin,
For your New York State park examples, protect_class=21 might be the best
option, so go ahead and add this tagging, in addition to tagging any
specific areas within that qualify as a leisure=park or nature_reserve
But many State parks on the West Coast are similar to national parks, eg
man
Since there are check cashing shops (usually they also offer payday loans),
amenity=check_cashing_machine would be more specific, for tagging a node
with the precise location of the machine
But if this tag will be added to another feature, like a shop=supermarket,
a tag with the structure check_ca
I don’t usually map such small features; there are so many villages, roads
and rivers still missing from Indonesia.
But I wonder is leisure=garden is appropriate for “shrubbery” features,
since it is also used for front yards and back yards of private homes,
according to a recent thread? This woul
e of 2 weeks.
>
>
> On 21/07/19 10:39, Joseph Eisenberg wrote:
> > Tomorrow 22-July-2019 is the last day to vote on waterway=tidal_channel
> >
> >
> https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:waterway%3Dtidal_channel#Voting
> >
> > On 7/18/19, Joseph
Tomorrow 22-July-2019 is the last day to vote on waterway=tidal_channel
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:waterway%3Dtidal_channel#Voting
On 7/18/19, Joseph Eisenberg wrote:
> 14 people have voted so far on waterway=tidal_channel - all in favor
>
> Voting contin
14 people have voted so far on waterway=tidal_channel - all in favor
Voting continues until the 22nd of July, 2019
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:waterway%3Dtidal_channel#Voting
On 7/10/19, Joseph Eisenberg wrote:
> On Mon, Jul 8, 2019 at 1:31 PM Joseph Eisenb
It looks like the main effect of this proposal would be to replace
pipeline=marker (used 29k times) with marker=pipeline, though the new key
marker= could also be used for power cables and telecommunications cables.
Is it really necessary to change pipeline=marker?
-Joseph
On Sun, Jul 14, 2019 a
5 approval votes so far, none in opposition yet. I will be off the grid for
the next week, but keep voting and I’ll respond to any comments next
Thursday.
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:waterway%3Dtidal_channel#Voting
On Mon, Jul 8, 2019 at 1:31 PM Joseph Eisenberg
Brad, re:
https://www.dropbox.com/s/agj4njek1r35vnz/2018-10-03-13.06.54r.jpg?dl=0
This shows a track that cuts across a scree slope or alluvial fan of small
boulders, cobbled and sand which appears to be eroded from the ridge above,
in a mostly dry climate.
It’s quite bumpy so a low-clearance sed
Voting is now open for the proposed feature waterway=tidal_channel
"A natural intertidal waterway in mangroves, salt marshes and tidal
flats with water flow in the direction of the tide"
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:waterway=tidal_channel
Please read the page, then a
eserve an amenity key.
I'm willing to write up a proposal.
Joseph
On 7/7/19, Minh Nguyen wrote:
> On 2019-07-06 14:20, marc marc wrote:
>> Le 06.07.19 à 15:17, Joseph Eisenberg a écrit :
>>> provide after-school additional instruction
>>
>> why it isn't st
No.
While tracktype= has some issues, smoothness= is more subjective and less
generally useful.
Surface= is very helpful and more objective, so it should be mentioned,but
I believe it is already suggested on most of the minor highway, path and
track pages.
On Mon, Jul 8, 2019 at 10:24 AM brad w
> status=de facto means it was in use before the tagging list made up the
> approval process, and is generally accepted?
The "De facto" is not only used for tags that were created before the
approval process started. A number of more recent tags (post-2008)
have status "de facto" and are listed on
ained very often, if at all, erosion creates
> hazards in the road also requiring 4wd or at least a very high clearance
> vehicle.
>
> *"Tracktype* is a measure of how well-maintained a track or other minor
> road is..."
>
>
> On 7/6/19 6:21 PM, Joseph Eisenberg wrot
From the talk page:
>I propose to tackle the varying quality of this page in different languages by
>changing Map
>Features to a single multilingual page that outputs its text in the user’s
>preferred interface
>language.
>The tag tables can be generated from Taginfo/Taglists. For the best resu
I would think that an unimproved track across naturally solid rock or
naturally well-compacted gravel would not be tracktype=grade5 - while it
might be bumpy, it’s probably passable by any vehicke with sufficient
clearance and tire size, even when wet, unlike a track of unimproved clay,
silt or loa
ersal of water flow direction.
The wiki page for waterway=tidal_channel should mention that
"tidal=yes" is implied.
-Joseph
> Other channels will have a lower level but won't be empty.
>
> Let me know how do you feel about this
>
> All the best
>
> François
>
&g
> ... we could use something like building=boat,
> building=caravan or building=vehicle, but it is unfortunate that none
> of these can be understood to be buildings in any sense of the word.
building=static_caravan is common for mobile homes and caravans (aka
trailers) which are semi-permanently
cilities that only provide preparation for certain tests, like
Kaplan in the USA.
Joseph
On 7/5/19, Jmapb via Tagging wrote:
> On 7/5/2019 2:16 AM, Joseph Eisenberg wrote:
>> So, what's a better term for a test prep centre, cramp school, or
>> tutoring office? There the rarely
Re: > basic picnic tables where you can provide your own mini grill
It looks like we can propose "bring_own_bbq=yes" for that situation
Re: > some fixed on a post grills
Do you think this should be "bbq=yes" or "barbecue_grill=yes"?
-Joseph
On 7/6/19, Nita S. wrote:
> One caravan park I am fa
I'd like to vote on the proposal for waterway=tidal_channel soon
If you haven't read the page yet, please check and add any comments
or bring up any problems that might have been missed.
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:waterway%3Dtidal_channel
"Definition:A natural
It’s fine to make up new values in the “shop” key, so “shop=christmas”
would work: already used 14 times.
I think party shops are different.
On Sat, Jul 6, 2019 at 3:51 PM Graeme Fitzpatrick
wrote:
> Just mapping a Christmas shop https://christmasshack.com.au/, which, as
> the name suggests!,
>> *"For example, use the feature leisure=picnic_site with the property
>> tag drinking_water=yes, instead of using the separate feature tag
>> amenity=drinking_water on the same node or area."
>>
>> This example is a bad idea and mappers shouldn't be encouraged to do
>> so. amenity=drinking_water
to specify the presence of a grill that can be
used for bbq / grilling?
On 7/6/19, Warin <61sundow...@gmail.com> wrote:
> On 06/07/19 02:28, Jmapb via Tagging wrote:
>> On 7/5/2019 10:56 AM, Joseph Eisenberg wrote:
>>> I don't think it would be necessary to combine &q
I don't think it would be necessary to combine "bbq=no" and
"bring_own_bbq=yes" - if a feature such as a leisure=picnic_site is
tagged "bring_own_bbq=yes" that is sufficient. The tag "bbq=no", like
most tags with value "no", can be omitted.
There might be times when there is "bbq=yes" and "bring_o
I believe smoothness=* is very important in dry areas, including most
of the western USA in summertime (when most people visit remote areas
on track roads).
But a road that is very smooth, dry clay in summer, for example an
unimproved track across a dry lakebed, will become impassible mud
after a
I followed a link from amenity=school to amenity=prep_school, which
was only as stub with the text "Tutorial schools" and
description="Tutor school".
Taghistory shows it has been used since 2012, slowly increasing to a
few hundred uses since 2018, but had no wiki page still March 2019.
However, I
the best practice, because of this ambiguity. Users should not be
encouraged to delete all single node objects within buildings without
carefully considering each of the tags.
Joseph
On 7/5/19, Joseph Eisenberg wrote:
> I agree that this page could be improved. Until now it hasn't
I agree that this page could be improved. Until now it hasn't
mentioned the problems with tagging multiple features on one database
object.
This can be difficult for database users, for example this comment at
the Openstreetmap-carto github page:
https://github.com/gravitystorm/openstreetmap-carto
be useful even with
tourism=camp_pitch.
Joseph
On 7/4/19, Warin <61sundow...@gmail.com> wrote:
> On 04/07/19 11:47, Graeme Fitzpatrick wrote:
>>
>>
>> On Wed, 3 Jul 2019 at 10:06, Joseph Eisenberg
>> mailto:joseph.eisenb...@gmail.com>> wrote:
>>
>&
> poorly tagged "maxtents=yes". Did you check if that came from a weird
> > import?
> >
> > tom
> >
> >
> > On 03.07.2019 02:05, Joseph Eisenberg wrote:
> >> Some users specify the number of tents or caravans allowed at a
> >> ca
The user (Hjart) who created the wiki page for booking=* says they are
fine with deprecating it and using reservation=* instead
See:
https://wiki.openstreetmap.org/wiki/Talk:Key:booking
Joseph
On 7/3/19, Graeme Fitzpatrick wrote:
> On Tue, 2 Jul 2019 at 21:37, Joseph Eisenberg
>
Some users specify the number of tents or caravans allowed at a
campsite or camp pitch with tents= and caravans=, but
more frequently these are specified with capacity:caravans=,
capacity:tents= or maxtents=
Currently maxtents=* is used most frequently and it's the shortest
key, but there is no eq
There are two similar property tags that describe the presence of a
barbecue (BBQ) grill at another feature such as a campsite or picnic
site.
https://wiki.openstreetmap.org/wiki/Key:bbq
https://wiki.openstreetmap.org/wiki/Key:barbecue_grill
If you check taghistory.raifer.tech it's clear that
ba
While making the new page for tourism=camp_pitch, I noticed that
"booking=*" is recommended to be used with tourism=camp_site, but the
similar tag "reservation=*" has been used for many more years and
several times more frequently. Both are not very common yet.
https://wiki.openstreetmap.org/wiki/
> Yes capacity= would work. Guess that one is an either / or.
There is also capacity:cabins=, capacity:tents=, capacity=caravans -
and maxtents=* but that doesn't fit the pattern and seems to have been
mainly used for imports of backcountry campsites with maxtents=yes?!
> fireplace=yes - if there
> cabins Whether cabins are offered
>>
>
> I have only ever seen 1 cabin per site, but it would be helpful, especially
> for families, to also list number of beds per each cabin (cabin=yes +
> beds=2/4/8).
The tag capacity= can be used for the total number of visitors allowed
too, but ye
ain
for this pitch."
This seems less useful, but perhaps this is for RV/caravans, which I
don't use. The simple tag "drain=yes/no" could be confused with uses
to describe the type of waterway=drain, so I'm not sure what's best
for this.
Joseph
On 6/30/19, War
re as a
wood fire on the ground, not charcoal in a portable grill.
However, the key "openfire=" has never been extensively discussed, so
it may be ambiguous in actual use.
On 6/30/19, Graeme Fitzpatrick wrote:
> On Sun, 30 Jun 2019 at 00:45, Joseph Eisenberg
> wrote:
>
>
A couple of users added two new sections to the Good Practice page recently:
https://wiki.openstreetmap.org/wiki/Good_practice
I think these need discussion.
1) "Check the history of important objects"
"Before making significant changes to important objects (in particular
settlements, administr
The tag tourism=camp_pitch was approved with 24 yes votes and 1 no vote.
The wiki page has been updated at
https://wiki.openstreetmap.org/wiki/Tag:tourism=camp_pitch
I've listed camp_site=camp_pitch as deprecated, and added
tourism=camp_pitch to Map features.
It looks like the French page has al
On 6/24/19, yo paseopor wrote:
> BOE-020_Codigo_de_Trafico_y_Seguridad_Vial
> Page 50
> Carril. Banda longitudinal en que puede estar subdividida la calzada,
> delimitada o no por marcas viales longitudinales, siempre que tenga una
> anchura suficiente para permitir la circulación de una fila de
quot; has been used 122 times and
"healthcare=midwife" 427 times.
The one issue would be health posts that have no trained nurse or
midwife, but only a minimally-trained "community health worker", eg
"kader kesehatan" in Indonesian - this situation is common in very
remote
I agree that amenity=power_supply is useful for features that provide
free or paid access to an electrical outlet.
Another place where this would be useful is in airports and train
stations, where the waiting areas often have specific locations to
charge electronic devices.
There might be some co
<61sundow...@gmail.com> wrote:
> I would think that the bed count would be a reasonable guide for the
> staffing levels.
>
> Certainly for emergency use the number of bed would be usefull and this
> should be something that can be reasonably verified.
>
>
>
>
> O
Voting for tourism=camp_pitch has been open for 1 week, and there are
now 16 votes in favor and 1 vote in opposition. Voting will continue
for another week until 2019-6-28 as scheduled.
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:tourism%3Dcamp_pitch
On 6/14/19, Joseph Eisenberg
ith a list of 100 different insurance company and plan
combinations? This would be hard to manage and maintain by most
openstreetmap mappers.
-Joseph Eisenberg M.D.
On 6/20/19, Mhairi O'Hara wrote:
> Hello Tagging Mailing List,
>
> We would like to bring your attention and comments
4) health_amenity:type
I think the key "healthcare" should be used instead of the new key
health_amenity:type". If it's necessary to tag an MRI facility
separately, then create a tag like "healthcare=mri".
However, it may be more useful to use a tag like "mri=yes" on the
main amenity=hospital or
h of these categories is to be included in the number of nurses?
-Joseph Eisenberg M.D.
On 6/20/19, Mhairi O'Hara wrote:
> Hello Tagging Mailing List,
>
> We would like to bring your attention and comments on the proposal for the
> staff_count:doctors and staff_count:nurses tag
/wiki/Verifiability - approved tags
should be things that an ordinary mapper can confirm to be true or
false.
- Joseph Eisenberg, M.D.
On 6/20/19, Mhairi O'Hara wrote:
> Hello Tagging Mailing List,
>
> We would like to bring your attention and comments on the proposal for the
> s
I agree that this discussion should be in 5 different threads, one for
each tag, so I will respond in that way, and on the individual pages.
In general, I appreciate the work that you are doing on this, but I
don't think you should rely too much on the abandoned healthcare 2.0
proposal - it wasn't
I asked my wife (native American English speaker) how she would
describe a ferry that wasn't free. She thought of paying a fare first,
for foot ferries, but when pressed suggested that "Toll ferry" was
better than something with "fee"
Searching online, I'm finding results for both "toll ferry" and
Daniel, I find this whole conversation pretty off-topic for the
tagging forum. Perhaps "Talk" would be more appropriate, since you
closed the original discussion on github.
1)Simplification of geometries:
> There can be some simplification used (just beware of oversimplification,
> especially fo
Good suggestion. I've updated the page.
On 6/17/19, Graeme Fitzpatrick wrote:
> On Sun, 16 Jun 2019 at 16:39, Joseph Eisenberg
> wrote:
>
>>
>> Does this clearly define the difference between a tidal channel and a
>> river or stream?
>>
>
> Yep, I
this clearly define the difference between a tidal channel and a
river or stream?
Please comment on the waterway=tidal_channel proposal or here:
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:waterway%3Dtidal_channel
I've added more photos and examples there too.
On 6/6/19
I think "bring_own_bbq=yes" is sensible; "bbq=designated" is a little
confusing, but probably also correct.
The tag leisure=firepit is for a structure or spot designated for open
fires, such as a fire ring made of stones or bricks, or a metal fire
pit.
I checked the page for amenity=bbq and notic
The page https://wiki.openstreetmap.org/wiki/Key:manhole implies that
manhole=drain is for manholes that provide access to an underground
"surface water drain for removing rainwater", so they should not be
the opening or grate for water.
However, I don't know if this is how the tag is actually use
Some people disapprove of editing a database object without checking
if it still exists, because an edit implies that you have confirmed
that the information about the feature is still correct.
Back to the original question: should diplomatic=honorary_consulate
and the related tags be marked as de
This requirement is fine for Europe, but the presence of lane markings
is not reliable in all of the world.
In developing countries, such as here in Indonesia, the presence of
painted lane markings is inconsistent. Often cheap pain is used
instead of more durable thermoplastic, so the markings onl
The proposal for the feature tag tourism=camp_pitch is now open for voting.
This is a follow-up to the rejected proposal for camp_site=camp_pitch
The proposed tag tourism=camp_pitch provides a way to tag individual
pitches within a campsite (a.k.a. "campground" in American English) or
caravan sit
Right.
By "deprecated" this is what I mean: should the wiki pages be changed
to make it clear that diplomatic=honorary_consulate is no longer
preferred, and could be changed to diplomatic=consulate +
consulate=honorary_consulate ?
On 6/14/19, Lionel Giard wrote:
> I think that the only deprecate
I was checking the pages related to the office=diplomatic proposal,
which approved the tags diplomatic=embassy, diplomatic=consulate and
diplomatic=liaison - I just made pages for these 3 tags and added
=liaison to the key:diplomatic page.
Based on the proposal, I suspect that the other values cou
I understand why refugee camps have been mapped with
amenity=social_facility - it's the closest existing tag, since
tourism=camp_site is clearly wrong and landuse=residential isn't quite
right.
However, I don't think that large refugee camps are a perfect fit for
amenity=social_facility.
Most of
> The OSMwiki says tourism=caravan_site is not for sites that accept tents
> at all.
I think you are mistaken. The wiki page says "They may also have some
space for tents. If a site is primarily for tents, it should be tagged
as tourism=camp_site". This has always been a part of the page, since
20
> How do you handle sites that accept both caravans and tents on different
> pitches?
>
I believe you may be thinking about how to choose between tourism=camp_site
vs tourism=caravan_site for a dual-use campground or campsite. I would use
camp_site if it is mostly used for tent camping and caravan
> what about pedestrians, can they walk on cart paths? And other vehicles,
> e.g. lawnmowers or tractors?
> Shouldn’t these get a highway tag?
Yes, they should get a highway tag, in my opinion.
The current proposal requires the use of highway=* with golf=cartpath.
Either "highway=service" or "hi
> if I want all the path in a park, I create a propal with park=path ?
> then forest=path ? and so on with all "this object is inside this one"
That's a theoretical risk and I wouldn't support adding any such tags,
but in this case there is already a well-used key "golf=*" for golf
course features
Any additional comments on golf=cartpath?
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:golf%3Dcartpath
On 5/27/19, Joseph Eisenberg wrote:
> I've created a complete proposal page for golf=cartpath:
> https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:golf%3Dcartpa
601 - 700 of 1105 matches
Mail list logo
