On Sat, 29 Dec 2018 at 12:58, Daniele Santini wrote:
> I updated the proposal page with the new tags:
> https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up
> Check it out.
>
The final image on your proposal, of a PayPoint sign, reminded me of yet
another complication (at
least in the UK
I updated the proposal page with the new tags:
https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up
Check it out.
Kind regards
So, basing on these problems, we could change the proposal to:
> - prepaid_top_up= -> to specify the type of services whose top-ups
> are sold (like mobile_phone
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
> "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
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
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 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
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
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
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
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
"top up" is commonly used in Thailand for adding money to a cell phone
balance. My bank's website, Kasikorn Bank, uses that exact term and offers
a way to "top up" your phone online.
On Thu, Dec 27, 2018 at 7:54 AM Tom Pfeifer wrote:
> On 26.12.2018 19:05, bkil wrote:
> > Please don't confuse to
On 26.12.2018 19:05, bkil wrote:
Please don't confuse top ups with refilling:
https://wiki.openstreetmap.org/wiki/Proposed_features/Refilling_a_purchased_drink
No I don't confuse it. The refilling proposal is about refills without
additional charge.
To top-up a drink is purchasing a new one wi
On Wed, 26 Dec 2018 at 21:48, bkil wrote:
> Yes, it would be more comfortable to tag the PayPoint service itself in a
> certain way instead of all the individual services.
>
> It is also better maintainable, as when a new provider registers with
> PayPoint, we don't need to amend all previously t
Yes, it would be more comfortable to tag the PayPoint service itself in a
certain way instead of all the individual services.
It is also better maintainable, as when a new provider registers with
PayPoint, we don't need to amend all previously tagged places with a mass
import.
>From a perspective
I don't use these systems but would agree with Paul on this, there will be
hundreds of things that can be paid at these terminals.
Beyond what has so far been mentioned you can pay road tolls or buy tickets for
my local bus and probably many other local bus companies. Although I can
imagine so
On Wed, 26 Dec 2018 at 18:07, bkil wrote:
> Please don't confuse top ups with refilling:
>
> https://wiki.openstreetmap.org/wiki/Proposed_features/Refilling_a_purchased_drink
>
> I think "top up" is standard terminology in the UK for increasing the
> balance of prepaid mobile phone accounts.
>
T
Stefan, I think most of us here do not fully understand your hard
arguments, but if you could please elaborate a bit more or give some more
examples, maybe we could better address your concerns. Anyway, this
question sounds a bit orthogonal to the proposal at hand. Could anyone
please link to a pre
Please don't confuse top ups with refilling:
https://wiki.openstreetmap.org/wiki/Proposed_features/Refilling_a_purchased_drink
I think "top up" is standard terminology in the UK for increasing the
balance of prepaid mobile phone accounts.
The author has since updated the wiki page for the proposa
Am Mi., 26. Dez. 2018 um 16:47 Uhr schrieb Martin Koppenhoefer
:
> For practical reason, I would expect a scheme
> characteristic_I_need_to_know=yes/no
>
> much easier to evaluate than one like:
> some_services=foo;characteristic_I_need_to_know;bar
No it's not easier. The following
some_services_f
sent from a phone
> On 26. Dec 2018, at 15:08, Stefan Keller wrote:
>
> Tag-proposals in the form
> :[:]=yes/no should be
> avoided. It's shifting values to attribute names!
it’s not a value, it‘s a property ;-)
it depends on your interpretation, e.g. motorroad=yes
oneway=yes
aren’t these
On Wed, 26 Dec 2018 at 15:10, Stefan Keller wrote:
>
> Tag-proposals in the form
> :[:]=yes/no should be
> avoided. It's shifting values to attribute names!
>
> This detracts processing - given we/OSM already have a non-relational
> key-value schema. Specifically it makes processing with presets a
(I am resending this mail because the first time I forgot to change the
object from "Digest". Sorry for the double mail!)
So what's your suggestion?
top_up:=? _top_up:=yes/no?
_top_up:brand=?
Il giorno mer 26 dic 2018 alle ore 15:09
ha scritto:
> Hi,
>
> Am Mi., 26. Dez. 2018 um 10:13 Uhr schrie
Hi,
Am Mi., 26. Dez. 2018 um 10:13 Uhr schrieb Markus :
> I don't see a problem that would prevent using the proposed tags
> top_up:[:]=yes/no for vending machines, ATMs, convenience
Tag-proposals in the form
:[:]=yes/no should be
avoided. It's shifting values to attribute names!
This detracts p
I find "top_up" alone highly misleading and unspecific.
I encountered the term in filling stations, where you would order either "5 gallons" or "top up",
i.e. to fully fill the tank. Or when pre-paying the fuel, you would either pay "fuel for $20", or
leave your credit card with the cashier to
This seems right. I updated the proposal page, check it out:
https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up
Il giorno mer 26 dic 2018 alle ore 12:42
ha scritto:
> Hi Daniele,
>
> >From the proposal page:
>
> > It's possible to specify which brand/carrier vouchers are sold with the
I support the scheme outline by Markus, please update your proposal. I've
already proposed the exactly same scheme on our local mailing list some
time ago, so it is very intuitive:
top_up:[:]=yes/no
On Wed, Dec 26, 2018 at 12:35 PM Martin Koppenhoefer
wrote:
>
>
> sent from a phone
>
> > On 26.
sent from a phone
> On 26. Dec 2018, at 10:11, Markus wrote:
>
> I don't see a problem that would prevent using the proposed tags
> top_up:[:]=yes/no for vending machines, ATMs, convenience
> stores, kiosks etc. too.
+1, I was proposing on talk-it a very similar
phone_top_up=yes/no
phone_to
I don't see a problem that would prevent using the proposed tags
top_up:[:]=yes/no for vending machines, ATMs, convenience
stores, kiosks etc. too.
On Wed, 26 Dec 2018 at 09:59, Warin <61sundow...@gmail.com> wrote:
>
> There are some vending machines that offer 'top up' ... how are these to be
>
There are some vending machines that offer 'top up' ... how are these to be
tagged? Together with a payment tag too.
There are some convenience stores that offer 'top up' services .. how are these
to be tagged?
On 26/12/18 19:31, Markus wrote:
Hi Daniele,
From the proposal page:
It's pos
Hi Daniele,
From the proposal page:
> It's possible to specify which brand/carrier vouchers are sold with the key
> brand=*.
>
> A bar that sells Vodafone phone vouchers: amenity=bar + top_up=yes +
> brand=vodafone
The brand=* key specifies the brand of the main tag, here amenity=bar.
In your
Link of the proposal:
https://wiki.openstreetmap.org/wiki/Proposed_features/Top_up
Hi, I propose to introduce the top_up=* key to specify whether a
shop/amenity sells top-ups (mobile phone credit recharge vouchers,
over-the-air credit top up and/or public transport credit recharge
vouchers).
Kind r
32 matches
Mail list logo
