Thanks for the edit. Seems that the sign was removed to be replaced with a newer one.

I recently updated the imagery of that junction in Mapillary with the restriction sign re-installed: http://www.mapillary.com/map/im/hGgYlZ-dXJ_rzc_tRI_1lQ/photo

Though yes, there’s the odd-even plate restriction along Jalan Gatot Subroto and Jalan Letjen S. Parman, the aforementioned restriction was simply “Do not turn right from leftmost lane”. A “No Right Turn” signage is installed at the junction between Jalan Gatot Subroto and Jalan Tentara Pelajar, which was intended to be read by vehicles moving from the latter street.

Hello,I'd like to comment on the changes of the junction of Jalan Gatot Subroto/Letjen S. Parman/Aipda KS. Tubun/Palmerah Utara streets (near the bus station "Slipi Petamburan"). The last map edit on this junction (edited by me), though geometrically incorrect, was designed to cope with a unique turn restriction that may result in fines, for vehicles moving from Jalan Tentara Pelajar as well as Jalan Gatot Subroto (from South to North).

Vehicles moving from Jalan Gatot Subroto can freely choose the direction they would like to turn.


Meanwhile, vehicles from Jalan Tentara Pelajar are not allowed to take a right turn (as well as a U-turn) to Jalan Aipda KS. Tubun and Jalan Gatot Subroto.


I'm quite concerned with how current payment methods are classified here. For example, in defining Electronic Purses, which applies to multiple payment systems around the world. Not all EPs are using "ep_" prefixes, such as Japan's ICSF cards ("payment:icsf"), as before this was only used for transport.

Another one is how to add mobile payment apps to OpenStreetMap. For example, Apple Pay ("payment:apple_pay") and Samsung Pay ("payment:samsung_pay") apps may integrate to other payment systems, such as Alipay ("payment:alipay") and WeChat Pay ("payment:wechat") in China.

I see this tagging scheme as confusing, as this do not specify whether to follow "tagging by payment medium" (e.g. "payment:fuel_cards") vs "tagging by payment system" (e.g. "payment:visa").

But at least, making a de facto tagging standard might be useful for future improvements.

Hi,
Thanks for noticing this. So yes, you may update the tags, noting that I added these "incorrect" tags as a feasibility testing for one of my payment scheme proposals.

Note that not all "id_" - prefixed tags may be replaced with "ep_", as some of them may refer to payment systems which do not fall under "electronic purses". For example, "payment:id_mandiri_emoney" is changed to "payment:ep_mandiri_emoney", "payment:id_ovo" to "payment:ovo", and "payment:id_gopay" to "payment:gopay_id" (to avoid "gopay" trademark conflicts between Indonesia and Malaysia).

i previously added several payment tags which are prefixed with "id_" (such as payment:id_flazz and payment:id_gopay) before I edited the wiki (see osm.wiki/w/index.php?title=Key:payment&oldid=1889649) to include these new, unprefixed tags for Indonesian payment systems.

I decided to introduce those in the existing Wiki article, as I believe that would be easier than creating a new scheme proposal (I made one at osm.wiki/Proposed_features/Scheme_for_local_payment_systems and another one at https://telegra.ph/Konvensi-tag-payment-di-Indonesia-04-19).

As of today, there are still some objects that are tagged with the previous, "id_" scheme. For example, there are about 50 places which are tagged with "payment:id_flazz=yes" across Jakarta and Bandung (see TagInfo).

Halo, maksud dari "B", "C", dan "SOHO" itu apa ya?

At first, it's quite difficult to decide, considering that these roads connects multiple villages together. But after consulting with the wiki I agree to change both ways as unclassified.

It seems that I incorrectly tagged some long roads there, such as 682698602 which should be tagged as either service or unclassified.

There's still a debate on tagging village roads as unclassified/residential/service, such as in https://github.com/GRABOSM/Grab-Data/issues/22. I'll be checking this area later.

I have proposed a changeset for this. Can you re-check whether the issue has been resolved? Thanks.
https://osmcha.mapbox.com/changesets/56584161/

Thanks for reporting. While this issue is being fixed, I temporarily removed these turn restrictions.
changeset/56583038