From 5e5e7748cc0485d6b95f3a810be72dec6d65e5d6 Mon Sep 17 00:00:00 2001 From: Adityo Dwijananto Date: Thu, 10 Oct 2019 11:24:42 +0700 Subject: [PATCH] Formatting --- .../06_Menggunakan_to_do_list_di_JOSM.md | 5 +- ...embuatan_Batas_Administrasi_dengan_JOSM.md | 628 +++++++++--------- ...ngatasi_Konflik_pada_Data_OpenStreetMap.md | 288 ++++---- ...an_Kualitas_Data_dengan_Tasking_Manager.md | 4 +- .../01_Menggunakan_Export_Tool.md | 217 +++--- .../01_Metodologi_Kerangka_Kerja_Pemetaan.md | 455 +++++++------ .../02_Model_Data_OpenStreetMap.md | 2 +- .../03_Membuat_Presets_OpenStreetMap.md | 8 +- .../04-Penggunaan-YAML-pada-Export-Tool.md | 449 ++++++------- .../08_Membuat_MBTiles_untuk_OpenMapKit.md | 3 + ...tas-Data-Menggunakan-Plugin-Group-Stats.md | 451 ++++++------- .../10_Konversi_Data_Shapefile_ke_GeoJSON.md | 3 +- .../01_Integrasi_Data_OSM_ke_InAWARE.md | 102 +-- themes/book | 2 +- 14 files changed, 1315 insertions(+), 1302 deletions(-) rename content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/{01_Metodologi_Kerangka_Kerja_Pemetaan => 01-Metodologi-Kerangka-Kerja-Pemetaan-OpenStreetMap}/01_Metodologi_Kerangka_Kerja_Pemetaan.md (88%) diff --git a/content/en/pages/03-JOSM/06-Menggunakan-to-do-list-di-JOSM/06_Menggunakan_to_do_list_di_JOSM.md b/content/en/pages/03-JOSM/06-Menggunakan-to-do-list-di-JOSM/06_Menggunakan_to_do_list_di_JOSM.md index 06ea0da..9ea49cd 100644 --- a/content/en/pages/03-JOSM/06-Menggunakan-to-do-list-di-JOSM/06_Menggunakan_to_do_list_di_JOSM.md +++ b/content/en/pages/03-JOSM/06-Menggunakan-to-do-list-di-JOSM/06_Menggunakan_to_do_list_di_JOSM.md @@ -13,6 +13,7 @@ After conducting a survey using the OpenMapKit (OMK) application, the next step ### **I. Installing to-do list plugin in JOSM** Because the Todo list plugin is an additional tool in JOSM, you need to install the JOSM plugin first before using it. The steps to install the todo list plugin in JOSM are as follows: + * Click on the menu bar **Edit → Preferences** * The **Preferences** window will appear and select the **Plugins** menu to install the new plugin. If the plugins list has not yet appeared, you can click **Download list** and make sure your internet is connected to download the plugin. @@ -34,6 +35,7 @@ Because the Todo list plugin is an additional tool in JOSM, you need to install ### **II. Using to-do list** The steps to use the to-do list plugin are as follows: + * Firstly, you need to add all .osm files into that will be uploaded into JOSM. These .osm files contain survey point objects that have been exported from OpenMapKit (OMK). You should open the files by clicking **File → Open** on the menu bar. * Because one file contains only one point object, you need to combine all the layers into one layer. You can merge the files by selecting all the layers on the **Layers** panel then right-click and choose **Merge** option. You can select several layers at one time by clicking on one layer then hold to select all layers on the panel or simply click layers one by one by pressing the **Ctrl** key on your keyboard. @@ -46,7 +48,7 @@ The steps to use the to-do list plugin are as follows:

Add list objects into todo list panel

* To zoom in on one of the objects you want to work on, you can use the **Zoom** option in the Todo list panel or double-click on the object in the list. -* + ![Zoom in the objects through Todo list panel](/en/images/03-JOSM/06-Menggunakan-to-do-list-di-JOSM/0606_perbesar_objek.png)

Zoom in the objects through Todo list panel

@@ -67,5 +69,6 @@ The steps to use the to-do list plugin are as follows: **SUMMARY** + If you can follow and pay attention to all the stages in this chapter, then you have successfully installed the plugin in JOSM. In addition, you have also successfully learned and practiced how to operate the Todo list plugin in JOSM to facilitate your work. diff --git a/content/en/pages/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/09.Pembuatan_Batas_Administrasi_dengan_JOSM.md b/content/en/pages/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/09.Pembuatan_Batas_Administrasi_dengan_JOSM.md index f1b3b02..ac9239b 100644 --- a/content/en/pages/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/09.Pembuatan_Batas_Administrasi_dengan_JOSM.md +++ b/content/en/pages/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/09.Pembuatan_Batas_Administrasi_dengan_JOSM.md @@ -1,314 +1,314 @@ ---- -title: Creating the Administrative Boundaries in JOSM -weight: 9 ---- - -**Objectives:** - -* To be able to explain the definition and example of relation in OpenStreetMap -* To be able to explain administrative boundary concept in OpenStreetMap -* To be able to explain term and condition to create an administrative boundary in OpenStreetMap -* To be able to create the administrative boundaries in OpenStreetMap - -The mapping of administrative boundaries in OpenStreetMap was suggested to an advanced mapper or experienced user with regularly mapping in OpenStreetMap. You can obtain the administrative boundary by government which have authorized with the boundary. In the PDC InAWARE project, we are associated with village offices and university in the cities. Therefore, we can obtain the administrative boundaries data from village offices, they drawing the boundaries in the paper maps. - -The data source very important in administrative boundaries, you can not decide the boundary by yourself. If the data source is unclear and does not have an [Open Data Commons Open Database License](https://opendatacommons.org/licenses/odbl/) (ODbL), the data is not allowed to be uploaded into OSM. This can cause problems when other users download and use administrative boundary data freely for their benefit. - -### **I. Relation in OSM** - -A relation is a group of elements. To be more exact it is one of the core data elements that consists of one or more tags and also an ordered list of one or more nodes, ways and/or relations as members which is used to define logical or geographic relationships between other elements. A member of a relation can optionally have a role that describes the part that a particular feature plays within a relation. The types of relation the administrative boundary : - -**a. Relation Tags** - -Relation tags to the administrative boundary in Indonesia - -|Key|Value|Definition| -|--|--|--| -|admin_level|(1-11) Adjusted according to administrative boundaries|The admin_level key describes the administrative level of an object within a government hierarchy. A lower level means higher in the hierarchy. Besides others, this tag is used for the borders of territorial political entities (e.g. country, state, municipality) together with [boundary](https://wiki.openstreetmap.org/wiki/Key:boundary)=[administrative](https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative). Due to cultural and political differences, admin levels of different countries only correspond approximately to each other.| -|boundary|administrative|An administrative boundary. Subdivisions of areas/territories/jurisdictions recognized by governments or other organizations for administrative purposes.| -|type|boundary|This tag to identify the object in administrative boundary| -|name|Name of administrative level|This tag to identify the name in administrative boundary, example: RW 03, Candisari Village| -|place|Example suburb, island|This optional tag, used to indicate that a particular location is known by a particular name, to indicate what sort of "place" it is. A place tag should exist for every significant human settlement (city, town, suburb, etc.) and also for notable unpopulated, named places. [http://wiki.openstreetmap.org/wiki/Key:place](http://wiki.openstreetmap.org/wiki/Key:place)| -|land_area|administrative|Tags to identify a land area boundary| -|is_in:province|Name of province|Tags to identify the name of the province. This tag must be included in lower-level administrative from (City/Town, Municipality, Village, Community group, Neighborhood Unit)| -|**(City)** is_in:city, **(Town)** is_in:town|Name of City/Town|Tags to identify the name of the city/town. This tag must be included in lower-level administrative from City/Town ( Municipality, Village, Community group, Neighborhood Unit)| -|is_in:municipality|Name of Municipality|Tags to identify the name of the municipality. This tag must be included in lower-level administrative from Municipality (Village, Community group, Neighborhood Unit)| -|is_in:village|Name of Village|Tags to identify the name of the village. This tag must be included in administrative from Village (Community group, Neighborhood Unit)| -|is_in:RW|Name of Community group|Tags to identify the name of the community group. This tag must be included in lower-level administrative from Community group (Neighborhood Unit)| - -**b. Relation Members** - -* Admin_centre - -The point that represents the centre of administration in one area (a capital, county seat, etc.), usually a town, city or village (depending on the boundary level, see [place](https://wiki.openstreetmap.org/wiki/Key:place)=*). - -* Outer - - The multiple ways that form the closed border - -* Inner - - Enclaves of this border - the multiple ways that form the closed inner borders - -![Area C is inside Area A and Area C is identified as an inner of the relation members](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0901_relationmember.png)

Area C is inside Area A and Area C is identified as an inner of the relation members (https://wiki.openstreetmap.org/wiki/Main_Page)

- -### **II. Understanding Administrative Boundary in OSM** - - **a. Definition of Administrative Boundary** - - An administrative boundary. Subdivisions of areas/territories/jurisdictions recognized by governments or other organizations for administrative purposes. These range from large groups of nation-states right down to small administrative districts and suburbs, as indicated by the '[admin_level](https://wiki.openstreetmap.org/wiki/Key:admin_level)=*' combo tag. - -![Boundary Administrative in Petamburan](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0902_bataskelpetamburan.png) -

Boundary Administrative in Petamburan (openstreetmap.org)

- - **b. Admin_level values for specific countries** - - Admin_level=1 to 10 has been introduced in order that different borders can be rendered consistently among countries (doing this based on border_type would require knowledge of their hierarchy in each country). The lists of admin-level boundary for specific countries: - [http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative](http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative) or [https://tinyurl.com/wiki-batasadm](https://tinyurl.com/wiki-batasadm) - - **c. Admin_level values for Indonesia** - - The division of administrative boundaries in Indonesia is adjusted to the division of regions and divisions in Indonesia which are managed by regional governments based on the principles of autonomy, deconcentration, decentralization and co-administration tasks. The types of administrative boundaries that exist in Indonesia are Provinces, City/Town, Municipality, Village, Hamlet (only rural area), Community group, Neighborhood Unit. - -When the types of administrative boundaries in Indonesia are seen in OpenStreetMap, administrative boundaries have different values ​​according to the level of administration. The levels of administration in Indonesia is as follows: - -|**value**|**Admin Level**|**Example Rendering**|**Place**| -|---|---|---|---| -|1|-|-|-| -|2|Country|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0903_batasnegara.png)|-| -|3|-|-|-| -|4|Province|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0904_batasprovinsi.png)|Province| -|5|City/Town|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0905_bataskota.png)|Big City=City, Small City=Town| -|6|Municipality|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0906_bataskec.png)|Municipality| -|7|Village|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0907_bataskel.png)|Village| -|8|Hamlet|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0908_batasdusun.png)|Hamlet| -|9|Community Group|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0910_batasrtrw.png)|Community Group| -|10|Neighborhood Unit|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0911_batasrtrw.png)|Neighborhood Unit| - -### **III. Terms and Condition When Create Administrative Boundary in OSM** - -**a. Term and Condition to Mapper** - -As mentioned above, administrative boundaries are a sensitive topic to map. In order to avoid issues in the future, there are specific requirements when it comes to mapping administrative boundaries on OpenStreetMap, they are: - -* The mapper has learned the concept relation data in OSM especially for the relation of administrative boundary -* The mapper has learned about how to create the administrative boundary and concern the data source -* The mapper can explain the admin level of the administrative boundary in Indonesia - - **b. Term and Condition to Data Source** - - Term and condition to the data source of the administrative boundary in OSM: - -* Data must come from a reliable source, for example the Geospatial Information Agency (BIG) -* Data used must have a permission to use license, to ensure it is legal to be used for public use. -* Data must have clear administration boundaries, as legally acknowledged and approved by the concerned authorities. - -### **IV. Adding the Administrative Boundary in OSM** - -In making administrative borders, it is highly encouraged to use editor Java OpenStreetMap (JOSM) due to the complete tools available to edit and modify are much easier to use than other editors such as iD editor. - - -> **Note :** -Data used in this tutorial are fictitious data to easily help understand and practice creating administrative borders. - -Here are the steps in creating administrative boundaries on OpenStreetMap: - -**a. Drawing the Lines of Administrative Boundary** -* Open JOSM editor. -* Then, select that you will make administrative boundaries in, by downloading the OSM data of the specified area. -* If the OSM data has mapped such as buildings and roads, you can use the filter data in JOSM in referring to chapter **Using Filter in JOSM**. The tool filter helps to hide the building and road in OSM data. -* Starting to digitize with **Draw Node** - -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0912_drawtool.png) - -* The image below is an example of digitizing administrative boundaries. We will create three villages that connected in the administrative boundary, there are Desa A (Village A), Desa B (Village B), and Desa C (Village C). - -![Divide the area](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0913_relasidesa.png) -

Divide the area

- -* When drawing administrative boundaries, please consider the following: - * Drawing lines connects with other lines in administrative boundary - * Ensure that do not overlap lines in administrative boundary and drawn twice - * Ensure that every interconnected line is drawn its own separate line (in a different segment). If the lines look something like this: - -![The mistake of creating the relation](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0914_kesalahanrelasi.png) -

The mistake of creating the relation

- -You can separate the lines use **Tools → Split Way** or use the shortcut **(P)** in your keyboard with choosing two-node between lines that separated like this: - -![The split way in lines administrative](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0915_splitwaydesa.png) -

The split way in lines administrative

- -**b. Assigning Tags on Administrative Boundary Lines** - -* The next step is to assign a tag on each boundary line made Select one line in a segment from the administrative boundary. - -![Select line in administrative boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0916_pemilihangarisbatas.png) -

Choose line in administrative boundary

- -* Then, we will tag the lines with administrative boundary presets with click on **Presets Menu → Batas Administrasi → Garis Batas Administrasi**. If these presets not showing in your Menu Presets, please refer to the chapter **Using JOSM** for adding the “PDC InAWARE Indonesia preset”. It is only in Bahasa. - -![Menu Presets](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0917_presetsgaris.png) -

Menu Presets

- -* It will appear the dialog window that you can fill the name according to the name village between boundaries, such as Desa A / Desa B. This tag is intended to explain the line segments as administrative boundaries for Village A (Desa A) and Village B (Desa B). Then click on **Apply preset** to save the result. - -![The presets form Administrative Line](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0918_applygarisadm.png) -

The presets form Administrative Line

- -* You can see the properties of the tag in line with select the lines using **select tool** and see the information on the right side, like the image below: - -![Tagging in administrative line boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0919_taggarisadm.png) -

Tagging in administrative line boundary

- -* In the next step, we will tag on the segments in line administrative boundary Desa A. Select the segment in line between Desa A and Desa C. Tagging in the same way as before. - -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0920_desaac.png) - -![Tagging in administrative line boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0921_tagdesaac.png) -

Tagging in administrative line boundary

- -* This part of the tutorial will show how to make village/district administrative boundaries where the village/district are covers the entire mainland/island. In the image below, the red line is the boundary between Village A and the ocean. - ![The boundary administrative with coastline](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0922_bataslaut.png) -

The boundary administrative with coastline

- - In this case, the tag given is different, where you need to add **key=natural **and **value=coastline**, then remove for tag **key=note**. To add the tagging, click on** Menu Presets → Perairan → Natural → Garis Pantai**. - -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0923_presetsgarispantai.png) - -![The boundary between line and coastline](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0924_tagcoasline.png) -

The boundary between line and coastline

- -* After the segments have tagged in Desa A. Let’s draw a node as administrative centre from Desa A. - ![Digitize a node in Desa A](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0925_titikdesa.png) -

Digitize a node in Desa A

- -* Add the presets for the object with **Presets Menu → Batas Administrasi → Titik Pusat Administrasi**. Fill the properties with the village name according to the admin level. - -![Add tags in point of village](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0926_tagnamadesa.png) -

Add tags in point of village

- -* The result should be like this: - -![The result for the village name](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0927_namadesa.png) -

The result for the village name

- -**c. Create Relations Administrative Boundary (example: Desa/Village)** - -* Next step we will create a relation to the administrative boundary in Desa A. Use the **Select Tool **to select all segments in lines and node in the area Desa A**.** - -![Select all lines and point in Desa A](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0928_pilihgarisdesa.png) -

Select all lines and point in Desa A

- -* Add presets for the relations with click on **Presets Menu → Batas Administrasi → Wilayah Administrasi** - -![Presets for relation tag](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0929_wilayahadm.png) -

Presets for relation tag

- -* The preset window above should appear. Assign the administrative name (example: Village A), and on the boundary type column select Administrative, and on Administrative level column, select according to the level of administration (example: Village -. Level of Administration = 7). If you find the **sign** **v** in the row, please click on it and drop down the row. Click on **New relation** to create a new relation. - -![The list the relations tag administrative boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0930_isianrelasi.png) -

The list the relations tag administrative boundary

- -* A new relation window should appear: - -![New relation window](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0931_relasikel.png) -

New relation window

- -* Check on the Role. After relation member Desa A is complete, we can determine the **role** of each member. The line segments Desa A have a role as **“outer”** or an outline from the administrative boundary. Also, add the role to node Desa A with **“admin_centre”**. - -![The role of each member](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0932_roledesaA.png) -

The role of each member

- -* Ensure the member list of the administrative boundary in order. If it is not ordered, it looks like here: - -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0933_segmentidakurut.png) - - To organize the line segments, click the **Sort the relation members** icon -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0934_sortirtool.png) - -* After the line segments are in the correct order, the lines in the right hand side of the window should look like this: - -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0935_segmenurut.png) - -* After assigning the role of each relation as well ensuring the list of administrative boundaries are in order, click **OK.** -* Check on the geometry relation in the data layer with a double-click on the area Desa A. The right relation will be shown in purple color. - -![Relation of Desa A/Village A](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0936_wilayahdesaA.png) -

Relation of Desa A/Village A

- -* Please following step by step the same with before to create a relation of Desa B/Village B. If you are successful, the result like an image below: - -![Desa B Area](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0937_desaB.png) -

Desa B Area

- -* Add a new village in your relation boundary, we can named with Desa D/Village D. The village inside the area Desa C - -![Add new administrative boundary Desa D](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0938_desacd.png) -

Add new administrative boundary Desa D

- -* After assigning relation members of Village C, assign the roles of each relation members. -* Line segments of **the outer layer** of Village C (boundary lines between Village C/A, boundary lines between VIllage C/B, and boundary lines between Village C/Ocean) -> acts as the **“outer”** boundaries of the administrative area. -* Line segments of the **inner layer** of Village C (boundary lines between Village C/D) -> acts as the **“inner”** boundaries of the administrative area. -* Centre point of Village C -> assign as **“admin_centre”** - -![The setting of relation Desa C](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0939_relasidesac.png) -

The setting of relation Desa C

- -* Click on icon **Sort the relation members**, to ensure the list of relation members are in order -* Now Double-click in administrative boundary Desa C. If the relation has been made, the area of Desa C should appear purple color like below: -![The result of relation Desa C](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0940_hasilrelasic.png") -

The result of relation Desa C

- -* After creating administrative boundaries for Village C, continue creating boundaries for Village D. **Follow the same steps** from **Assigning Tags on Administrative Boundaries** until **Creating Relations of Administrative Boundaries.** The end result should look like this: - -![The result of relation Desa D](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0941_relasid.png) -

The result of relation Desa D

- -**d. Creating the relation of the administrative boundaries (example: Municipality)** - -* In this section, we will create a boundary in the up-level from the village. The step will be the same to create the relation of the village boundary. -* Let’s create a point of administrative centre in Kecamatan Kertamukti, and assign a tag: Click on **Preset Menu → Batas Administrasi → Titik Batas Administrasi** - -![Tagging on admin centre municipality](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0942_titikec.png) -

Tagging on admin centre municipality

- -* Select all segments in an administrative boundary to create a new relation. - -![Select all lines outer and node of municipality boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0943_selecallgaris.png) -

Select all lines outer and node of municipality boundary

- -* Add tagging with click on **Presets Menu → Batas Administrasi → Wilayah Administrasi**. Please fill the name of municipality, admin-level, and do not fill “Kecamatan” - -![The lists preset of municipality boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0944_relasikec.png) -

The lists preset of municipality boundary

- -* We will determine the role of relation members. All segments in Kertamukti municipality (Kecamatan Kertamukti) has a role as outer and the point of the municipality name has a role as admin_centre. - -![The role of relation member](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0945_rolekec.png) -

The role of relation member

- -* Ensure the member list of the administrative boundary in order. If it is not ordered, it looks like here: - -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0933_segmentidakurut.png) - - To create the segments in order, click on button **Sort the relation members** - -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0934_sortirtool.png) - -* If the member list of the administrative boundary in order, it looks like here: - -![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0935_segmenurut.png) - -* Click **OK**. -* If you need to create the administrative boundary in up-level such as the city and province, you can do the same ways. The different way to add tags on relations and admin centre. -* The result will appear in [www.openstreetmap.org](http://www.openstreetmap.org) - -![Example the administrative boundary in OSM](/id/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0946_hasilrelasiosm.png) -

Example the administrative boundary in OSM

- - -**SUMMARY** - -You have learned about activities to create administrative boundaries with relation concepts in JOSM. A relation is a group of elements. To be more exact, it is one of the core data elements that consists of one or more tags and also an ordered list of one or more nodes, ways and/or relations as members which is used to define logical or geographic relationships between other elements. You can download the administrative boundary in polygons using the Export Tool. - +--- +title: Creating the Administrative Boundaries in JOSM +weight: 9 +--- + +**Objectives:** + +* To be able to explain the definition and example of relation in OpenStreetMap +* To be able to explain administrative boundary concept in OpenStreetMap +* To be able to explain term and condition to create an administrative boundary in OpenStreetMap +* To be able to create the administrative boundaries in OpenStreetMap + +The mapping of administrative boundaries in OpenStreetMap was suggested to an advanced mapper or experienced user with regularly mapping in OpenStreetMap. You can obtain the administrative boundary by government which have authorized with the boundary. In the PDC InAWARE project, we are associated with village offices and university in the cities. Therefore, we can obtain the administrative boundaries data from village offices, they drawing the boundaries in the paper maps. + +The data source very important in administrative boundaries, you can not decide the boundary by yourself. If the data source is unclear and does not have an [Open Data Commons Open Database License](https://opendatacommons.org/licenses/odbl/) (ODbL), the data is not allowed to be uploaded into OSM. This can cause problems when other users download and use administrative boundary data freely for their benefit. + +### **I. Relation in OSM** + +A relation is a group of elements. To be more exact it is one of the core data elements that consists of one or more tags and also an ordered list of one or more nodes, ways and/or relations as members which is used to define logical or geographic relationships between other elements. A member of a relation can optionally have a role that describes the part that a particular feature plays within a relation. The types of relation the administrative boundary : + +**a. Relation Tags** + +Relation tags to the administrative boundary in Indonesia + +|Key|Value|Definition| +|---|---|---| +|admin_level|(1-11) Adjusted according to administrative boundaries|The admin_level key describes the administrative level of an object within a government hierarchy. A lower level means higher in the hierarchy. Besides others, this tag is used for the borders of territorial political entities (e.g. country, state, municipality) together with [boundary](https://wiki.openstreetmap.org/wiki/Key:boundary)=[administrative](https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative). Due to cultural and political differences, admin levels of different countries only correspond approximately to each other.| +|boundary|administrative|An administrative boundary. Subdivisions of areas/territories/jurisdictions recognized by governments or other organizations for administrative purposes.| +|type|boundary|This tag to identify the object in administrative boundary| +|name|Name of administrative level|This tag to identify the name in administrative boundary, example: RW 03, Candisari Village| +|place|Example suburb, island|This optional tag, used to indicate that a particular location is known by a particular name, to indicate what sort of "place" it is. A place tag should exist for every significant human settlement (city, town, suburb, etc.) and also for notable unpopulated, named places. [http://wiki.openstreetmap.org/wiki/Key:place](http://wiki.openstreetmap.org/wiki/Key:place)| +|land_area|administrative|Tags to identify a land area boundary| +|is_in:province|Name of province|Tags to identify the name of the province. This tag must be included in lower-level administrative from (City/Town, Municipality, Village, Community group, Neighborhood Unit)| +|**(City)** is_in:city, **(Town)** is_in:town|Name of City/Town|Tags to identify the name of the city/town. This tag must be included in lower-level administrative from City/Town ( Municipality, Village, Community group, Neighborhood Unit)| +|is_in:municipality|Name of Municipality|Tags to identify the name of the municipality. This tag must be included in lower-level administrative from Municipality (Village, Community group, Neighborhood Unit)| +|is_in:village|Name of Village|Tags to identify the name of the village. This tag must be included in administrative from Village (Community group, Neighborhood Unit)| +|is_in:RW|Name of Community group|Tags to identify the name of the community group. This tag must be included in lower-level administrative from Community group (Neighborhood Unit)| + +**b. Relation Members** + +* Admin_centre + +The point that represents the centre of administration in one area (a capital, county seat, etc.), usually a town, city or village (depending on the boundary level, see [place](https://wiki.openstreetmap.org/wiki/Key:place)=*). + +* Outer + + The multiple ways that form the closed border + +* Inner + + Enclaves of this border - the multiple ways that form the closed inner borders + +![Area C is inside Area A and Area C is identified as an inner of the relation members](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0901_relationmember.png)

Area C is inside Area A and Area C is identified as an inner of the relation members (https://wiki.openstreetmap.org/wiki/Main_Page)

+ +### **II. Understanding Administrative Boundary in OSM** + + **a. Definition of Administrative Boundary** + + An administrative boundary. Subdivisions of areas/territories/jurisdictions recognized by governments or other organizations for administrative purposes. These range from large groups of nation-states right down to small administrative districts and suburbs, as indicated by the '[admin_level](https://wiki.openstreetmap.org/wiki/Key:admin_level)=*' combo tag. + +![Boundary Administrative in Petamburan](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0902_bataskelpetamburan.png) +

Boundary Administrative in Petamburan (openstreetmap.org)

+ + **b. Admin_level values for specific countries** + + Admin_level=1 to 10 has been introduced in order that different borders can be rendered consistently among countries (doing this based on border_type would require knowledge of their hierarchy in each country). The lists of admin-level boundary for specific countries: + [http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative](http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative) or [https://tinyurl.com/wiki-batasadm](https://tinyurl.com/wiki-batasadm) + + **c. Admin_level values for Indonesia** + + The division of administrative boundaries in Indonesia is adjusted to the division of regions and divisions in Indonesia which are managed by regional governments based on the principles of autonomy, deconcentration, decentralization and co-administration tasks. The types of administrative boundaries that exist in Indonesia are Provinces, City/Town, Municipality, Village, Hamlet (only rural area), Community group, Neighborhood Unit. + +When the types of administrative boundaries in Indonesia are seen in OpenStreetMap, administrative boundaries have different values ​​according to the level of administration. The levels of administration in Indonesia is as follows: + +|**value**|**Admin Level**|**Example Rendering**|**Place**| +|---|---|---|---| +|1|-|-|-| +|2|Country|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0903_batasnegara.png)|-| +|3|-|-|-| +|4|Province|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0904_batasprovinsi.png)|Province| +|5|City/Town|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0905_bataskota.png)|Big City=City, Small City=Town| +|6|Municipality|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0906_bataskec.png)|Municipality| +|7|Village|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0907_bataskel.png)|Village| +|8|Hamlet|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0908_batasdusun.png)|Hamlet| +|9|Community Group|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0910_batasrtrw.png)|Community Group| +|10|Neighborhood Unit|![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0911_batasrtrw.png)|Neighborhood Unit| + +### **III. Terms and Condition When Create Administrative Boundary in OSM** + +**a. Term and Condition to Mapper** + +As mentioned above, administrative boundaries are a sensitive topic to map. In order to avoid issues in the future, there are specific requirements when it comes to mapping administrative boundaries on OpenStreetMap, they are: + +* The mapper has learned the concept relation data in OSM especially for the relation of administrative boundary +* The mapper has learned about how to create the administrative boundary and concern the data source +* The mapper can explain the admin level of the administrative boundary in Indonesia + + **b. Term and Condition to Data Source** + + Term and condition to the data source of the administrative boundary in OSM: + +* Data must come from a reliable source, for example the Geospatial Information Agency (BIG) +* Data used must have a permission to use license, to ensure it is legal to be used for public use. +* Data must have clear administration boundaries, as legally acknowledged and approved by the concerned authorities. + +### **IV. Adding the Administrative Boundary in OSM** + +In making administrative borders, it is highly encouraged to use editor Java OpenStreetMap (JOSM) due to the complete tools available to edit and modify are much easier to use than other editors such as iD editor. + + +> **Note :** +Data used in this tutorial are fictitious data to easily help understand and practice creating administrative borders. + +Here are the steps in creating administrative boundaries on OpenStreetMap: + +**a. Drawing the Lines of Administrative Boundary** +* Open JOSM editor. +* Then, select that you will make administrative boundaries in, by downloading the OSM data of the specified area. +* If the OSM data has mapped such as buildings and roads, you can use the filter data in JOSM in referring to chapter **Using Filter in JOSM**. The tool filter helps to hide the building and road in OSM data. +* Starting to digitize with **Draw Node** + +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0912_drawtool.png) + +* The image below is an example of digitizing administrative boundaries. We will create three villages that connected in the administrative boundary, there are Desa A (Village A), Desa B (Village B), and Desa C (Village C). + +![Divide the area](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0913_relasidesa.png) +

Divide the area

+ +* When drawing administrative boundaries, please consider the following: + * Drawing lines connects with other lines in administrative boundary + * Ensure that do not overlap lines in administrative boundary and drawn twice + * Ensure that every interconnected line is drawn its own separate line (in a different segment). If the lines look something like this: + +![The mistake of creating the relation](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0914_kesalahanrelasi.png) +

The mistake of creating the relation

+ +You can separate the lines use **Tools → Split Way** or use the shortcut **(P)** in your keyboard with choosing two-node between lines that separated like this: + +![The split way in lines administrative](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0915_splitwaydesa.png) +

The split way in lines administrative

+ +**b. Assigning Tags on Administrative Boundary Lines** + +* The next step is to assign a tag on each boundary line made Select one line in a segment from the administrative boundary. + +![Select line in administrative boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0916_pemilihangarisbatas.png) +

Choose line in administrative boundary

+ +* Then, we will tag the lines with administrative boundary presets with click on **Presets Menu → Batas Administrasi → Garis Batas Administrasi**. If these presets not showing in your Menu Presets, please refer to the chapter **Using JOSM** for adding the “PDC InAWARE Indonesia preset”. It is only in Bahasa. + +![Menu Presets](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0917_presetsgaris.png) +

Menu Presets

+ +* It will appear the dialog window that you can fill the name according to the name village between boundaries, such as Desa A / Desa B. This tag is intended to explain the line segments as administrative boundaries for Village A (Desa A) and Village B (Desa B). Then click on **Apply preset** to save the result. + +![The presets form Administrative Line](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0918_applygarisadm.png) +

The presets form Administrative Line

+ +* You can see the properties of the tag in line with select the lines using **select tool** and see the information on the right side, like the image below: + +![Tagging in administrative line boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0919_taggarisadm.png) +

Tagging in administrative line boundary

+ +* In the next step, we will tag on the segments in line administrative boundary Desa A. Select the segment in line between Desa A and Desa C. Tagging in the same way as before. + +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0920_desaac.png) + +![Tagging in administrative line boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0921_tagdesaac.png) +

Tagging in administrative line boundary

+ +* This part of the tutorial will show how to make village/district administrative boundaries where the village/district are covers the entire mainland/island. In the image below, the red line is the boundary between Village A and the ocean. + ![The boundary administrative with coastline](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0922_bataslaut.png) +

The boundary administrative with coastline

+ + In this case, the tag given is different, where you need to add **key=natural **and **value=coastline**, then remove for tag **key=note**. To add the tagging, click on** Menu Presets → Perairan → Natural → Garis Pantai**. + +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0923_presetsgarispantai.png) + +![The boundary between line and coastline](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0924_tagcoasline.png) +

The boundary between line and coastline

+ +* After the segments have tagged in Desa A. Let’s draw a node as administrative centre from Desa A. + ![Digitize a node in Desa A](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0925_titikdesa.png) +

Digitize a node in Desa A

+ +* Add the presets for the object with **Presets Menu → Batas Administrasi → Titik Pusat Administrasi**. Fill the properties with the village name according to the admin level. + +![Add tags in point of village](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0926_tagnamadesa.png) +

Add tags in point of village

+ +* The result should be like this: + +![The result for the village name](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0927_namadesa.png) +

The result for the village name

+ +**c. Create Relations Administrative Boundary (example: Desa/Village)** + +* Next step we will create a relation to the administrative boundary in Desa A. Use the **Select Tool **to select all segments in lines and node in the area Desa A**.** + +![Select all lines and point in Desa A](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0928_pilihgarisdesa.png) +

Select all lines and point in Desa A

+ +* Add presets for the relations with click on **Presets Menu → Batas Administrasi → Wilayah Administrasi** + +![Presets for relation tag](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0929_wilayahadm.png) +

Presets for relation tag

+ +* The preset window above should appear. Assign the administrative name (example: Village A), and on the boundary type column select Administrative, and on Administrative level column, select according to the level of administration (example: Village -. Level of Administration = 7). If you find the **sign** **v** in the row, please click on it and drop down the row. Click on **New relation** to create a new relation. + +![The list the relations tag administrative boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0930_isianrelasi.png) +

The list the relations tag administrative boundary

+ +* A new relation window should appear: + +![New relation window](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0931_relasikel.png) +

New relation window

+ +* Check on the Role. After relation member Desa A is complete, we can determine the **role** of each member. The line segments Desa A have a role as **“outer”** or an outline from the administrative boundary. Also, add the role to node Desa A with **“admin_centre”**. + +![The role of each member](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0932_roledesaA.png) +

The role of each member

+ +* Ensure the member list of the administrative boundary in order. If it is not ordered, it looks like here: + +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0933_segmentidakurut.png) + + To organize the line segments, click the **Sort the relation members** icon +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0934_sortirtool.png) + +* After the line segments are in the correct order, the lines in the right hand side of the window should look like this: + +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0935_segmenurut.png) + +* After assigning the role of each relation as well ensuring the list of administrative boundaries are in order, click **OK.** +* Check on the geometry relation in the data layer with a double-click on the area Desa A. The right relation will be shown in purple color. + +![Relation of Desa A/Village A](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0936_wilayahdesaA.png) +

Relation of Desa A/Village A

+ +* Please following step by step the same with before to create a relation of Desa B/Village B. If you are successful, the result like an image below: + +![Desa B Area](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0937_desaB.png) +

Desa B Area

+ +* Add a new village in your relation boundary, we can named with Desa D/Village D. The village inside the area Desa C + +![Add new administrative boundary Desa D](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0938_desacd.png) +

Add new administrative boundary Desa D

+ +* After assigning relation members of Village C, assign the roles of each relation members. +* Line segments of **the outer layer** of Village C (boundary lines between Village C/A, boundary lines between VIllage C/B, and boundary lines between Village C/Ocean) -> acts as the **“outer”** boundaries of the administrative area. +* Line segments of the **inner layer** of Village C (boundary lines between Village C/D) -> acts as the **“inner”** boundaries of the administrative area. +* Centre point of Village C -> assign as **“admin_centre”** + +![The setting of relation Desa C](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0939_relasidesac.png) +

The setting of relation Desa C

+ +* Click on icon **Sort the relation members**, to ensure the list of relation members are in order +* Now Double-click in administrative boundary Desa C. If the relation has been made, the area of Desa C should appear purple color like below: +![The result of relation Desa C](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0940_hasilrelasic.png") +

The result of relation Desa C

+ +* After creating administrative boundaries for Village C, continue creating boundaries for Village D. **Follow the same steps** from **Assigning Tags on Administrative Boundaries** until **Creating Relations of Administrative Boundaries.** The end result should look like this: + +![The result of relation Desa D](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0941_relasid.png) +

The result of relation Desa D

+ +**d. Creating the relation of the administrative boundaries (example: Municipality)** + +* In this section, we will create a boundary in the up-level from the village. The step will be the same to create the relation of the village boundary. +* Let’s create a point of administrative centre in Kecamatan Kertamukti, and assign a tag: Click on **Preset Menu → Batas Administrasi → Titik Batas Administrasi** + +![Tagging on admin centre municipality](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0942_titikec.png) +

Tagging on admin centre municipality

+ +* Select all segments in an administrative boundary to create a new relation. + +![Select all lines outer and node of municipality boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0943_selecallgaris.png) +

Select all lines outer and node of municipality boundary

+ +* Add tagging with click on **Presets Menu → Batas Administrasi → Wilayah Administrasi**. Please fill the name of municipality, admin-level, and do not fill “Kecamatan” + +![The lists preset of municipality boundary](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0944_relasikec.png) +

The lists preset of municipality boundary

+ +* We will determine the role of relation members. All segments in Kertamukti municipality (Kecamatan Kertamukti) has a role as outer and the point of the municipality name has a role as admin_centre. + +![The role of relation member](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0945_rolekec.png) +

The role of relation member

+ +* Ensure the member list of the administrative boundary in order. If it is not ordered, it looks like here: + +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0933_segmentidakurut.png) + + To create the segments in order, click on button **Sort the relation members** + +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0934_sortirtool.png) + +* If the member list of the administrative boundary in order, it looks like here: + +![](/en/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0935_segmenurut.png) + +* Click **OK**. +* If you need to create the administrative boundary in up-level such as the city and province, you can do the same ways. The different way to add tags on relations and admin centre. +* The result will appear in [www.openstreetmap.org](http://www.openstreetmap.org) + +![Example the administrative boundary in OSM](/id/images/03-JOSM/09-Pembuatan-Batas-Administrasi-dengan-JOSM/0946_hasilrelasiosm.png) +

Example the administrative boundary in OSM

+ + +**SUMMARY** + +You have learned about activities to create administrative boundaries with relation concepts in JOSM. A relation is a group of elements. To be more exact, it is one of the core data elements that consists of one or more tags and also an ordered list of one or more nodes, ways and/or relations as members which is used to define logical or geographic relationships between other elements. You can download the administrative boundary in polygons using the Export Tool. + diff --git a/content/en/pages/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/10_Mengatasi_Konflik_pada_Data_OpenStreetMap.md b/content/en/pages/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/10_Mengatasi_Konflik_pada_Data_OpenStreetMap.md index 1f192bb..8042cfa 100644 --- a/content/en/pages/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/10_Mengatasi_Konflik_pada_Data_OpenStreetMap.md +++ b/content/en/pages/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/10_Mengatasi_Konflik_pada_Data_OpenStreetMap.md @@ -1,145 +1,145 @@ ---- -title: Resolving Conflict on OpenStreetMap Data (OSM) -weight: 10 ---- - -**Objectives:** - -* Participants can explain what is data conflict on OpenStreetMap -* Participants knowing about types of conflict in JOSM -* Participants can fix data conflicts using JOSM -* Participants know to avoid data conflict in JOSM - -When you are uploading your changes in JSOM, some contributors might also do editing in your area. This might occur data conflict in your uploading process. Therefore, in this module, you will learn about data conflict in OpenStreetMap, types of conflict, and how to fix it using JOSM. - -### **I. Data Conflict on OpenStreetMap** - -When you have edited your changes and were uploading them in JOSM (learn more about this in **Using JOSM** module), maybe you ever received a message like this: - -![Example of Conflict Detection Window in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1001_conflict.png) -

Example of Conflict Detection Window in JOSM

- -The picture above shows data conflict in OSM. Why that could possibly happen? This conflict happens because when you edit your data in JOSM, you edit the same data/object(s) with the other contributor in the same time. Thus, the other contributor have uploaded the changes first and have received by OSM server. After that, you also want to upload the same data/object(s) with your own changes. Therefore, your changes will automatically rejected by the server because it causes confusion. - -You will face with data conflict when you do changes in JOSM such as editing, adding, or delet some objects in OpenStreetMap, while the other contributor also do the same thing on the objects. The other contributor has uploaded their changes slightly before you. Therefore, when you try to upload your changes, it causes confusion for the OSM Server because it does not know which changes is correct and can be saved. If this happens, then the data conflict need to be fixed before you can continue to upload your changes into OSM server. - -![Example why conflict happens in JOSMExample why conflict happens in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1002_ilustrasi_konflik.png) -

Example why conflict happens in JOSM

- -The picture above is example of conflict that could happen because of different position with the object between your version (my version) and version of the other contributor / have received by server (their version). To resolve this conflict, you have to choose one version between them (look chapter **III. Fixing Data Conflict in JOSM**). - -### **II. Types of Data Conflict in JOSM** - -**a. Conflict of Properties** - -Conflict of properties happens when an object(s) has been moved or deleted so one or more of its node has different location/position than the other version. - -![Conflict Property Window](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1003_konflik_properti.png) -

Conflict Property Window

- -The picture above is an example of conflict of properties in JOSM. As can be seen in the picture, in My Version the object has square shape and in the other version (their version) one of the node is deleted then change its shape become triangle. To fixed this, you need to choose which version that correct based on the location of the different nodes in both version. - -**b. Conflict of Tag** - -Conflict of tag happens because there are different information (tag) on on the object that has been edited by two or more contributors. The information could be deleted or changed on the other version. - -![Conflict of Tag in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1004_konflik_tag.png) -

Conflict of Tag in JOSM

- - -The picture above shows differences between two versions on the same object in JOSM. **_My version_** has Rumah Sakit _tag_ (_amenity = hospital_) with its name value is Rumah Sakit Tebet Raya while the other version (**_Their version_**) has tag klinik (_amenity = clinic_) with name RS Tebet Timur. You have to choose one of them that you think has correct information to fix it before upload it to the server. - - -**c. Conflict of Node** - -This conflict happens when there are differences order of the nodes in a way or closedway object(s) which have been removed or moved on one of the versions and has been uploaded to the OSM server. - -![Conflict of Nodes in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1005_konflik_node.png) -

Conflict of Nodes in JOSM

- -### **III. Fix Conflict Data in JOSM** - -Fixing conflict data in JOSM is quite simple, even though most OSM contributors would have some confusion to do it. Generally, every data conflict fixing in JOSM asks you to choose the correct changes between your version and the other version that have uploaded to the server (their version). You have to choose whether to **keep your version** or delete you version and **use their version**. Steps to fix conflict data in JOSM as follows: - -* When the conflict window appears, you might be only want to select the **Synchronize node 5,960,126 only** option. However, this option will only fix conflict in one certain nodes. Instead, you should choose **Synchronize entire dataset** option so you can resolve all conflict nodes in one time. - -![Conflict Detection Window in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1006_kotak_konflik.png) -

Conflict Detection Window in JOSM

- -* After that, JOSM will show how many conflicts that has been detected, Click **_OK_**. - -![Number of detected conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1007_conflict_detected.png) -

Number of detected conflict

- -* There is a list of conflicts in **Conflict** panel at bottom right corner in your JOSM. You can choose which conflict you want to fix and click **_Resolve_**. - -![Conflict panel to fix detected conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1008_panel_conflict.png) -

Conflict panel to fix detected conflict

- -* When you have click the **_Resolve_** button, the window will appears and shows detail about detected conflict. The message about conflict might be looks complicated but it actually has simple instruction. You will know about what type of conflict do you have by looking at ![](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1009_simbol.png) symbol. Therefore, the conflict in this example was caused by different coordinate location and position of object. You can look at a list of changed or moved coordinate as shown in picture below. Thus, conflict in this example was caused by one changed node. - -![A Window to Resolve Conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1010_penyelesaian_konflik.png) -

A Window to Resolve Conflict

- -* You only can resolve one conflicts at one time. You can choose which correct version between your version or their version in the server. If you sure that your version is the correct one (you edit / add the object based on your field survey mapping or you already know the object personally), then choose **My Version (local dataset)**. However, if you are not sure about your version and think that the other version more convincing then you can choose **Their version (server dataset)**. Click blue arrow symbol in the version that you choose. If the conflict has been fixed then the symbol will be going turn to green check mark![](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1012_ikon_konflik_selesai.png) - - -![Choose one of the versions to resolve data conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1013_tahap_penyelesaian.png) -

Choose one of the versions to resolve data conflict

- -* After you have select the right version, you have to make sure the color of conflict box has been changed from pink to green. This means you have successfully fixed the conflict. - -![Difference color between original conflict and resolved conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1014_perbedaan_warna.png) -

Difference color between original conflict and resolved conflict

- -* Then click **_Apply Resolution_** as shown in the picture above. After you have finished all of your conflict, you can start to upload your OSM changes. - -![Resolved conflict window](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1015_apply_resolution.png) -

Resolved conflict window

- -* In window menu, you can activate **Conflicts**![](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1016_ikon_konflik.png) window. This window shows total number of conflict on all of your data when you click the **_Resolve_** button. You also can use another way by right click on one of the conflict and choose **_Resolve to my versions_** or **_Resolve to their versions._** To find the object you can right click and click **_Zoom to Conflict_**. This will be very useful if you have many conflicts and need to check and fix them one by one. - -![Window of list conflict on JOSM_](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1017_zoom_conflict.png) -

Window of list conflict on JOSM_

- ->Note : -You can not upload your changes until you have resolved all of your conflict and list of conflict in the conflict window has empty. Keep in mind, you need to be careful when resolving the conflict and need to check it one by one to make sure everything is correct as it should. - -### **IV. Avoiding Data Conflict in JOSM** - -You can do some things to avoid conflict when uploading your data into OSM server, as follows: - -**a. Upload your changes continuously** - -* To minimize conflict, you can upload your changes continuously. For instance, if you mapped 100 buildings but does not have a good internet connection, you should upload your changes for every 20 buildings or every 15 minutes. The reason for this is because the conflict would have bigger possibility to occur if you upload when it is finished. The longer you waiting to upload the more possibility the data could possibly have edited and uploaded to the server by other contributors. Therefore, the probability of conflict for your edit will increase. - -* If you want to save your OSM data and upload it later, you can update your OSM data first before you upload it. This should be done so you can get the latest OSM data from the server before you upload it. You can do that by click **_File → Update data_** or **_Update Modified_** then waiting until the updating process is finished. After that, you can upload your changes with **_Upload data_** options **_File_** menu or just click -![](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1018_ikon_upload.png)icon on _menu_ bar. - - -![Update data options in file menu](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1019_update_data.png) -

Update data options in file menu

- - -**b. Edit Only in Downloaded Area** - -You can do mapping in specific area to minimize risk of conflict with avoid editing objects outside your downloaded area in JOSM. This can prevent two or more users editing in same area. Notice that diagonal lines around your downloaded area is an area you need to avoid to edit in JOSM. - -![Downloaded Area (black) dan Outside Downloaded Area (diagonal lines)](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1020_perbedaan_area_download.png) -

Downloaded Area (black) dan Outside Downloaded Area (diagonal lines)

- -After you download the data, your editing area is only area inside which does not have diagonal lines. The area outside you editing area most likely currently editing or have been edited by other contributors. Avoid edit in the area will reduce the risk of getting conflict in your data. - -**c. Using _Tasking Manager_** - -If you want to do collaborative mapping, you can use _Tasking Manager_. It will help you to divide your mapping area into task grids. Thus, you can choose your mapping area grid easily without worry getting same area with other OSM contributors because once you select certain grid, it will be locked and cannot choose by other contributors. - - -Any mapping volunteer in the area can choose one grid that they want and after finish they can mark the grid as completed mapped. This will allow a lot of people to map certain area in same time without getting worried to get conflict. You can read how to use _Tasking Manager_ in **Using[ Tasking Manager](https://docs.google.com/document/d/1vi9wnbM1fS76bK9k4KhHRVHo0pwdA7zQeUpcKTLfKYo/edit) **module**.** - -![Tasking Manager Interface (tasks.openstreetmap.id)](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1021_tasking_manager.png) -

Tasking Manager Interface (tasks.openstreetmap.id)

- -**Summary** - +--- +title: Resolving Conflict on OpenStreetMap Data (OSM) +weight: 10 +--- + +**Objectives:** + +* Participants can explain what is data conflict on OpenStreetMap +* Participants knowing about types of conflict in JOSM +* Participants can fix data conflicts using JOSM +* Participants know to avoid data conflict in JOSM + +When you are uploading your changes in JSOM, some contributors might also do editing in your area. This might occur data conflict in your uploading process. Therefore, in this module, you will learn about data conflict in OpenStreetMap, types of conflict, and how to fix it using JOSM. + +### **I. Data Conflict on OpenStreetMap** + +When you have edited your changes and were uploading them in JOSM (learn more about this in **Using JOSM** module), maybe you ever received a message like this: + +![Example of Conflict Detection Window in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1001_conflict.png) +

Example of Conflict Detection Window in JOSM

+ +The picture above shows data conflict in OSM. Why that could possibly happen? This conflict happens because when you edit your data in JOSM, you edit the same data/object(s) with the other contributor in the same time. Thus, the other contributor have uploaded the changes first and have received by OSM server. After that, you also want to upload the same data/object(s) with your own changes. Therefore, your changes will automatically rejected by the server because it causes confusion. + +You will face with data conflict when you do changes in JOSM such as editing, adding, or delet some objects in OpenStreetMap, while the other contributor also do the same thing on the objects. The other contributor has uploaded their changes slightly before you. Therefore, when you try to upload your changes, it causes confusion for the OSM Server because it does not know which changes is correct and can be saved. If this happens, then the data conflict need to be fixed before you can continue to upload your changes into OSM server. + +![Example why conflict happens in JOSMExample why conflict happens in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1002_ilustrasi_konflik.png) +

Example why conflict happens in JOSM

+ +The picture above is example of conflict that could happen because of different position with the object between your version (my version) and version of the other contributor / have received by server (their version). To resolve this conflict, you have to choose one version between them (look chapter **III. Fixing Data Conflict in JOSM**). + +### **II. Types of Data Conflict in JOSM** + +**a. Conflict of Properties** + +Conflict of properties happens when an object(s) has been moved or deleted so one or more of its node has different location/position than the other version. + +![Conflict Property Window](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1003_konflik_properti.png) +

Conflict Property Window

+ +The picture above is an example of conflict of properties in JOSM. As can be seen in the picture, in My Version the object has square shape and in the other version (their version) one of the node is deleted then change its shape become triangle. To fixed this, you need to choose which version that correct based on the location of the different nodes in both version. + +**b. Conflict of Tag** + +Conflict of tag happens because there are different information (tag) on on the object that has been edited by two or more contributors. The information could be deleted or changed on the other version. + +![Conflict of Tag in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1004_konflik_tag.png) +

Conflict of Tag in JOSM

+ + +The picture above shows differences between two versions on the same object in JOSM. **_My version_** has Rumah Sakit _tag_ (_amenity = hospital_) with its name value is Rumah Sakit Tebet Raya while the other version (**_Their version_**) has tag klinik (_amenity = clinic_) with name RS Tebet Timur. You have to choose one of them that you think has correct information to fix it before upload it to the server. + + +**c. Conflict of Node** + +This conflict happens when there are differences order of the nodes in a way or closedway object(s) which have been removed or moved on one of the versions and has been uploaded to the OSM server. + +![Conflict of Nodes in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1005_konflik_node.png) +

Conflict of Nodes in JOSM

+ +### **III. Fix Conflict Data in JOSM** + +Fixing conflict data in JOSM is quite simple, even though most OSM contributors would have some confusion to do it. Generally, every data conflict fixing in JOSM asks you to choose the correct changes between your version and the other version that have uploaded to the server (their version). You have to choose whether to **keep your version** or delete you version and **use their version**. Steps to fix conflict data in JOSM as follows: + +* When the conflict window appears, you might be only want to select the **Synchronize node 5,960,126 only** option. However, this option will only fix conflict in one certain nodes. Instead, you should choose **Synchronize entire dataset** option so you can resolve all conflict nodes in one time. + +![Conflict Detection Window in JOSM](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1006_kotak_konflik.png) +

Conflict Detection Window in JOSM

+ +* After that, JOSM will show how many conflicts that has been detected, Click **_OK_**. + +![Number of detected conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1007_conflict_detected.png) +

Number of detected conflict

+ +* There is a list of conflicts in **Conflict** panel at bottom right corner in your JOSM. You can choose which conflict you want to fix and click **_Resolve_**. + +![Conflict panel to fix detected conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1008_panel_conflict.png) +

Conflict panel to fix detected conflict

+ +* When you have click the **_Resolve_** button, the window will appears and shows detail about detected conflict. The message about conflict might be looks complicated but it actually has simple instruction. You will know about what type of conflict do you have by looking at ![](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1009_simbol.png) symbol. Therefore, the conflict in this example was caused by different coordinate location and position of object. You can look at a list of changed or moved coordinate as shown in picture below. Thus, conflict in this example was caused by one changed node. + +![A Window to Resolve Conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1010_penyelesaian_konflik.png) +

A Window to Resolve Conflict

+ +* You only can resolve one conflicts at one time. You can choose which correct version between your version or their version in the server. If you sure that your version is the correct one (you edit / add the object based on your field survey mapping or you already know the object personally), then choose **My Version (local dataset)**. However, if you are not sure about your version and think that the other version more convincing then you can choose **Their version (server dataset)**. Click blue arrow symbol in the version that you choose. If the conflict has been fixed then the symbol will be going turn to green check mark![](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1012_ikon_konflik_selesai.png) + + +![Choose one of the versions to resolve data conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1013_tahap_penyelesaian.png) +

Choose one of the versions to resolve data conflict

+ +* After you have select the right version, you have to make sure the color of conflict box has been changed from pink to green. This means you have successfully fixed the conflict. + +![Difference color between original conflict and resolved conflict](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1014_perbedaan_warna.png) +

Difference color between original conflict and resolved conflict

+ +* Then click **_Apply Resolution_** as shown in the picture above. After you have finished all of your conflict, you can start to upload your OSM changes. + +![Resolved conflict window](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1015_apply_resolution.png) +

Resolved conflict window

+ +* In window menu, you can activate **Conflicts**![](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1016_ikon_konflik.png) window. This window shows total number of conflict on all of your data when you click the **_Resolve_** button. You also can use another way by right click on one of the conflict and choose **_Resolve to my versions_** or **_Resolve to their versions._** To find the object you can right click and click **_Zoom to Conflict_**. This will be very useful if you have many conflicts and need to check and fix them one by one. + +![Window of list conflict on JOSM_](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1017_zoom_conflict.png) +

Window of list conflict on JOSM_

+ +>Note : +You can not upload your changes until you have resolved all of your conflict and list of conflict in the conflict window has empty. Keep in mind, you need to be careful when resolving the conflict and need to check it one by one to make sure everything is correct as it should. + +### **IV. Avoiding Data Conflict in JOSM** + +You can do some things to avoid conflict when uploading your data into OSM server, as follows: + +**a. Upload your changes continuously** + +* To minimize conflict, you can upload your changes continuously. For instance, if you mapped 100 buildings but does not have a good internet connection, you should upload your changes for every 20 buildings or every 15 minutes. The reason for this is because the conflict would have bigger possibility to occur if you upload when it is finished. The longer you waiting to upload the more possibility the data could possibly have edited and uploaded to the server by other contributors. Therefore, the probability of conflict for your edit will increase. + +* If you want to save your OSM data and upload it later, you can update your OSM data first before you upload it. This should be done so you can get the latest OSM data from the server before you upload it. You can do that by click **_File → Update data_** or **_Update Modified_** then waiting until the updating process is finished. After that, you can upload your changes with **_Upload data_** options **_File_** menu or just click +![](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1018_ikon_upload.png)icon on _menu_ bar. + + +![Update data options in file menu](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1019_update_data.png) +

Update data options in file menu

+ + +**b. Edit Only in Downloaded Area** + +You can do mapping in specific area to minimize risk of conflict with avoid editing objects outside your downloaded area in JOSM. This can prevent two or more users editing in same area. Notice that diagonal lines around your downloaded area is an area you need to avoid to edit in JOSM. + +![Downloaded Area (black) dan Outside Downloaded Area (diagonal lines)](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1020_perbedaan_area_download.png) +

Downloaded Area (black) dan Outside Downloaded Area (diagonal lines)

+ +After you download the data, your editing area is only area inside which does not have diagonal lines. The area outside you editing area most likely currently editing or have been edited by other contributors. Avoid edit in the area will reduce the risk of getting conflict in your data. + +**c. Using _Tasking Manager_** + +If you want to do collaborative mapping, you can use _Tasking Manager_. It will help you to divide your mapping area into task grids. Thus, you can choose your mapping area grid easily without worry getting same area with other OSM contributors because once you select certain grid, it will be locked and cannot choose by other contributors. + + +Any mapping volunteer in the area can choose one grid that they want and after finish they can mark the grid as completed mapped. This will allow a lot of people to map certain area in same time without getting worried to get conflict. You can read how to use _Tasking Manager_ in **Using[ Tasking Manager](https://docs.google.com/document/d/1vi9wnbM1fS76bK9k4KhHRVHo0pwdA7zQeUpcKTLfKYo/edit) module.** + +![Tasking Manager Interface (tasks.openstreetmap.id)](/en/images/03-JOSM/10-Mengatasi-konflik-data-pada-OpenStreetMap/1021_tasking_manager.png) +

Tasking Manager Interface (tasks.openstreetmap.id)

+ +**Summary** + If you have followed and finished to practice all the steps in this chapter, You have successfully understand about data conflict in JOSM and how to fix it. Moreover, you also have learned about types of conflict and how to avoid them in JOSM. Congratulations! \ No newline at end of file diff --git a/content/en/pages/04-Data-Validation-and-Quality-Assurance/03-Penjaminan-Kualitas-Data-dengan-Tasking-Manager/03_Penjaminan_Kualitas_Data_dengan_Tasking_Manager.md b/content/en/pages/04-Data-Validation-and-Quality-Assurance/03-Penjaminan-Kualitas-Data-dengan-Tasking-Manager/03_Penjaminan_Kualitas_Data_dengan_Tasking_Manager.md index 4cdf0e1..89434bf 100644 --- a/content/en/pages/04-Data-Validation-and-Quality-Assurance/03-Penjaminan-Kualitas-Data-dengan-Tasking-Manager/03_Penjaminan_Kualitas_Data_dengan_Tasking_Manager.md +++ b/content/en/pages/04-Data-Validation-and-Quality-Assurance/03-Penjaminan-Kualitas-Data-dengan-Tasking-Manager/03_Penjaminan_Kualitas_Data_dengan_Tasking_Manager.md @@ -63,7 +63,7 @@ How to validating using tasking manager is similarly with editing with tasking m

General information about the tasking

-* If you scroll down, you will see the **Instructions. **Above the instructions there are four tabs, one of them is validate. You can start validation by click **Validate**. Besides by click validate, at the bottom there is a question box **"Ready to get started?"** with the Map and Validate options, please choose **Validate**. +* If you scroll down, you will see the **Instructions.** Above the instructions there are four tabs, one of them is validate. You can start validation by click **Validate**. Besides by click validate, at the bottom there is a question box **"Ready to get started?"** with the Map and Validate options, please choose **Validate**. ![Option to start validation](/en/images/04-Data-Validation-and-Quality-Assurance/03-Penjaminan-Kualitas-Data-dengan-Tasking-Manager/0308_Pilihan_untuk_memulai_validasi.png)

Option to start validation

@@ -116,7 +116,7 @@ How to validating using tasking manager is similarly with editing with tasking m **b. Things to Watch When Do Validation in Tasking Manager** -When you do validation using tasking manager_ _there are things to watch, that is the time limit for working on the box you have chosen. If you have started validation, there is a time limit for working on the tasking you selected at the top like the picture below: +When you do validation using tasking manager there are things to watch, that is the time limit for working on the box you have chosen. If you have started validation, there is a time limit for working on the tasking you selected at the top like the picture below: ![Time limit for validation](/en/images/04-Data-Validation-and-Quality-Assurance/03-Penjaminan-Kualitas-Data-dengan-Tasking-Manager/0314_Contoh_batas_waktu_untuk_validasi.png) diff --git a/content/en/pages/05-HOT-Export/01-Penggunaan-Export-Tool/01_Menggunakan_Export_Tool.md b/content/en/pages/05-HOT-Export/01-Penggunaan-Export-Tool/01_Menggunakan_Export_Tool.md index dd7514d..e01a209 100644 --- a/content/en/pages/05-HOT-Export/01-Penggunaan-Export-Tool/01_Menggunakan_Export_Tool.md +++ b/content/en/pages/05-HOT-Export/01-Penggunaan-Export-Tool/01_Menggunakan_Export_Tool.md @@ -1,108 +1,109 @@ ---- -title: Download OSM Data using Export Tool -weight: 1 ---- - - -**Objectives:** - -* To be able to explain the definition and function of Export Tools -* To be able to operate Export Tools - -In this chapter, we can learn about how to download the OSM data that we have added and uploaded into OSM. The data can be used to analysis, customize with data symbology, create maps, and others depend on your necessary. - -### **I. Export Tool Concept** - -The Export Tool is an open service that creates customized extracts of up-to-date OSM data in various file formats, such as ESRI shapefiles (.shapefile), google KML (.kml), GeoPackage (.gpkg) dan MBTiles (.mbtiles). We can select the area and specific categories that we necessary. Download and use the data simply by crediting the **© OpenStreetMap contributors**. Anyone can create a custom OpenStreetMap export with the Export Tool - just register an account. You can register with an OpenStreetMap account from [OpenStreetMap.org](https://openstreetmap.org/) and a valid email address. - -### **II. How to using Export Tool** - -**a. Login with OSM account** -* Open your browser, and type this link https://export.hotosm.org - -![The interface of Export Tool](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0101_tampilanexporttool.png) -

The interface of Export Tool

- -* The first we have login with your OSM account to using Export Tool. Click on **Login** in the right corner. The next click on ‘Authorize access to your account’ → **Grant Access**. -* To create a new project in Export Tool click on **Start Exporting** -* The Export Tool window will be displayed like the image below - -![The fill from Export Tool](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0102_lembarkerjaet.png) -

The fill from Export Tool

- -**b. Defining an area of interest** - -There are 5 ways to define an Area of Interest for your export: - -1. **Bounding Box: **Use the "Box" tool to the right to click and drag a rectangle, or use the "Current View" tool to match the map's viewport. - -![Bounding box](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0103_Penentuan_Area_dengan_Kotak.png) -

Bounding box

- -2. **Draw Polygon:** Draw a freeform polygon. This must be a simple (not multi-) polygon. - -![Manually edit](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0104_penentuan_manual.png) -

Manually edit

- -3. **Upload:** By uploading a GeoJSON polygon in WGS84 (geographic) coordinates. If you have not the GeoJSON data, you can refer to this chapter **Using GeoJSON**. - - -![Import the administrative boundary](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0105_penentuangeojson.png) -

Import the administrative boundary

- -4. **Search Bar:** input a minX,minY,maxX,maxY string into the search bar. This will define a rectangular area of interest. - -5. **Current View:** Use "Current View" to match the map's viewport. - -The maximum extent of export on the Export Tool is determined by the density of OSM data in the defined area. **The bounding box of the area can contain at most 10,000,000 OSM nodes. **This limitation means that a 10,000 square kilometer box over a heavily mapped area like Western Europe or North America will likely be rejected, but an equal-sized box over a sparsely mapped area will be accepted by the Export Tool. If you need larger exports, please Contact Us or use an alternative resource such as downloads from [Geofabrik](http://download.geofabrik.de/) or [Mapzen](https://mapzen.com/data/metro-extracts/). - -**c. Naming and Describing your Export** - -* **Name (required):** choose a short, descriptive name. -* **Description:** a long text body, perhaps describing what relevant features the export includes. -* **Project:** Helps to group together exports particular to a project, e.g. "PDC InAWARE Indonesia” - -**d. Choosing File Format** - -* Check at least one file format to export. To learn more about each individual format, read the documentation: [Export Formats](https://export.hotosm.org/en/v3/learn/export_formats) - -![Spatial data](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0106_menuformat.png) -

Spatial data

- - -**e. Choosing Map Features** - -* For your first time using the export tool, it's recommended to use the Tag Tree, which curates a set of filters and tags for common map features. As an example, check the box "**Buildings and Transportation → Roads**" to create an export of all building geometries, as well as related data such as name and address keys. - -![Select the object in export Tool](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0107_buildingandroads.png) -

Select the object in export Tool

- -**f. Downloading your File** - -* The last step is the Summary Menu that will be displayed about the projects. Click the **Create Export** to starting the process - -![menu summary](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0108_menusummary.png) -

Menu Summary

- -* After you submit your export using **Create Export**, you will be redirected to the **Export Detail Page**, which shows a list of **Export Runs**. You will see the first run at the top of the page. It will be in one of the following states: - - **Submitted:** The export is waiting to be processed. This should be brief, depending on the server load. - - - **Running:** The export is waiting to be processed. City-sized regions should be a few minutes - larger regions can take upwards of 20 minutes, depending on the density of OSM data. - - - **Completed:** Your export files are available for download. Each export format has a separate download link for its ZIP archive. - -![menu export](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0109_menuexporttool.png) -

Menu Exports

- -* If the status will be **COMPLETED**, we can download the data with a click on **buildings_and-roads-bali-upate.shp.zip** and save in your directory. - -![Completed Process](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0110_selesaiexport.png) -

Completed Process

- - -**SUMMARY** - -We have learned about how to download the OSM data using Export Tool. We can open the data in the mapping software as for example QGIS ([www.qgis.org](http://www.qgis.org)). You also can use the data to calculate the quantities of infrastructures. +--- +title: Download OSM Data using Export Tool +weight: 1 +--- + + +**Objectives:** + +* To be able to explain the definition and function of Export Tools +* To be able to operate Export Tools + +In this chapter, we can learn about how to download the OSM data that we have added and uploaded into OSM. The data can be used to analysis, customize with data symbology, create maps, and others depend on your necessary. + +### **I. Export Tool Concept** + +The Export Tool is an open service that creates customized extracts of up-to-date OSM data in various file formats, such as ESRI shapefiles (.shapefile), google KML (.kml), GeoPackage (.gpkg) dan MBTiles (.mbtiles). We can select the area and specific categories that we necessary. Download and use the data simply by crediting the **© OpenStreetMap contributors**. Anyone can create a custom OpenStreetMap export with the Export Tool - just register an account. You can register with an OpenStreetMap account from [OpenStreetMap.org](https://openstreetmap.org/) and a valid email address. + +### **II. How to using Export Tool** + +**a. Login with OSM account** + +* Open your browser, and type this link https://export.hotosm.org + +![The interface of Export Tool](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0101_tampilanexporttool.png) +

The interface of Export Tool

+ +* The first we have login with your OSM account to using Export Tool. Click on **Login** in the right corner. The next click on ‘Authorize access to your account’ → **Grant Access**. +* To create a new project in Export Tool click on **Start Exporting** +* The Export Tool window will be displayed like the image below + +![The fill from Export Tool](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0102_lembarkerjaet.png) +

The fill from Export Tool

+ +**b. Defining an area of interest** + +There are 5 ways to define an Area of Interest for your export: + +1. **Bounding Box:** Use the "Box" tool to the right to click and drag a rectangle, or use the "Current View" tool to match the map's viewport. + + ![Bounding box](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0103_Penentuan_Area_dengan_Kotak.png) +

Bounding box

+ +2. **Draw Polygon:** Draw a freeform polygon. This must be a simple (not multi-polygon). + + ![Manually edit](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0104_penentuan_manual.png) +

Manually edit

+ +3. **Upload:** By uploading a GeoJSON polygon in WGS84 (geographic) coordinates. If you have not the GeoJSON data, you can refer to this chapter **Using GeoJSON**. + + + ![Import the administrative boundary](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0105_penentuangeojson.png) +

Import the administrative boundary

+ +4. **Search Bar:** input a minX,minY,maxX,maxY string into the search bar. This will define a rectangular area of interest. + +5. **Current View:** Use "Current View" to match the map's viewport. + + The maximum extent of export on the Export Tool is determined by the density of OSM data in the defined area. **The bounding box of the area can contain at most 10,000,000 OSM nodes.** This limitation means that a 10,000 square kilometer box over a heavily mapped area like Western Europe or North America will likely be rejected, but an equal-sized box over a sparsely mapped area will be accepted by the Export Tool. If you need larger exports, please Contact Us or use an alternative resource such as downloads from [Geofabrik](http://download.geofabrik.de/) or [Mapzen](https://mapzen.com/data/metro-extracts/). + +**c. Naming and Describing your Export** + +* **Name (required):** choose a short, descriptive name. +* **Description:** a long text body, perhaps describing what relevant features the export includes. +* **Project:** Helps to group together exports particular to a project, e.g. "PDC InAWARE Indonesia” + +**d. Choosing File Format** + +* Check at least one file format to export. To learn more about each individual format, read the documentation: [Export Formats](https://export.hotosm.org/en/v3/learn/export_formats) + +![Spatial data](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0106_menuformat.png) +

Spatial data

+ + +**e. Choosing Map Features** + +* For your first time using the export tool, it's recommended to use the Tag Tree, which curates a set of filters and tags for common map features. As an example, check the box "**Buildings and Transportation → Roads**" to create an export of all building geometries, as well as related data such as name and address keys. + +![Select the object in export Tool](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0107_buildingandroads.png) +

Select the object in export Tool

+ +**f. Downloading your File** + +* The last step is the Summary Menu that will be displayed about the projects. Click the **Create Export** to starting the process + +![menu summary](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0108_menusummary.png) +

Menu Summary

+ +* After you submit your export using **Create Export**, you will be redirected to the **Export Detail Page**, which shows a list of **Export Runs**. You will see the first run at the top of the page. It will be in one of the following states: + + **Submitted:** The export is waiting to be processed. This should be brief, depending on the server load. + + + **Running:** The export is waiting to be processed. City-sized regions should be a few minutes - larger regions can take upwards of 20 minutes, depending on the density of OSM data. + + + **Completed:** Your export files are available for download. Each export format has a separate download link for its ZIP archive. + +![menu export](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0109_menuexporttool.png) +

Menu Exports

+ +* If the status will be **COMPLETED**, we can download the data with a click on **buildings_and-roads-bali-upate.shp.zip** and save in your directory. + +![Completed Process](/en/images/05-HOT-Export/01-Penggunaan-Export-Tool/0110_selesaiexport.png) +

Completed Process

+ + +**SUMMARY** + +We have learned about how to download the OSM data using Export Tool. We can open the data in the mapping software as for example QGIS ([www.qgis.org](http://www.qgis.org)). You also can use the data to calculate the quantities of infrastructures. diff --git a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/01_Metodologi_Kerangka_Kerja_Pemetaan.md b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/01-Metodologi-Kerangka-Kerja-Pemetaan-OpenStreetMap/01_Metodologi_Kerangka_Kerja_Pemetaan.md similarity index 88% rename from content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/01_Metodologi_Kerangka_Kerja_Pemetaan.md rename to content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/01-Metodologi-Kerangka-Kerja-Pemetaan-OpenStreetMap/01_Metodologi_Kerangka_Kerja_Pemetaan.md index d1c4a8e..72484a3 100644 --- a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/01_Metodologi_Kerangka_Kerja_Pemetaan.md +++ b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/01-Metodologi-Kerangka-Kerja-Pemetaan-OpenStreetMap/01_Metodologi_Kerangka_Kerja_Pemetaan.md @@ -1,229 +1,226 @@ ---- -title: The Mapping Methodology with OpenStreetMap -weight: 1 ---- - -**Objectives:** - -* To be able to explain how to create a timeline for mapping activity -* To be able to explain how to create a folder for each team mapping -* To be able to explain how to divide the survey area based on the administrative boundary -* To be able to explain how to create team mapping effectively - -Planning a mapping project requires an appropriate and efficient survey methodology to achieve the target and purpose. Indicators that need to be considered in making survey methodologies include: survey area, number of team mapping, number of objects collected, and project funding. If the area is larger and the number of objects collected is increasing, the funding of the project will also increase. - -The mapping project will be carried out by a team mapping divided into 3 (three) roles: - - - -* Mapping Supervisor = organize, manage and supervise mapping projects, prepare equipment field surveys, create a report the survey progress, and check the quality and the quantity of data that validated by Quality Assurance -* Quality Assurance = Validate the quality and the quantity of data from data entry and manage a team of data entry -* Data Entry = Collect the object from field survey and entry the data to OSM. Also, digitize the buildings and roads - -### **I. Create a Framework for Mapping Activity** - -We will create a framework for a mapping project that integrates with indicators. The framework can reference in the implementation of the mapping project that will be monitored by Mapping Supervisor and Quality Assurance. These are the guideline of the framework: - -* Preparing the mapping projects -* Determine the team mapping of data entry and quality assurance -* OSM Training to team mapping -* Mapping process and mapathon activity -* QGIS Training for the staff mapping -* Creating the final maps - -An example, this image below is arranged as a framework for mapping in Semarang City. Semarang City has 373,8 km2 area with 16 data entry and 4 quality assurance. The infrastructures were collected 58 categories consists of roads, rivers, embankment, and public facilities. The mapping project has finished for 6 months. - -![The mapping framework](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0101_Kerangka_kerja_pemetaan.png) -

The mapping framework

- -**a. OSM and QGIS Training for Team Mapping** - - The training to explain about mapping methodology, using tools of field survey, and creating final maps. These are training material that you have to prepare before starting the project: - -* OSM Basic Training for Data Entry and Quality Assurance - - The training was held for three days with the purpose to use tools of field survey and how to input OSM data. - - - These are the training material: - -1. Getting started with OSM -2. Using JOSM -3. Using Tools Field Survey -4. Field Survey Mapping -5. Using Tasking Manager -6. Adding OSM Data using JOSM -7. Creating the administrative boundary using JOSM -8. Download OSM Data with Export Tool - -* Quality Data Training for Quality Assurance - - The training was held for two days that the purpose of validated OSM data by results data entry. The training material in lists below: - -1. Validation OSM Data using JOSM -2. Validation OSM Data using Tasking Manager -* QGIS Training for Data Entry and Quality Assurance - - The training was held for one day that the purpose to create the final maps. The training material in lists below: - -1. Download dan Install QGIS -2. Preparing the data -3. Create Final Map Using Map Composer - - **b. Preparing the Mapathon Activity** - - - A mapathon is a coordinated mapping event using a Tasking Manager. The public is invited to make online map improvements in their local area to improve coverage and to help disaster risk assessment and energy management. Mapathons use an online site for storing map data, for example, OpenStreetMap. A mapathon is organized by a respective organization or a non-profit organization or local government. - - Mapathons are often held inside (armchair mapping) in a room with strong Wi-Fi for simultaneous access, assisted by satellite imagery. We can collaborate with local universities to conduct the mapathon. We are usually conducting the mapathon in three days, involve one-day training and two days mapping. - - -### **II. Create a Timeline for Mapping Activity** - -Mapping timeline is different from the framework, in this section you will be focused on manage and oversee the implementation of a field survey. In outline, mapping timeline divide into three-part: - - -**a. Before Field Survey** - - In this part, the mapping supervisor has to prepare survey equipment. The survey equipment consists of GPS, smartphone, and maps. Each smartphone will be installed by open source android application, there are ODK Collect, OpenMapKit (OMK), and OSMTrackers. The lists task of mapping activities before field survey that mapping supervisor do: - -* Create the MBTiles with base map imagery -* Create maps with administrative boundary -* Create guideline to mapping activity - - Example Table for monitory the mapping activities before field survey - -| No | Timeline | Data Entry | Municipality | Total of Villages | Village Name | Total RW | MBTiles | Maps (imagery) | Maps (OSM) | -|---|---|---|---|---|---|---|---|---|---| -|1| Feb - Mar| A | Candisari | 3 | Candi | 11 | v | v | v | -|| | |100% Dipetakan | | Jatingaleh | 10 | v | v | v | -|| | |100% Divalidasi | | Jomblang | 10 | v | v | v | -|2| Feb - Mar| B | Banyumanik | 3 | Sumurboto | 5 | v | v | v | -|| | |100% Dipetakan | | Ngesrep | 11 | v | v | v | -|| | |100% Divalidasi | | Gedawang | 10 | v | v | v | -_*Filled by Mapping Supervisor_ - -**b. Mapping** - -Every mapping staff has a role in the implementation field survey. There are parts of roles: - -* Data Entry = prepare the smartphone, collect the objects, input the survey data, and upload in OSM, digitize buildings and roads, and create the final maps. -* Quality Assurance = ensure and manage the quality of data uploaded by data entry, monitory mapping activity in field, and manage the mapping strategy with data entry. -* Mapping Supervisor = ensure the quality and quantity of survey data, monitory whole implementation the mapping activity adjusted to timeline. - -Example Table on Mapping Process - - -|mbtiles|clear file manager|Survey|Getting RW Boundary|Survey Infrastructure|Shelters|Route|Upload track|Send form|Objects|RW|Shelters and Route|Validation| -|---|---|---|---|---|---|---|---|---|---|---|---|---| -| v | v | 1,5-6 Mar 2018 | 1 Mar 2018 | v | v | x | v | v | v | v | v | 26 Mar 2018 | -| v | v | 12 Feb 2018 | 12 Feb 2018 | v | v | x | v | v | v | v | v | 14, 19 Feb 2018 | -| v | v | 8,12-14 Mar 2018 | 12 Mar 2018 | v | v | x | v | v | v | v | v | 27-28 Mar 2018 | - - -**c. After Mapping Activity** - -If the mapping activities have finished, mapping supervisor and quality assurance have to ensure whole the survey data will be uploaded into OSM and validated. The next step is to create and prepare final maps for feedback to the government that involved in the mapping process. - -Example of the table after mapping activity - -|**Validate the admin boundary**|**Data Quantity**|**Data Quality**|**Print and Distribute the final maps**| -|---|---|---|---| -| v | v | v | v | -| v | v | v | v | -| v | v | v | v | - -You can download the complete table in this link [https://tinyurl.com/timeline-pemetaan](https://tinyurl.com/timeline-pemetaan) - -### **III. Save and Share the Survey Data** - -We need the folder directory to save and share the data that folder will be organized and easy to share. The results of the mapping project are spatial data uploaded in OpenStreetMap. The data can be downloaded and saved in other format spatial data with your necessary. - -We can upload and publish the data using Google Drive because everyone has a Gmail account and we usually use Google Drive in working. There is the example folder that we can use to save the data: - -Example Folder in Google Drive - -|**Folder Name**|**Description**| -|---|---| -|Timeline| Framework and table of the timeline the mapping activity| -|Training| Training agenda and training material| -|Staff Mapping| Profile of staff mapping (data entry, quality assurance, and mapping supervisor)| -|Data Survey| The results of mapping consist of OMK Data, ODK Collect Data, GPS Tracks, and final data| -|Documentation| Photos and videos of mapping activity| -|Maps| Maps of survey, progress, final results| -|Report| The monthly report to mapping activities| -|Data Quality|The results of calculating the data quality| -|Data Quantity| The results of calculating the data quantity| -|OMK Equipment| MBTiles of base map imagery| - -The digital data will be uploaded in each folder according to the mapping process so that we get the backup data and avoid losing the data. - -![The folder in Google Drive](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0102_Contoh_folder_Google_Drive.png) -

-

The folder in Google Drive

- -### **IV. Divide the Area Survey based on the Administrative Boundary** - -We will determine the factors that affect in divide the area survey it was related to characteristics area. The characteristics are an area, topography, and land use. We can divide the area based on village-level the administrative boundary. In the next step, we can start the analysis to divide the area by identifying the characteristics of the village-level. - -In this case, mapping in Semarang City has 373,8 km2 area in 16 sub-districts and 177 villages. Semarang City has a unique topography, it is a hill in South Semarang and coastal area in North Semarang. The North area is the central government, business, and residential area. While the south Semarang is the development of residential, education, and farmland. Therefore, the north Semarang has many infrastructures and a high density than the south Semarang area. - -The analysis topography can affect route the field survey because each region has obstacles area. The other factor is the weather on the implementation field survey, rain season can be a challenge in flood areas. If heavy rain, we can directive the data entry to survey in a location not flood affected or they can digitize buildings and roads in the office. - -If we already know about the factors that impact the mapping timeline, we can divide the area survey based on the administrative boundary. For example, one sub-district can be finished in a month by one team data entry. Based on the analysis, the mapping project in Semarang City has finished in four-month with 16 data entry. - -We can start the mapping area with nearby form the office because it is easy to coordinate between data entry and quality assurance about field survey. If data entry found the problem in the field likely problem with their smartphone or permission letter in the village office, they can ask the quality assurance or back to the office and resolve the problem with the team. - -![Mapping Timeline in Semarang City](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0103_peta_timeline.png) -

Mapping Timeline in Semarang City

- -In the map below, we can divide the area into two sections based on characteristics area, so that we need two mapping supervisor to manage and monitory the mapping activities - -![Divide Area in Mapping Project](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0104_peta_survey.png) -

Divide Area in Mapping Project

- -Example Table of Divide Area Survey - -|**Timeline**|**Sub-District**|**Mapping Supervisor North**|**Mapping Supervisor South**| -|---|---|---|---| -|Stage 1 (1,5 Months)|Near from the office less distance 20 km|Semarang Barat|Candisari| -|| |Semarang Tengah|Semarang Selatan| -|| |Semarang Timur|Gayamsari| -|| |Semarang Utara|Gajah Mungkur| -|Stage 2 (2,5 Months)|The distance more than 20 km from the office|Ngaliyan|Banyumanik| -|| |Pedurungan|Tembalang| -|| |Tugu|Mijen| -|| |Genuk|Gunung Pati| - -### **V. Create Team Mapping** - -We will choose the team data entry based on their knowledge about the area, it is a strategy to quickly in the understanding survey area. We can give the list question about the area in the recruitment process data entry. - -![Team Mapping](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0105_bagan_kelompok.png) -

Team Mapping

- -Example table of Team Mapping based on Survey Area - -|**Mapping Supervisor**|**Quality Assurance**|**Data Entry**|**Sub-districts**|**Village**|**Total Villages**| -|---|---|---|---|---|---| -|**Mapping Supervisor 1**| QA1 | DE1 | Candisari | 7 | 21 | -| | | DE2 | Mijen | 14 | | -| | | DE3 | Semarang Selatan | 10 | | -| | | DE4 | Banyumanik | 11 | | -| | QA2 | DE5 | Gayamsari | 7 | 23 | -| | | DE6 | Gunung Pati | 16 | | -| | | DE7 | Gajah Mungkur | 8 | 20 | -| | | DE8 | Tembalang | 12 | | -|**Mapping Supervisor 2**| QA3 | DE9 | Semarang Barat | 16 | 23 | -| | | DE10 | Tugu | 7 | | -| | | DE11 | Semarang Tengah | 15 | 25 | -| | | DE12 | Ngaliyan | 10 | | -| | QA4 | DE13 | Semarang Timur | 10 | 23 | -| | | DE14 | Genuk | 13 | | -| | | DE15 | Semarang Utara | 9 | 21 | -| | | DE16 | Pedurungan | 12 | | - - -**SUMMARY** - -If you can follow the instructions whole the process in this chapter, you have succeeded in creating the planning of mapping projects, create the methodology, divide the area, and create the team mapping. You can implement this process into your mapping project. If we can create appropriate methodology in the mapping project, you can reach the best results in good qualities and quantities of data. +--- +title: The Mapping Methodology with OpenStreetMap +weight: 1 +--- + +**Objectives:** + +* To be able to explain how to create a timeline for mapping activity +* To be able to explain how to create a folder for each team mapping +* To be able to explain how to divide the survey area based on the administrative boundary +* To be able to explain how to create team mapping effectively + +Planning a mapping project requires an appropriate and efficient survey methodology to achieve the target and purpose. Indicators that need to be considered in making survey methodologies include: survey area, number of team mapping, number of objects collected, and project funding. If the area is larger and the number of objects collected is increasing, the funding of the project will also increase. + +The mapping project will be carried out by a team mapping divided into 3 (three) roles: + + + +* Mapping Supervisor = organize, manage and supervise mapping projects, prepare equipment field surveys, create a report the survey progress, and check the quality and the quantity of data that validated by Quality Assurance +* Quality Assurance = Validate the quality and the quantity of data from data entry and manage a team of data entry +* Data Entry = Collect the object from field survey and entry the data to OSM. Also, digitize the buildings and roads + +### **I. Create a Framework for Mapping Activity** + +We will create a framework for a mapping project that integrates with indicators. The framework can reference in the implementation of the mapping project that will be monitored by Mapping Supervisor and Quality Assurance. These are the guideline of the framework: + +* Preparing the mapping projects +* Determine the team mapping of data entry and quality assurance +* OSM Training to team mapping +* Mapping process and mapathon activity +* QGIS Training for the staff mapping +* Creating the final maps + +An example, this image below is arranged as a framework for mapping in Semarang City. Semarang City has 373,8 km2 area with 16 data entry and 4 quality assurance. The infrastructures were collected 58 categories consists of roads, rivers, embankment, and public facilities. The mapping project has finished for 6 months. + +![The mapping framework](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0101_Kerangka_kerja_pemetaan.png) +

The mapping framework

+ +**a. OSM and QGIS Training for Team Mapping** + + The training to explain about mapping methodology, using tools of field survey, and creating final maps. These are training material that you have to prepare before starting the project: + +* OSM Basic Training for Data Entry and Quality Assurance + + The training was held for three days with the purpose to use tools of field survey and how to input OSM data. These are the training material: + + 1. Getting started with OSM + 2. Using JOSM + 3. Using Tools Field Survey + 4. Field Survey Mapping + 1. Using Tasking Manager + 2. Adding OSM Data using JOSM + 3. Creating the administrative boundary using JOSM + 4. Download OSM Data with Export Tool + +* Quality Data Training for Quality Assurance + + The training was held for two days that the purpose of validated OSM data by results data entry. The training material in lists below: + + 1. Validation OSM Data using JOSM + 2. Validation OSM Data using Tasking Manager + +* QGIS Training for Data Entry and Quality Assurance + + The training was held for one day that the purpose to create the final maps. The training material in lists below: + + 1. Download dan Install QGIS + 2. Preparing the data + 3. Create Final Map Using Map Composer + +**b. Preparing the Mapathon Activity** + +A mapathon is a coordinated mapping event using a Tasking Manager. The public is invited to make online map improvements in their local area to improve coverage and to help disaster risk assessment and energy management. Mapathons use an online site for storing map data, for example, OpenStreetMap. A mapathon is organized by a respective organization or a non-profit organization or local government. + +Mapathons are often held inside (armchair mapping) in a room with strong Wi-Fi for simultaneous access, assisted by satellite imagery. We can collaborate with local universities to conduct the mapathon. We are usually conducting the mapathon in three days, involve one-day training and two days mapping. + + +### **II. Create a Timeline for Mapping Activity** + +Mapping timeline is different from the framework, in this section you will be focused on manage and oversee the implementation of a field survey. In outline, mapping timeline divide into three-part: + + +**a. Before Field Survey** + + In this part, the mapping supervisor has to prepare survey equipment. The survey equipment consists of GPS, smartphone, and maps. Each smartphone will be installed by open source android application, there are ODK Collect, OpenMapKit (OMK), and OSMTrackers. The lists task of mapping activities before field survey that mapping supervisor do: + +* Create the MBTiles with base map imagery +* Create maps with administrative boundary +* Create guideline to mapping activity + + Example Table for monitory the mapping activities before field survey + +| No | Timeline | Data Entry | Municipality | Total of Villages | Village Name | Total RW | MBTiles | Maps (imagery) | Maps (OSM) | +|---|---|---|---|---|---|---|---|---|---| +|1| Feb - Mar| A | Candisari | 3 | Candi | 11 | v | v | v | +|| | |100% Dipetakan | | Jatingaleh | 10 | v | v | v | +|| | |100% Divalidasi | | Jomblang | 10 | v | v | v | +|2| Feb - Mar| B | Banyumanik | 3 | Sumurboto | 5 | v | v | v | +|| | |100% Dipetakan | | Ngesrep | 11 | v | v | v | +|| | |100% Divalidasi | | Gedawang | 10 | v | v | v | +_*Filled by Mapping Supervisor_ + +**b. Mapping** + +Every mapping staff has a role in the implementation field survey. There are parts of roles: + +* Data Entry = prepare the smartphone, collect the objects, input the survey data, and upload in OSM, digitize buildings and roads, and create the final maps. +* Quality Assurance = ensure and manage the quality of data uploaded by data entry, monitory mapping activity in field, and manage the mapping strategy with data entry. +* Mapping Supervisor = ensure the quality and quantity of survey data, monitory whole implementation the mapping activity adjusted to timeline. + +Example Table on Mapping Process + + +|mbtiles|clear file manager|Survey|Getting RW Boundary|Survey Infrastructure|Shelters|Route|Upload track|Send form|Objects|RW|Shelters and Route|Validation| +|---|---|---|---|---|---|---|---|---|---|---|---|---| +| v | v | 1,5-6 Mar 2018 | 1 Mar 2018 | v | v | x | v | v | v | v | v | 26 Mar 2018 | +| v | v | 12 Feb 2018 | 12 Feb 2018 | v | v | x | v | v | v | v | v | 14, 19 Feb 2018 | +| v | v | 8,12-14 Mar 2018 | 12 Mar 2018 | v | v | x | v | v | v | v | v | 27-28 Mar 2018 | + + +**c. After Mapping Activity** + +If the mapping activities have finished, mapping supervisor and quality assurance have to ensure whole the survey data will be uploaded into OSM and validated. The next step is to create and prepare final maps for feedback to the government that involved in the mapping process. + +Example of the table after mapping activity + +|**Validate the admin boundary**|**Data Quantity**|**Data Quality**|**Print and Distribute the final maps**| +|---|---|---|---| +| v | v | v | v | +| v | v | v | v | +| v | v | v | v | + +You can download the complete table in this link [https://tinyurl.com/timeline-pemetaan](https://tinyurl.com/timeline-pemetaan) + +### **III. Save and Share the Survey Data** + +We need the folder directory to save and share the data that folder will be organized and easy to share. The results of the mapping project are spatial data uploaded in OpenStreetMap. The data can be downloaded and saved in other format spatial data with your necessary. + +We can upload and publish the data using Google Drive because everyone has a Gmail account and we usually use Google Drive in working. There is the example folder that we can use to save the data: + +Example Folder in Google Drive + +|**Folder Name**|**Description**| +|---|---| +|Timeline| Framework and table of the timeline the mapping activity| +|Training| Training agenda and training material| +|Staff Mapping| Profile of staff mapping (data entry, quality assurance, and mapping supervisor)| +|Data Survey| The results of mapping consist of OMK Data, ODK Collect Data, GPS Tracks, and final data| +|Documentation| Photos and videos of mapping activity| +|Maps| Maps of survey, progress, final results| +|Report| The monthly report to mapping activities| +|Data Quality|The results of calculating the data quality| +|Data Quantity| The results of calculating the data quantity| +|OMK Equipment| MBTiles of base map imagery| + +The digital data will be uploaded in each folder according to the mapping process so that we get the backup data and avoid losing the data. + +![The folder in Google Drive](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0102_Contoh_folder_Google_Drive.png) +

+

The folder in Google Drive

+ +### **IV. Divide the Area Survey based on the Administrative Boundary** + +We will determine the factors that affect in divide the area survey it was related to characteristics area. The characteristics are an area, topography, and land use. We can divide the area based on village-level the administrative boundary. In the next step, we can start the analysis to divide the area by identifying the characteristics of the village-level. + +In this case, mapping in Semarang City has 373,8 km2 area in 16 sub-districts and 177 villages. Semarang City has a unique topography, it is a hill in South Semarang and coastal area in North Semarang. The North area is the central government, business, and residential area. While the south Semarang is the development of residential, education, and farmland. Therefore, the north Semarang has many infrastructures and a high density than the south Semarang area. + +The analysis topography can affect route the field survey because each region has obstacles area. The other factor is the weather on the implementation field survey, rain season can be a challenge in flood areas. If heavy rain, we can directive the data entry to survey in a location not flood affected or they can digitize buildings and roads in the office. + +If we already know about the factors that impact the mapping timeline, we can divide the area survey based on the administrative boundary. For example, one sub-district can be finished in a month by one team data entry. Based on the analysis, the mapping project in Semarang City has finished in four-month with 16 data entry. + +We can start the mapping area with nearby form the office because it is easy to coordinate between data entry and quality assurance about field survey. If data entry found the problem in the field likely problem with their smartphone or permission letter in the village office, they can ask the quality assurance or back to the office and resolve the problem with the team. + +![Mapping Timeline in Semarang City](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0103_peta_timeline.png) +

Mapping Timeline in Semarang City

+ +In the map below, we can divide the area into two sections based on characteristics area, so that we need two mapping supervisor to manage and monitory the mapping activities + +![Divide Area in Mapping Project](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0104_peta_survey.png) +

Divide Area in Mapping Project

+ +Example Table of Divide Area Survey + +|**Timeline**|**Sub-District**|**Mapping Supervisor North**|**Mapping Supervisor South**| +|---|---|---|---| +|Stage 1 (1,5 Months)|Near from the office less distance 20 km|Semarang Barat|Candisari| +|| |Semarang Tengah|Semarang Selatan| +|| |Semarang Timur|Gayamsari| +|| |Semarang Utara|Gajah Mungkur| +|Stage 2 (2,5 Months)|The distance more than 20 km from the office|Ngaliyan|Banyumanik| +|| |Pedurungan|Tembalang| +|| |Tugu|Mijen| +|| |Genuk|Gunung Pati| + +### **V. Create Team Mapping** + +We will choose the team data entry based on their knowledge about the area, it is a strategy to quickly in the understanding survey area. We can give the list question about the area in the recruitment process data entry. + +![Team Mapping](/en/images/06-OSM-Field-Survey-Manager-Guidelines/01_Metodologi_Kerangka_Kerja_Pemetaan/0105_bagan_kelompok.png) +

Team Mapping

+ +Example table of Team Mapping based on Survey Area + +|**Mapping Supervisor**|**Quality Assurance**|**Data Entry**|**Sub-districts**|**Village**|**Total Villages**| +|---|---|---|---|---|---| +|**Mapping Supervisor 1**| QA1 | DE1 | Candisari | 7 | 21 | +| | | DE2 | Mijen | 14 | | +| | | DE3 | Semarang Selatan | 10 | | +| | | DE4 | Banyumanik | 11 | | +| | QA2 | DE5 | Gayamsari | 7 | 23 | +| | | DE6 | Gunung Pati | 16 | | +| | | DE7 | Gajah Mungkur | 8 | 20 | +| | | DE8 | Tembalang | 12 | | +|**Mapping Supervisor 2**| QA3 | DE9 | Semarang Barat | 16 | 23 | +| | | DE10 | Tugu | 7 | | +| | | DE11 | Semarang Tengah | 15 | 25 | +| | | DE12 | Ngaliyan | 10 | | +| | QA4 | DE13 | Semarang Timur | 10 | 23 | +| | | DE14 | Genuk | 13 | | +| | | DE15 | Semarang Utara | 9 | 21 | +| | | DE16 | Pedurungan | 12 | | + + +**SUMMARY** + +If you can follow the instructions whole the process in this chapter, you have succeeded in creating the planning of mapping projects, create the methodology, divide the area, and create the team mapping. You can implement this process into your mapping project. If we can create appropriate methodology in the mapping project, you can reach the best results in good qualities and quantities of data. diff --git a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/02-Model-Data-OpenStreetMap/02_Model_Data_OpenStreetMap.md b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/02-Model-Data-OpenStreetMap/02_Model_Data_OpenStreetMap.md index f9f0155..2cf7b90 100644 --- a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/02-Model-Data-OpenStreetMap/02_Model_Data_OpenStreetMap.md +++ b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/02-Model-Data-OpenStreetMap/02_Model_Data_OpenStreetMap.md @@ -195,7 +195,7 @@ The purpose of HOT-PDC InAWARE mapping project is to gather information of criti **Color Information:** * Blue color means the _key_ and _value_ are compulsory for the object. -* Red color means the _key _and _value _are information for building of the object. This tag /information only collected if the object has its own building. Otherwise, the tag is unnecessary. +* Red color means the _key_ and _value_ are information for building of the object. This tag /information only collected if the object has its own building. Otherwise, the tag is unnecessary. * Black color means the _key_ and _value_ **should be** added regardless the object has its own building or not. **1.Economic Facilities** diff --git a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/03-Membuat-Presets-OpenStreetMap/03_Membuat_Presets_OpenStreetMap.md b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/03-Membuat-Presets-OpenStreetMap/03_Membuat_Presets_OpenStreetMap.md index 6301d50..5ab7bac 100644 --- a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/03-Membuat-Presets-OpenStreetMap/03_Membuat_Presets_OpenStreetMap.md +++ b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/03-Membuat-Presets-OpenStreetMap/03_Membuat_Presets_OpenStreetMap.md @@ -11,7 +11,7 @@ weight: 3 * To be able to comprehend presets concept on OpenStreetMap * To be able to comprehend XML format to create presets on OpenStreetMap * To be able to create a customized presets on OpenStreetMap -* To be able to comprehend presets’_ _elements +* To be able to comprehend presets elements As explained before, OpenStreetMap is a free, open, participatory map of the whole world. This means that the use of OpenStreetMap can be very distinctive. The more distinct the mapping objectives are, the more diverse the information are. The needs of various information made OpenStreetMap user come to an agreement to standardize the information added into OpenStreetMap. This standardized information is called Tag. To learn more about Tag, please refer to **OpenStreetMap Model Data** module. @@ -81,11 +81,11 @@ This is an example of a presets XML file: ### **III. Creating Customized Presets** -To be able to create your own presets, there are several things you need to prepare first. You need to install additional software to create XML file. One of the software to create XML file is **Notepad ++ **which can be downloaded at [https://notepad-plus-plus.org/download/v7.6.3.html](https://notepad-plus-plus.org/download/v7.6.3.html). After downloading it, install the software. You also need to learn about the principle of making OSM presets, like: +To be able to create your own presets, there are several things you need to prepare first. You need to install additional software to create XML file. One of the software to create XML file is **Notepad ++** which can be downloaded at [https://notepad-plus-plus.org/download/v7.6.3.html](https://notepad-plus-plus.org/download/v7.6.3.html). After downloading it, install the software. You also need to learn about the principle of making OSM presets, like: -* The object type you want to map. As explained in **Data Model OpenStreetMap** module, that there are three types of mapped objects in OpenStreetMap: **point (nodes), line (ways), **and** area (closedway)**. For example, if the mapped object is road, then the object type you write on your presets is ways, not other type. +* The object type you want to map. As explained in **Data Model OpenStreetMap** module, that there are three types of mapped objects in OpenStreetMap: **point (nodes), line (ways),** and **area (closedway)**. For example, if the mapped object is road, then the object type you write on your presets is ways, not other type. * The standardized key and value for mapped objects on OpenStreetMap. You can refer to Map Features on Wikipedia Page, OSM Indonesia Object Reference and Tag Info. To know more about key and value, please refer to **Data Model OpenStreetMap** module. * Key dan value should be written in English, but for the presets label can be written in Bahasa. @@ -160,7 +160,7 @@ This element defines object’s information in multiselect format. This element ![Multiselect key](/en/images/06-OSM-Field-Survey-Manager-Guidelines/03-Membuat-Presets-OpenStreetMap/0315_presets.png) -The multiselect key structure is very similar with combo key structure._ _The differences are the key ‘multiselect’ is used instead of key ‘combo’ and the separator used in between values is semicolon (;) while key and value labels can be written in Bahasa Indonesia, using ‘text’ and ‘display_values’. This picture is the presets appearance of multiselect key example above: +The multiselect key structure is very similar with combo key structure. The differences are the key ‘multiselect’ is used instead of key ‘combo’ and the separator used in between values is semicolon (;) while key and value labels can be written in Bahasa Indonesia, using ‘text’ and ‘display_values’. This picture is the presets appearance of multiselect key example above: ![Element multiselect key on JOSM](/en/images/06-OSM-Field-Survey-Manager-Guidelines/03-Membuat-Presets-OpenStreetMap/0308_presets_8.png) diff --git a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/04-Penggunaan-YAML-pada-Export-Tool.md b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/04-Penggunaan-YAML-pada-Export-Tool.md index 200f65c..b3094f8 100644 --- a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/04-Penggunaan-YAML-pada-Export-Tool.md +++ b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/04-Penggunaan-YAML-pada-Export-Tool.md @@ -1,222 +1,227 @@ ---- -title: Using YAML -weight: 4 ---- - -**Objectives:** - -* To be able to explain about YAML concept -* To be able to create YAML for export data in Export Tool -* To be able to demonstrate how to get OSM data in Export Tool using YAML - -As explained before, we have learned how to create a customized presets on OpenStreetMap and determine the OpenStreetMap data model to use in the mapping process. In the chapter Using Export Tool, we found the result data attributes only show the attribute from the OSM format. Therefore, you can use YAML to download the OSM data with the specific attribute that will be the same with the OpenStreetMap data model. - -### **I. YAML Concept** - -**YAML** ("YAML Ain't Markup Language") is a [human-readable](https://en.wikipedia.org/wiki/Human-readable) [data serialization language](https://en.wikipedia.org/wiki/Serialization). It is commonly used for [configuration files](https://en.wikipedia.org/wiki/Configuration_file), but could be used in many applications where data is being stored (e.g. debugging output) or transmitted (e.g. document headers). We can use to create data structures in YAML format according to tag (key and value) in the OpenStreetMap data model. - -### **II. Creating YAML to Data Filter in Export Tool** - -**a. YAML Structure Data** - - There are 4 sections to define a YAML structure: -1. Title = define the name of file -2. Types = define the name of mapping, consist of points, lines, and polygons -3. Select = define key from OSM data -4. Where = define key and value by OSM data to pull up the data - -![YAML Structure for OSM data](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0401_Struktur_format_YAML.png) -

YAML Structure for OSM data

- - - **b. Requirements to Creating YAML Structures Data** - - There are some requirements that important to create the YAML structure: -* All formats are lowercase, Not allow the uppercase -* The position of the title has to put at the beginning of the document. Using the (_) sign to separate the title, an example bank_points -* The position of all formats are equal, an example in the image above - -**c. Creating YAML** - -We will create the YAML structure form OpenStreetMap Data Model that you can open the chapter **OpenStreetMap data Model **to refer the lists of OSM data Models that the objects mapped in the project. There are steps to create the YAML: - -* Open the lists OSM data model or you can create a table like below - -Bank Tag Information Table - -| key | possible values | -|---|---| -|amenity|bank| -|building|bank| -|amenity|bank| -|name|fill the name of bank| -|addr:full|detail of address| -|capacity|<50, 50-100, 100-250, 250-500, >500| -|building:levels|number| -|building:structure|confined_masonry, steel_frame, wood_frame, bamboo_frame| -|building:walls|brick, concrete, wood, bamboo, glass| -|building:floor|ground, wood, cement, tekhel, ceramics| -|building:roof|tile, tin, asbestos, concrete| -|access:roof|yes, no| -|building:condition|poor, good| -|backup_generator|yes, no| - - -* Open Notepad that already on your computer -* The first line, type the name of title, an example bank - - bank: - -* The second line, click enter + space four times and typing the **types:**, and click enter + space eight times + typing **- points/polygons/lines**, an example - - types: - - points - - polygons - -* Click enter on your keyboard and suitable the position with “types:”, and type **select:** → enter + space eight times and type the lists of the key in the Bank Tag Information Table. - - select: - - amenity - - name - - addr:full - - addr:city - - capacity:persons - - building - - building:levels - - building:structure - - building:walls - - building:floor - - building:roof - - access:roof - - building:condition - - backup_generator - - source - -* The last step, click enter and suitable position types and select → type **where: key dan value** - - where: amenity='bank' - -* If the format was completed, you can save the format in .txt file in your computer. - - bank: - types: - - points - - polygons - select: - - amenity - - name - - addr:full - - addr:city - - capacity:persons - - building - - building:levels - - building:structure - - building:walls - - building:floor - - building:roof - - access:roof - - building:condition - - backup_generator - - source -### **III. How to Using YAML in Export Tool** - -**a. Login with OSM account** -* Open your browser, and type this link https://export.hotosm.org - -![The interface of Export Tool ](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0402_Halaman_Situs_Export.png) -

The interface of Export Tool

- -* The first we have login with your OSM account to using Export Tool. Click on **Login** in the right corner. The next click on ‘Authorize access to your account’ → **Grant Access**. - -![Grant Access](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0403_Izin_akses_akun_OSM.png) -

Login to Export Tool

- -* To create a new project in Export Tool click on **Start Exporting** -* The Export Tool window will be displayed like the image below - - -![The fill from Export Tool](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0404_Lembar_kerja_Export_Tool.png) -

The fill from Export Tool

- -**b. Defining an area of interest** - -There are 5 ways to define an Area of Interest for your export: - -1. **Bounding Box:** Use the "Box" tool to the right to click and drag a rectangle, or use the "Current View" tool to match the map's viewport. - -![Bounding box](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0405_Penentuan_area_box.png) -

Bounding box

- -2. **Draw Polygon:** Draw a freeform polygon. This must be a simple (not multi-) polygon. - -![Manually edit](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0406_Penentuan_area_dengan_bentuk_manual.png) -

Manually edit

- - -3. **Upload:** By uploading a GeoJSON polygon in WGS84 (geographic) coordinates. If you have not the GeoJSON data, you can refer to this chapter **Using GeoJSON**. - -![Import the administrative boundary](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0407_Penentuan_area_dengan_import.png) -

Import the administrative boundary

- - -4. **Search Bar:** input a minX,minY,maxX,maxY string into the search bar. This will define a rectangular area of interest. - -5. **Current View:** Use "Current View" to match the map's viewport. - -The maximum extent of export on the Export Tool is determined by the density of OSM data in the defined area. **The bounding box of the area can contain at most 10,000,000 OSM nodes. **This limitation means that a 10,000 square kilometer box over a heavily mapped area like Western Europe or North America will likely be rejected, but an equal-sized box over a sparsely mapped area will be accepted by the Export Tool. If you need larger exports, please Contact Us or use an alternative resource such as downloads from [Geofabrik](http://download.geofabrik.de/) or [Mapzen](https://mapzen.com/data/metro-extracts/). - -**c. Naming and Describing your Export** - -* **Name (required):** choose a short, descriptive name. -* **Description:** a long text body, perhaps describing what relevant features the export includes. -* **Project:** Helps to group together exports particular to a project, e.g. "PDC InAWARE in Semarang City” - -**d. Choosing File Format** - -* Check at least one file format to export. To learn more about each individual format, read the documentation: [Export Formats](https://export.hotosm.org/en/v3/learn/export_formats) - -![Spatial data](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0408_Format_data_spasial.png) -

Spatial data

- -**e. Choosing Map Features** - -* Click on **Data Menu → YAML**. You can copy and paste the YAML from the section “Creating YAML” in the box. - - ![menu yaml](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0409_Menu_YAML.png) -

Menu YAML

- - -**f. Downloading your File** - -* The last step is the Summary Menu that will be displayed about the projects. Click the **Create Export** to starting the process - -![menu summary](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0410_Menu_summary.png) -

Menu summary

- - -* After you submit your export using **Create Export**, you will be redirected to the **Export Detail Page**, which shows a list of **Export Runs**. You will see the first run at the top of the page. It will be in one of the following states: - - **Submitted:** The export is waiting to be processed. This should be brief, depending on the server load. - **Running:** The export is waiting to be processed. City-sized regions should be a few minutes - larger regions can take upwards of 20 minutes, depending on the density of OSM data. - **Completed:** Your export files are available for download. Each export format has a separate download link for its ZIP archive. - -![menu export](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0411_Menu_export.png) -

Menu Export

- - -* If the status will be **COMPLETED**, we can download the data with a click on **bank_smg_shp.zip **and save in your directory. - -![Completed Process](/id/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0412_Done.png) -

Completed Process

- - -**Exercise!** - -* Create the new projects form this link [https://tinyurl.com/group-stats](https://tinyurl.com/group-stats). -* You can use the administrative boundary from Semarang City for Import in the project, download the admin in this link [https://tinyurl.com/admin-semarang](https://tinyurl.com/admin-semarang). -* The results will be used in the next chapter **Group Stats Plugin for Calculate The Objects**. If you have finished, the results consist of two shapefile (public facilities and highways). - -**SUMMARY** - -You have learned about how to download the spatial data using YAML in the Export Tool. The results data from YAML, the attributes table will be the same with the data in your mapping projects and the attributes table have organized. You can open the file in mapping software, like QGIS. - +--- +title: Using YAML +weight: 4 +--- + +**Objectives:** + +* To be able to explain about YAML concept +* To be able to create YAML for export data in Export Tool +* To be able to demonstrate how to get OSM data in Export Tool using YAML + +As explained before, we have learned how to create a customized presets on OpenStreetMap and determine the OpenStreetMap data model to use in the mapping process. In the chapter Using Export Tool, we found the result data attributes only show the attribute from the OSM format. Therefore, you can use YAML to download the OSM data with the specific attribute that will be the same with the OpenStreetMap data model. + +### **I. YAML Concept** + +**YAML** ("YAML Ain't Markup Language") is a [human-readable](https://en.wikipedia.org/wiki/Human-readable) [data serialization language](https://en.wikipedia.org/wiki/Serialization). It is commonly used for [configuration files](https://en.wikipedia.org/wiki/Configuration_file), but could be used in many applications where data is being stored (e.g. debugging output) or transmitted (e.g. document headers). We can use to create data structures in YAML format according to tag (key and value) in the OpenStreetMap data model. + +### **II. Creating YAML to Data Filter in Export Tool** + +**a. YAML Structure Data** + + There are 4 sections to define a YAML structure: + +1. Title = define the name of file +2. Types = define the name of mapping, consist of points, lines, and polygons +3. Select = define key from OSM data +4. Where = define key and value by OSM data to pull up the data + +![YAML Structure for OSM data](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0401_Struktur_format_YAML.png) +

YAML Structure for OSM data

+ + +**b. Requirements to Creating YAML Structures Data** + + There are some requirements that important to create the YAML structure: + +* All formats are lowercase, Not allow the uppercase +* The position of the title has to put at the beginning of the document. Using the (_) sign to separate the title, an example bank_points +* The position of all formats are equal, an example in the image above + +**c. Creating YAML** + +We will create the YAML structure form OpenStreetMap Data Model that you can open the chapter **OpenStreetMap data Model **to refer the lists of OSM data Models that the objects mapped in the project. There are steps to create the YAML: + +* Open the lists OSM data model or you can create a table like below + + Bank Tag Information Table + + | key | possible values | + |---|---| + |amenity|bank| + |building|bank| + |amenity|bank| + |name|fill the name of bank| + |addr:full|detail of address| + |capacity|<50, 50-100, 100-250, 250-500, >500| + |building:levels|number| + |building:structure|confined_masonry, steel_frame, wood_frame, bamboo_frame| + |building:walls|brick, concrete, wood, bamboo, glass| + |building:floor|ground, wood, cement, tekhel, ceramics| + |building:roof|tile, tin, asbestos, concrete| + |access:roof|yes, no| + |building:condition|poor, good| + |backup_generator|yes, no| + + +* Open Notepad that already on your computer +* The first line, type the name of title, an example bank + + bank: + +* The second line, click enter + space four times and typing the **types:**, and click enter + space eight times + typing **- points/polygons/lines**, an example + + types: + - points + - polygons + +* Click enter on your keyboard and suitable the position with “types:”, and type **select:** → enter + space eight times and type the lists of the key in the Bank Tag Information Table. + + select: + - amenity + - name + - addr:full + - addr:city + - capacity:persons + - building + - building:levels + - building:structure + - building:walls + - building:floor + - building:roof + - access:roof + - building:condition + - backup_generator + - source + +* The last step, click enter and suitable position types and select → type **where: key dan value** + + where: amenity='bank' + +* If the format was completed, you can save the format in .txt file in your computer. + + bank: + types: + - points + - polygons + select: + - amenity + - name + - addr:full + - addr:city + - capacity:persons + - building + - building:levels + - building:structure + - building:walls + - building:floor + - building:roof + - access:roof + - building:condition + - backup_generator + - source + where: amenity='bank' + +### **III. How to Using YAML in Export Tool** + +**a. Login with OSM account** + +* Open your browser, and type this link https://export.hotosm.org + +![The interface of Export Tool ](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0402_Halaman_Situs_Export.png) +

The interface of Export Tool

+ +* The first we have login with your OSM account to using Export Tool. Click on **Login** in the right corner. The next click on ‘Authorize access to your account’ → **Grant Access**. + +![Grant Access](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0403_Izin_akses_akun_OSM.png) +

Login to Export Tool

+ +* To create a new project in Export Tool click on **Start Exporting** +* The Export Tool window will be displayed like the image below + + +![The fill from Export Tool](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0404_Lembar_kerja_Export_Tool.png) +

The fill from Export Tool

+ +**b. Defining an area of interest** + +There are 5 ways to define an Area of Interest for your export: + +1. **Bounding Box:** Use the "Box" tool to the right to click and drag a rectangle, or use the "Current View" tool to match the map's viewport. + + ![Bounding box](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0405_Penentuan_area_box.png) +

Bounding box

+ +2. **Draw Polygon:** Draw a freeform polygon. This must be a simple (not multi-) polygon. + + ![Manually edit](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0406_Penentuan_area_dengan_bentuk_manual.png) +

Manually edit

+ + +3. **Upload:** By uploading a GeoJSON polygon in WGS84 (geographic) coordinates. If you have not the GeoJSON data, you can refer to this chapter **Using GeoJSON**. + + ![Import the administrative boundary](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0407_Penentuan_area_dengan_import.png) +

Import the administrative boundary

+ + +4. **Search Bar:** input a minX,minY,maxX,maxY string into the search bar. This will define a rectangular area of interest. + +5. **Current View:** Use "Current View" to match the map's viewport. + +The maximum extent of export on the Export Tool is determined by the density of OSM data in the defined area. **The bounding box of the area can contain at most 10,000,000 OSM nodes. **This limitation means that a 10,000 square kilometer box over a heavily mapped area like Western Europe or North America will likely be rejected, but an equal-sized box over a sparsely mapped area will be accepted by the Export Tool. If you need larger exports, please Contact Us or use an alternative resource such as downloads from [Geofabrik](http://download.geofabrik.de/) or [Mapzen](https://mapzen.com/data/metro-extracts/). + +**c. Naming and Describing your Export** + +* **Name (required):** choose a short, descriptive name. +* **Description:** a long text body, perhaps describing what relevant features the export includes. +* **Project:** Helps to group together exports particular to a project, e.g. "PDC InAWARE in Semarang City” + +**d. Choosing File Format** + +* Check at least one file format to export. To learn more about each individual format, read the documentation: [Export Formats](https://export.hotosm.org/en/v3/learn/export_formats) + +![Spatial data](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0408_Format_data_spasial.png) +

Spatial data

+ +**e. Choosing Map Features** + +* Click on **Data Menu → YAML**. You can copy and paste the YAML from the section “Creating YAML” in the box. + + ![menu yaml](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0409_Menu_YAML.png) +

Menu YAML

+ + +**f. Downloading your File** + +* The last step is the Summary Menu that will be displayed about the projects. Click the **Create Export** to starting the process + +![menu summary](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0410_Menu_summary.png) +

Menu summary

+ + +* After you submit your export using **Create Export**, you will be redirected to the **Export Detail Page**, which shows a list of **Export Runs**. You will see the first run at the top of the page. It will be in one of the following states: + + **Submitted:** The export is waiting to be processed. This should be brief, depending on the server load. + **Running:** The export is waiting to be processed. City-sized regions should be a few minutes - larger regions can take upwards of 20 minutes, depending on the density of OSM data. + **Completed:** Your export files are available for download. Each export format has a separate download link for its ZIP archive. + +![menu export](/en/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0411_Menu_export.png) +

Menu Export

+ + +* If the status will be **COMPLETED**, we can download the data with a click on **bank_smg_shp.zip **and save in your directory. + +![Completed Process](/id/images/06-OSM-Field-Survey-Manager-Guidelines/04-Penggunaan-YAML-pada-Export-Tool/0412_Done.png) +

Completed Process

+ + +**Exercise!** + +* Create the new projects form this link [https://tinyurl.com/group-stats](https://tinyurl.com/group-stats). +* You can use the administrative boundary from Semarang City for Import in the project, download the admin in this link [https://tinyurl.com/admin-semarang](https://tinyurl.com/admin-semarang). +* The results will be used in the next chapter **Group Stats Plugin for Calculate The Objects**. If you have finished, the results consist of two shapefile (public facilities and highways). + +**SUMMARY** + +You have learned about how to download the spatial data using YAML in the Export Tool. The results data from YAML, the attributes table will be the same with the data in your mapping projects and the attributes table have organized. You can open the file in mapping software, like QGIS. + diff --git a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/08-Pembuatan-MBTiles-untuk-OpenMapKit/08_Membuat_MBTiles_untuk_OpenMapKit.md b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/08-Pembuatan-MBTiles-untuk-OpenMapKit/08_Membuat_MBTiles_untuk_OpenMapKit.md index a3b4afd..4cd4349 100644 --- a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/08-Pembuatan-MBTiles-untuk-OpenMapKit/08_Membuat_MBTiles_untuk_OpenMapKit.md +++ b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/08-Pembuatan-MBTiles-untuk-OpenMapKit/08_Membuat_MBTiles_untuk_OpenMapKit.md @@ -4,6 +4,7 @@ weight: 8 --- **Objectives:** + * To be able to understand the concept of MBTiles * To be able to create MBTiles using Export Tool * To be able to create MBTiles using Plugin QTiles @@ -90,6 +91,7 @@ Export Tool is one of the sites that is used to download OpenStreetMap data for The QTiles plugin is a plugin that can be used to produce tile rasters from QGIS project. This plugin can save the tile raster display settings from tilemap services such as Slippy map, TMS. You can use the QuickMapServices plugin in the previous module **Creating Field Maps with QGIS** to display tile raster services. Another advantage of using this plugin is that you can display the road layers and administrative boundaries in the QGIS project, so that the OMK basemap display will help data entry in the field surveys introduction. The steps to create .mbtiles with the QTiles plugin are as follows: **a. Installing Plugin QTiles** + * Open QGIS and_ _install the plugin by clicking **_Plugin Menu → Manage and Install Plugin._** Type “qtiles” in **Search** box so your display will be the same as the picture below, give a check mark and click **Install Plugin**. If your download process failed, check your internet connection immediately. ![Installing Plugin QTiles](/en/images/06-OSM-Field-Survey-Manager-Guidelines/08-Pembuatan-MBTiles-untuk-OpenMapKit/0812_qtiles.png) @@ -102,6 +104,7 @@ The QTiles plugin is a plugin that can be used to produce tile rasters from QGIS **b. Preparing Data Layer** + * Add administrative data layer and road network that is taken from field survey mapping. Then, click **_Add Vector Layer_** → choose the directory file **_→ Open → Open_**. Data layer will appear in both map canvas and layer panel. ![Adding layer](/en/images/06-OSM-Field-Survey-Manager-Guidelines/08-Pembuatan-MBTiles-untuk-OpenMapKit/0814_menambahkanlayer.png) diff --git a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats.md b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats.md index 30828b9..3c83b7e 100644 --- a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats.md +++ b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats.md @@ -1,224 +1,227 @@ ---- -title: Group Stats Plugin for Calculate The Objects -weight: 9 ---- - -**Objectives:** - -* To be able to demonstrate how to install a plugin for calculate number of object in QGIS -* To be able to operate the Group Stats plugin for calculate number of OSM Object - -The calculation of the quantity of data can be an indicator of the achievement of mapping projects that can be poured into a mapping report. The process of calculating the quantity of OSM data can be done by installing the plugin group stats in QGIS for free, this plugin can use to count the number of objects based on categories. - -### **I. Group Stats Installation** - -* If you haven’t the QGIS application, you can download it in this link and install the QGIS. - - [http://download.osgeo.org/qgis/win64/QGIS-OSGeo4W-2.14.22-1-Setup-x86.exe](http://download.osgeo.org/qgis/win64/QGIS-OSGeo4W-2.14.22-1-Setup-x86.exe) for Windows 32 bit and [http://download.osgeo.org/qgis/win64/QGIS-OSGeo4W-2.14.22-1-Setup-x86_64.exe](http://download.osgeo.org/qgis/win64/QGIS-OSGeo4W-2.14.22-1-Setup-x86_64.exe) for Windows 64 bit. - -* Open QGIS and ensure the internet connection is working. Click on **Plugins Menu → Manage and Install Plugins** - - ![Plugins Menu Interface](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0901_menuplugin.png) -

Plugins Menu Interface

- -* Type **Group Stats** in the **Search** box and click on **Install Plugin** - -![Install the plugin](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0902_plugingroupstats.png) -

Install the plugin

- -* If the installation has finished, the plugin will show up in **Vector Menu → GroupStats** - -![GroupStats Interface](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0903_menugroupstats.png) -

GroupStats Interface

- - -### **II. Calculate OSM Objects using Group Stats** - -We can overlay the administrative boundaries and the infrastructures to get the calculate of data quantity. The results of the calculation can be used to create a monthly report and monitory the mapping timeline. Before we starting to calculate the objects, we have to prepare the data in the shapefile format. - -We can use the data form PDC InaWARE project in Semarang City in this chapter, getting the administrative boundary data in this link [https://openstreetmap.id/data-semarang/](https://openstreetmap.id/data-semarang/) and the infrastructures data in [https://export.hotosm.org/en/v3/exports](https://export.hotosm.org/en/v3/exports) (follow this chapter **04.Using YAML** to the instructions). The list of the objects in the shapefile: - -* **Public Facilities: Points and Polygons** -1. All objects in amenity=* -2. Electrical Facility (power=*) -3. Park (leisure=*) -4. Government Office (office=*) -5. Supermarket (shop=supermarket) -* **highways:** Lines - - highway=* - -The next step we will start to calculate the objects: - -**a. Preparing the Data** - -* Open the layer in QGIS with click on **Add Vector Layer → Browse** or click **Layer Menu → Add Layer → Add Vector Layer → Browse**. - -![Add Vector Layer](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0904_addvector.png) -

Add Vector Layer

- -* Choose your directory that the objects file is saved → **Select All → Open → Open** - -![shapefile](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0905_daftarfileshp.png) -

Open shapefile from directory

- -* The layers will appear on map canvas and **Layers Panel** - -![The Objects layer view on the map canvas](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0906_tampilanlayer.png) -

The Objects layer view on the map canvas

- -* Add the administrative boundary to QGIS with click on the **Add Vector Layer** - -![The layer view on the map canvas](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0907_tampilanbatas.png) -

The layer view on the map canvas

- -**b. Merge the Objects Layer and Administrative Boundary** - -* Merge the layer between the objects and administrative boundary so that the objects have a new column from the administrative boundary. Click **Menu Vector → Geoprocessing Tool → Intersect **to merge the layer. In section,** input vector layer** selects the object layer with the **Intersect layer** (administrative boundary layer). Choose **Browse** to save the file **output shapefile** in your directory, and click **OK**. - -![intersect layer](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0908_intersectproses.png) -

Intersect layer

- -* The results will appear in your map canvas as a new layer. We can get the details of the attribute data form “**fasum_point_admin”** layer with right-click on the layer and click on **Open Attribute Table**. We found at the column **name_2** the name of a village in each object. - -![The attribute table of intersecting result](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0909_tabelatribut.png) -

The attribute table of intersecting result

- -* We will repeat the process on the highways layer and the polygon public facilities layer. The intersecting results will be three-layer on the QGIS. -* Open the attribute table in each layer and check the column that it is a reference to calculate the OSM data. The list of the column in attribute table: -1. Point public facilities = amenity, power, office dan supermarket -2. Polygon public facilities = amenity, power, office, supermarket, dan leisure -3. highways = highway - -**c. Calculate the Objects using Group Stats Plugin** - -The mapping results are points, lines, and polygons so that we can calculate with a different formula in Group Stats plugin based on the type of data. OSM data in points and polygons will be calculated with the formula **“count”** that calculating the number of an attribute in the column. Although, OSM data in lines will be calculated with the formula **“sum”**, that calculating the number of length segments. - -1. **The Calculating Points and Polygons** -* Open the plugin with **Menu Vector → Group Stats → GroupStats** - -![group stats](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0912_menugroupstats.png) -

Group Stats

- -* Follow the instructions as below: -1. **Layers** (1)= show the layer will be calculated. **Fields** = an automatic show the column in attribute table that chooses -2. **Filter** (2) = use to show objects only in specific administrative boundary -3. **Columns** (3) = use to become column on the table, fill the column on the Fields, with a click and move the Columns box. -4. **Rows** (4) = use to become a row in the table, fill the column on the Fields, with a click and move the Row box. -5. **Value** (5)= use to select the formula -6. Click on **Calculate** (6) to starting the calculation - -![Step by step the Group Stats](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0913_langkahgroupstats.png) -

Step by step the Group Stats

- -* We will use the filter function to select the objects only in specific sub-district. Click on “**fasum_point_admin”**, so that the data only show for once sub-districts. Filter data on the “**fasum_point_admin”** layer, and click the **Filter in Group Stats**. The filter window will appear. - -![Filter data](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0910_filtermenu.png) -

Filter data

- -* We will move the result table in group stats to other spreadsheet applications such as Ms.Excel or Google Sheets. So we can change the visual data to become a graph and a diagram. To start the process click on **Data → Copy all to clipboard**. - -![Copy and paste the attribute table](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0914_clipboard.png) -

Copy and paste the attribute table

- -* Open the Microsoft Excel or Google Sheets to move the results table Group Stats. -* We can do the same instructions to calculate the other objects, see the example results from PDC Semarang City in this link [http://tinyurl.com/kuantitas-data](http://tinyurl.com/kuantitas-data). - -**2. Calculate the Lines Object with Calculation Length Segments.** - -The Calculation a type of lines different with points and polygon. If we calculate the length segments of highways, the shapefile will be changed in Universal Transverse Mercator (UTM) coordinate system. The steps to calculate the length of the highways: - -**Change the Coordinate System** - -* Right-click on highways layer **→ Save as → choose the Format ESRI Shapefile → Save as in your directory → CRS** choose the reference system on your UTM area. - -![Save as with different CRS](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0915_simpanfile.png) -

Save as with different CRS

- -* If you give the checkmark on the **Add saved the file to map**, the result will show up in the map canvas and **Layers Panel**. - -**Create the New Column to Calculation Length of the highways** - -* Then right-click on the Layers **“Jalan_Admin_UTM”** → **Open Attribute Table**. Click on the **Toggle editing mode** to activate the attribute toolbar. - -![toolbar toggle editing mode](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0916_toggleediting.png) -

Toolbar Toggle editing mode

- -* To add a new column, click on the **New Field** in the toolbar. - -![toolbar new field](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0917_newfield.png) -

Toolbar New Field

- -* There are the filled form **Add field window** -1. **Name** = Title of the column (a maximum of 10 characters) -2. **Type** = Type of data that you need in the fill of the table. Select the Decimal number (real) to view the length of the segments -3. **Provider type double** = The length shows the maximum number of columns and precision shows the number of the decimal in behind comma. -4. Click OK - -![Add field setting](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0918_pengaturanfield.png) -

Add field setting

- -**Calculation the Length (meter) with Field Calculator** - -* To start the process click on **Open field calculator** -* The settings in the Open field calculator: -1. We can put the checkmark in **Update existing field** to update the existing column. -2. Choose the column that will be updated -3. We can type the **“length”** to calculate the length of the highway with the formula. -4. Double-click on **Geometry → $ length** is a formula to calculate the length of segments. After we clicked the formula, **$length** will appear in the Expression box in the right panel. -5. Click OK - -![The setting of Field Calculator](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0919_fieldpj.png) -

The setting of Field Calculator

- -* The results will be displayed in the last column. - -![The length of highways](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0920_hasilpj.png) -

The length of highways

- - -* Save your edit with **Save Edits** in the toolbar. To finish the process click **Toggle Editing**. - -![Save edits](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0921_savechange.png) -

Save edits

- -**Calculation the length of highways based on the type of highways with Group Stats** - -* Open **Group Stats** click on the **Menu Vector → Group Stats → Group Stats**. -* We can use the **“sum” and Length** formula to calculate the number of length on the **Value box** - -![The setting of length segments](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0923_groupstatspj.png) -

The setting of length segments

- -* If we want to calculate based on the administrative boundary, we can use the filter function in the Group Stats plugin. Click on Filter and follow the instructions. - -![Filter based on subdistricts](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0922_langkahfilterdata.png) -

Filter based on subdistricts

- -* As explained before, we can move the table to another spreadsheet to create a graph. Click on the **Data → Copy all to clipboard**. - -![Copy all the clipboard](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0924_copyhasilpj.png) -

Copy all the clipboard

- -* Open the spreadsheet and paste the table in there. - -The example table of length the highways - -|Type of highway|Candi|Jatingaleh|Jomblang|Kaliwiru|Karang Gunung|Tegalsari|Wonotinggal| -|---|---|---|---|---|---|---|---| -|Motorway|-|1313.88|163.85|-|-|-|-| -|Trunk|-|1571.20|-|1602.19|-|-|-| -|Primary|-|1389.34|1264.54|-|206.96|-|-| -|Secondary|1065.13|-|24.17|2353.86|-|-|-| -|Tertiary|271.49|3920.71|1612.78|-|836.18|-|-| -|Service|500.24|2567.00|226.11|116.68|150.03|301.93|851.94| -|Residential|8486.45|14300.66|20972.41|5424.36|13322.03|15234.38|11635.03| -|Pedestrian|-|1313.88|163.85|-|-|141.93|344.38| -|Path|-|14.68|-|-|-|601.85|26.40| -|Living Street|5913.74|2841.22|6588.17|451.66|4401.59|3509.38|2576.71| - -* We can do the same instructions to calculate the other objects in lines, see the example results from PDC Semarang City in this link [http://tinyurl.com/kuantitas-data](http://tinyurl.com/kuantitas-data). - -**SUMMARY** - -We have learned about how to calculate the quantities of OSM data using the Group Stats plugin. We can use the statistic data in the report to analysis, mapping progress, and mapping achievement. If you want to create the timeline from the results based on an admin level, we can calculate the data in each village that the village survey has finished. +--- +title: Group Stats Plugin for Calculate The Objects +weight: 9 +--- + +**Objectives:** + +* To be able to demonstrate how to install a plugin for calculate number of object in QGIS +* To be able to operate the Group Stats plugin for calculate number of OSM Object + +The calculation of the quantity of data can be an indicator of the achievement of mapping projects that can be poured into a mapping report. The process of calculating the quantity of OSM data can be done by installing the plugin group stats in QGIS for free, this plugin can use to count the number of objects based on categories. + +### **I. Group Stats Installation** + +* If you haven’t the QGIS application, you can download it in this link and install the QGIS. + + [http://download.osgeo.org/qgis/win64/QGIS-OSGeo4W-2.14.22-1-Setup-x86.exe](http://download.osgeo.org/qgis/win64/QGIS-OSGeo4W-2.14.22-1-Setup-x86.exe) for Windows 32 bit and [http://download.osgeo.org/qgis/win64/QGIS-OSGeo4W-2.14.22-1-Setup-x86_64.exe](http://download.osgeo.org/qgis/win64/QGIS-OSGeo4W-2.14.22-1-Setup-x86_64.exe) for Windows 64 bit. + +* Open QGIS and ensure the internet connection is working. Click on **Plugins Menu → Manage and Install Plugins** + + ![Plugins Menu Interface](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0901_menuplugin.png) +

Plugins Menu Interface

+ +* Type **Group Stats** in the **Search** box and click on **Install Plugin** + +![Install the plugin](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0902_plugingroupstats.png) +

Install the plugin

+ +* If the installation has finished, the plugin will show up in **Vector Menu → GroupStats** + +![GroupStats Interface](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0903_menugroupstats.png) +

GroupStats Interface

+ + +### **II. Calculate OSM Objects using Group Stats** + +We can overlay the administrative boundaries and the infrastructures to get the calculate of data quantity. The results of the calculation can be used to create a monthly report and monitory the mapping timeline. Before we starting to calculate the objects, we have to prepare the data in the shapefile format. + +We can use the data form PDC InaWARE project in Semarang City in this chapter, getting the administrative boundary data in this link [https://openstreetmap.id/data-semarang/](https://openstreetmap.id/data-semarang/) and the infrastructures data in [https://export.hotosm.org/en/v3/exports](https://export.hotosm.org/en/v3/exports) (follow this chapter **04.Using YAML** to the instructions). The list of the objects in the shapefile: + +* **Public Facilities: Points and Polygons** + 1. All objects in amenity=* + 2. Electrical Facility (power=*) + 3. Park (leisure=*) + 4. Government Office (office=*) + 5. Supermarket (shop=supermarket) + + +* **highways:** Lines + + highway=* + +The next step we will start to calculate the objects: + +**a. Preparing the Data** + +* Open the layer in QGIS with click on **Add Vector Layer → Browse** or click **Layer Menu → Add Layer → Add Vector Layer → Browse**. + +![Add Vector Layer](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0904_addvector.png) +

Add Vector Layer

+ +* Choose your directory that the objects file is saved → **Select All → Open → Open** + +![shapefile](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0905_daftarfileshp.png) +

Open shapefile from directory

+ +* The layers will appear on map canvas and **Layers Panel** + +![The Objects layer view on the map canvas](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0906_tampilanlayer.png) +

The Objects layer view on the map canvas

+ +* Add the administrative boundary to QGIS with click on the **Add Vector Layer** + +![The layer view on the map canvas](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0907_tampilanbatas.png) +

The layer view on the map canvas

+ +**b. Merge the Objects Layer and Administrative Boundary** + +* Merge the layer between the objects and administrative boundary so that the objects have a new column from the administrative boundary. Click **Menu Vector → Geoprocessing Tool → Intersect** to merge the layer. In section, **input vector layer** selects the object layer with the **Intersect layer** (administrative boundary layer). Choose **Browse** to save the file **output shapefile** in your directory, and click **OK**. + +![intersect layer](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0908_intersectproses.png) +

Intersect layer

+ +* The results will appear in your map canvas as a new layer. We can get the details of the attribute data form “**fasum_point_admin”** layer with right-click on the layer and click on **Open Attribute Table**. We found at the column **name_2** the name of a village in each object. + +![The attribute table of intersecting result](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0909_tabelatribut.png) +

The attribute table of intersecting result

+ +* We will repeat the process on the highways layer and the polygon public facilities layer. The intersecting results will be three-layer on the QGIS. +* Open the attribute table in each layer and check the column that it is a reference to calculate the OSM data. The list of the column in attribute table: +1. Point public facilities = amenity, power, office dan supermarket +2. Polygon public facilities = amenity, power, office, supermarket, dan leisure +3. highways = highway + +**c. Calculate the Objects using Group Stats Plugin** + +The mapping results are points, lines, and polygons so that we can calculate with a different formula in Group Stats plugin based on the type of data. OSM data in points and polygons will be calculated with the formula **“count”** that calculating the number of an attribute in the column. Although, OSM data in lines will be calculated with the formula **“sum”**, that calculating the number of length segments. + +1. **The Calculating Points and Polygons** + +* Open the plugin with **Menu Vector → Group Stats → GroupStats** + +![group stats](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0912_menugroupstats.png) +

Group Stats

+ +* Follow the instructions as below: + 1. **Layers** (1)= show the layer will be calculated. **Fields** = an automatic show the column in attribute table that chooses + 2. **Filter** (2) = use to show objects only in specific administrative boundary + 3. **Columns** (3) = use to become column on the table, fill the column on the Fields, with a click and move the Columns box. + 4. **Rows** (4) = use to become a row in the table, fill the column on the Fields, with a click and move the Row box. + 5. **Value** (5)= use to select the formula + 6. Click on **Calculate** (6) to starting the calculation + +![Step by step the Group Stats](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0913_langkahgroupstats.png) +

Step by step the Group Stats

+ +* We will use the filter function to select the objects only in specific sub-district. Click on “**fasum_point_admin”**, so that the data only show for once sub-districts. Filter data on the “**fasum_point_admin”** layer, and click the **Filter in Group Stats**. The filter window will appear. + +![Filter data](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0910_filtermenu.png) +

Filter data

+ +* We will move the result table in group stats to other spreadsheet applications such as Ms.Excel or Google Sheets. So we can change the visual data to become a graph and a diagram. To start the process click on **Data → Copy all to clipboard**. + +![Copy and paste the attribute table](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0914_clipboard.png) +

Copy and paste the attribute table

+ +* Open the Microsoft Excel or Google Sheets to move the results table Group Stats. +* We can do the same instructions to calculate the other objects, see the example results from PDC Semarang City in this link [http://tinyurl.com/kuantitas-data](http://tinyurl.com/kuantitas-data). + +**2. Calculate the Lines Object with Calculation Length Segments.** + +The Calculation a type of lines different with points and polygon. If we calculate the length segments of highways, the shapefile will be changed in Universal Transverse Mercator (UTM) coordinate system. The steps to calculate the length of the highways: + +**a. Change the Coordinate System** + +* Right-click on highways layer **→ Save as → choose the Format ESRI Shapefile → Save as in your directory → CRS** choose the reference system on your UTM area. + +![Save as with different CRS](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0915_simpanfile.png) +

Save as with different CRS

+ +* If you give the checkmark on the **Add saved the file to map**, the result will show up in the map canvas and **Layers Panel**. + +**b. Create the New Column to Calculation Length of the highways** + +* Then right-click on the Layers **“Jalan_Admin_UTM”** → **Open Attribute Table**. Click on the **Toggle editing mode** to activate the attribute toolbar. + +![toolbar toggle editing mode](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0916_toggleediting.png) +

Toolbar Toggle editing mode

+ +* To add a new column, click on the **New Field** in the toolbar. + +![toolbar new field](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0917_newfield.png) +

Toolbar New Field

+ +* There are the filled form **Add field window** +1. **Name** = Title of the column (a maximum of 10 characters) +2. **Type** = Type of data that you need in the fill of the table. Select the Decimal number (real) to view the length of the segments +3. **Provider type double** = The length shows the maximum number of columns and precision shows the number of the decimal in behind comma. +4. Click OK + +![Add field setting](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0918_pengaturanfield.png) +

Add field setting

+ +**c. Calculation the Length (meter) with Field Calculator** + +* To start the process click on **Open field calculator** +* The settings in the Open field calculator: +1. We can put the checkmark in **Update existing field** to update the existing column. +2. Choose the column that will be updated +3. We can type the **“length”** to calculate the length of the highway with the formula. +4. Double-click on **Geometry → $ length** is a formula to calculate the length of segments. After we clicked the formula, **$length** will appear in the Expression box in the right panel. +5. Click OK + +![The setting of Field Calculator](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0919_fieldpj.png) +

The setting of Field Calculator

+ +* The results will be displayed in the last column. + +![The length of highways](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0920_hasilpj.png) +

The length of highways

+ + +* Save your edit with **Save Edits** in the toolbar. To finish the process click **Toggle Editing**. + +![Save edits](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0921_savechange.png) +

Save edits

+ +**d. Calculation the length of highways based on the type of highways with Group Stats** + +* Open **Group Stats** click on the **Menu Vector → Group Stats → Group Stats**. +* We can use the **“sum” and Length** formula to calculate the number of length on the **Value box** + +![The setting of length segments](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0923_groupstatspj.png) +

The setting of length segments

+ +* If we want to calculate based on the administrative boundary, we can use the filter function in the Group Stats plugin. Click on Filter and follow the instructions. + +![Filter based on subdistricts](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0922_langkahfilterdata.png) +

Filter based on subdistricts

+ +* As explained before, we can move the table to another spreadsheet to create a graph. Click on the **Data → Copy all to clipboard**. + +![Copy all the clipboard](/en/images/06-OSM-Field-Survey-Manager-Guidelines/09-Perhitungan-Kuantitas-Data-Menggunakan-Plugin-Group-Stats/0924_copyhasilpj.png) +

Copy all the clipboard

+ +* Open the spreadsheet and paste the table in there. + +The example table of length the highways + +|Type of highway|Candi|Jatingaleh|Jomblang|Kaliwiru|Karang Gunung|Tegalsari|Wonotinggal| +|---|---|---|---|---|---|---|---| +|Motorway|-|1313.88|163.85|-|-|-|-| +|Trunk|-|1571.20|-|1602.19|-|-|-| +|Primary|-|1389.34|1264.54|-|206.96|-|-| +|Secondary|1065.13|-|24.17|2353.86|-|-|-| +|Tertiary|271.49|3920.71|1612.78|-|836.18|-|-| +|Service|500.24|2567.00|226.11|116.68|150.03|301.93|851.94| +|Residential|8486.45|14300.66|20972.41|5424.36|13322.03|15234.38|11635.03| +|Pedestrian|-|1313.88|163.85|-|-|141.93|344.38| +|Path|-|14.68|-|-|-|601.85|26.40| +|Living Street|5913.74|2841.22|6588.17|451.66|4401.59|3509.38|2576.71| + +* We can do the same instructions to calculate the other objects in lines, see the example results from PDC Semarang City in this link [http://tinyurl.com/kuantitas-data](http://tinyurl.com/kuantitas-data). + +**SUMMARY** + +We have learned about how to calculate the quantities of OSM data using the Group Stats plugin. We can use the statistic data in the report to analysis, mapping progress, and mapping achievement. If you want to create the timeline from the results based on an admin level, we can calculate the data in each village that the village survey has finished. diff --git a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/10-Konversi-Data-Shapefile-ke-GeoJSON/10_Konversi_Data_Shapefile_ke_GeoJSON.md b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/10-Konversi-Data-Shapefile-ke-GeoJSON/10_Konversi_Data_Shapefile_ke_GeoJSON.md index d0cc3b5..46b92d4 100644 --- a/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/10-Konversi-Data-Shapefile-ke-GeoJSON/10_Konversi_Data_Shapefile_ke_GeoJSON.md +++ b/content/en/pages/06-OSM-Field-Survey-Manager-Guidelines/10-Konversi-Data-Shapefile-ke-GeoJSON/10_Konversi_Data_Shapefile_ke_GeoJSON.md @@ -1,9 +1,10 @@ --- title: Converting Shapefile Data to GeoJSON -weight: 8 +weight: 10 --- **Objectives:** + * To be able to understand the definition of GeoJSON data * To be able to convert shapefile to GeoJSON with QGIS * To be able to download GeoJSON from Overpass Turbo diff --git a/content/en/pages/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/01_Integrasi_Data_OSM_ke_InAWARE.md b/content/en/pages/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/01_Integrasi_Data_OSM_ke_InAWARE.md index bf1908f..4b5c043 100644 --- a/content/en/pages/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/01_Integrasi_Data_OSM_ke_InAWARE.md +++ b/content/en/pages/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/01_Integrasi_Data_OSM_ke_InAWARE.md @@ -1,51 +1,51 @@ ---- -title: OpenStreetMap Data Integration to InAWARE -weight: 1 ---- - -**Objectives:** - -* Knowing to create an account in InAWARE -* Knowing Add OpenStreetMap Data into InAWARE - -The main goal of HOT-PDC InAWARE Mapping Project is to to complete and provide spatial open data for public so it can be used for any disaster management sector by National Government (BNPB) and Local Disaster Management Agency (BPBD) in InAWARE, a platform that made by Pacific Disaster Center (PDC), an institution from _University of Hawaii_. A complete explanation about InAWARE can be seen in PDC modules. This module will only explain about how OpenStreetMap data can be added and used into InAWARE. - - -### I. **Create and Access InAWARE Account** - -InAWARE limit its access only to specific users such as National Disaster Management Agency (BNPB), Local Disaster Management Agency (BPBD), humanitarian worker and disaster expert / practitioner. This policy is to maintain and ensure InAWARE critical information and content access still clear and without any intervention during disaster management activities. You can send a request to create InAWARE account with these steps: - -* Access InAWARE at **inaware.bnpb.go.id/** -* Click **Request InAWARE Access** in **_login_** page. - -The process would take about 24 hours before your request being approved. It also depends on BNPB as approval of the request. When you account has been made, it will be sent to you by _e-mail_. - -* Please **_login_** into system - -### **II. Adding _OpenStreetMap_ Data into InAWARE** - -After you know about InAWARE and the steps to create an account, you will learn about how to add your field survey data that have been uploaded on OpenStreetMap into InAWARE. Data spatial format which can be used in InAWARE is **_GeoJSON._** You can see **Converting Shapefile to GeoJSON** module. These are steps how to add OpenStreetMap data into InAWARE: - -* Please click **_Layers _**menu in InAWARE -* Click **_Edit_** and select **_Add Layer_** - -![Add OpenStreetMap data as a New Layer](/en/images/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/0101_osm_to_inaware.png) -

Add OpenStreetMap data as a New Layer

- -* Select **_File_** and click **_Please Choose the File_** -* Search and find your OpenStreetMap Data that has been converted into GeoJSON format -* Your OSM data layer will appear in InAWARE and placed into **_KML & External Layers_** folderwith name **_GeoJSON_ _Feature_** - -![OpenStreetMap Data Layer in InAWARE](/en/images/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/0102_osm_to_inaware.png) -

OpenStreetMap Data Layer in InAWARE

- -* You will see information of each feature / object from your OpenStreetMap data. You can select and click on the feature that you want to know its information and choose **_info_** option. - - -![OpenStreetMap Feature Information in InAWARE](/en/images/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/0103_osm_to_inaware.png) -

OpenStreetMap Feature Information in InAWARE

- -### **SUMMARY** - -Congratulations! You have understand about InAWARE and how to add you field survey data into it. For more advanced analysis, you can overlay others layer with your OpenStreetMap data in InAWARE. You can look at PDC modules that provided by _Pacific Disaster Center_ (PDC) for more information about InAWARE. - +--- +title: OpenStreetMap Data Integration to InAWARE +weight: 1 +--- + +**Objectives:** + +* Knowing to create an account in InAWARE +* Knowing Add OpenStreetMap Data into InAWARE + +The main goal of HOT-PDC InAWARE Mapping Project is to to complete and provide spatial open data for public so it can be used for any disaster management sector by National Government (BNPB) and Local Disaster Management Agency (BPBD) in InAWARE, a platform that made by Pacific Disaster Center (PDC), an institution from _University of Hawaii_. A complete explanation about InAWARE can be seen in PDC modules. This module will only explain about how OpenStreetMap data can be added and used into InAWARE. + + +### I. **Create and Access InAWARE Account** + +InAWARE limit its access only to specific users such as National Disaster Management Agency (BNPB), Local Disaster Management Agency (BPBD), humanitarian worker and disaster expert / practitioner. This policy is to maintain and ensure InAWARE critical information and content access still clear and without any intervention during disaster management activities. You can send a request to create InAWARE account with these steps: + +* Access InAWARE at **inaware.bnpb.go.id/** +* Click **Request InAWARE Access** in **_login_** page. + +The process would take about 24 hours before your request being approved. It also depends on BNPB as approval of the request. When you account has been made, it will be sent to you by _e-mail_. + +* Please **_login_** into system + +### **II. Adding _OpenStreetMap_ Data into InAWARE** + +After you know about InAWARE and the steps to create an account, you will learn about how to add your field survey data that have been uploaded on OpenStreetMap into InAWARE. Data spatial format which can be used in InAWARE is **_GeoJSON._** You can see **Converting Shapefile to GeoJSON** module. These are steps how to add OpenStreetMap data into InAWARE: + +* Please click **_Layers_** menu in InAWARE +* Click **_Edit_** and select **_Add Layer_** + +![Add OpenStreetMap data as a New Layer](/en/images/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/0101_osm_to_inaware.png) +

Add OpenStreetMap data as a New Layer

+ +* Select **_File_** and click **_Please Choose the File_** +* Search and find your OpenStreetMap Data that has been converted into GeoJSON format +* Your OSM data layer will appear in InAWARE and placed into **_KML & External Layers_** folderwith name **_GeoJSON_ _Feature_** + +![OpenStreetMap Data Layer in InAWARE](/en/images/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/0102_osm_to_inaware.png) +

OpenStreetMap Data Layer in InAWARE

+ +* You will see information of each feature / object from your OpenStreetMap data. You can select and click on the feature that you want to know its information and choose **_info_** option. + + +![OpenStreetMap Feature Information in InAWARE](/en/images/08-OSM-Data-Integration-to-InAWARE/01-Integrasi-OSM-ke-InAWARE/0103_osm_to_inaware.png) +

OpenStreetMap Feature Information in InAWARE

+ +### **SUMMARY** + +Congratulations! You have understand about InAWARE and how to add you field survey data into it. For more advanced analysis, you can overlay others layer with your OpenStreetMap data in InAWARE. You can look at PDC modules that provided by _Pacific Disaster Center_ (PDC) for more information about InAWARE. + diff --git a/themes/book b/themes/book index 047ab01..4908f48 160000 --- a/themes/book +++ b/themes/book @@ -1 +1 @@ -Subproject commit 047ab01783d5c714c1ea7daca305598d61fd03fa +Subproject commit 4908f487849c628dada7d370f077e256dd4ffdb8