User:Ybon/Workflow

From OpenStreetMap Wiki
Jump to: navigation, search

HAITI HOT OSM Mapping Workflow


Reference documents

I. Preparing the surveys

Editing the OSM database using available imagery over the area of interest

Aim: enhance the efficiency of your field survey by editing remotely roads, landuses and building footprints from available imagery.The Tasking Manager, a coordination tool HOT uses for remote mapping and survey, can be used in this section of the mapping process.

Using the HOT Tasking Manager

Related support doc: 

  • Intermediate OpenStreetMap, Chapter 5 "Quality Assurance" , Section II: “Tasking Manager[a]


  1.  Go to the TM website: http://tasks.hotosm.org/
  2. Login with the OSM account
  3. Select the job set up for your survey work; context about the job in the project description page.
  4. Pick up a task by clicking a grid on the map of the area of survey
  5.  Open the OSM data of your grid in JOSM
    1. Start JOSM
    2.  Make sure JOSM is well set (see Annex - JOSM settings section)
    3.  Make sure the “Remote control” function is enabled
    4.  In the Tasking Manager, click on the JOSM button in the Tasking Manager job tab,
    5. Make sure the OSM data of your TM grid shows in JOSM; alternatively, download the OSM data as a file, copy it in your working folder and open it up in JOSM
  6. Complete the task during an editing session in JOSM, refer to the edit session in JOSM in the next paragraph for detailed steps and instructions,
  7. Mark the task as done in the Tasking Manager
  8. Logout

Preparing your edit session in JOSM

Related support docs:

  • OpenStreetMap Beginner and Intermediate Guide.
  • OpenStreetMap Intermediate Guide
  • LearnOSM.org [Beginners guide (all chapters) and Advanced guide (chapters 1,2,4)]

In addition to the OSM data already opened in JOSM and showing in the JOSM Layers window, add raw GPS data and imagery that will support your editing session

  1. Download the OSM "raw GPS data".
  2.  Change colors of GPS raw data to be more visible[i]
    1. In the JOSM layers window, right click the Downloaded GPX layer, select “Customize Colors” in the menu
    2. In the “Customize Colors” window, pick a color (purple for example) and click ok</li></ol>
  3. Add Imagery. This will primarily be BING imagery, [j]other source can be used during the project
  4. Check quality of BING imagery:
    1. Turn off OSM data layer
    2. The JOSM Layers show Bing, and the OSM “Downoladed GPX Data” [k]
    3. Compare the BING imagery with GPS traces
    4. Check in the OSM wiki if an offset of BING imagery has been documented[l]
    5. Correct the offset of BING imagery using tracks so that roads in the BING image match with the GPS tracks, if enough good tracks are present:
      1. Right click Bing in JOSM Layers and select New offset
      2. Left Click continuous to shift the imagery so that roads in Bing match our tracks[m]
Watch out: the Bing imagery is not always good and this imagery checks need to be carried out at every new cluster of points from the surveyed data of your AOI.


Set zoom level (these are indicative values that can be adjusted):

  • 1/25 meters for tracing roads, see picture of the scale bar
  • Below for tracing buildings, see picture of the scale bar


You are ready for your editing session.

Editing with JOSM

For each feature node, way (ex. Road) and closed way (multi building footprints) you want to edit, you have to make sure that it is not already in the OSM database.


Related support docs:


  1. Visual check on JOSM
    Search or filter by tag key/value of the feature you want to edit (example for a school: amenity=school)
  2. Turn off filters
  3. Two cases:
    1. Case 1: the feature already exists in the OSM database
      1. Geometry: If the feature is not correctly positioned in the OSM database move it to the right location using GPS traces, and imagery - offset corrected.
      2. Attribute/Tags:
        1. Select the feature
        2. In the Properties window, check the keys and values entered for the feature
        3. If feature is tagged incorrectly compared to today methods, correct it. Ask more advanced mapper for help if needed.
    2. Case 2: the feature does not exist
      1. Geometry
        1. Draw the geometry of the feature using as support materials GPS traces and BING imagery - offset corrected.
      2. Attributes/Tags
        1. Use the correct xml preset to enter the attributes[o].
  4. Validate your edits
  5. Verify there is no selected object
  6. Run Validator by clicking on the Validation button
  7. If none of your added/edited features are highlighted, disregard
  8. If yes, correct errors with your edits
  9. Upload your features.
