Tagging blok flat / PPR / apartment (nak ikut MS 2039 ke?)

[petajalanterbuka]

Hi korang,

Saya selalu edit kawasan KL, and one thing keeps coming up: macam mana nak tag blok untuk flat, PPR dan apartment. Tak jumpa convention dalam forum/wiki Malaysia, jadi nak tanya pendapat.

Standard rasmi dah ada: MS 2039:2006

MS 2039:2006 — Addresses: Standard format requirements (Jabatan Standard Malaysia), seksyen 4.7. Contoh yang sama ada dalam dokumen awam UPU S42 Malaysia, yang based on standard ni. Format unit dalam bangunan bertingkat:

X-Y-Z, <Nama Bangunan>
X = blok, Y = tingkat, Z = nombor unit

Contoh dari standard (Table 7):

Salah	Betul
No 5, Tingkat 7 Blok A1, Pangsapuri Kelana Kelana Jaya 47300 Petaling Jaya	A1-7-5, Pangsapuri Kelana Kelana Jaya 47300 Petaling Jaya

Flat awam pun sama format: 2-2-10, Flat Sri Kelantan (seksyen 5.2.2).

MCMC punya Sistem Alamat Nasional (NAS) (pilot 2026, full 2027) pun aligned dengan MS 2039. So format ni memang arah yang kerajaan pakai.

Situasi dalam OSM sekarang (KL, Sep 2026)

Rojak sikit:

Cara tag	Jumlah (KL)	Contoh
name=Blok …	442	w28287704
addr:housename=Blok …	25	w616692702
building=apartments/residential + ref	285	—
↳ ref sahaja (takde name / housename / housenumber)	150	w144865065

Masalah dengan Nominatim

Saya test:

• name=Blok A → keluar dalam search
• addr:housename=... → keluar sebagai nama bangunan dalam address
• ref sahaja → tak di-index langsung (w144865065 lookup kosong)

Nominatim hanya index building kalau ada name, addr:housename atau addr:housenumber. ref cuma “extra name”. Jadi 150 blok tu memang tak boleh dicari.

Tapi bila ref + addr:housename ada sekali, ref jadi searchable dan jadi display name:

Way	Tags	Result
w433812959	ref=A5 + addr:housename=Menara Kencana Petroleum	Display: "A5, The Square, Solaris Dutamas…"
	search A5 Menara Kencana Petroleum	rank 1
	search Menara Kencana Petroleum	rank 1

Cadangan: satu scheme untuk semua (flat, PPR, apartment, kondo)

Sebab MS 2039 guna format sama untuk semua, tak perlu bezakan berpagar ke tak.

Kawasan complex:

landuse=residential
name=Pangsapuri Kelana

Setiap blok:

building=apartments
ref=A1                              ← "X" dalam X-Y-Z
addr:housename=Pangsapuri Kelana    ← nama bangunan dalam alamat
addr:street=Jalan …                 ← kalau alamat rasmi ada jalan
addr:postcode=47300

• ref = kod blok, sama macam dalam alamat rasmi (A1, bukan “Blok A1”).
• Kalau ref sentiasa kod bare (A1, bukan “Blok A1”), alamat MS 2039 macam A1-7-5, Pangsapuri Kelana boleh terus di-match ke blok. Senang untuk mana-mana geocoder / app, bukan Nominatim je.
• addr:housename buat blok tu di-index Nominatim, dan ref jadi searchable (“A1 Pangsapuri Kelana”).
• Address addr:* duplicate kat setiap blok supaya setiap satu boleh dicari.
• Unit (A1-7-5) tak perlu map, cukup sampai level blok.
• Elak addr:place + place=neighbourhood untuk nama complex. Thread Taman perumahan pun cakap place=* sorang-sorang boleh rosakkan address.

Blok bernama (contoh Blok Kenanga, Blok Melor). MS 2039 sendiri bagi contoh Melor-6-2, Pangsapuri Impian, jadi nama blok tu la “X”:

building=apartments
ref=Kenanga
name=Blok Kenanga                   ← kalau papan tanda memang tulis macam ni
addr:housename=Pangsapuri Impian

name ok untuk blok bernama sebab tu nama betul, bukan kod. Untuk A1/B2, ref je.

Soalan

1. Setuju tak guna MS 2039 sebagai basis? Ada local practice yang saya miss?
2. name=Blok A1 yang dah ada (442): biar je, atau pindah ke ref + addr:housename? (Blok bernama macam Blok Kenanga kekal name.) Tak nak mass-edit tanpa consensus.

Terima kasih!

[mataharimau]

I like the way how you researched deeply and came up with your proposal. It has many advantages in terms of standardising how apartments should be tagged, and moves towards giving good quality Nominatim display results.

Below are some of my personal opinions:

@petajalanterbuka

Cadangan: satu scheme untuk semua (flat, PPR, apartment, kondo)

Sebab MS 2039 guna format sama untuk semua, tak perlu bezakan berpagar ke tak.

If by saying “tak perlu bezakan berpagar ke tak” you mean “tak perlu map pagar”, then I would disagree because if the apartment complex is fenced, then OSM database is much richer with the mapper mapping ground truth and adding barrier=fence around the complex perimeter. It will make sense to differentiate whether fenced or unfenced in OSM database even though MS 2039 makes no such distinction.

[mataharimau]

@petajalanterbuka

Kawasan complex:

landuse=residential
name=Pangsapuri Kelana

I agree that this should be the standard tag for most apartment complex area. I would also add the additional tag:

• residential=apartments

However, not-so-uncommon situations may arise. Take for example Empire Mall in Subang Jaya. On top of this mall sits 3 buildings: Empire SoHo (condo/office), Empire Tower (office suites) and Empire Hotel. The best land area tags for…

• mall: landuse=retail
• condo: landuse=residential
• office: landuse=commercial
• hotel: tourism=hotel

So how do you tag the land area for a complex that has all these functions which Malaysian developers commonly call “mixed development”? As far as I know,

• landuse=mixed_development

is not an accepted standard in OSM.

My proposal for standardising residential mixed-development area tags is as such:

Use the most dominant feature.

As a local, I visit Empire Mall frequently. I vaguely know there are some buildings above the mall, but I can’t even remember their names offhand. The mall is the dominant feature. The condo, office and hotel are less dominant. So in this case the land area complex should be tagged with

• landuse=retail

even though Empire SoHo is a residential tower.

Another example: Petronas Twin Tower (office) is more famous than Suria KLCC (mall). So the entire area complex should be tagged with

• landuse=commercial

rather than

• landuse=retail.

[mataharimau]

@petajalanterbuka

Setiap blok:

building=apartments
ref=A1                              ← "X" dalam X-Y-Z
addr:housename=Pangsapuri Kelana    ← nama bangunan dalam alamat
addr:street=Jalan …                 ← kalau alamat rasmi ada jalan
addr:postcode=47300

I like your vision for standardising OSM tags so that the object’s address can be displayed as set by MS 2039.

@petajalanterbuka

• ref = kod blok, sama macam dalam alamat rasmi (A1, bukan “Blok A1”).
• Kalau ref sentiasa kod bare (A1, bukan “Blok A1”), alamat MS 2039 macam A1-7-5, Pangsapuri Kelana boleh terus di-match ke blok. Senang untuk mana-mana geocoder / app, bukan Nominatim je.
• addr:housename buat blok tu di-index Nominatim, dan ref jadi searchable (“A1 Pangsapuri Kelana”).
• Address addr:* duplicate kat setiap blok supaya setiap satu boleh dicari.
• Unit (A1-7-5) tak perlu map, cukup sampai level blok.

I know you said you have no intentions of mapping individual units (eg A1-7-5), but if assuming that we do, we’d want the tags for this unit to reflect it’s actual mailing address. The standard tag in OSM if you want the object to display exactly as its mailing address is addr:*

So, to display A1-7-5 Pangsapuri Kelana, Jalan ABC, Taman Kelana XYZ, Kelana Jaya, 47300 Petaling Jaya, for that individual unit you will need to tag:

