sent from a phone
> On 27. Dec 2018, at 07:45, Michael Patrick wrote:
>
> > Is there an upper cut-off where things stop being a peninsula?
>
> Hmmm ... not really.
is there a difference to a “cape”? What about a promontory? Shall we
distinguish these, and if yes how and according to which
There is a substantial difference between tagging a limited set of
physical properties (and yes clearly some of this could have been done
as a list too) that are known in advance vs. moving an essentially
unbounded list of fantasy names in to key space.
The argument that semi-colons shouldn't be
PS: btw this specific proposal is also "interesting" as it introduces
mixed case keys, which in general have been considered nonos.
Am 27.12.2018 um 11:44 schrieb Simon Poole:
> There is a substantial difference between tagging a limited set of
> physical properties (and yes clearly some of this c
On 26.12.2018 19:05, bkil wrote:> top_up:phone:‹brand›=yes;no
> top_up:transport:‹brand›=yes;no
> top_up:credit_card:‹brand›=yes;no
>
> This is not the same wording as discussed above, but I still like this one.
I'd prefer if the supported brands were part of the value – as most
brand-related str
sent from a phone
On 27. Dec 2018, at 11:44, Simon Poole wrote:
>> much easier to evaluate than one like:
>> some_services=foo;characteristic_I_need_to_know;bar
>
> This is being directly disingenuous, because what is a actually being
> proposed is
>
> characteristic_I_need_to_know:random_st
Am 27.12.2018 um 15:25 schrieb Martin Koppenhoefer:
>
> sent from a phone
>
> On 27. Dec 2018, at 11:44, Simon Poole wrote:
>
>>> much easier to evaluate than one like:
>>> some_services=foo;characteristic_I_need_to_know;bar
>> This is being directly disingenuous, because what is a actually being
Summarizing the problems of the top_up:[:]=yes/no approach:
- Some networks (like PayPoint) allow top-up more than one service (mobile
phone, public transport, ...)
- The scheme has a over-namespacing problem because both the second and the
third subkeys could be values
- The name "top_up" can be c
Am Do., 27. Dez. 2018 um 19:40 Uhr schrieb Daniele Santini <
danysa...@gmail.com>:
> Summarizing the problems of the top_up:[:]=yes/no approach:
> - Some networks (like PayPoint) allow top-up more than one service (mobile
> phone, public transport, ...)
> - The scheme has a over-namespacing proble
> "phone" is better than "prepaid" because prepaid doesn't tell you whether
> this is about phone, public transport, parking, drinks, or whatever.
>
This tag is not only about phones. It includes prepaid public transport
cards, prepaid credit cards, ...
Otherwise the prepaid_top_up= would not be n
On Thu, 27 Dec 2018 at 19:04, Daniele Santini wrote:
> If I understood correctly from the mailing list networks like PayPoint are
> different, they allow you to top up prepaid credit and to pay other things
> (where you put the money in). So I don't think payment:* is correct here.
>
More on the
On Thu, 27 Dec 2018 at 19:05, Martin Koppenhoefer
wrote:
>
> > Is there an upper cut-off where things stop being a peninsula?
>
> Hmmm ... not really.
>
> No indeed! When I did some looking into it, Europe can actually be
considered to be a peninsula off Asia!
> is there a difference to a “cape
Hi
The vote on the pipeline valve proposal has started 11 days ago.
https://wiki.openstreetmap.org/wiki/Proposed_features/Pipeline_valves_proposal
Due to a significant debate started about the opportunity to use or not
namespaces on proposed keys, I plan to extend the voting period until the
15 o
On Mon, 10 Dec 2018 at 12:14, Bryan Housel wrote:
>
> *🍔 Brand Name Suggestions*
> We've released a huge upgrade to the brand name suggestions in iD. Thank
> you to everyone who volunteered to match brand names to their proper
> OpenStreetMap tags. Follow the brand name suggestion project here:
Glad you like it! The brand name list is tracked in this repository:
https://github.com/osmlab/name-suggestion-index
So just open an issue or pull request there if you know of anything to be added!
Thanks, Bryan
> On Dec 27, 2018, at 6:07 PM, Graeme Fitzpatrick wrote:
>
>
>
> On Mon, 10 D
Thanks Bryan
Separate request for each brand, or one for multiples?
& what do you need - just name & what they do / type of store & speciality?
Thanks
Graeme
On Fri, 28 Dec 2018 at 09:16, Bryan Housel wrote:
> Glad you like it! The brand name list is tracked in this repository:
> https://
" I would think all of these should come under natural=x, & should be
mapped as they are named: =headland, =cape, =peninsula, =promontory etc etc
"
+1 That's been my general practice as well. The designations of cape,
point, peninsula, headland, etc., are all arbitrary and come from
historical
Just doing mapping of some more-or-less retail areas after a drive around,
& have some questions as to what we'd call some of the businesses /
establishments
http://p3sportsgoldcoast.com.au/
A specialised sports recovery centre, for football teams & similar
high-level athletes to be treated & rec
17 matches
Mail list logo
