User:Seav/LGUs
This is a proposed set of mapping conventions intended to overhaul or replace the existing one. Feedback is very much welcome on the talk page or on any of the communication channels where this has been shared. |
This page documents the conventions for mapping administrative entities in the Philippines such as regions, provinces, cities, municipalities, barangays, and everything in between.
Philosophy: As much as practically possible, the conventions for mapping administrative entities should match the global conventions. This includes reusing globally-defined tags instead of inventing local tags (for example, use ref=* instead of psgc=* or ref:psgc=*).
Summary
admin_level=* | Entity type | Boundary relation example | Extent of maritime boundary | place=* node | Quick remarks | |
---|---|---|---|---|---|---|
As admin_centre | As label | |||||
2 | Country | 443174 443174 (Philippines) | Territorial sea (12 nautical miles from the Philippine baselines, per the United Nations Convention on the Law of the Sea) |
|
||
3 | Region | 3821409 3821409 (Bangsamoro) | Municipal waters (15 kilometers from the coastline, per R.A. 8550) |
|
||
4 | Province | 1504669 1504669 (Pampanga) |
|
Exclude Highly Urbanized Cities from the provincial boundary relation if possible; include Independent Component Cities (except Cotabato City) since these are still considered "component" cities of the province | ||
5 | Sangguniang Panlalawigan (Provincial Board) district | 5428241 5428241 (Leyte 1st District) | Not needed | These often coincide with districts of the Congress of the Philippines | ||
National Capital Region district | 11037661 11037661 (Fourth District) |
|
Not needed | These were formerly assigned province-level 9-digit PSGC numbers | ||
6 | City | 12165003 12165003 (Mandaue) | Not needed | |||
Municipality | 12236874 12236874 (Pagbilao) | |||||
7 | Sangguniang Panlungsod (City Council) district | 2274282 2274282 (5th District, Quezon City) | Coastline | Not needed | These sometimes coincide with districts of the Congress of the Philippines | |
Sangguniang Bayan (Municipal Council) district | No example yet | |||||
8 | City district | 9713955 9713955 (Mandurriao, Iloilo City) | Not needed |
|
Cities that have recognized districts include:
| |
9 | Barangay zones | 11322819 11322819 (Zone 16, Caloocan) | Not needed | Applies to Manila, Pasay, and Caloocan | ||
10 | Barangay | 12309923 12309923 (Calitcalit, San Juan, Batangas) | Not needed |
|
Add poblacion=yes to the nodes of poblacion barangays | |
11 | Sitio/Purok | Optional 1805481 1805481 (Sitio 6, San Isidro, Makati) |
Not needed |
|
Recommended tags
Tag | On boundary relation? | On place node? | Quick remarks | |
---|---|---|---|---|
admin_level=* | Required | See the table above | ||
boundary=administrative + type=boundary |
Required | Omit | ||
place=* | Omit | Required | ||
admin_type:PH=* | Omit | admin_type:PH=province admin_type:PH=municipality admin_type:PH=barangay admin_type:PH=sitio admin_type:PH=purok |
||
is_in=* | Omit if redundant |
| ||
ISO3166-2=* | Only for regions and provinces | Tag value format is PH-00 for regions and PH-XYZ for provinces. Consult Wikipedia for the list of valid values.
| ||
int_ref=* | Only for regions and provinces | Tag value should be the same with ISO3166-2=* | ||
ref=* | If 10-digit PSGC exists | Only applies to regions, provinces, cities, municipalities, barangays, NCR districts, and some Manila districts (Sampaloc and Santa Ana have since been split with the addition of Santa Mesa and San Andres but the PSGC number still refers to the original district) | ||
old_ref=* | If old 9-digit PSGC exists | |||
poblacion=yes | Omit | Add for poblacion barangays | Poblacion barangays either have "Poblacion" in their name or are marked with "(Pob.)" in the PSGC database | |
name=* | Required |
| ||
official_name=* | Optional |
| ||
alt_name=* | Optional | The "Region IX" names use these tags, hence alt_name=Region X;Region 10 | ||
short_name=* or name:abbr=* |
Optional |
| ||
*name:*=* | Optional | See Names for other name-related tags | ||
population=* | Required | source=* tags on individual OSM objects is no longer recommended and the current practice is to add the source in changeset tags. If the population:date=* has a value of 2020-05-01 , 2015-08-01 , or 2010-05-01 , then it is already implied that the source is the Philippine Statistics Authority. Some existing population values need updating because they still reflect the 2015 census. | ||
population:date=2020-05-01 | Required | |||
source:population=Philippine Statistics Authority | Optional | |||
wikidata=* | Optional | Required if Wikidata item exists (which includes everything down to the city/municipal level; some barangays may have items) | ||
wikipedia=* | Optional |
|
Detailed place node conventions
Location
The global label place node convention states that this is the "node representing the place, located at the coordinate where the place is typically labeled. For example, a city's commonly accepted "center" may be at the city hall, a public square, or the origin of the city's street grid, rather than the geographic centroid of the boundary." This is how it is translated into the Philippine context:
- For the administrative entities higher than cities and municipalities (i.e., provinces and regions), put it at the "logical" geometric center of the province. Do not put it at the capital to avoid clashing with the label for the admin_centre place node (i.e., the capital city or municipality).
- For cities and municipalities, place the admin_centre node at the cultural or economic center of the city or municipality. This is usually in the poblacion area at the city or town plaza, or around where the main parish church, central elementary school, main public market, city or municipal hall is clustered. Do not place the node at the city or municipal hall especially if the city or municipal hall has been rebuilt elsewhere. An exception to the poblacion placement is if the city or municipality has a well-known central business district area or downtown district.
- Example 1: The Biñan place=city node (198531889 198531889) should be placed at Plaza Rizal (648982827 648982827), which is surrounded by the Biñan Church (San Isidro Labrador Parish Church), the old municipal hall (which now houses the Biñan museum), and the main public market, and should not be placed at the new Biñan City Hall complex (756176861 756176861), located around 3 km to the south.
- Example 2: The Makati place=city node (255066773 255066773) should be placed at the "center" of the Makati CBD because the CBD has already eclipsed the Poblacion in importance. When people think of Makati, they think of the CBD and not the poblacion area that contains the Spanish-era Makati Church and the old town hall.
- For barangays, sitios, and puroks:
- If there is a logical center, often where the cluster of barangay hall, parish/chapel, and school(s) are located, put the barangay place=* node there. If possible, prefer near the intersection of major streets.
- Example 1: 600229063 600229063 - Brgy. Logon (aka Malapascua), Daanbantauan, Cebu
- Example 2: 6578512014 6578512014 - Brgy. Cabra, Lubang, Occidental Mindoro
- If there is no logical center, and this is usually because the barangay is completely urban, put the barangay place=* node at the geographic center and add it as label in the boundary relation.
- Example 1: 5866009920 5866009920 - Brgy. Banilad, Mandaue
- Example 2: 251005197 251005197 - Brgy. South Triangle, Quezon City
- If the barangay/sitio/purok has a generic alphanumeric name (example "Barangay 1") and it is small in area, do not anymore add a place node; the boundary relation is enough.
- Philosophy: These small alphanumeric-named barangays are often for administrative convenience and residents do not really refer to these places in everyday talk; therefore, we shouldn't add any place=* nodes for these barangays and only have the boundary relation.
- Example 1: 8142179 8142179 - Barangay 658, Intramuros, Manila.
- Example 2: 11311757 11311757 - Barangay 15-B, Poblacion, Davao City
- If there is a logical center, often where the cluster of barangay hall, parish/chapel, and school(s) are located, put the barangay place=* node there. If possible, prefer near the intersection of major streets.
place=* value decision matrix
LGU type | Condition | place=* value | Examples | |
---|---|---|---|---|
City | — | place=city | Not needed | |
Municipality | — | place=town | Not needed | |
City district | ≤ 500 hectares | place=borough | None yet | |
> 500 hectares | place=suburb | None yet | ||
Barangay | Urban AND ≤ 50 hectares AND no sitios/puroks/neighbourhoods | place=neighbourhood | 12253665 12253665 | Daungan, Pagbilao, Quezon: 11 ha |
12284899 12284899 | Poblacion, San Juan, Batangas: 46 ha | |||
104057 104057 | Kasilawan, Makati: 10 ha | |||
366188 366188 | Escopa III, Quezon City: 9 ha | |||
Urban AND (> 50 hectares OR has sitios/puroks/neighbourhoods) | place=quarter | 2973728 2973728 | Barangay 76, Pasay: 416 ha | |
103690 103690 | San Lorenzo, Makati: 173 ha | |||
11124743 11124743 | Bocohan, Lucena: 334 ha | |||
Rural AND ≤ 300 population | place=hamlet | 8392479021 8392479021 | Ilayang Bagumbungan, Pagbilao, Quezon: 277 pop. | |
6243971732 6243971732 | Helene, Loreto, Dinagat Islands: 278 pop. | |||
2638666474 2638666474 | Nakanmuan, Sabtang, Batanes: 142 pop. | |||
Rural AND > 300 population | place=village | 6578512014 6578512014 | Cabra, Lubang, Occidental Mindoro: 1762 pop. | |
3658434607 3658434607 | Balesin, Polillo, Quezon: 1415 pop. | |||
617250346 617250346 | Apo Island, Dauin, Negros Oriental: 823 pop. | |||
Sitio/Purok | Urban | place=neighbourhood | 32975076 32975076 | Sitio Masagana (Purok 11), Alabang, Muntinlupa |
Rural | place=hamlet | 8403468500 8403468500 | Sitio Bulihan, Janaojanao, San Juan, Batangas |
Notes
- Urban vs rural can be decided based on the PSGC classification, or by simple inspection of the administrative entity's territory:
- If > 66.7% to 75% of the territory is undeveloped or farmland, it is probably rural
- Otherwise and/or if it is part of the city or town's poblacion, or its built-up core is an extension of the poblacion area, it is probably urban
- place=* nodes may also be used for non-administrative places that have distinct characteristics. For example:
- Malibay is a fuzzy district in Pasay and can be tagged as place=suburb.
- Cubao, Diliman, San Francisco del Monte, and the various Projects are defined/fuzzy districts in Quezon City and can be tagged as place=suburb or place=borough.
- Salcedo Village is a defined area in Makati (bounded by Buendia, Ayala, Paseo de Roxas and Makati Avenue) and can be tagged as place=neighbourhood.
- Large subdivisions such as BF Homes Parañaque in Parañaque that contains a lot of independent homeowners associations can be tagged as place=quarter.
- Note: Small or homogeneous gated subdivisions should just be tagged as an named (name=*) landuse=residential; no need to have a place=* node. Example: 72656404 72656404 (McKinley Hill Village in Taguig).
- Mixed-use "townships" such as Eastwood City in Quezon City, Filinvest City in Muntinlupa, or Arca South in Taguig can be tagged as place=neighbourhood or place=quarter depending on size. These townships often have a mixture of landuse=residential, landuse=retail, or landuse=commercial areas.
Detailed boundary relation conventions
Mandatory
- The relation should include the admin_centre node and the label node, if they exist.
- The outer and inner ways should be complete and unbroken.
- Province boundary area should exclude Highly Urbanized Cities, if possible, but still include Independent Component Cities (except Cotabato City) since these are still "component" cities. This may result in a admin_centre node that is outside the provincial boundary (which is actually the case). For instance, while Cebu City is the capital of the province of Cebu, the provincial government has no jurisdiction over the city's territory and pays the city government for upkeep and other expenses related to the Cebu Provincial Capitol complex.
- If the boundary way already has a primary tag (typically, highway=*, waterway=*, or natural=coastline), do not add any boundary-related tags to it (this confuses iD). Otherwise, and if the way would have been untagged, please add the following mandatory tags:
- admin_level=* - with the lowest numeric value
- boundary=administrative
- Additionally, if the boundary way delimits municipal waters, add the maritime=yes tag. Also, the landward end of such boundary ways should be connected to the coastline.
- Example: 910892453 910892453 - boundary way delimiting the northern municipal waters between Lubang and Looc in Occidental Mindoro
Nice-to-have
Relations should not be modified just to follow these suggestions. But if the relation would be modified anyway, then the following should be followed.
- Order of relation members:
- First relation member is the admin_centre node, if present
- Second relation member is the label node, if present
- Next relation members are the main outer ways going counterclockwise starting from the "north" corner. (This follows the coastline direction convention.) Followed by the corresponding inner ways.
- Next relation members are the secondary outer and inner ways, if any. (Example, the ways surrounding Corregidor for Cavite City.)
Administrative building conventions
Common tags
- building=public
- office=government
- government=administrative
- Usual tags like addr=*, wikipedia=*, wikidata=*, building:levels=*. etc.
Specific tags
Type | Tags | name=* format |
---|---|---|
Provincial capitol | "XXX Provincial Capitol" | |
City hall | "XXX City Hall" | |
Municipal hall | "XXX Municipal Hall" | |
Barangay hall |
Complex area
- No conventions yet aside from landuse=commercial
- Current tagging examples:
Unresolved questions
- Province place nodes are currently tagged as place=state. Should we migrate to place=province? Note that the latter is currently not recognized as a POI in JOSM (shows up as a generic node icon).
- Should admin_type:PH=* be added also on boundary relations? For context, designation=* is added to the boundary relations of civil parishes in the UK and admin_type:FR=* is added to the boundary relations of communes in France.