• addr:housenumber=A1-7-5
• addr:housename=Pangsapuri Kelana
• addr:street=Jalan ABC
• addr:place=Taman Kelana XYZ, Kelana Jaya
• addr:postcode=47300
• addr:city=Petaling Jaya

If you leave out tagging addr: street/place/postcode/city Nominatim will try to work them out based on the polygon the object is contained within and proximity to relevant nodes. Sometimes Nominatim gets it right. Sometimes wrong.

Since you mentioned that you’d like the block, floor and unit number to be coded for proper classification purposes to be utilised by any geocoder, then perhaps I can suggest these additional tags for that particular unit:

• addr:block_number=A1
  addr:floor=7
  addr:unit=5

The above three are all approved OSM tags and they all have their relevant wiki pages. I don’t think Nominatim or Carto renders them, but they will render addr:housenumber=A1-7-5

My suggestion if we are going to tag individual apartment units:

Bare minimum standard:

• addr:housenumber=A1-7-5
• addr:housename=Pangsapuri Kelana
• addr:street=Jalan ABC

Complete standard:

• addr:housenumber=A1-7-5
• addr:housename=Pangsapuri Kelana
• addr:street=Jalan ABC
• addr:place=Taman Kelana XYZ, Kelana Jaya
• addr:postcode=47300
• addr:city=Petaling Jaya
• addr:block_number=A1
• addr:floor=7
• addr:unit=5

(How we are going to place the node of the 3D apartment unit on a 2D map is beyond the scope of this discussion)

Assuming that the community is in consensus that this shall be the standard to tag individual apartment units, we can now use this standard to be applied to tagging apartment blocks.

The MS 2039 system sets the standard how write the address for individual units in apartments (eg A1-7-5 Pangsapuri Kelana). I believe it doesn’t set a standard how to write the address for the entire block. So for Blok A1, how would you like its address to be displayed by Nominatim and other geocoders?

Blok A1, Pangsapuri Kelana, Jalan ABC, Taman Kelana XYZ ?
or
A1, Pangsapuri Kelana, Jalan ABC, Taman Kelana XYZ ?

The latter feels like an incomplete address to me. When we see A1-7-5, we know it is a unit number. But when we see A1 only, it may stump us that this is the block number. That is why I personally perfer the former address format. So my suggested tags for apartment blocks are:

• addr:housenumber=Blok A1
• addr:housename=Pangsapuri Kelana
• addr:street=Jalan ABC

I know you want to throw away the word “Blok” in order to have accurate coding records. To achieve this purpose, you can simply add the tag addr:block_number=A1 to the existing tags above.

[mataharimau]

@petajalanterbuka

• Elak addr:place + place=neighbourhood untuk nama complex. Thread Taman perumahan pun cakap place=* sorang-sorang boleh rosakkan address.

This is an old thread 8 years ago. You may want to check with @AkuAnakTimur whether today he still agrees not to use place=* tags because (according to him) it causes Nominatim to display addresses incorrectly. I don’t have the same experience. Nominatim has lots of bugs anyway when attempting to display full address correctly and until today, I don’t know what triggers those bugs. I know that most of the time, Nominatim gets the place=* right, but sometimes it gets it wrong. The same goes for objects within landuse=residential polygons. Nominatim sometimes gets this wrong too.

It may interest you to know that despite tagging the object with the complete addr:* tags, Nominatim may sometimes still choose to ignore those tags and attempt to work out its own address instead and give you the wrong address.

I rarely map apartment area complex with place=neighbourhood. My default standard is landuse=residential. But sometimes, the complex may be a mixed development whereby Block A in the north is a retail complex, and a separate Block B in the south is the residential tower. (They are not on top of one another like Empire Subang). So the land area around Block A - I tag with landuse=retail, and the land area around Block B - I tag with landuse=residential, and the whole area complex to include both residential and retail landuse, I tag with place=neighbourhood and I insert the name of the complex here.

[mataharimau]

@petajalanterbuka

Blok bernama (contoh Blok Kenanga, Blok Melor). MS 2039 sendiri bagi contoh Melor-6-2, Pangsapuri Impian, jadi nama blok tu la “X”:

building=apartments
ref=Kenanga
name=Blok Kenanga                   ← kalau papan tanda memang tulis macam ni
addr:housename=Pangsapuri Impian

name ok untuk blok bernama sebab tu nama betul, bukan kod. Untuk A1/B2, ref je.

I agree that if MS 2039 treats “Melor” from the name Blok Melor as a code and standardises it as the address with “Melor-6-2” then “Melor” should be the block code.

For standardisation, I have already suggested above to use addr:block_number=* as replacement for ref=* to record the block code. So, yes, I agree to your proposed standard; just that ref=Kenanga be changed to addr:block_number=Kenanga.

And yes - we should keep the tag name=Blok Kenanga because it is the representation of ground truth.

[mataharimau]

@petajalanterbuka

Soalan

1. Setuju tak guna MS 2039 sebagai basis? Ada local practice yang saya miss?

I believe I have already written extensively on this above.

@petajalanterbuka

2. name=Blok A1 yang dah ada (442): biar je, atau pindah ke ref + addr:housename? (Blok bernama macam Blok Kenanga kekal name.) Tak nak mass-edit tanpa consensus.

Leave it. name=Blok A1 represents ground truth and is used for rendering on maps like OSM Carto.

Add addr:housenumber=Blok A1, addr:housename=Pangsapuri Kelana, and addr:street=Jalan ABC for accurate display of address when queried for the address.

Add addr:block_number=A1 to record the code in the database.

I tahu you started the thread pakai BM and I replied in English. Please feel free to reply dlm Bahasa Melayu. I bole jer cakap ok pakai BM, tapi topic nie cukup berat and I feel I can express the details more clearly kalu pakai cakap om puteh.

My dua sen

[kucai]

Idea yg bagus dan yg dah lama bergelut nak memahamkan camna nominatim berfungsi.

@petajalanterbuka

w433812959 ref=A5 + addr:housename=Menara Kencana Petroleum Display: "A5, The Square, Solaris Dutamas…"

cuma, bagi aku ialah camne kita nak suruh nominatim ni masukkan nama landuse dalam alamat. contoh di atas: kalau kita tgk alamat poi ‘the roomah’, alamat yang keluar takde pulak tulis menara kencana petroleum walaupun dia duduk dalam polygon menara tu. tukar addr:housename → addr:unit?

ni perkara yang sama berlaku kat sesetengah komplek apartmen / flat, nama kompleks tu tak keluar dalam address search. mungkin setiap mende tu kena masukkan semua details dalam tag dan elakkan nominatim daripada membuat rumusan alamat berdasarkan subset polygon. nak guna admin level tag sama mcm kampung ke? boundary type? pefenifing..

name vs addr:housename. aku cadang guna addr:housename dan buang name sebab redundant (asalkan dirender).
ref = A5 dan buang description. Paling penting, nombor/nama blok dirender dlm semua map supaya senang nak cari bila tgk peta masa buat delivery.

[mataharimau]

@kucai

cuma, bagi aku ialah camne kita nak suruh nominatim ni masukkan nama landuse dalam alamat. contoh di atas: kalau kita tgk alamat poi ‘the roomah’, alamat yang keluar takde pulak tulis menara kencana petroleum walaupun dia duduk dalam polygon menara tu. tukar addr:housename → addr:unit?

ni perkara yang sama berlaku kat sesetengah komplek apartmen / flat, nama kompleks tu tak keluar dalam address search. mungkin setiap mende tu kena masukkan semua details dalam tag dan elakkan nominatim daripada membuat rumusan alamat berdasarkan subset polygon. nak guna admin level tag sama mcm kampung ke? boundary type? pefenifing..

I setuju yg Nominatim nie has a long way more to go… Kat UM I nampak ada Blok B dlm polygon Fakulti Perniagaan & Ekonomi dlm polygon Universiti Malaya. Tapi bila I search “Blok B Fakulti Perniagaan & Ekonomi Universiti Malaya” Nominatim kata: No Results Found. Aku rasa Nominatim algorithm ni masih confused polygon yg mana to include & yg mana to exclude in their search results.

@kucai

name vs addr:housename. aku cadang guna addr:housename dan buang name sebab redundant (asalkan dirender).

I agree that its redundant to tag both name and addr:housename if they both render and have the same values. But there are instances they may not have the same values.

Example: A hypothetical AirBnB bungalow with the signboard: “The Bayu” addressed at 118, Jalan Tepi Pantai. Let’s say the owner markets this AirBnB online as “Bayu by the Beach” and in his website, puts his official address as “Bayu by the Beach, 118 Jalan Tepi Pantai.” In a situation such as this, you’d want to tag: name=The Bayu so that this name renders in Carto as per “ground truth”, but also include addr:housename=Bayu by the Beach, addr:housenumber=118, and addr:street=Jalan Tepi Pantai so that when queried, the address displays as per official address as used by the business.

This situation becomes much more complex when dealing with apartments. Let’s revisit the Blok Kenanga, Pangsapuri Impian example given by op. When querying the address, you’d want the address result to display as: Blok Kenanga, Pangsapuri Impian, Jalan XYZ. This theoretically will require 3 tags: addr:block=Blok Kenanga, addr:complex=Pangsapuri Impian and addr:street=Jalan XYZ. The problem is addr:block=* is not supported by Nominatim, and addr:complex=* (or any other similar variant to represent the apartment compound) doesn’t even exist in OSM tagging. Nominatim only recognises addr:housenumber=* and addr:housename=*.

This was the reason why op suggested name=* and addr:housename:* to be different…

@petajalanterbuka

name=Blok Kenanga                   ← kalau papan tanda memang tulis macam ni
addr:housename=Pangsapuri Impian

… and I agree with him. Because addr:complex=* doesn’t exist and so we are forced to use addr:housename=* to tag the area complex as part of the address.

[kucai]

1. addr:housenumber/flat : 123

2. addr:unit = Blok Kenanga

3. Pangsapuri impian is a polygon, minimally landuse=residential.

4. addr:street also on pangsapuri polygon (for apt/flat that doesn’t have street names in their complexes - which is a whole lot majority of them)

our current issue is that nominatim is not consistent is using item 3) as a admin level 10 ranking to be shown in the resulting address search. that’s why you see sometimes the polygon also has a place=* tag, trying to force nominatim to use the name with some success.

Otherwise, we have to resort to the brute force method. every single building will have all the tags, including addr:suburb, addr:town etc etc. In this way we hope nominatim only uses those tags and not try to be clever. This brings up another potential issue, since addr:suburb will cause two admin levels to clash, for example if pangsapuri is inside a huge residential area. (in the wiki addr:suburb is also applicable to village/neighborhood - same admin rank)

That bayu issue, I do believe osmand will render both housename and number. It will show “bayuxxx(118)”.

[mataharimau]

@kucai

our current issue is that nominatim is not consistent is using item 3) as a admin level 10 ranking to be shown in the resulting address search.

Setuju.

I guess the question now is how do we move forward to standardise tagging of blocks in apartment compounds given that Nominatim is very stubborn in displaying address results that Blok Kenanga is in Pangsapuri Impian since it rarely acknowledges the landuse=residential polygon.

Do you think op’s proposal ie tagging name=Blok Kenanga, addr:housename=Pangsapuri Impian onto the building block will solve the issue?

[kucai]

susah nak kata. let’s experiment. cari satu kompleks pangsapuri yang berada dalam taman (supaya ada 2 suburb), dalam bandar. cari blok yg sebelah menyebelah. setiap satu try variation tags yg kita bincang. kemudian beri masa supaya osm & nominatim update. kita tengok mana hasil yang paling memuaskan.

[mataharimau]

Just for general informational purposes - there was already a discussion in the international forum to move away from landuse=residential in favour of place=neighbourhood when mapping named housing estates. The main reason being the landuse within the area (eg Bangsar Park) is not only residential, but also retail, commercial, school, etc.

Someone suggested that for apartment complexes, to move on from landuse=residential + residential=apartments to place=apartments though it was generally met with resistance, but there were some opinions that this is the way to move forward because of mixed development apartment projects especially seen in South Korea and Singapore.

Speaking of Singapore - is there an already established standard how to tag apartment blocks? If yes, maybe can consider following their standard?

[petajalanterbuka]

@mataharimau

Speaking of Singapore - is there an already established standard how to tag apartment blocks?

Had a look. Singapore is consistent, diorang guna addr:housenumber.

Of 22,121 building=apartments/residential in SG, 94% carry addr:housenumber. Typical HDB block:

addr:housenumber = 596A
addr:street      = Ang Mo Kio Street 52
addr:postcode    = 561596

It works over there because an HDB block number really is the official premise number on the street, and one block = one postcode. Blok sebelah-menyebelah pun lain poskod:

Blok	Poskod
596A	561596
596B	562596
596C	563596
596D	564596

So alamat penuh dia memang 596A, Ang Mo Kio Street 52, Singapore 561596. Takde nama kompleks langsung, tak perlu pun.

Kat Malaysia dua-dua kes wujud, so belum tentu boleh terus pakai corak SG.

[petajalanterbuka]

Terima kasih @mataharimau, @kucai. Aku rasa skop asal dah terlalu besar.

Jalan, nombor premis (addr:housenumber) dan nama kompleks takde pertikaian. Yang tinggal cuma kod blok. Dua soalan je.

Soalan 1: kod blok masuk key mana?

@mataharimau aku setuju dengan arah kau, keluarkan dari ref dan masuk namespace addr:*. Cuma aku cadang key addr:block.

Wiki addr:block_number tulis “block as in area between roads”. I think it was referring to sistem banchi Jepun. Top values dunia pun 1, 2, 3. Macam dah lari original purpose of the tag.

addr:block pula pernah digunakan sikit kat MY untuk pangsapuri. Aku check: 123 bangunan apartments/residential kat MY ada addr:block, 90 daripadanya edit kau. Jadi apa yang aku cadang ni lebih kepada standardise apa yang kau dah buat.

Kalau korang check taginfo nampak 713 objek addr:block kat MY. Majoriti tu POI dalam mall Kota Kinabalu, tapi maksud “blok” dia lain sikit. Untuk pangsapuri angka dia 123.

Nilainya pula belum konsisten, G ke Blok G? Data sekarang campur dua-dua. Aku suggest code je, buang “Blok”/“Block” (G, A1) sebab MS 2039 tulis A1-7-5.

Soalan 2: flat yang takde nama kompleks

Masa tulis post tu, aku ingat semua kompleks ada nama. Rupanya tak.

Flat PKNS Seksyen 16 Bangi, alamat rasminya:

BLOCK 6, JALAN 6C/9, SEKSYEN 16, 43650 BANDAR BARU BANGI

Blok dengan jalan sahaja. Kalau blok macam ni cuma dapat addr:block, dia takde nama dalam database dan tak boleh dicari.

Jadi it’s either:

Pilihan	Bila sesuai
name=Blok 6	papan tanda memang tulis (442 objek KL dah macam ni)
addr:housenumber=6	blok tu memang nombor premis atas jalan

Ni soalan sebenar aku kat korang.

@kucai

let’s experiment. cari satu kompleks pangsapuri yang berada dalam taman (supaya ada 2 suburb), dalam bandar. cari blok yg sebelah menyebelah. setiap satu try variation tags yg kita bincang.

Setuju, jom. Kau pilih kompleks, aku tolong tag separuh blok.

[kucai]

aku rasa addr:block tak perlu. cuba tengok addr:unit seperti yg dibincang kat Addresses in the United Kingdom - OpenStreetMap Wiki . sama mcm yg kita bincangkan sekarang.

"If a named building or large complex is split into sub-parts then you need to use one of these tags. This puts that sub-part before the building name when the address is written out on an envelope. The choice of tag depends on whether you are recording a single address of multiple addresses. For more info see the addr:housenumber, addr:unit and addr:flats section below.

Single address:

• Use addr:unit to record the number, letter, or name of a single unit or flat that exists within a larger complex. If a ground survey identifies a “Flat 1” then the tag should be addr:unit=Flat 1, i.e. it should include the word Flat. Similarly if a ground survey identifies a “Unit B” then use addr:unit=Unit B as the tag."

bab tagging eksperiment ni aku khuatirkan akan ambik masa kalau aku yg start. lepas seharian buat delivery, aku capek. elok hang lead, aku boleh try tengokkan alternatif area kalau sempat. mula2 kena cari suburb yg luas.

edit: dah cuba variation untuk block, ref, housename. kat flat taman nirwana. kita tunggu result…

[mataharimau]

@petajalanterbuka

Aku rasa skop asal dah terlalu besar.

Sorry for overkill feedback. I will keep it brief and straight to the point here.

@petajalanterbuka

Soalan 1: kod blok masuk key mana?

aku cadang key addr:block.

Nilainya pula belum konsisten, G ke Blok G? Data sekarang campur dua-dua. Aku suggest code je, buang “Blok”/“Block” (G, A1) sebab MS 2039 tulis A1-7-5.

Ok, setuju - Boleh pakai addr:block=* untuk tujuan simpan code dlm database.

Blok Kenanga pun buang “Blok” dan simpan “Kenanga” shj sbg code.

Cuma I rasa Nominatim tak baca tag nie dan tak display dalam address result. Dan Carto tak render dlm peta.

Dicadangkan supaya ditambah addr:housenumber=* spt yg dipakai di Singapore sebab nie standard yang dipakai dan di-render oleh Carto dan Nominatim. Di tag ini, value boleh ada perkataan “Blok”, eg: “Blok A1”, “Blok Kenanga”

@kucai

aku rasa addr:block tak perlu. cuba tengok addr:unit seperti yg dibincang kat Addresses in the United Kingdom - OpenStreetMap Wiki . sama mcm yg kita bincangkan sekarang.

Single address:

• Use addr:unit to record the number, letter, or name of a single unit or flat that exists within a larger complex.

I rasa addr:block lagi sesuai drp addr:unit utk tagging apartment block. Kat UK, ‘unit’ dan ‘flat’ sama makna dan merujuk kepada ruang kediaman individu bagi setiap keluarga, bukan kpd the building block. Op nak code utk building block, bukan unit yg didiami oleh keluarga.

@petajalanterbuka

Soalan 2: flat yang takde nama kompleks

Masa tulis post tu, aku ingat semua kompleks ada nama. Rupanya tak.

Flat PKNS Seksyen 16 Bangi, alamat rasminya:

BLOCK 6, JALAN 6C/9, SEKSYEN 16, 43650 BANDAR BARU BANGI

(Amik perhatian bahawa alamat rasmi tak ikut MS 2039 ya. MS 2039 hanya utk alamat rasmi unit condo/apartment, bukan utk alamat rasmi blok).

Cadangan saya - ikut format sama spt dlm soalan 1

• addr:block=6
• addr:housenumber=Block 6
• addr:street=Jalan 6C/9

Asalkan Seksyen 6 dan Bandar Baru Bangi dah dilukis relational polygon dgn tag2 type=boundary, boundary=administrative dan admin_level=*, dan blok apartment terkandung dlm polygon masing2, Nominatim akan display alamat rasmi spt yg dituliskan.

Practice di mana addr:block=6 dan addr:housenumber=Block 6 di-tag bersama-sama bukan redundant ya. Nie dipanggil concurrent tagging (tengok key:education=*). Bila dlm masa hadapan, Nominatim dan Carto acknowledge dan render addr:block=* tags, maka addr:housenumber=* boleh di mass-delete-kan.

[petajalanterbuka]

@kucai

bab tagging eksperiment ni aku khuatirkan akan ambik masa kalau aku yg start. lepas seharian buat delivery, aku capek. elok hang lead, aku boleh try tengokkan alternatif area kalau sempat. mula2 kena cari suburb yg luas.

edit: dah cuba variation untuk block, ref, housename. kat flat taman nirwana. kita tunggu result…

