Re: [Tagging] Feature Proposal - RFC - (consulate)

On 31/10/18 12:33, Allan Mustard wrote: Some responses to Warin: On 10/31/2018 3:45 AM, Warin wrote: Errr. By combining Embassy with High Commission there is a decrease in information. No information is lost. "High Commission" is an embassy by another name, between Commonwealth members. 

Re: [Tagging] Feature Proposal - RFC - (consulate)

On 10/31/2018 3:11 AM, Joseph Eisenberg wrote: > > If the consensus is that "other" sucks as an option I'm certainly > open to other suggestions, but we need something for diplomatic > missions headed by neither an ambassador/charge d'affaires (i.e., > subject to the VCDR) nor a

Re: [Tagging] Feature Proposal - RFC - (consulate)

Some responses to Warin: On 10/31/2018 3:45 AM, Warin wrote: > Errr. > > By combining Embassy with High Commission there is a decrease in > information. > No information is lost.  "High Commission" is an embassy by another name, between Commonwealth members.  The term "high commission" would be

[Tagging] Public Transport Timetables Proposal RFC

Hello everyone! I recently wrote up a proposal page for public transport schedule data. This information would allow OpenStreetMap to store information about when or how often certain buses or trains arrive at a platform. https://wiki.osm.org/wiki/Proposed_features/Public_transport_schedules

[Tagging] Add telecom=* to Map Feature pages

Hi all, Following the approval of the Telecom local loops proposal, the telecom=* key got 3 new values replacing several building=* and man_made=* very particular values. telecom=* is intended to be one of the keys used to map telecommunication infrastructure.

Re: [Tagging] Feature Proposal - RFC - (consulate)

On 31/10/18 04:46, Allan Mustard wrote: Not really dropping. More like reorganizing. Errr. By combining Embassy with High Commission there is a decrease in information. As someone who has spent hours puzzling over Maperitive's rendering rules, deciding how to build them so that

Re: [Tagging] Feature Proposal - RFC - (consulate)

Re: “To make this work, projects like osm carto would either have to add a column for this key to their dbs” I don’t think this is a big problem. This year we added “advertising” as a top-level key that is rendered for advertising=column. It does make the code a little more complex, but so does

Re: [Tagging] Feature Proposal - RFC - (consulate)

Am Di., 30. Okt. 2018 um 18:48 Uhr schrieb Allan Mustard : > Not really dropping. More like reorganizing. As someone who has spent > hours puzzling over Maperitive's rendering rules, deciding how to build > them so that particular categories of POIs will be rendered in specific > ways, I am

Re: [Tagging] Feature Proposal - RFC - (consulate)

Not really dropping.  More like reorganizing.  As someone who has spent hours puzzling over Maperitive's rendering rules, deciding how to build them so that particular categories of POIs will be rendered in specific ways, I am quite sensitive to the need for consistency and a finite number of

Re: [Tagging] Area with restaurants, hotels, cinemas - is it landuse=commercial?

> If it’s 40 storeys of apartments above a 3 storey mall, use landuse=retail for the whole mall area, and building=apartment for the residential towers. The whole, larger mall building could probably be building=mall; it sounds like there are several tall but narrow residential towers around or on

Re: [Tagging] Another multipolygon question

On Tue, Oct 30, 2018 at 7:54 AM Dave Swarthout wrote: > Someone added the Arctic National Wildlife Refuge to OSM but did not add a > bunch of inner areas that aren't part of the refuge. I have the inners in a > shapefile that end up in a separate layer when I import them into JOSM. I > would

Re: [Tagging] Another multipolygon question

Kevin, Okay, I see understand the offset now and the reasons for doing it but wow, such attention to detail is unusual in OSM mapping methinks. It was clever indeed. I just began to use QGIS but I'm a complete noobie at it. My only use of it so far has been to select and save into its own folder

Re: [Tagging] Feature Proposal - RFC - (consulate)

The problem I see is that, as I understand it, Allan is proposing to drop some existing diplomatic=* values, such as diplomatic=permanent_mission. And the proposed substitute is to rely on the name=* tag. Martin pointed out a problem where something not an embassy has a name like an embassy. But

Re: [Tagging] Feature Proposal - RFC - (consulate)

On 29/10/18 21:23, Martin Koppenhoefer wrote: sent from a phone On 29. Oct 2018, at 11:18, Martin Koppenhoefer > wrote: At the moment mappers can simply tag by using the name here’s an example for a misleading name tag: