Re: [OSM-talk] Tagging POI's - Nodes vs. areas

2015-04-21 Thread Jan van Bekkum
If you use a relation shouldn't it be a site relation instead of a
multipolygon?

On Tue, Apr 21, 2015 at 4:24 PM Bryan Housel br...@7thposition.com wrote:

 `amenity=hospital` is what makes it a proper hospital.  You can create a
 node where the hospital is, or an area around the property of the
 hospital.  Drawing either a node or an area is ok, but drawing areas is
 preferred if you have time for it.

 If the hospital is just one building, you can add `building=yes` or
 `building=hospital` to the amenity.   If the hospital is a campus of
 several buildings, you can draw each building as well.  `building=*`
 (anything) should make it render like a building/structure.   The actual
 value of the building tag is not really used often (it’s considered a
 description of what the building looks like, not what it is), so most
 buildings are just tagged as `building=yes` unless they are really special
 somehow.

 Thanks, Bryan




 On Apr 21, 2015, at 9:58 AM, EthnicFood IsGreat 
 ethnicfoodisgr...@gmail.com wrote:

 I want to know how to tag buildings which are also amenities or shops.  I
 have consulted the wiki and I cannot find a clear explanation of this.  Say
 you have a building which is a hospital.  One way to tag the polygon would
 be building = hospital.  Another way would be amenity = hospital.
 Another way would be to simply tag the building as building = yes and
 then place a node inside the building polygon and tag the node as amenity
 = hospital.  I'm thinking in terms of how the hospital will show up in the
 various renderers.  Do most renderers require the amenity tag in order to
 display a hospital symbol at that location?  (In other words, what happens
 if I just use the building = hospital tag on the polygon and no amenity
 tag?)  And what about the hospital name?  Do I include it with the building
 polygon or the node?  Or both?  This is very confusing.  It seems there is
 a certain amount of overlap when it comes to the application of building,
 amenity, and shop tags.

 Mark Bradley
 ___
 talk mailing list
 talk@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk


 ___
 talk mailing list
 talk@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Voting on voting system for proposals

2015-03-19 Thread Jan van Bekkum
I would assume that in this phase of the OSM lifecycle most new tags would
start in specialist renders. For example I expect that the current
discussion about campgrounds camp_site=* leading to different types of
campgrounds would be rendered in specialist renders for camping first and
would be rendered to more general maps once they gain momentum.

This makes it important that renderers can show raw attribute tags of
namespace tags they show. In this way I can see if more information is
hidden behind the symbol shown.

On Thu, Mar 19, 2015 at 7:20 AM Paul Norman penor...@mac.com wrote:

 On 3/18/2015 2:43 PM, Clifford Snow wrote:
  Since you are involved with updating the rendering, can you tell us
  the process to decide what should be rendered? I realize that part of
  it must be stylistic, but what outside influences cause you to include
  a tag as part of the standard rendered OSM tile?
 I should preface this by stating that these are my opinions, and I know
 other OpenStreetMap Carto maintainers look at it differently. They are
 also not the opinion of my employer, MapQuest, and the MapQuest Open
 style has different cartographic goals.

 There are no policies on what is rendered, and types of features are
 decided on a case by case basis.

 Normally the process of deciding to render a feature and deciding to
 render a particular tag are separate. You might decide you want to
 render bus stops, but also find that in the region you're rendering
 there is a GTFS feed with better data. In OpenStreetMap Carto, these two
 steps are more entwined. We're aiming at mappers and want to avoid
 additional sources of non-OSM data.

 A first consideration is technical. Some of the crazy relation types out
 there are not designed in a way that they can be reasonably rendered
 with a standard toolchain. If I can't figure out how to write the SQL to
 be able to get a data layer suitable for rendering, it almost certainly
 won't be rendered.

 I'm only interested in rendering established tags. The primary indicator
 of this is usage. There are some exceptions to this like national
 capitals, where there are only many of them. My view is that a tag
 should be able to obtain reasonable usage numbers on its own merits
 without being rendered. I also look beyond taginfo numbers to see if
 they are being skewed by a small number of contributors, mechanical
 edits, or a bulk import.

 We don't want to encourage difficult to consume tagging approach. This
 is why we will not use disused=yes. (#111)

 The wiki is a source I use, but just one among many.

 A good read is Andy's comment about changing tags:
 https://github.com/gravitystorm/openstreetmap-
 carto/issues/230#issuecomment-29238913.
 It is related.

 And of course, all of this is done in a limited amount of available
 time. If I decide to work on something with the style it means I'm not
 working on a different part of it. It's zero sum for me, and I always
 have more I can work on. Rendering new types of features is about bottom
 of the priority list for me right now.

  Would you render a tag without a wiki entry, or with just a proposal?
 In principle, if it were an established tag? Yes. It's very unlikely an
 established tag would not have a wiki page.
  How does the fact that it may be useful to specific groups, ie,
  cyclists which has its own style impact your decisions?
 I don't particularly consider the presence of specialist styles. There
 are styles for most topical interests these days.

 ___
 talk mailing list
 talk@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] TagFinder - a full text search engine for OSM tags (prototype)

2015-01-18 Thread Jan van Bekkum
Hi Stefan,

Looks good!

Can I direct questions or remarks to you?

Regards,

Jan van Bekkum

On Sun Jan 18 2015 at 8:53:19 PM Stefan Keller sfkel...@gmail.com wrote:

 It's a pleasure to release a new webapp called TagFinder. TagFinder is
 a full text search engine for OpenStreetMap tags. It uses the
 unequaled Taginfo, translation services (german to english), thesaurs
 and an adapted domain-specific semantic net.

 There's a demo prototype (in english and german) including an API
 running on Heroku:  http://tagfinder.herokuapp.com/ .

 TagFinder was developed during a semester thesis in informatics at the
 Geometa Lab (Prof. Keller) at University for Applied Sciences
 Rapperswil (Switzerland). The application is written in Python 2.7 and
 uses the Flask web framework. The source code is on Github
 (https://github.com/geometalab/OSMTagFinder ).

 Feel free to test it and give feedback e.g. here, on Twitter
 @geometalab, as a Github issue or to me directly.

 -S.

 [1] http://tagfinder.herokuapp.com/
 [2] https://github.com/geometalab/OSMTagFinder
 [3] https://twitter.com/geometalab

 ___
 talk mailing list
 talk@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk-nl] Talk-nl Digest, Vol 94, Issue 23

2014-12-30 Thread Jan van Bekkum
Beste Marc,

Bedankt voor het antwoord. Ik gebruik nu inderdaad keys uit het
extensievoorstel. Ik had alleen de hoop/illusie dat goedgekeurde keys meer
kans hebben om in renderers zoals OsmAnd terecht te komen en ik wil
vermijden om eigen uitvindingen te gaan doen.

Groeten,

Jan

On Tue Dec 30 2014 at 1:02:18 PM talk-nl-requ...@openstreetmap.org wrote:

 Send Talk-nl mailing list submissions to
 talk-nl@openstreetmap.org

 To subscribe or unsubscribe via the World Wide Web, visit
 https://lists.openstreetmap.org/listinfo/talk-nl
 or, via email, send a message with subject or body 'help' to
 talk-nl-requ...@openstreetmap.org

 You can reach the person managing the list at
 talk-nl-ow...@openstreetmap.org

 When replying, please edit your Subject line so it is more specific
 than Re: Contents of Talk-nl digest...


 Today's Topics:

1. Re:  Voting (Marc Gemis)


 --

 Message: 1
 Date: Mon, 29 Dec 2014 13:32:44 +0100
 From: Marc Gemis marc.ge...@gmail.com
 To: OpenStreetMap NL discussion list talk-nl@openstreetmap.org
 Subject: Re: [OSM-talk-nl] Voting
 Message-ID:
 CAJKJX-RdW7sN6r+dMY-VhEhoVUEgEeMgPcJNt==Q0vhb2Wn+
 f...@mail.gmail.com
 Content-Type: text/plain; charset=utf-8

 Het voorstel wordt gewoonlijk door de indiener ter stemming gebracht. Bv.
 de street_cabinet proposal werd na ongeveer een half jaar ter stemming
 voorgelegd. Het voorstel werd eerst neergeschreven en ter discussie
 voorgesteld aan de tagging mailing list.

 Soms verliest de indiener interesse, of is er gewoon geen interesse van de
 community.
 Verder is iedereen vrij om te stemmen, je hebt enkel een account op de wiki
 nodig.

 Wil dit zeggen dat je tag niet kan gebruiken ? Neen, als jij de zinvol vind
 kan je ze gebruiken. Kijk bijvoorbeeld naar de heritage tags. Al jaren in
 proposal fase, maar al duizende keren gebruikt.

 Vandaar dat er mensen zijn die heel dat stemproces maar niks vinden (veel
 te weinig stemmen nodig). Zij gaan ervan uit dan nuttige tag wel vanzelf
 gebruikt worden, en kijken liever naar taginfo.openstreetmap.org om de
 bruikbare tags te vinden.

 mvg

 m

 2014-12-29 11:30 GMT+01:00 Jan van Bekkum jan.vanbek...@gmail.com:

  Goedemorgen,
 
  Ik heb een vraag over het stemproces. De procedure heb ik in de wiki
  gevonden, maar mij is daaruit niet duidelijk geworden wanneer een
 voorstel
  voor stemming wordt ingediend en wie stemt. Bijvoorbeeld Extend camp_site
  staat al bijna vijf jaar in RFC met eigenaar various terwijl er nog wel
  regelmatig dingen worden toegevoegd.
 
  Als achtergrond: ik ben bezig om OSM-aanvullingen en -correcties
 verzameld
  tijdens een overlandtrip van Nederland naar Zuid Afrika (
  www.DeEinderVoorbij.nl) te verwerken.
 
  Groeten,
 
  Jan van Bekkum
 
  ___
  Talk-nl mailing list
  Talk-nl@openstreetmap.org
  https://lists.openstreetmap.org/listinfo/talk-nl
 
 
 -- next part --
 An HTML attachment was scrubbed...
 URL: http://lists.openstreetmap.org/pipermail/talk-nl/
 attachments/20141229/b86596b0/attachment-0001.html

 --

 Subject: Digest Footer

 ___
 Talk-nl mailing list
 Talk-nl@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk-nl


 --

 End of Talk-nl Digest, Vol 94, Issue 23
 ***

___
Talk-nl mailing list
Talk-nl@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-nl


[OSM-talk-nl] Voting

2014-12-29 Thread Jan van Bekkum
Goedemorgen,

Ik heb een vraag over het stemproces. De procedure heb ik in de wiki
gevonden, maar mij is daaruit niet duidelijk geworden wanneer een voorstel
voor stemming wordt ingediend en wie stemt. Bijvoorbeeld Extend camp_site
staat al bijna vijf jaar in RFC met eigenaar various terwijl er nog wel
regelmatig dingen worden toegevoegd.

Als achtergrond: ik ben bezig om OSM-aanvullingen en -correcties verzameld
tijdens een overlandtrip van Nederland naar Zuid Afrika (
www.DeEinderVoorbij.nl) te verwerken.

Groeten,

Jan van Bekkum
___
Talk-nl mailing list
Talk-nl@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-nl