Oh sorryy. takpe aku dah figure out camne nak run Nominatim locally on my computer. Later aku test all test cases

[petajalanterbuka]

@mataharimau

Cuma I rasa Nominatim tak baca tag nie dan tak display dalam address result.

Aku dah test guna Nominatim kat laptop sendiri. Dia baca addr:block dan boleh search, tapi kod tu tak keluar dalam alamat.

Aku buat Pangsapuri Test dalam Taman Test, lepas tu tag blok cara lain-lain. Output Nominatim:

Tag pada blok	Alamat keluar
addr:block=B + addr:housename=Pangsapuri Test	Pangsapuri Test, Jalan Batu Arang, Pangsapuri Test, Majlis Perbandaran Selayang, …
name=Blok D + addr:housename=Pangsapuri Test	Blok D, Jalan Batu Arang, Pangsapuri Test, Majlis Perbandaran Selayang, …
addr:housenumber=E + addr:street=Jalan Test 1	E, Jalan Test 1, Taman Test, Majlis Perbandaran Selayang, …

Blok B tak nampak langsung dalam alamat. Blok D keluar sebab ada name, dan nama complex masih ada. Blok E pula ada addr:housenumber + addr:street, jadi “Pangsapuri Test” hilang, yang keluar “Taman Test”.

Blok yang ada addr:block je, takde name atau addr:housename, langsung tak masuk index.

Kalau nak addr:block keluar dalam alamat, kena minta kat Nominatim. Tak payah tag addr:housenumber semata-mata untuk dia.

@kucai

aku rasa addr:block tak perlu. cuba tengok addr:unit

Page wiki UK yang sama, bawah sikit (“When to use addr:unit?”):

The name/number of the block goes in addr:housename/addr:housenumber and the individual dwelling numbers go in addr:unit.

addr:unit untuk nombor rumah. Dalam A1-7-5, addr:unit lebih kepada 5, bukan A1.

Setakat ni rasanya kita dah setuju kod blok masuk addr:block, value kod je (A1, Kenanga). Ikut kes:

1. Blok dalam complex ada nama

Complex (polygon):
landuse          = residential
residential      = apartments
name             = Pangsapuri Test
addr:housenumber = 22            (kalau complex ada nombor jalan)
addr:street      = Jalan Test 1

Blok:
building         = apartments
addr:block       = A1
addr:housename   = Pangsapuri Test

Aku rasa blok tak perlu addr:housenumber. Kod blok bukan nombor rumah atas jalan, dan macam blok E atas, nama complex hilang.

2. Blok takde complex, macam Bangi

building         = apartments
addr:block       = 6
addr:housenumber = Block 6
addr:street      = Jalan 6C/9

[mataharimau]

@petajalanterbuka

Tag pada blok	Alamat keluar
addr:block=B + addr:housename=Pangsapuri Test	Pangsapuri Test, Jalan Batu Arang, Pangsapuri Test, Majlis Perbandaran Selayang, …
name=Blok D + addr:housename=Pangsapuri Test	Blok D, Jalan Batu Arang, Pangsapuri Test, Majlis Perbandaran Selayang, …

I perasan - dlm output pertama, alamat “Pangsapuri Test” display dua kali, tapi dlm output kedua, dia keluar sekali shj. Saya nak tahu output nie dtg dari tag addr:housename=Pangsapuri Test pada building blok ker ataupun dari tag name=Pangsapuri Test pada complex polygon.

Boleh minta repeat experiment sama? Cuma sekarang tag:

• blok dgn addr:housename=Pangsapuri Test (blok tag), dan
• complex polygon dgn name=Pangsapuri Test (complex tag)

Saya suspect:

• output pertama akan keluar: Pangsapuri Test (blok tag), Jalan Batu Arang, Pangsapuri Test (complex tag), Majlis Perbandaran Selayang, …
• output kedua akan keluar: Blok D, Jalan Batu Arang, Pangsapuri Test (complex tag), Majlis Perbandaran Selayang, …

Terima kasih kerana sudi buat test2 nie. Saya dulu pernah cuba buat, tapi terlalu peningkan saya.