NOTE: try to upload often, every few features or few minutes.
    1. Add a relevant comment for your changeset, with location mentioned. If you are working with the Tasking Manager, good practice is also to add the link to the current task
    2. If conflicts with edits by other mappers, resolve the conflicts in favor of the other data. It is your fault for not uploading often enough.


Upload, Upload, Upload frequently!

Survey maps

Related support doc:

  1. CAP103 LEARNOSM APPENDIX HAITI HOT SURVEY MAPS ENGLISH

Create GPS and paper survey map (general and tasks) for vehicles (track only)

Create the map

Save paper maps in C:\00_HAITI_HOT_KIT\02_SURVEYS\0201_PLANNED\020103_MAPS with these naming conventions:

  1. date(yyyymmdd)_location_type(vehicle,survey)_format(paper,gps)_creator-name:[p]cap103[q]
  2. date(yyyymmdd)_location_vehicle_gps_creator-name:cap103[r]
  3. date(yyyymmdd)_location_vehicle_paper_creator-name:cap103
  4. date(yyyymmdd)_location_survey_gps_creator-name:cap103
  5. date(yyyymmdd)_location_survey_paper_creator-name:cap103


Print maps

Distribute maps

Take/consult maps

Save GPS maps in C:\00_HAITI_HOT_KIT\02_SURVEYS\0201_PLANNED\020103_MAPS

Load GPS maps in GPS

GPS and paper survey map (general, zone, tasks) for surveyors

Create the map with tracks and OSM data filtered by source_field_mission=yes[s];

Save paper maps in C:\00_HAITI_HOT_KIT\02_SURVEYS\0201_PLANNED\020103_MAPS with these naming conventions:

  1. date(yyyymmdd)_location_type(survey-general,survey-zone[t],task)_format(paper,gps)_creator-name:cap103
  2. date(yyyymmdd)_location_survey-general_paper_creator-name:cap103
  3. date(yyyymmdd)_location_survey-zone_paper_creator-name:cap103
  4. date(yyyymmdd)_location_vehicle_gps_creator-name:cap103
  5. date(yyyymmdd)_location_task_paper_creator-name:cap103
  6. date(yyyymmdd)_location_task_gps_creator-name:cap103

Print maps

Distribute maps

Take/consult maps

Save GPS maps in C:\00_HAITI_HOT_KIT\02_SURVEYS\0201_PLANNED\020103_MAPS

Load GPS maps in GPS.


Walking Papers (WP)

Aim: Create Walking Papers (WP) for Areas Of Interest as per surveys maps from the Tasking Manager


Related support docs:

  1. LearnOSM Beginner, Walking Papers


From the Tasking Manager, click the Walking Paper button [u]on the task you picked in the Job set for the Survey work.


Check that the extent of the WP and the Tasking Manager grid are the same. If this is not the case, In your internet browser, edit the URL of the WP to reflect the zoom level set for the job in the Tasking Manager
Create a Walking Paper with the Bing Imagery as a background

Save WP in C:\00_HAITI_HOT_KIT\02_SURVEYS\0201_PLANNED\020103_MAPS following this naming convention:

  1. date[yyyymmdd]_location_WP_imagery_creator name:cap 103


Create a Walking Paper with the Mapnik rendering as a background

Save WP in C:\00_HAITI_HOT_KIT\02_SURVEYS\0201_PLANNED\020103_MAPS following this naming convention:

  1. date[yyyymmdd]_location_WP_mapnik_creator name:cap 103]


Print WPs

Distribute WPs

Take WPs


GPS

Take GPS

Turn it on

Check batteries

Take extra batteries (2)

Check settings:

Language

Units meters, datum WGS 84, decimal degrees

Tracks

Garmin HCX Legend series

Enable tracklog (Setup>Tracks)

Enable write when full

Set interval to “time” and “1 second”

Set tracks to save to mass storage (micro SDcard)

Set Map setup - lock on road “Off” (go to Settings>Map)[v]

Garmin Etrex 20-30 series

Enable tracklog (Setup>Tracks)

Set interval to “time” and “1 second”

Set Auto Archive to Daily[w]

Delete old waypoints


Check satellite reception if accuracy is correct

Make sure last available osm map (gmapsupp file) is loaded

After survey:

  1. Stop tracking
  2. Save  track[x]
  3. Delete current track[y]

Camera

Take camera

Turn device on

Check battery

Empty memory

Check device is functioning: take picture of the GPS time for synchronization


Forms

Print survey forms

Store survey forms

Take enough survey forms for the day

Take extra white sheets of paper

Take clipboard and pen

II. Surveying

Navigate to Area Of Interest (AOI) using survey maps, WP and OSM maps on GPS

Use Where to? function to navigate through preloaded waypoint or areas (if any)


Point of Interest (POI)

Take general picture of POI if safe. Avoid include other people than the ones involved in the survey

POI with small footprint (Ex water point)

Mark waypoint

Fill in your Form and Locate on WP if the OSM map is sufficiently detailed; otherwise draw location sketch related to cross-roads, well distinct geo features

Mark POI on WP as a dot and write waypoint number on its side. Choose one only orientation for all your annotations

POI with large footprint

Single building

  1. Case 1: POI has not been traced [z]on imagery or surveyed

Mark waypoint in front of entrance of building

Fill in Form (building and other activities)

Mark POI on WP as a dot and write waypoint number on its side
Draw location sketch related to cross-roads, well distinct geo features

Mark waypoint location on sketch


  1. Case 2: POI has been traced on imagery or surveyed

Mark waypoint at entrance of building

Fill in Form

Locate POI on WP and add waypoint number

Multiple buildings fenced (Ex a school made of multiple buildings)

  1. Case 1: POI has not been traced on imagery or surveyed

Verify tracklog is enabled

Take perimeter (if any) of the POI object by walking with the device 1 m from the fence

Mark POI o[aa]n WP as a dot and write waypoint number on its side

Take perimeter of buildings and mark one waypoint for each building in the perimeter

Fill in Forms (ex: public services, buildings, water points,etc.)
Draw location sketch related to cross-roads, well distinct geo features, or locate on WP if the OSM map is sufficiently detailed

Mark waypoint location on sketch


  1. Case 2: POI has been traced on imagery or surveyed

Verify tracklog is enabled

Mark waypoint at entrance of multi buildings

Fill in Form for every building inside the fence

Locate every waypoint on WP with waypoint number. If too tight, draw a sketch for this

Activer le journal de traces

Marquer un waypoint à l’entrée de l’enceinte et pour chaque building à l’intérieur du périmètre et les marquer avec leur numéro associé respectif sur le WP

Remplir le ou les questionnaires (ex : Service d’intérêt public, bâtiments, points d’eau, etc.)[ab]

Linear Features (Roads)

Enable tracklog

Use Roads Collection form and refer to Roads Assessment guidance doc[ac]

Start recording road values for a first road stretch in the road collection form (this will be the first row of your form)

Mark a waypoint at the start of the road assessment

On the form, mark the waypoint number in the first empty line in the “From GPS point” column

Take a picture of the road

Drive (or walk) for 50 m

Fill in Roads collection form the roads attributes (name, type, practicability, surface and surface condition)

Drive (or walk) until one of the road attribute changes value(s)

Mark a waypoint

Take a picture

Make sure the change is consistent [ad]over 100 meters

  1. Case 1 : change is not consistent

Leave the road values untouched in the road collection form (your form still have only one row)

Move to the obstacle collection form (if the change of values generates a bottleneck in traffic or access restriction)

Write the waypoint number

Fill in the obstacle values (type, practicability)


  1. Case 2 : change is consistent

Write the waypoint number (from 100 meters ago) in the column “To GPS point” of the road assessment form which terminates the previous road stretch[ae]

Start recording road values for a second road stretch of the road collection form (this will be the next [af]row of your form)

Write the waypoint number in the “From” column of the road condition form which initiates a new road stretch

Tick the [ag]new road values of this new road stretch in the “Name”, “Surface”, “Road conditions” and “Open for what traffic ?” columns

Drive (or walk) until one of the road attribute changes values

Keep proceeding this way until the end of the road segments that were assigned for the road assessment

Area (ex: landuse)

Take a general picture of the area

Enable the tracklog

Two cases:

  1. Case 1: Area has not been traced on imagery or surveyed

Walk around the perimeter of the area that has been assigned to survey, take relevant waypoints

Fill in form(s)

Draw a sketch in the form with waypoints

Draw on the WP and put the main waypoints as dots with their number on their side

  1. Case 2: Area has been already traced on imagery or surveyed

Take relevant waypoints

Fill in form(s)

Draw a sketch in the form with waypoints

Draw on the WP and put the main waypoints as dots with their number on their side[ah]

Draw a sketch in the form

Put the main waypoints as dots with their number on their side

Annotate the WP[ah]


Forms

Make sure Metadata and Data are entered on the form during the survey

Metadata

- Date

- First Name, Name, OSM Name

- GPS number

III. Saving the collected Information

GPS Data

Related support documents:

  1. Beginner guide, Using the GPS
  2. Beginner guide, GPS: etrex 20Beginner guide, JOSM Plugins


Download waypoints and tracks using GPS Babel or your file explorer as gpx points and gpx tracks

Save the gpx waypoint and track file to

C:\00_HAITI_HOT_KIT\02_SURVEYS\0202_IN_COMING\020201_GPS

Use the following naming convention: 

  1. date(yyyymmdd)_location_waypoints_creator-name:cap103
  2. date(yyyymmdd)_location_track_creator-name:cap103


Open the track GPX file

Check the tracks and clean them with EditGPX

Simplify the tracks with GPSBabel[ai]

HOT/Local Technical Coordinator only: upload tracks to OSM via the OSM website or via JOSM using the plugin DirectUpload

Use the following naming convention (skip what does not fit):

  1. Country,region,city,neighborhood,road name


It is easier to use DirectUpload with only one gpx in JOSM


Forms

Write on your form the name of the gpx file that it refers to

File your forms to the archive folders

Make sure enough forms are printed for the next days, if not print and/or make copies.


Walking Papers

Write in your Walking Papers the name of the gpx waypoint file it refers to

File your walking paper to the archive folders gramped with the refering forms.


Pictures

Save your pictures to

C:\HAITI_HOT_KIT\02_SURVEYS\0201_IN_COMING\020202_PICTURES

Use the following naming convention:

  1. date(yyyymmdd)_location_pictures_creator-name:cap103[aj]

Upload relevant pictures (mostly non residential buildings) in whichever procedure applies to project:

  1. Hard Disk
  2. Web-based storage solution

Delete pictures on the memory of the camera


Equipments

Put batteries on charge



IV. Editing via JOSM

Related support docs:

  1. LearnOSM Beginner, Getting Started Editing with JOSM
  2. LearnOSM Beginner, Editing OpenStreetMap with JOSM
  3. LearnOSM Beginner, Imagery Offset 
  4. LearnOSM Intermediate, Editing in Detail
  5. LearnOSM Intermediate, Quality Assurance
  1. LearnOSM Intermediate, Conflict Resolution
  2. LearnOMS Appendix, Introduction to the HAITI HOT preset
  1. LearnOMS Appendix, Learn OSM - Appendix Checklist quality assurance
  2. LearnOMS Appendix, Learn OSM - Appendix Use Filters for data quality


Preparing your edit session

Launch JOSM

Check the following JOSM settings:[ak]


Bring in the JOSM Layers, the OSM data, the imagery and materials that will support your editing session

Open the waypoints gpx files that you collected and that you will be editing.

Download OSM data and “raw GPS data”; this is the OSM layer (file) that you will be editing using the gpx (waypoints and traces), imagery, forms, pictures and Walking Papers as support documents.

Change colors of GPS data to be more visible, use different colors for your new traces and the “raw GPS data”.

Add the BING imagery (or from another source if more relevant)

Check quality of BING imagery:

Turn off OSM data layer

The JOSM Layers show Bing, OSM tracks (vehicles), and GPS data (survey)

Compare the BING imagery with GPS traces

Check in the OSM wiki if an offset of BING imagery has been documented

Correct the offset of BING imagery using tracks so that roads in the BING image match with the GPS tracks, if enough good tracks are present:

Right click Bing in JOSM Layers and select New offset

Left Click continuous to shift the imagery so that roads in Bing match our tracks


Watch out: the Bing imagery is not always good and this imagery checks need to be carried out at every new cluster of points from the surveyed data of your Aera Of Interest.


Have your forms filled in during your data collection ready to use

Have your walking papers (hard copy) edited during your data collection ready to use[al]


Set zoom level (these are indicative values that can be adjusted):

1/25 meters for tracing roads, see picture of the scale bar

Below for tracing buildings, see picture of the scale bar


You are ready for your editing session.


Editing session

For each feature, point (POI), linear (ex. Road), area (multi building footprints) you want to edit, make sure that it is not already in the OSM database:

Visual check on the JOSM

Search or filter by tag key/value of the feature you want to edit:

example for a school: amenity=school

See [am]

Turn off filters


Two cases :

  1. Case 1: the feature already exists in the OSM database

Geometry:

If the feature is not correctly positioned in the OSM database against the localities, sketch of your form or your Walking Paper, move it to the right location using waypoints, GPS tracks, sketches and Walking Papers, and Bing imagery - offset corrected.

Attribute/Tags:

Select the feature

In the Properties window, check the keys and values entered for the feature

Compare with the values collected in your form

Add the values of your form that are not in the feature using the preset

If feature is tagged incorrectly compared to todays methods, correct it. Ask more advanced mapper for help if needed


  1. Case 2: the feature does not exist

Geometry:

Draw the feature using as support materials the waypoints, GPS traces, sketches, Walking Papers, and Bing imagery - offset corrected

The Bing Imagery (check offset) is the primary source

Your waypoints/tracks from survey helps you locating your features in JOSM[an]

Use Sketch and Walking Papesr to locate your feature against other features (POI, crossroads, landmark)

Attributes/Tags:

Use the correct preset to enter the attributes from the form used during the survey

Guidance on Amenities with Buildings

For fenced single and multiple buildings

Check that feature is not in the OSM database as per instruction above

Draw the fence or property border

Apply Landuse presets to apply appropriate landuse, as well as add a fence or wall if necessary

Place node in the middle of the grounds for the feature

Apply the amenity preset to node in the middle of the grounds

Draw each building that shares common use in this amenity

Apply Building features preset to these buildings, and specify building use in Building type. If the drop down does not contain the actual use of the building, use building=yes and write its use in the field Notes. In addition, notify the coordinators who make sure to update a Spreadsheet of building usages

For amenity or shop[ao] with one building, no ground, no shared use

Check that feature is not in the OSM database as per instruction above

Place node in the middle of the building

Apply the amenity or shop preset to node in the middle of the building

If building is not a prominent feature, do not draw [ap]and do not tag building

If building is prominent, draw building using imagery, GPS, and sketches

Apply Building features preset, if “Building type” matches, use it, otherwise, leave as “yes” and write the usage in Notes

Buildings with multi usages (different shops in one building)

Check that feature is not in the OSM database as per instruction above

Treat the fenced or unfenced buildings as per instructions above

Draw building using imagery, GPS, and sketches

Apply Building features preset. For multi-use buildings, leave Building type as “yes”

Place a node in the location of the building for a certain use, and apply relevant preset to that node.

Repeat with other nodes, placing them in their location in the building (do not place them outside the building) and applying the preset for each use

Guidance on Roads

A road has to be edited the way it has been surveyed: that is stretch by stretch.


Check that feature is not in the OSM database as per instruction above

  1. Case 1: the road already exists

Geometry:

Fix geometry of the road using imagery (imagery must be offset correctly using GPS traces)

Check if the road is not wrongly made of more than one road or street. If so, cut it at the intersections

Find the stretch of road you would like to select for feature

If way continue on past From and To points, cut the way at those points

Select (create and select non-existent) a node at the waypoint

Use the cut tool (P) to cut the way

Hold down control and select all road segments for this stretch; make sure you have not selected single nodes

Attributes:

Use the preset to tag (attribute) each road stretch accordingly to your survey (form and walking paper)

Fixing editing errors affecting the road stretch surveyed and edited:

A road (way tagged highway=*) can only intersect with roads: fix errors (roads connected to a building or a landuse feature)

A road has to intersect with other roads through a common node:

Have draw tool activated

Double click on intersection of ways

  1. Case 2: the road does not exist

Draw a road stretch from the first road waypoint surveyed to the second waypoint surveyed. Avoid U shapes: cut at intersections

Make sure that your road stretch intersects with other roads through a node:

Simply make sure to place a node on intersecting routes while drawing

Use the HOT preset to tag (attribute) each road stretch accordingly to your survey (form and walking paper)

Validate your edits

Related support docs:

  1. LearnOSM Intermediate, Editing in Detail
  2. LearnOSM Intermediate, Quality Assurance
  1. LearnOSM Intermediate, Conflict Resolution
  2. LearnOMS Appendix, Learn OSM - Appendix Checklist quality assurance
  1. LearnOMS Appendix, Learn OSM - Appendix Use Filters for data quality


Verify there is no selected object

Run Validator by clicking on the Validation button

If none of your added/edited features are highlighted, disregard

If yes, correct errors with your edits

Upload your features

If conflicts with edits by other mappers, resolve the conflicts.

Upload


When done editing with JOSM, move gpx files

From C:\00_HAITI_HOT_KIT\02_SURVEYS\0202_IN_COMING\020201\GPS

To  C:\00_countryname_HOT_KIT\02_SURVEYS\\0203_PROCESSED\020301_GPS


V. Quality Control

Related support docs:

  1. LearnOSM Intermediate,[1]Editing in Detail
  2. LearnOSM Intermediate,[2]Quality Assurance
  1. LearnOSM Intermediate,[3]Conflict Resolution
  2. LearnOMS Appendix,[4]Learn OSM - Appendix Checklist quality assurance
  1. LearnOMS Appendix,[5]Learn OSM - Appendix Use Filters for data quality


At the end of your editing session after your upload, run a quality control over the OSM data that you edited using JOSM Validator and Osmose.  


For a quality assurance process using JOSM filters and Validator to evaluate a Tasking Manager square, see LearnOSM Appendix Checklist Quality Assurance

JOSM filters

Related support document:

  1. LearnOSM Appendix Use Filters for Data Quality


The JOSM filters allow to check the data according to personal queries, so they are very useful to check specific tags or objects. See the support document for more information and concrete examples.


JOSM Validator

It is the first level of quality control. It should be processed before any upload of edits.


Related support documents:

  1. OSM wiki section of the JOSM Validator[aq]


Launch JOSM

Download the OSM data covering the area that you edited

Click the blue check mark symbol in the left side bar (or ctrl+shift+v)

Validation Results box opens on right side

Run the Validation button is the box if nothing is shown

Issues can be divided in errors, warnings and other, depending on their severity

Click the plus mark on the lists to expand the Validation Results

Expand folders you want to investigate by clicking the + symbols

Pick a feature in the folder and right click “Zoom to Problem” to have JOSM focus on and highlight the problem feature

Fix according to what the issue was (refer to the list of types of errors already documented in the project)

Click-right on an issue then to Zoom to problem to figure out what it is. Some of them can be automatically fix by clicking on the Fix button


Among the most important errors:

  1. Duplicate ways
  2. Duplicate roads, paths, etc
  3. Duplicate nodes

Always fix


Among the warnings:

  1. Unnamed ways

Only add street names when existing.

  1. Crossing buildings

Everything must be fixed

  1. Way end node near other way

Check there is no missing intersection between the two ways

  1. Crossing ways

Two ways crossing each other without any intersection. To be fixed most of cases

  1. Crossing waterway/highway

The information regarding if there is a ford or a bridge is missing. To be always fixed.

  1. Untagged ways

An object must always have attributes. To be always fixed.

  1. No tags - Unconnected nodes without physical tags

An object must always have attributes. To be always fixed.


If your error is not documented, then call for a discussion with supervisor & coordinators, so that the error is documented and known by all

Shall you have any doubt, call for support from team, supervisor and coordinators

If no fix is necessary, disregard and continue on


Osmose

Osmose is a data quality tool for the OSM database. The system checks data once a day, specific analyses allow for highlighting errors by type. For example: wrong tag, wrong value for a given tag, crossing building and roads... Errors are then visible on a map


Related document

  1. Osmose documentation (OSM wiki): http://wiki.openstreetmap.org/wiki/FR:Osmose


Step by step

1. Go to Osmose: http://osmose.openstreetmap.fr/fr/byuser/

2. Enter you OSM user name in the right field and validate the form

3. On the new page, click “Display the errors on a map"

4. On the map, click a marker, this will open a call out box

5. On the call out box, click on “josm zone” (JOSM must have been started previously and the remote "control" must be active)

6. Fix the error on JOSM

7. Get back to the call out box in Osmose, and, click on “Fixed”


Detail on Osmose Callout box File:Images/image02.png



Technical Annexes

Setting up JOSM

Related document

  1. Beginner guide, Getting Started with JOSM
  2. Beginner guide, JOSM Plug ins


Ensure that the following settings are there:

Make sure you are using the latest version of JOSM

Make sure you are signed in as you personal OSM account; do not save your login while uploading.

Make sure that the geographic Projection method is in WGS 84

Make sure that you are using the last version of the preset

Make sure that the Remote Control feature is enabled

Make sure that the following plugins are enabled:

  • Building_tools
  • DirectUpload
  • Editgpx
  • Measurement
  • mirrored_download
  • Utilsplugin2
  • Walking Papers
  • Photo_geotagging
  • Geotools