From f3b4abfdce617f3be45a2f8415e6bc6ac4d89a90 Mon Sep 17 00:00:00 2001 From: tatsvc Date: Thu, 14 Apr 2016 13:47:15 -0400 Subject: [PATCH 01/66] fixing svg css --- site.css | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/site.css b/site.css index 9c1047e..51f7674 100644 --- a/site.css +++ b/site.css @@ -62,6 +62,10 @@ h1, h2 { font-size: 30px; } +svg { + width: 100%; +} + /* Colors ------------------------------------------------------- */ From 8404ec759328c338d0d95303fffc3ae9bdfd5687 Mon Sep 17 00:00:00 2001 From: Katy DeCorah Date: Thu, 14 Apr 2016 13:58:02 -0400 Subject: [PATCH 02/66] clean up mb-pages --- CONTRIBUTING.md | 2 + JOSM/data-qa.mapcss | 44 - JOSM/scripts/combine-highways/README.md | 29 - JOSM/scripts/combine-highways/index.js | 185 - JOSM/sessions/README.md | 5 - JOSM/sessions/basic.jos | 84 - JOSM/sessions/india_gns_places.jos | 95 - JOSM/sessions/japan.jos | 94 - JOSM/sessions/sidewalks.jos | 66 - JOSM/sessions/team_edits.jos | 104 - JOSM/tasks-config/josm-config-turnlanes.json | 70 - Studio/styles/osmlint-dark.json | 4150 ------------------ 12 files changed, 2 insertions(+), 4926 deletions(-) delete mode 100644 JOSM/data-qa.mapcss delete mode 100644 JOSM/scripts/combine-highways/README.md delete mode 100644 JOSM/scripts/combine-highways/index.js delete mode 100644 JOSM/sessions/README.md delete mode 100644 JOSM/sessions/basic.jos delete mode 100644 JOSM/sessions/india_gns_places.jos delete mode 100644 JOSM/sessions/japan.jos delete mode 100644 JOSM/sessions/sidewalks.jos delete mode 100644 JOSM/sessions/team_edits.jos delete mode 100644 JOSM/tasks-config/josm-config-turnlanes.json delete mode 100644 Studio/styles/osmlint-dark.json diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e387c82..d760780 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,4 +1,6 @@ +The mapping guides are hosted on the `mb-pages` branch of this repo only. Please make pull requests from `mb-pages`. + Please read through this contributing guide to learn how /mapping is built. ## Structure diff --git a/JOSM/data-qa.mapcss b/JOSM/data-qa.mapcss deleted file mode 100644 index 62cb199..0000000 --- a/JOSM/data-qa.mapcss +++ /dev/null @@ -1,44 +0,0 @@ - -meta { - title: "Created in 2015 year"; - description: "Highlights features that were created/modified in 2015 year"; - author: "Mapbox"; - watch-modified: true; - version: "0.1"; -} -meta[lang=uk] { - title: "Створено у 2015 році"; - description: "Підсвічує об’єкти, створені/змінені у 2015 році"; -} - -meta[lang=ru] { - title: "Создано в 2015 году"; - description: "Подсвечивает объекты, созданные/изменённые в 2015 году"; -} - - - -*|z-12[eval(JOSM_search("timestamp:2015/today"))] { - casing-width: 4; - casing-color: lime; - casing-opacity: 0.2; -} - -*|z13-18[eval(JOSM_search("timestamp:2015/today"))] { - casing-width: 5; - casing-color: lime; - casing-opacity: 0.2; -} - -*|z19-[eval(JOSM_search("timestamp:2015/today"))] { - casing-width: 10; - casing-color: lime; - casing-opacity: 0.2; -} - - -*|z10-15[eval(JOSM_search("modified"))] { - casing-width: 10; - casing-color: lime; - casing-opacity: 0.1; -} diff --git a/JOSM/scripts/combine-highways/README.md b/JOSM/scripts/combine-highways/README.md deleted file mode 100644 index 878b93a..0000000 --- a/JOSM/scripts/combine-highways/README.md +++ /dev/null @@ -1,29 +0,0 @@ -# Combine OSM highways - -The script allows us to combine highways which are: - -- Highways with version <=3 -- Highways tagged as `motorway,trunk,primary,secondary,tertiary` -- Highways with similar direction -- Highways with similar tags -- Highways which are not part of any relations -- Highway intersections with an angle of > 150 && < 210 degrees - - -##### How to set up - -Use JOSM > v8945, install [Scripting plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Scripting). - -Activate JOSM support engine for *ECMAScript* - -![d5450ba8-7cb9-11e5-8a82-05d0808ff381](https://cloud.githubusercontent.com/assets/1152236/10770537/d5450ba8-7cb9-11e5-8a82-05d0808ff381.png) - -##### How to use the script - -Load the [index.js](https://github.com/mapbox/mapping/blob/master/JOSM/scripts/combine-highways/index.js) from **Scripting > Run** - -![scripting](https://cloud.githubusercontent.com/assets/1152236/11653643/88bb9bee-9dc5-11e5-9e96-5df06fe697ca.gif) - -Once loaded, you can use the script again from the list of loaded scripts, in the **Scripting** menu. - -![scrpting2](https://cloud.githubusercontent.com/assets/1152236/10769851/23146d82-7cb6-11e5-83a3-230051669cba.gif) diff --git a/JOSM/scripts/combine-highways/index.js b/JOSM/scripts/combine-highways/index.js deleted file mode 100644 index 106031b..0000000 --- a/JOSM/scripts/combine-highways/index.js +++ /dev/null @@ -1,185 +0,0 @@ -var util = require("josm/util"); -var cmd = require("josm/command"); - -var num_ways_actual = 0; -var num_ways_combined = 0; -var is_counting_ways = true; -var relation_ways = []; -var relation_nodes = []; -var endnodes = []; -var interways = []; -var interways_id = {}; -//type of roads to take account -var preserve_type = { - "motorway": true, - "trunk": true, - "primary": true, - "secondary": true, - "tertiary": true -}; - -var avoid_tags = [ - "yh:LINE_NAME", - "yh:LINE_NUM", - "yh:STRUCTURE", - "yh:TOTYUMONO", - "yh:TYPE", - "yh:WIDTH", - "yh:WIDTH_RANK", -]; - -function relations() { - var layer = josm.layers.activeLayer; - if (layer == null) return; - var ds = layer.data; - var result = ds.query("type:relation"); - for (j = 0; j < result.length; j++) { - var relation = result[j]; - var members = relation.members; - for (var i = 0; i < members.length; i++) { - if (members[i].isWay()) { - var way = members[i].getWay(); - relation_ways.push(way.id) - } else if (members[i].isNode()) { - var node = members[i].getNode(); - relation_nodes.push(node.id) - } - }; - } -} - -function skip_ways(way) { - var check = []; - check.push((relation_ways.indexOf(way.id) < 0) ? true : false) - check.push(preserve_type[way.tags.highway] || false); - check.push(way.tags.bridge || true); - check.push(way.tags.tunel || true); - check.push((way.tags.layer || true) ? true : false); - check.push((way.version <= 3) ? true : false); - return (check.every(function(a) { - return a == true - })); -} - -function ways() { - var layer = josm.layers.activeLayer; - if (layer == null) return; - var ds = layer.data; - var result = ds.query("type:way"); - for (j = 0; j < result.length; j++) { - var way = result[j]; - if (skip_ways(way)) { - var w = { - way_id: way.id, - first: [way.getNode(0), way.getNode(1)], - last: [way.getNode(way.nodesCount - 1), way.getNode(way.nodesCount - 2)] - }; - endnodes.push(w); - } - } -} - -function find_angle(Nlast, Nfirst) { - //A first point - //C second point - //B center point - var coordsA = Nlast[1].getCoor(); - var A = [coordsA.getY(), coordsA.getX()]; - var coordsB = Nlast[0].getCoor(); - var B = [coordsB.getY(), coordsB.getX()]; - var coordsC = Nfirst[1].getCoor(); - var C = [coordsC.getY(), coordsC.getX()]; - var pi = 3.14159265; - var AB = Math.sqrt(Math.pow(B[0] - A[0], 2) + Math.pow(B[1] - A[1], 2)); - var BC = Math.sqrt(Math.pow(B[0] - C[0], 2) + Math.pow(B[1] - C[1], 2)); - var AC = Math.sqrt(Math.pow(C[0] - A[0], 2) + Math.pow(C[1] - A[1], 2)); - return Math.acos((BC * BC + AB * AB - AC * AC) / (2 * BC * AB)) * (180 / pi); -} - -function equal(x, y) { - var x_keys = []; - var y_keys = []; - if (x && y && typeof x === 'object' && typeof y === 'object') { - x_keys = Object.keys(x); - y_keys = Object.keys(y); - x_keys = Object.keys(x).filter(function(k, i) { - if (avoid_tags.indexOf(k) < 0) { - return Object.keys(x)[i] - } - }); - y_keys = Object.keys(y).filter(function(k, i) { - if (avoid_tags.indexOf(k) < 0) { - return Object.keys(y)[i] - } - }); - } - return (x_keys.length === y_keys.length) && (x_keys.length !== 0) && (y_keys.length !== 0) ? - x_keys.reduce(function(isequal, key) { - return isequal && equal(x[key], y[key]); - }, true) : (x === y); -} - -function merge() { - var layer = josm.layers.activeLayer; - if (layer == null) return; - var ds = layer.data; - for (j = 0; j < endnodes.length; j++) { - var aw = endnodes[j]; //actual way - for (var i = 0; i < endnodes.length; i++) { - var sw = endnodes[i]; //sw = second way - if (aw.way_id !== sw.way_id) { - if (aw.last[0].id === sw.first[0].id) { - var angle = find_angle(aw.last, sw.first); - if (angle > 150 && angle < 210 && equal(ds.way(aw.way_id).tags, ds.way(sw.way_id).tags)) { - interways.push([aw.way_id, sw.way_id]); - interways_id[sw.way_id] = [aw.way_id, sw.way_id]; - } - } - } - } - } - - if (is_counting_ways) { - num_ways = interways.length; - is_counting_ways = false; - } - var z = interways.length; - while (z--) { - for (var key in interways_id) { - for (var i = 0; i < interways.length; i++) { - if (interways_id[key] !== undefined) { - if (interways_id[key][interways_id[key].length - 1] === interways[i][0]) { - interways_id[key].push(interways[i][1]); - delete interways_id[interways[i][0]]; - interways[i] = []; - } - } - } - } - } - - for (var key in interways_id) { - var ways = []; - for (var i = 0; i < interways_id[key].length; i++) { - ways.push(ds.way(interways_id[key][i])); - }; - cmd.combineWays(ways); - } -} - -relations(); -//Execute the script -var exe = true; -while (exe) { - ways(); - merge(); - if (interways.length > 0) { - exe = true; - interways = []; - interways_id = {}; - endnodes = []; - } else { - josm.alert(num_ways + " highways were combined into " + josm.layers.activeLayer.data.query("modified type:way").length); - exe = false; - } -} \ No newline at end of file diff --git a/JOSM/sessions/README.md b/JOSM/sessions/README.md deleted file mode 100644 index f103139..0000000 --- a/JOSM/sessions/README.md +++ /dev/null @@ -1,5 +0,0 @@ -#JOSM Sessions - -JOSM sessions allows you to pre-load various layers within JOSM similar most GIS software (in QGIS we call it a project file). More information about using JOSM session [here](https://github.com/mapbox/mapping/wiki/Saving-and-loading-a-JOSM-session) - -Within this directory are several session configuration files (`.jos`) we use. diff --git a/JOSM/sessions/basic.jos b/JOSM/sessions/basic.jos deleted file mode 100644 index 4a22ee9..0000000 --- a/JOSM/sessions/basic.jos +++ /dev/null @@ -1,84 +0,0 @@ - - - -
- - - - - Strava running heatmap - strava_running_heatmap - tms - http://globalheat.strava.com/tiles/running/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - Strava cycling heatmap - strava_cycling_heatmap - tms - http://globalheat.strava.com/tiles/cycling/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - OpenStreetMap GPS Traces - osm-gps - tms - https://gps-{switch:a,b,c}.tile.openstreetmap.org/lines/{zoom}/{x}/{y}.png - © OpenStreetMap contributors, CC-BY-SA - https://openstreetmap.org/ - 20 - true - true - true - 0.0 - 0.0 - - - Mapbox Satellite - Mapbox - tms - http://{switch:a,b,c}.tiles.mapbox.com/v4/openstreetmap.map-inh7ifmo/{zoom}/{x}/{y}.png?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcCIsImEiOiJncjlmd0t3In0.DmZsIeOW-3x-C5eX-wAqTw - 19 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAYAAADgdz34AAAYJWlDQ1BJQ0MgUHJvZmlsZQAAWAmteXk4ld3X/77PfUbzPGU4Zhkyz5nnISRzxDHPwzEkyZRHhYpIRKSkECpzJUWSSBqQokgyJFNJUrxbTz3P93u9v/e/331d5z6fs/baa6+91tp77bUPADz1lPDwYAwTACGhUVRbE32yk7MLmTACSIAL0IMdgJ7iFRmuZ2NjCf7P5+sgQLYan8tsyfo/2f7fDczePpFeACA2sNnTO9IrBOJ6ANBmr3BqFAC4LXki+6PCt3AWxGxUqCDEZVvY72/cvIU9/8a9v3jsbA0gzxgARDoKheoHAP0cpJNjvPygHAY6APAsod4BobAbGWJtL3+KNwA8HpBHOiQkbAtnQizh+R9y/P4DUyie/8ikUPz+wX/PBfaEAxsGRIYHUw78+vH/8xUSHA3t9evhh2+6yKA9FvCbA9ot1otitAdiLohP+PuYWf6ml4dH6dv+pt8OiDKzg5gN8rzwjza1/42no4Ps9SDmhfQfQWEWW/zQThiuUE8ra4hZIBbxijSAtt8aC6MS52/n+JvH0tvH0AhiGEUYJ2qY7R9+/8iYPX/ocXH+BlZ/+AMp5lv+ZoD86RQqRL/0weT7BJtsjSsE6VfDo2y29Nwaqy802Or3XDDvfanGWzxb9O8+kb/mu6Wbf5S/nSmkQ51Rpiiq3RYPnCPK6xtgbAYx1A2V86ea/qHrhgf/imnYF7WjRttu2UEEYl+fUPstG27R070phlu2hTZBi4AxoAAq8AGeIBTMADKwBAbA8PebDOmhkOYFwkAw/FDJjH9acB9wT3HvcAO4MdzwHxrs+ZsPBABviP+W9R/9IX0PiAOfoFQfEPlnNCwPVhuribWEb134UcCqYdX/tPXNNc39wb919YN9ZX7L1v+tfQyU+PMPn3tACvUP/t3H858e/1snY/AeWsDvD4dcldyM3I8//f+dMd4Ib4g3xRvjt6NH0Tq0C72HdqO30SZARtvQZrQXbd3Cv/X6MwoFUrassmXhSGABregDon/9Cv0z3n9ZKfofjt8SGCQZlIEt7BUKgmBbwD8jOPzSOuB/SYmGHJ5wxEDIa/GPP37rhRWD1lXG6mO1oJ2hjbEcWB4gg1WCFtfD6kAfKEPqv17879nIAN9f1o75NZcg8AHOIyTKJzYKxhIwCAs/QA3w848i68Hd0keabBbqtUOarCAnrwC29t4tHgA+2/7aUxGOJ//SqC0A7NSCsbjyL82DB4A6uC8yh/xLE0FhuCsC0PrIK5oa87c87NYXDtAARrgquAE/EAYS0CIKQAVoAl1gBMyBNbADzmAfjGF/EAI13g/iQTJIAxkgC5wGZ0EJuAiugGpwAzSB2+AeeAB6QD8YAK/BGJgEH8Ei+ArWEQQhIPQIK8KNCCCiiBSigKgh2ogRYonYIs6IB+KHhCLRSDxyGMlATiFnkVKkArmOtCD3kG7kKTKMjCMzyDLyHYNi6DBsGD6MGEYWo4bRw1hg7DBuGD9MBCYOk4o5gcnHXMBcxTRi7mF6MAOYMcxHzAoKUFqUAxVEZVA11AC1Rl1QX5SKJqDpaB56Aa1Bb8JYfI6OoXPoGhaPZcWSsTLQk6ZYe6wXNgKbgM3EnsVewTZi72OfY8exi9gNHD2OFyeF08CZ4Zxwfrj9uDRcHq4c14DrhOt5EvcVj8dz4MXxqjDanfGB+IP4TPw5fC3+Lv4pfgK/QiAQuAlSBC2CNYFCiCKkEQoIVwlthGeEScI3Ii1RgKhANCa6EEOJKcQ8YiXxDvEZcYq4TmIiiZI0SNYkb9IB0klSGekm6QlpkrROw0wjTqNFY0cTSJNMk09TQ9NJM0LzmZaWVohWnXY3bQBtEm0+7TXah7TjtGt0LHSSdAZ0rnTRdCfoLtPdpRum+0xPTy9Gr0vvQh9Ff4K+gr6D/g39NwZWhh0MZgzeDIkMhQyNDM8Y5hlJjKKMeoz7GOMY8xjrGJ8wzjGRmMSYDJgoTAlMhUwtTENMK8yszPLM1swhzJnMlczdzNMsBBYxFiMWb5ZUlossHSwTrCirMKsBqxfrYdYy1k7WSTY8mzibGVsgWwZbNVsf2yI7C7sSuwN7LHsheyv7GAfKIcZhxhHMcZLjBscgx3dOPk49Th/OY5w1nM84V7m2cely+XClc9VyDXB95yZzG3EHcWdzN3GP8mB5JHl28+znKebp5JnbxrZNc5vXtvRtN7a94sXwSvLa8h7kvcjby7vCx89nwhfOV8DXwTfHz8Gvyx/In8t/h39GgFVAWyBAIFegTWCWzE7WIweT88n3yYuCvIKmgtGCpYJ9gutC4kL2QilCtUKjwjTCasK+wrnC7cKLIgIiu0TiRapEXomSRNVE/UXPiHaJroqJizmKHRFrEpsW5xI3E48TrxIfkaCX0JGIkLgg8WI7frva9qDt57b3S2IklSX9JQsln0hhpFSkAqTOST2VxkmrS4dKX5AekqGT0ZOJkamSGd/BscNyR8qOph3zsiKyLrLZsl2yG3LKcsFyZXKv5VnkzeVT5G/KLytIKngpFCq8UKRXNFZMVGxWXFKSUvJRKlZ6qcyqvEv5iHK78k8VVRWqSo3KjKqIqodqkeqQGpuajVqm2kN1nLq+eqL6bfU1DRWNKI0bGguaMppBmpWa0zvFd/rsLNs5oSWkRdEq1RrTJmt7aJ/XHtMR1KHoXNB5pyus661brjult10vUO+q3ry+nD5Vv0F/1UDD4JDBXUPU0MQw3bDPiMXI3uis0RtjIWM/4yrjRRNlk4Mmd01xpham2aZDZnxmXmYVZovmquaHzO9b0FnssThr8c5S0pJqeXMXZpf5rpxdI1aiVqFWTdbA2sw6x3rURtwmwubWbvxum92Fuz/YytvG23btYd3jvqdyz1c7fbuTdq/tJeyj7dsdGB1cHSocVh0NHU85jjnJOh1y6nHmcQ5wbnYhuDi4lLus7DXae3rvpKuya5rroJu4W6xb9z6efcH7Wt0Z3SnudR44D0ePSo8fFGvKBcqKp5lnkeeil4HXGa+P3rreud4zPlo+p3ymfLV8T/lO+2n55fjN+Ov45/nPBRgEnA1YCjQNLAlcDbIOuhy0GewYXBtCDPEIaQllCQ0KvR/GHxYb9jRcKjwtfCxCI+J0xCLVgloeiUS6RTZHscFDbm+0RPRf0eMx2jGFMd/2O+yvi2WODY3tPSB54NiBqTjjuEsHsQe9DrbHC8Ynx48f0jtUmoAkeCa0JwonpiZOJpkkXUmmSQ5Kfpwil3Iq5cthx8M3U/lSk1In/jL5qyqNIY2aNnRE80jJUezRgKN9xxSPFRzbSPdOf5Qhl5GX8SPTK/PRcfnj+cc3T/ie6DupcrI4C58VmjWYrZN95RTzqbhTEzm7chpzybnpuV9Ou5/uzlPKKzlDcyb6zFi+ZX5zgUhBVsGPs/5nBwr1C2uLeIuOFa2e8z73rFi3uKaErySj5Pv5gPMvS01KGy+IXci7iL8Yc/FDmUNZ1yW1SxXlPOUZ5T8vh14eu2J75X6FakVFJW/lySpMVXTVzFXXq/3VhtXNNTI1pbUctRnXwLXoa7PXPa4P3rC40V6nVldTL1pf1MDakN6INB5oXGzybxprdm5+2mLe0n5T82bDrR23Lt8WvF3Yyt568g7NndQ7m21xbSt3w+/O3fO7N9Hu3v66w6njxf3d9/s6LTofPjB+0NGl19X2UOvh7W6N7pZHao+aelR6GnuVexseKz9u6FPpa3yi+qS5X73/5tOdT+8803l277nh8wcvzF70DFgNPB20H3w55Do09tL75fRw8PDSq5hX66+TRnAj6aNMo3lveN9ceLv9be2YyljruOF477s9715PeE18fB/5/sdk6gf6D3lTAlMV0wrTt2eMZ/pn985Ofgz/uD6X9on5U9G8xHz9gu5C76LT4uQSdWlzOfMz9+fLX5S+tK/YrLz5GvJ1fTX9G/e3K2tqa13fHb9Pre//QfiR/3P7z5sbFhsjmyGbm+EUKuXXWQCeDgDG1xeA5cuwLnIGgLUfABqGv2ujXxzwiIFAHoix8LQgB1xADhiBuTwRGcfYY4ZRPyyKbcBF4jUIdIQ54gipl6ad9j5dF/1jhiEmReYSVla2Y+wbnAncKE8qLzNfqYAy+aGQrwhBtEp8j8SGZLW0q8ysbIDcrIKf4riys0qPmqp6iSayc6/WNR1E11ovV/+1Ib/RbmMPkzDTJLNs84sWDZbdu0atlm2Iu8m2anus7fztDzuUODY59TlP70Vcud0U91m6e3scpOR6Vnm1ew/7LPnR+PMFSAeqBRkH24VQQsPCDoYfjcillkZejWqJvh/zdP/r2DcHxuPeH5yKnzk0mzCX+ClpPnk+Zf7wfOrCXwtpn47MHp0+NpU+nfExc+H41xObWTTZnKfEclRyzU775GWeqc9/VbBZKFRkcI5SfKgk//z10u4Lby+uXCKV81yWuqJRYVbpWOV1Naz6QE0KjNjc60U3yura6kcb1pqYm0VblG/q3jK+bdpqfEe3Tf2u3D3ldpuOgPtJnbkPyrpqHzZ0Nz2q76npLXtc0Jf+JK4/4KnjM8Pn8i94B/AD84ODQ7dfXhg+8sr/tfGI0Mjm6Miblrd5Y1Hjtu/kJhgnPr3vnSz5EDilMLU63TRDnZWYffkxeU50rvOTx6f1+dIFs4XPiyVLlks/lms+U75wfulbOfJV7evIqvNq/zfrb8/XAr/Tfu9Zv/yj+Gf1xpPNTeh/FNZTvEAZOIIU0Ai+IPpIEQaDicIso/FYFuxNXDA8/cwSGoiHSU40KrTMtEv0JAYlRg+mDOY7LN/ZFNijOW5x0XA78VzlJfD58HeTdwjmCKMioaL94vIS6dvfS+2UzpaZkN0hFynfoLCgJKZsp5KsWqnWr/5Zk2YnuxaftrCOhK6Mnry+vIGcoayRjLGEiZAprxmnOZMF0eKH5dKuKasR62c2j3a3297a02BXY1/hUOZ43qnIOd8ld2+m619uh/bFuId5+FPcPR28dnkb+mj4yvmJw9hgDkQDV4KmgodDekJbw2rCSyKyqMmREVGUaNsYg/1ysXwHSAe+wvh4Gt92qCahOPFEUlIyNcXnsEuq/V/OafuOeB71PRaYHpwRmhl2POJE5MmorJjsA6cSclJyj5zOzDt55lR+bsHps3mFZ4ryzxUUF5acO3+ttPPC0MXpstVyzGXaKywVXJW8VeSrwtUSNcq1lte8rsfdOFl3sb6u4V5jb9OL5uGW1zdHb727vX6HrU3mrtE91/aIjsP3czrPP6jqqnt4s7v10Z2eu72dj3v6Bp686196hj7nfCEzYDjoOhT4MmI49lXy6/SR06Olb2rf3hl7Mj72bvk9Oomd3PywDiPjy8zy7NLHpbnlT1/mVxfWl5Blxs9CXzRXXL8eWb2zhvluv17/k28j85f/MYAIK2FhoA7sYT1wHjxB8Igjch3DgUlDEfQ4VgT7ABeC34bvJRwiKhLnSJU0ybRhdBR6RwYrRjMmM+ZdLHasHmzh7GkcxZwtXC+517cJ8ZrxhfFnC1wldwm+E1oXYREVFVMQ3ylhuN1YUh/Gg4KM6A5OWZzsotxL+XsKFYqnlA4q+6hYqaqpCarTqH/WeKP5cOcNrSLtFB03XUU9kt5b/XqDY4ZuRvLGWONBkwrTg2ZW5gLmSxYdlrm7fK3UrOmsx22adp+w9dmjbcdht2j/yOGSY5KTi7O8C9Hl7d5G1+Nu3vs03Zndpz3aKHmeoV7G3vzen30e+hb7RfqbBvDBfP4gqDA4PMQolCd0IawzvDAikmoeKRS5FtUfXR4Tv98mViT224HeuJKD1HjF+IVDVQlBiQqJm0nPk2tSsg4fSPX/a2+a7RGLo4bHdqYrZUhmChxnOv7zxIeTPVlV2UdOueco5fKf5ssjnxHNlyyQO6taqFNkcs662LHE/bxfqd+FvRd3lelf0ihXuaxyZWeFSaVzVfjVjOqqmse189cZbkjXmdf7NhxuLGm61fyy5estjtuqrV538tse30PaFTu87p/sbH4w2rXRzfdIo8et91of75Nj/V+feT9/NqA3eP2l0HDua/xI7BvhMa133u/Pf1idCZtjnB9ZervC8y3jh/SW//++I9vKCXgVAEqHAHCgAcCqB4DiYQBEmQFghLWnDT0AduoAU+4LMDRa8Bpq9z/5gw3WmEawpowBJ0EF6ACjYA3hQBRhLUhFcpCryANY7/3AcGGUMLaYMFjVXcX0YuZQOljBWaHhaA7aiA6jP7GCWGNsEDYb24R9g8PhZHD2uCRcLe4tngmvh4/CX8GPElgJFoRUWFutE9WJB4i3iJskQ1ImaYBGkCaU5jYtPa0X7QM6KbpsujV6T5il1BkuM3IwHmFcYwpmGmd2Yu5nMWPpYNVlvcumx9bBbsLex2HP8ZYziHON6yg3D3c1jwHPq21UXjrear7dfN/4zwuYC6ySLwk6CJGE7ghHi8iKzIpeEfMTlxBflmjbfkLSXUpRmkZ6QubOjnOyCXIUeRMFWUVuJbzSmvInlXeqL9X61B9otGo27KzWuqRdrHNGN1svQz/ewN/QwcjEWNNEwVTaTNJc2kLeUmOXsZW9tZ9N/O4c2xt7ntl9deB1NHaKdC5zeenK5Ga+76j7Qwqtp41Xsvd1n0k/fv99AWWBy8GmIZfDGMIPRSxHhkR9itHafzL2Q5z+wUuHGBKSEteTEw/TpV5I0z3y/lhWhn7m2om6rMhTarno6RdnKgvSCn3PmZfolupc1L1kdNmywqHKs5pam3q9oO56w0Kz+c26VsW2J+3ZnYkPC3oG+8afjr4YHOp6dX309FjUhM2HnI/kBZ3l2yvnvtF+V/2hsSH6a/8QAnrAAySCc/DGYAT8RMiIARKAZCHXkH5kCdb3qpi9mETMJVjDL6HcqC4agJ6CN0UfsMzYnVh/7GlsB3YJJ4Czhv6ux03j+fEO+BP4hwSUoEtIILQRMbB+Pk4cIgmRIkj3aNhoAmju0vLQxtGO0ZnS1dGT6U8yIAwxsKb1Z5xk8mGahhXrF5YEVlrWc2xybJ3sbuxfObI4ZTh7uIK5Gbhv8DhtA9sqeR34iHy3+CMEtgtMkM8LeggJC00LXxM5KGoqxik2I35XonB7rKSTlIa0gAxBZnnHmGy/3H35mwo3FKuVapXrVG6p3ofZ643G/E6gxaotoaOt66AXpp9scNyw0Kja+J7JS9PPMHfJWdru2m9VbN1ls2TLu8fMLta+0uGtE5eznUvO3gE3nn0U90qPFU89r3jvRp8VP1X/xIDeIIHgmJDnYYrhZyI2Iv2insaI74+PHYiTO5gV/yVhX+LjZIOUtlT9v3qOOB2dTnfKeHRc50Rjlnz2tRzl3Dt5VmcmChILBYu6iqPPS5W+vZhzyah85crFSuuqteqLMPus3CipN29kaxprqbkV32rexn13qr3xfuoD24dC3cs9HY8bn7Q8bXveOdA7NDA8+vrD6OLb7+9w75k/bJvmmWWZw3yaXuhYyv5su4L7WvXNZO3Vut+PpY3YX/5XAnvhHdIl0A0WEE54eghDziGdyDxc8YbwJqcE04fZQGVRClzpXeg6Vh7rhy3GDuIYcebwpuUBnoi3wGfhhwhkQjDhFpGeSCG2kNhJUaQheA9STstKmwpvOsLoZui96d8xeDJMMgYyLjPFMxOZz7BIsNxmdWXDstWwu3IwcHRwxnOpc61xt/KkbrPm5eWd5+vgPysQSd4lKAnX8Kxwn0idaKFYmniUROB2T8l9Um7S7jI+O0Jl4+SOyRcqXFPsUppSIanuUHNUT9Wo15zWEtB21snTHdTnNnAzLDOaN9EyzTKbtjCyLLeitY62mbDdbydg3+po7TTgYr231U1oX4r7KEXV86TXnI+Fb60/Z0Ba4EZwUih9WHmEJXUjqiVGaf+lA1xxmfHgUEzCpyTf5PHD+1LfpHnAVRoPM8bLE6lZMtnPcsJPk/IK88ULagoViuqKFUqaSrUuPCyzvzR1+WAFS2XVVePqd7UJ17fdaK63axhp8myevRlzG99a0KZw92l7zH2hzhddmd3mPXS9LX18T5L6J5+ZP782wDmYODQ9vPvVrRGx0ew3P8eCxocnTN83Ta5+WJv6Nr0yszA79XF4rvtT/fzZhfhF5yX5Zdzys8/nvnisCMOqI2/VYnX9W+Wa7dra95J17fXRH/E/2X/WbBhvDG8Gb/k/0ldRYSt7AIROH14/vtnc/CwGAOEUAD+zNzfXL2xu/rwID5kjANwN/vt/ly1mPLyrL4I5BoDO5K2/dv77+R8P0NEUOETYwgAAAAlwSFlzAAALEwAACxMBAJqcGAAAA1NpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IlhNUCBDb3JlIDUuMS4yIj4KICAgPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6ZXhpZj0iaHR0cDovL25zLmFkb2JlLmNvbS9leGlmLzEuMC8iPgogICAgICAgICA8ZXhpZjpQaXhlbFlEaW1lbnNpb24+NzE8L2V4aWY6UGl4ZWxZRGltZW5zaW9uPgogICAgICAgICA8ZXhpZjpQaXhlbFhEaW1lbnNpb24+NjA8L2V4aWY6UGl4ZWxYRGltZW5zaW9uPgogICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6dGlmZj0iaHR0cDovL25zLmFkb2JlLmNvbS90aWZmLzEuMC8iPgogICAgICAgICA8dGlmZjpZUmVzb2x1dGlvbj43MjwvdGlmZjpZUmVzb2x1dGlvbj4KICAgICAgICAgPHRpZmY6Q29tcHJlc3Npb24+NTwvdGlmZjpDb21wcmVzc2lvbj4KICAgICAgICAgPHRpZmY6WFJlc29sdXRpb24+NzI8L3RpZmY6WFJlc29sdXRpb24+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICAgICA8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIgogICAgICAgICAgICB4bWxuczp4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iPgogICAgICAgICA8eG1wOkNyZWF0b3JUb29sPkFjb3JuIHZlcnNpb24gMy41PC94bXA6Q3JlYXRvclRvb2w+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICA8L3JkZjpSREY+CjwveDp4bXBtZXRhPgqb9JbbAAAGd0lEQVRIDX1We4xVRxn/zZzXfd9l9+7efcCy9LqsYFtAAVHTFaQtrba1plltDKVRUfoHxeCDBE0FTI3+gTXWxkRNUVpNWtbExDSUlhQW2kKjDZWHCyzsdndZdvfC3ru79577OOeec8ZvDpx100S/ZM7MfDPzPX7f980cCCHw0bZXCI5Dh5R5fH37uwOPbTp87pRsckxrerAu98ozwXx+z+QkoH379vG9y5cz0dPjBrznLow+dHLS3D5mWhtrqq7anoew6zhL4sZbqxtjL+xe0f5asJf19ip7+/vFnj17vDnebQVsQ1+f0rdhg0tzX+PvLo51Hh6d3TpRsZ52YnVhxywirXN0xAxcMm3MqGHUW2Yloau/Wb0g/OKetXcMSKGMaP3x48rx9eulkYLJJlEKNPYN32z+y2h++7/y5S2mGlpUrFRxb1PU3dCaZFcKFfbdT7TBEZ7Y9vaguFp2lGQkjKhbuZaJh1/a2lX3wprGxslAFmNgaiA8m81Gd56femCoaO+YNqLdltCwqU4VKzNpkdRULjfnqjU0hjR5nm1sTYoLF8Y9XThsSjEWTZr48fnT1+/JRG48v/+u1JF0Ol2SslW5e9c/hx84O2XuHDGr91t6FB/ntnj8zkbvyc40p2X+9KlB/G0kh/aYjjNTJvUGTt8oMk1hTAUTn0tobtFx+Hkn1D0zY3Z/48zNN1ekKr/6+ZqOI0r44S3JE9niwVwsdU+dZ2NbZoHzszUdfG1jXAonCIHhYhUfkOCqK3A2b+KVoSl8SDzbE7i7PsoOfn4pfzzTCM2tuUOlGs/HU5mpfH7ZpWLpVfVYzjQmy1XNdXLYtTztfL2zSQkEXytZOJsrYXUqhk83xXH0+gwpAzzyPaorGDYtxHUVnPt2sKeWtSj1uuo8cz6rVmq2NlT2dLVBD3nDqNU452iLGXNWS8uvzFbw/fcGsWnhAmztakaVLD6XLyFBwi3y5pMNMdzXlpRbA2KtUYNzhUPUWC1shD0/BvA84gCm46e/zCjfpC+01mH/ugwFVsW6pgT+Pponj0xM2y4WRgwc6F6KjrgRCJe9KNQcPyUZBK+VSxSjgEgkxSyYzfUPt9ejRIp3nB7EsfEZJAmSMYJuRUPEFz5RtnGjUiOPPKwlGOtoXVoY5P0tBRKY/0P7zozg0NBNNEd0X1lzWMeWzjROTRaw5eQAbBK+oj6KP61fipqYK2Jfoq+AEyISHO22B+9OzqKFhN2RCOOX58bwyuAUWmmuUZxcz4VNQb48U0G2YkFiSzWB3SvbUbAdHBjI+oJDFPgBqv45iGQl1Ruaf/HtfG8IYZXjU5Q9JyYKiGkKwcdRoyBTySFfdTBO0Dy1rBUPtaeQSYTm/JcQucKlBtQT1wdHI+gl+tfLlrxL8KNVi3ycZb5LLKUyuqSgkPBCzcWXFtfje3e1IUL8+cKllkfaG8gY+PtbYnHwCXJDVxUvRKn12/5xnBifZo8uTuErHSnKd5DVnm+FtMSTDKIHKW3/B/lZIj8CzNMiUcHzNU3CqBI4sjrFt965Kra9cwWbP9aE/WuXIEHwmGS1Ks0iYqTj1siffvQjaq4nPDKKSC3O5BTeFY9Z5KmjxBKIkRTHE66EbCUV0ebOJjy7usOHSKajLFgZg78O59A3PouDFNBBujIC+sfNovvipUmmxZMUN+Y08pil/PulX1tHxvI5r1xa50YSdVTRvDmkeKvqo0Lm/JJ4iH02nUDOcjBRskkB92P1xtg0Dl+bBl0nokFXxYErWfGLS1NKVqiswSqMtoT0Z/58f9cHcy/as+9/2PV+vvTEDct5oqCG2xPCwaNtCZfuF0aPCiPP2ZeP9uNqoYoFdFWYLoXdY0K+UFxTFVvREbJLo4tjkZe7W+pe3nV362XpGVU0PTj/LTzsePvq8vGK/ZORqv21GW5giS7wZCblyUr94+UsK1JVU0L4T5THVS6MEDSrjIVh7dVVDdGf7l7V3h9ARogy3wM5QC+46PHrTa4b+y+MfPHkdfPbI6a1yQ5HOatWEGLCk8VG+cp5KAKlUvIIzjfWtcT+8IM7Fx+mc5Y8/NVeKL09fhLK5/JW6t1a6FV6aTDv0Q/98PTgg+fy5e/MOs59PJqQVzmUsukmDfXo0kTo9899JvM6sfxIy0e/hyaH5v00+JUrlcxvPfQbQvt85bf5xjePXXxs42tnj9xLbfPRi/K3xQjOyL3yTDCf3/8H+UFA5Uwbuc8AAAAASUVORK5CYII= - {"ETag":"\"067736a547cafe90014b4e59b6510abe\""} - true - true - true - 0.0 - 0.0 - - - Bing aerial imagery - Bing - bing - http://www.bing.com/maps/ - 22 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAMAAADXqc3KAAAAdVBMVEX/phX/04r/////6cX/zXz/7Mz/vFD/u0z/1I7/tT3/yXH/uEX/v1f/rCT/2pz/vlP/qRz/4a//yG3/xmn//Pj/9eb/+/T/897/t0H/wl7/sTL//vv/+O3/2Jn/7dD/+vH/9+n/3KT/tDr/9OL/8Nf/26D/ynSCVQVOAAAAkklEQVR4Xq3R1w7DIBQD0NiQne69d///E3tvBYVU6UsVPyEdCYycIOlOv5AB004Aaf6DCpLtF4yxp8tkFMGCkiEkKyGz9qCxrkxuhLIAeaijMvAwi/vMycJDuyi5/AVUaPwTPik5UdCDiWCjtd5Q70TK+KKD26M+6o+tdGxwIlmFPeyZn1yuraFKFOnt/sCz/81f+9UEaf1lPCAAAAAASUVORK5CYII= - {"X-VE-Tile-Info":"no-tile"} - {"X-VE-TILEMETA-CaptureDatesRange":"Capture Date"} - true - true - true - 0.0 - 0.0 - - - diff --git a/JOSM/sessions/india_gns_places.jos b/JOSM/sessions/india_gns_places.jos deleted file mode 100644 index abbffcd..0000000 --- a/JOSM/sessions/india_gns_places.jos +++ /dev/null @@ -1,95 +0,0 @@ - - - -
- - - - - geonames.nga.mil: Approved_(N) - wms - http://geonames.nga.mil/names/service.svc/get?FORMAT=image/jpeg&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&LAYERS=Approved__N_&STYLES=&SRS={proj}&WIDTH={width}&HEIGHT={height}&BBOX={bbox} - EPSG:4326 - true - true - true - 0.0 - 0.0 - - - Strava running heatmap - strava_running_heatmap - tms - http://globalheat.strava.com/tiles/running/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - Strava cycling heatmap - strava_cycling_heatmap - tms - http://globalheat.strava.com/tiles/cycling/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - OpenStreetMap GPS Traces - osm-gps - tms - https://gps-{switch:a,b,c}.tile.openstreetmap.org/lines/{zoom}/{x}/{y}.png - © OpenStreetMap contributors, CC-BY-SA - https://openstreetmap.org/ - 20 - true - true - true - 0.0 - 0.0 - - - Mapbox Satellite - Mapbox - tms - http://{switch:a,b,c}.tiles.mapbox.com/v4/openstreetmap.map-inh7ifmo/{zoom}/{x}/{y}.png?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcCIsImEiOiJncjlmd0t3In0.DmZsIeOW-3x-C5eX-wAqTw - 19 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAYAAADgdz34AAAYJWlDQ1BJQ0MgUHJvZmlsZQAAWAmteXk4ld3X/77PfUbzPGU4Zhkyz5nnISRzxDHPwzEkyZRHhYpIRKSkECpzJUWSSBqQokgyJFNJUrxbTz3P93u9v/e/331d5z6fs/baa6+91tp77bUPADz1lPDwYAwTACGhUVRbE32yk7MLmTACSIAL0IMdgJ7iFRmuZ2NjCf7P5+sgQLYan8tsyfo/2f7fDczePpFeACA2sNnTO9IrBOJ6ANBmr3BqFAC4LXki+6PCt3AWxGxUqCDEZVvY72/cvIU9/8a9v3jsbA0gzxgARDoKheoHAP0cpJNjvPygHAY6APAsod4BobAbGWJtL3+KNwA8HpBHOiQkbAtnQizh+R9y/P4DUyie/8ikUPz+wX/PBfaEAxsGRIYHUw78+vH/8xUSHA3t9evhh2+6yKA9FvCbA9ot1otitAdiLohP+PuYWf6ml4dH6dv+pt8OiDKzg5gN8rzwjza1/42no4Ps9SDmhfQfQWEWW/zQThiuUE8ra4hZIBbxijSAtt8aC6MS52/n+JvH0tvH0AhiGEUYJ2qY7R9+/8iYPX/ocXH+BlZ/+AMp5lv+ZoD86RQqRL/0weT7BJtsjSsE6VfDo2y29Nwaqy802Or3XDDvfanGWzxb9O8+kb/mu6Wbf5S/nSmkQ51Rpiiq3RYPnCPK6xtgbAYx1A2V86ea/qHrhgf/imnYF7WjRttu2UEEYl+fUPstG27R070phlu2hTZBi4AxoAAq8AGeIBTMADKwBAbA8PebDOmhkOYFwkAw/FDJjH9acB9wT3HvcAO4MdzwHxrs+ZsPBABviP+W9R/9IX0PiAOfoFQfEPlnNCwPVhuribWEb134UcCqYdX/tPXNNc39wb919YN9ZX7L1v+tfQyU+PMPn3tACvUP/t3H858e/1snY/AeWsDvD4dcldyM3I8//f+dMd4Ib4g3xRvjt6NH0Tq0C72HdqO30SZARtvQZrQXbd3Cv/X6MwoFUrassmXhSGABregDon/9Cv0z3n9ZKfofjt8SGCQZlIEt7BUKgmBbwD8jOPzSOuB/SYmGHJ5wxEDIa/GPP37rhRWD1lXG6mO1oJ2hjbEcWB4gg1WCFtfD6kAfKEPqv17879nIAN9f1o75NZcg8AHOIyTKJzYKxhIwCAs/QA3w848i68Hd0keabBbqtUOarCAnrwC29t4tHgA+2/7aUxGOJ//SqC0A7NSCsbjyL82DB4A6uC8yh/xLE0FhuCsC0PrIK5oa87c87NYXDtAARrgquAE/EAYS0CIKQAVoAl1gBMyBNbADzmAfjGF/EAI13g/iQTJIAxkgC5wGZ0EJuAiugGpwAzSB2+AeeAB6QD8YAK/BGJgEH8Ei+ArWEQQhIPQIK8KNCCCiiBSigKgh2ogRYonYIs6IB+KHhCLRSDxyGMlATiFnkVKkArmOtCD3kG7kKTKMjCMzyDLyHYNi6DBsGD6MGEYWo4bRw1hg7DBuGD9MBCYOk4o5gcnHXMBcxTRi7mF6MAOYMcxHzAoKUFqUAxVEZVA11AC1Rl1QX5SKJqDpaB56Aa1Bb8JYfI6OoXPoGhaPZcWSsTLQk6ZYe6wXNgKbgM3EnsVewTZi72OfY8exi9gNHD2OFyeF08CZ4Zxwfrj9uDRcHq4c14DrhOt5EvcVj8dz4MXxqjDanfGB+IP4TPw5fC3+Lv4pfgK/QiAQuAlSBC2CNYFCiCKkEQoIVwlthGeEScI3Ii1RgKhANCa6EEOJKcQ8YiXxDvEZcYq4TmIiiZI0SNYkb9IB0klSGekm6QlpkrROw0wjTqNFY0cTSJNMk09TQ9NJM0LzmZaWVohWnXY3bQBtEm0+7TXah7TjtGt0LHSSdAZ0rnTRdCfoLtPdpRum+0xPTy9Gr0vvQh9Ff4K+gr6D/g39NwZWhh0MZgzeDIkMhQyNDM8Y5hlJjKKMeoz7GOMY8xjrGJ8wzjGRmMSYDJgoTAlMhUwtTENMK8yszPLM1swhzJnMlczdzNMsBBYxFiMWb5ZUlossHSwTrCirMKsBqxfrYdYy1k7WSTY8mzibGVsgWwZbNVsf2yI7C7sSuwN7LHsheyv7GAfKIcZhxhHMcZLjBscgx3dOPk49Th/OY5w1nM84V7m2cely+XClc9VyDXB95yZzG3EHcWdzN3GP8mB5JHl28+znKebp5JnbxrZNc5vXtvRtN7a94sXwSvLa8h7kvcjby7vCx89nwhfOV8DXwTfHz8Gvyx/In8t/h39GgFVAWyBAIFegTWCWzE7WIweT88n3yYuCvIKmgtGCpYJ9gutC4kL2QilCtUKjwjTCasK+wrnC7cKLIgIiu0TiRapEXomSRNVE/UXPiHaJroqJizmKHRFrEpsW5xI3E48TrxIfkaCX0JGIkLgg8WI7frva9qDt57b3S2IklSX9JQsln0hhpFSkAqTOST2VxkmrS4dKX5AekqGT0ZOJkamSGd/BscNyR8qOph3zsiKyLrLZsl2yG3LKcsFyZXKv5VnkzeVT5G/KLytIKngpFCq8UKRXNFZMVGxWXFKSUvJRKlZ6qcyqvEv5iHK78k8VVRWqSo3KjKqIqodqkeqQGpuajVqm2kN1nLq+eqL6bfU1DRWNKI0bGguaMppBmpWa0zvFd/rsLNs5oSWkRdEq1RrTJmt7aJ/XHtMR1KHoXNB5pyus661brjult10vUO+q3ry+nD5Vv0F/1UDD4JDBXUPU0MQw3bDPiMXI3uis0RtjIWM/4yrjRRNlk4Mmd01xpham2aZDZnxmXmYVZovmquaHzO9b0FnssThr8c5S0pJqeXMXZpf5rpxdI1aiVqFWTdbA2sw6x3rURtwmwubWbvxum92Fuz/YytvG23btYd3jvqdyz1c7fbuTdq/tJeyj7dsdGB1cHSocVh0NHU85jjnJOh1y6nHmcQ5wbnYhuDi4lLus7DXae3rvpKuya5rroJu4W6xb9z6efcH7Wt0Z3SnudR44D0ePSo8fFGvKBcqKp5lnkeeil4HXGa+P3rreud4zPlo+p3ymfLV8T/lO+2n55fjN+Ov45/nPBRgEnA1YCjQNLAlcDbIOuhy0GewYXBtCDPEIaQllCQ0KvR/GHxYb9jRcKjwtfCxCI+J0xCLVgloeiUS6RTZHscFDbm+0RPRf0eMx2jGFMd/2O+yvi2WODY3tPSB54NiBqTjjuEsHsQe9DrbHC8Ynx48f0jtUmoAkeCa0JwonpiZOJpkkXUmmSQ5Kfpwil3Iq5cthx8M3U/lSk1In/jL5qyqNIY2aNnRE80jJUezRgKN9xxSPFRzbSPdOf5Qhl5GX8SPTK/PRcfnj+cc3T/ie6DupcrI4C58VmjWYrZN95RTzqbhTEzm7chpzybnpuV9Ou5/uzlPKKzlDcyb6zFi+ZX5zgUhBVsGPs/5nBwr1C2uLeIuOFa2e8z73rFi3uKaErySj5Pv5gPMvS01KGy+IXci7iL8Yc/FDmUNZ1yW1SxXlPOUZ5T8vh14eu2J75X6FakVFJW/lySpMVXTVzFXXq/3VhtXNNTI1pbUctRnXwLXoa7PXPa4P3rC40V6nVldTL1pf1MDakN6INB5oXGzybxprdm5+2mLe0n5T82bDrR23Lt8WvF3Yyt568g7NndQ7m21xbSt3w+/O3fO7N9Hu3v66w6njxf3d9/s6LTofPjB+0NGl19X2UOvh7W6N7pZHao+aelR6GnuVexseKz9u6FPpa3yi+qS5X73/5tOdT+8803l277nh8wcvzF70DFgNPB20H3w55Do09tL75fRw8PDSq5hX66+TRnAj6aNMo3lveN9ceLv9be2YyljruOF477s9715PeE18fB/5/sdk6gf6D3lTAlMV0wrTt2eMZ/pn985Ofgz/uD6X9on5U9G8xHz9gu5C76LT4uQSdWlzOfMz9+fLX5S+tK/YrLz5GvJ1fTX9G/e3K2tqa13fHb9Pre//QfiR/3P7z5sbFhsjmyGbm+EUKuXXWQCeDgDG1xeA5cuwLnIGgLUfABqGv2ujXxzwiIFAHoix8LQgB1xADhiBuTwRGcfYY4ZRPyyKbcBF4jUIdIQ54gipl6ad9j5dF/1jhiEmReYSVla2Y+wbnAncKE8qLzNfqYAy+aGQrwhBtEp8j8SGZLW0q8ysbIDcrIKf4riys0qPmqp6iSayc6/WNR1E11ovV/+1Ib/RbmMPkzDTJLNs84sWDZbdu0atlm2Iu8m2anus7fztDzuUODY59TlP70Vcud0U91m6e3scpOR6Vnm1ew/7LPnR+PMFSAeqBRkH24VQQsPCDoYfjcillkZejWqJvh/zdP/r2DcHxuPeH5yKnzk0mzCX+ClpPnk+Zf7wfOrCXwtpn47MHp0+NpU+nfExc+H41xObWTTZnKfEclRyzU775GWeqc9/VbBZKFRkcI5SfKgk//z10u4Lby+uXCKV81yWuqJRYVbpWOV1Naz6QE0KjNjc60U3yura6kcb1pqYm0VblG/q3jK+bdpqfEe3Tf2u3D3ldpuOgPtJnbkPyrpqHzZ0Nz2q76npLXtc0Jf+JK4/4KnjM8Pn8i94B/AD84ODQ7dfXhg+8sr/tfGI0Mjm6Miblrd5Y1Hjtu/kJhgnPr3vnSz5EDilMLU63TRDnZWYffkxeU50rvOTx6f1+dIFs4XPiyVLlks/lms+U75wfulbOfJV7evIqvNq/zfrb8/XAr/Tfu9Zv/yj+Gf1xpPNTeh/FNZTvEAZOIIU0Ai+IPpIEQaDicIso/FYFuxNXDA8/cwSGoiHSU40KrTMtEv0JAYlRg+mDOY7LN/ZFNijOW5x0XA78VzlJfD58HeTdwjmCKMioaL94vIS6dvfS+2UzpaZkN0hFynfoLCgJKZsp5KsWqnWr/5Zk2YnuxaftrCOhK6Mnry+vIGcoayRjLGEiZAprxmnOZMF0eKH5dKuKasR62c2j3a3297a02BXY1/hUOZ43qnIOd8ld2+m619uh/bFuId5+FPcPR28dnkb+mj4yvmJw9hgDkQDV4KmgodDekJbw2rCSyKyqMmREVGUaNsYg/1ysXwHSAe+wvh4Gt92qCahOPFEUlIyNcXnsEuq/V/OafuOeB71PRaYHpwRmhl2POJE5MmorJjsA6cSclJyj5zOzDt55lR+bsHps3mFZ4ryzxUUF5acO3+ttPPC0MXpstVyzGXaKywVXJW8VeSrwtUSNcq1lte8rsfdOFl3sb6u4V5jb9OL5uGW1zdHb727vX6HrU3mrtE91/aIjsP3czrPP6jqqnt4s7v10Z2eu72dj3v6Bp686196hj7nfCEzYDjoOhT4MmI49lXy6/SR06Olb2rf3hl7Mj72bvk9Oomd3PywDiPjy8zy7NLHpbnlT1/mVxfWl5Blxs9CXzRXXL8eWb2zhvluv17/k28j85f/MYAIK2FhoA7sYT1wHjxB8Igjch3DgUlDEfQ4VgT7ABeC34bvJRwiKhLnSJU0ybRhdBR6RwYrRjMmM+ZdLHasHmzh7GkcxZwtXC+517cJ8ZrxhfFnC1wldwm+E1oXYREVFVMQ3ylhuN1YUh/Gg4KM6A5OWZzsotxL+XsKFYqnlA4q+6hYqaqpCarTqH/WeKP5cOcNrSLtFB03XUU9kt5b/XqDY4ZuRvLGWONBkwrTg2ZW5gLmSxYdlrm7fK3UrOmsx22adp+w9dmjbcdht2j/yOGSY5KTi7O8C9Hl7d5G1+Nu3vs03Zndpz3aKHmeoV7G3vzen30e+hb7RfqbBvDBfP4gqDA4PMQolCd0IawzvDAikmoeKRS5FtUfXR4Tv98mViT224HeuJKD1HjF+IVDVQlBiQqJm0nPk2tSsg4fSPX/a2+a7RGLo4bHdqYrZUhmChxnOv7zxIeTPVlV2UdOueco5fKf5ssjnxHNlyyQO6taqFNkcs662LHE/bxfqd+FvRd3lelf0ihXuaxyZWeFSaVzVfjVjOqqmse189cZbkjXmdf7NhxuLGm61fyy5estjtuqrV538tse30PaFTu87p/sbH4w2rXRzfdIo8et91of75Nj/V+feT9/NqA3eP2l0HDua/xI7BvhMa133u/Pf1idCZtjnB9ZervC8y3jh/SW//++I9vKCXgVAEqHAHCgAcCqB4DiYQBEmQFghLWnDT0AduoAU+4LMDRa8Bpq9z/5gw3WmEawpowBJ0EF6ACjYA3hQBRhLUhFcpCryANY7/3AcGGUMLaYMFjVXcX0YuZQOljBWaHhaA7aiA6jP7GCWGNsEDYb24R9g8PhZHD2uCRcLe4tngmvh4/CX8GPElgJFoRUWFutE9WJB4i3iJskQ1ImaYBGkCaU5jYtPa0X7QM6KbpsujV6T5il1BkuM3IwHmFcYwpmGmd2Yu5nMWPpYNVlvcumx9bBbsLex2HP8ZYziHON6yg3D3c1jwHPq21UXjrear7dfN/4zwuYC6ySLwk6CJGE7ghHi8iKzIpeEfMTlxBflmjbfkLSXUpRmkZ6QubOjnOyCXIUeRMFWUVuJbzSmvInlXeqL9X61B9otGo27KzWuqRdrHNGN1svQz/ewN/QwcjEWNNEwVTaTNJc2kLeUmOXsZW9tZ9N/O4c2xt7ntl9deB1NHaKdC5zeenK5Ga+76j7Qwqtp41Xsvd1n0k/fv99AWWBy8GmIZfDGMIPRSxHhkR9itHafzL2Q5z+wUuHGBKSEteTEw/TpV5I0z3y/lhWhn7m2om6rMhTarno6RdnKgvSCn3PmZfolupc1L1kdNmywqHKs5pam3q9oO56w0Kz+c26VsW2J+3ZnYkPC3oG+8afjr4YHOp6dX309FjUhM2HnI/kBZ3l2yvnvtF+V/2hsSH6a/8QAnrAAySCc/DGYAT8RMiIARKAZCHXkH5kCdb3qpi9mETMJVjDL6HcqC4agJ6CN0UfsMzYnVh/7GlsB3YJJ4Czhv6ux03j+fEO+BP4hwSUoEtIILQRMbB+Pk4cIgmRIkj3aNhoAmju0vLQxtGO0ZnS1dGT6U8yIAwxsKb1Z5xk8mGahhXrF5YEVlrWc2xybJ3sbuxfObI4ZTh7uIK5Gbhv8DhtA9sqeR34iHy3+CMEtgtMkM8LeggJC00LXxM5KGoqxik2I35XonB7rKSTlIa0gAxBZnnHmGy/3H35mwo3FKuVapXrVG6p3ofZ643G/E6gxaotoaOt66AXpp9scNyw0Kja+J7JS9PPMHfJWdru2m9VbN1ls2TLu8fMLta+0uGtE5eznUvO3gE3nn0U90qPFU89r3jvRp8VP1X/xIDeIIHgmJDnYYrhZyI2Iv2insaI74+PHYiTO5gV/yVhX+LjZIOUtlT9v3qOOB2dTnfKeHRc50Rjlnz2tRzl3Dt5VmcmChILBYu6iqPPS5W+vZhzyah85crFSuuqteqLMPus3CipN29kaxprqbkV32rexn13qr3xfuoD24dC3cs9HY8bn7Q8bXveOdA7NDA8+vrD6OLb7+9w75k/bJvmmWWZw3yaXuhYyv5su4L7WvXNZO3Vut+PpY3YX/5XAnvhHdIl0A0WEE54eghDziGdyDxc8YbwJqcE04fZQGVRClzpXeg6Vh7rhy3GDuIYcebwpuUBnoi3wGfhhwhkQjDhFpGeSCG2kNhJUaQheA9STstKmwpvOsLoZui96d8xeDJMMgYyLjPFMxOZz7BIsNxmdWXDstWwu3IwcHRwxnOpc61xt/KkbrPm5eWd5+vgPysQSd4lKAnX8Kxwn0idaKFYmniUROB2T8l9Um7S7jI+O0Jl4+SOyRcqXFPsUppSIanuUHNUT9Wo15zWEtB21snTHdTnNnAzLDOaN9EyzTKbtjCyLLeitY62mbDdbydg3+po7TTgYr231U1oX4r7KEXV86TXnI+Fb60/Z0Ba4EZwUih9WHmEJXUjqiVGaf+lA1xxmfHgUEzCpyTf5PHD+1LfpHnAVRoPM8bLE6lZMtnPcsJPk/IK88ULagoViuqKFUqaSrUuPCyzvzR1+WAFS2XVVePqd7UJ17fdaK63axhp8myevRlzG99a0KZw92l7zH2hzhddmd3mPXS9LX18T5L6J5+ZP782wDmYODQ9vPvVrRGx0ew3P8eCxocnTN83Ta5+WJv6Nr0yszA79XF4rvtT/fzZhfhF5yX5Zdzys8/nvnisCMOqI2/VYnX9W+Wa7dra95J17fXRH/E/2X/WbBhvDG8Gb/k/0ldRYSt7AIROH14/vtnc/CwGAOEUAD+zNzfXL2xu/rwID5kjANwN/vt/ly1mPLyrL4I5BoDO5K2/dv77+R8P0NEUOETYwgAAAAlwSFlzAAALEwAACxMBAJqcGAAAA1NpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IlhNUCBDb3JlIDUuMS4yIj4KICAgPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6ZXhpZj0iaHR0cDovL25zLmFkb2JlLmNvbS9leGlmLzEuMC8iPgogICAgICAgICA8ZXhpZjpQaXhlbFlEaW1lbnNpb24+NzE8L2V4aWY6UGl4ZWxZRGltZW5zaW9uPgogICAgICAgICA8ZXhpZjpQaXhlbFhEaW1lbnNpb24+NjA8L2V4aWY6UGl4ZWxYRGltZW5zaW9uPgogICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6dGlmZj0iaHR0cDovL25zLmFkb2JlLmNvbS90aWZmLzEuMC8iPgogICAgICAgICA8dGlmZjpZUmVzb2x1dGlvbj43MjwvdGlmZjpZUmVzb2x1dGlvbj4KICAgICAgICAgPHRpZmY6Q29tcHJlc3Npb24+NTwvdGlmZjpDb21wcmVzc2lvbj4KICAgICAgICAgPHRpZmY6WFJlc29sdXRpb24+NzI8L3RpZmY6WFJlc29sdXRpb24+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICAgICA8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIgogICAgICAgICAgICB4bWxuczp4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iPgogICAgICAgICA8eG1wOkNyZWF0b3JUb29sPkFjb3JuIHZlcnNpb24gMy41PC94bXA6Q3JlYXRvclRvb2w+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICA8L3JkZjpSREY+CjwveDp4bXBtZXRhPgqb9JbbAAAGd0lEQVRIDX1We4xVRxn/zZzXfd9l9+7efcCy9LqsYFtAAVHTFaQtrba1plltDKVRUfoHxeCDBE0FTI3+gTXWxkRNUVpNWtbExDSUlhQW2kKjDZWHCyzsdndZdvfC3ru79577OOeec8ZvDpx100S/ZM7MfDPzPX7f980cCCHw0bZXCI5Dh5R5fH37uwOPbTp87pRsckxrerAu98ozwXx+z+QkoH379vG9y5cz0dPjBrznLow+dHLS3D5mWhtrqq7anoew6zhL4sZbqxtjL+xe0f5asJf19ip7+/vFnj17vDnebQVsQ1+f0rdhg0tzX+PvLo51Hh6d3TpRsZ52YnVhxywirXN0xAxcMm3MqGHUW2Yloau/Wb0g/OKetXcMSKGMaP3x48rx9eulkYLJJlEKNPYN32z+y2h++7/y5S2mGlpUrFRxb1PU3dCaZFcKFfbdT7TBEZ7Y9vaguFp2lGQkjKhbuZaJh1/a2lX3wprGxslAFmNgaiA8m81Gd56femCoaO+YNqLdltCwqU4VKzNpkdRULjfnqjU0hjR5nm1sTYoLF8Y9XThsSjEWTZr48fnT1+/JRG48v/+u1JF0Ol2SslW5e9c/hx84O2XuHDGr91t6FB/ntnj8zkbvyc40p2X+9KlB/G0kh/aYjjNTJvUGTt8oMk1hTAUTn0tobtFx+Hkn1D0zY3Z/48zNN1ekKr/6+ZqOI0r44S3JE9niwVwsdU+dZ2NbZoHzszUdfG1jXAonCIHhYhUfkOCqK3A2b+KVoSl8SDzbE7i7PsoOfn4pfzzTCM2tuUOlGs/HU5mpfH7ZpWLpVfVYzjQmy1XNdXLYtTztfL2zSQkEXytZOJsrYXUqhk83xXH0+gwpAzzyPaorGDYtxHUVnPt2sKeWtSj1uuo8cz6rVmq2NlT2dLVBD3nDqNU452iLGXNWS8uvzFbw/fcGsWnhAmztakaVLD6XLyFBwi3y5pMNMdzXlpRbA2KtUYNzhUPUWC1shD0/BvA84gCm46e/zCjfpC+01mH/ugwFVsW6pgT+Pponj0xM2y4WRgwc6F6KjrgRCJe9KNQcPyUZBK+VSxSjgEgkxSyYzfUPt9ejRIp3nB7EsfEZJAmSMYJuRUPEFz5RtnGjUiOPPKwlGOtoXVoY5P0tBRKY/0P7zozg0NBNNEd0X1lzWMeWzjROTRaw5eQAbBK+oj6KP61fipqYK2Jfoq+AEyISHO22B+9OzqKFhN2RCOOX58bwyuAUWmmuUZxcz4VNQb48U0G2YkFiSzWB3SvbUbAdHBjI+oJDFPgBqv45iGQl1Ruaf/HtfG8IYZXjU5Q9JyYKiGkKwcdRoyBTySFfdTBO0Dy1rBUPtaeQSYTm/JcQucKlBtQT1wdHI+gl+tfLlrxL8KNVi3ycZb5LLKUyuqSgkPBCzcWXFtfje3e1IUL8+cKllkfaG8gY+PtbYnHwCXJDVxUvRKn12/5xnBifZo8uTuErHSnKd5DVnm+FtMSTDKIHKW3/B/lZIj8CzNMiUcHzNU3CqBI4sjrFt965Kra9cwWbP9aE/WuXIEHwmGS1Ks0iYqTj1siffvQjaq4nPDKKSC3O5BTeFY9Z5KmjxBKIkRTHE66EbCUV0ebOJjy7usOHSKajLFgZg78O59A3PouDFNBBujIC+sfNovvipUmmxZMUN+Y08pil/PulX1tHxvI5r1xa50YSdVTRvDmkeKvqo0Lm/JJ4iH02nUDOcjBRskkB92P1xtg0Dl+bBl0nokFXxYErWfGLS1NKVqiswSqMtoT0Z/58f9cHcy/as+9/2PV+vvTEDct5oqCG2xPCwaNtCZfuF0aPCiPP2ZeP9uNqoYoFdFWYLoXdY0K+UFxTFVvREbJLo4tjkZe7W+pe3nV362XpGVU0PTj/LTzsePvq8vGK/ZORqv21GW5giS7wZCblyUr94+UsK1JVU0L4T5THVS6MEDSrjIVh7dVVDdGf7l7V3h9ARogy3wM5QC+46PHrTa4b+y+MfPHkdfPbI6a1yQ5HOatWEGLCk8VG+cp5KAKlUvIIzjfWtcT+8IM7Fx+mc5Y8/NVeKL09fhLK5/JW6t1a6FV6aTDv0Q/98PTgg+fy5e/MOs59PJqQVzmUsukmDfXo0kTo9899JvM6sfxIy0e/hyaH5v00+JUrlcxvPfQbQvt85bf5xjePXXxs42tnj9xLbfPRi/K3xQjOyL3yTDCf3/8H+UFA5Uwbuc8AAAAASUVORK5CYII= - {"ETag":"\"067736a547cafe90014b4e59b6510abe\""} - true - true - true - 0.0 - 0.0 - - - Bing aerial imagery - Bing - bing - http://www.bing.com/maps/ - 22 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAMAAADXqc3KAAAAdVBMVEX/phX/04r/////6cX/zXz/7Mz/vFD/u0z/1I7/tT3/yXH/uEX/v1f/rCT/2pz/vlP/qRz/4a//yG3/xmn//Pj/9eb/+/T/897/t0H/wl7/sTL//vv/+O3/2Jn/7dD/+vH/9+n/3KT/tDr/9OL/8Nf/26D/ynSCVQVOAAAAkklEQVR4Xq3R1w7DIBQD0NiQne69d///E3tvBYVU6UsVPyEdCYycIOlOv5AB004Aaf6DCpLtF4yxp8tkFMGCkiEkKyGz9qCxrkxuhLIAeaijMvAwi/vMycJDuyi5/AVUaPwTPik5UdCDiWCjtd5Q70TK+KKD26M+6o+tdGxwIlmFPeyZn1yuraFKFOnt/sCz/81f+9UEaf1lPCAAAAAASUVORK5CYII= - {"X-VE-Tile-Info":"no-tile"} - {"X-VE-TILEMETA-CaptureDatesRange":"Capture Date"} - true - true - true - 0.0 - 0.0 - - - diff --git a/JOSM/sessions/japan.jos b/JOSM/sessions/japan.jos deleted file mode 100644 index bb97fda..0000000 --- a/JOSM/sessions/japan.jos +++ /dev/null @@ -1,94 +0,0 @@ - - - -
- - - - - OpenStreetMap GPS Traces - osm-gps - tms - https://gps-{switch:a,b,c}.tile.openstreetmap.org/lines/{zoom}/{x}/{y}.png - © OpenStreetMap contributors, CC-BY-SA - https://openstreetmap.org/ - 20 - true - true - true - 0.0 - 0.0 - - - Strava running heatmap - strava_running_heatmap - tms - http://globalheat.strava.com/tiles/running/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - Strava cycling heatmap - strava_cycling_heatmap - tms - http://globalheat.strava.com/tiles/cycling/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - GSIMaps/ort - tms - http://cyberjapandata.gsi.go.jp/xyz/ort/{z}/{x}/{y}.jpg - true - true - true - 0.0 - 0.0 - - - Mapbox Satellite - Mapbox - tms - http://{switch:a,b,c}.tiles.mapbox.com/v4/openstreetmap.map-inh7ifmo/{zoom}/{x}/{y}.png?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcCIsImEiOiJncjlmd0t3In0.DmZsIeOW-3x-C5eX-wAqTw - 19 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAYAAADgdz34AAAYJWlDQ1BJQ0MgUHJvZmlsZQAAWAmteXk4ld3X/77PfUbzPGU4Zhkyz5nnISRzxDHPwzEkyZRHhYpIRKSkECpzJUWSSBqQokgyJFNJUrxbTz3P93u9v/e/331d5z6fs/baa6+91tp77bUPADz1lPDwYAwTACGhUVRbE32yk7MLmTACSIAL0IMdgJ7iFRmuZ2NjCf7P5+sgQLYan8tsyfo/2f7fDczePpFeACA2sNnTO9IrBOJ6ANBmr3BqFAC4LXki+6PCt3AWxGxUqCDEZVvY72/cvIU9/8a9v3jsbA0gzxgARDoKheoHAP0cpJNjvPygHAY6APAsod4BobAbGWJtL3+KNwA8HpBHOiQkbAtnQizh+R9y/P4DUyie/8ikUPz+wX/PBfaEAxsGRIYHUw78+vH/8xUSHA3t9evhh2+6yKA9FvCbA9ot1otitAdiLohP+PuYWf6ml4dH6dv+pt8OiDKzg5gN8rzwjza1/42no4Ps9SDmhfQfQWEWW/zQThiuUE8ra4hZIBbxijSAtt8aC6MS52/n+JvH0tvH0AhiGEUYJ2qY7R9+/8iYPX/ocXH+BlZ/+AMp5lv+ZoD86RQqRL/0weT7BJtsjSsE6VfDo2y29Nwaqy802Or3XDDvfanGWzxb9O8+kb/mu6Wbf5S/nSmkQ51Rpiiq3RYPnCPK6xtgbAYx1A2V86ea/qHrhgf/imnYF7WjRttu2UEEYl+fUPstG27R070phlu2hTZBi4AxoAAq8AGeIBTMADKwBAbA8PebDOmhkOYFwkAw/FDJjH9acB9wT3HvcAO4MdzwHxrs+ZsPBABviP+W9R/9IX0PiAOfoFQfEPlnNCwPVhuribWEb134UcCqYdX/tPXNNc39wb919YN9ZX7L1v+tfQyU+PMPn3tACvUP/t3H858e/1snY/AeWsDvD4dcldyM3I8//f+dMd4Ib4g3xRvjt6NH0Tq0C72HdqO30SZARtvQZrQXbd3Cv/X6MwoFUrassmXhSGABregDon/9Cv0z3n9ZKfofjt8SGCQZlIEt7BUKgmBbwD8jOPzSOuB/SYmGHJ5wxEDIa/GPP37rhRWD1lXG6mO1oJ2hjbEcWB4gg1WCFtfD6kAfKEPqv17879nIAN9f1o75NZcg8AHOIyTKJzYKxhIwCAs/QA3w848i68Hd0keabBbqtUOarCAnrwC29t4tHgA+2/7aUxGOJ//SqC0A7NSCsbjyL82DB4A6uC8yh/xLE0FhuCsC0PrIK5oa87c87NYXDtAARrgquAE/EAYS0CIKQAVoAl1gBMyBNbADzmAfjGF/EAI13g/iQTJIAxkgC5wGZ0EJuAiugGpwAzSB2+AeeAB6QD8YAK/BGJgEH8Ei+ArWEQQhIPQIK8KNCCCiiBSigKgh2ogRYonYIs6IB+KHhCLRSDxyGMlATiFnkVKkArmOtCD3kG7kKTKMjCMzyDLyHYNi6DBsGD6MGEYWo4bRw1hg7DBuGD9MBCYOk4o5gcnHXMBcxTRi7mF6MAOYMcxHzAoKUFqUAxVEZVA11AC1Rl1QX5SKJqDpaB56Aa1Bb8JYfI6OoXPoGhaPZcWSsTLQk6ZYe6wXNgKbgM3EnsVewTZi72OfY8exi9gNHD2OFyeF08CZ4Zxwfrj9uDRcHq4c14DrhOt5EvcVj8dz4MXxqjDanfGB+IP4TPw5fC3+Lv4pfgK/QiAQuAlSBC2CNYFCiCKkEQoIVwlthGeEScI3Ii1RgKhANCa6EEOJKcQ8YiXxDvEZcYq4TmIiiZI0SNYkb9IB0klSGekm6QlpkrROw0wjTqNFY0cTSJNMk09TQ9NJM0LzmZaWVohWnXY3bQBtEm0+7TXah7TjtGt0LHSSdAZ0rnTRdCfoLtPdpRum+0xPTy9Gr0vvQh9Ff4K+gr6D/g39NwZWhh0MZgzeDIkMhQyNDM8Y5hlJjKKMeoz7GOMY8xjrGJ8wzjGRmMSYDJgoTAlMhUwtTENMK8yszPLM1swhzJnMlczdzNMsBBYxFiMWb5ZUlossHSwTrCirMKsBqxfrYdYy1k7WSTY8mzibGVsgWwZbNVsf2yI7C7sSuwN7LHsheyv7GAfKIcZhxhHMcZLjBscgx3dOPk49Th/OY5w1nM84V7m2cely+XClc9VyDXB95yZzG3EHcWdzN3GP8mB5JHl28+znKebp5JnbxrZNc5vXtvRtN7a94sXwSvLa8h7kvcjby7vCx89nwhfOV8DXwTfHz8Gvyx/In8t/h39GgFVAWyBAIFegTWCWzE7WIweT88n3yYuCvIKmgtGCpYJ9gutC4kL2QilCtUKjwjTCasK+wrnC7cKLIgIiu0TiRapEXomSRNVE/UXPiHaJroqJizmKHRFrEpsW5xI3E48TrxIfkaCX0JGIkLgg8WI7frva9qDt57b3S2IklSX9JQsln0hhpFSkAqTOST2VxkmrS4dKX5AekqGT0ZOJkamSGd/BscNyR8qOph3zsiKyLrLZsl2yG3LKcsFyZXKv5VnkzeVT5G/KLytIKngpFCq8UKRXNFZMVGxWXFKSUvJRKlZ6qcyqvEv5iHK78k8VVRWqSo3KjKqIqodqkeqQGpuajVqm2kN1nLq+eqL6bfU1DRWNKI0bGguaMppBmpWa0zvFd/rsLNs5oSWkRdEq1RrTJmt7aJ/XHtMR1KHoXNB5pyus661brjult10vUO+q3ry+nD5Vv0F/1UDD4JDBXUPU0MQw3bDPiMXI3uis0RtjIWM/4yrjRRNlk4Mmd01xpham2aZDZnxmXmYVZovmquaHzO9b0FnssThr8c5S0pJqeXMXZpf5rpxdI1aiVqFWTdbA2sw6x3rURtwmwubWbvxum92Fuz/YytvG23btYd3jvqdyz1c7fbuTdq/tJeyj7dsdGB1cHSocVh0NHU85jjnJOh1y6nHmcQ5wbnYhuDi4lLus7DXae3rvpKuya5rroJu4W6xb9z6efcH7Wt0Z3SnudR44D0ePSo8fFGvKBcqKp5lnkeeil4HXGa+P3rreud4zPlo+p3ymfLV8T/lO+2n55fjN+Ov45/nPBRgEnA1YCjQNLAlcDbIOuhy0GewYXBtCDPEIaQllCQ0KvR/GHxYb9jRcKjwtfCxCI+J0xCLVgloeiUS6RTZHscFDbm+0RPRf0eMx2jGFMd/2O+yvi2WODY3tPSB54NiBqTjjuEsHsQe9DrbHC8Ynx48f0jtUmoAkeCa0JwonpiZOJpkkXUmmSQ5Kfpwil3Iq5cthx8M3U/lSk1In/jL5qyqNIY2aNnRE80jJUezRgKN9xxSPFRzbSPdOf5Qhl5GX8SPTK/PRcfnj+cc3T/ie6DupcrI4C58VmjWYrZN95RTzqbhTEzm7chpzybnpuV9Ou5/uzlPKKzlDcyb6zFi+ZX5zgUhBVsGPs/5nBwr1C2uLeIuOFa2e8z73rFi3uKaErySj5Pv5gPMvS01KGy+IXci7iL8Yc/FDmUNZ1yW1SxXlPOUZ5T8vh14eu2J75X6FakVFJW/lySpMVXTVzFXXq/3VhtXNNTI1pbUctRnXwLXoa7PXPa4P3rC40V6nVldTL1pf1MDakN6INB5oXGzybxprdm5+2mLe0n5T82bDrR23Lt8WvF3Yyt568g7NndQ7m21xbSt3w+/O3fO7N9Hu3v66w6njxf3d9/s6LTofPjB+0NGl19X2UOvh7W6N7pZHao+aelR6GnuVexseKz9u6FPpa3yi+qS5X73/5tOdT+8803l277nh8wcvzF70DFgNPB20H3w55Do09tL75fRw8PDSq5hX66+TRnAj6aNMo3lveN9ceLv9be2YyljruOF477s9715PeE18fB/5/sdk6gf6D3lTAlMV0wrTt2eMZ/pn985Ofgz/uD6X9on5U9G8xHz9gu5C76LT4uQSdWlzOfMz9+fLX5S+tK/YrLz5GvJ1fTX9G/e3K2tqa13fHb9Pre//QfiR/3P7z5sbFhsjmyGbm+EUKuXXWQCeDgDG1xeA5cuwLnIGgLUfABqGv2ujXxzwiIFAHoix8LQgB1xADhiBuTwRGcfYY4ZRPyyKbcBF4jUIdIQ54gipl6ad9j5dF/1jhiEmReYSVla2Y+wbnAncKE8qLzNfqYAy+aGQrwhBtEp8j8SGZLW0q8ysbIDcrIKf4riys0qPmqp6iSayc6/WNR1E11ovV/+1Ib/RbmMPkzDTJLNs84sWDZbdu0atlm2Iu8m2anus7fztDzuUODY59TlP70Vcud0U91m6e3scpOR6Vnm1ew/7LPnR+PMFSAeqBRkH24VQQsPCDoYfjcillkZejWqJvh/zdP/r2DcHxuPeH5yKnzk0mzCX+ClpPnk+Zf7wfOrCXwtpn47MHp0+NpU+nfExc+H41xObWTTZnKfEclRyzU775GWeqc9/VbBZKFRkcI5SfKgk//z10u4Lby+uXCKV81yWuqJRYVbpWOV1Naz6QE0KjNjc60U3yura6kcb1pqYm0VblG/q3jK+bdpqfEe3Tf2u3D3ldpuOgPtJnbkPyrpqHzZ0Nz2q76npLXtc0Jf+JK4/4KnjM8Pn8i94B/AD84ODQ7dfXhg+8sr/tfGI0Mjm6Miblrd5Y1Hjtu/kJhgnPr3vnSz5EDilMLU63TRDnZWYffkxeU50rvOTx6f1+dIFs4XPiyVLlks/lms+U75wfulbOfJV7evIqvNq/zfrb8/XAr/Tfu9Zv/yj+Gf1xpPNTeh/FNZTvEAZOIIU0Ai+IPpIEQaDicIso/FYFuxNXDA8/cwSGoiHSU40KrTMtEv0JAYlRg+mDOY7LN/ZFNijOW5x0XA78VzlJfD58HeTdwjmCKMioaL94vIS6dvfS+2UzpaZkN0hFynfoLCgJKZsp5KsWqnWr/5Zk2YnuxaftrCOhK6Mnry+vIGcoayRjLGEiZAprxmnOZMF0eKH5dKuKasR62c2j3a3297a02BXY1/hUOZ43qnIOd8ld2+m619uh/bFuId5+FPcPR28dnkb+mj4yvmJw9hgDkQDV4KmgodDekJbw2rCSyKyqMmREVGUaNsYg/1ysXwHSAe+wvh4Gt92qCahOPFEUlIyNcXnsEuq/V/OafuOeB71PRaYHpwRmhl2POJE5MmorJjsA6cSclJyj5zOzDt55lR+bsHps3mFZ4ryzxUUF5acO3+ttPPC0MXpstVyzGXaKywVXJW8VeSrwtUSNcq1lte8rsfdOFl3sb6u4V5jb9OL5uGW1zdHb727vX6HrU3mrtE91/aIjsP3czrPP6jqqnt4s7v10Z2eu72dj3v6Bp686196hj7nfCEzYDjoOhT4MmI49lXy6/SR06Olb2rf3hl7Mj72bvk9Oomd3PywDiPjy8zy7NLHpbnlT1/mVxfWl5Blxs9CXzRXXL8eWb2zhvluv17/k28j85f/MYAIK2FhoA7sYT1wHjxB8Igjch3DgUlDEfQ4VgT7ABeC34bvJRwiKhLnSJU0ybRhdBR6RwYrRjMmM+ZdLHasHmzh7GkcxZwtXC+517cJ8ZrxhfFnC1wldwm+E1oXYREVFVMQ3ylhuN1YUh/Gg4KM6A5OWZzsotxL+XsKFYqnlA4q+6hYqaqpCarTqH/WeKP5cOcNrSLtFB03XUU9kt5b/XqDY4ZuRvLGWONBkwrTg2ZW5gLmSxYdlrm7fK3UrOmsx22adp+w9dmjbcdht2j/yOGSY5KTi7O8C9Hl7d5G1+Nu3vs03Zndpz3aKHmeoV7G3vzen30e+hb7RfqbBvDBfP4gqDA4PMQolCd0IawzvDAikmoeKRS5FtUfXR4Tv98mViT224HeuJKD1HjF+IVDVQlBiQqJm0nPk2tSsg4fSPX/a2+a7RGLo4bHdqYrZUhmChxnOv7zxIeTPVlV2UdOueco5fKf5ssjnxHNlyyQO6taqFNkcs662LHE/bxfqd+FvRd3lelf0ihXuaxyZWeFSaVzVfjVjOqqmse189cZbkjXmdf7NhxuLGm61fyy5estjtuqrV538tse30PaFTu87p/sbH4w2rXRzfdIo8et91of75Nj/V+feT9/NqA3eP2l0HDua/xI7BvhMa133u/Pf1idCZtjnB9ZervC8y3jh/SW//++I9vKCXgVAEqHAHCgAcCqB4DiYQBEmQFghLWnDT0AduoAU+4LMDRa8Bpq9z/5gw3WmEawpowBJ0EF6ACjYA3hQBRhLUhFcpCryANY7/3AcGGUMLaYMFjVXcX0YuZQOljBWaHhaA7aiA6jP7GCWGNsEDYb24R9g8PhZHD2uCRcLe4tngmvh4/CX8GPElgJFoRUWFutE9WJB4i3iJskQ1ImaYBGkCaU5jYtPa0X7QM6KbpsujV6T5il1BkuM3IwHmFcYwpmGmd2Yu5nMWPpYNVlvcumx9bBbsLex2HP8ZYziHON6yg3D3c1jwHPq21UXjrear7dfN/4zwuYC6ySLwk6CJGE7ghHi8iKzIpeEfMTlxBflmjbfkLSXUpRmkZ6QubOjnOyCXIUeRMFWUVuJbzSmvInlXeqL9X61B9otGo27KzWuqRdrHNGN1svQz/ewN/QwcjEWNNEwVTaTNJc2kLeUmOXsZW9tZ9N/O4c2xt7ntl9deB1NHaKdC5zeenK5Ga+76j7Qwqtp41Xsvd1n0k/fv99AWWBy8GmIZfDGMIPRSxHhkR9itHafzL2Q5z+wUuHGBKSEteTEw/TpV5I0z3y/lhWhn7m2om6rMhTarno6RdnKgvSCn3PmZfolupc1L1kdNmywqHKs5pam3q9oO56w0Kz+c26VsW2J+3ZnYkPC3oG+8afjr4YHOp6dX309FjUhM2HnI/kBZ3l2yvnvtF+V/2hsSH6a/8QAnrAAySCc/DGYAT8RMiIARKAZCHXkH5kCdb3qpi9mETMJVjDL6HcqC4agJ6CN0UfsMzYnVh/7GlsB3YJJ4Czhv6ux03j+fEO+BP4hwSUoEtIILQRMbB+Pk4cIgmRIkj3aNhoAmju0vLQxtGO0ZnS1dGT6U8yIAwxsKb1Z5xk8mGahhXrF5YEVlrWc2xybJ3sbuxfObI4ZTh7uIK5Gbhv8DhtA9sqeR34iHy3+CMEtgtMkM8LeggJC00LXxM5KGoqxik2I35XonB7rKSTlIa0gAxBZnnHmGy/3H35mwo3FKuVapXrVG6p3ofZ643G/E6gxaotoaOt66AXpp9scNyw0Kja+J7JS9PPMHfJWdru2m9VbN1ls2TLu8fMLta+0uGtE5eznUvO3gE3nn0U90qPFU89r3jvRp8VP1X/xIDeIIHgmJDnYYrhZyI2Iv2insaI74+PHYiTO5gV/yVhX+LjZIOUtlT9v3qOOB2dTnfKeHRc50Rjlnz2tRzl3Dt5VmcmChILBYu6iqPPS5W+vZhzyah85crFSuuqteqLMPus3CipN29kaxprqbkV32rexn13qr3xfuoD24dC3cs9HY8bn7Q8bXveOdA7NDA8+vrD6OLb7+9w75k/bJvmmWWZw3yaXuhYyv5su4L7WvXNZO3Vut+PpY3YX/5XAnvhHdIl0A0WEE54eghDziGdyDxc8YbwJqcE04fZQGVRClzpXeg6Vh7rhy3GDuIYcebwpuUBnoi3wGfhhwhkQjDhFpGeSCG2kNhJUaQheA9STstKmwpvOsLoZui96d8xeDJMMgYyLjPFMxOZz7BIsNxmdWXDstWwu3IwcHRwxnOpc61xt/KkbrPm5eWd5+vgPysQSd4lKAnX8Kxwn0idaKFYmniUROB2T8l9Um7S7jI+O0Jl4+SOyRcqXFPsUppSIanuUHNUT9Wo15zWEtB21snTHdTnNnAzLDOaN9EyzTKbtjCyLLeitY62mbDdbydg3+po7TTgYr231U1oX4r7KEXV86TXnI+Fb60/Z0Ba4EZwUih9WHmEJXUjqiVGaf+lA1xxmfHgUEzCpyTf5PHD+1LfpHnAVRoPM8bLE6lZMtnPcsJPk/IK88ULagoViuqKFUqaSrUuPCyzvzR1+WAFS2XVVePqd7UJ17fdaK63axhp8myevRlzG99a0KZw92l7zH2hzhddmd3mPXS9LX18T5L6J5+ZP782wDmYODQ9vPvVrRGx0ew3P8eCxocnTN83Ta5+WJv6Nr0yszA79XF4rvtT/fzZhfhF5yX5Zdzys8/nvnisCMOqI2/VYnX9W+Wa7dra95J17fXRH/E/2X/WbBhvDG8Gb/k/0ldRYSt7AIROH14/vtnc/CwGAOEUAD+zNzfXL2xu/rwID5kjANwN/vt/ly1mPLyrL4I5BoDO5K2/dv77+R8P0NEUOETYwgAAAAlwSFlzAAALEwAACxMBAJqcGAAAA1NpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IlhNUCBDb3JlIDUuMS4yIj4KICAgPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6ZXhpZj0iaHR0cDovL25zLmFkb2JlLmNvbS9leGlmLzEuMC8iPgogICAgICAgICA8ZXhpZjpQaXhlbFlEaW1lbnNpb24+NzE8L2V4aWY6UGl4ZWxZRGltZW5zaW9uPgogICAgICAgICA8ZXhpZjpQaXhlbFhEaW1lbnNpb24+NjA8L2V4aWY6UGl4ZWxYRGltZW5zaW9uPgogICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6dGlmZj0iaHR0cDovL25zLmFkb2JlLmNvbS90aWZmLzEuMC8iPgogICAgICAgICA8dGlmZjpZUmVzb2x1dGlvbj43MjwvdGlmZjpZUmVzb2x1dGlvbj4KICAgICAgICAgPHRpZmY6Q29tcHJlc3Npb24+NTwvdGlmZjpDb21wcmVzc2lvbj4KICAgICAgICAgPHRpZmY6WFJlc29sdXRpb24+NzI8L3RpZmY6WFJlc29sdXRpb24+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICAgICA8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIgogICAgICAgICAgICB4bWxuczp4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iPgogICAgICAgICA8eG1wOkNyZWF0b3JUb29sPkFjb3JuIHZlcnNpb24gMy41PC94bXA6Q3JlYXRvclRvb2w+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICA8L3JkZjpSREY+CjwveDp4bXBtZXRhPgqb9JbbAAAGd0lEQVRIDX1We4xVRxn/zZzXfd9l9+7efcCy9LqsYFtAAVHTFaQtrba1plltDKVRUfoHxeCDBE0FTI3+gTXWxkRNUVpNWtbExDSUlhQW2kKjDZWHCyzsdndZdvfC3ru79577OOeec8ZvDpx100S/ZM7MfDPzPX7f980cCCHw0bZXCI5Dh5R5fH37uwOPbTp87pRsckxrerAu98ozwXx+z+QkoH379vG9y5cz0dPjBrznLow+dHLS3D5mWhtrqq7anoew6zhL4sZbqxtjL+xe0f5asJf19ip7+/vFnj17vDnebQVsQ1+f0rdhg0tzX+PvLo51Hh6d3TpRsZ52YnVhxywirXN0xAxcMm3MqGHUW2Yloau/Wb0g/OKetXcMSKGMaP3x48rx9eulkYLJJlEKNPYN32z+y2h++7/y5S2mGlpUrFRxb1PU3dCaZFcKFfbdT7TBEZ7Y9vaguFp2lGQkjKhbuZaJh1/a2lX3wprGxslAFmNgaiA8m81Gd56femCoaO+YNqLdltCwqU4VKzNpkdRULjfnqjU0hjR5nm1sTYoLF8Y9XThsSjEWTZr48fnT1+/JRG48v/+u1JF0Ol2SslW5e9c/hx84O2XuHDGr91t6FB/ntnj8zkbvyc40p2X+9KlB/G0kh/aYjjNTJvUGTt8oMk1hTAUTn0tobtFx+Hkn1D0zY3Z/48zNN1ekKr/6+ZqOI0r44S3JE9niwVwsdU+dZ2NbZoHzszUdfG1jXAonCIHhYhUfkOCqK3A2b+KVoSl8SDzbE7i7PsoOfn4pfzzTCM2tuUOlGs/HU5mpfH7ZpWLpVfVYzjQmy1XNdXLYtTztfL2zSQkEXytZOJsrYXUqhk83xXH0+gwpAzzyPaorGDYtxHUVnPt2sKeWtSj1uuo8cz6rVmq2NlT2dLVBD3nDqNU452iLGXNWS8uvzFbw/fcGsWnhAmztakaVLD6XLyFBwi3y5pMNMdzXlpRbA2KtUYNzhUPUWC1shD0/BvA84gCm46e/zCjfpC+01mH/ugwFVsW6pgT+Pponj0xM2y4WRgwc6F6KjrgRCJe9KNQcPyUZBK+VSxSjgEgkxSyYzfUPt9ejRIp3nB7EsfEZJAmSMYJuRUPEFz5RtnGjUiOPPKwlGOtoXVoY5P0tBRKY/0P7zozg0NBNNEd0X1lzWMeWzjROTRaw5eQAbBK+oj6KP61fipqYK2Jfoq+AEyISHO22B+9OzqKFhN2RCOOX58bwyuAUWmmuUZxcz4VNQb48U0G2YkFiSzWB3SvbUbAdHBjI+oJDFPgBqv45iGQl1Ruaf/HtfG8IYZXjU5Q9JyYKiGkKwcdRoyBTySFfdTBO0Dy1rBUPtaeQSYTm/JcQucKlBtQT1wdHI+gl+tfLlrxL8KNVi3ycZb5LLKUyuqSgkPBCzcWXFtfje3e1IUL8+cKllkfaG8gY+PtbYnHwCXJDVxUvRKn12/5xnBifZo8uTuErHSnKd5DVnm+FtMSTDKIHKW3/B/lZIj8CzNMiUcHzNU3CqBI4sjrFt965Kra9cwWbP9aE/WuXIEHwmGS1Ks0iYqTj1siffvQjaq4nPDKKSC3O5BTeFY9Z5KmjxBKIkRTHE66EbCUV0ebOJjy7usOHSKajLFgZg78O59A3PouDFNBBujIC+sfNovvipUmmxZMUN+Y08pil/PulX1tHxvI5r1xa50YSdVTRvDmkeKvqo0Lm/JJ4iH02nUDOcjBRskkB92P1xtg0Dl+bBl0nokFXxYErWfGLS1NKVqiswSqMtoT0Z/58f9cHcy/as+9/2PV+vvTEDct5oqCG2xPCwaNtCZfuF0aPCiPP2ZeP9uNqoYoFdFWYLoXdY0K+UFxTFVvREbJLo4tjkZe7W+pe3nV362XpGVU0PTj/LTzsePvq8vGK/ZORqv21GW5giS7wZCblyUr94+UsK1JVU0L4T5THVS6MEDSrjIVh7dVVDdGf7l7V3h9ARogy3wM5QC+46PHrTa4b+y+MfPHkdfPbI6a1yQ5HOatWEGLCk8VG+cp5KAKlUvIIzjfWtcT+8IM7Fx+mc5Y8/NVeKL09fhLK5/JW6t1a6FV6aTDv0Q/98PTgg+fy5e/MOs59PJqQVzmUsukmDfXo0kTo9899JvM6sfxIy0e/hyaH5v00+JUrlcxvPfQbQvt85bf5xjePXXxs42tnj9xLbfPRi/K3xQjOyL3yTDCf3/8H+UFA5Uwbuc8AAAAASUVORK5CYII= - {"ETag":"\"067736a547cafe90014b4e59b6510abe\""} - true - true - true - 0.0 - 0.0 - - - Bing aerial imagery - Bing - bing - http://www.bing.com/maps/ - 22 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAMAAADXqc3KAAAAdVBMVEX/phX/04r/////6cX/zXz/7Mz/vFD/u0z/1I7/tT3/yXH/uEX/v1f/rCT/2pz/vlP/qRz/4a//yG3/xmn//Pj/9eb/+/T/897/t0H/wl7/sTL//vv/+O3/2Jn/7dD/+vH/9+n/3KT/tDr/9OL/8Nf/26D/ynSCVQVOAAAAkklEQVR4Xq3R1w7DIBQD0NiQne69d///E3tvBYVU6UsVPyEdCYycIOlOv5AB004Aaf6DCpLtF4yxp8tkFMGCkiEkKyGz9qCxrkxuhLIAeaijMvAwi/vMycJDuyi5/AVUaPwTPik5UdCDiWCjtd5Q70TK+KKD26M+6o+tdGxwIlmFPeyZn1yuraFKFOnt/sCz/81f+9UEaf1lPCAAAAAASUVORK5CYII= - {"X-VE-Tile-Info":"no-tile"} - {"X-VE-TILEMETA-CaptureDatesRange":"Capture Date"} - true - true - true - 0.0 - 0.0 - - - diff --git a/JOSM/sessions/sidewalks.jos b/JOSM/sessions/sidewalks.jos deleted file mode 100644 index 0d50bcf..0000000 --- a/JOSM/sessions/sidewalks.jos +++ /dev/null @@ -1,66 +0,0 @@ - - - -
- - - - - Strava running heatmap - strava_running_heatmap - tms - http://globalheat.strava.com/tiles/running/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - Sidewalks - tms - https://{switch:a,b,c}.tiles.mapbox.com/v4/tcql.usa-sidewalks/{zoom}/{x}/{y}.png?access_token=pk.eyJ1IjoidGNxbCIsImEiOiJaSlZ6X3JZIn0.mPwXgf3BvAR4dPuBB3ypfA - true - true - true - 0.0 - 0.0 - - - Strava cycling heatmap - strava_cycling_heatmap - tms - http://globalheat.strava.com/tiles/cycling/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - Bing aerial imagery - Bing - bing - http://www.bing.com/maps/ - 22 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAMAAADXqc3KAAAAdVBMVEX/phX/04r/////6cX/zXz/7Mz/vFD/u0z/1I7/tT3/yXH/uEX/v1f/rCT/2pz/vlP/qRz/4a//yG3/xmn//Pj/9eb/+/T/897/t0H/wl7/sTL//vv/+O3/2Jn/7dD/+vH/9+n/3KT/tDr/9OL/8Nf/26D/ynSCVQVOAAAAkklEQVR4Xq3R1w7DIBQD0NiQne69d///E3tvBYVU6UsVPyEdCYycIOlOv5AB004Aaf6DCpLtF4yxp8tkFMGCkiEkKyGz9qCxrkxuhLIAeaijMvAwi/vMycJDuyi5/AVUaPwTPik5UdCDiWCjtd5Q70TK+KKD26M+6o+tdGxwIlmFPeyZn1yuraFKFOnt/sCz/81f+9UEaf1lPCAAAAAASUVORK5CYII= - {"X-VE-Tile-Info":"no-tile"} - {"X-VE-TILEMETA-CaptureDatesRange":"Capture Date"} - true - true - true - 0.0 - 0.0 - - - diff --git a/JOSM/sessions/team_edits.jos b/JOSM/sessions/team_edits.jos deleted file mode 100644 index 949d9f9..0000000 --- a/JOSM/sessions/team_edits.jos +++ /dev/null @@ -1,104 +0,0 @@ - - - -
- - - - - team-edits - tms - http://{switch:a,b,c}.tiles.mapbox.com/v4/planemad.8715bc28/{zoom}/{x}/{y}.png?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcCIsImEiOiJncjlmd0t3In0.DmZsIeOW-3x-C5eX-wAqTw - true - true - true - 0.0 - 0.0 - - - GSIMaps/ort - tms - http://cyberjapandata.gsi.go.jp/xyz/ort/{z}/{x}/{y}.jpg - true - true - true - 0.0 - 0.0 - - - Strava running heatmap - strava_running_heatmap - tms - http://globalheat.strava.com/tiles/running/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - Strava cycling heatmap - strava_cycling_heatmap - tms - http://globalheat.strava.com/tiles/cycling/color2/{zoom}/{x}/{y}.png - http://labs.strava.com/heatmap/ - http://labs.strava.com/heatmap/ - 17 - 3 - https://d3nn82uaxijpm6.cloudfront.net/assets/website/mobile/icon-app-81cc8ba60200bed099176eb699e218ab.png - true - true - true - 0.0 - 0.0 - - - OpenStreetMap GPS Traces - osm-gps - tms - https://gps-{switch:a,b,c}.tile.openstreetmap.org/lines/{zoom}/{x}/{y}.png - © OpenStreetMap contributors, CC-BY-SA - https://openstreetmap.org/ - 20 - true - true - true - 0.0 - 0.0 - - - Mapbox Satellite - Mapbox - tms - http://{switch:a,b,c}.tiles.mapbox.com/v4/openstreetmap.map-inh7ifmo/{zoom}/{x}/{y}.png?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcCIsImEiOiJncjlmd0t3In0.DmZsIeOW-3x-C5eX-wAqTw - 19 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAYAAADgdz34AAAYJWlDQ1BJQ0MgUHJvZmlsZQAAWAmteXk4ld3X/77PfUbzPGU4Zhkyz5nnISRzxDHPwzEkyZRHhYpIRKSkECpzJUWSSBqQokgyJFNJUrxbTz3P93u9v/e/331d5z6fs/baa6+91tp77bUPADz1lPDwYAwTACGhUVRbE32yk7MLmTACSIAL0IMdgJ7iFRmuZ2NjCf7P5+sgQLYan8tsyfo/2f7fDczePpFeACA2sNnTO9IrBOJ6ANBmr3BqFAC4LXki+6PCt3AWxGxUqCDEZVvY72/cvIU9/8a9v3jsbA0gzxgARDoKheoHAP0cpJNjvPygHAY6APAsod4BobAbGWJtL3+KNwA8HpBHOiQkbAtnQizh+R9y/P4DUyie/8ikUPz+wX/PBfaEAxsGRIYHUw78+vH/8xUSHA3t9evhh2+6yKA9FvCbA9ot1otitAdiLohP+PuYWf6ml4dH6dv+pt8OiDKzg5gN8rzwjza1/42no4Ps9SDmhfQfQWEWW/zQThiuUE8ra4hZIBbxijSAtt8aC6MS52/n+JvH0tvH0AhiGEUYJ2qY7R9+/8iYPX/ocXH+BlZ/+AMp5lv+ZoD86RQqRL/0weT7BJtsjSsE6VfDo2y29Nwaqy802Or3XDDvfanGWzxb9O8+kb/mu6Wbf5S/nSmkQ51Rpiiq3RYPnCPK6xtgbAYx1A2V86ea/qHrhgf/imnYF7WjRttu2UEEYl+fUPstG27R070phlu2hTZBi4AxoAAq8AGeIBTMADKwBAbA8PebDOmhkOYFwkAw/FDJjH9acB9wT3HvcAO4MdzwHxrs+ZsPBABviP+W9R/9IX0PiAOfoFQfEPlnNCwPVhuribWEb134UcCqYdX/tPXNNc39wb919YN9ZX7L1v+tfQyU+PMPn3tACvUP/t3H858e/1snY/AeWsDvD4dcldyM3I8//f+dMd4Ib4g3xRvjt6NH0Tq0C72HdqO30SZARtvQZrQXbd3Cv/X6MwoFUrassmXhSGABregDon/9Cv0z3n9ZKfofjt8SGCQZlIEt7BUKgmBbwD8jOPzSOuB/SYmGHJ5wxEDIa/GPP37rhRWD1lXG6mO1oJ2hjbEcWB4gg1WCFtfD6kAfKEPqv17879nIAN9f1o75NZcg8AHOIyTKJzYKxhIwCAs/QA3w848i68Hd0keabBbqtUOarCAnrwC29t4tHgA+2/7aUxGOJ//SqC0A7NSCsbjyL82DB4A6uC8yh/xLE0FhuCsC0PrIK5oa87c87NYXDtAARrgquAE/EAYS0CIKQAVoAl1gBMyBNbADzmAfjGF/EAI13g/iQTJIAxkgC5wGZ0EJuAiugGpwAzSB2+AeeAB6QD8YAK/BGJgEH8Ei+ArWEQQhIPQIK8KNCCCiiBSigKgh2ogRYonYIs6IB+KHhCLRSDxyGMlATiFnkVKkArmOtCD3kG7kKTKMjCMzyDLyHYNi6DBsGD6MGEYWo4bRw1hg7DBuGD9MBCYOk4o5gcnHXMBcxTRi7mF6MAOYMcxHzAoKUFqUAxVEZVA11AC1Rl1QX5SKJqDpaB56Aa1Bb8JYfI6OoXPoGhaPZcWSsTLQk6ZYe6wXNgKbgM3EnsVewTZi72OfY8exi9gNHD2OFyeF08CZ4Zxwfrj9uDRcHq4c14DrhOt5EvcVj8dz4MXxqjDanfGB+IP4TPw5fC3+Lv4pfgK/QiAQuAlSBC2CNYFCiCKkEQoIVwlthGeEScI3Ii1RgKhANCa6EEOJKcQ8YiXxDvEZcYq4TmIiiZI0SNYkb9IB0klSGekm6QlpkrROw0wjTqNFY0cTSJNMk09TQ9NJM0LzmZaWVohWnXY3bQBtEm0+7TXah7TjtGt0LHSSdAZ0rnTRdCfoLtPdpRum+0xPTy9Gr0vvQh9Ff4K+gr6D/g39NwZWhh0MZgzeDIkMhQyNDM8Y5hlJjKKMeoz7GOMY8xjrGJ8wzjGRmMSYDJgoTAlMhUwtTENMK8yszPLM1swhzJnMlczdzNMsBBYxFiMWb5ZUlossHSwTrCirMKsBqxfrYdYy1k7WSTY8mzibGVsgWwZbNVsf2yI7C7sSuwN7LHsheyv7GAfKIcZhxhHMcZLjBscgx3dOPk49Th/OY5w1nM84V7m2cely+XClc9VyDXB95yZzG3EHcWdzN3GP8mB5JHl28+znKebp5JnbxrZNc5vXtvRtN7a94sXwSvLa8h7kvcjby7vCx89nwhfOV8DXwTfHz8Gvyx/In8t/h39GgFVAWyBAIFegTWCWzE7WIweT88n3yYuCvIKmgtGCpYJ9gutC4kL2QilCtUKjwjTCasK+wrnC7cKLIgIiu0TiRapEXomSRNVE/UXPiHaJroqJizmKHRFrEpsW5xI3E48TrxIfkaCX0JGIkLgg8WI7frva9qDt57b3S2IklSX9JQsln0hhpFSkAqTOST2VxkmrS4dKX5AekqGT0ZOJkamSGd/BscNyR8qOph3zsiKyLrLZsl2yG3LKcsFyZXKv5VnkzeVT5G/KLytIKngpFCq8UKRXNFZMVGxWXFKSUvJRKlZ6qcyqvEv5iHK78k8VVRWqSo3KjKqIqodqkeqQGpuajVqm2kN1nLq+eqL6bfU1DRWNKI0bGguaMppBmpWa0zvFd/rsLNs5oSWkRdEq1RrTJmt7aJ/XHtMR1KHoXNB5pyus661brjult10vUO+q3ry+nD5Vv0F/1UDD4JDBXUPU0MQw3bDPiMXI3uis0RtjIWM/4yrjRRNlk4Mmd01xpham2aZDZnxmXmYVZovmquaHzO9b0FnssThr8c5S0pJqeXMXZpf5rpxdI1aiVqFWTdbA2sw6x3rURtwmwubWbvxum92Fuz/YytvG23btYd3jvqdyz1c7fbuTdq/tJeyj7dsdGB1cHSocVh0NHU85jjnJOh1y6nHmcQ5wbnYhuDi4lLus7DXae3rvpKuya5rroJu4W6xb9z6efcH7Wt0Z3SnudR44D0ePSo8fFGvKBcqKp5lnkeeil4HXGa+P3rreud4zPlo+p3ymfLV8T/lO+2n55fjN+Ov45/nPBRgEnA1YCjQNLAlcDbIOuhy0GewYXBtCDPEIaQllCQ0KvR/GHxYb9jRcKjwtfCxCI+J0xCLVgloeiUS6RTZHscFDbm+0RPRf0eMx2jGFMd/2O+yvi2WODY3tPSB54NiBqTjjuEsHsQe9DrbHC8Ynx48f0jtUmoAkeCa0JwonpiZOJpkkXUmmSQ5Kfpwil3Iq5cthx8M3U/lSk1In/jL5qyqNIY2aNnRE80jJUezRgKN9xxSPFRzbSPdOf5Qhl5GX8SPTK/PRcfnj+cc3T/ie6DupcrI4C58VmjWYrZN95RTzqbhTEzm7chpzybnpuV9Ou5/uzlPKKzlDcyb6zFi+ZX5zgUhBVsGPs/5nBwr1C2uLeIuOFa2e8z73rFi3uKaErySj5Pv5gPMvS01KGy+IXci7iL8Yc/FDmUNZ1yW1SxXlPOUZ5T8vh14eu2J75X6FakVFJW/lySpMVXTVzFXXq/3VhtXNNTI1pbUctRnXwLXoa7PXPa4P3rC40V6nVldTL1pf1MDakN6INB5oXGzybxprdm5+2mLe0n5T82bDrR23Lt8WvF3Yyt568g7NndQ7m21xbSt3w+/O3fO7N9Hu3v66w6njxf3d9/s6LTofPjB+0NGl19X2UOvh7W6N7pZHao+aelR6GnuVexseKz9u6FPpa3yi+qS5X73/5tOdT+8803l277nh8wcvzF70DFgNPB20H3w55Do09tL75fRw8PDSq5hX66+TRnAj6aNMo3lveN9ceLv9be2YyljruOF477s9715PeE18fB/5/sdk6gf6D3lTAlMV0wrTt2eMZ/pn985Ofgz/uD6X9on5U9G8xHz9gu5C76LT4uQSdWlzOfMz9+fLX5S+tK/YrLz5GvJ1fTX9G/e3K2tqa13fHb9Pre//QfiR/3P7z5sbFhsjmyGbm+EUKuXXWQCeDgDG1xeA5cuwLnIGgLUfABqGv2ujXxzwiIFAHoix8LQgB1xADhiBuTwRGcfYY4ZRPyyKbcBF4jUIdIQ54gipl6ad9j5dF/1jhiEmReYSVla2Y+wbnAncKE8qLzNfqYAy+aGQrwhBtEp8j8SGZLW0q8ysbIDcrIKf4riys0qPmqp6iSayc6/WNR1E11ovV/+1Ib/RbmMPkzDTJLNs84sWDZbdu0atlm2Iu8m2anus7fztDzuUODY59TlP70Vcud0U91m6e3scpOR6Vnm1ew/7LPnR+PMFSAeqBRkH24VQQsPCDoYfjcillkZejWqJvh/zdP/r2DcHxuPeH5yKnzk0mzCX+ClpPnk+Zf7wfOrCXwtpn47MHp0+NpU+nfExc+H41xObWTTZnKfEclRyzU775GWeqc9/VbBZKFRkcI5SfKgk//z10u4Lby+uXCKV81yWuqJRYVbpWOV1Naz6QE0KjNjc60U3yura6kcb1pqYm0VblG/q3jK+bdpqfEe3Tf2u3D3ldpuOgPtJnbkPyrpqHzZ0Nz2q76npLXtc0Jf+JK4/4KnjM8Pn8i94B/AD84ODQ7dfXhg+8sr/tfGI0Mjm6Miblrd5Y1Hjtu/kJhgnPr3vnSz5EDilMLU63TRDnZWYffkxeU50rvOTx6f1+dIFs4XPiyVLlks/lms+U75wfulbOfJV7evIqvNq/zfrb8/XAr/Tfu9Zv/yj+Gf1xpPNTeh/FNZTvEAZOIIU0Ai+IPpIEQaDicIso/FYFuxNXDA8/cwSGoiHSU40KrTMtEv0JAYlRg+mDOY7LN/ZFNijOW5x0XA78VzlJfD58HeTdwjmCKMioaL94vIS6dvfS+2UzpaZkN0hFynfoLCgJKZsp5KsWqnWr/5Zk2YnuxaftrCOhK6Mnry+vIGcoayRjLGEiZAprxmnOZMF0eKH5dKuKasR62c2j3a3297a02BXY1/hUOZ43qnIOd8ld2+m619uh/bFuId5+FPcPR28dnkb+mj4yvmJw9hgDkQDV4KmgodDekJbw2rCSyKyqMmREVGUaNsYg/1ysXwHSAe+wvh4Gt92qCahOPFEUlIyNcXnsEuq/V/OafuOeB71PRaYHpwRmhl2POJE5MmorJjsA6cSclJyj5zOzDt55lR+bsHps3mFZ4ryzxUUF5acO3+ttPPC0MXpstVyzGXaKywVXJW8VeSrwtUSNcq1lte8rsfdOFl3sb6u4V5jb9OL5uGW1zdHb727vX6HrU3mrtE91/aIjsP3czrPP6jqqnt4s7v10Z2eu72dj3v6Bp686196hj7nfCEzYDjoOhT4MmI49lXy6/SR06Olb2rf3hl7Mj72bvk9Oomd3PywDiPjy8zy7NLHpbnlT1/mVxfWl5Blxs9CXzRXXL8eWb2zhvluv17/k28j85f/MYAIK2FhoA7sYT1wHjxB8Igjch3DgUlDEfQ4VgT7ABeC34bvJRwiKhLnSJU0ybRhdBR6RwYrRjMmM+ZdLHasHmzh7GkcxZwtXC+517cJ8ZrxhfFnC1wldwm+E1oXYREVFVMQ3ylhuN1YUh/Gg4KM6A5OWZzsotxL+XsKFYqnlA4q+6hYqaqpCarTqH/WeKP5cOcNrSLtFB03XUU9kt5b/XqDY4ZuRvLGWONBkwrTg2ZW5gLmSxYdlrm7fK3UrOmsx22adp+w9dmjbcdht2j/yOGSY5KTi7O8C9Hl7d5G1+Nu3vs03Zndpz3aKHmeoV7G3vzen30e+hb7RfqbBvDBfP4gqDA4PMQolCd0IawzvDAikmoeKRS5FtUfXR4Tv98mViT224HeuJKD1HjF+IVDVQlBiQqJm0nPk2tSsg4fSPX/a2+a7RGLo4bHdqYrZUhmChxnOv7zxIeTPVlV2UdOueco5fKf5ssjnxHNlyyQO6taqFNkcs662LHE/bxfqd+FvRd3lelf0ihXuaxyZWeFSaVzVfjVjOqqmse189cZbkjXmdf7NhxuLGm61fyy5estjtuqrV538tse30PaFTu87p/sbH4w2rXRzfdIo8et91of75Nj/V+feT9/NqA3eP2l0HDua/xI7BvhMa133u/Pf1idCZtjnB9ZervC8y3jh/SW//++I9vKCXgVAEqHAHCgAcCqB4DiYQBEmQFghLWnDT0AduoAU+4LMDRa8Bpq9z/5gw3WmEawpowBJ0EF6ACjYA3hQBRhLUhFcpCryANY7/3AcGGUMLaYMFjVXcX0YuZQOljBWaHhaA7aiA6jP7GCWGNsEDYb24R9g8PhZHD2uCRcLe4tngmvh4/CX8GPElgJFoRUWFutE9WJB4i3iJskQ1ImaYBGkCaU5jYtPa0X7QM6KbpsujV6T5il1BkuM3IwHmFcYwpmGmd2Yu5nMWPpYNVlvcumx9bBbsLex2HP8ZYziHON6yg3D3c1jwHPq21UXjrear7dfN/4zwuYC6ySLwk6CJGE7ghHi8iKzIpeEfMTlxBflmjbfkLSXUpRmkZ6QubOjnOyCXIUeRMFWUVuJbzSmvInlXeqL9X61B9otGo27KzWuqRdrHNGN1svQz/ewN/QwcjEWNNEwVTaTNJc2kLeUmOXsZW9tZ9N/O4c2xt7ntl9deB1NHaKdC5zeenK5Ga+76j7Qwqtp41Xsvd1n0k/fv99AWWBy8GmIZfDGMIPRSxHhkR9itHafzL2Q5z+wUuHGBKSEteTEw/TpV5I0z3y/lhWhn7m2om6rMhTarno6RdnKgvSCn3PmZfolupc1L1kdNmywqHKs5pam3q9oO56w0Kz+c26VsW2J+3ZnYkPC3oG+8afjr4YHOp6dX309FjUhM2HnI/kBZ3l2yvnvtF+V/2hsSH6a/8QAnrAAySCc/DGYAT8RMiIARKAZCHXkH5kCdb3qpi9mETMJVjDL6HcqC4agJ6CN0UfsMzYnVh/7GlsB3YJJ4Czhv6ux03j+fEO+BP4hwSUoEtIILQRMbB+Pk4cIgmRIkj3aNhoAmju0vLQxtGO0ZnS1dGT6U8yIAwxsKb1Z5xk8mGahhXrF5YEVlrWc2xybJ3sbuxfObI4ZTh7uIK5Gbhv8DhtA9sqeR34iHy3+CMEtgtMkM8LeggJC00LXxM5KGoqxik2I35XonB7rKSTlIa0gAxBZnnHmGy/3H35mwo3FKuVapXrVG6p3ofZ643G/E6gxaotoaOt66AXpp9scNyw0Kja+J7JS9PPMHfJWdru2m9VbN1ls2TLu8fMLta+0uGtE5eznUvO3gE3nn0U90qPFU89r3jvRp8VP1X/xIDeIIHgmJDnYYrhZyI2Iv2insaI74+PHYiTO5gV/yVhX+LjZIOUtlT9v3qOOB2dTnfKeHRc50Rjlnz2tRzl3Dt5VmcmChILBYu6iqPPS5W+vZhzyah85crFSuuqteqLMPus3CipN29kaxprqbkV32rexn13qr3xfuoD24dC3cs9HY8bn7Q8bXveOdA7NDA8+vrD6OLb7+9w75k/bJvmmWWZw3yaXuhYyv5su4L7WvXNZO3Vut+PpY3YX/5XAnvhHdIl0A0WEE54eghDziGdyDxc8YbwJqcE04fZQGVRClzpXeg6Vh7rhy3GDuIYcebwpuUBnoi3wGfhhwhkQjDhFpGeSCG2kNhJUaQheA9STstKmwpvOsLoZui96d8xeDJMMgYyLjPFMxOZz7BIsNxmdWXDstWwu3IwcHRwxnOpc61xt/KkbrPm5eWd5+vgPysQSd4lKAnX8Kxwn0idaKFYmniUROB2T8l9Um7S7jI+O0Jl4+SOyRcqXFPsUppSIanuUHNUT9Wo15zWEtB21snTHdTnNnAzLDOaN9EyzTKbtjCyLLeitY62mbDdbydg3+po7TTgYr231U1oX4r7KEXV86TXnI+Fb60/Z0Ba4EZwUih9WHmEJXUjqiVGaf+lA1xxmfHgUEzCpyTf5PHD+1LfpHnAVRoPM8bLE6lZMtnPcsJPk/IK88ULagoViuqKFUqaSrUuPCyzvzR1+WAFS2XVVePqd7UJ17fdaK63axhp8myevRlzG99a0KZw92l7zH2hzhddmd3mPXS9LX18T5L6J5+ZP782wDmYODQ9vPvVrRGx0ew3P8eCxocnTN83Ta5+WJv6Nr0yszA79XF4rvtT/fzZhfhF5yX5Zdzys8/nvnisCMOqI2/VYnX9W+Wa7dra95J17fXRH/E/2X/WbBhvDG8Gb/k/0ldRYSt7AIROH14/vtnc/CwGAOEUAD+zNzfXL2xu/rwID5kjANwN/vt/ly1mPLyrL4I5BoDO5K2/dv77+R8P0NEUOETYwgAAAAlwSFlzAAALEwAACxMBAJqcGAAAA1NpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IlhNUCBDb3JlIDUuMS4yIj4KICAgPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6ZXhpZj0iaHR0cDovL25zLmFkb2JlLmNvbS9leGlmLzEuMC8iPgogICAgICAgICA8ZXhpZjpQaXhlbFlEaW1lbnNpb24+NzE8L2V4aWY6UGl4ZWxZRGltZW5zaW9uPgogICAgICAgICA8ZXhpZjpQaXhlbFhEaW1lbnNpb24+NjA8L2V4aWY6UGl4ZWxYRGltZW5zaW9uPgogICAgICA8L3JkZjpEZXNjcmlwdGlvbj4KICAgICAgPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIKICAgICAgICAgICAgeG1sbnM6dGlmZj0iaHR0cDovL25zLmFkb2JlLmNvbS90aWZmLzEuMC8iPgogICAgICAgICA8dGlmZjpZUmVzb2x1dGlvbj43MjwvdGlmZjpZUmVzb2x1dGlvbj4KICAgICAgICAgPHRpZmY6Q29tcHJlc3Npb24+NTwvdGlmZjpDb21wcmVzc2lvbj4KICAgICAgICAgPHRpZmY6WFJlc29sdXRpb24+NzI8L3RpZmY6WFJlc29sdXRpb24+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICAgICA8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIgogICAgICAgICAgICB4bWxuczp4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iPgogICAgICAgICA8eG1wOkNyZWF0b3JUb29sPkFjb3JuIHZlcnNpb24gMy41PC94bXA6Q3JlYXRvclRvb2w+CiAgICAgIDwvcmRmOkRlc2NyaXB0aW9uPgogICA8L3JkZjpSREY+CjwveDp4bXBtZXRhPgqb9JbbAAAGd0lEQVRIDX1We4xVRxn/zZzXfd9l9+7efcCy9LqsYFtAAVHTFaQtrba1plltDKVRUfoHxeCDBE0FTI3+gTXWxkRNUVpNWtbExDSUlhQW2kKjDZWHCyzsdndZdvfC3ru79577OOeec8ZvDpx100S/ZM7MfDPzPX7f980cCCHw0bZXCI5Dh5R5fH37uwOPbTp87pRsckxrerAu98ozwXx+z+QkoH379vG9y5cz0dPjBrznLow+dHLS3D5mWhtrqq7anoew6zhL4sZbqxtjL+xe0f5asJf19ip7+/vFnj17vDnebQVsQ1+f0rdhg0tzX+PvLo51Hh6d3TpRsZ52YnVhxywirXN0xAxcMm3MqGHUW2Yloau/Wb0g/OKetXcMSKGMaP3x48rx9eulkYLJJlEKNPYN32z+y2h++7/y5S2mGlpUrFRxb1PU3dCaZFcKFfbdT7TBEZ7Y9vaguFp2lGQkjKhbuZaJh1/a2lX3wprGxslAFmNgaiA8m81Gd56femCoaO+YNqLdltCwqU4VKzNpkdRULjfnqjU0hjR5nm1sTYoLF8Y9XThsSjEWTZr48fnT1+/JRG48v/+u1JF0Ol2SslW5e9c/hx84O2XuHDGr91t6FB/ntnj8zkbvyc40p2X+9KlB/G0kh/aYjjNTJvUGTt8oMk1hTAUTn0tobtFx+Hkn1D0zY3Z/48zNN1ekKr/6+ZqOI0r44S3JE9niwVwsdU+dZ2NbZoHzszUdfG1jXAonCIHhYhUfkOCqK3A2b+KVoSl8SDzbE7i7PsoOfn4pfzzTCM2tuUOlGs/HU5mpfH7ZpWLpVfVYzjQmy1XNdXLYtTztfL2zSQkEXytZOJsrYXUqhk83xXH0+gwpAzzyPaorGDYtxHUVnPt2sKeWtSj1uuo8cz6rVmq2NlT2dLVBD3nDqNU452iLGXNWS8uvzFbw/fcGsWnhAmztakaVLD6XLyFBwi3y5pMNMdzXlpRbA2KtUYNzhUPUWC1shD0/BvA84gCm46e/zCjfpC+01mH/ugwFVsW6pgT+Pponj0xM2y4WRgwc6F6KjrgRCJe9KNQcPyUZBK+VSxSjgEgkxSyYzfUPt9ejRIp3nB7EsfEZJAmSMYJuRUPEFz5RtnGjUiOPPKwlGOtoXVoY5P0tBRKY/0P7zozg0NBNNEd0X1lzWMeWzjROTRaw5eQAbBK+oj6KP61fipqYK2Jfoq+AEyISHO22B+9OzqKFhN2RCOOX58bwyuAUWmmuUZxcz4VNQb48U0G2YkFiSzWB3SvbUbAdHBjI+oJDFPgBqv45iGQl1Ruaf/HtfG8IYZXjU5Q9JyYKiGkKwcdRoyBTySFfdTBO0Dy1rBUPtaeQSYTm/JcQucKlBtQT1wdHI+gl+tfLlrxL8KNVi3ycZb5LLKUyuqSgkPBCzcWXFtfje3e1IUL8+cKllkfaG8gY+PtbYnHwCXJDVxUvRKn12/5xnBifZo8uTuErHSnKd5DVnm+FtMSTDKIHKW3/B/lZIj8CzNMiUcHzNU3CqBI4sjrFt965Kra9cwWbP9aE/WuXIEHwmGS1Ks0iYqTj1siffvQjaq4nPDKKSC3O5BTeFY9Z5KmjxBKIkRTHE66EbCUV0ebOJjy7usOHSKajLFgZg78O59A3PouDFNBBujIC+sfNovvipUmmxZMUN+Y08pil/PulX1tHxvI5r1xa50YSdVTRvDmkeKvqo0Lm/JJ4iH02nUDOcjBRskkB92P1xtg0Dl+bBl0nokFXxYErWfGLS1NKVqiswSqMtoT0Z/58f9cHcy/as+9/2PV+vvTEDct5oqCG2xPCwaNtCZfuF0aPCiPP2ZeP9uNqoYoFdFWYLoXdY0K+UFxTFVvREbJLo4tjkZe7W+pe3nV362XpGVU0PTj/LTzsePvq8vGK/ZORqv21GW5giS7wZCblyUr94+UsK1JVU0L4T5THVS6MEDSrjIVh7dVVDdGf7l7V3h9ARogy3wM5QC+46PHrTa4b+y+MfPHkdfPbI6a1yQ5HOatWEGLCk8VG+cp5KAKlUvIIzjfWtcT+8IM7Fx+mc5Y8/NVeKL09fhLK5/JW6t1a6FV6aTDv0Q/98PTgg+fy5e/MOs59PJqQVzmUsukmDfXo0kTo9899JvM6sfxIy0e/hyaH5v00+JUrlcxvPfQbQvt85bf5xjePXXxs42tnj9xLbfPRi/K3xQjOyL3yTDCf3/8H+UFA5Uwbuc8AAAAASUVORK5CYII= - {"ETag":"\"067736a547cafe90014b4e59b6510abe\""} - true - true - true - 0.0 - 0.0 - - - Bing aerial imagery - Bing - bing - http://www.bing.com/maps/ - 22 - data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAMAAADXqc3KAAAAdVBMVEX/phX/04r/////6cX/zXz/7Mz/vFD/u0z/1I7/tT3/yXH/uEX/v1f/rCT/2pz/vlP/qRz/4a//yG3/xmn//Pj/9eb/+/T/897/t0H/wl7/sTL//vv/+O3/2Jn/7dD/+vH/9+n/3KT/tDr/9OL/8Nf/26D/ynSCVQVOAAAAkklEQVR4Xq3R1w7DIBQD0NiQne69d///E3tvBYVU6UsVPyEdCYycIOlOv5AB004Aaf6DCpLtF4yxp8tkFMGCkiEkKyGz9qCxrkxuhLIAeaijMvAwi/vMycJDuyi5/AVUaPwTPik5UdCDiWCjtd5Q70TK+KKD26M+6o+tdGxwIlmFPeyZn1yuraFKFOnt/sCz/81f+9UEaf1lPCAAAAAASUVORK5CYII= - {"X-VE-Tile-Info":"no-tile"} - {"X-VE-TILEMETA-CaptureDatesRange":"Capture Date"} - true - true - true - 0.0 - 0.0 - - - diff --git a/JOSM/tasks-config/josm-config-turnlanes.json b/JOSM/tasks-config/josm-config-turnlanes.json deleted file mode 100644 index cce6984..0000000 --- a/JOSM/tasks-config/josm-config-turnlanes.json +++ /dev/null @@ -1,70 +0,0 @@ -{ - "project": { - "type": "task", - "name": "Turn Lanes", - "description": "Mapping turn lanes from satellite imagery", - "doc_url": "https://github.com/mapbox/mapping/issues/153", - "changeset": { - "comment": "Add missing turn lanes from satellite imagery https://github.com/mapbox/mapping/issues/153", - "source":"" - }, - "imagery": [ - { - "name": "USGS High Quality", - "url": "http://{switch:a,b,c}.tile.openstreetmap.us/usgs_large_scale/{zoom}/{x}/{y}.jpg" - }, - { - "name": "Mapbox Satellite", - "url": "http://{switch:a,b,c}.tiles.mapbox.com/v4/openstreetmap.map-inh7ifmo/{zoom}/{x}/{y}.png?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcCIsImEiOiJncjlmd0t3In0.DmZsIeOW-3x-C5eX-wAqTw" - - } - - ], - "filters": [ - { - "name": "Surface transport", - "filter": "boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:" - }, - { - "name": "Surface transport", - "filter": "motorway | trunk | primary | secondary | tertiary | _link | new" - } - ], - "mapcss": [ - { - "name": "Recent changes (2015)", - "description": "Highlights features that were created/modified in 2015 year", - "url": "https://github.com/Andygol/josm-styles/raw/master/recent%20changes_2015.mapcss" - }, - { - "name": "Recent changes (2016)", - "description": "Highlights features that were created/modified in 2016 year", - "url": "https://github.com/Andygol/josm-styles/raw/master/recent%20changes_2016.mapcss" - }, - { - "name": "Lane attributes", - "description": "Lane and Road attributes", - "url": "https://josm.openstreetmap.de/josmfile?page=Styles/Lane_and_Road_Attributes&zip=1" - } - ], - "presets": [ - { - "name": "Lane attributes", - "description": "Lane and Road attributes", - "url": "https://josm.openstreetmap.de/josmfile?page=Presets/LaneAttributes&zip=1" - } - ], - "plugins": [ - { - "name": "turnlanes" - } - ], - "contact_name": "Arun", - "contact_email": "arun@mapbox.com" - }, - "tags": [ - { - "key": "turn:lanes" - } - ] -} diff --git a/Studio/styles/osmlint-dark.json b/Studio/styles/osmlint-dark.json deleted file mode 100644 index 20dae65..0000000 --- a/Studio/styles/osmlint-dark.json +++ /dev/null @@ -1,4150 +0,0 @@ -{ - "version": 8, - "name": "osmlint", - "metadata": { - "mapbox:groups": { - "1444855829844.9736": { - "name": "Aeroways", - "collapsed": true - }, - "1444855878987.3848": { - "name": "Landuses", - "collapsed": true - }, - "1452665161948.7004": { - "name": "osmlint", - "collapsed": true - }, - "1444855808224.0002": { - "name": "Bridges", - "collapsed": true - }, - "1444855728283.4546": { - "name": "Place labels", - "collapsed": true - }, - "1444855743302.092": { - "name": "POI labels", - "collapsed": true - }, - "1444855823615.3472": { - "name": "Tunnels", - "collapsed": true - }, - "1444855712732.9983": { - "name": "State labels", - "collapsed": true - }, - "1444855871001.7312": { - "name": "Hillshades", - "collapsed": true - }, - "1444855787203.2078": { - "name": "Waterway labels", - "collapsed": true - }, - "1444855767413.334": { - "name": "Road labels", - "collapsed": true - }, - "1444855862406.4956": { - "name": "Buildings", - "collapsed": true - }, - "1444855720231.1272": { - "name": "Marine labels", - "collapsed": true - }, - "1444855816509.7878": { - "name": "Roads", - "collapsed": true - }, - "1444855707128.6584": { - "name": "Country labels", - "collapsed": true - }, - "1444855886145.2253": { - "name": "Landcovers", - "collapsed": true - }, - "1444855797854.0842": { - "name": "Admin boundaries", - "collapsed": true - }, - "1444855733376.9668": { - "name": "Water labels", - "collapsed": true - }, - "1452667653414.454": { - "name": "osmlint labels" - }, - "1444855857485.0151": { - "name": "Water", - "collapsed": true - } - }, - "mapbox:trackposition": false - }, - "center": [ - 119.9179912104388, - 12.671610571557252 - ], - "zoom": 5, - "bearing": 0, - "pitch": 0, - "sources": { - "mapbox": { - "url": "mapbox://mapbox.mapbox-streets-v6", - "type": "vector" - }, - "mapbox://mapbox.mapbox-terrain-v2": { - "url": "mapbox://mapbox.mapbox-terrain-v2", - "type": "vector" - }, - "mapbox://planemad.3f1b8ov4": { - "url": "mapbox://planemad.3f1b8ov4", - "type": "vector" - } - }, - "sprite": "mapbox://sprites/planemad/cijcefp3q00elbskq4cgvcivf", - "glyphs": "mapbox://fonts/planemad/{fontstack}/{range}.pbf", - "layers": [ - { - "id": "background", - "type": "background", - "paint": { - "background-color": "#111" - }, - "interactive": true - }, - { - "id": "landcover_snow", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "landcover", - "filter": [ - "==", - "class", - "snow" - ], - "paint": { - "fill-color": "#000", - "fill-opacity": 0.5 - }, - "metadata": { - "mapbox:group": "1444855886145.2253" - }, - "interactive": true - }, - { - "id": "landcover_crop", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "landcover", - "filter": [ - "==", - "class", - "crop" - ], - "paint": { - "fill-color": "#131313", - "fill-opacity": 0.5 - }, - "metadata": { - "mapbox:group": "1444855886145.2253" - }, - "interactive": true - }, - { - "id": "landcover_grass", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "landcover", - "filter": [ - "==", - "class", - "grass" - ], - "paint": { - "fill-color": "#1a1a1a", - "fill-opacity": 0.5 - }, - "metadata": { - "mapbox:group": "1444855886145.2253" - }, - "interactive": true - }, - { - "id": "landcover_scrub", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "landcover", - "filter": [ - "==", - "class", - "scrub" - ], - "paint": { - "fill-color": "#1c1c1c", - "fill-opacity": 0.5 - }, - "metadata": { - "mapbox:group": "1444855886145.2253" - }, - "interactive": true - }, - { - "id": "landcover_wood", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "landcover", - "filter": [ - "==", - "class", - "wood" - ], - "paint": { - "fill-color": "#232323", - "fill-opacity": 0.5 - }, - "metadata": { - "mapbox:group": "1444855886145.2253" - }, - "interactive": true - }, - { - "id": "landuse_industrial", - "type": "fill", - "source": "mapbox", - "source-layer": "landuse", - "filter": [ - "all", - [ - "==", - "$type", - "Polygon" - ], - [ - "==", - "class", - "industrial" - ] - ], - "paint": { - "fill-color": "#000", - "fill-opacity": 0.5 - }, - "metadata": { - "mapbox:group": "1444855878987.3848" - }, - "interactive": true - }, - { - "id": "landuse_park", - "type": "fill", - "source": "mapbox", - "source-layer": "landuse", - "filter": [ - "==", - "class", - "park" - ], - "paint": { - "fill-color": "#1b1b1b" - }, - "metadata": { - "mapbox:group": "1444855878987.3848" - }, - "interactive": true - }, - { - "id": "landuse_wood", - "type": "fill", - "source": "mapbox", - "source-layer": "landuse", - "filter": [ - "==", - "class", - "wood" - ], - "paint": { - "fill-color": "#1f1f1f" - }, - "metadata": { - "mapbox:group": "1444855878987.3848" - }, - "interactive": true - }, - { - "id": "hillshade_highlight_bright", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "hillshade", - "filter": [ - "==", - "level", - 94 - ], - "paint": { - "fill-color": "#000", - "fill-opacity": { - "base": 1, - "stops": [ - [ - 15, - 0.15 - ], - [ - 17, - 0.05 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855871001.7312" - }, - "interactive": true - }, - { - "id": "hillshade_highlight_med", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "hillshade", - "filter": [ - "==", - "level", - 90 - ], - "paint": { - "fill-color": "#000", - "fill-opacity": { - "base": 1, - "stops": [ - [ - 15, - 0.15 - ], - [ - 17, - 0.05 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855871001.7312" - }, - "interactive": true - }, - { - "id": "hillshade_shadow_faint", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "hillshade", - "filter": [ - "==", - "level", - 89 - ], - "paint": { - "fill-color": "#999999", - "fill-opacity": { - "base": 1, - "stops": [ - [ - 14, - 0.06 - ], - [ - 17, - 0.01 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855871001.7312" - }, - "interactive": true - }, - { - "id": "hillshade_shadow_med", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "hillshade", - "filter": [ - "==", - "level", - 78 - ], - "paint": { - "fill-color": "#999999", - "fill-opacity": { - "base": 1, - "stops": [ - [ - 14, - 0.06 - ], - [ - 17, - 0.01 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855871001.7312" - }, - "interactive": true - }, - { - "id": "hillshade_shadow_dark", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "hillshade", - "filter": [ - "==", - "level", - 67 - ], - "paint": { - "fill-color": "#888888", - "fill-opacity": { - "base": 1, - "stops": [ - [ - 14, - 0.06 - ], - [ - 17, - 0.01 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855871001.7312" - }, - "interactive": true - }, - { - "id": "hillshade_shadow_extreme", - "type": "fill", - "source": "mapbox://mapbox.mapbox-terrain-v2", - "source-layer": "hillshade", - "filter": [ - "==", - "level", - 56 - ], - "paint": { - "fill-color": "#999", - "fill-opacity": { - "base": 1, - "stops": [ - [ - 14, - 0.06 - ], - [ - 17, - 0.01 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855871001.7312" - }, - "interactive": true - }, - { - "id": "building", - "type": "fill", - "source": "mapbox", - "source-layer": "building", - "minzoom": 15, - "paint": { - "fill-outline-color": "#444444", - "fill-opacity": { - "base": 1, - "stops": [ - [ - 15, - 0 - ], - [ - 16.5, - 1 - ] - ] - }, - "fill-antialias": true, - "fill-color": "#383838" - }, - "metadata": { - "mapbox:group": "1444855862406.4956" - }, - "interactive": true - }, - { - "id": "waterway", - "type": "line", - "source": "mapbox", - "source-layer": "waterway", - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "in", - "class", - "river", - "canal" - ] - ], - "paint": { - "line-color": "#2c2c2c", - "line-width": { - "base": 1, - "stops": [ - [ - 6, - 0.25 - ], - [ - 20, - 6 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855857485.0151" - }, - "interactive": true - }, - { - "id": "waterway_stream", - "type": "line", - "source": "mapbox", - "source-layer": "waterway", - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "class", - "stream" - ] - ], - "paint": { - "line-color": "#2c2c2c", - "line-width": { - "base": 1, - "stops": [ - [ - 13, - 0.75 - ], - [ - 20, - 4 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855857485.0151" - }, - "interactive": true - }, - { - "id": "water", - "type": "fill", - "source": "mapbox", - "source-layer": "water", - "paint": { - "fill-color": "#2c2c2c" - }, - "metadata": { - "mapbox:group": "1444855857485.0151" - }, - "interactive": true - }, - { - "interactive": true, - "layout": { - "line-join": "miter", - "visibility": "visible" - }, - "metadata": { - "mapbox:group": "1444855829844.9736" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "type", - "runway" - ] - ], - "type": "line", - "source": "mapbox", - "id": "aeroway_runway", - "paint": { - "line-width": { - "base": 1.15, - "stops": [ - [ - 11, - 3 - ], - [ - 20, - 32 - ] - ] - }, - "line-color": "#000", - "line-opacity": { - "base": 1, - "stops": [ - [ - 9, - 0.5 - ], - [ - 11, - 1 - ] - ] - } - }, - "source-layer": "aeroway" - }, - { - "interactive": true, - "layout": { - "line-join": "miter" - }, - "metadata": { - "mapbox:group": "1444855829844.9736" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "type", - "taxiway" - ] - ], - "type": "line", - "source": "mapbox", - "id": "aeroway_taxiway", - "paint": { - "line-width": { - "base": 1.15, - "stops": [ - [ - 10, - 0.25 - ], - [ - 11, - 1 - ], - [ - 20, - 8 - ] - ] - }, - "line-color": "#3c3c3c" - }, - "source-layer": "aeroway" - }, - { - "id": "tunnel_minor", - "type": "line", - "source": "mapbox", - "source-layer": "tunnel", - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "in", - "class", - "motorway_link", - "street", - "street_limited", - "service", - "driveway", - "path" - ] - ], - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.55, - "stops": [ - [ - 4, - 0.25 - ], - [ - 20, - 20 - ] - ] - }, - "line-dasharray": [ - 0.36, - 0.18 - ] - }, - "metadata": { - "mapbox:group": "1444855823615.3472" - }, - "interactive": true - }, - { - "id": "tunnel_major", - "type": "line", - "source": "mapbox", - "source-layer": "tunnel", - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "in", - "class", - "motorway", - "main" - ] - ], - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.4, - "stops": [ - [ - 6, - 0.5 - ], - [ - 20, - 30 - ] - ] - }, - "line-dasharray": [ - 0.28, - 0.14 - ] - }, - "metadata": { - "mapbox:group": "1444855823615.3472" - }, - "interactive": true - }, - { - "id": "road-path", - "type": "line", - "source": "mapbox", - "source-layer": "road", - "filter": [ - "==", - "class", - "path" - ], - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1, - "stops": [ - [ - 15, - 1 - ], - [ - 18, - 4 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "interactive": true - }, - { - "interactive": true, - "minzoom": 11, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "maxzoom": 14.1, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "in", - "class", - "street", - "street_limited" - ] - ], - "type": "line", - "source": "mapbox", - "id": "road-street-low-zoom", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 12.5, - 0.5 - ], - [ - 14, - 2 - ], - [ - 18, - 18 - ] - ] - }, - "line-opacity": { - "base": 1, - "stops": [ - [ - 11.5, - 0 - ], - [ - 12, - 1 - ] - ] - } - }, - "source-layer": "road" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "in", - "class", - "service", - "driveway" - ], - "type": "line", - "source": "mapbox", - "id": "road-service-driveway", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1, - "stops": [ - [ - 14, - 0.5 - ], - [ - 18, - 12 - ] - ] - } - }, - "source-layer": "road" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "==", - "class", - "motorway_link" - ], - "type": "line", - "source": "mapbox", - "id": "road-motorway_link", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 12.5, - 0.5 - ], - [ - 14, - 2 - ], - [ - 18, - 18 - ] - ] - } - }, - "source-layer": "road" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "class", - "street_limited" - ] - ], - "type": "line", - "source": "mapbox", - "id": "road-street_limited", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 12.5, - 0.5 - ], - [ - 14, - 2 - ], - [ - 18, - 18 - ] - ] - } - }, - "source-layer": "road" - }, - { - "interactive": true, - "minzoom": 14, - "layout": { - "line-cap": "round", - "line-join": "round", - "visibility": "visible" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "class", - "street" - ] - ], - "type": "line", - "source": "mapbox", - "id": "road-street", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 12.5, - 0.3 - ], - [ - 14, - 2 - ], - [ - 18, - 18 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "road" - }, - { - "interactive": true, - "layout": { - "line-cap": "round", - "line-join": "round", - "visibility": "visible" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "class", - "main" - ] - ], - "type": "line", - "source": "mapbox", - "id": "road-main", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 6, - 0.5 - ], - [ - 18, - 26 - ] - ] - }, - "line-opacity": { - "base": 1, - "stops": [ - [ - 5, - 0 - ], - [ - 5.5, - 1 - ] - ] - } - }, - "source-layer": "road" - }, - { - "interactive": true, - "layout": { - "line-cap": "round", - "line-join": "round", - "visibility": "visible" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "all", - [ - "==", - "class", - "main" - ], - [ - "==", - "type", - "trunk" - ] - ], - "type": "line", - "source": "mapbox", - "id": "road-trunk", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 5, - 0.75 - ], - [ - 18, - 32 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "road" - }, - { - "interactive": true, - "layout": { - "line-cap": "round", - "line-join": "round", - "visibility": "visible" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "==", - "class", - "motorway" - ], - "type": "line", - "source": "mapbox", - "id": "road-motorway", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 5, - 0.75 - ], - [ - 18, - 32 - ] - ] - }, - "line-opacity": { - "base": 1, - "stops": [ - [ - 5, - 0 - ], - [ - 5.5, - 1 - ] - ] - } - }, - "source-layer": "road" - }, - { - "interactive": true, - "minzoom": 13, - "layout": { - "line-cap": "round", - "line-join": "round", - "visibility": "visible" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "in", - "class", - "major_rail", - "minor_rail" - ], - "type": "line", - "source": "mapbox", - "id": "road-rail", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 14, - 0.5 - ], - [ - 20, - 1 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "road" - }, - { - "interactive": true, - "minzoom": 13, - "layout": { - "line-cap": "butt", - "line-join": "miter", - "visibility": "visible" - }, - "metadata": { - "mapbox:group": "1444855816509.7878" - }, - "filter": [ - "in", - "class", - "major_rail", - "minor_rail" - ], - "type": "line", - "source": "mapbox", - "id": "road-rail-tracks", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 14, - 4 - ], - [ - 20, - 8 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "road" - }, - { - "id": "bridge_minor_case", - "type": "line", - "source": "mapbox", - "source-layer": "bridge", - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "in", - "class", - "motorway_link", - "street", - "street_limited", - "service", - "driveway", - "path" - ] - ], - "paint": { - "line-color": "#111", - "line-width": { - "base": 1.6, - "stops": [ - [ - 12, - 0.5 - ], - [ - 20, - 10 - ] - ] - }, - "line-gap-width": { - "base": 1.55, - "stops": [ - [ - 4, - 0.25 - ], - [ - 20, - 20 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "interactive": true - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "==", - "class", - "path" - ], - "type": "line", - "source": "mapbox", - "id": "bridge-path", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 15, - 1 - ], - [ - 18, - 4 - ] - ] - } - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "minzoom": 11, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "maxzoom": 14.1, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "in", - "class", - "street", - "street_limited" - ] - ], - "type": "line", - "source": "mapbox", - "id": "bridge-street-low-zoom", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 12.5, - 0.5 - ], - [ - 14, - 2 - ], - [ - 18, - 18 - ] - ] - }, - "line-opacity": { - "base": 1, - "stops": [ - [ - 11.5, - 0 - ], - [ - 12, - 1 - ] - ] - } - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "minzoom": 10, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "class", - "motorway_link" - ] - ], - "type": "line", - "source": "mapbox", - "id": "bridge-motorway_link", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 12.5, - 0.5 - ], - [ - 14, - 2 - ], - [ - 18, - 18 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "minzoom": 14, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "class", - "street_limited" - ] - ], - "type": "line", - "source": "mapbox", - "id": "bridge-street_limited", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 12.5, - 0.5 - ], - [ - 14, - 2 - ], - [ - 18, - 18 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "minzoom": 14, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "==", - "class", - "street" - ], - "type": "line", - "source": "mapbox", - "id": "bridge-street", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 12.5, - 0.5 - ], - [ - 14, - 2 - ], - [ - 18, - 18 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "all", - [ - "==", - "class", - "main" - ], - [ - "!=", - "type", - "trunk" - ] - ], - "type": "line", - "source": "mapbox", - "id": "bridge-main", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 6, - 0.5 - ], - [ - 18, - 26 - ] - ] - }, - "line-opacity": { - "base": 1, - "stops": [ - [ - 5, - 0 - ], - [ - 5.5, - 1 - ] - ] - } - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "all", - [ - "==", - "class", - "main" - ], - [ - "==", - "type", - "trunk" - ] - ], - "type": "line", - "source": "mapbox", - "id": "bridge-trunk", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1, - "stops": [ - [ - 3, - 0.5 - ], - [ - 9, - 1.25 - ], - [ - 20, - 10 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-cap": "round", - "line-join": "round" - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "==", - "class", - "motorway" - ], - "type": "line", - "source": "mapbox", - "id": "bridge-motorway", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1, - "stops": [ - [ - 3, - 0.5 - ], - [ - 9, - 1.25 - ], - [ - 20, - 10 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "minzoom": 13, - "layout": { - "visibility": "visible", - "line-cap": "butt", - "line-join": "miter", - "line-round-limit": 2 - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "in", - "class", - "major_rail", - "minor_rail" - ], - "type": "line", - "source": "mapbox", - "id": "bridge-rail", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 14, - 0.5 - ], - [ - 20, - 1 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "minzoom": 14, - "layout": { - "visibility": "visible", - "line-cap": "butt", - "line-join": "miter", - "line-round-limit": 2 - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "in", - "class", - "major_rail", - "minor_rail" - ], - "type": "line", - "source": "mapbox", - "id": "bridge-rail-tracks", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 14, - 4 - ], - [ - 20, - 8 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "minzoom": 14, - "layout": { - "visibility": "visible", - "line-cap": "butt", - "line-join": "miter", - "line-round-limit": 2 - }, - "metadata": { - "mapbox:group": "1444855808224.0002" - }, - "filter": [ - "==", - "class", - "aerialway" - ], - "type": "line", - "source": "mapbox", - "id": "bridge-rail-tracks_copy", - "paint": { - "line-color": "#484848", - "line-width": { - "base": 1.5, - "stops": [ - [ - 14, - 0.5 - ], - [ - 20, - 1 - ] - ] - }, - "line-opacity": 1 - }, - "source-layer": "bridge" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-join": "bevel" - }, - "metadata": { - "mapbox:group": "1444855797854.0842" - }, - "filter": [ - "all", - [ - ">=", - "admin_level", - 3 - ], - [ - "==", - "maritime", - 0 - ] - ], - "type": "line", - "source": "mapbox", - "id": "admin-3-4-boundaries-bg", - "paint": { - "line-width": { - "base": 1, - "stops": [ - [ - 3, - 3.5 - ], - [ - 12, - 6 - ] - ] - }, - "line-opacity": { - "base": 1, - "stops": [ - [ - 2, - 0 - ], - [ - 5, - 0.75 - ] - ] - }, - "line-color": "#000" - }, - "source-layer": "admin" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-join": "miter" - }, - "metadata": { - "mapbox:group": "1444855797854.0842" - }, - "filter": [ - "all", - [ - "==", - "admin_level", - 2 - ], - [ - "==", - "maritime", - 0 - ], - [ - "==", - "disputed", - 2 - ] - ], - "type": "line", - "source": "mapbox", - "id": "admin-2-boundaries-bg", - "paint": { - "line-color": "#000000", - "line-opacity": { - "base": 1, - "stops": [ - [ - 3, - 0 - ], - [ - 4, - 0.75 - ] - ] - }, - "line-width": { - "base": 1, - "stops": [ - [ - 2, - 3.5 - ], - [ - 10, - 10 - ] - ] - } - }, - "source-layer": "admin" - }, - { - "interactive": true, - "layout": { - "visibility": "visible", - "line-join": "miter" - }, - "metadata": { - "mapbox:group": "1444855797854.0842" - }, - "filter": [ - "all", - [ - ">=", - "admin_level", - 3 - ], - [ - "==", - "maritime", - 0 - ] - ], - "type": "line", - "source": "mapbox", - "id": "admin-3-4-boundaries", - "paint": { - "line-color": "#797979", - "line-opacity": { - "base": 1, - "stops": [ - [ - 2, - 0 - ], - [ - 3, - 1 - ] - ] - }, - "line-width": { - "base": 1, - "stops": [ - [ - 3, - 0.5 - ], - [ - 12, - 2 - ] - ] - }, - "line-dasharray": { - "base": 1, - "stops": [ - [ - 4, - [ - 2, - 0 - ] - ], - [ - 5, - [ - 2, - 2, - 6, - 2 - ] - ] - ] - } - }, - "source-layer": "admin" - }, - { - "interactive": true, - "minzoom": 1, - "layout": { - "visibility": "visible", - "line-join": "round", - "line-cap": "round" - }, - "metadata": { - "mapbox:group": "1444855797854.0842" - }, - "filter": [ - "all", - [ - "==", - "admin_level", - 2 - ], - [ - "==", - "maritime", - 0 - ], - [ - "==", - "disputed", - 0 - ] - ], - "type": "line", - "source": "mapbox", - "id": "admin-2-boundaries", - "paint": { - "line-color": "#5f5f5f", - "line-opacity": 1, - "line-width": { - "base": 1, - "stops": [ - [ - 3, - 0.5 - ], - [ - 10, - 2 - ] - ] - } - }, - "source-layer": "admin" - }, - { - "interactive": true, - "minzoom": 12, - "layout": { - "text-font": [ - "DIN Offc Pro Italic", - "Arial Unicode MS Regular" - ], - "visibility": "visible", - "symbol-placement": "line", - "text-field": "{name_en}", - "text-size": { - "base": 1, - "stops": [ - [ - 13, - 12 - ], - [ - 18, - 16 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855787203.2078" - }, - "filter": [ - "==", - "class", - "river" - ], - "type": "symbol", - "source": "mapbox", - "id": "waterway-label", - "paint": { - "text-color": "#929292" - }, - "source-layer": "waterway_label" - }, - { - "interactive": true, - "minzoom": 12, - "layout": { - "symbol-placement": "line", - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Bold" - ], - "text-transform": "none", - "text-letter-spacing": 0, - "text-padding": 0, - "text-size": { - "base": 1, - "stops": [ - [ - 8, - 8 - ], - [ - 20, - 15 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855767413.334" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "!in", - "class", - "motorway", - "main", - "street_limited", - "street" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "road-label-sm", - "paint": { - "text-halo-color": "#000", - "text-halo-width": 2, - "text-color": "#929292" - }, - "source-layer": "road_label" - }, - { - "interactive": true, - "layout": { - "symbol-placement": "line", - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Bold" - ], - "text-transform": "none", - "text-letter-spacing": 0, - "text-padding": 0, - "text-size": { - "base": 1, - "stops": [ - [ - 8, - 8 - ], - [ - 20, - 16 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855767413.334" - }, - "filter": [ - "in", - "class", - "street", - "street_limited" - ], - "type": "symbol", - "source": "mapbox", - "id": "road-label-med", - "paint": { - "text-halo-color": "#000", - "text-halo-width": 2, - "text-color": "#929292" - }, - "source-layer": "road_label" - }, - { - "interactive": true, - "layout": { - "symbol-placement": "line", - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Bold" - ], - "text-transform": "none", - "text-letter-spacing": 0, - "text-padding": 0, - "text-size": { - "base": 1, - "stops": [ - [ - 8, - 8 - ], - [ - 20, - 17 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855767413.334" - }, - "filter": [ - "in", - "class", - "motorway", - "main" - ], - "type": "symbol", - "source": "mapbox", - "id": "road-label-large", - "paint": { - "text-halo-color": "#000", - "text-halo-width": 2, - "text-color": "#929292" - }, - "source-layer": "road_label" - }, - { - "interactive": true, - "layout": { - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "visibility": "visible", - "text-field": { - "base": 1, - "stops": [ - [ - 10, - "{name_en}" - ], - [ - 13, - "" - ] - ] - }, - "text-max-width": 9, - "text-size": { - "base": 1, - "stops": [ - [ - 10, - 10 - ], - [ - 18, - 18 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855743302.092" - }, - "filter": [ - "all", - [ - "in", - "maki", - "airport", - "heliport", - "rocket" - ], - [ - "<=", - "scalerank", - 2 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "airport-label", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1, - "text-halo-blur": 0 - }, - "source-layer": "poi_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 8, - "visibility": "visible", - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Regular", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 10, - 10 - ], - [ - 18, - 14 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855743302.092" - }, - "filter": [ - "all", - [ - "==", - "scalerank", - 1 - ], - [ - "==", - "maki", - "park" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "poi-parks-scalerank1", - "paint": { - "text-color": "#c2c2c2", - "text-halo-color": "#000", - "text-halo-width": 1 - }, - "source-layer": "poi_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 8, - "visibility": "visible", - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Regular", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 10, - 10 - ], - [ - 18, - 14 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855743302.092" - }, - "filter": [ - "all", - [ - "!in", - "maki", - "rail-light", - "rail-metro", - "rail", - "airport", - "airfield", - "heliport", - "rocket", - "park", - "golf", - "cemetary", - "zoo", - "campsite", - "swimming", - "dog-park" - ], - [ - "<=", - "scalerank", - 1 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "poi-scalerank1", - "paint": { - "text-color": "#b7b8b7", - "text-halo-color": "#000", - "text-halo-width": 1 - }, - "source-layer": "poi_label" - }, - { - "interactive": true, - "minzoom": 5, - "layout": { - "text-font": [ - "DIN Offc Pro Italic", - "Arial Unicode MS Regular" - ], - "visibility": "visible", - "text-field": "{name_en}", - "text-max-width": 7, - "text-size": { - "base": 1, - "stops": [ - [ - 13, - 12 - ], - [ - 18, - 16 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855733376.9668" - }, - "type": "symbol", - "source": "mapbox", - "id": "water-label", - "paint": { - "text-color": { - "base": 1, - "stops": [ - [ - 0, - "#969696" - ], - [ - 20, - "#969696" - ] - ] - } - }, - "source-layer": "water_label" - }, - { - "layout": { - "line-join": "round", - "visibility": "visible" - }, - "metadata": { - "mapbox:group": "1452665161948.7004" - }, - "type": "line", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint line", - "paint": { - "line-color": "rgba(255,255,255,1)", - "line-width": 1 - }, - "source-layer": "osmlint", - "interactive": true - }, - { - "layout": {}, - "metadata": { - "mapbox:group": "1452665161948.7004" - }, - "filter": [ - "==", - "_osmlint", - "unclosedWays" - ], - "type": "fill", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint fill", - "paint": { - "fill-color": "rgba(255,255,255,1)", - "fill-opacity": 0.3 - }, - "source-layer": "osmlint", - "interactive": true - }, - { - "layout": {}, - "metadata": { - "mapbox:group": "1452665161948.7004" - }, - "filter": [ - "all", - [ - "in", - "$type", - "Polygon", - "Point", - "LineString" - ], - [ - "==", - "_osmlint", - "selfintersecting" - ] - ], - "type": "circle", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint circle selfintersecting", - "paint": { - "circle-color": "rgba(199,38,38,1)", - "circle-blur": 1, - "circle-radius": 7 - }, - "source-layer": "osmlint", - "interactive": true - }, - { - "layout": {}, - "metadata": { - "mapbox:group": "1452665161948.7004" - }, - "filter": [ - "all", - [ - "in", - "$type", - "Polygon", - "Point", - "LineString" - ], - [ - "==", - "_osmlint", - "bridgeonnode" - ] - ], - "type": "circle", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint circle bridgeonnode", - "paint": { - "circle-color": "rgba(169,189,79,1)", - "circle-blur": 1, - "circle-radius": 7 - }, - "source-layer": "osmlint", - "interactive": true - }, - { - "layout": {}, - "metadata": { - "mapbox:group": "1452665161948.7004" - }, - "filter": [ - "all", - [ - "in", - "$type", - "Polygon", - "Point", - "LineString" - ], - [ - "==", - "_osmlint", - "unclosedWays" - ] - ], - "type": "circle", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint circle unclosed", - "paint": { - "circle-color": "rgba(38,180,199,1)", - "circle-blur": 1, - "circle-radius": 7 - }, - "source-layer": "osmlint", - "interactive": true - }, - { - "layout": {}, - "metadata": { - "mapbox:group": "1452665161948.7004" - }, - "filter": [ - "in", - "$type", - "Polygon", - "Point", - "LineString" - ], - "type": "circle", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint circle", - "paint": { - "circle-color": "rgba(255,255,255,1)", - "circle-radius": 2, - "circle-opacity": 0.9 - }, - "source-layer": "osmlint", - "interactive": true - }, - { - "interactive": true, - "minzoom": 12, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Bold", - "Arial Unicode MS Bold" - ], - "text-max-width": 7, - "text-letter-spacing": 0.1, - "text-transform": "uppercase", - "text-size": { - "stops": [ - [ - 12, - 10 - ], - [ - 16, - 14 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855728283.4546" - }, - "filter": [ - "all", - [ - "==", - "$type", - "Point" - ], - [ - "in", - "type", - "suburb", - "neighbourhood" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "place_label_neighborhood", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1, - "text-halo-blur": 1, - "text-opacity": { - "base": 1, - "stops": [ - [ - 0, - 0 - ], - [ - 12, - 0.66 - ], - [ - 13, - 1 - ] - ] - } - }, - "source-layer": "place_label" - }, - { - "interactive": true, - "minzoom": 8, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Bold" - ], - "text-max-width": 15, - "text-size": { - "stops": [ - [ - 6, - 10 - ], - [ - 12, - 13 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855728283.4546" - }, - "filter": [ - "all", - [ - "==", - "$type", - "Point" - ], - [ - "in", - "type", - "town", - "village", - "hamlet" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "place_label_other", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1, - "text-halo-blur": 1, - "text-opacity": 0.7 - }, - "source-layer": "place_label" - }, - { - "interactive": true, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Bold" - ], - "text-max-width": 10, - "text-anchor": { - "base": 1, - "stops": [ - [ - 0, - "top" - ], - [ - 6, - "center" - ] - ] - }, - "text-offset": { - "base": 1, - "stops": [ - [ - 0, - [ - 0, - 0.1 - ] - ], - [ - 6, - [ - 0, - 0 - ] - ] - ] - }, - "text-size": { - "stops": [ - [ - 6, - 11 - ], - [ - 14, - 19 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855728283.4546" - }, - "maxzoom": 16, - "filter": [ - "all", - [ - "==", - "type", - "city" - ], - [ - ">", - "scalerank", - 4 - ], - [ - "in", - "ldir", - "S", - "E", - "SE", - "SW" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "place_label_city_small_s", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1.5, - "text-halo-blur": 0, - "text-opacity": 0.7 - }, - "source-layer": "place_label" - }, - { - "interactive": true, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Bold" - ], - "text-max-width": 10, - "text-anchor": { - "base": 1, - "stops": [ - [ - 0, - "bottom" - ], - [ - 6, - "center" - ] - ] - }, - "text-offset": { - "base": 1, - "stops": [ - [ - 0, - [ - 0, - -0.2 - ] - ], - [ - 6, - [ - 0, - 0 - ] - ] - ] - }, - "text-size": { - "stops": [ - [ - 6, - 11 - ], - [ - 14, - 19 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855728283.4546" - }, - "maxzoom": 16, - "filter": [ - "all", - [ - "==", - "type", - "city" - ], - [ - ">", - "scalerank", - 4 - ], - [ - "in", - "ldir", - "N", - "W", - "NW", - "NE" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "place_label_city_small_n", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1.5, - "text-halo-blur": 0, - "text-opacity": 0.7 - }, - "source-layer": "place_label" - }, - { - "interactive": true, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Bold" - ], - "text-max-width": 10, - "text-anchor": { - "base": 1, - "stops": [ - [ - 0, - "top" - ], - [ - 6, - "center" - ] - ] - }, - "text-offset": { - "base": 1, - "stops": [ - [ - 0, - [ - 0, - 0.1 - ] - ], - [ - 6, - [ - 0, - 0 - ] - ] - ] - }, - "text-size": { - "stops": [ - [ - 5, - 11 - ], - [ - 12, - 19 - ] - ], - "base": 0.9 - } - }, - "metadata": { - "mapbox:group": "1444855728283.4546" - }, - "maxzoom": 16, - "filter": [ - "all", - [ - "==", - "type", - "city" - ], - [ - "<=", - "scalerank", - 4 - ], - [ - ">", - "scalerank", - 1 - ], - [ - "in", - "ldir", - "S", - "E", - "SE", - "SW" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "place_label_city_medium_s", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1.5, - "text-halo-blur": 0, - "text-opacity": 0.7 - }, - "source-layer": "place_label" - }, - { - "interactive": true, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Bold" - ], - "text-max-width": 10, - "text-anchor": { - "base": 1, - "stops": [ - [ - 0, - "bottom" - ], - [ - 6, - "center" - ] - ] - }, - "text-offset": { - "base": 1, - "stops": [ - [ - 0, - [ - 0, - -0.2 - ] - ], - [ - 6, - [ - 0, - 0 - ] - ] - ] - }, - "text-size": { - "stops": [ - [ - 5, - 11 - ], - [ - 12, - 19 - ] - ], - "base": 0.9 - } - }, - "metadata": { - "mapbox:group": "1444855728283.4546" - }, - "maxzoom": 16, - "filter": [ - "all", - [ - "==", - "type", - "city" - ], - [ - "<=", - "scalerank", - 4 - ], - [ - ">", - "scalerank", - 1 - ], - [ - "in", - "ldir", - "N", - "W", - "NW", - "NE" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "place_label_city_medium_n", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1.5, - "text-halo-blur": 0, - "text-opacity": 0.7 - }, - "source-layer": "place_label" - }, - { - "interactive": true, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Bold", - "Arial Unicode MS Bold" - ], - "text-max-width": 15, - "text-transform": "none", - "text-anchor": { - "base": 1, - "stops": [ - [ - 0, - "top" - ], - [ - 6, - "center" - ] - ] - }, - "text-offset": { - "base": 1, - "stops": [ - [ - 0, - [ - 0, - 0.1 - ] - ], - [ - 6, - [ - 0, - 0 - ] - ] - ] - }, - "text-size": { - "stops": [ - [ - 4, - 11 - ], - [ - 10, - 20 - ] - ], - "base": 0.9 - } - }, - "metadata": { - "mapbox:group": "1444855728283.4546" - }, - "maxzoom": 16, - "filter": [ - "all", - [ - "==", - "type", - "city" - ], - [ - "<=", - "scalerank", - 1 - ], - [ - "in", - "ldir", - "S", - "SE", - "SW", - "E" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "place_label_city_large_s", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1.5, - "text-halo-blur": 0, - "text-opacity": 0.7 - }, - "source-layer": "place_label" - }, - { - "interactive": true, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Bold", - "Arial Unicode MS Bold" - ], - "text-max-width": 5, - "text-transform": "none", - "text-anchor": { - "base": 1, - "stops": [ - [ - 0, - "bottom" - ], - [ - 6, - "center" - ] - ] - }, - "text-offset": { - "base": 1, - "stops": [ - [ - 0, - [ - 0, - -0.2 - ] - ], - [ - 6, - [ - 0, - 0 - ] - ] - ] - }, - "symbol-avoid-edges": false, - "text-size": { - "stops": [ - [ - 4, - 11 - ], - [ - 10, - 20 - ] - ], - "base": 0.9 - } - }, - "metadata": { - "mapbox:group": "1444855728283.4546" - }, - "maxzoom": 16, - "filter": [ - "all", - [ - "<=", - "scalerank", - 1 - ], - [ - "in", - "ldir", - "N", - "NE", - "NW", - "W" - ], - [ - "==", - "type", - "city" - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "place_label_city_large_n", - "paint": { - "text-color": "#999999", - "text-halo-color": "#000", - "text-halo-width": 1.5, - "text-halo-blur": 0, - "text-opacity": 0.7 - }, - "source-layer": "place_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 8, - "visibility": "none", - "symbol-placement": "point", - "text-field": "{name_en}", - "text-line-height": 1.2, - "text-letter-spacing": 0.1, - "text-font": [ - "DIN Offc Pro Regular", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 4, - 12 - ], - [ - 6, - 16 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855720231.1272" - }, - "filter": [ - "all", - [ - "==", - "$type", - "Point" - ], - [ - "in", - "labelrank", - 4, - 5, - 6 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "marine_label_point_other", - "paint": { - "text-color": "#999999" - }, - "source-layer": "marine_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 8, - "visibility": "visible", - "symbol-placement": "point", - "text-field": "{name_en}", - "text-line-height": 1.3, - "text-letter-spacing": 0.1, - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 3, - 13 - ], - [ - 5, - 18 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855720231.1272" - }, - "filter": [ - "all", - [ - "==", - "$type", - "Point" - ], - [ - "==", - "labelrank", - 3 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "marine_label_point_3", - "paint": { - "text-color": "#999999", - "text-opacity": 0.25 - }, - "source-layer": "marine_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 8, - "visibility": "visible", - "symbol-placement": "point", - "text-field": "{name_en}", - "text-line-height": 1.2, - "text-letter-spacing": 0, - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 3, - 14 - ], - [ - 5, - 24 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855720231.1272" - }, - "filter": [ - "all", - [ - "==", - "$type", - "Point" - ], - [ - "==", - "labelrank", - 2 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "marine_label_point_2", - "paint": { - "text-color": "#999999", - "text-opacity": 0.25 - }, - "source-layer": "marine_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 4, - "visibility": "visible", - "symbol-placement": "point", - "text-field": "{name_en}", - "text-line-height": 1.5, - "text-letter-spacing": 0.25, - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 1, - 12 - ], - [ - 4, - 30 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855720231.1272" - }, - "filter": [ - "all", - [ - "==", - "$type", - "Point" - ], - [ - "==", - "labelrank", - 1 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "marine_label_point_1", - "paint": { - "text-color": "#999999", - "text-opacity": 0.25 - }, - "source-layer": "marine_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 15, - "visibility": "visible", - "symbol-placement": "line", - "text-field": "{name_en}", - "text-line-height": 1.2, - "text-letter-spacing": 0, - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 4, - 12 - ], - [ - 6, - 16 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855720231.1272" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "in", - "labelrank", - 4, - 5, - 6 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "marine_label_line_other", - "paint": { - "text-color": "#999999", - "text-opacity": 0.25 - }, - "source-layer": "marine_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 15, - "visibility": "visible", - "symbol-placement": "line", - "text-field": "{name_en}", - "text-line-height": 1.2, - "text-letter-spacing": 0, - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 3, - 13 - ], - [ - 5, - 18 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855720231.1272" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "labelrank", - 3 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "marine_label_line_3", - "paint": { - "text-color": "#999999", - "text-opacity": 0.25 - }, - "source-layer": "marine_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 15, - "visibility": "visible", - "symbol-placement": "line", - "text-field": "{name_en}", - "text-line-height": 1.2, - "text-letter-spacing": 0, - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 3, - 14 - ], - [ - 5, - 24 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855720231.1272" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "labelrank", - 2 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "marine_label_line_2", - "paint": { - "text-color": "#999999", - "text-opacity": 0.25 - }, - "source-layer": "marine_label" - }, - { - "interactive": true, - "layout": { - "text-max-width": 15, - "visibility": "visible", - "symbol-placement": "line", - "text-field": "{name_en}", - "text-line-height": 1.2, - "text-letter-spacing": 0.4, - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-size": { - "base": 1, - "stops": [ - [ - 3, - 25 - ], - [ - 4, - 30 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855720231.1272" - }, - "filter": [ - "all", - [ - "==", - "$type", - "LineString" - ], - [ - "==", - "labelrank", - 1 - ] - ], - "type": "symbol", - "source": "mapbox", - "id": "marine_label_line_1", - "paint": { - "text-color": "#999999", - "text-opacity": 0.25 - }, - "source-layer": "marine_label" - }, - { - "interactive": true, - "minzoom": 3, - "layout": { - "text-transform": "uppercase", - "visibility": "visible", - "text-field": { - "base": 1, - "stops": [ - [ - 0, - "{abbr}" - ], - [ - 4, - "{name_en}" - ] - ] - }, - "text-font": [ - "DIN Offc Pro Bold", - "Arial Unicode MS Regular" - ], - "text-letter-spacing": 0.15, - "text-max-width": 7, - "text-size": { - "base": 1, - "stops": [ - [ - 4, - 9 - ], - [ - 7, - 18 - ] - ] - } - }, - "metadata": { - "mapbox:group": "1444855712732.9983" - }, - "maxzoom": 7, - "filter": [ - ">=", - "area", - 80000 - ], - "type": "symbol", - "source": "mapbox", - "id": "state-label-lg", - "paint": { - "text-color": { - "base": 1, - "stops": [ - [ - 0, - "#969696" - ], - [ - 20, - "#969696" - ] - ] - } - }, - "source-layer": "state_label" - }, - { - "interactive": true, - "minzoom": 1, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-max-width": 7, - "text-size": { - "stops": [ - [ - 3, - 8 - ], - [ - 9, - 18 - ] - ], - "base": 0.9 - } - }, - "metadata": { - "mapbox:group": "1444855707128.6584" - }, - "maxzoom": 10, - "filter": [ - ">=", - "scalerank", - 5 - ], - "type": "symbol", - "source": "mapbox", - "id": "country-label-sm", - "paint": { - "text-color": { - "base": 1, - "stops": [ - [ - 0, - "#444" - ], - [ - 10, - "#888" - ] - ] - }, - "text-halo-color": "#000", - "text-halo-width": 1, - "text-halo-blur": 1 - }, - "source-layer": "country_label" - }, - { - "interactive": true, - "minzoom": 1, - "layout": { - "text-field": { - "base": 1, - "stops": [ - [ - 0, - "{code}" - ], - [ - 2, - "{name_en}" - ] - ] - }, - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-max-width": 7, - "text-size": { - "stops": [ - [ - 2, - 8 - ], - [ - 7, - 18 - ] - ], - "base": 0.9 - } - }, - "metadata": { - "mapbox:group": "1444855707128.6584" - }, - "maxzoom": 8, - "filter": [ - "in", - "scalerank", - 3, - 4 - ], - "type": "symbol", - "source": "mapbox", - "id": "country-label-md", - "paint": { - "text-color": { - "base": 1, - "stops": [ - [ - 0, - "#444" - ], - [ - 10, - "#888" - ] - ] - }, - "text-halo-color": "#000", - "text-halo-width": 1, - "text-halo-blur": 1 - }, - "source-layer": "country_label" - }, - { - "interactive": true, - "layout": { - "text-field": "{name_en}", - "text-font": [ - "DIN Offc Pro Medium", - "Arial Unicode MS Regular" - ], - "text-max-width": 6, - "text-size": { - "stops": [ - [ - 1, - 9 - ], - [ - 5, - 18 - ] - ], - "base": 0.9 - } - }, - "metadata": { - "mapbox:group": "1444855707128.6584" - }, - "maxzoom": 12, - "filter": [ - "in", - "scalerank", - 1, - 2 - ], - "type": "symbol", - "source": "mapbox", - "id": "country-label-lg", - "paint": { - "text-color": { - "base": 1, - "stops": [ - [ - 0, - "#666" - ], - [ - 10, - "#999" - ] - ] - }, - "text-halo-color": "#000", - "text-halo-width": 1, - "text-halo-blur": 1 - }, - "source-layer": "country_label" - }, - { - "layout": { - "text-field": "{_osmlint}", - "symbol-placement": "line", - "text-rotation-alignment": "map", - "text-keep-upright": true, - "visibility": "none" - }, - "filter": [ - "in", - "$type", - "Polygon", - "Point", - "LineString" - ], - "type": "symbol", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint copy", - "paint": { - "text-color": "rgba(3,252,244,1)" - }, - "source-layer": "osmlint", - "interactive": true - }, - { - "layout": { - "text-field": "{_osmlint}", - "text-font": [ - "Open Sans Semibold", - "Arial Unicode MS Regular" - ], - "text-anchor": "bottom", - "text-size": { - "base": 1, - "stops": [ - [ - 4, - 6 - ], - [ - 8, - 10 - ] - ] - }, - "text-allow-overlap": false, - "text-offset": [ - 0, - 1.5 - ] - }, - "metadata": { - "mapbox:group": "1452667653414.454" - }, - "filter": [ - "in", - "$type", - "Polygon", - "Point", - "LineString" - ], - "type": "symbol", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint type", - "paint": { - "text-color": "rgba(255,255,255,1)", - "text-halo-width": 2, - "text-halo-color": "rgba(0,0,0,1)", - "text-opacity": { - "base": 1, - "stops": [ - [ - 10, - 0 - ], - [ - 11, - 1 - ] - ] - } - }, - "source-layer": "osmlint", - "interactive": true - }, - { - "layout": { - "text-field": "{_osm_node_id} {_osm_way_id}", - "text-font": [ - "Open Sans Regular", - "Arial Unicode MS Regular" - ], - "text-anchor": "top", - "text-allow-overlap": false, - "text-size": 10, - "text-offset": [ - 0, - 1.5 - ], - "text-ignore-placement": true - }, - "metadata": { - "mapbox:group": "1452667653414.454" - }, - "filter": [ - "in", - "$type", - "Polygon", - "Point", - "LineString" - ], - "type": "symbol", - "source": "mapbox://planemad.3f1b8ov4", - "id": "osmlint id", - "paint": { - "text-color": "rgba(255,255,255,1)", - "text-halo-width": 2, - "text-halo-color": "rgba(0,0,0,1)", - "text-translate": [ - 0, - 0 - ], - "text-translate-anchor": "map", - "text-opacity": { - "base": 1, - "stops": [ - [ - 14, - 0 - ], - [ - 16, - 1 - ] - ] - } - }, - "source-layer": "osmlint", - "interactive": true - } - ], - "created": "2016-01-13T05:40:59.234Z", - "id": "cijcefp3q00elbskq4cgvcivf", - "modified": "2016-01-13T06:52:51.809Z", - "owner": "planemad", - "draft": false -} \ No newline at end of file From dce8b7e85ab6c7330320439630579deace3881b5 Mon Sep 17 00:00:00 2001 From: Katy DeCorah Date: Thu, 14 Apr 2016 14:00:46 -0400 Subject: [PATCH 03/66] update link --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9092fee..2f0f978 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ Public issue tracker for OpenStreetMap contribution work by Mapbox. You're invit ## Contributing -Read the [contributing guide](https://github.com/mapbox/maping/blob/mb-pages/CONTRIBUTING.md) to learn how to add or edit any content. +Read the [contributing guide](https://github.com/mapbox/mapping/blob/mb-pages/CONTRIBUTING.md) to learn how to add or edit any content. ## Build @@ -20,4 +20,4 @@ This site is built with [Jekyll](https://help.github.com/articles/setting-up-you **Testing site** (if testing for the first time, run `npm install` first); - npm test \ No newline at end of file + npm test From 2cf6b88de052eb3af61f8d33d620d31d213b02a5 Mon Sep 17 00:00:00 2001 From: Will Knowles Date: Sat, 16 Apr 2016 07:54:36 +0100 Subject: [PATCH 04/66] add **Download objects to a new layer** option this was not explicitly stated in the instructions but was shown in the image above. I thought it would help to clarify. --- getting-started/_posts/0000-01-01-getting-started.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index b79deaf..ee1b19c 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -74,7 +74,7 @@ Remote control allows you to launch JOSM directly from the map on OpenStreetMap. ![enable-remote-control]({{site.baseurl}}/images/enable-remote-control.png) -Also check the **** option. Now you should be able to retrieve data directly starting on OpenStreetMap.org like this: +Also check the **Download objects to a new layer** option. Now you should be able to retrieve data directly starting on OpenStreetMap.org like this: ![retrieve-data]({{site.baseurl}}/images/retrieve-data.gif) @@ -84,4 +84,4 @@ By default JOSM is allocated with 247-1024 MB of memory depending on the operati ![increasing memory]({{site.baseurl}}/images/increasing-memory.png) -To get rid of this error increase the default allocated memory for JOSM by following [these steps](https://gist.github.com/jothirnadh/00352fff58ce2628cc4f#supply-parameters). If you are not sure of fixing this, do contact someone from the data team. \ No newline at end of file +To get rid of this error increase the default allocated memory for JOSM by following [these steps](https://gist.github.com/jothirnadh/00352fff58ce2628cc4f#supply-parameters). If you are not sure of fixing this, do contact someone from the data team. From 7456097adab121b5268c526c11b0f4e1289ad3dc Mon Sep 17 00:00:00 2001 From: Andrey Golovin Date: Fri, 6 May 2016 23:54:09 +0300 Subject: [PATCH 05/66] fixed link to fresh (2016) .mapcss QA style --- mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md b/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md index 1fd5096..fe95a49 100644 --- a/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md +++ b/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md @@ -170,7 +170,7 @@ Try different drawing styles yourself and figure out which ones help you do your #### Highlight data freshness -You can use [this style](https://raw.githubusercontent.com/Andygol/josm-styles/master/created_in_2015.mapcss) to highlight features that are created or modified in 2015. To configure this: +You can use [this style](https://raw.githubusercontent.com/Andygol/josm-styles/master/recent%20changes_2016.mapcss) to highlight features that are created or modified in 2016. To configure this: ![](https://cloud.githubusercontent.com/assets/369696/9634340/e596f890-5199-11e5-8335-55d63a9b11d2.gif) @@ -207,4 +207,4 @@ You can script JOSM to automate certain workflows. For example: ## Further reading and questions -For further information, take a look at the [JOSM help](https://josm.openstreetmap.de/wiki/Help). \ No newline at end of file +For further information, take a look at the [JOSM help](https://josm.openstreetmap.de/wiki/Help). From e4d481d44f4cdf7995dcc3652e40dbc1c8ba42d3 Mon Sep 17 00:00:00 2001 From: Katy DeCorah Date: Mon, 6 Jun 2016 08:41:35 -0400 Subject: [PATCH 06/66] to jekyll 3 (#190) --- Gemfile | 6 ---- Gemfile.lock | 82 ------------------------------------------- _config.yml | 20 +++-------- _layouts/default.html | 10 +++--- index.html | 4 --- 5 files changed, 10 insertions(+), 112 deletions(-) delete mode 100644 Gemfile delete mode 100644 Gemfile.lock delete mode 100644 index.html diff --git a/Gemfile b/Gemfile deleted file mode 100644 index b8f6986..0000000 --- a/Gemfile +++ /dev/null @@ -1,6 +0,0 @@ -source 'https://rubygems.org' - -gem 'jekyll', '2.1.1' -gem 'liquid', '2.6.1' -gem 'rdiscount', '2.1.7' -gem 'jekyll-sitemap' \ No newline at end of file diff --git a/Gemfile.lock b/Gemfile.lock deleted file mode 100644 index 2d91f34..0000000 --- a/Gemfile.lock +++ /dev/null @@ -1,82 +0,0 @@ -GEM - remote: https://rubygems.org/ - specs: - addressable (2.3.8) - blankslate (2.1.2.4) - classifier (1.3.4) - fast-stemmer (>= 1.0.0) - coffee-script (2.4.1) - coffee-script-source - execjs - coffee-script-source (1.10.0) - colorator (0.1) - execjs (2.6.0) - faraday (0.9.2) - multipart-post (>= 1.2, < 3) - fast-stemmer (1.0.2) - ffi (1.9.10) - jekyll (2.1.1) - classifier (~> 1.3) - colorator (~> 0.1) - jekyll-coffeescript (~> 1.0) - jekyll-gist (~> 1.0) - jekyll-paginate (~> 1.0) - jekyll-sass-converter (~> 1.0) - jekyll-watch (~> 1.0) - kramdown (~> 1.3) - liquid (~> 2.6.1) - mercenary (~> 0.3.3) - pygments.rb (~> 0.6.0) - redcarpet (~> 3.1) - safe_yaml (~> 1.0) - toml (~> 0.1.0) - jekyll-coffeescript (1.0.1) - coffee-script (~> 2.2) - jekyll-gist (1.4.0) - octokit (~> 4.2) - jekyll-paginate (1.1.0) - jekyll-sass-converter (1.4.0) - sass (~> 3.4) - jekyll-sitemap (0.10.0) - jekyll-watch (1.3.1) - listen (~> 3.0) - kramdown (1.9.0) - liquid (2.6.1) - listen (3.0.6) - rb-fsevent (>= 0.9.3) - rb-inotify (>= 0.9.7) - mercenary (0.3.5) - multipart-post (2.0.0) - octokit (4.2.0) - sawyer (~> 0.6.0, >= 0.5.3) - parslet (1.5.0) - blankslate (~> 2.0) - posix-spawn (0.3.11) - pygments.rb (0.6.3) - posix-spawn (~> 0.3.6) - yajl-ruby (~> 1.2.0) - rb-fsevent (0.9.7) - rb-inotify (0.9.7) - ffi (>= 0.5.0) - rdiscount (2.1.7) - redcarpet (3.3.4) - safe_yaml (1.0.4) - sass (3.4.21) - sawyer (0.6.0) - addressable (~> 2.3.5) - faraday (~> 0.8, < 0.10) - toml (0.1.2) - parslet (~> 1.5.0) - yajl-ruby (1.2.1) - -PLATFORMS - ruby - -DEPENDENCIES - jekyll (= 2.1.1) - jekyll-sitemap - liquid (= 2.6.1) - rdiscount (= 2.1.7) - -BUNDLED WITH - 1.11.2 diff --git a/_config.yml b/_config.yml index b495275..a0f624b 100644 --- a/_config.yml +++ b/_config.yml @@ -4,48 +4,38 @@ tileApi: https://api-maps-staging.tilestream.net permalink: /:categories/:title/ baseurl: /mapping title: Mapping with OpenStreetMap -markdown: kramdown exclude: - package.json - node_modules -- Gemfile -- Gemfile.lock - README.MD - CONTRIBUTING.md - test -- JOSM -- Studio - -kramdown: - auto_ids: true - toc_levels: 1..6 - smart_quotes: lsquo,rsquo,ldquo,rdquo defaults: - scope: path: "" # an empty string here means all files in the project - type: "post" # previously `post` in Jekyll 2.2. + type: "posts" values: layout: "post" # DEFAULT ENGLISH - scope: path: "" - type: "page" + type: "pages" values: lang: "en" - scope: path: "" - type: "post" + type: "posts" values: lang: "en" # SPANISH - scope: path: "es" - type: "page" + type: "pages" values: lang: "es" - scope: path: "es" - type: "post" + type: "posts" values: lang: "es" \ No newline at end of file diff --git a/_layouts/default.html b/_layouts/default.html index 2226c4d..f80e680 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -12,8 +12,8 @@ {% if page.card %} - - + + @@ -64,9 +64,9 @@ {% if site.test %}{% endif %} - {% if page.head %}{{page.head}}{% endif %} + {% if page.head %}{{page.head}}{% endif %}{% if layout.head %}{{layout.head}}{% endif %} - + @@ -101,7 +101,7 @@

{{page.title}}

-
{{content}}
+
{{content}}
Terms + diff --git a/index.html b/index.html deleted file mode 100644 index bef2d5e..0000000 --- a/index.html +++ /dev/null @@ -1,4 +0,0 @@ ---- -layout: home -title: Mapping with OpenStreetMap ---- From 982fa73d35918e532c1fa479e941c67779c4c0c8 Mon Sep 17 00:00:00 2001 From: Andrey Golovin Date: Wed, 15 Jun 2016 12:57:53 +0300 Subject: [PATCH 07/66] fixed formatting issue --- .../0000-01-02-modeling-roads-for-navigation.md | 7 ++++--- .../_posts/0000-01-03-turn-lanes.md | 7 ++++--- .../_posts/0000-01-04-qa-for-turn-lanes.md | 14 +++++++------- 3 files changed, 15 insertions(+), 13 deletions(-) diff --git a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-navigation.md b/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-navigation.md index 781bd49..e2a1cf8 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-navigation.md +++ b/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-navigation.md @@ -24,6 +24,7 @@ Use the `lanes=*` key to tag how many full-width traffic lanes there are on a hi ### Roads with more than two lanes There are two cases: + - Roads which carry traffic in both directions and ![bidirectional_road](https://cloud.githubusercontent.com/assets/369696/13230341/9f9db6c0-d9ad-11e5-9f5d-53dd80b40f67.png) @@ -97,10 +98,10 @@ Trace ways for dual carriageways road for each direction as close as possible to Place nodes of the lines in each direction, opposite to each other, which will get a good view of the road on the map -![motorway](https://cloud.githubusercontent.com/assets/369696/13231932/5b417e00-d9b5-11e5-854e-dbed2d209d7c.png) - + ![motorway](https://cloud.githubusercontent.com/assets/369696/13231932/5b417e00-d9b5-11e5-854e-dbed2d209d7c.png) + ## Further reading * Adding lanes in OSM: [OSM wiki](http://wiki.openstreetmap.org/wiki/Key:lanes) * Specifying placement of the OSM-way relative to the road it represents: [Proposal in OSM wiki](http://wiki.openstreetmap.org/wiki/Proposed_features/placement) -* Specifying lanes or similar features running in both directions of the OSM way: [Proposal in OSM wiki](http://wiki.openstreetmap.org/wiki/Proposed_features/Suffix_both_ways) \ No newline at end of file +* Specifying lanes or similar features running in both directions of the OSM way: [Proposal in OSM wiki](http://wiki.openstreetmap.org/wiki/Proposed_features/Suffix_both_ways) diff --git a/mapping-to-improve-navigation/_posts/0000-01-03-turn-lanes.md b/mapping-to-improve-navigation/_posts/0000-01-03-turn-lanes.md index 266845a..20160cf 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-03-turn-lanes.md +++ b/mapping-to-improve-navigation/_posts/0000-01-03-turn-lanes.md @@ -30,10 +30,10 @@ bothways | ![turn lanes both ways](https://cloud.githubusercontent.com/assets/84 ![](http://pdd.ua/r/r/EEB7A996-D8DC-40FC-87EA-01F3E115BC7C/m_1.18_4.jpg) _road markings on the ground_ - © [pdd.ua](http://pdd.ua/ua/34/1.18/) - - + + ## Other Markings apart from turn:lanes - + ### HOV [HOV](http://wiki.openstreetmap.org/wiki/Key:hov) is a symbol demarcated on major roads generally used to indicate vehicle occupancy requirements. @@ -45,6 +45,7 @@ In the above cases tag given to the road are `hov:lanes=designated|yes|yes|yes` ## Pre-requirements for mapping a turn lane in JOSM Before mapping turn lanes activate the following preferences in JOSM to visualize the mapped turn lanes: `preferences > Map Settings` + * *`Map Paint Styles > Lane and road attributes`* ![lane_and_road_attributes](https://cloud.githubusercontent.com/assets/13744156/13218788/c55fab96-d991-11e5-89b2-b281986d704e.gif) diff --git a/mapping-to-improve-navigation/_posts/0000-01-04-qa-for-turn-lanes.md b/mapping-to-improve-navigation/_posts/0000-01-04-qa-for-turn-lanes.md index 69ea18a..85cfc3d 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-04-qa-for-turn-lanes.md +++ b/mapping-to-improve-navigation/_posts/0000-01-04-qa-for-turn-lanes.md @@ -36,18 +36,18 @@ Turn lanes should terminate at the first highway junction after the start of the ### 5. Turn lane forward -In case of bi-directional ways, the key [turn:lanes:forward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the same direction as the osm-way; while adding this we must view the road in the direction to the osm-way(**on the direction where the osm-way arrow is pointing**). +In case of bi-directional ways, the key [turn:lanes:forward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the same direction as the osm-way; while adding this we must view the road in the direction to the osm-way (**on the direction where the osm-way arrow is pointing**). ![turn:lanes:forward](https://cloud.githubusercontent.com/assets/8401827/13175904/c5c922fc-d733-11e5-91b1-c0f9e5181fda.gif) ### 6. Turn lane backward -In case of bi-directional ways, the key [turn:lanes:backward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the opposite direction as the osm-way; while adding this we must view the road in the oppoiste direction to the osm-way(**opposite to direction where the osm-way arrow is pointing**). +In case of bi-directional ways, the key [turn:lanes:backward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the opposite direction as the osm-way; while adding this we must view the road in the opposite direction to the osm-way (**opposite to direction where the osm-way arrow is pointing**). ![turn:lanes:backward](https://cloud.githubusercontent.com/assets/13744156/13172709/859957c4-d71f-11e5-8cd9-ea154ad5d2e8.gif) *Adding a `turn:lanes:backward` tag* - + ### 7. Adding dual carriageways: When finding roads mapped as single carriageway while the imagery shows clear separation between roads, split the road where the physical separation starts and add dual carriageways. @@ -56,9 +56,9 @@ When finding roads mapped as single carriageway while the imagery shows clear se **When to add dual carriageway?** -- Add Dual-carriage when - - you see physical separation betweens roads - - **no relation is attached to the way.** +- Add Dual-carriage when + - you see physical separation betweens roads + - **no relation is attached to the way.** - Add `turn:lanes` tag to both the ways. @@ -119,4 +119,4 @@ In the above cases the areas with markings on the roads are not considered as a These are the lanes specifically categorised to take U-turn or reverse-turn. -![screen shot 2016-03-14 at 2 25 28 pm](https://cloud.githubusercontent.com/assets/8401827/13776502/84944b6c-ead0-11e5-92fa-0bb2951760ef.png) \ No newline at end of file +![screen shot 2016-03-14 at 2 25 28 pm](https://cloud.githubusercontent.com/assets/8401827/13776502/84944b6c-ead0-11e5-92fa-0bb2951760ef.png) From 29a6cea66853cac84fc6180adc7aa7a92c642ab0 Mon Sep 17 00:00:00 2001 From: tatsvc Date: Tue, 21 Jun 2016 09:31:15 -0400 Subject: [PATCH 08/66] fixing svgs for firefox --- .../svgs/_mapping-to-improve-navigation.svg | 686 +++++++++++ .../svgs/_the-openstreetmap-data-model.svg | 235 ++++ .../svgs/mapping-to-improve-navigation.svg | 1065 +++++++++++------ .../svgs/the-openstreetmap-data-model.svg | 379 +++--- 4 files changed, 1809 insertions(+), 556 deletions(-) create mode 100644 _includes/svgs/_mapping-to-improve-navigation.svg create mode 100644 _includes/svgs/_the-openstreetmap-data-model.svg diff --git a/_includes/svgs/_mapping-to-improve-navigation.svg b/_includes/svgs/_mapping-to-improve-navigation.svg new file mode 100644 index 0000000..60595c6 --- /dev/null +++ b/_includes/svgs/_mapping-to-improve-navigation.svg @@ -0,0 +1,686 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/_includes/svgs/_the-openstreetmap-data-model.svg b/_includes/svgs/_the-openstreetmap-data-model.svg new file mode 100644 index 0000000..b9937fd --- /dev/null +++ b/_includes/svgs/_the-openstreetmap-data-model.svg @@ -0,0 +1,235 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/_includes/svgs/mapping-to-improve-navigation.svg b/_includes/svgs/mapping-to-improve-navigation.svg index 699f5ba..d2ab931 100644 --- a/_includes/svgs/mapping-to-improve-navigation.svg +++ b/_includes/svgs/mapping-to-improve-navigation.svg @@ -1,388 +1,685 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/_includes/svgs/the-openstreetmap-data-model.svg b/_includes/svgs/the-openstreetmap-data-model.svg index 2f8be3a..e629521 100644 --- a/_includes/svgs/the-openstreetmap-data-model.svg +++ b/_includes/svgs/the-openstreetmap-data-model.svg @@ -1,176 +1,211 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + width="399px" height="377px" viewBox="110 -134 399 377" style="enable-background:new 110 -134 399 377;" xml:space="preserve"> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + From 470d18526565636222f3212eec0b8633b9927438 Mon Sep 17 00:00:00 2001 From: tatsvc Date: Tue, 21 Jun 2016 09:43:07 -0400 Subject: [PATCH 09/66] css fixes --- _layouts/home.html | 4 ++-- site.css | 14 ++++++++++++++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/_layouts/home.html b/_layouts/home.html index d01ccf8..df163d9 100644 --- a/_layouts/home.html +++ b/_layouts/home.html @@ -19,10 +19,10 @@ {% assign langDir = page.lang | append: '/' %} {% assign title = page.dir | downcase | replace: langDir,'' | replace: '/','' %} {% assign guideCount = 0 %}{% for post in site.categories[title] %}{% assign guideCount = guideCount | plus: 1 %}{% endfor %} - +
- + {% if page.image %} {% assign illo = page.image | prepend: 'svgs/' %} {% include {{illo}} %} diff --git a/site.css b/site.css index 51f7674..dd1ad8a 100644 --- a/site.css +++ b/site.css @@ -66,6 +66,11 @@ svg { width: 100%; } +#the-openstreetmap-data-model svg +{ + height: 350px; +} + /* Colors ------------------------------------------------------- */ @@ -1235,6 +1240,9 @@ pre.pre-guides:before { height: 230px; padding: 30px; } + #the-openstreetmap-data-model svg { + height: 270px; + } } @media only screen and (max-width: 1024px) { @@ -1247,6 +1255,9 @@ pre.pre-guides:before { height: 325px; } + #the-openstreetmap-data-model svg { + height: 360px; + } } @media only screen and (max-width: 900px) { @@ -1270,6 +1281,9 @@ pre.pre-guides:before { .guide > div { /*height: 455px;*/ } + #the-openstreetmap-data-model svg { + height: 140px; +} } From 917ac7387916c5af33a6284574c0c56aa5c74759 Mon Sep 17 00:00:00 2001 From: Jothirnadh Date: Mon, 18 Jul 2016 15:54:23 +0530 Subject: [PATCH 10/66] Update 0000-01-05-navigation-mapping-projects.md Updated the status of Navigation projects that are completed by the data team. cc:/ @planemad --- .../0000-01-05-navigation-mapping-projects.md | 29 ++++++++++++++----- 1 file changed, 21 insertions(+), 8 deletions(-) diff --git a/mapping-to-improve-navigation/_posts/0000-01-05-navigation-mapping-projects.md b/mapping-to-improve-navigation/_posts/0000-01-05-navigation-mapping-projects.md index 6691fc7..91862d9 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-05-navigation-mapping-projects.md +++ b/mapping-to-improve-navigation/_posts/0000-01-05-navigation-mapping-projects.md @@ -4,11 +4,24 @@ title: Mapping projects related to navigation Location | Description|Start|End(ETA)|Validation ---|---|---|---|---| -[Palo Alto - Redwood City](http://tasks.teachosm.org/project/119) | Trial run for estimates and workflow evaluation|12/10 |(12/11) | Completed -[SF Peninsula](http://tasks.openstreetmap.us/project/17) | Turn lanes on motorway and trunk junctions in San Francisco Peninsula | 20/01/16 | 5/02/2016 | Completed -[Turn lanes in Palo Alto - 1](https://github.com/mapbox/mapping/issues/144) | Mapping turn lanes on highways tertiary and up in Palo Alto | 08/02/16 | 09/02/16 | Completed | -[Turn lanes in DC - 1](http://tasks.openstreetmap.us/project/19) | Mapping turn lanes on highways tertiary and up in DC | 08/02/16 | 08/02/16 | Completed | -[Turn lanes in SF city](http://tasks.openstreetmap.us/project/21) | Mapping turn lanes on highways tertiary and up in SF city |09/02/16 | 10/02/16 | Completed | -[Turn lanes in DC](http://tasks.openstreetmap.us/project/22) | Mapping turn lanes on highways tertiary and up in DC | 11/02/16 | 12/02/16 | Completed | -[Turn lanes in LA](http://tasks.openstreetmap.us/project/23) | Mapping turn lanes on highways tertiary and up in LA | 12/02/16 | | | -[Turn lanes in SF peninsula up to San Jose ](http://tasks.openstreetmap.us/project/24) | Mapping turn lanes on highways tertiary and up in SF peninsula | | | | +[Palo Alto - Redwood City](http://tasks.teachosm.org/project/119) | Trial run for estimates and workflow evaluation| 10/12/2015 | | | +[SF Peninsula](http://tasks.openstreetmap.us/project/17) | Turn lanes on motorway and trunk junctions in San Francisco Peninsula | 1/20/2016 | 2/05/2016 | Completed +[Turn lanes in Palo Alto - 1](http://tasks.openstreetmap.us/project/18) | Mapping turn lanes on highways tertiary and up in Palo Alto | 2/08/2016 | 2/09/2016 | Completed | +[Turn lanes in DC - 1](http://tasks.openstreetmap.us/project/19) | Mapping turn lanes on highways tertiary and up in DC | 2/08/2016 | 2/08/2016 | Completed | +[Turn lanes in SF city](http://tasks.openstreetmap.us/project/21) | Mapping turn lanes on highways tertiary and up in SF city | 2/09/2016 | 10/02/16 | Completed | +[Turn lanes in DC](http://tasks.openstreetmap.us/project/22) | Mapping turn lanes on highways tertiary and up in DC | 2/11/2016 | 2/12/2016 | Completed | +[Turn lanes in LA](http://tasks.openstreetmap.us/project/23) | Mapping turn lanes on highways tertiary and up in LA | 2/12/2016 | 3/29/2016 | Completed | +[Mapping Exit Numbers and Destinations in 30 US Cities](https://github.com/mapbox/mapping/issues/178) | Adding Exit numbers and Destinations for Top 30 US Cities | 4/01/2016 | 5/04/2016 | Completed | +[San Francisco](http://tasks.openstreetmap.us/project/35) | Mapping turn lanes on highways tertiary and up | 5/05/2016 | 5/11/2016 | Completed | +[Portland](http://tasks.openstreetmap.us/project/36) | Mapping turn lanes on highways tertiary and up | 5/16/2016 | 5/17/2016 | Completed | +[Dallas & Fort Worth](http://tasks.openstreetmap.us/project/37) | Mapping turn lanes on highways tertiary and up | 5/18/2016 |5/23/2016 | Completed | +[New York](http://tasks.openstreetmap.us/project/39) | Mapping turn lanes on highways tertiary and up |5/23/2016 |5/30/2016 |Completed | +[Detroit](http://tasks.openstreetmap.us/project/40) | Mapping turn lanes on highways tertiary and up |5/30/2016 | 6/02/2016 | Completed | +[Houston](http://tasks.openstreetmap.us/project/42) | Mapping turn lanes on highways tertiary and up | 6/03/2016 | 6/09/2016 | Completed | +[Philadelphia](http://tasks.openstreetmap.us/project/44) | Mapping turn lanes on highways tertiary and up | 6/08/2016 | 6/15/2016| Completed | +[Baltimore](http://tasks.openstreetmap.us/project/45) | Mapping turn lanes on highways tertiary and up | 6/15/2016 | 6/16/2016 | Completed | +[Oklahoma](http://tasks.openstreetmap.us/project/46) | Mapping turn lanes on highways tertiary and up | 6/22/2016 | 6/22/2016 | Completed | +[Boston](http://tasks.openstreetmap.us/project/47) | Mapping turn lanes on highways tertiary and up | 6/22/2016 | 06/27/2016 | Completed | +[Denver](http://tasks.openstreetmap.us/project/48) | Mapping turn lanes on highways tertiary and up | 6/28/2016 | 6/29/2016 | Completed | +[Seattle](http://tasks.openstreetmap.us/project/49) | Mapping turn lanes on highways tertiary and up | 6/29/2016 | 7/01/2016 | Completed | +[Mapping turn-restrictions for navigation in 30 cities in US](https://github.com/mapbox/mapping/issues/187) | To map turn-restrictions in 39 US cities using Mapillary as the source | 5/25/2016 | | | From 92a4a48af909048d84c18ec3a8d4ac41f7e6c4f8 Mon Sep 17 00:00:00 2001 From: Sajjad Anwar Date: Fri, 23 Sep 2016 15:39:28 +0200 Subject: [PATCH 11/66] first cut --- .../_posts/0000-01-01-validating-osm.md | 172 ++++++++++++++++++ validating-osm/index.md | 8 + 2 files changed, 180 insertions(+) create mode 100644 validating-osm/_posts/0000-01-01-validating-osm.md create mode 100644 validating-osm/index.md diff --git a/validating-osm/_posts/0000-01-01-validating-osm.md b/validating-osm/_posts/0000-01-01-validating-osm.md new file mode 100644 index 0000000..d3b2608 --- /dev/null +++ b/validating-osm/_posts/0000-01-01-validating-osm.md @@ -0,0 +1,172 @@ +--- +title: Validating OpenStreetMap Data +--- + +At Mapbox, we map as well as inspect the data that is coming into OpenStreetMap for quality. This is the definitive guide that we follow - from detecting potentially harmful changes to inspecting them and eventually fixing the map. + +# Contents + +1. [What is a problematic edit?](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#1-what-is-a-problematic-edit) +2. [Identifying problematic edits.](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#2-identifying-problematic-edits +) + * OSMCha + * OSM Lint + * OSM Communication Channels +3. [Investigation.](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#3-investigation +) + * Inspecting the change. + * Understanding the user. + * Inspecting the changeset. +4. [Response](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#4-response +) +5. [Common Scenarios](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#5-common-scenarios) + + +# 1. What is a problematic edit? + +Every change to OpenStreetMap is contained in a [changeset](http://wiki.openstreetmap.org/wiki/Changeset). They consist of either additions (new feature), modifications (change existing tags, feature location, or location of a referred feature) or deletions by a mapper. + +When working with data in OpenStreetMap, you sometimes come across places where another mapper might have added bad features or tags, changed or moved or deleted a large set of data or an important set of tags. Changes that spoil the quality of OpenStreetMap data are considered problematic edits. + +There are several kinds of potentially problematic changes. For example: + +* Use of proprietary data (like Google Maps) to add data in OpenStreetMap. +* Modification to significant tags like `place`, `boundary`, `highway`, etc. +* Undocumented imports. +* Modifications with outdated imagery. +* Unintentional dragging of nodes in way, that result in geometry changes. + +Creation and deletion of features, modification to tags and modification to a node's location, result in a `version` increment. Every change by every user is retained as a separate version of the object in the OpenStreetMap database. Changes to nodes within a way, or to members of a relation, result in displayed changes to the way/relation but do *not* increment `version`. + +# 2. Identifying problematic edits. + * **OSMCha**: Changeset level notification, giving an overview of how many objects were affected in a changeset. A set of suspects words automatically flag some suspicious changes. Custom filters can be used with chaneset comment, source, and other combinations to look for suspicious edits. Read more about [using OSMCha to identify and inspect OpenStreetMap data.](https://github.com/mapbox/mapping/wiki/Using-OSMCha-for-inspecting-changes-in-OpenStreetMap) + * **Linting** + * **Map Feedback from Mapbox users**: Sometimes we receive notice through [Map feedback](https://www.mapbox.com/map-feedback/) where the Mapbox users report the changes. + * **OSM communication channels.** + +# 3. Investigation + +After identifying potentially problematic data on the map, we want to determine few things to start - the *user* responsible, when - the *time* they made the edit and what made the changes -- the *changeset id*, and the *features edited*. + +These information help you to investigate the change and identify the root cause and type of change. We'll follow an example of misaligned roads in New York City. + +![screenshot 2016-04-14 12 56 09](https://cloud.githubusercontent.com/assets/3423533/14520241/0c277554-0241-11e6-8695-7a76c9cd0683.png) + +## Inspecting the Change + +- Open the area in `JOSM`. +- Select the problematic feature, and check the modified object's history using `Ctrl+H`. +- The History window displays how that selected object was changed over time by different mappers. The display will vary based on the type of object (node/way/relation) selected. The left panel shows the object's versions, modification dates, and responsible users. + - The `Tags` tab of History window have history of tags changed between versions. + - The `Nodes` tab of History window have history of addition/deletion/modification of nodes associated with a way's geometry between versions. + - The `Coordinates` tab of history window have history of the object if its moved for a significant distance. + +![history](https://cloud.githubusercontent.com/assets/3423533/15171329/52dca16a-176b-11e6-8b78-ce3220c62d40.png) + +*JOSM History window* + +In this example, a node was moved a significant distance. From the JOSM history window, we can see the change was made by user `osm_user_name`, in changeset `38544431`, dated `04/14/2016`. + +## Understand the mapper + +The mapper's OSM user profile and [HDYC](hdyc.neis-one.org) profile give an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. + +Click on the OSM user name in the JOSM History window, and load the OpenStreetMap user page where you can view the user's `Edits` history, any `Active Blocks`, any other details on the user, and `Diary` entries. + +A mapper's experience can also be gauged by looking at the number of project days, type of mapper and other points in [HDYC](http://hdyc.neis-one.org/). + +![hdyc](https://cloud.githubusercontent.com/assets/3423533/15170921/ee9fbe6a-1767-11e6-8601-e74f7891a88f.png) + +## Investigate the changeset + +Click on the changeset ID in the JOSM History window to open the OpenStreetMap changeset page, and load details on how many objects were added/modified/deleted. You'll also see the changeset comment, which may contain more self reported details from the user, as well as information on the editor and sources used. + +The OpenStreetMap changeset pages simply lists the objects touched by the user in that particular changeset, but it won't highlight the specific details of changed objects. + +![screenshot 2016-04-14 17 35 26](https://cloud.githubusercontent.com/assets/3423533/14527442/b721eacc-0267-11e6-9fe4-807e6271ccf4.png) + + +This is where [Changeset Map](http://osmlab.github.io/changeset-map/) comes in handy. Changeset Map visualizes all specific features changes made to OpenStreetMap in a changeset. + +- Submit the changeset id to changeset-map to see the changes affected in that changeset. + + `Example`: http://osmlab.github.io/changeset-map/#38544431 + +- Changeset Map shows the features added/modified/deleted or touched during the changeset. Identify all the problematic changed objects by exploring the edits. + +![vali](https://cloud.githubusercontent.com/assets/3423533/14984377/f28d4942-115f-11e6-9c28-956faab784a3.gif) + +# 4. Response + +At this point we know who, when and which changeset associated with the problematic change. + +Most bad edits are accidental and the general strategy to respond to such changes is education. Work to share knowledge with the mapper about the mistake and how it can be avoided in future. Communicate feedback through public changeset comments, visible to all, or sometimes direct messages if more direct contact is helpful. This helps build our community and improve the quality of future contributions to the map. + +In cases where it is determined that the intent of the mapper was to damage the map, an urgent response may be required by reverting the change and reporting the issue to an OSM administrator or DWG. + +## Communicate + +* Drop a comment on the changeset with a description of what was wrong and how it can be fixed. Link to OpenStreetMap wiki or help material that is relevant. +* If the user does not respond or fix non-urgent issues within a week, alert a nearby active mapper of the issue. +* Also look for help on IRC or the local forums or mailing list of the area. + +## Repair + +* For specific malicious changes, consider fixing the specific issue (and reporting it immediately). +* For a changeset that is wholly bad, revert it. Send a message to the mapper responsible and ask for a description of what happened. +* For simple issues, communicate with the mapper to discuss on how it should be fixed. + +### Revert using the JOSM Plugin + +The JOSM [Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter) is a convenient way to revert changes in OpenStreetMap. After every revert, make sure you upload the changes by sharing a changeset comment on why this changeset was reverted. + +Reverting changesets can be tricky, and you can unintentionally break things yourself. Attempt to revert a changeset if you are 100% sure that the changeset is bad and if something goes wrong -- you should be able to fix it. + +![revert](https://cloud.githubusercontent.com/assets/3423533/14527229/25b55a52-0266-11e6-847d-b9601f8fae8d.gif) + +*Using the revert plugin* + +## Report + +* For urgent issues that requires an experienced response, contact the [Data Working Group](http://wiki.openstreetmap.org/wiki/Data_working_group). + +## How to assess urgency to respond + +The level of response depends on how severe the change is to OpenStreetMap. Urgency is somewhat subjective, but here is some guidance. + +1. Changes to significant features like the following should trigger an immediate repair. + - Major boundaries + - Highway connectivity + - Highway hierarchy + - Highways misalignment (like our NYC example) + - Broken multipolygons (water/border) which effect admin boundaries + - Landmarks + +2. Changes to important but less critical features should start with communication, and repair later only if the user does not respond. + - Land use features like forests + - Buildings + - Water bodies + +3. If the mapper is using the proprietary data sources like Google, Bing Maps, Here Maps or other sources which are not open licensed then comment on the user changeset and mention [Copyright guidance for OpenStreetMap](http://www.openstreetmap.org/copyright). Encourage them to revert the changes and follow local knowledge, or stick to Bing and Mapbox Satellite Imagery. + +# 5. Common Scenarios + +Here are a few common scenarios of bad edits in OpenStreetMap. + +### Mistakes by inexperienced mappers +New users are always welcome to edit OpenStreetMap! During their learning process sometimes they might mistakingly attempt to modify/delete major land features like boundaries, important place tags, highways, relations which causes faulty data. In cases like this its good to educate the users by directing them to proper guides, and instructions they need to follow while mapping and encourage them to correct their mistakes. Revert immediately if it's a serious error. + +### Humanitarian OpenStreetMap Team projects +Many new mappers join OpenStreetMap during HOT Activation. HOT tasks have custom imagery; the changeset review should be done using them. If data added does not match either imagery or the custom imagery, or added data is not of good quality, comment on user changeset to help improve their edits and mapping skills. + +### Intentional bad edits +There are few OSM users who intentionally add bad data to OpenStreetMap which should be reverted immediately. +One such example is shown below. Here the user `Andyt30` was intentionally adding family-names to towns, buildings and footpaths. (Changeset:[34155722](https://www.openstreetmap.org/changeset/34155722)) + +![screenshot 2016-05-03 18 47 00](https://cloud.githubusercontent.com/assets/3423533/14984342/d96fe7ee-115f-11e6-9af5-28ac515d9b28.png) + +### Undocumented imports +Open data sets are can be imported into OpenStreetMap. Imports should follow the [Import Guidelines](http://wiki.openstreetmap.org/wiki/Import_guidelines) and add proper documentation to the [Imports catalogue](http://wiki.openstreetmap.org/wiki/Import/Catalogue), and use a dedicated import accounts. If any undocumented imports are seen, comment on the changeset to request documentation details. + +### Automated edits +Automated edits are changes made to OpenStreetMap with less direct human involvement which involves bots, algorithmic imports etc. \ No newline at end of file diff --git a/validating-osm/index.md b/validating-osm/index.md new file mode 100644 index 0000000..b6a0654 --- /dev/null +++ b/validating-osm/index.md @@ -0,0 +1,8 @@ +--- +title: Validating OpenStreetMap +layout: category +order: 8 +color: orange +description: A walkthrough of how to detect, inspect and fix potentially harmful changes in OpenStreetMap. +image: mapping-common-features.svg +--- From 96aaaa52accdf3c8e842c5fddd58bd56f7446edc Mon Sep 17 00:00:00 2001 From: tatsvc Date: Fri, 23 Sep 2016 15:56:02 +0200 Subject: [PATCH 12/66] svg --- _includes/svgs/validating-osm.svg | 241 ++++++++++++++++++++++++++++++ validating-osm/index.md | 2 +- 2 files changed, 242 insertions(+), 1 deletion(-) create mode 100644 _includes/svgs/validating-osm.svg diff --git a/_includes/svgs/validating-osm.svg b/_includes/svgs/validating-osm.svg new file mode 100644 index 0000000..d39fc8a --- /dev/null +++ b/_includes/svgs/validating-osm.svg @@ -0,0 +1,241 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/validating-osm/index.md b/validating-osm/index.md index b6a0654..1bf1b5c 100644 --- a/validating-osm/index.md +++ b/validating-osm/index.md @@ -4,5 +4,5 @@ layout: category order: 8 color: orange description: A walkthrough of how to detect, inspect and fix potentially harmful changes in OpenStreetMap. -image: mapping-common-features.svg +image: validating-osm.svg --- From 37c4eb549e0a3321eadfb4cfe98005eed0d4635e Mon Sep 17 00:00:00 2001 From: Sajjad Anwar Date: Fri, 23 Sep 2016 15:57:04 +0200 Subject: [PATCH 13/66] fix up title --- .../_posts/0000-01-01-validating-osm.md | 44 ++++++------------- 1 file changed, 13 insertions(+), 31 deletions(-) diff --git a/validating-osm/_posts/0000-01-01-validating-osm.md b/validating-osm/_posts/0000-01-01-validating-osm.md index d3b2608..9c292b9 100644 --- a/validating-osm/_posts/0000-01-01-validating-osm.md +++ b/validating-osm/_posts/0000-01-01-validating-osm.md @@ -4,25 +4,7 @@ title: Validating OpenStreetMap Data At Mapbox, we map as well as inspect the data that is coming into OpenStreetMap for quality. This is the definitive guide that we follow - from detecting potentially harmful changes to inspecting them and eventually fixing the map. -# Contents - -1. [What is a problematic edit?](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#1-what-is-a-problematic-edit) -2. [Identifying problematic edits.](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#2-identifying-problematic-edits -) - * OSMCha - * OSM Lint - * OSM Communication Channels -3. [Investigation.](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#3-investigation -) - * Inspecting the change. - * Understanding the user. - * Inspecting the changeset. -4. [Response](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#4-response -) -5. [Common Scenarios](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#5-common-scenarios) - - -# 1. What is a problematic edit? +## What is a problematic edit? Every change to OpenStreetMap is contained in a [changeset](http://wiki.openstreetmap.org/wiki/Changeset). They consist of either additions (new feature), modifications (change existing tags, feature location, or location of a referred feature) or deletions by a mapper. @@ -38,13 +20,13 @@ There are several kinds of potentially problematic changes. For example: Creation and deletion of features, modification to tags and modification to a node's location, result in a `version` increment. Every change by every user is retained as a separate version of the object in the OpenStreetMap database. Changes to nodes within a way, or to members of a relation, result in displayed changes to the way/relation but do *not* increment `version`. -# 2. Identifying problematic edits. +## Identifying problematic edits. * **OSMCha**: Changeset level notification, giving an overview of how many objects were affected in a changeset. A set of suspects words automatically flag some suspicious changes. Custom filters can be used with chaneset comment, source, and other combinations to look for suspicious edits. Read more about [using OSMCha to identify and inspect OpenStreetMap data.](https://github.com/mapbox/mapping/wiki/Using-OSMCha-for-inspecting-changes-in-OpenStreetMap) * **Linting** * **Map Feedback from Mapbox users**: Sometimes we receive notice through [Map feedback](https://www.mapbox.com/map-feedback/) where the Mapbox users report the changes. * **OSM communication channels.** -# 3. Investigation +## Investigation After identifying potentially problematic data on the map, we want to determine few things to start - the *user* responsible, when - the *time* they made the edit and what made the changes -- the *changeset id*, and the *features edited*. @@ -52,7 +34,7 @@ These information help you to investigate the change and identify the root cause ![screenshot 2016-04-14 12 56 09](https://cloud.githubusercontent.com/assets/3423533/14520241/0c277554-0241-11e6-8695-7a76c9cd0683.png) -## Inspecting the Change +### Inspecting the Change - Open the area in `JOSM`. - Select the problematic feature, and check the modified object's history using `Ctrl+H`. @@ -67,7 +49,7 @@ These information help you to investigate the change and identify the root cause In this example, a node was moved a significant distance. From the JOSM history window, we can see the change was made by user `osm_user_name`, in changeset `38544431`, dated `04/14/2016`. -## Understand the mapper +### Understand the mapper The mapper's OSM user profile and [HDYC](hdyc.neis-one.org) profile give an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. @@ -77,7 +59,7 @@ A mapper's experience can also be gauged by looking at the number of project day ![hdyc](https://cloud.githubusercontent.com/assets/3423533/15170921/ee9fbe6a-1767-11e6-8601-e74f7891a88f.png) -## Investigate the changeset +### Investigate the changeset Click on the changeset ID in the JOSM History window to open the OpenStreetMap changeset page, and load details on how many objects were added/modified/deleted. You'll also see the changeset comment, which may contain more self reported details from the user, as well as information on the editor and sources used. @@ -96,7 +78,7 @@ This is where [Changeset Map](http://osmlab.github.io/changeset-map/) comes in h ![vali](https://cloud.githubusercontent.com/assets/3423533/14984377/f28d4942-115f-11e6-9c28-956faab784a3.gif) -# 4. Response +## Response At this point we know who, when and which changeset associated with the problematic change. @@ -104,19 +86,19 @@ Most bad edits are accidental and the general strategy to respond to such change In cases where it is determined that the intent of the mapper was to damage the map, an urgent response may be required by reverting the change and reporting the issue to an OSM administrator or DWG. -## Communicate +### Communicate * Drop a comment on the changeset with a description of what was wrong and how it can be fixed. Link to OpenStreetMap wiki or help material that is relevant. * If the user does not respond or fix non-urgent issues within a week, alert a nearby active mapper of the issue. * Also look for help on IRC or the local forums or mailing list of the area. -## Repair +### Repair * For specific malicious changes, consider fixing the specific issue (and reporting it immediately). * For a changeset that is wholly bad, revert it. Send a message to the mapper responsible and ask for a description of what happened. * For simple issues, communicate with the mapper to discuss on how it should be fixed. -### Revert using the JOSM Plugin +#### Revert using the JOSM Plugin The JOSM [Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter) is a convenient way to revert changes in OpenStreetMap. After every revert, make sure you upload the changes by sharing a changeset comment on why this changeset was reverted. @@ -126,11 +108,11 @@ Reverting changesets can be tricky, and you can unintentionally break things you *Using the revert plugin* -## Report +### Report * For urgent issues that requires an experienced response, contact the [Data Working Group](http://wiki.openstreetmap.org/wiki/Data_working_group). -## How to assess urgency to respond +### How to assess urgency to respond The level of response depends on how severe the change is to OpenStreetMap. Urgency is somewhat subjective, but here is some guidance. @@ -149,7 +131,7 @@ The level of response depends on how severe the change is to OpenStreetMap. Urge 3. If the mapper is using the proprietary data sources like Google, Bing Maps, Here Maps or other sources which are not open licensed then comment on the user changeset and mention [Copyright guidance for OpenStreetMap](http://www.openstreetmap.org/copyright). Encourage them to revert the changes and follow local knowledge, or stick to Bing and Mapbox Satellite Imagery. -# 5. Common Scenarios +## Common Scenarios Here are a few common scenarios of bad edits in OpenStreetMap. From 708708810bd6f6883664e74393c599a2426b8fa4 Mon Sep 17 00:00:00 2001 From: Katy DeCorah Date: Fri, 23 Sep 2016 10:18:09 -0400 Subject: [PATCH 14/66] copy edits --- .../_posts/0000-01-01-validating-osm.md | 119 +++++++++--------- 1 file changed, 56 insertions(+), 63 deletions(-) diff --git a/validating-osm/_posts/0000-01-01-validating-osm.md b/validating-osm/_posts/0000-01-01-validating-osm.md index d3b2608..f35e6d6 100644 --- a/validating-osm/_posts/0000-01-01-validating-osm.md +++ b/validating-osm/_posts/0000-01-01-validating-osm.md @@ -4,25 +4,7 @@ title: Validating OpenStreetMap Data At Mapbox, we map as well as inspect the data that is coming into OpenStreetMap for quality. This is the definitive guide that we follow - from detecting potentially harmful changes to inspecting them and eventually fixing the map. -# Contents - -1. [What is a problematic edit?](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#1-what-is-a-problematic-edit) -2. [Identifying problematic edits.](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#2-identifying-problematic-edits -) - * OSMCha - * OSM Lint - * OSM Communication Channels -3. [Investigation.](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#3-investigation -) - * Inspecting the change. - * Understanding the user. - * Inspecting the changeset. -4. [Response](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#4-response -) -5. [Common Scenarios](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap#5-common-scenarios) - - -# 1. What is a problematic edit? +## 1. What is a problematic edit? Every change to OpenStreetMap is contained in a [changeset](http://wiki.openstreetmap.org/wiki/Changeset). They consist of either additions (new feature), modifications (change existing tags, feature location, or location of a referred feature) or deletions by a mapper. @@ -34,54 +16,60 @@ There are several kinds of potentially problematic changes. For example: * Modification to significant tags like `place`, `boundary`, `highway`, etc. * Undocumented imports. * Modifications with outdated imagery. -* Unintentional dragging of nodes in way, that result in geometry changes. +* Unintentional dragging of nodes in way that results in geometry changes. Creation and deletion of features, modification to tags and modification to a node's location, result in a `version` increment. Every change by every user is retained as a separate version of the object in the OpenStreetMap database. Changes to nodes within a way, or to members of a relation, result in displayed changes to the way/relation but do *not* increment `version`. -# 2. Identifying problematic edits. - * **OSMCha**: Changeset level notification, giving an overview of how many objects were affected in a changeset. A set of suspects words automatically flag some suspicious changes. Custom filters can be used with chaneset comment, source, and other combinations to look for suspicious edits. Read more about [using OSMCha to identify and inspect OpenStreetMap data.](https://github.com/mapbox/mapping/wiki/Using-OSMCha-for-inspecting-changes-in-OpenStreetMap) - * **Linting** +## 2. Identifying problematic edits. + + * **OSMCha**: Changeset level notification, giving an overview of how many objects were affected in a changeset. A set of suspects words automatically flag some suspicious changes. Custom filters can be used with changeset comment, source, and other combinations to look for suspicious edits. Read more about [using OSMCha to identify and inspect OpenStreetMap data.](https://github.com/mapbox/mapping/wiki/Using-OSMCha-for-inspecting-changes-in-OpenStreetMap) + * **Linting** * **Map Feedback from Mapbox users**: Sometimes we receive notice through [Map feedback](https://www.mapbox.com/map-feedback/) where the Mapbox users report the changes. * **OSM communication channels.** -# 3. Investigation +## 3. Investigation + +After identifying potentially problematic data on the map, you will want to determine few things to start: -After identifying potentially problematic data on the map, we want to determine few things to start - the *user* responsible, when - the *time* they made the edit and what made the changes -- the *changeset id*, and the *features edited*. +* the *user* responsible +* the *time* they made the edit +* what made the changes - the *changeset id* +* the *features edited* -These information help you to investigate the change and identify the root cause and type of change. We'll follow an example of misaligned roads in New York City. +This information will help us investigate the change and identify the cause and type of change. Let's follow an example of misaligned roads in New York City. ![screenshot 2016-04-14 12 56 09](https://cloud.githubusercontent.com/assets/3423533/14520241/0c277554-0241-11e6-8695-7a76c9cd0683.png) -## Inspecting the Change +### Inspecting the change -- Open the area in `JOSM`. -- Select the problematic feature, and check the modified object's history using `Ctrl+H`. -- The History window displays how that selected object was changed over time by different mappers. The display will vary based on the type of object (node/way/relation) selected. The left panel shows the object's versions, modification dates, and responsible users. - - The `Tags` tab of History window have history of tags changed between versions. - - The `Nodes` tab of History window have history of addition/deletion/modification of nodes associated with a way's geometry between versions. - - The `Coordinates` tab of history window have history of the object if its moved for a significant distance. +1. Open the area in `JOSM`. +2. Select the problematic feature, and check the modified object's history using `Ctrl+H`. +3. The History window displays how that selected object was changed over time by different mappers. The display will vary based on the type of object (node/way/relation) selected. The left panel shows the object's versions, modification dates, and responsible users. + - The `Tags` tab of History window has the history of tags changed between versions. + - The `Nodes` tab of History window has the history of addition/deletion/modification of nodes associated with a way's geometry between versions. + - The `Coordinates` tab of history window has the history of the object if its moved for a significant distance. ![history](https://cloud.githubusercontent.com/assets/3423533/15171329/52dca16a-176b-11e6-8b78-ce3220c62d40.png) *JOSM History window* -In this example, a node was moved a significant distance. From the JOSM history window, we can see the change was made by user `osm_user_name`, in changeset `38544431`, dated `04/14/2016`. +In this example, a node was moved a significant distance. From the JOSM history window, you can see the change was made by user `osm_user_name`, in changeset `38544431`, dated `04/14/2016`. -## Understand the mapper +### Understand the mapper -The mapper's OSM user profile and [HDYC](hdyc.neis-one.org) profile give an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. +The mapper's OSM user profile and [HDYC](http://hdyc.neis-one.org) profile gives an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. -Click on the OSM user name in the JOSM History window, and load the OpenStreetMap user page where you can view the user's `Edits` history, any `Active Blocks`, any other details on the user, and `Diary` entries. +Click on the OSM user name in the JOSM History window, and load the OSM user page where you can view the user's `Edits` history, any `Active Blocks`, any other details on the user, and `Diary` entries. -A mapper's experience can also be gauged by looking at the number of project days, type of mapper and other points in [HDYC](http://hdyc.neis-one.org/). +You cal also gauge a mapper's experience by looking at the number of project days, type of mapper and other points in [HDYC](http://hdyc.neis-one.org/). ![hdyc](https://cloud.githubusercontent.com/assets/3423533/15170921/ee9fbe6a-1767-11e6-8601-e74f7891a88f.png) -## Investigate the changeset +### Investigate the changeset -Click on the changeset ID in the JOSM History window to open the OpenStreetMap changeset page, and load details on how many objects were added/modified/deleted. You'll also see the changeset comment, which may contain more self reported details from the user, as well as information on the editor and sources used. +Click on the changeset ID in the JOSM History window to open the OpenStreetMap changeset page, and load details on how many objects were added/modified/deleted. You'll also see the changeset comment, which may contain more self-reported details from the user, as well as information on the editor and sources used. -The OpenStreetMap changeset pages simply lists the objects touched by the user in that particular changeset, but it won't highlight the specific details of changed objects. +The OpenStreetMap changeset pages list the objects touched by the user in that particular changeset, but it won't highlight the specific details of changed objects. ![screenshot 2016-04-14 17 35 26](https://cloud.githubusercontent.com/assets/3423533/14527442/b721eacc-0267-11e6-9fe4-807e6271ccf4.png) @@ -90,33 +78,33 @@ This is where [Changeset Map](http://osmlab.github.io/changeset-map/) comes in h - Submit the changeset id to changeset-map to see the changes affected in that changeset. - `Example`: http://osmlab.github.io/changeset-map/#38544431 + `Example`: -- Changeset Map shows the features added/modified/deleted or touched during the changeset. Identify all the problematic changed objects by exploring the edits. +- Changeset Map shows the features added/modified/deleted or touched during the changeset. Identify all the problematic changed objects by exploring the edits. ![vali](https://cloud.githubusercontent.com/assets/3423533/14984377/f28d4942-115f-11e6-9c28-956faab784a3.gif) -# 4. Response +## 4. Response -At this point we know who, when and which changeset associated with the problematic change. +At this point, you know who, when, and which changeset are associated with the problematic change. -Most bad edits are accidental and the general strategy to respond to such changes is education. Work to share knowledge with the mapper about the mistake and how it can be avoided in future. Communicate feedback through public changeset comments, visible to all, or sometimes direct messages if more direct contact is helpful. This helps build our community and improve the quality of future contributions to the map. +Most bad edits are accidental, and the general strategy to respond to such changes is education. Work to share knowledge with the mapper about the mistake and how it can be avoided in future. Communicate feedback through public changeset comments, visible to all, or sometimes direct messages if more direct contact is helpful. This helps build our community and improve the quality of future contributions to the map. In cases where it is determined that the intent of the mapper was to damage the map, an urgent response may be required by reverting the change and reporting the issue to an OSM administrator or DWG. -## Communicate +### Communicate -* Drop a comment on the changeset with a description of what was wrong and how it can be fixed. Link to OpenStreetMap wiki or help material that is relevant. +* Leave a comment on the changeset with a description of what was wrong and how it can be fixed. Link to OpenStreetMap wiki or link to help material that is relevant. * If the user does not respond or fix non-urgent issues within a week, alert a nearby active mapper of the issue. * Also look for help on IRC or the local forums or mailing list of the area. -## Repair +### Repair -* For specific malicious changes, consider fixing the specific issue (and reporting it immediately). +* For specific malicious changes, consider fixing the issue (and reporting it immediately). * For a changeset that is wholly bad, revert it. Send a message to the mapper responsible and ask for a description of what happened. * For simple issues, communicate with the mapper to discuss on how it should be fixed. -### Revert using the JOSM Plugin +#### Revert using the JOSM Plugin The JOSM [Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter) is a convenient way to revert changes in OpenStreetMap. After every revert, make sure you upload the changes by sharing a changeset comment on why this changeset was reverted. @@ -126,11 +114,11 @@ Reverting changesets can be tricky, and you can unintentionally break things you *Using the revert plugin* -## Report +### Report * For urgent issues that requires an experienced response, contact the [Data Working Group](http://wiki.openstreetmap.org/wiki/Data_working_group). -## How to assess urgency to respond +### How to assess urgency to respond The level of response depends on how severe the change is to OpenStreetMap. Urgency is somewhat subjective, but here is some guidance. @@ -153,20 +141,25 @@ The level of response depends on how severe the change is to OpenStreetMap. Urge Here are a few common scenarios of bad edits in OpenStreetMap. -### Mistakes by inexperienced mappers -New users are always welcome to edit OpenStreetMap! During their learning process sometimes they might mistakingly attempt to modify/delete major land features like boundaries, important place tags, highways, relations which causes faulty data. In cases like this its good to educate the users by directing them to proper guides, and instructions they need to follow while mapping and encourage them to correct their mistakes. Revert immediately if it's a serious error. +#### Mistakes by inexperienced mappers + +New users are always welcome to edit OpenStreetMap! During their learning process sometimes they may mistakingly attempt to modify/delete major land features like boundaries, important place tags, highways, and relations which can cause faulty data. In cases like this it's good to educate the users by directing them to proper guides, and instructions they need to follow while mapping and encourage them to correct their mistakes. Revert immediately if it's a serious error. + +#### Humanitarian OpenStreetMap Team projects -### Humanitarian OpenStreetMap Team projects Many new mappers join OpenStreetMap during HOT Activation. HOT tasks have custom imagery; the changeset review should be done using them. If data added does not match either imagery or the custom imagery, or added data is not of good quality, comment on user changeset to help improve their edits and mapping skills. -### Intentional bad edits -There are few OSM users who intentionally add bad data to OpenStreetMap which should be reverted immediately. -One such example is shown below. Here the user `Andyt30` was intentionally adding family-names to towns, buildings and footpaths. (Changeset:[34155722](https://www.openstreetmap.org/changeset/34155722)) +#### Intentional bad edits + +There are few users who intentionally add bad data to OpenStreetMap which should be reverted immediately. +One such example is shown below. Here the user `Andyt30` was intentionally adding family-names to towns, buildings, and footpaths. (Changeset:[34155722](https://www.openstreetmap.org/changeset/34155722)) ![screenshot 2016-05-03 18 47 00](https://cloud.githubusercontent.com/assets/3423533/14984342/d96fe7ee-115f-11e6-9af5-28ac515d9b28.png) -### Undocumented imports -Open data sets are can be imported into OpenStreetMap. Imports should follow the [Import Guidelines](http://wiki.openstreetmap.org/wiki/Import_guidelines) and add proper documentation to the [Imports catalogue](http://wiki.openstreetmap.org/wiki/Import/Catalogue), and use a dedicated import accounts. If any undocumented imports are seen, comment on the changeset to request documentation details. +#### Undocumented imports + +You can import open datasets into OpenStreetMap. Imports should follow the [Import Guidelines](http://wiki.openstreetmap.org/wiki/Import_guidelines) and add proper documentation to the [Imports catalogue](http://wiki.openstreetmap.org/wiki/Import/Catalogue), and use a dedicated import accounts. If any undocumented imports are seen, comment on the changeset to request documentation details. + +#### Automated edits -### Automated edits -Automated edits are changes made to OpenStreetMap with less direct human involvement which involves bots, algorithmic imports etc. \ No newline at end of file +Automated edits are changes made to OpenStreetMap with less direct human involvement which involves bots, algorithmic imports, etc. \ No newline at end of file From 88e1ef687e235591c83decc82ee7d0fbf41d3168 Mon Sep 17 00:00:00 2001 From: tatsvc Date: Fri, 23 Sep 2016 16:20:35 +0200 Subject: [PATCH 15/66] fixes --- .../svgs/mapping-to-improve-navigation-01.svg | 6 + .../svgs/mapping-to-improve-navigation.svg | 1377 +++++++++-------- _includes/svgs/validating-osm.svg | 1066 ++++++++++--- site.css | 26 +- 4 files changed, 1570 insertions(+), 905 deletions(-) create mode 100644 _includes/svgs/mapping-to-improve-navigation-01.svg diff --git a/_includes/svgs/mapping-to-improve-navigation-01.svg b/_includes/svgs/mapping-to-improve-navigation-01.svg new file mode 100644 index 0000000..161aeb7 --- /dev/null +++ b/_includes/svgs/mapping-to-improve-navigation-01.svg @@ -0,0 +1,6 @@ + + + + diff --git a/_includes/svgs/mapping-to-improve-navigation.svg b/_includes/svgs/mapping-to-improve-navigation.svg index d2ab931..4a2e6d2 100644 --- a/_includes/svgs/mapping-to-improve-navigation.svg +++ b/_includes/svgs/mapping-to-improve-navigation.svg @@ -1,685 +1,718 @@ - - + - - - - - - + + + + + - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + - - - - - - - - - + + + + + + + + + - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/_includes/svgs/validating-osm.svg b/_includes/svgs/validating-osm.svg index d39fc8a..69d8bcc 100644 --- a/_includes/svgs/validating-osm.svg +++ b/_includes/svgs/validating-osm.svg @@ -1,241 +1,843 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - - + + + + + + + + + + + + diff --git a/site.css b/site.css index dd1ad8a..bcc1ede 100644 --- a/site.css +++ b/site.css @@ -70,6 +70,15 @@ svg { { height: 350px; } +#mapping-to-improve-navigation svg +{ + max-height: 260px; +} + + #validating-openstreetmap svg +{ + height: 210px; +} /* Colors ------------------------------------------------------- */ @@ -1283,7 +1292,8 @@ pre.pre-guides:before { } #the-openstreetmap-data-model svg { height: 140px; -} + } + } @@ -1318,4 +1328,18 @@ pre.pre-guides:before { padding-right: 0px; min-height: 0px; } + + #the-openstreetmap-data-model svg + { + max-height: 140px; + } + #mapping-to-improve-navigation svg + { + max-height: 140px; + } + + #validating-openstreetmap svg + { + max-height: 140px; + } } From defc8029c7d046df70d96b7722274ad8025178df Mon Sep 17 00:00:00 2001 From: Sajjad Anwar Date: Fri, 23 Sep 2016 17:21:43 +0200 Subject: [PATCH 16/66] add osmcha --- .../_posts/0000-01-02-using-osmcha.md | 94 +++++++++++++++++++ 1 file changed, 94 insertions(+) create mode 100644 validating-osm/_posts/0000-01-02-using-osmcha.md diff --git a/validating-osm/_posts/0000-01-02-using-osmcha.md b/validating-osm/_posts/0000-01-02-using-osmcha.md new file mode 100644 index 0000000..7adbbe1 --- /dev/null +++ b/validating-osm/_posts/0000-01-02-using-osmcha.md @@ -0,0 +1,94 @@ +--- +title: Using OSMCha for inspecting changes in OpenStreetMap +--- + +## Finding suspicious map edits using OSMCha + +**[OSM Changeset Analyzer](http://osmcha.mapbox.com/)** or OSMCha is a tool to filter and analyze changesets on OpenStreetMap using the [changeset metadata](https://www.openstreetmap.org/api/0.6/changeset/41775489/download). The tool has a live listing of every changeset on the map, flags potentially suspicious edits and has various filters to find changesets that match a certain criteria. + +![screenshot 2016-09-06 16 00 06](https://cloud.githubusercontent.com/assets/8921295/18270541/0de8330c-744b-11e6-8582-7e49d6acec9d.png) +_Latest changesets listed in OSMCha_ + +The changeset is shown with id, date and time of creation, OSM user, creations in green, modification in yellow, deletions in red, a keyword describing if the changeset fits any set behaviors along with a cross mark to signify that the changeset is unreviewed. + +### Filtering changesets + +The filters available in OSMCha allow various combination of searches to help find problematic edits. + +![screenshot 2016-08-30 16 37 31](https://cloud.githubusercontent.com/assets/8921295/18086930/1a28da0c-6ed0-11e6-8eed-5a0b7ee6cf72.png) +_OSMCha filter dialog_ + +OSMCha automatically tags changeset with certain parameters like `Mass creations` or `Possible import`. + +![screenshot 2016-08-30 16 48 17](https://cloud.githubusercontent.com/assets/8921295/18087208/932c74c6-6ed1-11e6-8176-d6a1a6bb9f93.png)
+_Filter based on automatic flagging_ + + +### Examining the quality of the changeset + +OSMCha uses [Changeset map](https://github.com/osmlab/changeset-map/) to visually represent the features that were added, modified and deleted along with tag changes. This help check the quality of the edits for obvious mistakes. + +screenshot 2016-08-22 15 16 17
+_A [changeset](http://osmlab.github.io/changeset-map/#41576998/way/24464264) showing a object that incorrectly made into a circle_ + +### Workflow to find suspicious changes + +#### Suspicious editing behavior + +**Inexperienced users, deletions and imports** +- [Edits from Maps.me editor](http://osmcha.mapbox.com/?editor__icontains=Maps.Me&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) +- [Mass deletions](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) +- [Mass deletions + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) +- [Mass modifications + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=4) +- [Mass creations + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2)/ [Possible import](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2) + +**Strategy for filters** + +1. iD editor is targeted towards simple editing from new users and any advanced editing happens in JOSM. So, if a mass deletion takes place using iD editor, there is a probability that the user could be inexperienced and the deletions unreasonable. [Example harmful changeset](http://osmcha.mapbox.com/41628531/) + +2. Maps.me users tend to be new to OSM. It is suggested to look for changesets that added unreasonable amount of similar POIs in one area. This could be due to lack experience of the user in mapping coupled with lack of amenities available through the app preset. [Example harmful changeset](http://osmcha.mapbox.com/40927770/) + + Edits from Maps.me editor are automatically uploaded through the app. The app generates an automatic changeset comment based on the kind of amenities that were added. Filtering Maps.me edits with most creations first as sort order helped us in finding most of the bad edits from Maps.me users so far. + +3. This is similar to the first assumption. Mass modifications using iD editor could be a suspicious changeset. Mass modification could be 2 scenarios. When the user modifies tags of a long way(coastline, administrative boundaries,long motorway...) and polygons, these edits are registered to the way/polygon and all the nodes in the feature object. + + The second scenario is when the user changes geometry of an object on OSM, even though only one node is added the whole way/polygon is updated to be modified. [Example harmful changeset](http://osmcha.mapbox.com/41991749/) + +4. Mass creations can also be coupled with iD editor in the filters. The idea is to review changesets which have most creations and see if all the editions fall under the [OSM editing standards and conventions](http://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions). [Example harmful changeset](http://osmcha.mapbox.com/38282141/) + +5. Sometimes, we were able to detect suspicious changesets by going through reason filters such as `edited an object with a significant place tag`, 'edited an object with a significant tag', `edited a wikipedia landmark`. [Example harmful changeset](http://osmcha.mapbox.com/38534916/) + +6. Clever acts of vandalism are hard to detect as the changesets may not be big. We can verify these modifications to `name` tags, deletion of tags from [small changesets that are iD editor contributions](http://osmcha.mapbox.com/?modify__lte=50&editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) or through [random search in OSMCha](http://osmcha.mapbox.com/). Example harmful changeset [1](http://www.openstreetmap.org/node/4331919989), [2](http://www.openstreetmap.org/node/4353068192/history). + + +#### Suspicious changeset keywords + +There are [certain keywords we have stored](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085) to quickly look through changesets that have these words in the changeset comments. For example: Google, Cuss words. + + +#### Finding vandalism detected by the community and reverted by DWG + +Community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map, community informs DWG, DWG reverts these changesets with a changeset comment. + + +- Using **Keywords** + - Using keywords such as `revert`, `cleanup`, `fix` in changeset comment filter, we can find most of the changesets community has taken action on. This list in OSMCha includes fixes, reverts DWG as well. + + +- Using [**OSM - comments**](https://www.mapbox.com/osm-comments/) + - OSM-comments API allows querying changesets with specific parameters + - Link to see changeset comments from all users in OSM - [URL for webview](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) + +Currently there is no direct way of using OSM-Comments-API to see all the changesets on which DWG members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) + +**Finding reverts by DWG** + +![documentations1](https://cloud.githubusercontent.com/assets/8921295/18270714/0cc820da-744c-11e6-8db8-71421c956e07.gif) +_Finding DWG reverts using OSMCha_ + + +- OSMCha allows us to query changesets from specific users. + +- We can query all changesets from revert accounts of DWG members such Woodpeck_repair, pnorman_mechanical etc. + +See more about the [full validation workflow here](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap). \ No newline at end of file From 76af9f28cb465f238170196d01cc3adf33ff611e Mon Sep 17 00:00:00 2001 From: Sajjad Anwar Date: Fri, 23 Sep 2016 17:44:48 +0200 Subject: [PATCH 17/66] merge osmcha. dont call out users --- .../_posts/0000-01-01-validating-osm.md | 96 ++++++++++++++++++- .../_posts/0000-01-02-using-osmcha.md | 94 ------------------ 2 files changed, 93 insertions(+), 97 deletions(-) delete mode 100644 validating-osm/_posts/0000-01-02-using-osmcha.md diff --git a/validating-osm/_posts/0000-01-01-validating-osm.md b/validating-osm/_posts/0000-01-01-validating-osm.md index 6f91a9a..24987ff 100644 --- a/validating-osm/_posts/0000-01-01-validating-osm.md +++ b/validating-osm/_posts/0000-01-01-validating-osm.md @@ -22,7 +22,7 @@ Creation and deletion of features, modification to tags and modification to a no ## Identifying problematic edits. - * **OSMCha**: Changeset level notification, giving an overview of how many objects were affected in a changeset. A set of suspects words automatically flag some suspicious changes. Custom filters can be used with changeset comment, source, and other combinations to look for suspicious edits. Read more about [using OSMCha to identify and inspect OpenStreetMap data.](https://github.com/mapbox/mapping/wiki/Using-OSMCha-for-inspecting-changes-in-OpenStreetMap) + * **OSMCha**: Changeset level notification, giving an overview of how many objects were affected in a changeset. A set of suspects words automatically flag some suspicious changes. Custom filters can be used with changeset comment, source, and other combinations to look for suspicious edits. Read more about [using OSMCha to identify and inspect OpenStreetMap data.](#finding-suspicious-map-edits-using-osmcha) * **Linting** * **Map Feedback from Mapbox users**: Sometimes we receive notice through [Map feedback](https://www.mapbox.com/map-feedback/) where the Mapbox users report the changes. * **OSM communication channels.** @@ -152,7 +152,7 @@ Many new mappers join OpenStreetMap during HOT Activation. HOT tasks have custom #### Intentional bad edits There are few users who intentionally add bad data to OpenStreetMap which should be reverted immediately. -One such example is shown below. Here the user `Andyt30` was intentionally adding family-names to towns, buildings, and footpaths. (Changeset:[34155722](https://www.openstreetmap.org/changeset/34155722)) +One such example is shown below. Here the user was intentionally adding family names to towns, buildings, and footpaths. ![screenshot 2016-05-03 18 47 00](https://cloud.githubusercontent.com/assets/3423533/14984342/d96fe7ee-115f-11e6-9af5-28ac515d9b28.png) @@ -162,4 +162,94 @@ You can import open datasets into OpenStreetMap. Imports should follow the [Impo #### Automated edits -Automated edits are changes made to OpenStreetMap with less direct human involvement which involves bots, algorithmic imports, etc. \ No newline at end of file +Automated edits are changes made to OpenStreetMap with less direct human involvement which involves bots, algorithmic imports, etc. + + +## Finding suspicious map edits using OSMCha + +**[OSM Changeset Analyzer](http://osmcha.mapbox.com/)** or OSMCha is a tool to filter and analyze changesets on OpenStreetMap using the [changeset metadata](https://www.openstreetmap.org/api/0.6/changeset/41775489/download). The tool has a live listing of every changeset on the map, flags potentially suspicious edits and has various filters to find changesets that match a certain criteria. + +![screenshot 2016-09-06 16 00 06](https://cloud.githubusercontent.com/assets/8921295/18270541/0de8330c-744b-11e6-8582-7e49d6acec9d.png) +_Latest changesets listed in OSMCha_ + +The changeset is shown with id, date and time of creation, OSM user, creations in green, modification in yellow, deletions in red, a keyword describing if the changeset fits any set behaviors along with a cross mark to signify that the changeset is unreviewed. + +### Filtering changesets + +The filters available in OSMCha allow various combination of searches to help find problematic edits. + +![screenshot 2016-08-30 16 37 31](https://cloud.githubusercontent.com/assets/8921295/18086930/1a28da0c-6ed0-11e6-8eed-5a0b7ee6cf72.png) +_OSMCha filter dialog_ + +OSMCha automatically tags changeset with certain parameters like `Mass creations` or `Possible import`. + +![screenshot 2016-08-30 16 48 17](https://cloud.githubusercontent.com/assets/8921295/18087208/932c74c6-6ed1-11e6-8176-d6a1a6bb9f93.png)
+_Filter based on automatic flagging_ + + +### Examining the quality of the changeset + +OSMCha uses [Changeset map](https://github.com/osmlab/changeset-map/) to visually represent the features that were added, modified and deleted along with tag changes. This help check the quality of the edits for obvious mistakes. + +screenshot 2016-08-22 15 16 17
+_A [changeset](http://osmlab.github.io/changeset-map/#41576998/way/24464264) showing a object that incorrectly made into a circle_ + +### Workflow to find suspicious changes + +#### Suspicious editing behavior + +**Inexperienced users, deletions and imports** +- [Edits from Maps.me editor](http://osmcha.mapbox.com/?editor__icontains=Maps.Me&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) +- [Mass deletions](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) +- [Mass deletions + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) +- [Mass modifications + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=4) +- [Mass creations + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2)/ [Possible import](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2) + +**Strategy for filters** + +1. iD editor is targeted towards simple editing from new users and any advanced editing happens in JOSM. So, if a mass deletion takes place using iD editor, there is a probability that the user could be inexperienced and the deletions unreasonable. [Example harmful changeset](http://osmcha.mapbox.com/41628531/) + +2. Maps.me users tend to be new to OSM. It is suggested to look for changesets that added unreasonable amount of similar POIs in one area. This could be due to lack experience of the user in mapping coupled with lack of amenities available through the app preset. [Example harmful changeset](http://osmcha.mapbox.com/40927770/) + + Edits from Maps.me editor are automatically uploaded through the app. The app generates an automatic changeset comment based on the kind of amenities that were added. Filtering Maps.me edits with most creations first as sort order helped us in finding most of the bad edits from Maps.me users so far. + +3. This is similar to the first assumption. Mass modifications using iD editor could be a suspicious changeset. Mass modification could be 2 scenarios. When the user modifies tags of a long way(coastline, administrative boundaries,long motorway...) and polygons, these edits are registered to the way/polygon and all the nodes in the feature object. + + The second scenario is when the user changes geometry of an object on OSM, even though only one node is added the whole way/polygon is updated to be modified. [Example harmful changeset](http://osmcha.mapbox.com/41991749/) + +4. Mass creations can also be coupled with iD editor in the filters. The idea is to review changesets which have most creations and see if all the editions fall under the [OSM editing standards and conventions](http://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions). [Example harmful changeset](http://osmcha.mapbox.com/38282141/) + +5. Sometimes, we were able to detect suspicious changesets by going through reason filters such as `edited an object with a significant place tag`, 'edited an object with a significant tag', `edited a wikipedia landmark`. [Example harmful changeset](http://osmcha.mapbox.com/38534916/) + +6. Clever acts of vandalism are hard to detect as the changesets may not be big. We can verify these modifications to `name` tags, deletion of tags from [small changesets that are iD editor contributions](http://osmcha.mapbox.com/?modify__lte=50&editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) or through [random search in OSMCha](http://osmcha.mapbox.com/). Example harmful changeset [1](http://www.openstreetmap.org/node/4331919989), [2](http://www.openstreetmap.org/node/4353068192/history). + + +#### Suspicious changeset keywords + +There are [certain keywords we have stored](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085) to quickly look through changesets that have these words in the changeset comments. For example: Google, Cuss words. + + +#### Finding vandalism detected by the community and reverted by DWG + +Community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map, community informs DWG, DWG reverts these changesets with a changeset comment. + + +- Using **Keywords** + - Using keywords such as `revert`, `cleanup`, `fix` in changeset comment filter, we can find most of the changesets community has taken action on. This list in OSMCha includes fixes, reverts DWG as well. + + +- Using [**OSM - comments**](https://www.mapbox.com/osm-comments/) + - OSM-comments API allows querying changesets with specific parameters + - Link to see changeset comments from all users in OSM - [URL for webview](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) + +Currently there is no direct way of using OSM-Comments-API to see all the changesets on which DWG members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) + +**Finding reverts by DWG** + +![documentations1](https://cloud.githubusercontent.com/assets/8921295/18270714/0cc820da-744c-11e6-8db8-71421c956e07.gif) +_Finding DWG reverts using OSMCha_ + + +- OSMCha allows us to query changesets from specific users. + +- We can query all changesets from revert accounts of DWG members such Woodpeck_repair, pnorman_mechanical etc. \ No newline at end of file diff --git a/validating-osm/_posts/0000-01-02-using-osmcha.md b/validating-osm/_posts/0000-01-02-using-osmcha.md deleted file mode 100644 index 7adbbe1..0000000 --- a/validating-osm/_posts/0000-01-02-using-osmcha.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Using OSMCha for inspecting changes in OpenStreetMap ---- - -## Finding suspicious map edits using OSMCha - -**[OSM Changeset Analyzer](http://osmcha.mapbox.com/)** or OSMCha is a tool to filter and analyze changesets on OpenStreetMap using the [changeset metadata](https://www.openstreetmap.org/api/0.6/changeset/41775489/download). The tool has a live listing of every changeset on the map, flags potentially suspicious edits and has various filters to find changesets that match a certain criteria. - -![screenshot 2016-09-06 16 00 06](https://cloud.githubusercontent.com/assets/8921295/18270541/0de8330c-744b-11e6-8582-7e49d6acec9d.png) -_Latest changesets listed in OSMCha_ - -The changeset is shown with id, date and time of creation, OSM user, creations in green, modification in yellow, deletions in red, a keyword describing if the changeset fits any set behaviors along with a cross mark to signify that the changeset is unreviewed. - -### Filtering changesets - -The filters available in OSMCha allow various combination of searches to help find problematic edits. - -![screenshot 2016-08-30 16 37 31](https://cloud.githubusercontent.com/assets/8921295/18086930/1a28da0c-6ed0-11e6-8eed-5a0b7ee6cf72.png) -_OSMCha filter dialog_ - -OSMCha automatically tags changeset with certain parameters like `Mass creations` or `Possible import`. - -![screenshot 2016-08-30 16 48 17](https://cloud.githubusercontent.com/assets/8921295/18087208/932c74c6-6ed1-11e6-8176-d6a1a6bb9f93.png)
-_Filter based on automatic flagging_ - - -### Examining the quality of the changeset - -OSMCha uses [Changeset map](https://github.com/osmlab/changeset-map/) to visually represent the features that were added, modified and deleted along with tag changes. This help check the quality of the edits for obvious mistakes. - -screenshot 2016-08-22 15 16 17
-_A [changeset](http://osmlab.github.io/changeset-map/#41576998/way/24464264) showing a object that incorrectly made into a circle_ - -### Workflow to find suspicious changes - -#### Suspicious editing behavior - -**Inexperienced users, deletions and imports** -- [Edits from Maps.me editor](http://osmcha.mapbox.com/?editor__icontains=Maps.Me&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) -- [Mass deletions](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) -- [Mass deletions + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) -- [Mass modifications + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=4) -- [Mass creations + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2)/ [Possible import](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2) - -**Strategy for filters** - -1. iD editor is targeted towards simple editing from new users and any advanced editing happens in JOSM. So, if a mass deletion takes place using iD editor, there is a probability that the user could be inexperienced and the deletions unreasonable. [Example harmful changeset](http://osmcha.mapbox.com/41628531/) - -2. Maps.me users tend to be new to OSM. It is suggested to look for changesets that added unreasonable amount of similar POIs in one area. This could be due to lack experience of the user in mapping coupled with lack of amenities available through the app preset. [Example harmful changeset](http://osmcha.mapbox.com/40927770/) - - Edits from Maps.me editor are automatically uploaded through the app. The app generates an automatic changeset comment based on the kind of amenities that were added. Filtering Maps.me edits with most creations first as sort order helped us in finding most of the bad edits from Maps.me users so far. - -3. This is similar to the first assumption. Mass modifications using iD editor could be a suspicious changeset. Mass modification could be 2 scenarios. When the user modifies tags of a long way(coastline, administrative boundaries,long motorway...) and polygons, these edits are registered to the way/polygon and all the nodes in the feature object. - - The second scenario is when the user changes geometry of an object on OSM, even though only one node is added the whole way/polygon is updated to be modified. [Example harmful changeset](http://osmcha.mapbox.com/41991749/) - -4. Mass creations can also be coupled with iD editor in the filters. The idea is to review changesets which have most creations and see if all the editions fall under the [OSM editing standards and conventions](http://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions). [Example harmful changeset](http://osmcha.mapbox.com/38282141/) - -5. Sometimes, we were able to detect suspicious changesets by going through reason filters such as `edited an object with a significant place tag`, 'edited an object with a significant tag', `edited a wikipedia landmark`. [Example harmful changeset](http://osmcha.mapbox.com/38534916/) - -6. Clever acts of vandalism are hard to detect as the changesets may not be big. We can verify these modifications to `name` tags, deletion of tags from [small changesets that are iD editor contributions](http://osmcha.mapbox.com/?modify__lte=50&editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) or through [random search in OSMCha](http://osmcha.mapbox.com/). Example harmful changeset [1](http://www.openstreetmap.org/node/4331919989), [2](http://www.openstreetmap.org/node/4353068192/history). - - -#### Suspicious changeset keywords - -There are [certain keywords we have stored](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085) to quickly look through changesets that have these words in the changeset comments. For example: Google, Cuss words. - - -#### Finding vandalism detected by the community and reverted by DWG - -Community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map, community informs DWG, DWG reverts these changesets with a changeset comment. - - -- Using **Keywords** - - Using keywords such as `revert`, `cleanup`, `fix` in changeset comment filter, we can find most of the changesets community has taken action on. This list in OSMCha includes fixes, reverts DWG as well. - - -- Using [**OSM - comments**](https://www.mapbox.com/osm-comments/) - - OSM-comments API allows querying changesets with specific parameters - - Link to see changeset comments from all users in OSM - [URL for webview](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) - -Currently there is no direct way of using OSM-Comments-API to see all the changesets on which DWG members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) - -**Finding reverts by DWG** - -![documentations1](https://cloud.githubusercontent.com/assets/8921295/18270714/0cc820da-744c-11e6-8db8-71421c956e07.gif) -_Finding DWG reverts using OSMCha_ - - -- OSMCha allows us to query changesets from specific users. - -- We can query all changesets from revert accounts of DWG members such Woodpeck_repair, pnorman_mechanical etc. - -See more about the [full validation workflow here](https://github.com/mapbox/mapping/wiki/Validating-OpenStreetMap). \ No newline at end of file From 844388c2f567dfb170ca96ddaf35e8a1510021e9 Mon Sep 17 00:00:00 2001 From: Katy DeCorah Date: Fri, 23 Sep 2016 12:08:29 -0400 Subject: [PATCH 18/66] copy edits --- .../_posts/0000-01-01-validating-osm.md | 70 ++++++++----------- 1 file changed, 31 insertions(+), 39 deletions(-) diff --git a/validating-osm/_posts/0000-01-01-validating-osm.md b/validating-osm/_posts/0000-01-01-validating-osm.md index 24987ff..2f1823e 100644 --- a/validating-osm/_posts/0000-01-01-validating-osm.md +++ b/validating-osm/_posts/0000-01-01-validating-osm.md @@ -53,13 +53,13 @@ This information will help us investigate the change and identify the cause and *JOSM History window* -In this example, a node was moved a significant distance. From the JOSM history window, you can see the change was made by user `osm_user_name`, in changeset `38544431`, dated `04/14/2016`. +In this example, someone moved a node a significant distance. From the JOSM history window, you can see the change was made by user `osm_user_name`, in changeset `38544431`, dated `04/14/2016`. ### Understand the mapper The mapper's OSM user profile and [HDYC](http://hdyc.neis-one.org) profile gives an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. -Click on the OSM user name in the JOSM History window, and load the OSM user page where you can view the user's `Edits` history, any `Active Blocks`, any other details on the user, and `Diary` entries. +Click on the OSM username in the JOSM History window, and load the OSM user page where you can view the user's `Edits` history, any `Active Blocks`, any other details on the user, and `Diary` entries. You cal also gauge a mapper's experience by looking at the number of project days, type of mapper and other points in [HDYC](http://hdyc.neis-one.org/). @@ -88,25 +88,25 @@ This is where [Changeset Map](http://osmlab.github.io/changeset-map/) comes in h At this point, you know who, when, and which changeset are associated with the problematic change. -Most bad edits are accidental, and the general strategy to respond to such changes is education. Work to share knowledge with the mapper about the mistake and how it can be avoided in future. Communicate feedback through public changeset comments, visible to all, or sometimes direct messages if more direct contact is helpful. This helps build our community and improve the quality of future contributions to the map. +Most bad edits are accidental, and the general strategy to respond to such changes is education. Work to share knowledge with the mapper about the mistake and how they can avoid the mistake in the future. Communicate feedback through public changeset comments, visible to all, or sometimes direct messages if more direct contact is helpful. This helps build our community and improve the quality of future contributions to the map. In cases where it is determined that the intent of the mapper was to damage the map, an urgent response may be required by reverting the change and reporting the issue to an OSM administrator or DWG. ### Communicate -* Leave a comment on the changeset with a description of what was wrong and how it can be fixed. Link to OpenStreetMap wiki or link to help material that is relevant. +* Leave a comment on the changeset with a description of what was wrong and how it can be fixed. Link to an OpenStreetMap wiki or link to help material that is relevant. * If the user does not respond or fix non-urgent issues within a week, alert a nearby active mapper of the issue. * Also look for help on IRC or the local forums or mailing list of the area. ### Repair * For specific malicious changes, consider fixing the issue (and reporting it immediately). -* For a changeset that is wholly bad, revert it. Send a message to the mapper responsible and ask for a description of what happened. -* For simple issues, communicate with the mapper to discuss on how it should be fixed. +* For a changeset that is wholly inaccurate, revert it. Send a message to the mapper responsible and ask for a description of what happened. +* For simple issues, communicate with the mapper to discuss on how they can fix it. #### Revert using the JOSM Plugin -The JOSM [Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter) is a convenient way to revert changes in OpenStreetMap. After every revert, make sure you upload the changes by sharing a changeset comment on why this changeset was reverted. +The JOSM [Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter) is a convenient way to revert changes in OpenStreetMap. After every revert, make sure you upload the changes by sharing a changeset comment on why you reverted the changeset. Reverting changesets can be tricky, and you can unintentionally break things yourself. Attempt to revert a changeset if you are 100% sure that the changeset is bad and if something goes wrong -- you should be able to fix it. @@ -116,7 +116,7 @@ Reverting changesets can be tricky, and you can unintentionally break things you ### Report -* For urgent issues that requires an experienced response, contact the [Data Working Group](http://wiki.openstreetmap.org/wiki/Data_working_group). +* For urgent issues that require an experienced response, contact the [Data Working Group](http://wiki.openstreetmap.org/wiki/Data_working_group). ### How to assess urgency to respond @@ -152,13 +152,13 @@ Many new mappers join OpenStreetMap during HOT Activation. HOT tasks have custom #### Intentional bad edits There are few users who intentionally add bad data to OpenStreetMap which should be reverted immediately. -One such example is shown below. Here the user was intentionally adding family names to towns, buildings, and footpaths. +One such example is shown below. Here the user intentionally added family names to towns, buildings, and footpaths. ![screenshot 2016-05-03 18 47 00](https://cloud.githubusercontent.com/assets/3423533/14984342/d96fe7ee-115f-11e6-9af5-28ac515d9b28.png) #### Undocumented imports -You can import open datasets into OpenStreetMap. Imports should follow the [Import Guidelines](http://wiki.openstreetmap.org/wiki/Import_guidelines) and add proper documentation to the [Imports catalogue](http://wiki.openstreetmap.org/wiki/Import/Catalogue), and use a dedicated import accounts. If any undocumented imports are seen, comment on the changeset to request documentation details. +You can import open datasets into OpenStreetMap. Imports should follow the [Import Guidelines](http://wiki.openstreetmap.org/wiki/Import_guidelines) and add proper documentation to the [Imports catalogue](http://wiki.openstreetmap.org/wiki/Import/Catalogue), and use a dedicated import accounts. If you see any undocumented imports, comment on the changeset to request documentation details. #### Automated edits @@ -167,7 +167,7 @@ Automated edits are changes made to OpenStreetMap with less direct human involve ## Finding suspicious map edits using OSMCha -**[OSM Changeset Analyzer](http://osmcha.mapbox.com/)** or OSMCha is a tool to filter and analyze changesets on OpenStreetMap using the [changeset metadata](https://www.openstreetmap.org/api/0.6/changeset/41775489/download). The tool has a live listing of every changeset on the map, flags potentially suspicious edits and has various filters to find changesets that match a certain criteria. +**[OSM Changeset Analyzer](http://osmcha.mapbox.com/)** or OSMCha is a tool to filter and analyze changesets on OpenStreetMap using the [changeset metadata](https://www.openstreetmap.org/api/0.6/changeset/41775489/download). The tool has a live listing of every changeset on the map, flags potentially suspicious edits and has various filters to find changesets that match certain criteria. ![screenshot 2016-09-06 16 00 06](https://cloud.githubusercontent.com/assets/8921295/18270541/0de8330c-744b-11e6-8582-7e49d6acec9d.png) _Latest changesets listed in OSMCha_ @@ -176,7 +176,7 @@ The changeset is shown with id, date and time of creation, OSM user, creations i ### Filtering changesets -The filters available in OSMCha allow various combination of searches to help find problematic edits. +The filters available in OSMCha allow for a various combination of searches to help find problematic edits. ![screenshot 2016-08-30 16 37 31](https://cloud.githubusercontent.com/assets/8921295/18086930/1a28da0c-6ed0-11e6-8eed-5a0b7ee6cf72.png) _OSMCha filter dialog_ @@ -189,67 +189,59 @@ _Filter based on automatic flagging_ ### Examining the quality of the changeset -OSMCha uses [Changeset map](https://github.com/osmlab/changeset-map/) to visually represent the features that were added, modified and deleted along with tag changes. This help check the quality of the edits for obvious mistakes. +OSMCha uses [Changeset map](https://github.com/osmlab/changeset-map/) to visually represent the features that were added, modified and deleted along with tag changes. This helps check the quality of the edits for obvious mistakes. screenshot 2016-08-22 15 16 17
-_A [changeset](http://osmlab.github.io/changeset-map/#41576998/way/24464264) showing a object that incorrectly made into a circle_ +_A [changeset](http://osmlab.github.io/changeset-map/#41576998/way/24464264) showing an object that incorrectly made into a circle_ ### Workflow to find suspicious changes #### Suspicious editing behavior -**Inexperienced users, deletions and imports** +Inexperienced users, deletions, and imports: + - [Edits from Maps.me editor](http://osmcha.mapbox.com/?editor__icontains=Maps.Me&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) - [Mass deletions](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) - [Mass deletions + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) - [Mass modifications + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=4) - [Mass creations + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2)/ [Possible import](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2) -**Strategy for filters** - -1. iD editor is targeted towards simple editing from new users and any advanced editing happens in JOSM. So, if a mass deletion takes place using iD editor, there is a probability that the user could be inexperienced and the deletions unreasonable. [Example harmful changeset](http://osmcha.mapbox.com/41628531/) - -2. Maps.me users tend to be new to OSM. It is suggested to look for changesets that added unreasonable amount of similar POIs in one area. This could be due to lack experience of the user in mapping coupled with lack of amenities available through the app preset. [Example harmful changeset](http://osmcha.mapbox.com/40927770/) - - Edits from Maps.me editor are automatically uploaded through the app. The app generates an automatic changeset comment based on the kind of amenities that were added. Filtering Maps.me edits with most creations first as sort order helped us in finding most of the bad edits from Maps.me users so far. - -3. This is similar to the first assumption. Mass modifications using iD editor could be a suspicious changeset. Mass modification could be 2 scenarios. When the user modifies tags of a long way(coastline, administrative boundaries,long motorway...) and polygons, these edits are registered to the way/polygon and all the nodes in the feature object. - - The second scenario is when the user changes geometry of an object on OSM, even though only one node is added the whole way/polygon is updated to be modified. [Example harmful changeset](http://osmcha.mapbox.com/41991749/) +Strategy for filters: -4. Mass creations can also be coupled with iD editor in the filters. The idea is to review changesets which have most creations and see if all the editions fall under the [OSM editing standards and conventions](http://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions). [Example harmful changeset](http://osmcha.mapbox.com/38282141/) - -5. Sometimes, we were able to detect suspicious changesets by going through reason filters such as `edited an object with a significant place tag`, 'edited an object with a significant tag', `edited a wikipedia landmark`. [Example harmful changeset](http://osmcha.mapbox.com/38534916/) - -6. Clever acts of vandalism are hard to detect as the changesets may not be big. We can verify these modifications to `name` tags, deletion of tags from [small changesets that are iD editor contributions](http://osmcha.mapbox.com/?modify__lte=50&editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) or through [random search in OSMCha](http://osmcha.mapbox.com/). Example harmful changeset [1](http://www.openstreetmap.org/node/4331919989), [2](http://www.openstreetmap.org/node/4353068192/history). +1. iD editor is targeted towards simple editing from new users, and any advanced editing happens in JOSM. So, if a mass deletion takes place using iD editor, there is a probability that the user could be inexperienced and the deletions unreasonable. [Example of a harmful changeset.](http://osmcha.mapbox.com/41628531/) +2. Maps.me users tend to be new to OSM. It is suggested to look for changesets that add an unreasonable amount of similar POIs in one area. This could be due to a lack experience of the user in mapping coupled with a lack of amenities available through the app preset. [Example of a harmful changeset.](http://osmcha.mapbox.com/40927770/) + - Edits from Maps.me editor are automatically uploaded through the app. The app generates an automatic changeset comment based on the kind of amenities that were added. Filtering Maps.me edits with most creations first as sort order helped us in finding most of the bad edits from Maps.me users so far. +3. This is similar to the first assumption. Mass modifications using iD editor could be a suspicious changeset. Mass modification could be two scenarios: + - When the user modifies tags of a long way (coastline, administrative boundaries, long motorway, etc.) and polygons, these edits are registered to the way/polygon and all the nodes in the feature object. + - When the user changes the geometry of an object on OSM, even though only one node is added the whole way/polygon is updated to be modified. [Example of a harmful changeset.](http://osmcha.mapbox.com/41991749/) +4. Mass creations can also be coupled with the iD editor in the filters. The idea is to review changesets which have most creations and see if all the editions fall under the [OSM editing standards and conventions](http://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions). [Example of a harmful changeset.](http://osmcha.mapbox.com/38282141/) +5. Sometimes, we were able to detect suspicious changesets by going through reason filters such as `edited an object with a significant place tag`, `edited an object with a significant tag`, `edited a wikipedia landmark`. [Example of a harmful changeset.](http://osmcha.mapbox.com/38534916/) +6. Clever acts of vandalism are hard to detect as the changesets may not be big. We can verify these modifications to `name` tags, deletion of tags from [small changesets that are iD editor contributions](http://osmcha.mapbox.com/?modify__lte=50&editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) or through [random search in OSMCha](http://osmcha.mapbox.com/). Examples harmful changesets: [1](http://www.openstreetmap.org/node/4331919989), [2](http://www.openstreetmap.org/node/4353068192/history). #### Suspicious changeset keywords -There are [certain keywords we have stored](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085) to quickly look through changesets that have these words in the changeset comments. For example: Google, Cuss words. +There are [certain keywords we have stored](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085) to quickly look through changesets that have these words in the changeset comments. For example "Google" and any profane language. #### Finding vandalism detected by the community and reverted by DWG -Community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map, community informs DWG, DWG reverts these changesets with a changeset comment. +The community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map then the community will inform DWG and DWG will revert these changesets with a changeset comment. - Using **Keywords** - Using keywords such as `revert`, `cleanup`, `fix` in changeset comment filter, we can find most of the changesets community has taken action on. This list in OSMCha includes fixes, reverts DWG as well. - - Using [**OSM - comments**](https://www.mapbox.com/osm-comments/) - OSM-comments API allows querying changesets with specific parameters - - Link to see changeset comments from all users in OSM - [URL for webview](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) + - Link to see changeset comments from all users in OSM - [URL for web view](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) -Currently there is no direct way of using OSM-Comments-API to see all the changesets on which DWG members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) +Currently, there is no direct way of using OSM-Comments-API to see all the changesets on which DWG members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) **Finding reverts by DWG** ![documentations1](https://cloud.githubusercontent.com/assets/8921295/18270714/0cc820da-744c-11e6-8db8-71421c956e07.gif) _Finding DWG reverts using OSMCha_ - - OSMCha allows us to query changesets from specific users. - -- We can query all changesets from revert accounts of DWG members such Woodpeck_repair, pnorman_mechanical etc. \ No newline at end of file +- We can query all changesets from revert accounts of DWG members such `Woodpeck_repair`, `pnorman_mechanical`, etc. \ No newline at end of file From acb7e37f41a4cc7f86cec789f1a2f896a29c813e Mon Sep 17 00:00:00 2001 From: Sajjad Anwar Date: Fri, 23 Sep 2016 18:37:24 +0200 Subject: [PATCH 19/66] expand dwg --- .../_posts/0000-01-01-validating-osm.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/validating-osm/_posts/0000-01-01-validating-osm.md b/validating-osm/_posts/0000-01-01-validating-osm.md index 2f1823e..1074763 100644 --- a/validating-osm/_posts/0000-01-01-validating-osm.md +++ b/validating-osm/_posts/0000-01-01-validating-osm.md @@ -90,7 +90,7 @@ At this point, you know who, when, and which changeset are associated with the p Most bad edits are accidental, and the general strategy to respond to such changes is education. Work to share knowledge with the mapper about the mistake and how they can avoid the mistake in the future. Communicate feedback through public changeset comments, visible to all, or sometimes direct messages if more direct contact is helpful. This helps build our community and improve the quality of future contributions to the map. -In cases where it is determined that the intent of the mapper was to damage the map, an urgent response may be required by reverting the change and reporting the issue to an OSM administrator or DWG. +In cases where it is determined that the intent of the mapper was to damage the map, an urgent response may be required by reverting the change and reporting the issue to an OSM administrator or Data Working Group. ### Communicate @@ -224,24 +224,24 @@ Strategy for filters: There are [certain keywords we have stored](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085) to quickly look through changesets that have these words in the changeset comments. For example "Google" and any profane language. -#### Finding vandalism detected by the community and reverted by DWG +#### Finding vandalism detected by the community and reverted by Data Working Group -The community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map then the community will inform DWG and DWG will revert these changesets with a changeset comment. +The community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map then the community will inform Data Working Group and Data Working Group will revert these changesets with a changeset comment. - Using **Keywords** - - Using keywords such as `revert`, `cleanup`, `fix` in changeset comment filter, we can find most of the changesets community has taken action on. This list in OSMCha includes fixes, reverts DWG as well. + - Using keywords such as `revert`, `cleanup`, `fix` in changeset comment filter, we can find most of the changesets community has taken action on. This list in OSMCha includes fixes, reverts Data Working Group as well. - Using [**OSM - comments**](https://www.mapbox.com/osm-comments/) - OSM-comments API allows querying changesets with specific parameters - Link to see changeset comments from all users in OSM - [URL for web view](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) -Currently, there is no direct way of using OSM-Comments-API to see all the changesets on which DWG members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) +Currently, there is no direct way of using OSM-Comments-API to see all the changesets on which Data Working Group members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) -**Finding reverts by DWG** +**Finding reverts by Data Working Group** ![documentations1](https://cloud.githubusercontent.com/assets/8921295/18270714/0cc820da-744c-11e6-8db8-71421c956e07.gif) -_Finding DWG reverts using OSMCha_ +_Finding Data Working Group reverts using OSMCha_ - OSMCha allows us to query changesets from specific users. -- We can query all changesets from revert accounts of DWG members such `Woodpeck_repair`, `pnorman_mechanical`, etc. \ No newline at end of file +- We can query all changesets from revert accounts of Data Working Group members such `Woodpeck_repair`, `pnorman_mechanical`, etc. \ No newline at end of file From 9374a09cf01ee6f4fc8d952ea30690325ad02de5 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Mon, 24 Oct 2016 15:22:25 +0530 Subject: [PATCH 20/66] contents of navigation guide --- .../_posts/0000-01-01-introduction.md | 86 ++++++ ...01-02-modeling-roads-for-map-navigation.md | 87 ++++++ .../0000-01-03-road-features-mapping-guide.md | 216 +++++++++++++++ ...dding-turn-restrictions-using-mapillary.md | 251 ++++++++++++++++++ ...g-guide-for-adding-exit-and-destination.md | 135 ++++++++++ ...uide-for-adding-turn-lanes-from-imagery.md | 248 +++++++++++++++++ .../0000-01-07-resources-and-references.md | 49 ++++ 7 files changed, 1072 insertions(+) create mode 100644 mapping-to-improve-navigation/_posts/0000-01-01-introduction.md create mode 100644 mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md create mode 100644 mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md create mode 100644 mapping-to-improve-navigation/_posts/0000-01-04-mapping-guide-for-adding-turn-restrictions-using-mapillary.md create mode 100644 mapping-to-improve-navigation/_posts/0000-01-05-mapping-guide-for-adding-exit-and-destination.md create mode 100644 mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md create mode 100644 mapping-to-improve-navigation/_posts/0000-01-07-resources-and-references.md diff --git a/mapping-to-improve-navigation/_posts/0000-01-01-introduction.md b/mapping-to-improve-navigation/_posts/0000-01-01-introduction.md new file mode 100644 index 0000000..5e42863 --- /dev/null +++ b/mapping-to-improve-navigation/_posts/0000-01-01-introduction.md @@ -0,0 +1,86 @@ +--- +title: Introduction +--- + +The most basic use of a map is to find out where one is located. After that, one usually wants to use the map to find the best route to another location. On a [digital map](https://en.wikipedia.org/wiki/Digital_mapping), this is usually provided with [turn by turn navigation](https://en.wikipedia.org/wiki/Turn-by-turn_navigation) using a [navigation device](https://en.wikipedia.org/wiki/GPS_navigation_device). + +![navigation_optimized](https://cloud.githubusercontent.com/assets/13744156/18119269/76493c6c-6f77-11e6-8c18-a1daf7845f0b.gif) +_Let the computer find the best route for you!_ + +## Components of map navigation + +A navigations system has user facing components that interact with the user and back end components that computes the best route based on the user input and available data. In this guide we will focus on the back end components that rely on map data. + +**User facing components** +- User interface controls for setting the the origin and destination +- Map display that visually represents the route to take +- Turn by turn instructions that accurately describe the navigation maneuvers at the appropriate time +- Route status that includes current progress and the estimated time of arrival (ETA) at the destination + +**Back end components** +- A navigation profile that describes the mode of transport to use for the routing algorithm (eg. truck, cycle or foot) +- A route finder that finds the best possible route between the origin and destination for the selected navigation profile +- A guidance system that converts the route into instructions for turn by turn navigation + +### Navigation profile + +The navigation profile accurately describes the preferred types of roads to take based on the mode of transport used. A walking profile will have a fairly constant walking speed on any type of road, while a car profile will have avery high traveling speed on a motorway and will be much slower on a residential road. This has a large influence on the route finder. + +![screenshot_20160831-124644](https://cloud.githubusercontent.com/assets/8401827/18120537/b392baac-6f7d-11e6-9e36-480b3145c429.png) + +*Different routing profiles: cars, walking, bicycle.* + +### Routing + +[Routing](http://wiki.openstreetmap.org/wiki/Routing) is the process of selecting the best path in a network interconnected of roads on the map. Every road segment on the map has a traveling speed calculated based on various road factors, and the fastest and safest route is selected from all possible combinations. + +![](https://farm4.staticflickr.com/3814/12241013316_df99a4ff83_o.png)
+_Finding the route between two points involves complex calculations on a [routing graph](https://www.mapbox.com/blog/smart-directions-with-osrm-graph-model/)_ + +The calculation of an accurate route depends on a variety of factors which are taken into account by the routing algorithm: + +* Personal factors: fastest route, most scenic route, quietest route, shortest route, facilities needed, toll rates +* Vehicle factors: mode of transport, physical category of vehicle, optimum traveling speed, riding surface requirements, fueling requirements +* Route factors (static): classification of road, access restrictions, speed limits, turn restrictions, oneway rules, number of lanes +* Traffic factors (dynamic): traffic conditions, traffic signal cycle duration, weather conditions +* Riding surface factors: surface material, smoothness, barriers, speed breakers, road width, lane width, age + +### Guidance + +![](https://cloud.githubusercontent.com/assets/12932279/16989362/402b3f44-4e94-11e6-8e8a-a60cf0b08705.png) +_A route is converted into a series of easy to follow instructions for the user_ + +Route guidance is used to lead a person through the determined path. Once the routing algorithm determines the best path, that route is converted into a set of human-readable instructions known as guidance. The guidance represents the street names, the turn lanes marked on the roads, exit numbers, and destinations shown on sign boards. Accurate and relevant guidance can greatly enhance the user experience of using the map for navigation. + +## Navigating the future + +Providing accurate navigation using maps is dependent on having detailed and updated data about the world. The world is transforming every second and the next generation of navigation will need to have the latest information about the world that will come from various sources. + +### Telemetry + +screenshot 2016-09-15 21 27 43 +_Telemetry traces of Strava users from [Strava Globalheatmap](http://labs.strava.com/heatmap/#14/-74.02871/40.70159/blue/both)_ + +Telemetry is the remote collection of data which can be physical, environmental or biological. Most internet and GPS enabled phones collect location and other environmental data and reports it to a central service that can aggregate the data to determine traffic conditions on a road. + + +### Forward facing cameras & Street-view + +![untitled2](https://cloud.githubusercontent.com/assets/126868/18557457/a667474c-7b8c-11e6-844b-e308c650a8b1.gif) +_Crowdsourced streetview photographs from [narrow alleys in India using Mapillary](https://www.mapillary.com/app/?lat=23.018631999999997&lng=72.595325&z=17&pKey=4tjlrGmABA2sxmLLmAIq9Q&focus=photo)_ + +Street view images from dashcams, mounted cameras in vehicles using apps gives highly detailed 360° view of streets. This can help detect traffic signage, access restrictions, traffic signals, road markings to help add and confirm ground features into a map. Opensource street view photos include [Mapillary](https://www.mapillary.com/) and [OpenStreetView](http://openstreetview.com/). + +### Live Aerial & Drone Imagery + +screenshot 2016-09-15 21 34 33
+_High resolution imagery captured from [UAVs in Srilanka](https://www.mapbox.com/blog/sri-lanka-drone-imagery/)_ + +[Aerial imagery](https://en.wikipedia.org/wiki/Aerial_photography) using drones can capture the changing surface of the earth at a much higher resolution and lower cost compared to traditional satellite imagery that is expensive to acquire and are updated less frequently. + +### Machine learning and image recognition + +![untitled2](https://cloud.githubusercontent.com/assets/126868/18557642/4fba4e8e-7b8d-11e6-85fb-c30092aac39b.gif)
+_Automatic image segmentation by [Mapillary](http://blog.mapillary.com/update/2016/05/19/austria.html)_ + +Advances in [machine learning](https://en.wikipedia.org/wiki/Machine_learning) opens up opportunities to automate manual tasks like [digitization of roads from satellite](http://stateofthemap.us/2016/skynet/) imagery and can accelerate the creation and maintenance of map data. \ No newline at end of file diff --git a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md b/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md new file mode 100644 index 0000000..59cb86b --- /dev/null +++ b/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md @@ -0,0 +1,87 @@ +--- +title: Modeling Roads for Map Navigation +--- + +## Data influence map +A navigation map is influenced by several road characteristics, such as the turn restrictions, improper way of road tracing and road classification. The most important ones among those are: + +### Road geometry +Roads are the main features that are used for rendering a route in all navigational applications. Correct road mapping leads not only to the well-looking map but also to better navigation experience. With the change in the shape of the traced road, the distance covered will be altered which affects the route. The common approach for road mapping is to trace roads following the center-line from satellite imagery. + +![road_with_two_lanes](https://cloud.githubusercontent.com/assets/369696/13230189/1bc4b308-d9ad-11e5-88b7-f85fcd290926.png) + +*Roads on satellite imagery* + +### Road connectivity / topology: +If you want to travel from point A to point E as shown in the below image, you can either travel from `A to B, B to C and then C to E` or `A to B, B to D and then D to E`. + +![screen shot 2016-08-30 at 6 51 58 pm](https://cloud.githubusercontent.com/assets/8401827/18090553/e4e4eabc-6ee2-11e6-9908-8c9064c833af.png) + +But, if you have a restriction to enter D from A, the only possible route will be `A to B, B to C and then C to E`. This is where connectivity plays a major role in deciding the final route. + +### Road attributes / properties: +If `A to C` is a primary road which is crossing through a service road `B to D` and you want to travel from `A to E`, the navigation map comes up with the route traveling from `A to B, B to C and then C to E` and completely avoids `A to B, B to D and then D to E` because the travel on Primary road is much efficient than a narrow service road. This is how the attributes / properties with which the road is assigned with plays a crucial role in deciding the final route. + +![screen shot 2016-08-30 at 8 30 14 pm](https://cloud.githubusercontent.com/assets/8401827/18094299/9d9f5454-6ef0-11e6-85de-4f74a43d5657.png) + +## OpenStreetMap data model: + +The OpenStreetMap data model consists of nodes, ways, relations, and tags. A detailed description of the data model can be found in the [The OpenStreetMap Data Model](https://github.com/mapbox/mapping/wiki/The%20OpenStreetMap%20Data%20Model) guide. + +Navigation data is similarly a combination of nodes, ways, relations, and tags. Some of the examples are illustrated below: + +### Examples + +* Nodes: + - Exit numbers: + +![screen shot 2016-08-30 at 5 20 44 pm](https://cloud.githubusercontent.com/assets/13744156/18088263/517c2cf0-6ed7-11e6-8485-2d2761c42e84.png) + +* Ways: + - Highway=* + +![screen shot 2016-08-30 at 6 17 55 pm](https://cloud.githubusercontent.com/assets/13744156/18089616/6d060d0e-6ede-11e6-829d-47fc464a53a1.png) + +*An way tagged with highway=secondary tag* + +* Relations: + - Turn restrictions are a combination of nodes, ways, tags, and relations. It consists of `from way` `via node` and `to way`, tied together by a `restriction=*` relation. + + +![tr_relation](https://cloud.githubusercontent.com/assets/13744156/18089141/0c296c9e-6edc-11e6-916f-716e41c9f685.gif) + +* Tags: All the navigation features are differentiated and defined based on how they are tagged. Tags can be on any element: on nodes, ways, and relations. + +Examples are: `destination=*`, `ref=*`, `turn:lanes=*`, `restriction=*`, etc. + +## Tracing roads + +Before tracing, we need to inspect the start and endpoints of the road segment. We need to identify the road direction, general numbers of lanes and the places where there are extra lanes. Based on this we choose our strategy for tracing. + +We are not able to draw a road on its center line, especially if roads join/fork or the number of lanes change. Imagine two roads which join: how would you draw the OSM-way around the point where the roads join? + + ![center_line](https://wiki.openstreetmap.org/w/images/4/47/Lane_Placement_2.png) + + _Center line tracing_ + + ![main_direction](https://wiki.openstreetmap.org/w/images/e/e4/Lane_Placement_3.png) + + _Tracing based on road direction_ + +### Tracing roads with more than two lanes + +There are two cases: +- Dual carriageway roads + + ![dual_carriageway_road](https://cloud.githubusercontent.com/assets/369696/13230427/fe21579c-d9ad-11e5-86ba-38107d469c54.png) + +These are bidirectional roads which have a physical separation between the lanes in both the directions. Both the ways will be counted for lanes and will be tagged with `lanes=*`. Dual carriageways are always `oneway` roads. + +![motorway](https://cloud.githubusercontent.com/assets/369696/13231932/5b417e00-d9b5-11e5-854e-dbed2d209d7c.png) +*Placement of nodes of the lines in each direction, opposite to each other* + +- Roads which carry traffic in both directions (Bidirectional roads) + + ![bidirectional_road](https://cloud.githubusercontent.com/assets/369696/13230341/9f9db6c0-d9ad-11e5-9f5d-53dd80b40f67.png) +*Road carrying traffic in both directions* + diff --git a/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md b/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md new file mode 100644 index 0000000..f8262e3 --- /dev/null +++ b/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md @@ -0,0 +1,216 @@ +--- +title: Road Features Mapping Guide +--- + +*Detailed guide mapping features for navigation on the OpenStreetMap project. Before you start, please read the guide on [Mapping with OpenStreetMap](https://www.mapbox.com/mapping/)* + +[Query OpenStreetMap for Navigation Data via Overpass](http://overpass-turbo.eu/s/iyB) + +## Routing features + +These are features that help the routing engine find the safest and fastest route between two points. + + +### 1. Functional Road Class + +* `highway=*` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:highway) + +Roads are categorized according to its order of importance. They are tagged with the `highway=*`. The general order of importance for way types are: + +``` xml +highway= motorway > trunk > primary > secondary > ... > living streets > ... > footway +``` +![screen shot 2016-08-29 at 1 50 04 pm](https://cloud.githubusercontent.com/assets/13744156/18045336/ff8f31ea-6def-11e6-8692-bb4e082b94b8.png) + +*`highway=primary` in San Francisco* + +The value of the key helps show the importance of the highway within the road network as a whole. The importance ranges from the most important `motorway` to the least important `service`. The routing engine takes into account this importance of classification when determining optimum routes. + +Road classification may varies from country to country. The country specific use cases can be found in detail on separate wiki pages. For example, when mapping roads in India, the local community refer to the [India road tagging wiki](http://wiki.openstreetmap.org/wiki/India:Tags/Highway). + +Examples: +* [US roads classification](http://wiki.openstreetmap.org/wiki/United_States_Road_Classification) +* [UK roads classification/numbering](https://en.wikipedia.org/wiki/Great_Britain_road_numbering_scheme) + +For an example of an area with a good concentration of different classes of roads on OpenStreetMap, look at [San Francisco](https://www.openstreetmap.org/#map=14/37.7788/-122.4375) area. This [osm query](http://overpass-turbo.eu/s/i4y) can be used to extract and gather numbers of all the highways present in a given bounding box on OpenStreetMap. + +[Department of Transportation](https://www.fhwa.dot.gov/about/webstate.cfm) websites and [wikipedia](https://en.wikipedia.org/wiki/United_States_Numbered_Highways) are some of the primary sources for highway information. + +### 2. Oneways + +* `oneway=yes` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:oneway) + +Oneways generally refer to road segments which allow traffic in only one direction. There are also streets which have oneway characteristics for only on certain times of the day to regulate traffic. + +![screen shot 2016-08-29 at 5 47 47 pm](https://cloud.githubusercontent.com/assets/13744156/18051463/5fdc162c-6e12-11e6-8984-c48da11bf73f.png) + +*`oneway=yes` shown in Mapillary* + +The best source of mapping oneways are again street level photos. + +[San Francisco](https://www.openstreetmap.org/#map=12/37.7574/-122.4845) is one area which has been well mapped for oneways in OpenStreetMap. This [overpass query](http://overpass-turbo.eu/s/i50) can be used to extract oneways from OpenStreetMap data. + +### 3. Turn-Restrictions + +* `type=restriction` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Relation:restriction) +* [Mapping guide](/mapping/mapping-to-improve-navigation/mapping-guide-for-adding-turn-restrictions-using-mapillary/) + +`type=restriction` is added to a relation in OpenStreetMap which is used to describe turn restrictions at junctions. The relation has a set of tags that describes the type of restriction, for example. `no_left_turn`, `no_right_turn`, `no_u_turn`, etc. These are traffic signs at junctions and this information must be present on the map to find the best route by the routing engine while planning a route. + +![screen shot 2016-03-08 at 8 05 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604633/ad8bff4a-e569-11e5-9198-3ac9c88e5619.png) + +*Turn restriction denoting `no left turn` along with conditions: opening and closing times* + +The main resource for turn restriction data is [street view level images](https://www.mapbox.com/blog/safer-market-street/), local mapping drives, [DOT websites](http://www1.toronto.ca/wps/portal/contentonly?vgnextoid=83f6e69ae554e410VgnVCM10000071d60f89RCRD) + +![turn_restriction](https://cloud.githubusercontent.com/assets/13744156/18047415/7d9254c8-6dfa-11e6-94e6-9d85b58627c1.jpg) +*turn restriction which denotes `no right turn` at the junction* + +[San Francisco](https://www.openstreetmap.org/#map=13/37.7696/-122.4891) in OpenStreetMap has an excellent coverage of turn by turn restrictions at junctions. This [overpass query](http://overpass-turbo.eu/s/i4G) can be used to extract current turn restriction in a bounding box. + +### 4. Speed limits + +* `maxspeed=60` or `maxpseed=40 mph` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:maxspeed) + +The `maxspeed=*` tag defines the maximum legal speed limit for general traffic on a particular road, railway or waterway. The max speed values will be interpreted as kilometers per hour by default. The `maxspeed=*` is an important part of routing as it is used in determining the shortest time taken by a specific route to reach a destination. In the case of two routes, the one with the shortest time (higher maxspeed) and shortest distance will be considered as the optimum route. + + +![maxspeed](https://cloud.githubusercontent.com/assets/13744156/18046639/6602224c-6df6-11e6-8884-18a58bf4835a.jpg) + +*Maxspeed sign shown in Mapillary* + +The main data sources for detecting maxspeed signs are: [street view photos](https://www.mapbox.com/blog/mapillary-mapping/), [wikipedia](https://en.wikipedia.org/wiki/Speed_limits_in_Canada), [DOT documents](http://www.qld.gov.au/transport/safety/rules/speed-limits/index.html). + +The `maxspeed=*` data on OpenStreetMap (for example, in [London](https://www.openstreetmap.org/#map=14/51.5059/-0.1061)) in an area can be extracted by this [overpass query](http://overpass-turbo.eu/s/i4z). + + +### 5. Access-Restrictions + +* `access=*` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:access) + +Apart from turn restrictions, there are access restrictions for different parts of highways. Some of these tags are `access=no`, `access=private` etc which will end up altering the route to be taken during the journey. For more information on the various kinds of `access=*` tags take a look at [Key:access](http://wiki.openstreetmap.org/wiki/Key:access) and [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions) and [access restrictions](http://wiki.openstreetmap.org/wiki/OpenStreetMap_tags_for_routing/Access-Restrictions) + +![749px-mutcd_r5-7](https://cloud.githubusercontent.com/assets/13744156/18048743/b688e696-6e01-11e6-80ae-e65ce6743830.png) + +*An `access=no` for non-motorized traffic, ends up altering the route for bicycle profiles, source: US MUTDC* + +All the `access=private` tags on OpenStreetMap ways, which will not allow that segment of the way to be used in a route can be extracted from this [overpass query](http://overpass-turbo.eu/s/i4J). An example of well-mapped access restrictions in OpenStreetMap can be found in [London](https://www.openstreetmap.org/#map=13/51.5061/-0.1366). + +The sources for mapping access restrictions in OpenStreetMap are: [street view photos](http://blog.mapillary.com/update/2016/05/24/use-mapillary-editing-OpenStreetMap.html), local mapping drives. + +### 6. Traffic signals + +Traffic signals such as: `highway=traffic_signals`, `highway=stop` or `barrier=toll_booth` as well as `traffic_calming=*` are considered during routing. The `type=restriction` more commonly referred to as **turn restrictions** are traffic signage which prohibits certain turns in intersections are also a crucial part of a great `routing` engine. + +More details on mapping `traffic signals` for cars and pedestrians can be found in the [OpenStreetMap wiki](http://wiki.openstreetmap.org/wiki/Tag:highway%3Dtraffic_signals). + +Street view photos from Mapillary, local mapping drives using [OpenStreetMap tracker](http://wiki.openstreetmap.org/wiki/OpenStreetMapTracker_(Android)) can be used as sources to map traffic signals in OpenStreetMap. + +![800px-led_traffic_lights](https://cloud.githubusercontent.com/assets/13744156/18049581/cc237796-6e06-11e6-8d51-b8d446b2c3dc.jpg) + +*Traffic signal in a junction* + + +## Guidance features + +## 1. Exit & destination signs + +**What are exit numbers?** + * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. + + ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) + +**Different tags for exit numbers:** +* `ref=*` is used when the exit has a specific number assigned to it. +* `noref=yes` is used when the exit doesn't have any official number assigned to it. + +**What are destination tags?** + +* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. +* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. + +![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) + +#### Different tags for destinations: +* `destination` tag refers to the place that the way exiting from the freeway leads to. +* `destination:ref` is the reference of the roads directly ahead. +* `destination:ref:to` is to specify the reference of a major highway ahead. +* `destination:street` refers to the main street the way exiting from the freeway leads to. + +An example of a place with good exit/destination coverage in OpenStreetMap is [Ottawa, Canada](http://www.openstreetmap.org/#map=11/45.4283/-75.8331). These overpass queries for [destination](http://overpass-turbo.eu/s/i61) and [exit numbers](http://overpass-turbo.eu/s/i78) can be used to extract exit/destination data from OpenStreetMap. + +The [detailed guide](/mapping/mapping-to-improve-navigation/mapping-guide-for-adding-exit-and-destination/) on adding exit and destination numbers can be followed for adding exit/destinations. This guide is specifically focused on North America (US/Canada) for now. + +### 2. Turn Lanes + +As discussed in `Modeling Roads for navigation` page, there are two types of roads: unidirectional and bidirectional. `lanes=*` tag is used to count the number of lanes in both these type of roads. + +To set number of [lanes](http://wiki.openstreetmap.org/wiki/Key:lanes) for roads which carry traffic in both directions use [`:backward` and `:forward` suffixes](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right#Forward_and_backward) + +`Forward` means the direction in which the way is drawn in OpenStreetMap, while `backward` means the opposite direction. + +``` xml +Example: + highway=tertiary + lanes=5 + lanes:forward=3 + lanes:backward=2 +``` + +In the image below, the number of lanes is two - `lanes=2`. Orange line is the center line of bidirectional way which is the main way direction. When the extra lane starts in a bidirectional way, that segment is tagged as `lanes=3`+`lanes:forward=2`+`lanes:backward=1`. Optionally, we specify [placement](https://wiki.openstreetmap.org/wiki/Proposed_features/placement) of the lanes relative to the way. + + ![residential_road_2](https://cloud.githubusercontent.com/assets/369696/13228435/ae570094-d9a4-11e5-9f3c-4737112a7932.png) + +The below image have two tagging variants: + 1. `lanes=2` - 1 lane for each direction, or + 2. `lanes=3` - denote middle lane for left turn as (:point_left: _this is [discussed](http://wiki.openstreetmap.org/wiki/Proposed_features/Suffix_both_ways)_) + + ``` +highway=residential +lanes=3 +lanes:forward=1 +lanes:backward=1 +lanes:both_ways=1 +turn:lanes:both_ways=left + ``` + ![residential_road_3](https://cloud.githubusercontent.com/assets/369696/13229045/ab01d6f0-d9a7-11e5-8d8a-1fe5518c84a5.png) + + IN case the number of lanes is even but numbers of lanes for each direction not equal. :point_down: + + ![trunk_link](https://cloud.githubusercontent.com/assets/369696/13229897/b09a811c-d9ab-11e5-935e-25906c94585b.png) + +[Turn lanes](http://wiki.openstreetmap.org/wiki/Key:turn#Turning_indications_per_lane) have an influence on the path finding and are one of the most vital components for proper guidance. Choosing the correct turn lane can have a big influence in navigation. Oftentimes, they only help to illustrate a turn better but other times, they are vitally important. In guidance, the aim is to provide a set of instructions, like keep right or keep left by describing the optimum route found by the routing algorithm to a driver. + +![screen shot 2016-03-08 at 7 51 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604319/236e84dc-e568-11e5-850a-cf398719db11.png) + +*How a driver views turn lanes from the car. For a single direction way, it will be tagged `turn:lanes=left|left;through` while for a bidirectional way it will be tagged `turn:lanes:forward/turn:lanes:backward=left|left|through` depending upon OpenStreetMap way direction* + +There are three turn lanes tags in OpenStreetMap: + +``` xml +turn:lanes=* +turn:lanes:forward=* +turn:lanes:backward=* +``` + +Turn lanes can be mapped from high-resolution satellite imagery sources and street level photos. An example of the high density turn lane area in OpenStreetMap is [Los Angeles](https://www.openstreetmap.org/#map=11/33.9883/-118.3303). This [overpass query](http://overpass-turbo.eu/s/ipk) can be used to extract turn lanes data from OpenStreetMap + +[Mapping guide for mapping turn lanes](/mapping/mapping-to-improve-navigation/mapping-guide-for-adding-turn-lanes-from-imagery/): This is a detailed mapping guide for adding turn lanes in general with specific focus on the US. It will be updated as more and more countries are mapped for lane information in OpenStreetMap. + + +-- + +The other important attributes in besides `turn:lanes` and `exit/destination` data required to provide the better guidance using OpenStreetMap data are: +``` xml +lanes=* +name=* +ref=* +relation:route +``` + +Information for [lanes](http://wiki.openstreetmap.org/wiki/Key:lanes), [highway names](http://wiki.openstreetmap.org/wiki/Highways), [highway ref](http://wiki.openstreetmap.org/wiki/Key:ref) and [relation:route](http://wiki.openstreetmap.org/wiki/Relation:route) can be found in their respective OpenStreetMap wikis. \ No newline at end of file diff --git a/mapping-to-improve-navigation/_posts/0000-01-04-mapping-guide-for-adding-turn-restrictions-using-mapillary.md b/mapping-to-improve-navigation/_posts/0000-01-04-mapping-guide-for-adding-turn-restrictions-using-mapillary.md new file mode 100644 index 0000000..f27a2e5 --- /dev/null +++ b/mapping-to-improve-navigation/_posts/0000-01-04-mapping-guide-for-adding-turn-restrictions-using-mapillary.md @@ -0,0 +1,251 @@ +--- +title: Mapping Guide for adding Turn Restrictions using Mapillary +--- +## What are turn restrictions? + +A turn restriction at a junction is represented by a [relation](http://wiki.openstreetmap.org/wiki/Relation) that has a set of tags describing the type of turn restriction. Turn restrictions, like `No-left-turn` and `No-U-turn`, regulate traffic flow at intersections and accurately mapping them is critical for calculating valid routes on a map. + +![image](https://cloud.githubusercontent.com/assets/3423533/15504805/5d678d70-21de-11e6-8290-d20db2380d4d.png) + +## Traffic signs to be added + +Refer to the table given below to spot/match the traffic sign in the Mapillary image against the list of traffic signs and it also consists of the OSM tags: + + +Symbol | Description | OSM Tag | Node/Way/Relation | +------ | ----------- | ------- | ----------------- | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a9/MUTCD_R3-27.svg/80px-MUTCD_R3-27.svg.png)| No straight through | restriction=no_straight_on | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/8/8f/MUTCD_R3-1.svg/80px-MUTCD_R3-1.svg.png)| No Right Turn | restriction=no_right_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/MUTCD_R3-2.svg/80px-MUTCD_R3-2.svg.png)| No Left Turn | restriction=no_left_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/2/2b/MUTCD_R3-3.svg/80px-MUTCD_R3-3.svg.png)| No Turns | restriction=only_straight_on | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/d/d1/MUTCD_R3-4.svg/80px-MUTCD_R3-4.svg.png)| No U-turn | restriction=no_u_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a1/MUTCD_R3-18.svg/80px-MUTCD_R3-18.svg.png)| No Left or U-turn | restriction=no_left_turn; restriction=no_u_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | + + _The last two columns of the table enlists the correct tagging convention for adding the traffic data to OpenStreetMap._ + + +## Using OSM Navigation Map + +The [Navigation map](http://mapbox.github.io/osm-navigation-map/) helps us in recognizing the detected signage overlay from Mapillary on the map. These signage are represented using small circles in 3 colours: + +- **Green** - to be validated +- **Blue** - Reviewed and found valid +- **Yellow** - Reviewed and found redundant +- **Red** - Reviewed and found invalid + +When we click on the green circle, the area is automatically opened in JOSM and popup to select the review is opened in the Navigation map. The same can be opened in iD editor by clicking on **Edit Map** button on top right of the popup. Once done with the review, please add your OSM username. + +![](https://cloud.githubusercontent.com/assets/126868/16987647/ffa78c4a-4eaa-11e6-8bfd-b509b20e482b.gif) + + +## Mapping turn restrictions with iD editor + +The new version of iD, the web editor for OpenStreetMap, makes it even simpler to add turn restrictions to OpenStreetMap. + +### Adding Absolute Turn Restriction: +![epl4xsg](https://cloud.githubusercontent.com/assets/17887418/17285386/fe7453f6-57df-11e6-9d1d-e65ba060bc0b.gif) + +### Adding Conditional Turn Restriction: + ![conditional tr](https://cloud.githubusercontent.com/assets/17887418/17285391/055b6240-57e0-11e6-9c9f-16880b5c6cd2.gif) + +#### Mapillary overlay and Traffic Sign Overlay: + Mapillary has an efficient tool in iD that helps in seeing detected restrictions. Here's how you enable it: + + ![traffic overlay mapillary](https://cloud.githubusercontent.com/assets/17887418/17285393/069163a8-57e0-11e6-9564-293d91b276bc.gif) + +#### Pain Points in adding Turn Restrictions in iD editor: +1. iD editor provides no way of adding a `no_u_turn` restrictions via way. If there is a via way `no_u_turn`, you have to add it using JOSM editor. + + ![image](https://cloud.githubusercontent.com/assets/17887418/17285567/1a145830-57e1-11e6-8e2f-0581bc16695e.png) + +2. In certain cases, adding [no_u_turn turn via node](https://github.com/mapbox/mapping/issues/213#issuecomment-234221535) is also not possible. For such cases, it is better to add it using JOSM. + + +# Mapping turn restrictions with JOSM + +In order to be able to map traffic data easily, there are some plugins that JOSM needs to be configured with: + + - **Plugins to be downloaded**: + - [Mapillary plugin for JOSM](http://blog.mapillary.com/update/2015/06/25/josm-mapillary.html): This plugin allows the user to view mapillary images in JOSM. + - [Turn restrictions plugin for JOSM](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Turnrestrictions): This plugin allows to add turn restrictions to the selected roads with ease. + + ![mapi_plugins](https://cloud.githubusercontent.com/assets/1933377/11438854/cf4768fa-951d-11e5-819a-737d2e03342c.gif) + + - **Map-paint styles to be added**: + - traffic_signs: It displays all the existing traffic signs that have been already mapped on OSM. + + ![mapi_paint](https://cloud.githubusercontent.com/assets/1933377/11442184/3493f780-9539-11e5-985a-ac6a9095dcee.gif) + +## Guide to use the mapillary and turn restriction plugins + + **Using the Mapillary plugin** + + - The Mapillary imagery can be added by clicking on `imagery -> Mapillary` in JOSM. This will add the mapillary layer + over the dataset layer. + - The explanation for how the plugin works can be found [here](http://blog.mapillary.com/update/2015/06/25/josm-mapillary.html). + + **Note**: Every time a new data layer is added, you need to delete the existing **Mapillary layer** and add a new one + +**Using the turn restriction plugin** + - The explanation for how the turn restriction plugin works + can be found [here](http://overpass-turbo.eu/s/gTO). + + +## Start mapping Turn Restrictions + +- This **[Over-pass query](http://overpass-turbo.eu/s/grv)** can be used to get the current count of turn-restrictions present in a city that one is going to work on. This will help us in determining the current state of restrictions and further help in calculating the number of restrictions added by the team. + +**Note:** Change the city name in the above query + +- Use the **[navigation data coverage on OSM](http://mapbox.github.io/osm-navigation-map/#9.56/37.8188/-122.5575) map** to spot the Mapillary signage detections. +- Turn on the `Turn Restrictions`, `Oneways` and `Mapillary Street Photos` layers in the above map +- Click on the turn-restriction traffic symbols detected by Mapillary (which are denoted by green dots on the map) for it to open in JOSM. + + ![navigation](https://cloud.githubusercontent.com/assets/4470913/15466843/26bd5588-20f9-11e6-9eaa-0126e5c83c39.gif) + +- In the Mapillary layer in JOSM, detected traffic signs are represented by a tiny `red triangle` next to the green arrow. Please note that this layer might not be up-to-date. + + ![screen shot 2015-11-27 at 1 41 55 pm](https://cloud.githubusercontent.com/assets/4470913/11436699/1fa70b72-950d-11e5-8e05-9e09013c1f64.png) + +- Probe the previous and next images as well as the satellite imagery data to get a clear idea of the surroundings and then compare them with the existing Mapillary image to find the exact location of the `traffic-sign`. + + ![turn_res](https://cloud.githubusercontent.com/assets/1933377/11443497/a109430c-9543-11e5-8ef9-6907269d6145.gif) + +- Be cautious while adding an `U-turn` via a way in OSM, here is how you add it: + - Select the participating ways + - Go to `Presets -> Relations -> Turn Restrictions` + - Select `no_u_turn` in the `Restriction` field from the drop-down and click on `New Relation` + - In the `Members` section add the respective roles for all the ways enlisted + + + ![u-turn](https://cloud.githubusercontent.com/assets/4470913/15538899/ae22ff9c-229c-11e6-8d82-08b9e18c5540.gif) + + + **Note** + - To get a better idea about the area/road and to see the clear image, always inspect multiple consecutive images. + - With the help of the plugins, look for **traffic restrictions icons** at junctions which are already present on the road/area. + - We should avoid adding `turn restriction` to roads that are leading to one-ways going in the opposite direction, like the example below. It will only result in redundant data: + + ![screen_shot_2015-11-30_at_11_36_26_pm](https://cloud.githubusercontent.com/assets/4470913/11480317/deeac0c6-97bc-11e5-8d0a-852e3ae2f69f.png) + _Here we should avoid adding `turn-restriction` as it will result in redundant data_ + ![screen shot 2016-05-24 at 6 37 06 pm](https://cloud.githubusercontent.com/assets/4470913/15538956/1a068350-229d-11e6-9931-56770c643131.png) + _This situation is a clear indication of a redundant restriction_ + - Add a conditional restrictions when specific conditions are written on the turn-restriction sign-board. + - On certain times of the day. eg. Restriction during peak hours 7AM-10AM + - On a certain day of the year. eg. Restriction on baseball game days only + +## Adding Conditional turn restrictions + +**Special cases** +* [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions) during peak hours are common in SF. Tag them as `restriction:conditional=no_left_turn @ (Mo-Sa 07:00-09:00,16:00-18:00)`
![](https://cloud.githubusercontent.com/assets/4470913/14850426/9d4643f8-0c96-11e6-8c0c-dc94887e1613.png) +* Conditional restriction during baseball games. Ignore
+screenshot 2016-04-27 16 51 33 + +* In the case below, we are leaning towards adding this as a regular `restriction` since it applies for all regular personal vehicles. + + ![screenshot 2016-05-02 12 01 18](https://cloud.githubusercontent.com/assets/12103383/14948422/b9f1838a-105d-11e6-9604-2781de0d6d96.png) + +* If you come across the below instance where the restriction is applicable only on `School Days`. Per discussion we will be adding the restriction for `Monday - Friday` + + ![screen shot 2016-05-06 at 2 57 43 pm](https://cloud.githubusercontent.com/assets/1933377/15074787/7c6594d4-13be-11e6-9c01-1d277070960e.png) + +## QA for turn restrictions + +During turn restrictions mapping in various cities, we have come across certain special cases where we need to pay more attention while mapping. These cases are noted down here for your reference. + +---- + +# Be cautious when you come across these turn restrictions + +**1. Restrictions on Red** + +Be careful with interpreting signage and always verify Mapillary signage overlay with the image and the kind of restriction. The image below shows a sign for no free right that Mapillary interpreted as `no-right-turn`. This is NOT a turn restriction. If you are not sure, consult the community before mapping. +
screenshot 2016-04-26 21 39 06 + +A similar restriction found in Canada depicts that **left turn** cannot be taken when the signal is red, otherwise it is permitted to turn left. We are **not** adding such turn restrictions. + +![no_right_turn_on_red_sign](https://cloud.githubusercontent.com/assets/4470913/17021102/28acf658-4f63-11e6-8266-b380071706c4.jpeg) +_Picture by Share Bear - Own work - [Public Domain](https://commons.wikimedia.org/w/index.php?curid=8626974)_ + +**2. Location and bearing of Mapillary Signage overlay** + +The location and bearing of the Mapillary photo is not reliable and is prone to usual GPS errors. Cross check the photograph with the map to confirm you are looking at the intersection from the correct bearing. This photograph is facing the reverse of actual heading. +
screenshot 2016-04-27 12 28 12 + +**3. Single restriction per image detection** + +Mapillary will detect only one sign type per image. Lookout for multiple restrictions in the image
+screenshot 2016-04-27 17 49 34 + +**4. Careful with Turn restrictions plugin in JOSM** + +Sometimes the **Turn restrictions plugin** does not detect the correct signs i.e. even though it's a `no-right-turn`, the plugin detects it as `no-left-turn`. So be extra sure before adding the restriction +![turn_restrictions_plugin_bug](https://cloud.githubusercontent.com/assets/4470913/15529626/4f438044-226c-11e6-919e-02481acb5ad1.gif) + +**5. Advantage of previous/next images** + +There might be an offset in the Mapillary images, that is the image may appear after/before the actual location. It is ideal to inspect the previous and next images and also look for road names and other clues from the satellite imagery to verify it's exact location and bearing. +![offset_mapillary](https://cloud.githubusercontent.com/assets/4470913/15539155/712f0296-229e-11e6-8675-fecc95f4be51.png) + +**6. Temporary turn restrictions** + +When the roads are in construction or under repair, you might see temporary turn restrictions placed similar to shown in the below image. We are not adding temporary turn restrictions. +![pjimage](https://cloud.githubusercontent.com/assets/8921295/17290390/d8808ac2-57fb-11e6-8816-d681033e2a8f.jpg) + + + +**7. Restriction-ahead warnings** + +In the below image, there is a no_left_turn sign board as detected from the Mapillary image. This sign board means that there is a ```no_turn_restriction``` ahead. But this signage itself is **not** a turn restriction, so we do not map this. +[![screenshot 2016-07-26 15 31 15](https://cloud.githubusercontent.com/assets/8921295/17133998/03bf2e10-5346-11e6-949f-dcd4f554560b.png)](https://cloud.githubusercontent.com/assets/8921295/17133964/e83159fc-5345-11e6-935a-5b535390f730.jpg) + + +# Different conventions for turn restrictions in different countries + +### Canada + +**Case:1** + +The image below shows two signages, the first one is in French and translates to 'Wait for arrow to turn left' and the second one is a `no_u_turn`. In such cases, we ignore the the first signage and go ahead mapping `no_u_turn`. + +[![screenshot 2016-07-26 14 34 36](https://cloud.githubusercontent.com/assets/8921295/17132558/efc2a398-533f-11e6-93d7-7dc0e87978ae.png)](https://d1cuyjsrcm0gby.cloudfront.net/4ZA3OT0nHoDQ7F7JILG-pg/thumb-2048.jpg) + + +**Case:2** + + +In the below image, the first board for ```no_left_turn``` says Monday to Friday 8am-10am and 3pm-7pm (Lun-Ven 8h-10h,15h-19h in French). The second board is a ```no_u_turn``` **except authorized vehicles**. In this case, first one would be a conditional turn restriction; second, an absolute ```no_u_turn``` turn restriction. + +[![screenshot 2016-07-26 14 48 15](https://cloud.githubusercontent.com/assets/8921295/17132580/093ab860-5340-11e6-9863-ffe150f7c8c8.png)](https://d1cuyjsrcm0gby.cloudfront.net/IYi6WjwOQDnPW1HTTGyh8A/thumb-2048.jpg) + +**Case:3** + +The below image indicates that all the drivers (no matter the lane they are on) must follow this/these direction(s) at the intersection. This means that the driver needs to only turn right/left on the days mentioned in the sign and during that duration of the day. + +![image](https://cloud.githubusercontent.com/assets/3423533/17128539/0b5166e0-532b-11e6-96e6-69d21603f183.png) + +**Syntax to be used:** `restriction:conditional=only_right_turn @ (Mo-Fr 07:00-09:00,16:00-18:00)` + +### Germany + +In Germany, instead of signages to prohibit turns, the signages describe the legally allowed turns at the junction. Hence a signage for a no right turn will indicate only turns for left and straight. + +![screen shot 2016-08-17 at 4 12 05 pm](https://cloud.githubusercontent.com/assets/11845908/17733853/568ce2b6-6496-11e6-8665-8983fe1c94db.png) + +_An example of a `restriction=no_right_turn` traffic sign in Germany_ + +### Turn restriction signs of Germany and what it means: + +![screen shot 2016-08-17 at 4 27 33 pm](https://cloud.githubusercontent.com/assets/11845908/17734070/a6125f5e-6497-11e6-8d70-d55248e938ec.png) + +*Courtesy: [German wiki](http://wiki.openstreetmap.org/wiki/DE:Relation:restriction)* + + +**Reference** + +- OSM tags for routing http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing +- Turn restrictions http://wiki.openstreetmap.org/wiki/Relation:restriction +- Access restrictions http://wiki.openstreetmap.org/wiki/Key:access +- Conditional restrictions http://wiki.openstreetmap.org/wiki/Conditional_restrictions + +**Spanish version [here](https://github.com/mapbox/mapping/wiki/Gu%C3%ADa-de-mapeo-para-a%C3%B1adir-restricciones-de-giro-utilizando-mapillary)!** \ No newline at end of file diff --git a/mapping-to-improve-navigation/_posts/0000-01-05-mapping-guide-for-adding-exit-and-destination.md b/mapping-to-improve-navigation/_posts/0000-01-05-mapping-guide-for-adding-exit-and-destination.md new file mode 100644 index 0000000..8903d7b --- /dev/null +++ b/mapping-to-improve-navigation/_posts/0000-01-05-mapping-guide-for-adding-exit-and-destination.md @@ -0,0 +1,135 @@ +--- +title: Mapping guide for exit and destination +--- + +![5138660996_1957ee06ed_o](https://cloud.githubusercontent.com/assets/17887418/15180552/ec541b64-179f-11e6-88d7-4b3074f161e4.jpg) + +## What are exit numbers? + * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. + + ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) + +### Different tags for exit numbers: +* `ref=*` is used when the exit has a specific number assigned to it. +* `noref=yes` is used when the exit doesn't have any official number assigned to it. + +## How to add exit numbers? + +* Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. + +* Select the assigned highway from the dropdown and click on the `download` button. + + ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) + +### Verify the exits on the route for missing information + +* Load the route in JOSM + +![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) + + ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) + + * Browse along the route and check the ways on both directions at every exit location for the following: + - There is a `motorway_junction` at the start of every `motorway_link` exiting the highway + - The `motorway_junction` has a correct exit number `ref` value as per the source. + - The exit number on both directions are the same + - There is only one exit in a direction for every exit number + +**Add missing exit numbers** + +* Download the data and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) around the blue marker in the imagery. + +* Use a combination of Mapillary, Department of Transportation (DoT) documents and Wikipedia to add the `ref=*` tag on `highway=motorway_junction` (stick to using Mapillary and DoT doc as primary source and move to others in case of unavailability of information) + +* If it is confirmed there is no exit number for the `motorway_junction` add another tag `noref=yes` to indicate the exit does not have an official reference number. + + + +## Analyzing signboards in mapillary + +Look out of Highway sign boards on imagery. They may look something like this- + +![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) + +Places to look for- +- near a `motorway_junction` +- near **start** of a `motorway_link` + +![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) + + + +### Do's and don'ts +- It is not necessary that exit numbers are sequential. It might find 45 after 41. +- There are some `motorway_junction` which don't have any associated exit number. Add `noref=yes` on these nodes. +![no ref](https://cloud.githubusercontent.com/assets/17470597/15071466/65aff514-13a9-11e6-9392-3677c8b193a0.jpg) + +- If there are multiple exits on the same [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) then you can tag them as `ref=* ; *` instead of `ref:left=*` and `ref:right=*` until you are confirmed with that. + +- In the case of discrepancy between mapillary and DoT document, look out for the recent change in exit numbers on the web. Many states changes/in a process to change the exit numbers. +- **Ignore the `highway=motorway_junction` where the traffic flow is towards the motorway** + + +## What are destination tags? + +* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. +* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. + +![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) + +### Different tags for destinations: +* `destination` tag refers to the place that the way exiting from the freeway leads to. +* `destination:ref` is the reference of the roads directly ahead. +* `destination:ref:to` is to specify the reference of a major highway ahead. +* `destination:street` refers to the main street the way exiting from the freeway leads to. + +## How to add destination tags? + +### Assign a highway and use Checkautopista2 to map features + +1. Open the destination reference document for your assigned city area. Pick a highway to check and assign it on the spreadsheet to avoid conflict. + +2. Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. + +3. Select the assigned highway from the dropdown and click on the `download` button. + + ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) + + +4. Look out for red outer circle for missing destination. Use `open in JOSM` button to open the node in JOSM. Orange outer circle represents `exit_to` tag and we don't need to add destination tags in the way. Green outer circle represent that the concern way already has destination tag. + + + ![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) + + ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) + + +5. Download the data around the `motorway_junction` and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs). + +7. Use combination Mapillary images, DoT documents, and Wikipedia to add destination as `destination=*` on `motorway_link` ways and the destination highway as `destination:ref=*`. + **Below is a an example** + ![screen shot 2016-03-14 at 6 28 27 pm](https://cloud.githubusercontent.com/assets/12744420/13745188/a12098bc-ea12-11e5-8ffc-9fb839ed5aa2.png) + **On the `highway=motorway_link`(represented by red line) add `destination=Daly City` and `destination:ref=I 280 South`. This can be confirmed with [DoT document](http://www.dot.ca.gov/hq/traffops/engineering/calnexus/pdf/101.pdf) and [wikipedia](https://en.wikipedia.org/wiki/U.S._Route_101_in_California) while searching for exit number 431** + +8. Add any highway missing in the highway spreadsheet. Mark the highway done if all destination tags are mapped/review + + + +## Analyzing signboards in mapillary + +Look out of Highway sign boards on imagery. They may look something like this- + +![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) + +Places to look for- +- near a `motorway_junction` +- near **start** of a `motorway_link` + +![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) + + + +### Do's and don'ts +- Use `;` to separate multiple destination and refs. +- Read more on [Highway intersection](https://en.wikipedia.org/wiki/Interchange_(road)) to understand them better. + diff --git a/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md b/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md new file mode 100644 index 0000000..c53f038 --- /dev/null +++ b/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md @@ -0,0 +1,248 @@ + +--- +title: Mapping Guide for adding Turn Lanes from Imagery +--- + +## What is a turn lane + +A turn lane is an auxiliary lane demarcated on the road to specify directions to ongoing vehicles. +Turn lanes serve two purposes: + * Provide directional information to the ongoing vehicles and + * Provide the lane information to be chosen for the vehicles changing their direction + +### Types of turn lanes + +There are a total of 12 different turn lanes demarcated on the roads. They are: + +Turn Lane | Representation +--- | --- +turn:lanes = left | ![left](https://cloud.githubusercontent.com/assets/8401827/13217928/1d2fc24e-d98c-11e5-9d20-c526fe6e7f01.jpg) +turn:lanes = right | ![right](https://cloud.githubusercontent.com/assets/8401827/13217945/424f36e0-d98c-11e5-99e7-9d178f2529a1.jpg) +turn:lanes = through | ![through](https://cloud.githubusercontent.com/assets/8401827/13214156/f885d4b4-d973-11e5-9fb7-e9ecb70a932b.jpg) +turn:lanes = left;through | ![through left](https://cloud.githubusercontent.com/assets/8401827/13217986/80786072-d98c-11e5-99c6-db8665977550.png) +turn:lanes = right;through | ![through_right](https://cloud.githubusercontent.com/assets/8401827/13218022/b8aa9352-d98c-11e5-87c2-d8c17ee68305.jpg) +turn:lanes = left;through;right | ![leftthroughright](https://cloud.githubusercontent.com/assets/8401827/13218061/027e10ee-d98d-11e5-9747-c6867e0787b0.JPG) +turn:lanes = left;right | ![left_right](https://cloud.githubusercontent.com/assets/8401827/13217579/8f833c66-d989-11e5-9b2c-dc98fdff09b2.png) +turn:lanes = slight_left | ![slightleft](https://cloud.githubusercontent.com/assets/8401827/13218207/e450feaa-d98d-11e5-938c-a3956de2f7ba.png) +turn:lanes = slight_right | ![slightright](https://cloud.githubusercontent.com/assets/8401827/13218219/07052b56-d98e-11e5-8fc0-82b945fb95c6.png) +turn:lanes = merge_to_left | ![merge to left](https://cloud.githubusercontent.com/assets/8401827/13218244/2ca1fd6c-d98e-11e5-8be9-cb64271f5991.png) +turn:lanes = merge_to_right | ![fahrbahn_2](https://cloud.githubusercontent.com/assets/8401827/13218183/bc5d0790-d98d-11e5-9781-307f80cc0732.png) +turn:lanes:bothways = * | ![turn lanes both ways](https://cloud.githubusercontent.com/assets/8401827/13217721/a2594d48-d98a-11e5-87f1-11e11ebf57ec.png) + + ![](http://pdd.ua/r/r/EEB7A996-D8DC-40FC-87EA-01F3E115BC7C/m_1.18_4.jpg) + _road markings on the ground_ - © [pdd.ua](http://pdd.ua/ua/34/1.18/) + +### Pre-requirements for mapping a turn lane in JOSM + +Before mapping turn lanes activate the following preferences in JOSM to visualize the mapped turn lanes: `preferences > Map Settings` +* *`Map Paint Styles > Lane and road attributes`* + + ![lane_and_road_attributes](https://cloud.githubusercontent.com/assets/13744156/13218788/c55fab96-d991-11e5-89b2-b281986d704e.gif) + +* *`Tagging Presets > lane attributes`* + + ![tagging_presets](https://cloud.githubusercontent.com/assets/13744156/13218902/ad15c902-d992-11e5-872b-1bde24f27f5b.gif) + +* Filter out non-road features with inverse filter: `boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:` + +**Plugins** + +* Knife-tool: https://gist.github.com/jothirnadh/a10daeaef1498537ea56f0a65f7fdbc2 +* TurnLanes-tagging plugin: `JOSM Preferences > Plugins > turnlanes-tagging` + +### Mapping a turn lane + +* Check all roads in the imagery for turn lanes at junction points + + ![roads_markings](https://cloud.githubusercontent.com/assets/126868/11710074/b58b52e4-9f42-11e5-971a-000a699a0b6d.png) + +* Split the road into segments based on the total number of lanes for the segment. The easiest way for splitting the road is by using [Knife_tool](https://gist.github.com/jothirnadh/a10daeaef1498537ea56f0a65f7fdbc2) + + ![residential_road](https://cloud.githubusercontent.com/assets/369696/13223732/34cf7ffa-d98e-11e5-9a33-8f40f6498004.png) + +* For each road segment tag the turn lanes based on the road markings in the direction of the way. Eg. `turn:lanes=left|left;through|through`. Check [OSM turn:lanes](http://wiki.openstreetmap.org/wiki/Key:turn:lanes) for reference. + + ![oneway_turn:lanes_tagging](https://cloud.githubusercontent.com/assets/8401827/13252110/a6bdea8a-da5a-11e5-8c79-aa15c0c15f68.gif) + +* For bi-directional segments, use `turn:lanes:backward=` and `turn:lanes:forward=` to specify turn lanes in each direction. + + ![bidirectional_tagging](https://cloud.githubusercontent.com/assets/13744156/13219545/acd78f62-d996-11e5-85eb-3e05a7b79d3b.gif) + +* Verify correct tagging using the `Lane attributes` style + + ![lane_attributes](https://cloud.githubusercontent.com/assets/8401827/13251884/ddcbdd54-da58-11e5-86ae-c4a2918c9577.gif) + +* The simplest way to add turn lanes is by using **[turnlanes-tagging plugin](https://www.mapbox.com/blog/turnlanes-tagging/)** + +![turnlenes](https://cloud.githubusercontent.com/assets/8401827/17246767/d086ef48-55ab-11e6-8bce-46c434cb9005.gif) + +### `turn:lanes` and relations + +We use [relations](http://wiki.openstreetmap.org/wiki/Relation) for different purpose – for indicating [turn restriction](http://wiki.openstreetmap.org/wiki/Relation:restriction) or collect separate ways into solid [route](http://wiki.openstreetmap.org/wiki/Relation:route). +​ +JOSM help us to handle them. But sometimes we are faced with not properly denoted relations. JOSM will inform about it while uploading our changes. You may [ignore messages of level "Warnings"](https://github.com/mapbox/mapping/issues/153#issuecomment-185679507) (if you only split ways and didn't edit relations manually) but you have to fix all "Errors". + +## QA for turn lanes mapping + +While mapping turn lanes, there are a lot of scenarios are encountered in [#153](https://github.com/mapbox/mapping/issues/153) and [#144](https://github.com/mapbox/mapping/issues/144) mapping repos. All these scenarios are drafted in one place for validation purposes. + +## Different scenarios we came across while mapping + +### 1. Parking lanes + +In the U.S., when parallel parking spaces are marked, they are marked in one of [three ways](http://mutcd.fhwa.dot.gov/htm/2009/part3/fig3b_21_longdesc.htm): + + ![parking_lanes](https://cloud.githubusercontent.com/assets/8401827/13172245/326a7bb6-d71d-11e5-8617-a2516f75144b.png) + +Here’s an example of the box marking style: + + [![boxes](https://upload.wikimedia.org/wikipedia/commons/thumb/0/03/J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG/320px-J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG)](https://commons.wikimedia.org/wiki/File:J.S._Shingler_Bldg_%28East_face%29,_McLendon_St,_Ashburn.JPG) + +### 2. Counting number of turn lanes + +If there are no clear cut demarcations on the road and yet cars are parked on either sides of the road, consider them as drive lanes. Case below: + + ![number_of_lanes](https://cloud.githubusercontent.com/assets/8401827/13142482/5b26d0a0-d663-11e5-90cd-4a65d75e7248.png) + +### 3. Starting a turn lane + + Turn lanes should begin exactly as per the marking in the imagery, not before or after. + + ![turn:lanes_start](https://cloud.githubusercontent.com/assets/8401827/13110125/0fe83ad0-d5a4-11e5-82ff-00245d0ba043.png) + +### 4. Ending a turn lane + +Turn lanes should terminate at the first highway junction after the start of the turn lane. + + ![turn:lanes_end](https://cloud.githubusercontent.com/assets/8401827/13143057/4ff2b3c6-d667-11e5-8069-b028fabf7587.png) + +### 5. Turn lane forward + +In case of bi-directional ways, the key [turn:lanes:forward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the same direction as the osm-way; while adding this we must view the road in the direction to the osm-way(**on the direction where the osm-way arrow is pointing**). + + ![turn:lanes:forward](https://cloud.githubusercontent.com/assets/8401827/13175904/c5c922fc-d733-11e5-91b1-c0f9e5181fda.gif) + +### 6. Turn lane backward + +In case of bi-directional ways, the key [turn:lanes:backward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the opposite direction as the osm-way; while adding this we must view the road in the oppoiste direction to the osm-way(**opposite to direction where the osm-way arrow is pointing**). + + ![turn:lanes:backward](https://cloud.githubusercontent.com/assets/13744156/13172709/859957c4-d71f-11e5-8cd9-ea154ad5d2e8.gif) + + *Adding a `turn:lanes:backward` tag* + +### 7. Adding dual carriageways: + +When finding roads mapped as single carriageway while the imagery shows clear separation between roads, split the road where the physical separation starts and add dual carriageways. + +![dualcarriageway](https://cloud.githubusercontent.com/assets/8401827/13393542/117b59aa-df08-11e5-8fd3-21a931531f84.png) + + +**When to add dual carriageway?** +- Add Dual-carriage when + - you see physical separation betweens roads + - **no relation is attached to the way.** +- Add `turn:lanes` tag to both the ways. + + +### 8. Bicycle lanes and road shoulders + +Road shoulders and bicycle lanes are ignored from the lane count. Both these roads are `lanes=2` + + ![bicycle+shoulders](https://cloud.githubusercontent.com/assets/126868/11715007/628dd90a-9f64-11e5-9e22-58614d2afbf6.png) + + ![bicycle_lanes](https://cloud.githubusercontent.com/assets/13744156/13172922/adc69f08-d720-11e5-8600-7a606d2e9bae.png) + + *lanes=3 for the above example, ignoring the two cycle ways* + +* Ignore bicycle lanes even though they are in the middle;example below: + + ![xyz2](https://cloud.githubusercontent.com/assets/8401827/13495220/79a65aca-e16f-11e5-83e7-24d3e4f53ad0.png) + + *The middle way is also a bicycle lane which is not counted while adding the `lanes` tag* + +* Additionally, `Strava global-heat cycle` layer can used to verify if a particular lane is a cycle-way. +`tms[16]:http://globalheat.strava.com/tiles/cycling/color3/{zoom}/{x}/{y}.png` + +### 9. Lane marked as a separate way + +Do not add turn lanes in these cases where the only turn lane is already a mapped as a separate way. + + ![lane_as_separate_way](https://cloud.githubusercontent.com/assets/13744156/13173428/6694c468-d723-11e5-96be-b95502b9f58a.png) + +### 10. Bidirectional turn lanes + +These are the lanes marked with symbol representing both directions at a time. + + ![turn:lanes:both_ways](https://cloud.githubusercontent.com/assets/8401827/12642951/0162ff9c-c5df-11e5-8a14-a41f263ae086.png) + +Tag used for such lanes are `turn:lanes:both_ways=*` + +Yellow lines on both sides of a lane also gives an indication of `turn:lanes:both_ways=*` + +![screen shot 2016-05-16 at 4 12 49 pm](https://cloud.githubusercontent.com/assets/1933377/15287587/8dd24396-1b81-11e6-8527-b84814804175.png) + +![screen shot 2016-05-16 at 4 13 00 pm](https://cloud.githubusercontent.com/assets/1933377/15287591/9165c50a-1b81-11e6-9521-93cea4b7be16.png) +### 11. Mapillary Plugin to verify turn lanes + +The imagery at some places is not very clear and at-times the turn-lanes are covered by cars. In situations like these `Mapillary plugin` can be used. If there is Mapillary imagery coverage in that area, they can used to verify the presence of turn-lanes. + +**Name of the plugin:** Mapillary + + ![turnlanes_mapillary](https://cloud.githubusercontent.com/assets/4470913/12884912/6b405d1e-ce87-11e5-8d0f-cd8a8a8b3dfd.gif) + +### 12. Lanes with restricted access + +These are the areas on streets which are restricted for vehicular traffic. + +![screen shot 2016-03-15 at 3 36 36 pm](https://cloud.githubusercontent.com/assets/8401827/13776503/84c34002-ead0-11e5-911d-0581fe9173b7.png) + +![screen shot 2016-03-14 at 4 46 03 pm](https://cloud.githubusercontent.com/assets/8401827/13776504/84e64138-ead0-11e5-81f0-7918311ec6dc.png) + +![screen shot 2016-03-14 at 4 46 29 pm](https://cloud.githubusercontent.com/assets/8401827/13776505/84e71888-ead0-11e5-9135-553c11d99d12.png) + +In the above cases the areas with markings on the roads are not considered as a lane + +### 13. Reverse direction turn lanes + +These are the lanes specifically categorized to take U-turn or reverse-turn. + +![screen shot 2016-03-14 at 2 25 28 pm](https://cloud.githubusercontent.com/assets/8401827/13776502/84944b6c-ead0-11e5-92fa-0bb2951760ef.png) + +### 14. The order of the directions and valid combinations of values + + - `none` itself is valid value but **not** in conjunction with other + + - ✅ `turn:lanes=none|right` is equal to `turn:lanes=|right` - we use `none` for "_better readability_" + + - 👎 `turn:lanes=left||none|merge_to_right` - this combination of values is valid but there is mixing `none` and `||` (empty) - this is not good choice. + + - 👍 `turn:lanes=left|none|none|merge_to_right` or `turn:lanes=left|||merge_to_right` + + - ❎ `turn:lanes=none|none|none` or `turn:lanes=||` - in this case `turn:lanes=*` tag is redundant, just specify `lanes=3` or real number of lanes + + - ❎ `turn:lanes=none|none;slight_right` - isn't valid combination - "_there are no turn indications_" on the rightmost lane. Instead, must be used (based on https://github.com/mapbox/mapping/issues/180#issuecomment-225574666) + +``` +lanes=2 +turn:lanes=none|through;slight_right +transit:lanes=continue|new_on_right +``` + +- using `*right` | `*left` values + + - ✅ `turn:lanes=left|none|none` or `turn:lanes=||right` or `turn:lanes=merge_to_right||` or `turn:lanes=left|left;through|none|slight_right|right|right`- 👍 + + - ❎ `turn:lanes=|right|left|` or `turn:lanes=none|right|left|through` or `turn:lanes=none|left|none`- 👎 lanes that go in one direction should not cross with each other + +- using `reverse` value + + - `reverse` (u-turn) have to be on the leftmost lane for right-hand traffic or on the rightmost lane for right-hand + +### 15. + +_to be continued …_ + +### Further reading: +* [Mapping turn lanes: OSM wiki](http://wiki.openstreetmap.org/wiki/Key:turn) +* [Mapping turn lanes in OpenStreetMap by Andrey Golovin](https://www.mapbox.com/blog/turn-lanes-mapping/) +* Diary post by @Andygol : [Mapping turn lanes in OpenStreetMap](http://www.openstreetmap.org/user/andygol/diary/35489#) diff --git a/mapping-to-improve-navigation/_posts/0000-01-07-resources-and-references.md b/mapping-to-improve-navigation/_posts/0000-01-07-resources-and-references.md new file mode 100644 index 0000000..1c9eed5 --- /dev/null +++ b/mapping-to-improve-navigation/_posts/0000-01-07-resources-and-references.md @@ -0,0 +1,49 @@ +--- +title: Resources and References +--- + +**Mapbox navigation mapping projects** + +Navigation mapping forms a large part of Mapbox's mapping sprints in recent times. Given below are a few examples of some of the latest navigation mapping efforts across US, Canada, and Europe. To get an idea about all our historical mapping projects related to navigation in OSM, look into the [mapping repository](https://github.com/mapbox/mapping/issues). Our mapping projects are conducted in the open with active participation, feedback, and validation from the community. + +#### Examples + +Location | Description|Start|End(ETA)|Validation +---|---|---|---|---| +[Mapping turn lanes in 30 US cities](https://github.com/mapbox/mapping/issues/180)| Mapping all the turn lanes from satellite imagery in 30 US cities from secondary and above|04/05/2016|Continuing|Continuing +[Updating turn restrictions in Germany](https://github.com/mapbox/mapping/issues/226)| Updating missing turn restriction coverage in 3 german cities: Berlin, Stuttgart, Wolfsburg|29/08/2016|Continuing|Continuing +[Mapping turn restrictions in Canada](https://github.com/mapbox/mapping/issues/213)|Mapping turn restrictions from mapillary in top 5 cities in Canada|22/07/2016|05/08/2016|Completed +[Exit and destination mapping in Canada](https://github.com/mapbox/mapping/issues/220)|Map the exit and destination numbers in top 5 Canada cities using mapillary|11/08/2016|17/08/2016|Completed + +**Navigation data tools** + +* [OpenStreetMap navigation map](http://mapbox.github.io/osm-navigation-map/#11.63/37.7896/-122.4363): This map is used to add turn restrictions in OSM. It has a detected signage mapillary layer for easy detection of turn restrictions, oneways and a dataset which displays all the valid, invalid and redundant turn restrictions added. Get more [instructions](https://github.com/mapbox/osm-navigation-map/blob/gh-pages/MAPPING.md) on `how to use the OSM navigation map`. +* [CheckAutopista2](http://k1wiosm.github.io/checkautopista2/): It is a tool to investigate and add highway signboard features on motorways and freeways. For more details look into the [github repository](https://github.com/k1wiosm/checkautopista2) for `checkautopista`. +* [Overpass](https://overpass-turbo.eu/): The place to query and extract all OSM data related to a specific feature. It has a simple query builder feature that helps in querying each and every feature in OSM. Details about [overpass](http://wiki.openstreetmap.org/wiki/Overpass_turbo) can be found [here](http://wiki.openstreetmap.org/wiki/Overpass_API) and [here](http://wiki.openstreetmap.org/wiki/Overpass_API/Language_Guide). +* [Knife tool](https://www.mapbox.com/blog/knife-tool/): The knife tool can be used for quick splitting of ways while adding navigation features such as turn lanes. For more details, look [here](https://github.com/mapbox/auto-tools/tree/split) +* [Turn lanes tagging plugin](https://www.mapbox.com/blog/turnlanes-tagging/): With this plugin, you can add complex tag combinations for turn lanes at road junctions with ease, and minimize errors. For more details, look [here](https://github.com/JOSM/turnlanes-tagging) + + + +**Country specific navigation guide** + - Images of traffic signs and road markings : Traffic signs and road markings may undergo small changes and specific cases when mapping turn restrictions using Mapillary. There are subtle differences in turn restrictions between Canada, US, and Germany. *(This section is to be kept updated with new signages every time mapping is done in a separate country with new conventions)* + +1. **[Turn restriction images in US](https://gist.github.com/abhisheksaikia/7c9329a985816c128aabcba092747816)** + +2. **[Turn restrictions images in Germany](https://gist.github.com/abhisheksaikia/646b918fc64f9d8109b5d62a8137e86a)** + +3. **[Turn restrictions in Canada](https://gist.github.com/abhisheksaikia/bcfbf4ea0dc1e100337244867b2524fc)** + +4. **[Turn restrictions in France](https://gist.github.com/jothirnadh/3d0245816dabbf395c447130877c538c)** + + +For more details on cases for turn restrictions and signages in different countries take a look at [QA for mapping turn restrictions](https://gist.github.com/abhisheksaikia/6e12973daa5be78da3ef9ba6d21b8562) + +**Data sources and references for navigation data** + +* [Mapillary](https://www.mapillary.com/) + +* [OpenStreetView](http://openstreetview.org/map/) +- **DOT documents/websites**: Local official websites, documents released by local `Department of Transportation` bodies. +- **Wikipedia**: Exit and destination numbers, highways, highway refs. *(must be verified on ground or with official sources)* +- High resolution satellite imagery: Bing, Mapbox, USGS, open satellite datasets ([Landsat](http://landsat.usgs.gov/), [Sentinel2](http://www.esa.int/Our_Activities/Observing_the_Earth/Copernicus/Sentinel-2/Data_products), [LISS](http://bhuvan.nrsc.gov.in/data/download/index.php), government opendata portals). From d7d40ca699c189fa5799f61915d5a141e4aa57e7 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Mon, 24 Oct 2016 16:47:14 +0530 Subject: [PATCH 21/66] remove old content --- .../0000-01-01-understanding-navigation.md | 81 ------------ ...000-01-02-modeling-roads-for-navigation.md | 107 --------------- .../_posts/0000-01-03-turn-lanes.md | 91 ------------- .../_posts/0000-01-04-qa-for-turn-lanes.md | 122 ------------------ .../0000-01-05-navigation-mapping-projects.md | 27 ---- mapping-to-improve-navigation/index.md | 4 +- 6 files changed, 1 insertion(+), 431 deletions(-) delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-01-understanding-navigation.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-navigation.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-03-turn-lanes.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-04-qa-for-turn-lanes.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-05-navigation-mapping-projects.md diff --git a/mapping-to-improve-navigation/_posts/0000-01-01-understanding-navigation.md b/mapping-to-improve-navigation/_posts/0000-01-01-understanding-navigation.md deleted file mode 100644 index fd92377..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-01-understanding-navigation.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Understanding navigation ---- - -Navigation is a service which helps people to get from one place to another by using the best route. For a navigation system to work it should have two important components, routing and guidance. To most people, these may appear to be the same, but each has a unique function. Routing is the process of selecting the best path in a network of roads. Guidance describes routing in the form of a human-readable list of instructions. - -The navigation part looks at the road network as a form of connections and an expected travel time along the segments in between. In this part, turn restrictions, the shape of the road, or even traffic signals can influence the navigation. Everything that modifies the expected travel time along a road influences the navigation. - -## Routing Profile - -A navigation engine supports various *routing profiles*. These are the configurations, representing different routing behaviours for (typically) different transport modes. A profile describes whether we are supposed to route along a particular type of way, or over a particular node in the OpenStreetMap data, and also how quickly we'll be travelling when we follow its instructions. This feeds into the way the routing graph is created and thus influences the output routes. Examples of the most common routing profiles includes: car, bicycle and foot. - -## Routing - -Routing is used to **find an optimum path in a map**. There are some key OpenStreetMap tags which influence navigation, such as the `type=restriction`, which prohibits the access to certain kinds of turns at junctions, `maxspeed=*`, which defines the default-speed to be followed in the path and so on. - -The most important attributes required to provide the optimum route using OpenStreetMap data are: - -### 1. Road types - -The way types are considered according to their order of importance. They are tagged with `highway=*` tag. The general order of importance for way types are: - - major highways > main roads > streets > footpaths - -### 2. Maxspeed limits - -The `maxspeed=*` tag is used to define the maximum legal speed limit for general traffic on a particular road, railway or waterway. The max speed values will be interpreted as kilometers per hour by default. The `maxspeed=*` is an important part of routing as it is used in determining the shortest time taken by a specific route to reach a destination. In case of two routes, the one with the shortest time take(higher maxspeed) and shortest distance will be the optimum route. - -### 3. Turn-Restrictions - -`type=restriction` is the relation in OSM which is used to describe turn restrictions at junctions. The relation has a set of tags, e.g. `no_left_turn`, `no_right_turn`, `no_u_turn`, etc which describes the type of turn restriction. These are traffic signage at junctions and this information must be present on the map to find the best route by the routing engine while planning the journey. - -![screen shot 2016-03-08 at 8 05 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604633/ad8bff4a-e569-11e5-9198-3ac9c88e5619.png) - -### 4. Access-Restrictions - -Apart from turn restrictions, there are access restrictions for different parts of highways. Some of these tags are `access=no`, `access=private` etc which will end up altering the route to be taken during the journey. For more information on the various king of `access=*` tags take a look at [Key:access](http://wiki.openstreetmap.org/wiki/Key:access) and [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions). - -### 5. Traffic signals - -Traffic signals such as: `highway=traffic_signals`, `highway=stop` or `barrier=toll_booth` as well as `traffic_calming=*` are considered during routing. The `type=restriction` more commonly referred to as **turn restrictions** are traffic signage which prohibits certain turns in intersections are also a crucial component of a great `routing` engine. - -### 6. Other attributes - -Everything that modifies the expected travel time along a road influences the navigation. Considering this, there are some other tags apart from the above mentioned tags which play a significant role in routing. They are: - - oneway=yes - oneway=reversible - junction=roundabout - bridge=yes - tunnel=yes - surface=* - access=* - -Overall the selection of a particular route or the optimum route depends on a variety of factors which are taken into account by the routing engine: - -* Personal factors: fastest route, most scenic route, quietest route, shortest route, facilities requirement -* Vehicle factors: mode of transport, physical category of vehicle, optimum traveling speed, riding surface requirements, fueling requirements -* Route factors (static): classification of road, access restrictions, speed limits, turn restrictions, oneway rules, number of lanes -* Traffic factors (dynamic): traffic conditions, traffic signal cycle duration, weather conditions -* Riding surface factors: surface material, smoothness, barriers, speed breakers, road width, lane width, age - -## Lane Guidance - -![screen shot 2016-03-08 at 7 51 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604319/236e84dc-e568-11e5-850a-cf398719db11.png) - -*How a driver views turn lanes from the car* - -Guidance is used to **lead a person through the determined optimum path**. Once the routing algorithm determines the feasible optimum path, that route is converted into a set of human-readable instructions known as guidance. For proper guidance, there are some key OSM tags being used in OpenStreetMap,such as `turn:lanes=*` tag to specify the lane to be chosen in the routing path and so on. - -Turn lanes have an influence on the path finding and are one of the most vital components for proper guidance. Choosing the correct turn lane can have a big influence in navigation. In many cases, they only help to illustrate a turn better but other times, they are vitally important. In guidance, the aim is to provide a set of instructions, like keep right or keep left by describing the optimum route found by the routing algorithm to a driver. - -These tags also influence the travel times, such as lanes information which in the form of HOV lanes can both positively and negatively influence travel times. - -The most important attributes required to provide the better guidance using OpenStreetMap data are: - - lanes=* - turn:lanes=* - name=* - ref=* - relation:route diff --git a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-navigation.md b/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-navigation.md deleted file mode 100644 index e2a1cf8..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-navigation.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: Modeling roads in OSM for navigation ---- - -## Roads -Roads are the main map features that we use for rendering navigational applications. Accurate roads representation leads not only to the well-looking map but also to a more precise navigation. - -For now, most common approach for road mapping is to trace roads following their centroid. This way of tracing looks good for 2-lanes roads like unclassified and residential roads or for tracing over low-res imagery. - -![road_with_two_lanes](https://cloud.githubusercontent.com/assets/369696/13230189/1bc4b308-d9ad-11e5-88b7-f85fcd290926.png) - -## What is a Way - -A Way in OSM represents road as a complex feature. First of all, it is a line that represents an object (road), which covers a specific **area** on the ground. In order to show the shape and contours of the road we may to draw a polygon and mark it accordingly. (See [`area:highway`=`*`](http://wiki.openstreetmap.org/wiki/Key:area:highway), [description](http://wiki.openstreetmap.org/wiki/Proposed_features/Street_area) and [comprehensive mapping guide](http://wiki.openstreetmap.org/wiki/Proposed_features/area_highway/mapping_guidelines) in Wiki OSM) - -## What is a lane - -To understand the complexity of a Way, the width of the road is divided into absolute (meters) or in relative number of lanes units of measurement. Numbers of lanes on the road will help us to make our driving decisions. At least road has one lane for driving in both directions. This is a rough assumption. As a general rule, the road has two or more lanes for vehicular traffic. - -![residential_road](https://cloud.githubusercontent.com/assets/369696/13223732/34cf7ffa-d98e-11e5-9a33-8f40f6498004.png) - -Use the `lanes=*` key to tag how many full-width traffic lanes there are on a highway. - -### Roads with more than two lanes - -There are two cases: - -- Roads which carry traffic in both directions and - - ![bidirectional_road](https://cloud.githubusercontent.com/assets/369696/13230341/9f9db6c0-d9ad-11e5-9f5d-53dd80b40f67.png) - -- Dual carriageway roads. - - ![dual_carriageway_road](https://cloud.githubusercontent.com/assets/369696/13230427/fe21579c-d9ad-11e5-86ba-38107d469c54.png) - -To set number of lanes for roads which carry traffic in both directions use [`:backward` and `:forward` suffixes](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right#Forward_and_backward) - -`Forward` means the direction in which the way is drawn in OpenStreetMap, while `backward` means the opposite direction. - - Example: - highway=tertiary - lanes=5 - lanes:forward=3 - lanes:backward=2 - -Roads with an even number of lanes tend to have an equal number of lanes in each direction by default and thus we may omit `:forward` and `:backward` tagging. - -In opposite case, when numbers of lanes for each directions don't match, we have to explicitly denote their numbers with `lanes:forward=*`+`lanes:backward=*` along with overall numbers of `lanes=*`. - -We are not able to draw a road on its center line, especially if roads join/fork or the number of lanes change. Imagine two roads which join: how would you draw the OSM-way around the point where the roads join? - - ![center_line](https://wiki.openstreetmap.org/w/images/4/47/Lane_Placement_2.png) - - _center line tracing_ - - ![main_direction](https://wiki.openstreetmap.org/w/images/e/e4/Lane_Placement_3.png) - - _tracing main direction_ - -Our decision is to trace **main direction**! - -Before tracing (fix previous tracing), we need to inspect the start and end points of the road segments. We need to identify the road direction, general numbers of lanes and the places where there are extra lanes. Based on this we choose our strategy. - -### Bidirectional roads - -At the image below general number of lanes is two - `lanes=2`. Orange line is the center line of bidirectional way which represents main movement direction. We don't change its flow when extra lanes are appeared. Just set `lanes=3`+`lanes:forward=2`+`lanes:backward=1` tags for the segment at right low corner with extra lane for turn to right. Optionally we may specify [placement](https://wiki.openstreetmap.org/wiki/Proposed_features/placement) of the lanes relatively to the our OSM-way. - - ![residential_road](https://cloud.githubusercontent.com/assets/369696/13223732/34cf7ffa-d98e-11e5-9a33-8f40f6498004.png) - - ![residential_road_2](https://cloud.githubusercontent.com/assets/369696/13228435/ae570094-d9a4-11e5-9f3c-4737112a7932.png) - -Look to the below image. There is we have two tagging variants: - -1. `lanes=2` - 1 lane for each direction, or - -2. `lanes=3` - denote middle lane for left turn as (:point_left: _this is [discussed](http://wiki.openstreetmap.org/wiki/Proposed_features/Suffix_both_ways)_) - - highway=residential - lanes=3 - lanes:forward=1 - lanes:backward=1 - lanes:both_ways=1 - turn:lanes:both_ways=left - - ![residential_road_3](https://cloud.githubusercontent.com/assets/369696/13229045/ab01d6f0-d9a7-11e5-8d8a-1fe5518c84a5.png) - - Case when number of lanes is even but numbers of lanes for each direction not equal. :point_down: - - ![trunk_link](https://cloud.githubusercontent.com/assets/369696/13229897/b09a811c-d9ab-11e5-935e-25906c94585b.png) - -### Dual carriageway roads - -Trace ways for dual carriageways road for each direction as close as possible to their outermost edge. There is some reasons for such way of tracing: - - In lower zoom levels we will be able to distinguish dual carriageways road from bidirectional one just glimpsing on the map - - GPS devices will associate their position with right road segments even in bad signal reception conditions - - Link roads which join to or fork from main highway will look good and will be connected in right places - - We are able to adjust position of the lanes on the road using `placement=right_of:3` tagging if needed. - -Place nodes of the lines in each direction, opposite to each other, which will get a good view of the road on the map - - ![motorway](https://cloud.githubusercontent.com/assets/369696/13231932/5b417e00-d9b5-11e5-854e-dbed2d209d7c.png) - -## Further reading - -* Adding lanes in OSM: [OSM wiki](http://wiki.openstreetmap.org/wiki/Key:lanes) -* Specifying placement of the OSM-way relative to the road it represents: [Proposal in OSM wiki](http://wiki.openstreetmap.org/wiki/Proposed_features/placement) -* Specifying lanes or similar features running in both directions of the OSM way: [Proposal in OSM wiki](http://wiki.openstreetmap.org/wiki/Proposed_features/Suffix_both_ways) diff --git a/mapping-to-improve-navigation/_posts/0000-01-03-turn-lanes.md b/mapping-to-improve-navigation/_posts/0000-01-03-turn-lanes.md deleted file mode 100644 index 20160cf..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-03-turn-lanes.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Mapping guide for turn lanes from imagery ---- - -## What is a turn lane - -A turn lane is an auxiliary lane demarcated on the road to specify directions to ongoing vehicles. -Turn lanes serve two purposes: - * Provide directional information to the ongoing vehicles and - * Provide the lane information to be chosen for the vehicles changing their direction - -## Types of turn lanes - -There are a total of 12 different turn lanes demarcated on the roads. They are: - -Turn Lane | Representation ---- | --- -left | ![left](https://cloud.githubusercontent.com/assets/8401827/13217928/1d2fc24e-d98c-11e5-9d20-c526fe6e7f01.jpg) -right | ![right](https://cloud.githubusercontent.com/assets/8401827/13217945/424f36e0-d98c-11e5-99e7-9d178f2529a1.jpg) -through | ![through](https://cloud.githubusercontent.com/assets/8401827/13214156/f885d4b4-d973-11e5-9fb7-e9ecb70a932b.jpg) -left_through | ![through left](https://cloud.githubusercontent.com/assets/8401827/13217986/80786072-d98c-11e5-99c6-db8665977550.png) -right_through | ![through_right](https://cloud.githubusercontent.com/assets/8401827/13218022/b8aa9352-d98c-11e5-87c2-d8c17ee68305.jpg) -left_through_right | ![leftthroughright](https://cloud.githubusercontent.com/assets/8401827/13218061/027e10ee-d98d-11e5-9747-c6867e0787b0.JPG) -left_right | ![left_right](https://cloud.githubusercontent.com/assets/8401827/13217579/8f833c66-d989-11e5-9b2c-dc98fdff09b2.png) -slight_left | ![slightleft](https://cloud.githubusercontent.com/assets/8401827/13218207/e450feaa-d98d-11e5-938c-a3956de2f7ba.png) -slight_right | ![slightright](https://cloud.githubusercontent.com/assets/8401827/13218219/07052b56-d98e-11e5-8fc0-82b945fb95c6.png) -merge_to_left | ![merge to left](https://cloud.githubusercontent.com/assets/8401827/13218244/2ca1fd6c-d98e-11e5-8be9-cb64271f5991.png) -merge_to_right | ![fahrbahn_2](https://cloud.githubusercontent.com/assets/8401827/13218183/bc5d0790-d98d-11e5-9781-307f80cc0732.png) -bothways | ![turn lanes both ways](https://cloud.githubusercontent.com/assets/8401827/13217721/a2594d48-d98a-11e5-87f1-11e11ebf57ec.png) - - ![](http://pdd.ua/r/r/EEB7A996-D8DC-40FC-87EA-01F3E115BC7C/m_1.18_4.jpg) - _road markings on the ground_ - © [pdd.ua](http://pdd.ua/ua/34/1.18/) - - -## Other Markings apart from turn:lanes - -### HOV - -[HOV](http://wiki.openstreetmap.org/wiki/Key:hov) is a symbol demarcated on major roads generally used to indicate vehicle occupancy requirements. - - ![xyz](https://cloud.githubusercontent.com/assets/8401827/13495163/13ecbc06-e16f-11e5-90d4-1bd1c8bb8b5e.png) - -In the above cases tag given to the road are `hov:lanes=designated|yes|yes|yes` - -## Pre-requirements for mapping a turn lane in JOSM - -Before mapping turn lanes activate the following preferences in JOSM to visualize the mapped turn lanes: `preferences > Map Settings` - -* *`Map Paint Styles > Lane and road attributes`* - - ![lane_and_road_attributes](https://cloud.githubusercontent.com/assets/13744156/13218788/c55fab96-d991-11e5-89b2-b281986d704e.gif) - -* *`Tagging Presets > lane attributes`* - - ![tagging_presets](https://cloud.githubusercontent.com/assets/13744156/13218902/ad15c902-d992-11e5-872b-1bde24f27f5b.gif) - -* Filter out non road features with inverse filter: `boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:` - -## Mapping a turn lane - -* Check all roads in the imagery for turn lanes at junction points - - ![roads_markings](https://cloud.githubusercontent.com/assets/126868/11710074/b58b52e4-9f42-11e5-971a-000a699a0b6d.png) - -* Split the road into segments based on the total number of lanes for the segment - - ![residential_road](https://cloud.githubusercontent.com/assets/369696/13223732/34cf7ffa-d98e-11e5-9a33-8f40f6498004.png) - -* For each road segment tag the turn lanes based on the road markings in the direction of the way. Eg. `turn:lanes=left|left;through|through`. Check [OSM turn:lanes](http://wiki.openstreetmap.org/wiki/Key:turn:lanes) for reference. - - ![oneway_turn:lanes_tagging](https://cloud.githubusercontent.com/assets/8401827/13252110/a6bdea8a-da5a-11e5-8c79-aa15c0c15f68.gif) - -* For bi-directional segments, use `turn:lanes:backward=` and `turn:lanes:forward=` to specify turn lanes in each direction. - - ![bidirectional_tagging](https://cloud.githubusercontent.com/assets/13744156/13219545/acd78f62-d996-11e5-85eb-3e05a7b79d3b.gif) - -* Verify correct tagging using the `Lane attributes` style - - ![lane_attributes](https://cloud.githubusercontent.com/assets/8401827/13251884/ddcbdd54-da58-11e5-86ae-c4a2918c9577.gif) - -## turn:lanes and relations - -We use [relations](http://wiki.openstreetmap.org/wiki/Relation) for different purpose – for indicating [turn restriction](http://wiki.openstreetmap.org/wiki/Relation:restriction) or collect separate ways into solid [route](http://wiki.openstreetmap.org/wiki/Relation:route). -​ -JOSM help us to handle them. But sometimes we are faced with not properly denoted relations. JOSM will inform about it while uploading our changes. You may [ignore messages of level "Warnings"](https://github.com/mapbox/mapping/issues/153#issuecomment-185679507) (if you only split ways and didn't edit relations manually) but you have to fix all "Errors". - -## Further reading - -* [Mapping turn lanes: OSM wiki](http://wiki.openstreetmap.org/wiki/Key:turn) -* [Mapping turn lanes in OpenStreetMap by Andrey Golovin](https://www.mapbox.com/blog/turn-lanes-mapping/) -* Diary post by @Andygol : [Mapping turn lanes in OpenStreetMap](http://www.openstreetmap.org/user/andygol/diary/35489#newcomment) diff --git a/mapping-to-improve-navigation/_posts/0000-01-04-qa-for-turn-lanes.md b/mapping-to-improve-navigation/_posts/0000-01-04-qa-for-turn-lanes.md deleted file mode 100644 index 85cfc3d..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-04-qa-for-turn-lanes.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -title: QA for turn lane data ---- - -While mapping turn lanes, there are a lot of scenarios are encountered in [#153](https://github.com/mapbox/mapping/issues/153) and [#144](https://github.com/mapbox/mapping/issues/144) mapping repos. All these scenarios are drafted in one place for validation purposes. - -## Different scenarios we came across while mapping - -### 1. Parking lanes - -In the U.S., when parallel parking spaces are marked, they are marked in one of [three ways](http://mutcd.fhwa.dot.gov/htm/2009/part3/fig3b_21_longdesc.htm): - - ![parking_lanes](https://cloud.githubusercontent.com/assets/8401827/13172245/326a7bb6-d71d-11e5-8617-a2516f75144b.png) - -Here’s an example of the box marking style: - - [![boxes](https://upload.wikimedia.org/wikipedia/commons/thumb/0/03/J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG/320px-J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG)](https://commons.wikimedia.org/wiki/File:J.S._Shingler_Bldg_%28East_face%29,_McLendon_St,_Ashburn.JPG) - -### 2. Counting number of turn lanes - -If there are no clear cut demarcations on the road and yet cars are parked on either sides of the road, consider them as drive lanes. Case below: - - ![number_of_lanes](https://cloud.githubusercontent.com/assets/8401827/13142482/5b26d0a0-d663-11e5-90cd-4a65d75e7248.png) - -### 3. Starting a turn lane - - Turn lanes should begin exactly as per the marking in the imagery, not before or after. - - ![turn:lanes_start](https://cloud.githubusercontent.com/assets/8401827/13110125/0fe83ad0-d5a4-11e5-82ff-00245d0ba043.png) - -### 4. Ending a turn lane - -Turn lanes should terminate at the first highway junction after the start of the turn lane. - - ![turn:lanes_end](https://cloud.githubusercontent.com/assets/8401827/13143057/4ff2b3c6-d667-11e5-8069-b028fabf7587.png) - -### 5. Turn lane forward - -In case of bi-directional ways, the key [turn:lanes:forward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the same direction as the osm-way; while adding this we must view the road in the direction to the osm-way (**on the direction where the osm-way arrow is pointing**). - - ![turn:lanes:forward](https://cloud.githubusercontent.com/assets/8401827/13175904/c5c922fc-d733-11e5-91b1-c0f9e5181fda.gif) - -### 6. Turn lane backward - -In case of bi-directional ways, the key [turn:lanes:backward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the opposite direction as the osm-way; while adding this we must view the road in the opposite direction to the osm-way (**opposite to direction where the osm-way arrow is pointing**). - - ![turn:lanes:backward](https://cloud.githubusercontent.com/assets/13744156/13172709/859957c4-d71f-11e5-8cd9-ea154ad5d2e8.gif) - - *Adding a `turn:lanes:backward` tag* - -### 7. Adding dual carriageways: - -When finding roads mapped as single carriageway while the imagery shows clear separation between roads, split the road where the physical separation starts and add dual carriageways. - -![dualcarriageway](https://cloud.githubusercontent.com/assets/8401827/13393542/117b59aa-df08-11e5-8fd3-21a931531f84.png) - - -**When to add dual carriageway?** -- Add Dual-carriage when - - you see physical separation betweens roads - - **no relation is attached to the way.** -- Add `turn:lanes` tag to both the ways. - - -### 8. Bicycle lanes and road shoulders - -Road shoulders and bicycle lanes are ignored from the lane count. Both these roads are `lanes=2` - - ![bicycle+shoulders](https://cloud.githubusercontent.com/assets/126868/11715007/628dd90a-9f64-11e5-9e22-58614d2afbf6.png) - - ![bicycle_lanes](https://cloud.githubusercontent.com/assets/13744156/13172922/adc69f08-d720-11e5-8600-7a606d2e9bae.png) - - *lanes=3 for the above example, ignoring the two cycle ways* - -* Ignore bicycle lanes even though they are in the middle;example below: - - ![xyz2](https://cloud.githubusercontent.com/assets/8401827/13495220/79a65aca-e16f-11e5-83e7-24d3e4f53ad0.png) - - *The middle way is also a biclcle lane which is not counted while adding the `lanes` tag* - -* Additionally, `Strava global-heat cycle` layer can used to verify if a particular lane is a cycle-way. -`tms[16]:http://globalheat.strava.com/tiles/cycling/color3/{zoom}/{x}/{y}.png` - -### 9. Lane marked as a separate way - -Do not add turn lanes in these cases where the only turn lane is already a mapped as a separate way. - - ![lane_as_separate_way](https://cloud.githubusercontent.com/assets/13744156/13173428/6694c468-d723-11e5-96be-b95502b9f58a.png) - -### 10. Bidirectional turn lanes - -These are the lanes marked with symbol representing both directions at a time. - - ![turn:lanes:both_ways](https://cloud.githubusercontent.com/assets/8401827/12642951/0162ff9c-c5df-11e5-8a14-a41f263ae086.png) - -Tag used for such lanes are `turn:lanes:both_ways=*` - -### 11. Mapillary Plugin to verify turn lanes - -The imagery at some places is not very clear and at-times the turn-lanes are covered by cars. In situations like these `Mapillary plugin` can be used. If there is Mapillary imagery coverage in that area, they can used to verify the presence of turn-lanes. - -**Name of the plugin:** Mapillary - - ![turnlanes_mapillary](https://cloud.githubusercontent.com/assets/4470913/12884912/6b405d1e-ce87-11e5-8d0f-cd8a8a8b3dfd.gif) - -### 12. Lanes with restricted access - -These are the areas on streets which are restricted for vehicular traffic. - -![screen shot 2016-03-15 at 3 36 36 pm](https://cloud.githubusercontent.com/assets/8401827/13776503/84c34002-ead0-11e5-911d-0581fe9173b7.png) - -![screen shot 2016-03-14 at 4 46 03 pm](https://cloud.githubusercontent.com/assets/8401827/13776504/84e64138-ead0-11e5-81f0-7918311ec6dc.png) - -![screen shot 2016-03-14 at 4 46 29 pm](https://cloud.githubusercontent.com/assets/8401827/13776505/84e71888-ead0-11e5-9135-553c11d99d12.png) - -In the above cases the areas with markings on the roads are not considered as a lane - -### 13. Reverse direction turn lanes - -These are the lanes specifically categorised to take U-turn or reverse-turn. - -![screen shot 2016-03-14 at 2 25 28 pm](https://cloud.githubusercontent.com/assets/8401827/13776502/84944b6c-ead0-11e5-92fa-0bb2951760ef.png) diff --git a/mapping-to-improve-navigation/_posts/0000-01-05-navigation-mapping-projects.md b/mapping-to-improve-navigation/_posts/0000-01-05-navigation-mapping-projects.md deleted file mode 100644 index 91862d9..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-05-navigation-mapping-projects.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Mapping projects related to navigation ---- - -Location | Description|Start|End(ETA)|Validation ----|---|---|---|---| -[Palo Alto - Redwood City](http://tasks.teachosm.org/project/119) | Trial run for estimates and workflow evaluation| 10/12/2015 | | | -[SF Peninsula](http://tasks.openstreetmap.us/project/17) | Turn lanes on motorway and trunk junctions in San Francisco Peninsula | 1/20/2016 | 2/05/2016 | Completed -[Turn lanes in Palo Alto - 1](http://tasks.openstreetmap.us/project/18) | Mapping turn lanes on highways tertiary and up in Palo Alto | 2/08/2016 | 2/09/2016 | Completed | -[Turn lanes in DC - 1](http://tasks.openstreetmap.us/project/19) | Mapping turn lanes on highways tertiary and up in DC | 2/08/2016 | 2/08/2016 | Completed | -[Turn lanes in SF city](http://tasks.openstreetmap.us/project/21) | Mapping turn lanes on highways tertiary and up in SF city | 2/09/2016 | 10/02/16 | Completed | -[Turn lanes in DC](http://tasks.openstreetmap.us/project/22) | Mapping turn lanes on highways tertiary and up in DC | 2/11/2016 | 2/12/2016 | Completed | -[Turn lanes in LA](http://tasks.openstreetmap.us/project/23) | Mapping turn lanes on highways tertiary and up in LA | 2/12/2016 | 3/29/2016 | Completed | -[Mapping Exit Numbers and Destinations in 30 US Cities](https://github.com/mapbox/mapping/issues/178) | Adding Exit numbers and Destinations for Top 30 US Cities | 4/01/2016 | 5/04/2016 | Completed | -[San Francisco](http://tasks.openstreetmap.us/project/35) | Mapping turn lanes on highways tertiary and up | 5/05/2016 | 5/11/2016 | Completed | -[Portland](http://tasks.openstreetmap.us/project/36) | Mapping turn lanes on highways tertiary and up | 5/16/2016 | 5/17/2016 | Completed | -[Dallas & Fort Worth](http://tasks.openstreetmap.us/project/37) | Mapping turn lanes on highways tertiary and up | 5/18/2016 |5/23/2016 | Completed | -[New York](http://tasks.openstreetmap.us/project/39) | Mapping turn lanes on highways tertiary and up |5/23/2016 |5/30/2016 |Completed | -[Detroit](http://tasks.openstreetmap.us/project/40) | Mapping turn lanes on highways tertiary and up |5/30/2016 | 6/02/2016 | Completed | -[Houston](http://tasks.openstreetmap.us/project/42) | Mapping turn lanes on highways tertiary and up | 6/03/2016 | 6/09/2016 | Completed | -[Philadelphia](http://tasks.openstreetmap.us/project/44) | Mapping turn lanes on highways tertiary and up | 6/08/2016 | 6/15/2016| Completed | -[Baltimore](http://tasks.openstreetmap.us/project/45) | Mapping turn lanes on highways tertiary and up | 6/15/2016 | 6/16/2016 | Completed | -[Oklahoma](http://tasks.openstreetmap.us/project/46) | Mapping turn lanes on highways tertiary and up | 6/22/2016 | 6/22/2016 | Completed | -[Boston](http://tasks.openstreetmap.us/project/47) | Mapping turn lanes on highways tertiary and up | 6/22/2016 | 06/27/2016 | Completed | -[Denver](http://tasks.openstreetmap.us/project/48) | Mapping turn lanes on highways tertiary and up | 6/28/2016 | 6/29/2016 | Completed | -[Seattle](http://tasks.openstreetmap.us/project/49) | Mapping turn lanes on highways tertiary and up | 6/29/2016 | 7/01/2016 | Completed | -[Mapping turn-restrictions for navigation in 30 cities in US](https://github.com/mapbox/mapping/issues/187) | To map turn-restrictions in 39 US cities using Mapillary as the source | 5/25/2016 | | | diff --git a/mapping-to-improve-navigation/index.md b/mapping-to-improve-navigation/index.md index 58e09f0..7342434 100644 --- a/mapping-to-improve-navigation/index.md +++ b/mapping-to-improve-navigation/index.md @@ -7,6 +7,4 @@ description: Learn the guidelines to map different components to help build a gr image: mapping-to-improve-navigation.svg --- -Navigational devices help people to get from one place to the other. The operation of such devices are largely dependent on quality of the underlying map data. Essentially this means the map data must consist of marked turn lanes, tagged one-ways roads, turn restrictions and so on. OpenStreetMap data includes all kinds of information to provide guidance in navigational devices by many modes including car, bicycle, foot and horse. In order to improve this data on OpenStreetMap, comprehensive mapping of turn lanes, turn restrictions, speed limits and oneways must be carried out. - -This is an effort to develop guidelines to map the different components which will ultimately help build a great navigational engine. Let's dive in: +This guide was designed to help anyone add navigation features in OpenStreetMap from scratch. Let's dive in: From a3078eefe3792aa3dd70c54b0280eb5a8116420e Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Mon, 24 Oct 2016 16:52:35 +0530 Subject: [PATCH 22/66] copy edits --- .../_posts/0000-01-02-modeling-roads-for-map-navigation.md | 1 - .../_posts/0000-01-03-road-features-mapping-guide.md | 1 + ...000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md | 1 - 3 files changed, 1 insertion(+), 2 deletions(-) diff --git a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md b/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md index 59cb86b..90f2f3c 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md +++ b/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md @@ -2,7 +2,6 @@ title: Modeling Roads for Map Navigation --- -## Data influence map A navigation map is influenced by several road characteristics, such as the turn restrictions, improper way of road tracing and road classification. The most important ones among those are: ### Road geometry diff --git a/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md b/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md index f8262e3..b4079aa 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md +++ b/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md @@ -30,6 +30,7 @@ The value of the key helps show the importance of the highway within the road ne Road classification may varies from country to country. The country specific use cases can be found in detail on separate wiki pages. For example, when mapping roads in India, the local community refer to the [India road tagging wiki](http://wiki.openstreetmap.org/wiki/India:Tags/Highway). Examples: + * [US roads classification](http://wiki.openstreetmap.org/wiki/United_States_Road_Classification) * [UK roads classification/numbering](https://en.wikipedia.org/wiki/Great_Britain_road_numbering_scheme) diff --git a/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md b/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md index c53f038..4ed219b 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md +++ b/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md @@ -1,4 +1,3 @@ - --- title: Mapping Guide for adding Turn Lanes from Imagery --- From 50a5f1317b2b2c08e4a05e8f6866903ff2f38b15 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Mon, 24 Oct 2016 17:02:26 +0530 Subject: [PATCH 23/66] copy edits --- .../_posts/0000-01-03-road-features-mapping-guide.md | 6 +++--- ...-mapillary.md => 0000-01-04-adding-turn-restrictions.md} | 2 +- ...n.md => 0000-01-05-adding-exit-and-destination-signs.md} | 2 +- ...anes-from-imagery.md => 0000-01-06-adding-turn-lanes.md} | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) rename mapping-to-improve-navigation/_posts/{0000-01-04-mapping-guide-for-adding-turn-restrictions-using-mapillary.md => 0000-01-04-adding-turn-restrictions.md} (99%) rename mapping-to-improve-navigation/_posts/{0000-01-05-mapping-guide-for-adding-exit-and-destination.md => 0000-01-05-adding-exit-and-destination-signs.md} (99%) rename mapping-to-improve-navigation/_posts/{0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md => 0000-01-06-adding-turn-lanes.md} (99%) diff --git a/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md b/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md index b4079aa..44660bc 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md +++ b/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md @@ -57,7 +57,7 @@ The best source of mapping oneways are again street level photos. * `type=restriction` * [OSM Wiki](http://wiki.openstreetmap.org/wiki/Relation:restriction) -* [Mapping guide](/mapping/mapping-to-improve-navigation/mapping-guide-for-adding-turn-restrictions-using-mapillary/) +* [Mapping guide](/mapping/mapping-to-improve-navigation/adding-turn-restrictions/) `type=restriction` is added to a relation in OpenStreetMap which is used to describe turn restrictions at junctions. The relation has a set of tags that describes the type of restriction, for example. `no_left_turn`, `no_right_turn`, `no_u_turn`, etc. These are traffic signs at junctions and this information must be present on the map to find the best route by the routing engine while planning a route. @@ -145,7 +145,7 @@ Street view photos from Mapillary, local mapping drives using [OpenStreetMap tra An example of a place with good exit/destination coverage in OpenStreetMap is [Ottawa, Canada](http://www.openstreetmap.org/#map=11/45.4283/-75.8331). These overpass queries for [destination](http://overpass-turbo.eu/s/i61) and [exit numbers](http://overpass-turbo.eu/s/i78) can be used to extract exit/destination data from OpenStreetMap. -The [detailed guide](/mapping/mapping-to-improve-navigation/mapping-guide-for-adding-exit-and-destination/) on adding exit and destination numbers can be followed for adding exit/destinations. This guide is specifically focused on North America (US/Canada) for now. +The [detailed guide](/mapping/mapping-to-improve-navigation/adding-exit-and-destination-signs/) on adding exit and destination numbers can be followed for adding exit/destinations. This guide is specifically focused on North America (US/Canada) for now. ### 2. Turn Lanes @@ -201,7 +201,7 @@ turn:lanes:backward=* Turn lanes can be mapped from high-resolution satellite imagery sources and street level photos. An example of the high density turn lane area in OpenStreetMap is [Los Angeles](https://www.openstreetmap.org/#map=11/33.9883/-118.3303). This [overpass query](http://overpass-turbo.eu/s/ipk) can be used to extract turn lanes data from OpenStreetMap -[Mapping guide for mapping turn lanes](/mapping/mapping-to-improve-navigation/mapping-guide-for-adding-turn-lanes-from-imagery/): This is a detailed mapping guide for adding turn lanes in general with specific focus on the US. It will be updated as more and more countries are mapped for lane information in OpenStreetMap. +[Mapping guide for mapping turn lanes](/mapping/mapping-to-improve-navigation/adding-turn-lanes/): This is a detailed mapping guide for adding turn lanes in general with specific focus on the US. It will be updated as more and more countries are mapped for lane information in OpenStreetMap. -- diff --git a/mapping-to-improve-navigation/_posts/0000-01-04-mapping-guide-for-adding-turn-restrictions-using-mapillary.md b/mapping-to-improve-navigation/_posts/0000-01-04-adding-turn-restrictions.md similarity index 99% rename from mapping-to-improve-navigation/_posts/0000-01-04-mapping-guide-for-adding-turn-restrictions-using-mapillary.md rename to mapping-to-improve-navigation/_posts/0000-01-04-adding-turn-restrictions.md index f27a2e5..b193dec 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-04-mapping-guide-for-adding-turn-restrictions-using-mapillary.md +++ b/mapping-to-improve-navigation/_posts/0000-01-04-adding-turn-restrictions.md @@ -1,5 +1,5 @@ --- -title: Mapping Guide for adding Turn Restrictions using Mapillary +title: Adding turn restrictions --- ## What are turn restrictions? diff --git a/mapping-to-improve-navigation/_posts/0000-01-05-mapping-guide-for-adding-exit-and-destination.md b/mapping-to-improve-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md similarity index 99% rename from mapping-to-improve-navigation/_posts/0000-01-05-mapping-guide-for-adding-exit-and-destination.md rename to mapping-to-improve-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md index 8903d7b..1a62fe6 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-05-mapping-guide-for-adding-exit-and-destination.md +++ b/mapping-to-improve-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md @@ -1,5 +1,5 @@ --- -title: Mapping guide for exit and destination +title: Adding exit and destination signs --- ![5138660996_1957ee06ed_o](https://cloud.githubusercontent.com/assets/17887418/15180552/ec541b64-179f-11e6-88d7-4b3074f161e4.jpg) diff --git a/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md b/mapping-to-improve-navigation/_posts/0000-01-06-adding-turn-lanes.md similarity index 99% rename from mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md rename to mapping-to-improve-navigation/_posts/0000-01-06-adding-turn-lanes.md index 4ed219b..24c5b7d 100644 --- a/mapping-to-improve-navigation/_posts/0000-01-06-mapping-guide-for-adding-turn-lanes-from-imagery.md +++ b/mapping-to-improve-navigation/_posts/0000-01-06-adding-turn-lanes.md @@ -1,5 +1,5 @@ --- -title: Mapping Guide for adding Turn Lanes from Imagery +title: Adding turn lanes --- ## What is a turn lane From 822a31d6a2da4312ec786a3e5e84100fe0d2df51 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Mon, 24 Oct 2016 17:06:48 +0530 Subject: [PATCH 24/66] copy edits --- mapping-to-improve-navigation/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mapping-to-improve-navigation/index.md b/mapping-to-improve-navigation/index.md index 7342434..00e5a9c 100644 --- a/mapping-to-improve-navigation/index.md +++ b/mapping-to-improve-navigation/index.md @@ -1,5 +1,5 @@ --- -title: Mapping to improve navigation +title: Mapping for navigation layout: category order: 6 color: orange From 8df44f9b3123759f13b85c87583760de0854be51 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Mon, 24 Oct 2016 17:19:19 +0530 Subject: [PATCH 25/66] copy edits --- .../index.md | 0 .../_posts/0000-01-01-introduction.md | 86 ------ ...01-02-modeling-roads-for-map-navigation.md | 86 ------ .../0000-01-03-road-features-mapping-guide.md | 217 --------------- .../0000-01-04-adding-turn-restrictions.md | 251 ------------------ ...01-05-adding-exit-and-destination-signs.md | 135 ---------- .../_posts/0000-01-06-adding-turn-lanes.md | 247 ----------------- .../0000-01-07-resources-and-references.md | 49 ---- 8 files changed, 1071 deletions(-) rename {mapping-to-improve-navigation => mapping-for-navigation}/index.md (100%) delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-01-introduction.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-04-adding-turn-restrictions.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-06-adding-turn-lanes.md delete mode 100644 mapping-to-improve-navigation/_posts/0000-01-07-resources-and-references.md diff --git a/mapping-to-improve-navigation/index.md b/mapping-for-navigation/index.md similarity index 100% rename from mapping-to-improve-navigation/index.md rename to mapping-for-navigation/index.md diff --git a/mapping-to-improve-navigation/_posts/0000-01-01-introduction.md b/mapping-to-improve-navigation/_posts/0000-01-01-introduction.md deleted file mode 100644 index 5e42863..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-01-introduction.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: Introduction ---- - -The most basic use of a map is to find out where one is located. After that, one usually wants to use the map to find the best route to another location. On a [digital map](https://en.wikipedia.org/wiki/Digital_mapping), this is usually provided with [turn by turn navigation](https://en.wikipedia.org/wiki/Turn-by-turn_navigation) using a [navigation device](https://en.wikipedia.org/wiki/GPS_navigation_device). - -![navigation_optimized](https://cloud.githubusercontent.com/assets/13744156/18119269/76493c6c-6f77-11e6-8c18-a1daf7845f0b.gif) -_Let the computer find the best route for you!_ - -## Components of map navigation - -A navigations system has user facing components that interact with the user and back end components that computes the best route based on the user input and available data. In this guide we will focus on the back end components that rely on map data. - -**User facing components** -- User interface controls for setting the the origin and destination -- Map display that visually represents the route to take -- Turn by turn instructions that accurately describe the navigation maneuvers at the appropriate time -- Route status that includes current progress and the estimated time of arrival (ETA) at the destination - -**Back end components** -- A navigation profile that describes the mode of transport to use for the routing algorithm (eg. truck, cycle or foot) -- A route finder that finds the best possible route between the origin and destination for the selected navigation profile -- A guidance system that converts the route into instructions for turn by turn navigation - -### Navigation profile - -The navigation profile accurately describes the preferred types of roads to take based on the mode of transport used. A walking profile will have a fairly constant walking speed on any type of road, while a car profile will have avery high traveling speed on a motorway and will be much slower on a residential road. This has a large influence on the route finder. - -![screenshot_20160831-124644](https://cloud.githubusercontent.com/assets/8401827/18120537/b392baac-6f7d-11e6-9e36-480b3145c429.png) - -*Different routing profiles: cars, walking, bicycle.* - -### Routing - -[Routing](http://wiki.openstreetmap.org/wiki/Routing) is the process of selecting the best path in a network interconnected of roads on the map. Every road segment on the map has a traveling speed calculated based on various road factors, and the fastest and safest route is selected from all possible combinations. - -![](https://farm4.staticflickr.com/3814/12241013316_df99a4ff83_o.png)
-_Finding the route between two points involves complex calculations on a [routing graph](https://www.mapbox.com/blog/smart-directions-with-osrm-graph-model/)_ - -The calculation of an accurate route depends on a variety of factors which are taken into account by the routing algorithm: - -* Personal factors: fastest route, most scenic route, quietest route, shortest route, facilities needed, toll rates -* Vehicle factors: mode of transport, physical category of vehicle, optimum traveling speed, riding surface requirements, fueling requirements -* Route factors (static): classification of road, access restrictions, speed limits, turn restrictions, oneway rules, number of lanes -* Traffic factors (dynamic): traffic conditions, traffic signal cycle duration, weather conditions -* Riding surface factors: surface material, smoothness, barriers, speed breakers, road width, lane width, age - -### Guidance - -![](https://cloud.githubusercontent.com/assets/12932279/16989362/402b3f44-4e94-11e6-8e8a-a60cf0b08705.png) -_A route is converted into a series of easy to follow instructions for the user_ - -Route guidance is used to lead a person through the determined path. Once the routing algorithm determines the best path, that route is converted into a set of human-readable instructions known as guidance. The guidance represents the street names, the turn lanes marked on the roads, exit numbers, and destinations shown on sign boards. Accurate and relevant guidance can greatly enhance the user experience of using the map for navigation. - -## Navigating the future - -Providing accurate navigation using maps is dependent on having detailed and updated data about the world. The world is transforming every second and the next generation of navigation will need to have the latest information about the world that will come from various sources. - -### Telemetry - -screenshot 2016-09-15 21 27 43 -_Telemetry traces of Strava users from [Strava Globalheatmap](http://labs.strava.com/heatmap/#14/-74.02871/40.70159/blue/both)_ - -Telemetry is the remote collection of data which can be physical, environmental or biological. Most internet and GPS enabled phones collect location and other environmental data and reports it to a central service that can aggregate the data to determine traffic conditions on a road. - - -### Forward facing cameras & Street-view - -![untitled2](https://cloud.githubusercontent.com/assets/126868/18557457/a667474c-7b8c-11e6-844b-e308c650a8b1.gif) -_Crowdsourced streetview photographs from [narrow alleys in India using Mapillary](https://www.mapillary.com/app/?lat=23.018631999999997&lng=72.595325&z=17&pKey=4tjlrGmABA2sxmLLmAIq9Q&focus=photo)_ - -Street view images from dashcams, mounted cameras in vehicles using apps gives highly detailed 360° view of streets. This can help detect traffic signage, access restrictions, traffic signals, road markings to help add and confirm ground features into a map. Opensource street view photos include [Mapillary](https://www.mapillary.com/) and [OpenStreetView](http://openstreetview.com/). - -### Live Aerial & Drone Imagery - -screenshot 2016-09-15 21 34 33
-_High resolution imagery captured from [UAVs in Srilanka](https://www.mapbox.com/blog/sri-lanka-drone-imagery/)_ - -[Aerial imagery](https://en.wikipedia.org/wiki/Aerial_photography) using drones can capture the changing surface of the earth at a much higher resolution and lower cost compared to traditional satellite imagery that is expensive to acquire and are updated less frequently. - -### Machine learning and image recognition - -![untitled2](https://cloud.githubusercontent.com/assets/126868/18557642/4fba4e8e-7b8d-11e6-85fb-c30092aac39b.gif)
-_Automatic image segmentation by [Mapillary](http://blog.mapillary.com/update/2016/05/19/austria.html)_ - -Advances in [machine learning](https://en.wikipedia.org/wiki/Machine_learning) opens up opportunities to automate manual tasks like [digitization of roads from satellite](http://stateofthemap.us/2016/skynet/) imagery and can accelerate the creation and maintenance of map data. \ No newline at end of file diff --git a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md b/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md deleted file mode 100644 index 90f2f3c..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: Modeling Roads for Map Navigation ---- - -A navigation map is influenced by several road characteristics, such as the turn restrictions, improper way of road tracing and road classification. The most important ones among those are: - -### Road geometry -Roads are the main features that are used for rendering a route in all navigational applications. Correct road mapping leads not only to the well-looking map but also to better navigation experience. With the change in the shape of the traced road, the distance covered will be altered which affects the route. The common approach for road mapping is to trace roads following the center-line from satellite imagery. - -![road_with_two_lanes](https://cloud.githubusercontent.com/assets/369696/13230189/1bc4b308-d9ad-11e5-88b7-f85fcd290926.png) - -*Roads on satellite imagery* - -### Road connectivity / topology: -If you want to travel from point A to point E as shown in the below image, you can either travel from `A to B, B to C and then C to E` or `A to B, B to D and then D to E`. - -![screen shot 2016-08-30 at 6 51 58 pm](https://cloud.githubusercontent.com/assets/8401827/18090553/e4e4eabc-6ee2-11e6-9908-8c9064c833af.png) - -But, if you have a restriction to enter D from A, the only possible route will be `A to B, B to C and then C to E`. This is where connectivity plays a major role in deciding the final route. - -### Road attributes / properties: -If `A to C` is a primary road which is crossing through a service road `B to D` and you want to travel from `A to E`, the navigation map comes up with the route traveling from `A to B, B to C and then C to E` and completely avoids `A to B, B to D and then D to E` because the travel on Primary road is much efficient than a narrow service road. This is how the attributes / properties with which the road is assigned with plays a crucial role in deciding the final route. - -![screen shot 2016-08-30 at 8 30 14 pm](https://cloud.githubusercontent.com/assets/8401827/18094299/9d9f5454-6ef0-11e6-85de-4f74a43d5657.png) - -## OpenStreetMap data model: - -The OpenStreetMap data model consists of nodes, ways, relations, and tags. A detailed description of the data model can be found in the [The OpenStreetMap Data Model](https://github.com/mapbox/mapping/wiki/The%20OpenStreetMap%20Data%20Model) guide. - -Navigation data is similarly a combination of nodes, ways, relations, and tags. Some of the examples are illustrated below: - -### Examples - -* Nodes: - - Exit numbers: - -![screen shot 2016-08-30 at 5 20 44 pm](https://cloud.githubusercontent.com/assets/13744156/18088263/517c2cf0-6ed7-11e6-8485-2d2761c42e84.png) - -* Ways: - - Highway=* - -![screen shot 2016-08-30 at 6 17 55 pm](https://cloud.githubusercontent.com/assets/13744156/18089616/6d060d0e-6ede-11e6-829d-47fc464a53a1.png) - -*An way tagged with highway=secondary tag* - -* Relations: - - Turn restrictions are a combination of nodes, ways, tags, and relations. It consists of `from way` `via node` and `to way`, tied together by a `restriction=*` relation. - - -![tr_relation](https://cloud.githubusercontent.com/assets/13744156/18089141/0c296c9e-6edc-11e6-916f-716e41c9f685.gif) - -* Tags: All the navigation features are differentiated and defined based on how they are tagged. Tags can be on any element: on nodes, ways, and relations. - -Examples are: `destination=*`, `ref=*`, `turn:lanes=*`, `restriction=*`, etc. - -## Tracing roads - -Before tracing, we need to inspect the start and endpoints of the road segment. We need to identify the road direction, general numbers of lanes and the places where there are extra lanes. Based on this we choose our strategy for tracing. - -We are not able to draw a road on its center line, especially if roads join/fork or the number of lanes change. Imagine two roads which join: how would you draw the OSM-way around the point where the roads join? - - ![center_line](https://wiki.openstreetmap.org/w/images/4/47/Lane_Placement_2.png) - - _Center line tracing_ - - ![main_direction](https://wiki.openstreetmap.org/w/images/e/e4/Lane_Placement_3.png) - - _Tracing based on road direction_ - -### Tracing roads with more than two lanes - -There are two cases: -- Dual carriageway roads - - ![dual_carriageway_road](https://cloud.githubusercontent.com/assets/369696/13230427/fe21579c-d9ad-11e5-86ba-38107d469c54.png) - -These are bidirectional roads which have a physical separation between the lanes in both the directions. Both the ways will be counted for lanes and will be tagged with `lanes=*`. Dual carriageways are always `oneway` roads. - -![motorway](https://cloud.githubusercontent.com/assets/369696/13231932/5b417e00-d9b5-11e5-854e-dbed2d209d7c.png) -*Placement of nodes of the lines in each direction, opposite to each other* - -- Roads which carry traffic in both directions (Bidirectional roads) - - ![bidirectional_road](https://cloud.githubusercontent.com/assets/369696/13230341/9f9db6c0-d9ad-11e5-9f5d-53dd80b40f67.png) -*Road carrying traffic in both directions* - diff --git a/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md b/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md deleted file mode 100644 index 44660bc..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-03-road-features-mapping-guide.md +++ /dev/null @@ -1,217 +0,0 @@ ---- -title: Road Features Mapping Guide ---- - -*Detailed guide mapping features for navigation on the OpenStreetMap project. Before you start, please read the guide on [Mapping with OpenStreetMap](https://www.mapbox.com/mapping/)* - -[Query OpenStreetMap for Navigation Data via Overpass](http://overpass-turbo.eu/s/iyB) - -## Routing features - -These are features that help the routing engine find the safest and fastest route between two points. - - -### 1. Functional Road Class - -* `highway=*` -* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:highway) - -Roads are categorized according to its order of importance. They are tagged with the `highway=*`. The general order of importance for way types are: - -``` xml -highway= motorway > trunk > primary > secondary > ... > living streets > ... > footway -``` -![screen shot 2016-08-29 at 1 50 04 pm](https://cloud.githubusercontent.com/assets/13744156/18045336/ff8f31ea-6def-11e6-8692-bb4e082b94b8.png) - -*`highway=primary` in San Francisco* - -The value of the key helps show the importance of the highway within the road network as a whole. The importance ranges from the most important `motorway` to the least important `service`. The routing engine takes into account this importance of classification when determining optimum routes. - -Road classification may varies from country to country. The country specific use cases can be found in detail on separate wiki pages. For example, when mapping roads in India, the local community refer to the [India road tagging wiki](http://wiki.openstreetmap.org/wiki/India:Tags/Highway). - -Examples: - -* [US roads classification](http://wiki.openstreetmap.org/wiki/United_States_Road_Classification) -* [UK roads classification/numbering](https://en.wikipedia.org/wiki/Great_Britain_road_numbering_scheme) - -For an example of an area with a good concentration of different classes of roads on OpenStreetMap, look at [San Francisco](https://www.openstreetmap.org/#map=14/37.7788/-122.4375) area. This [osm query](http://overpass-turbo.eu/s/i4y) can be used to extract and gather numbers of all the highways present in a given bounding box on OpenStreetMap. - -[Department of Transportation](https://www.fhwa.dot.gov/about/webstate.cfm) websites and [wikipedia](https://en.wikipedia.org/wiki/United_States_Numbered_Highways) are some of the primary sources for highway information. - -### 2. Oneways - -* `oneway=yes` -* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:oneway) - -Oneways generally refer to road segments which allow traffic in only one direction. There are also streets which have oneway characteristics for only on certain times of the day to regulate traffic. - -![screen shot 2016-08-29 at 5 47 47 pm](https://cloud.githubusercontent.com/assets/13744156/18051463/5fdc162c-6e12-11e6-8984-c48da11bf73f.png) - -*`oneway=yes` shown in Mapillary* - -The best source of mapping oneways are again street level photos. - -[San Francisco](https://www.openstreetmap.org/#map=12/37.7574/-122.4845) is one area which has been well mapped for oneways in OpenStreetMap. This [overpass query](http://overpass-turbo.eu/s/i50) can be used to extract oneways from OpenStreetMap data. - -### 3. Turn-Restrictions - -* `type=restriction` -* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Relation:restriction) -* [Mapping guide](/mapping/mapping-to-improve-navigation/adding-turn-restrictions/) - -`type=restriction` is added to a relation in OpenStreetMap which is used to describe turn restrictions at junctions. The relation has a set of tags that describes the type of restriction, for example. `no_left_turn`, `no_right_turn`, `no_u_turn`, etc. These are traffic signs at junctions and this information must be present on the map to find the best route by the routing engine while planning a route. - -![screen shot 2016-03-08 at 8 05 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604633/ad8bff4a-e569-11e5-9198-3ac9c88e5619.png) - -*Turn restriction denoting `no left turn` along with conditions: opening and closing times* - -The main resource for turn restriction data is [street view level images](https://www.mapbox.com/blog/safer-market-street/), local mapping drives, [DOT websites](http://www1.toronto.ca/wps/portal/contentonly?vgnextoid=83f6e69ae554e410VgnVCM10000071d60f89RCRD) - -![turn_restriction](https://cloud.githubusercontent.com/assets/13744156/18047415/7d9254c8-6dfa-11e6-94e6-9d85b58627c1.jpg) -*turn restriction which denotes `no right turn` at the junction* - -[San Francisco](https://www.openstreetmap.org/#map=13/37.7696/-122.4891) in OpenStreetMap has an excellent coverage of turn by turn restrictions at junctions. This [overpass query](http://overpass-turbo.eu/s/i4G) can be used to extract current turn restriction in a bounding box. - -### 4. Speed limits - -* `maxspeed=60` or `maxpseed=40 mph` -* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:maxspeed) - -The `maxspeed=*` tag defines the maximum legal speed limit for general traffic on a particular road, railway or waterway. The max speed values will be interpreted as kilometers per hour by default. The `maxspeed=*` is an important part of routing as it is used in determining the shortest time taken by a specific route to reach a destination. In the case of two routes, the one with the shortest time (higher maxspeed) and shortest distance will be considered as the optimum route. - - -![maxspeed](https://cloud.githubusercontent.com/assets/13744156/18046639/6602224c-6df6-11e6-8884-18a58bf4835a.jpg) - -*Maxspeed sign shown in Mapillary* - -The main data sources for detecting maxspeed signs are: [street view photos](https://www.mapbox.com/blog/mapillary-mapping/), [wikipedia](https://en.wikipedia.org/wiki/Speed_limits_in_Canada), [DOT documents](http://www.qld.gov.au/transport/safety/rules/speed-limits/index.html). - -The `maxspeed=*` data on OpenStreetMap (for example, in [London](https://www.openstreetmap.org/#map=14/51.5059/-0.1061)) in an area can be extracted by this [overpass query](http://overpass-turbo.eu/s/i4z). - - -### 5. Access-Restrictions - -* `access=*` -* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:access) - -Apart from turn restrictions, there are access restrictions for different parts of highways. Some of these tags are `access=no`, `access=private` etc which will end up altering the route to be taken during the journey. For more information on the various kinds of `access=*` tags take a look at [Key:access](http://wiki.openstreetmap.org/wiki/Key:access) and [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions) and [access restrictions](http://wiki.openstreetmap.org/wiki/OpenStreetMap_tags_for_routing/Access-Restrictions) - -![749px-mutcd_r5-7](https://cloud.githubusercontent.com/assets/13744156/18048743/b688e696-6e01-11e6-80ae-e65ce6743830.png) - -*An `access=no` for non-motorized traffic, ends up altering the route for bicycle profiles, source: US MUTDC* - -All the `access=private` tags on OpenStreetMap ways, which will not allow that segment of the way to be used in a route can be extracted from this [overpass query](http://overpass-turbo.eu/s/i4J). An example of well-mapped access restrictions in OpenStreetMap can be found in [London](https://www.openstreetmap.org/#map=13/51.5061/-0.1366). - -The sources for mapping access restrictions in OpenStreetMap are: [street view photos](http://blog.mapillary.com/update/2016/05/24/use-mapillary-editing-OpenStreetMap.html), local mapping drives. - -### 6. Traffic signals - -Traffic signals such as: `highway=traffic_signals`, `highway=stop` or `barrier=toll_booth` as well as `traffic_calming=*` are considered during routing. The `type=restriction` more commonly referred to as **turn restrictions** are traffic signage which prohibits certain turns in intersections are also a crucial part of a great `routing` engine. - -More details on mapping `traffic signals` for cars and pedestrians can be found in the [OpenStreetMap wiki](http://wiki.openstreetmap.org/wiki/Tag:highway%3Dtraffic_signals). - -Street view photos from Mapillary, local mapping drives using [OpenStreetMap tracker](http://wiki.openstreetmap.org/wiki/OpenStreetMapTracker_(Android)) can be used as sources to map traffic signals in OpenStreetMap. - -![800px-led_traffic_lights](https://cloud.githubusercontent.com/assets/13744156/18049581/cc237796-6e06-11e6-8d51-b8d446b2c3dc.jpg) - -*Traffic signal in a junction* - - -## Guidance features - -## 1. Exit & destination signs - -**What are exit numbers?** - * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. - - ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) - -**Different tags for exit numbers:** -* `ref=*` is used when the exit has a specific number assigned to it. -* `noref=yes` is used when the exit doesn't have any official number assigned to it. - -**What are destination tags?** - -* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. -* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. - -![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) - -#### Different tags for destinations: -* `destination` tag refers to the place that the way exiting from the freeway leads to. -* `destination:ref` is the reference of the roads directly ahead. -* `destination:ref:to` is to specify the reference of a major highway ahead. -* `destination:street` refers to the main street the way exiting from the freeway leads to. - -An example of a place with good exit/destination coverage in OpenStreetMap is [Ottawa, Canada](http://www.openstreetmap.org/#map=11/45.4283/-75.8331). These overpass queries for [destination](http://overpass-turbo.eu/s/i61) and [exit numbers](http://overpass-turbo.eu/s/i78) can be used to extract exit/destination data from OpenStreetMap. - -The [detailed guide](/mapping/mapping-to-improve-navigation/adding-exit-and-destination-signs/) on adding exit and destination numbers can be followed for adding exit/destinations. This guide is specifically focused on North America (US/Canada) for now. - -### 2. Turn Lanes - -As discussed in `Modeling Roads for navigation` page, there are two types of roads: unidirectional and bidirectional. `lanes=*` tag is used to count the number of lanes in both these type of roads. - -To set number of [lanes](http://wiki.openstreetmap.org/wiki/Key:lanes) for roads which carry traffic in both directions use [`:backward` and `:forward` suffixes](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right#Forward_and_backward) - -`Forward` means the direction in which the way is drawn in OpenStreetMap, while `backward` means the opposite direction. - -``` xml -Example: - highway=tertiary - lanes=5 - lanes:forward=3 - lanes:backward=2 -``` - -In the image below, the number of lanes is two - `lanes=2`. Orange line is the center line of bidirectional way which is the main way direction. When the extra lane starts in a bidirectional way, that segment is tagged as `lanes=3`+`lanes:forward=2`+`lanes:backward=1`. Optionally, we specify [placement](https://wiki.openstreetmap.org/wiki/Proposed_features/placement) of the lanes relative to the way. - - ![residential_road_2](https://cloud.githubusercontent.com/assets/369696/13228435/ae570094-d9a4-11e5-9f3c-4737112a7932.png) - -The below image have two tagging variants: - 1. `lanes=2` - 1 lane for each direction, or - 2. `lanes=3` - denote middle lane for left turn as (:point_left: _this is [discussed](http://wiki.openstreetmap.org/wiki/Proposed_features/Suffix_both_ways)_) - - ``` -highway=residential -lanes=3 -lanes:forward=1 -lanes:backward=1 -lanes:both_ways=1 -turn:lanes:both_ways=left - ``` - ![residential_road_3](https://cloud.githubusercontent.com/assets/369696/13229045/ab01d6f0-d9a7-11e5-8d8a-1fe5518c84a5.png) - - IN case the number of lanes is even but numbers of lanes for each direction not equal. :point_down: - - ![trunk_link](https://cloud.githubusercontent.com/assets/369696/13229897/b09a811c-d9ab-11e5-935e-25906c94585b.png) - -[Turn lanes](http://wiki.openstreetmap.org/wiki/Key:turn#Turning_indications_per_lane) have an influence on the path finding and are one of the most vital components for proper guidance. Choosing the correct turn lane can have a big influence in navigation. Oftentimes, they only help to illustrate a turn better but other times, they are vitally important. In guidance, the aim is to provide a set of instructions, like keep right or keep left by describing the optimum route found by the routing algorithm to a driver. - -![screen shot 2016-03-08 at 7 51 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604319/236e84dc-e568-11e5-850a-cf398719db11.png) - -*How a driver views turn lanes from the car. For a single direction way, it will be tagged `turn:lanes=left|left;through` while for a bidirectional way it will be tagged `turn:lanes:forward/turn:lanes:backward=left|left|through` depending upon OpenStreetMap way direction* - -There are three turn lanes tags in OpenStreetMap: - -``` xml -turn:lanes=* -turn:lanes:forward=* -turn:lanes:backward=* -``` - -Turn lanes can be mapped from high-resolution satellite imagery sources and street level photos. An example of the high density turn lane area in OpenStreetMap is [Los Angeles](https://www.openstreetmap.org/#map=11/33.9883/-118.3303). This [overpass query](http://overpass-turbo.eu/s/ipk) can be used to extract turn lanes data from OpenStreetMap - -[Mapping guide for mapping turn lanes](/mapping/mapping-to-improve-navigation/adding-turn-lanes/): This is a detailed mapping guide for adding turn lanes in general with specific focus on the US. It will be updated as more and more countries are mapped for lane information in OpenStreetMap. - - --- - -The other important attributes in besides `turn:lanes` and `exit/destination` data required to provide the better guidance using OpenStreetMap data are: -``` xml -lanes=* -name=* -ref=* -relation:route -``` - -Information for [lanes](http://wiki.openstreetmap.org/wiki/Key:lanes), [highway names](http://wiki.openstreetmap.org/wiki/Highways), [highway ref](http://wiki.openstreetmap.org/wiki/Key:ref) and [relation:route](http://wiki.openstreetmap.org/wiki/Relation:route) can be found in their respective OpenStreetMap wikis. \ No newline at end of file diff --git a/mapping-to-improve-navigation/_posts/0000-01-04-adding-turn-restrictions.md b/mapping-to-improve-navigation/_posts/0000-01-04-adding-turn-restrictions.md deleted file mode 100644 index b193dec..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-04-adding-turn-restrictions.md +++ /dev/null @@ -1,251 +0,0 @@ ---- -title: Adding turn restrictions ---- -## What are turn restrictions? - -A turn restriction at a junction is represented by a [relation](http://wiki.openstreetmap.org/wiki/Relation) that has a set of tags describing the type of turn restriction. Turn restrictions, like `No-left-turn` and `No-U-turn`, regulate traffic flow at intersections and accurately mapping them is critical for calculating valid routes on a map. - -![image](https://cloud.githubusercontent.com/assets/3423533/15504805/5d678d70-21de-11e6-8290-d20db2380d4d.png) - -## Traffic signs to be added - -Refer to the table given below to spot/match the traffic sign in the Mapillary image against the list of traffic signs and it also consists of the OSM tags: - - -Symbol | Description | OSM Tag | Node/Way/Relation | ------- | ----------- | ------- | ----------------- | -![](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a9/MUTCD_R3-27.svg/80px-MUTCD_R3-27.svg.png)| No straight through | restriction=no_straight_on | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | -![](https://upload.wikimedia.org/wikipedia/commons/thumb/8/8f/MUTCD_R3-1.svg/80px-MUTCD_R3-1.svg.png)| No Right Turn | restriction=no_right_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | -![](https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/MUTCD_R3-2.svg/80px-MUTCD_R3-2.svg.png)| No Left Turn | restriction=no_left_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | -![](https://upload.wikimedia.org/wikipedia/commons/thumb/2/2b/MUTCD_R3-3.svg/80px-MUTCD_R3-3.svg.png)| No Turns | restriction=only_straight_on | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | -![](https://upload.wikimedia.org/wikipedia/commons/thumb/d/d1/MUTCD_R3-4.svg/80px-MUTCD_R3-4.svg.png)| No U-turn | restriction=no_u_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | -![](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a1/MUTCD_R3-18.svg/80px-MUTCD_R3-18.svg.png)| No Left or U-turn | restriction=no_left_turn; restriction=no_u_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | - - _The last two columns of the table enlists the correct tagging convention for adding the traffic data to OpenStreetMap._ - - -## Using OSM Navigation Map - -The [Navigation map](http://mapbox.github.io/osm-navigation-map/) helps us in recognizing the detected signage overlay from Mapillary on the map. These signage are represented using small circles in 3 colours: - -- **Green** - to be validated -- **Blue** - Reviewed and found valid -- **Yellow** - Reviewed and found redundant -- **Red** - Reviewed and found invalid - -When we click on the green circle, the area is automatically opened in JOSM and popup to select the review is opened in the Navigation map. The same can be opened in iD editor by clicking on **Edit Map** button on top right of the popup. Once done with the review, please add your OSM username. - -![](https://cloud.githubusercontent.com/assets/126868/16987647/ffa78c4a-4eaa-11e6-8bfd-b509b20e482b.gif) - - -## Mapping turn restrictions with iD editor - -The new version of iD, the web editor for OpenStreetMap, makes it even simpler to add turn restrictions to OpenStreetMap. - -### Adding Absolute Turn Restriction: -![epl4xsg](https://cloud.githubusercontent.com/assets/17887418/17285386/fe7453f6-57df-11e6-9d1d-e65ba060bc0b.gif) - -### Adding Conditional Turn Restriction: - ![conditional tr](https://cloud.githubusercontent.com/assets/17887418/17285391/055b6240-57e0-11e6-9c9f-16880b5c6cd2.gif) - -#### Mapillary overlay and Traffic Sign Overlay: - Mapillary has an efficient tool in iD that helps in seeing detected restrictions. Here's how you enable it: - - ![traffic overlay mapillary](https://cloud.githubusercontent.com/assets/17887418/17285393/069163a8-57e0-11e6-9564-293d91b276bc.gif) - -#### Pain Points in adding Turn Restrictions in iD editor: -1. iD editor provides no way of adding a `no_u_turn` restrictions via way. If there is a via way `no_u_turn`, you have to add it using JOSM editor. - - ![image](https://cloud.githubusercontent.com/assets/17887418/17285567/1a145830-57e1-11e6-8e2f-0581bc16695e.png) - -2. In certain cases, adding [no_u_turn turn via node](https://github.com/mapbox/mapping/issues/213#issuecomment-234221535) is also not possible. For such cases, it is better to add it using JOSM. - - -# Mapping turn restrictions with JOSM - -In order to be able to map traffic data easily, there are some plugins that JOSM needs to be configured with: - - - **Plugins to be downloaded**: - - [Mapillary plugin for JOSM](http://blog.mapillary.com/update/2015/06/25/josm-mapillary.html): This plugin allows the user to view mapillary images in JOSM. - - [Turn restrictions plugin for JOSM](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Turnrestrictions): This plugin allows to add turn restrictions to the selected roads with ease. - - ![mapi_plugins](https://cloud.githubusercontent.com/assets/1933377/11438854/cf4768fa-951d-11e5-819a-737d2e03342c.gif) - - - **Map-paint styles to be added**: - - traffic_signs: It displays all the existing traffic signs that have been already mapped on OSM. - - ![mapi_paint](https://cloud.githubusercontent.com/assets/1933377/11442184/3493f780-9539-11e5-985a-ac6a9095dcee.gif) - -## Guide to use the mapillary and turn restriction plugins - - **Using the Mapillary plugin** - - - The Mapillary imagery can be added by clicking on `imagery -> Mapillary` in JOSM. This will add the mapillary layer - over the dataset layer. - - The explanation for how the plugin works can be found [here](http://blog.mapillary.com/update/2015/06/25/josm-mapillary.html). - - **Note**: Every time a new data layer is added, you need to delete the existing **Mapillary layer** and add a new one - -**Using the turn restriction plugin** - - The explanation for how the turn restriction plugin works - can be found [here](http://overpass-turbo.eu/s/gTO). - - -## Start mapping Turn Restrictions - -- This **[Over-pass query](http://overpass-turbo.eu/s/grv)** can be used to get the current count of turn-restrictions present in a city that one is going to work on. This will help us in determining the current state of restrictions and further help in calculating the number of restrictions added by the team. - -**Note:** Change the city name in the above query - -- Use the **[navigation data coverage on OSM](http://mapbox.github.io/osm-navigation-map/#9.56/37.8188/-122.5575) map** to spot the Mapillary signage detections. -- Turn on the `Turn Restrictions`, `Oneways` and `Mapillary Street Photos` layers in the above map -- Click on the turn-restriction traffic symbols detected by Mapillary (which are denoted by green dots on the map) for it to open in JOSM. - - ![navigation](https://cloud.githubusercontent.com/assets/4470913/15466843/26bd5588-20f9-11e6-9eaa-0126e5c83c39.gif) - -- In the Mapillary layer in JOSM, detected traffic signs are represented by a tiny `red triangle` next to the green arrow. Please note that this layer might not be up-to-date. - - ![screen shot 2015-11-27 at 1 41 55 pm](https://cloud.githubusercontent.com/assets/4470913/11436699/1fa70b72-950d-11e5-8e05-9e09013c1f64.png) - -- Probe the previous and next images as well as the satellite imagery data to get a clear idea of the surroundings and then compare them with the existing Mapillary image to find the exact location of the `traffic-sign`. - - ![turn_res](https://cloud.githubusercontent.com/assets/1933377/11443497/a109430c-9543-11e5-8ef9-6907269d6145.gif) - -- Be cautious while adding an `U-turn` via a way in OSM, here is how you add it: - - Select the participating ways - - Go to `Presets -> Relations -> Turn Restrictions` - - Select `no_u_turn` in the `Restriction` field from the drop-down and click on `New Relation` - - In the `Members` section add the respective roles for all the ways enlisted - - - ![u-turn](https://cloud.githubusercontent.com/assets/4470913/15538899/ae22ff9c-229c-11e6-8d82-08b9e18c5540.gif) - - - **Note** - - To get a better idea about the area/road and to see the clear image, always inspect multiple consecutive images. - - With the help of the plugins, look for **traffic restrictions icons** at junctions which are already present on the road/area. - - We should avoid adding `turn restriction` to roads that are leading to one-ways going in the opposite direction, like the example below. It will only result in redundant data: - - ![screen_shot_2015-11-30_at_11_36_26_pm](https://cloud.githubusercontent.com/assets/4470913/11480317/deeac0c6-97bc-11e5-8d0a-852e3ae2f69f.png) - _Here we should avoid adding `turn-restriction` as it will result in redundant data_ - ![screen shot 2016-05-24 at 6 37 06 pm](https://cloud.githubusercontent.com/assets/4470913/15538956/1a068350-229d-11e6-9931-56770c643131.png) - _This situation is a clear indication of a redundant restriction_ - - Add a conditional restrictions when specific conditions are written on the turn-restriction sign-board. - - On certain times of the day. eg. Restriction during peak hours 7AM-10AM - - On a certain day of the year. eg. Restriction on baseball game days only - -## Adding Conditional turn restrictions - -**Special cases** -* [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions) during peak hours are common in SF. Tag them as `restriction:conditional=no_left_turn @ (Mo-Sa 07:00-09:00,16:00-18:00)`
![](https://cloud.githubusercontent.com/assets/4470913/14850426/9d4643f8-0c96-11e6-8c0c-dc94887e1613.png) -* Conditional restriction during baseball games. Ignore
-screenshot 2016-04-27 16 51 33 - -* In the case below, we are leaning towards adding this as a regular `restriction` since it applies for all regular personal vehicles. - - ![screenshot 2016-05-02 12 01 18](https://cloud.githubusercontent.com/assets/12103383/14948422/b9f1838a-105d-11e6-9604-2781de0d6d96.png) - -* If you come across the below instance where the restriction is applicable only on `School Days`. Per discussion we will be adding the restriction for `Monday - Friday` - - ![screen shot 2016-05-06 at 2 57 43 pm](https://cloud.githubusercontent.com/assets/1933377/15074787/7c6594d4-13be-11e6-9c01-1d277070960e.png) - -## QA for turn restrictions - -During turn restrictions mapping in various cities, we have come across certain special cases where we need to pay more attention while mapping. These cases are noted down here for your reference. - ----- - -# Be cautious when you come across these turn restrictions - -**1. Restrictions on Red** - -Be careful with interpreting signage and always verify Mapillary signage overlay with the image and the kind of restriction. The image below shows a sign for no free right that Mapillary interpreted as `no-right-turn`. This is NOT a turn restriction. If you are not sure, consult the community before mapping. -
screenshot 2016-04-26 21 39 06 - -A similar restriction found in Canada depicts that **left turn** cannot be taken when the signal is red, otherwise it is permitted to turn left. We are **not** adding such turn restrictions. - -![no_right_turn_on_red_sign](https://cloud.githubusercontent.com/assets/4470913/17021102/28acf658-4f63-11e6-8266-b380071706c4.jpeg) -_Picture by Share Bear - Own work - [Public Domain](https://commons.wikimedia.org/w/index.php?curid=8626974)_ - -**2. Location and bearing of Mapillary Signage overlay** - -The location and bearing of the Mapillary photo is not reliable and is prone to usual GPS errors. Cross check the photograph with the map to confirm you are looking at the intersection from the correct bearing. This photograph is facing the reverse of actual heading. -
screenshot 2016-04-27 12 28 12 - -**3. Single restriction per image detection** - -Mapillary will detect only one sign type per image. Lookout for multiple restrictions in the image
-screenshot 2016-04-27 17 49 34 - -**4. Careful with Turn restrictions plugin in JOSM** - -Sometimes the **Turn restrictions plugin** does not detect the correct signs i.e. even though it's a `no-right-turn`, the plugin detects it as `no-left-turn`. So be extra sure before adding the restriction -![turn_restrictions_plugin_bug](https://cloud.githubusercontent.com/assets/4470913/15529626/4f438044-226c-11e6-919e-02481acb5ad1.gif) - -**5. Advantage of previous/next images** - -There might be an offset in the Mapillary images, that is the image may appear after/before the actual location. It is ideal to inspect the previous and next images and also look for road names and other clues from the satellite imagery to verify it's exact location and bearing. -![offset_mapillary](https://cloud.githubusercontent.com/assets/4470913/15539155/712f0296-229e-11e6-8675-fecc95f4be51.png) - -**6. Temporary turn restrictions** - -When the roads are in construction or under repair, you might see temporary turn restrictions placed similar to shown in the below image. We are not adding temporary turn restrictions. -![pjimage](https://cloud.githubusercontent.com/assets/8921295/17290390/d8808ac2-57fb-11e6-8816-d681033e2a8f.jpg) - - - -**7. Restriction-ahead warnings** - -In the below image, there is a no_left_turn sign board as detected from the Mapillary image. This sign board means that there is a ```no_turn_restriction``` ahead. But this signage itself is **not** a turn restriction, so we do not map this. -[![screenshot 2016-07-26 15 31 15](https://cloud.githubusercontent.com/assets/8921295/17133998/03bf2e10-5346-11e6-949f-dcd4f554560b.png)](https://cloud.githubusercontent.com/assets/8921295/17133964/e83159fc-5345-11e6-935a-5b535390f730.jpg) - - -# Different conventions for turn restrictions in different countries - -### Canada - -**Case:1** - -The image below shows two signages, the first one is in French and translates to 'Wait for arrow to turn left' and the second one is a `no_u_turn`. In such cases, we ignore the the first signage and go ahead mapping `no_u_turn`. - -[![screenshot 2016-07-26 14 34 36](https://cloud.githubusercontent.com/assets/8921295/17132558/efc2a398-533f-11e6-93d7-7dc0e87978ae.png)](https://d1cuyjsrcm0gby.cloudfront.net/4ZA3OT0nHoDQ7F7JILG-pg/thumb-2048.jpg) - - -**Case:2** - - -In the below image, the first board for ```no_left_turn``` says Monday to Friday 8am-10am and 3pm-7pm (Lun-Ven 8h-10h,15h-19h in French). The second board is a ```no_u_turn``` **except authorized vehicles**. In this case, first one would be a conditional turn restriction; second, an absolute ```no_u_turn``` turn restriction. - -[![screenshot 2016-07-26 14 48 15](https://cloud.githubusercontent.com/assets/8921295/17132580/093ab860-5340-11e6-9863-ffe150f7c8c8.png)](https://d1cuyjsrcm0gby.cloudfront.net/IYi6WjwOQDnPW1HTTGyh8A/thumb-2048.jpg) - -**Case:3** - -The below image indicates that all the drivers (no matter the lane they are on) must follow this/these direction(s) at the intersection. This means that the driver needs to only turn right/left on the days mentioned in the sign and during that duration of the day. - -![image](https://cloud.githubusercontent.com/assets/3423533/17128539/0b5166e0-532b-11e6-96e6-69d21603f183.png) - -**Syntax to be used:** `restriction:conditional=only_right_turn @ (Mo-Fr 07:00-09:00,16:00-18:00)` - -### Germany - -In Germany, instead of signages to prohibit turns, the signages describe the legally allowed turns at the junction. Hence a signage for a no right turn will indicate only turns for left and straight. - -![screen shot 2016-08-17 at 4 12 05 pm](https://cloud.githubusercontent.com/assets/11845908/17733853/568ce2b6-6496-11e6-8665-8983fe1c94db.png) - -_An example of a `restriction=no_right_turn` traffic sign in Germany_ - -### Turn restriction signs of Germany and what it means: - -![screen shot 2016-08-17 at 4 27 33 pm](https://cloud.githubusercontent.com/assets/11845908/17734070/a6125f5e-6497-11e6-8d70-d55248e938ec.png) - -*Courtesy: [German wiki](http://wiki.openstreetmap.org/wiki/DE:Relation:restriction)* - - -**Reference** - -- OSM tags for routing http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing -- Turn restrictions http://wiki.openstreetmap.org/wiki/Relation:restriction -- Access restrictions http://wiki.openstreetmap.org/wiki/Key:access -- Conditional restrictions http://wiki.openstreetmap.org/wiki/Conditional_restrictions - -**Spanish version [here](https://github.com/mapbox/mapping/wiki/Gu%C3%ADa-de-mapeo-para-a%C3%B1adir-restricciones-de-giro-utilizando-mapillary)!** \ No newline at end of file diff --git a/mapping-to-improve-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md b/mapping-to-improve-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md deleted file mode 100644 index 1a62fe6..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Adding exit and destination signs ---- - -![5138660996_1957ee06ed_o](https://cloud.githubusercontent.com/assets/17887418/15180552/ec541b64-179f-11e6-88d7-4b3074f161e4.jpg) - -## What are exit numbers? - * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. - - ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) - -### Different tags for exit numbers: -* `ref=*` is used when the exit has a specific number assigned to it. -* `noref=yes` is used when the exit doesn't have any official number assigned to it. - -## How to add exit numbers? - -* Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. - -* Select the assigned highway from the dropdown and click on the `download` button. - - ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) - -### Verify the exits on the route for missing information - -* Load the route in JOSM - -![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) - - ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) - - * Browse along the route and check the ways on both directions at every exit location for the following: - - There is a `motorway_junction` at the start of every `motorway_link` exiting the highway - - The `motorway_junction` has a correct exit number `ref` value as per the source. - - The exit number on both directions are the same - - There is only one exit in a direction for every exit number - -**Add missing exit numbers** - -* Download the data and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) around the blue marker in the imagery. - -* Use a combination of Mapillary, Department of Transportation (DoT) documents and Wikipedia to add the `ref=*` tag on `highway=motorway_junction` (stick to using Mapillary and DoT doc as primary source and move to others in case of unavailability of information) - -* If it is confirmed there is no exit number for the `motorway_junction` add another tag `noref=yes` to indicate the exit does not have an official reference number. - - - -## Analyzing signboards in mapillary - -Look out of Highway sign boards on imagery. They may look something like this- - -![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) - -Places to look for- -- near a `motorway_junction` -- near **start** of a `motorway_link` - -![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) - - - -### Do's and don'ts -- It is not necessary that exit numbers are sequential. It might find 45 after 41. -- There are some `motorway_junction` which don't have any associated exit number. Add `noref=yes` on these nodes. -![no ref](https://cloud.githubusercontent.com/assets/17470597/15071466/65aff514-13a9-11e6-9392-3677c8b193a0.jpg) - -- If there are multiple exits on the same [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) then you can tag them as `ref=* ; *` instead of `ref:left=*` and `ref:right=*` until you are confirmed with that. - -- In the case of discrepancy between mapillary and DoT document, look out for the recent change in exit numbers on the web. Many states changes/in a process to change the exit numbers. -- **Ignore the `highway=motorway_junction` where the traffic flow is towards the motorway** - - -## What are destination tags? - -* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. -* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. - -![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) - -### Different tags for destinations: -* `destination` tag refers to the place that the way exiting from the freeway leads to. -* `destination:ref` is the reference of the roads directly ahead. -* `destination:ref:to` is to specify the reference of a major highway ahead. -* `destination:street` refers to the main street the way exiting from the freeway leads to. - -## How to add destination tags? - -### Assign a highway and use Checkautopista2 to map features - -1. Open the destination reference document for your assigned city area. Pick a highway to check and assign it on the spreadsheet to avoid conflict. - -2. Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. - -3. Select the assigned highway from the dropdown and click on the `download` button. - - ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) - - -4. Look out for red outer circle for missing destination. Use `open in JOSM` button to open the node in JOSM. Orange outer circle represents `exit_to` tag and we don't need to add destination tags in the way. Green outer circle represent that the concern way already has destination tag. - - - ![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) - - ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) - - -5. Download the data around the `motorway_junction` and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs). - -7. Use combination Mapillary images, DoT documents, and Wikipedia to add destination as `destination=*` on `motorway_link` ways and the destination highway as `destination:ref=*`. - **Below is a an example** - ![screen shot 2016-03-14 at 6 28 27 pm](https://cloud.githubusercontent.com/assets/12744420/13745188/a12098bc-ea12-11e5-8ffc-9fb839ed5aa2.png) - **On the `highway=motorway_link`(represented by red line) add `destination=Daly City` and `destination:ref=I 280 South`. This can be confirmed with [DoT document](http://www.dot.ca.gov/hq/traffops/engineering/calnexus/pdf/101.pdf) and [wikipedia](https://en.wikipedia.org/wiki/U.S._Route_101_in_California) while searching for exit number 431** - -8. Add any highway missing in the highway spreadsheet. Mark the highway done if all destination tags are mapped/review - - - -## Analyzing signboards in mapillary - -Look out of Highway sign boards on imagery. They may look something like this- - -![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) - -Places to look for- -- near a `motorway_junction` -- near **start** of a `motorway_link` - -![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) - - - -### Do's and don'ts -- Use `;` to separate multiple destination and refs. -- Read more on [Highway intersection](https://en.wikipedia.org/wiki/Interchange_(road)) to understand them better. - diff --git a/mapping-to-improve-navigation/_posts/0000-01-06-adding-turn-lanes.md b/mapping-to-improve-navigation/_posts/0000-01-06-adding-turn-lanes.md deleted file mode 100644 index 24c5b7d..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-06-adding-turn-lanes.md +++ /dev/null @@ -1,247 +0,0 @@ ---- -title: Adding turn lanes ---- - -## What is a turn lane - -A turn lane is an auxiliary lane demarcated on the road to specify directions to ongoing vehicles. -Turn lanes serve two purposes: - * Provide directional information to the ongoing vehicles and - * Provide the lane information to be chosen for the vehicles changing their direction - -### Types of turn lanes - -There are a total of 12 different turn lanes demarcated on the roads. They are: - -Turn Lane | Representation ---- | --- -turn:lanes = left | ![left](https://cloud.githubusercontent.com/assets/8401827/13217928/1d2fc24e-d98c-11e5-9d20-c526fe6e7f01.jpg) -turn:lanes = right | ![right](https://cloud.githubusercontent.com/assets/8401827/13217945/424f36e0-d98c-11e5-99e7-9d178f2529a1.jpg) -turn:lanes = through | ![through](https://cloud.githubusercontent.com/assets/8401827/13214156/f885d4b4-d973-11e5-9fb7-e9ecb70a932b.jpg) -turn:lanes = left;through | ![through left](https://cloud.githubusercontent.com/assets/8401827/13217986/80786072-d98c-11e5-99c6-db8665977550.png) -turn:lanes = right;through | ![through_right](https://cloud.githubusercontent.com/assets/8401827/13218022/b8aa9352-d98c-11e5-87c2-d8c17ee68305.jpg) -turn:lanes = left;through;right | ![leftthroughright](https://cloud.githubusercontent.com/assets/8401827/13218061/027e10ee-d98d-11e5-9747-c6867e0787b0.JPG) -turn:lanes = left;right | ![left_right](https://cloud.githubusercontent.com/assets/8401827/13217579/8f833c66-d989-11e5-9b2c-dc98fdff09b2.png) -turn:lanes = slight_left | ![slightleft](https://cloud.githubusercontent.com/assets/8401827/13218207/e450feaa-d98d-11e5-938c-a3956de2f7ba.png) -turn:lanes = slight_right | ![slightright](https://cloud.githubusercontent.com/assets/8401827/13218219/07052b56-d98e-11e5-8fc0-82b945fb95c6.png) -turn:lanes = merge_to_left | ![merge to left](https://cloud.githubusercontent.com/assets/8401827/13218244/2ca1fd6c-d98e-11e5-8be9-cb64271f5991.png) -turn:lanes = merge_to_right | ![fahrbahn_2](https://cloud.githubusercontent.com/assets/8401827/13218183/bc5d0790-d98d-11e5-9781-307f80cc0732.png) -turn:lanes:bothways = * | ![turn lanes both ways](https://cloud.githubusercontent.com/assets/8401827/13217721/a2594d48-d98a-11e5-87f1-11e11ebf57ec.png) - - ![](http://pdd.ua/r/r/EEB7A996-D8DC-40FC-87EA-01F3E115BC7C/m_1.18_4.jpg) - _road markings on the ground_ - © [pdd.ua](http://pdd.ua/ua/34/1.18/) - -### Pre-requirements for mapping a turn lane in JOSM - -Before mapping turn lanes activate the following preferences in JOSM to visualize the mapped turn lanes: `preferences > Map Settings` -* *`Map Paint Styles > Lane and road attributes`* - - ![lane_and_road_attributes](https://cloud.githubusercontent.com/assets/13744156/13218788/c55fab96-d991-11e5-89b2-b281986d704e.gif) - -* *`Tagging Presets > lane attributes`* - - ![tagging_presets](https://cloud.githubusercontent.com/assets/13744156/13218902/ad15c902-d992-11e5-872b-1bde24f27f5b.gif) - -* Filter out non-road features with inverse filter: `boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:` - -**Plugins** - -* Knife-tool: https://gist.github.com/jothirnadh/a10daeaef1498537ea56f0a65f7fdbc2 -* TurnLanes-tagging plugin: `JOSM Preferences > Plugins > turnlanes-tagging` - -### Mapping a turn lane - -* Check all roads in the imagery for turn lanes at junction points - - ![roads_markings](https://cloud.githubusercontent.com/assets/126868/11710074/b58b52e4-9f42-11e5-971a-000a699a0b6d.png) - -* Split the road into segments based on the total number of lanes for the segment. The easiest way for splitting the road is by using [Knife_tool](https://gist.github.com/jothirnadh/a10daeaef1498537ea56f0a65f7fdbc2) - - ![residential_road](https://cloud.githubusercontent.com/assets/369696/13223732/34cf7ffa-d98e-11e5-9a33-8f40f6498004.png) - -* For each road segment tag the turn lanes based on the road markings in the direction of the way. Eg. `turn:lanes=left|left;through|through`. Check [OSM turn:lanes](http://wiki.openstreetmap.org/wiki/Key:turn:lanes) for reference. - - ![oneway_turn:lanes_tagging](https://cloud.githubusercontent.com/assets/8401827/13252110/a6bdea8a-da5a-11e5-8c79-aa15c0c15f68.gif) - -* For bi-directional segments, use `turn:lanes:backward=` and `turn:lanes:forward=` to specify turn lanes in each direction. - - ![bidirectional_tagging](https://cloud.githubusercontent.com/assets/13744156/13219545/acd78f62-d996-11e5-85eb-3e05a7b79d3b.gif) - -* Verify correct tagging using the `Lane attributes` style - - ![lane_attributes](https://cloud.githubusercontent.com/assets/8401827/13251884/ddcbdd54-da58-11e5-86ae-c4a2918c9577.gif) - -* The simplest way to add turn lanes is by using **[turnlanes-tagging plugin](https://www.mapbox.com/blog/turnlanes-tagging/)** - -![turnlenes](https://cloud.githubusercontent.com/assets/8401827/17246767/d086ef48-55ab-11e6-8bce-46c434cb9005.gif) - -### `turn:lanes` and relations - -We use [relations](http://wiki.openstreetmap.org/wiki/Relation) for different purpose – for indicating [turn restriction](http://wiki.openstreetmap.org/wiki/Relation:restriction) or collect separate ways into solid [route](http://wiki.openstreetmap.org/wiki/Relation:route). -​ -JOSM help us to handle them. But sometimes we are faced with not properly denoted relations. JOSM will inform about it while uploading our changes. You may [ignore messages of level "Warnings"](https://github.com/mapbox/mapping/issues/153#issuecomment-185679507) (if you only split ways and didn't edit relations manually) but you have to fix all "Errors". - -## QA for turn lanes mapping - -While mapping turn lanes, there are a lot of scenarios are encountered in [#153](https://github.com/mapbox/mapping/issues/153) and [#144](https://github.com/mapbox/mapping/issues/144) mapping repos. All these scenarios are drafted in one place for validation purposes. - -## Different scenarios we came across while mapping - -### 1. Parking lanes - -In the U.S., when parallel parking spaces are marked, they are marked in one of [three ways](http://mutcd.fhwa.dot.gov/htm/2009/part3/fig3b_21_longdesc.htm): - - ![parking_lanes](https://cloud.githubusercontent.com/assets/8401827/13172245/326a7bb6-d71d-11e5-8617-a2516f75144b.png) - -Here’s an example of the box marking style: - - [![boxes](https://upload.wikimedia.org/wikipedia/commons/thumb/0/03/J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG/320px-J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG)](https://commons.wikimedia.org/wiki/File:J.S._Shingler_Bldg_%28East_face%29,_McLendon_St,_Ashburn.JPG) - -### 2. Counting number of turn lanes - -If there are no clear cut demarcations on the road and yet cars are parked on either sides of the road, consider them as drive lanes. Case below: - - ![number_of_lanes](https://cloud.githubusercontent.com/assets/8401827/13142482/5b26d0a0-d663-11e5-90cd-4a65d75e7248.png) - -### 3. Starting a turn lane - - Turn lanes should begin exactly as per the marking in the imagery, not before or after. - - ![turn:lanes_start](https://cloud.githubusercontent.com/assets/8401827/13110125/0fe83ad0-d5a4-11e5-82ff-00245d0ba043.png) - -### 4. Ending a turn lane - -Turn lanes should terminate at the first highway junction after the start of the turn lane. - - ![turn:lanes_end](https://cloud.githubusercontent.com/assets/8401827/13143057/4ff2b3c6-d667-11e5-8069-b028fabf7587.png) - -### 5. Turn lane forward - -In case of bi-directional ways, the key [turn:lanes:forward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the same direction as the osm-way; while adding this we must view the road in the direction to the osm-way(**on the direction where the osm-way arrow is pointing**). - - ![turn:lanes:forward](https://cloud.githubusercontent.com/assets/8401827/13175904/c5c922fc-d733-11e5-91b1-c0f9e5181fda.gif) - -### 6. Turn lane backward - -In case of bi-directional ways, the key [turn:lanes:backward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the opposite direction as the osm-way; while adding this we must view the road in the oppoiste direction to the osm-way(**opposite to direction where the osm-way arrow is pointing**). - - ![turn:lanes:backward](https://cloud.githubusercontent.com/assets/13744156/13172709/859957c4-d71f-11e5-8cd9-ea154ad5d2e8.gif) - - *Adding a `turn:lanes:backward` tag* - -### 7. Adding dual carriageways: - -When finding roads mapped as single carriageway while the imagery shows clear separation between roads, split the road where the physical separation starts and add dual carriageways. - -![dualcarriageway](https://cloud.githubusercontent.com/assets/8401827/13393542/117b59aa-df08-11e5-8fd3-21a931531f84.png) - - -**When to add dual carriageway?** -- Add Dual-carriage when - - you see physical separation betweens roads - - **no relation is attached to the way.** -- Add `turn:lanes` tag to both the ways. - - -### 8. Bicycle lanes and road shoulders - -Road shoulders and bicycle lanes are ignored from the lane count. Both these roads are `lanes=2` - - ![bicycle+shoulders](https://cloud.githubusercontent.com/assets/126868/11715007/628dd90a-9f64-11e5-9e22-58614d2afbf6.png) - - ![bicycle_lanes](https://cloud.githubusercontent.com/assets/13744156/13172922/adc69f08-d720-11e5-8600-7a606d2e9bae.png) - - *lanes=3 for the above example, ignoring the two cycle ways* - -* Ignore bicycle lanes even though they are in the middle;example below: - - ![xyz2](https://cloud.githubusercontent.com/assets/8401827/13495220/79a65aca-e16f-11e5-83e7-24d3e4f53ad0.png) - - *The middle way is also a bicycle lane which is not counted while adding the `lanes` tag* - -* Additionally, `Strava global-heat cycle` layer can used to verify if a particular lane is a cycle-way. -`tms[16]:http://globalheat.strava.com/tiles/cycling/color3/{zoom}/{x}/{y}.png` - -### 9. Lane marked as a separate way - -Do not add turn lanes in these cases where the only turn lane is already a mapped as a separate way. - - ![lane_as_separate_way](https://cloud.githubusercontent.com/assets/13744156/13173428/6694c468-d723-11e5-96be-b95502b9f58a.png) - -### 10. Bidirectional turn lanes - -These are the lanes marked with symbol representing both directions at a time. - - ![turn:lanes:both_ways](https://cloud.githubusercontent.com/assets/8401827/12642951/0162ff9c-c5df-11e5-8a14-a41f263ae086.png) - -Tag used for such lanes are `turn:lanes:both_ways=*` - -Yellow lines on both sides of a lane also gives an indication of `turn:lanes:both_ways=*` - -![screen shot 2016-05-16 at 4 12 49 pm](https://cloud.githubusercontent.com/assets/1933377/15287587/8dd24396-1b81-11e6-8527-b84814804175.png) - -![screen shot 2016-05-16 at 4 13 00 pm](https://cloud.githubusercontent.com/assets/1933377/15287591/9165c50a-1b81-11e6-9521-93cea4b7be16.png) -### 11. Mapillary Plugin to verify turn lanes - -The imagery at some places is not very clear and at-times the turn-lanes are covered by cars. In situations like these `Mapillary plugin` can be used. If there is Mapillary imagery coverage in that area, they can used to verify the presence of turn-lanes. - -**Name of the plugin:** Mapillary - - ![turnlanes_mapillary](https://cloud.githubusercontent.com/assets/4470913/12884912/6b405d1e-ce87-11e5-8d0f-cd8a8a8b3dfd.gif) - -### 12. Lanes with restricted access - -These are the areas on streets which are restricted for vehicular traffic. - -![screen shot 2016-03-15 at 3 36 36 pm](https://cloud.githubusercontent.com/assets/8401827/13776503/84c34002-ead0-11e5-911d-0581fe9173b7.png) - -![screen shot 2016-03-14 at 4 46 03 pm](https://cloud.githubusercontent.com/assets/8401827/13776504/84e64138-ead0-11e5-81f0-7918311ec6dc.png) - -![screen shot 2016-03-14 at 4 46 29 pm](https://cloud.githubusercontent.com/assets/8401827/13776505/84e71888-ead0-11e5-9135-553c11d99d12.png) - -In the above cases the areas with markings on the roads are not considered as a lane - -### 13. Reverse direction turn lanes - -These are the lanes specifically categorized to take U-turn or reverse-turn. - -![screen shot 2016-03-14 at 2 25 28 pm](https://cloud.githubusercontent.com/assets/8401827/13776502/84944b6c-ead0-11e5-92fa-0bb2951760ef.png) - -### 14. The order of the directions and valid combinations of values - - - `none` itself is valid value but **not** in conjunction with other - - - ✅ `turn:lanes=none|right` is equal to `turn:lanes=|right` - we use `none` for "_better readability_" - - - 👎 `turn:lanes=left||none|merge_to_right` - this combination of values is valid but there is mixing `none` and `||` (empty) - this is not good choice. - - - 👍 `turn:lanes=left|none|none|merge_to_right` or `turn:lanes=left|||merge_to_right` - - - ❎ `turn:lanes=none|none|none` or `turn:lanes=||` - in this case `turn:lanes=*` tag is redundant, just specify `lanes=3` or real number of lanes - - - ❎ `turn:lanes=none|none;slight_right` - isn't valid combination - "_there are no turn indications_" on the rightmost lane. Instead, must be used (based on https://github.com/mapbox/mapping/issues/180#issuecomment-225574666) - -``` -lanes=2 -turn:lanes=none|through;slight_right -transit:lanes=continue|new_on_right -``` - -- using `*right` | `*left` values - - - ✅ `turn:lanes=left|none|none` or `turn:lanes=||right` or `turn:lanes=merge_to_right||` or `turn:lanes=left|left;through|none|slight_right|right|right`- 👍 - - - ❎ `turn:lanes=|right|left|` or `turn:lanes=none|right|left|through` or `turn:lanes=none|left|none`- 👎 lanes that go in one direction should not cross with each other - -- using `reverse` value - - - `reverse` (u-turn) have to be on the leftmost lane for right-hand traffic or on the rightmost lane for right-hand - -### 15. - -_to be continued …_ - -### Further reading: -* [Mapping turn lanes: OSM wiki](http://wiki.openstreetmap.org/wiki/Key:turn) -* [Mapping turn lanes in OpenStreetMap by Andrey Golovin](https://www.mapbox.com/blog/turn-lanes-mapping/) -* Diary post by @Andygol : [Mapping turn lanes in OpenStreetMap](http://www.openstreetmap.org/user/andygol/diary/35489#) diff --git a/mapping-to-improve-navigation/_posts/0000-01-07-resources-and-references.md b/mapping-to-improve-navigation/_posts/0000-01-07-resources-and-references.md deleted file mode 100644 index 1c9eed5..0000000 --- a/mapping-to-improve-navigation/_posts/0000-01-07-resources-and-references.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Resources and References ---- - -**Mapbox navigation mapping projects** - -Navigation mapping forms a large part of Mapbox's mapping sprints in recent times. Given below are a few examples of some of the latest navigation mapping efforts across US, Canada, and Europe. To get an idea about all our historical mapping projects related to navigation in OSM, look into the [mapping repository](https://github.com/mapbox/mapping/issues). Our mapping projects are conducted in the open with active participation, feedback, and validation from the community. - -#### Examples - -Location | Description|Start|End(ETA)|Validation ----|---|---|---|---| -[Mapping turn lanes in 30 US cities](https://github.com/mapbox/mapping/issues/180)| Mapping all the turn lanes from satellite imagery in 30 US cities from secondary and above|04/05/2016|Continuing|Continuing -[Updating turn restrictions in Germany](https://github.com/mapbox/mapping/issues/226)| Updating missing turn restriction coverage in 3 german cities: Berlin, Stuttgart, Wolfsburg|29/08/2016|Continuing|Continuing -[Mapping turn restrictions in Canada](https://github.com/mapbox/mapping/issues/213)|Mapping turn restrictions from mapillary in top 5 cities in Canada|22/07/2016|05/08/2016|Completed -[Exit and destination mapping in Canada](https://github.com/mapbox/mapping/issues/220)|Map the exit and destination numbers in top 5 Canada cities using mapillary|11/08/2016|17/08/2016|Completed - -**Navigation data tools** - -* [OpenStreetMap navigation map](http://mapbox.github.io/osm-navigation-map/#11.63/37.7896/-122.4363): This map is used to add turn restrictions in OSM. It has a detected signage mapillary layer for easy detection of turn restrictions, oneways and a dataset which displays all the valid, invalid and redundant turn restrictions added. Get more [instructions](https://github.com/mapbox/osm-navigation-map/blob/gh-pages/MAPPING.md) on `how to use the OSM navigation map`. -* [CheckAutopista2](http://k1wiosm.github.io/checkautopista2/): It is a tool to investigate and add highway signboard features on motorways and freeways. For more details look into the [github repository](https://github.com/k1wiosm/checkautopista2) for `checkautopista`. -* [Overpass](https://overpass-turbo.eu/): The place to query and extract all OSM data related to a specific feature. It has a simple query builder feature that helps in querying each and every feature in OSM. Details about [overpass](http://wiki.openstreetmap.org/wiki/Overpass_turbo) can be found [here](http://wiki.openstreetmap.org/wiki/Overpass_API) and [here](http://wiki.openstreetmap.org/wiki/Overpass_API/Language_Guide). -* [Knife tool](https://www.mapbox.com/blog/knife-tool/): The knife tool can be used for quick splitting of ways while adding navigation features such as turn lanes. For more details, look [here](https://github.com/mapbox/auto-tools/tree/split) -* [Turn lanes tagging plugin](https://www.mapbox.com/blog/turnlanes-tagging/): With this plugin, you can add complex tag combinations for turn lanes at road junctions with ease, and minimize errors. For more details, look [here](https://github.com/JOSM/turnlanes-tagging) - - - -**Country specific navigation guide** - - Images of traffic signs and road markings : Traffic signs and road markings may undergo small changes and specific cases when mapping turn restrictions using Mapillary. There are subtle differences in turn restrictions between Canada, US, and Germany. *(This section is to be kept updated with new signages every time mapping is done in a separate country with new conventions)* - -1. **[Turn restriction images in US](https://gist.github.com/abhisheksaikia/7c9329a985816c128aabcba092747816)** - -2. **[Turn restrictions images in Germany](https://gist.github.com/abhisheksaikia/646b918fc64f9d8109b5d62a8137e86a)** - -3. **[Turn restrictions in Canada](https://gist.github.com/abhisheksaikia/bcfbf4ea0dc1e100337244867b2524fc)** - -4. **[Turn restrictions in France](https://gist.github.com/jothirnadh/3d0245816dabbf395c447130877c538c)** - - -For more details on cases for turn restrictions and signages in different countries take a look at [QA for mapping turn restrictions](https://gist.github.com/abhisheksaikia/6e12973daa5be78da3ef9ba6d21b8562) - -**Data sources and references for navigation data** - -* [Mapillary](https://www.mapillary.com/) - -* [OpenStreetView](http://openstreetview.org/map/) -- **DOT documents/websites**: Local official websites, documents released by local `Department of Transportation` bodies. -- **Wikipedia**: Exit and destination numbers, highways, highway refs. *(must be verified on ground or with official sources)* -- High resolution satellite imagery: Bing, Mapbox, USGS, open satellite datasets ([Landsat](http://landsat.usgs.gov/), [Sentinel2](http://www.esa.int/Our_Activities/Observing_the_Earth/Copernicus/Sentinel-2/Data_products), [LISS](http://bhuvan.nrsc.gov.in/data/download/index.php), government opendata portals). From 3a62ceeb1924f89bc83f6e4846817a35e514c598 Mon Sep 17 00:00:00 2001 From: tatsvc Date: Mon, 24 Oct 2016 08:57:55 -0400 Subject: [PATCH 26/66] rename css and add breakpoints --- site.css | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/site.css b/site.css index bcc1ede..273cccf 100644 --- a/site.css +++ b/site.css @@ -70,9 +70,9 @@ svg { { height: 350px; } -#mapping-to-improve-navigation svg +#mapping-for-navigation svg { - max-height: 260px; + max-height: 300px; } #validating-openstreetmap svg @@ -1252,6 +1252,11 @@ pre.pre-guides:before { #the-openstreetmap-data-model svg { height: 270px; } + #mapping-for-navigation svg +{ + max-height: 230px; + } + } @media only screen and (max-width: 1024px) { @@ -1267,6 +1272,11 @@ pre.pre-guides:before { #the-openstreetmap-data-model svg { height: 360px; } + #mapping-for-navigation svg + { + max-height: 300px; + } + } @media only screen and (max-width: 900px) { @@ -1279,6 +1289,9 @@ pre.pre-guides:before { .image-card { height: 255px; } + #mapping-for-navigation svg { + max-height: 250px; +} } @media only screen and (max-width: 700px) { @@ -1333,11 +1346,9 @@ pre.pre-guides:before { { max-height: 140px; } - #mapping-to-improve-navigation svg - { - max-height: 140px; + #mapping-for-navigation svg { + max-height: 120px; } - #validating-openstreetmap svg { max-height: 140px; From 1c1b29288819ae3e262de817f00b95580695c711 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Mon, 24 Oct 2016 19:49:03 +0530 Subject: [PATCH 27/66] Restore deleted pages --- .../_posts/0000-01-01-introduction.md | 86 ++++++ ...01-02-modeling-roads-for-map-navigation.md | 86 ++++++ .../0000-01-03-road-features-mapping-guide.md | 217 +++++++++++++++ .../0000-01-04-adding-turn-restrictions.md | 251 ++++++++++++++++++ ...01-05-adding-exit-and-destination-signs.md | 135 ++++++++++ .../_posts/0000-01-06-adding-turn-lanes.md | 247 +++++++++++++++++ .../0000-01-07-resources-and-references.md | 49 ++++ 7 files changed, 1071 insertions(+) create mode 100644 mapping-for-navigation/_posts/0000-01-01-introduction.md create mode 100644 mapping-for-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md create mode 100644 mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md create mode 100644 mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md create mode 100644 mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md create mode 100644 mapping-for-navigation/_posts/0000-01-06-adding-turn-lanes.md create mode 100644 mapping-for-navigation/_posts/0000-01-07-resources-and-references.md diff --git a/mapping-for-navigation/_posts/0000-01-01-introduction.md b/mapping-for-navigation/_posts/0000-01-01-introduction.md new file mode 100644 index 0000000..5e42863 --- /dev/null +++ b/mapping-for-navigation/_posts/0000-01-01-introduction.md @@ -0,0 +1,86 @@ +--- +title: Introduction +--- + +The most basic use of a map is to find out where one is located. After that, one usually wants to use the map to find the best route to another location. On a [digital map](https://en.wikipedia.org/wiki/Digital_mapping), this is usually provided with [turn by turn navigation](https://en.wikipedia.org/wiki/Turn-by-turn_navigation) using a [navigation device](https://en.wikipedia.org/wiki/GPS_navigation_device). + +![navigation_optimized](https://cloud.githubusercontent.com/assets/13744156/18119269/76493c6c-6f77-11e6-8c18-a1daf7845f0b.gif) +_Let the computer find the best route for you!_ + +## Components of map navigation + +A navigations system has user facing components that interact with the user and back end components that computes the best route based on the user input and available data. In this guide we will focus on the back end components that rely on map data. + +**User facing components** +- User interface controls for setting the the origin and destination +- Map display that visually represents the route to take +- Turn by turn instructions that accurately describe the navigation maneuvers at the appropriate time +- Route status that includes current progress and the estimated time of arrival (ETA) at the destination + +**Back end components** +- A navigation profile that describes the mode of transport to use for the routing algorithm (eg. truck, cycle or foot) +- A route finder that finds the best possible route between the origin and destination for the selected navigation profile +- A guidance system that converts the route into instructions for turn by turn navigation + +### Navigation profile + +The navigation profile accurately describes the preferred types of roads to take based on the mode of transport used. A walking profile will have a fairly constant walking speed on any type of road, while a car profile will have avery high traveling speed on a motorway and will be much slower on a residential road. This has a large influence on the route finder. + +![screenshot_20160831-124644](https://cloud.githubusercontent.com/assets/8401827/18120537/b392baac-6f7d-11e6-9e36-480b3145c429.png) + +*Different routing profiles: cars, walking, bicycle.* + +### Routing + +[Routing](http://wiki.openstreetmap.org/wiki/Routing) is the process of selecting the best path in a network interconnected of roads on the map. Every road segment on the map has a traveling speed calculated based on various road factors, and the fastest and safest route is selected from all possible combinations. + +![](https://farm4.staticflickr.com/3814/12241013316_df99a4ff83_o.png)
+_Finding the route between two points involves complex calculations on a [routing graph](https://www.mapbox.com/blog/smart-directions-with-osrm-graph-model/)_ + +The calculation of an accurate route depends on a variety of factors which are taken into account by the routing algorithm: + +* Personal factors: fastest route, most scenic route, quietest route, shortest route, facilities needed, toll rates +* Vehicle factors: mode of transport, physical category of vehicle, optimum traveling speed, riding surface requirements, fueling requirements +* Route factors (static): classification of road, access restrictions, speed limits, turn restrictions, oneway rules, number of lanes +* Traffic factors (dynamic): traffic conditions, traffic signal cycle duration, weather conditions +* Riding surface factors: surface material, smoothness, barriers, speed breakers, road width, lane width, age + +### Guidance + +![](https://cloud.githubusercontent.com/assets/12932279/16989362/402b3f44-4e94-11e6-8e8a-a60cf0b08705.png) +_A route is converted into a series of easy to follow instructions for the user_ + +Route guidance is used to lead a person through the determined path. Once the routing algorithm determines the best path, that route is converted into a set of human-readable instructions known as guidance. The guidance represents the street names, the turn lanes marked on the roads, exit numbers, and destinations shown on sign boards. Accurate and relevant guidance can greatly enhance the user experience of using the map for navigation. + +## Navigating the future + +Providing accurate navigation using maps is dependent on having detailed and updated data about the world. The world is transforming every second and the next generation of navigation will need to have the latest information about the world that will come from various sources. + +### Telemetry + +screenshot 2016-09-15 21 27 43 +_Telemetry traces of Strava users from [Strava Globalheatmap](http://labs.strava.com/heatmap/#14/-74.02871/40.70159/blue/both)_ + +Telemetry is the remote collection of data which can be physical, environmental or biological. Most internet and GPS enabled phones collect location and other environmental data and reports it to a central service that can aggregate the data to determine traffic conditions on a road. + + +### Forward facing cameras & Street-view + +![untitled2](https://cloud.githubusercontent.com/assets/126868/18557457/a667474c-7b8c-11e6-844b-e308c650a8b1.gif) +_Crowdsourced streetview photographs from [narrow alleys in India using Mapillary](https://www.mapillary.com/app/?lat=23.018631999999997&lng=72.595325&z=17&pKey=4tjlrGmABA2sxmLLmAIq9Q&focus=photo)_ + +Street view images from dashcams, mounted cameras in vehicles using apps gives highly detailed 360° view of streets. This can help detect traffic signage, access restrictions, traffic signals, road markings to help add and confirm ground features into a map. Opensource street view photos include [Mapillary](https://www.mapillary.com/) and [OpenStreetView](http://openstreetview.com/). + +### Live Aerial & Drone Imagery + +screenshot 2016-09-15 21 34 33
+_High resolution imagery captured from [UAVs in Srilanka](https://www.mapbox.com/blog/sri-lanka-drone-imagery/)_ + +[Aerial imagery](https://en.wikipedia.org/wiki/Aerial_photography) using drones can capture the changing surface of the earth at a much higher resolution and lower cost compared to traditional satellite imagery that is expensive to acquire and are updated less frequently. + +### Machine learning and image recognition + +![untitled2](https://cloud.githubusercontent.com/assets/126868/18557642/4fba4e8e-7b8d-11e6-85fb-c30092aac39b.gif)
+_Automatic image segmentation by [Mapillary](http://blog.mapillary.com/update/2016/05/19/austria.html)_ + +Advances in [machine learning](https://en.wikipedia.org/wiki/Machine_learning) opens up opportunities to automate manual tasks like [digitization of roads from satellite](http://stateofthemap.us/2016/skynet/) imagery and can accelerate the creation and maintenance of map data. \ No newline at end of file diff --git a/mapping-for-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md b/mapping-for-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md new file mode 100644 index 0000000..90f2f3c --- /dev/null +++ b/mapping-for-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md @@ -0,0 +1,86 @@ +--- +title: Modeling Roads for Map Navigation +--- + +A navigation map is influenced by several road characteristics, such as the turn restrictions, improper way of road tracing and road classification. The most important ones among those are: + +### Road geometry +Roads are the main features that are used for rendering a route in all navigational applications. Correct road mapping leads not only to the well-looking map but also to better navigation experience. With the change in the shape of the traced road, the distance covered will be altered which affects the route. The common approach for road mapping is to trace roads following the center-line from satellite imagery. + +![road_with_two_lanes](https://cloud.githubusercontent.com/assets/369696/13230189/1bc4b308-d9ad-11e5-88b7-f85fcd290926.png) + +*Roads on satellite imagery* + +### Road connectivity / topology: +If you want to travel from point A to point E as shown in the below image, you can either travel from `A to B, B to C and then C to E` or `A to B, B to D and then D to E`. + +![screen shot 2016-08-30 at 6 51 58 pm](https://cloud.githubusercontent.com/assets/8401827/18090553/e4e4eabc-6ee2-11e6-9908-8c9064c833af.png) + +But, if you have a restriction to enter D from A, the only possible route will be `A to B, B to C and then C to E`. This is where connectivity plays a major role in deciding the final route. + +### Road attributes / properties: +If `A to C` is a primary road which is crossing through a service road `B to D` and you want to travel from `A to E`, the navigation map comes up with the route traveling from `A to B, B to C and then C to E` and completely avoids `A to B, B to D and then D to E` because the travel on Primary road is much efficient than a narrow service road. This is how the attributes / properties with which the road is assigned with plays a crucial role in deciding the final route. + +![screen shot 2016-08-30 at 8 30 14 pm](https://cloud.githubusercontent.com/assets/8401827/18094299/9d9f5454-6ef0-11e6-85de-4f74a43d5657.png) + +## OpenStreetMap data model: + +The OpenStreetMap data model consists of nodes, ways, relations, and tags. A detailed description of the data model can be found in the [The OpenStreetMap Data Model](https://github.com/mapbox/mapping/wiki/The%20OpenStreetMap%20Data%20Model) guide. + +Navigation data is similarly a combination of nodes, ways, relations, and tags. Some of the examples are illustrated below: + +### Examples + +* Nodes: + - Exit numbers: + +![screen shot 2016-08-30 at 5 20 44 pm](https://cloud.githubusercontent.com/assets/13744156/18088263/517c2cf0-6ed7-11e6-8485-2d2761c42e84.png) + +* Ways: + - Highway=* + +![screen shot 2016-08-30 at 6 17 55 pm](https://cloud.githubusercontent.com/assets/13744156/18089616/6d060d0e-6ede-11e6-829d-47fc464a53a1.png) + +*An way tagged with highway=secondary tag* + +* Relations: + - Turn restrictions are a combination of nodes, ways, tags, and relations. It consists of `from way` `via node` and `to way`, tied together by a `restriction=*` relation. + + +![tr_relation](https://cloud.githubusercontent.com/assets/13744156/18089141/0c296c9e-6edc-11e6-916f-716e41c9f685.gif) + +* Tags: All the navigation features are differentiated and defined based on how they are tagged. Tags can be on any element: on nodes, ways, and relations. + +Examples are: `destination=*`, `ref=*`, `turn:lanes=*`, `restriction=*`, etc. + +## Tracing roads + +Before tracing, we need to inspect the start and endpoints of the road segment. We need to identify the road direction, general numbers of lanes and the places where there are extra lanes. Based on this we choose our strategy for tracing. + +We are not able to draw a road on its center line, especially if roads join/fork or the number of lanes change. Imagine two roads which join: how would you draw the OSM-way around the point where the roads join? + + ![center_line](https://wiki.openstreetmap.org/w/images/4/47/Lane_Placement_2.png) + + _Center line tracing_ + + ![main_direction](https://wiki.openstreetmap.org/w/images/e/e4/Lane_Placement_3.png) + + _Tracing based on road direction_ + +### Tracing roads with more than two lanes + +There are two cases: +- Dual carriageway roads + + ![dual_carriageway_road](https://cloud.githubusercontent.com/assets/369696/13230427/fe21579c-d9ad-11e5-86ba-38107d469c54.png) + +These are bidirectional roads which have a physical separation between the lanes in both the directions. Both the ways will be counted for lanes and will be tagged with `lanes=*`. Dual carriageways are always `oneway` roads. + +![motorway](https://cloud.githubusercontent.com/assets/369696/13231932/5b417e00-d9b5-11e5-854e-dbed2d209d7c.png) +*Placement of nodes of the lines in each direction, opposite to each other* + +- Roads which carry traffic in both directions (Bidirectional roads) + + ![bidirectional_road](https://cloud.githubusercontent.com/assets/369696/13230341/9f9db6c0-d9ad-11e5-9f5d-53dd80b40f67.png) +*Road carrying traffic in both directions* + diff --git a/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md b/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md new file mode 100644 index 0000000..44660bc --- /dev/null +++ b/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md @@ -0,0 +1,217 @@ +--- +title: Road Features Mapping Guide +--- + +*Detailed guide mapping features for navigation on the OpenStreetMap project. Before you start, please read the guide on [Mapping with OpenStreetMap](https://www.mapbox.com/mapping/)* + +[Query OpenStreetMap for Navigation Data via Overpass](http://overpass-turbo.eu/s/iyB) + +## Routing features + +These are features that help the routing engine find the safest and fastest route between two points. + + +### 1. Functional Road Class + +* `highway=*` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:highway) + +Roads are categorized according to its order of importance. They are tagged with the `highway=*`. The general order of importance for way types are: + +``` xml +highway= motorway > trunk > primary > secondary > ... > living streets > ... > footway +``` +![screen shot 2016-08-29 at 1 50 04 pm](https://cloud.githubusercontent.com/assets/13744156/18045336/ff8f31ea-6def-11e6-8692-bb4e082b94b8.png) + +*`highway=primary` in San Francisco* + +The value of the key helps show the importance of the highway within the road network as a whole. The importance ranges from the most important `motorway` to the least important `service`. The routing engine takes into account this importance of classification when determining optimum routes. + +Road classification may varies from country to country. The country specific use cases can be found in detail on separate wiki pages. For example, when mapping roads in India, the local community refer to the [India road tagging wiki](http://wiki.openstreetmap.org/wiki/India:Tags/Highway). + +Examples: + +* [US roads classification](http://wiki.openstreetmap.org/wiki/United_States_Road_Classification) +* [UK roads classification/numbering](https://en.wikipedia.org/wiki/Great_Britain_road_numbering_scheme) + +For an example of an area with a good concentration of different classes of roads on OpenStreetMap, look at [San Francisco](https://www.openstreetmap.org/#map=14/37.7788/-122.4375) area. This [osm query](http://overpass-turbo.eu/s/i4y) can be used to extract and gather numbers of all the highways present in a given bounding box on OpenStreetMap. + +[Department of Transportation](https://www.fhwa.dot.gov/about/webstate.cfm) websites and [wikipedia](https://en.wikipedia.org/wiki/United_States_Numbered_Highways) are some of the primary sources for highway information. + +### 2. Oneways + +* `oneway=yes` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:oneway) + +Oneways generally refer to road segments which allow traffic in only one direction. There are also streets which have oneway characteristics for only on certain times of the day to regulate traffic. + +![screen shot 2016-08-29 at 5 47 47 pm](https://cloud.githubusercontent.com/assets/13744156/18051463/5fdc162c-6e12-11e6-8984-c48da11bf73f.png) + +*`oneway=yes` shown in Mapillary* + +The best source of mapping oneways are again street level photos. + +[San Francisco](https://www.openstreetmap.org/#map=12/37.7574/-122.4845) is one area which has been well mapped for oneways in OpenStreetMap. This [overpass query](http://overpass-turbo.eu/s/i50) can be used to extract oneways from OpenStreetMap data. + +### 3. Turn-Restrictions + +* `type=restriction` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Relation:restriction) +* [Mapping guide](/mapping/mapping-to-improve-navigation/adding-turn-restrictions/) + +`type=restriction` is added to a relation in OpenStreetMap which is used to describe turn restrictions at junctions. The relation has a set of tags that describes the type of restriction, for example. `no_left_turn`, `no_right_turn`, `no_u_turn`, etc. These are traffic signs at junctions and this information must be present on the map to find the best route by the routing engine while planning a route. + +![screen shot 2016-03-08 at 8 05 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604633/ad8bff4a-e569-11e5-9198-3ac9c88e5619.png) + +*Turn restriction denoting `no left turn` along with conditions: opening and closing times* + +The main resource for turn restriction data is [street view level images](https://www.mapbox.com/blog/safer-market-street/), local mapping drives, [DOT websites](http://www1.toronto.ca/wps/portal/contentonly?vgnextoid=83f6e69ae554e410VgnVCM10000071d60f89RCRD) + +![turn_restriction](https://cloud.githubusercontent.com/assets/13744156/18047415/7d9254c8-6dfa-11e6-94e6-9d85b58627c1.jpg) +*turn restriction which denotes `no right turn` at the junction* + +[San Francisco](https://www.openstreetmap.org/#map=13/37.7696/-122.4891) in OpenStreetMap has an excellent coverage of turn by turn restrictions at junctions. This [overpass query](http://overpass-turbo.eu/s/i4G) can be used to extract current turn restriction in a bounding box. + +### 4. Speed limits + +* `maxspeed=60` or `maxpseed=40 mph` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:maxspeed) + +The `maxspeed=*` tag defines the maximum legal speed limit for general traffic on a particular road, railway or waterway. The max speed values will be interpreted as kilometers per hour by default. The `maxspeed=*` is an important part of routing as it is used in determining the shortest time taken by a specific route to reach a destination. In the case of two routes, the one with the shortest time (higher maxspeed) and shortest distance will be considered as the optimum route. + + +![maxspeed](https://cloud.githubusercontent.com/assets/13744156/18046639/6602224c-6df6-11e6-8884-18a58bf4835a.jpg) + +*Maxspeed sign shown in Mapillary* + +The main data sources for detecting maxspeed signs are: [street view photos](https://www.mapbox.com/blog/mapillary-mapping/), [wikipedia](https://en.wikipedia.org/wiki/Speed_limits_in_Canada), [DOT documents](http://www.qld.gov.au/transport/safety/rules/speed-limits/index.html). + +The `maxspeed=*` data on OpenStreetMap (for example, in [London](https://www.openstreetmap.org/#map=14/51.5059/-0.1061)) in an area can be extracted by this [overpass query](http://overpass-turbo.eu/s/i4z). + + +### 5. Access-Restrictions + +* `access=*` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:access) + +Apart from turn restrictions, there are access restrictions for different parts of highways. Some of these tags are `access=no`, `access=private` etc which will end up altering the route to be taken during the journey. For more information on the various kinds of `access=*` tags take a look at [Key:access](http://wiki.openstreetmap.org/wiki/Key:access) and [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions) and [access restrictions](http://wiki.openstreetmap.org/wiki/OpenStreetMap_tags_for_routing/Access-Restrictions) + +![749px-mutcd_r5-7](https://cloud.githubusercontent.com/assets/13744156/18048743/b688e696-6e01-11e6-80ae-e65ce6743830.png) + +*An `access=no` for non-motorized traffic, ends up altering the route for bicycle profiles, source: US MUTDC* + +All the `access=private` tags on OpenStreetMap ways, which will not allow that segment of the way to be used in a route can be extracted from this [overpass query](http://overpass-turbo.eu/s/i4J). An example of well-mapped access restrictions in OpenStreetMap can be found in [London](https://www.openstreetmap.org/#map=13/51.5061/-0.1366). + +The sources for mapping access restrictions in OpenStreetMap are: [street view photos](http://blog.mapillary.com/update/2016/05/24/use-mapillary-editing-OpenStreetMap.html), local mapping drives. + +### 6. Traffic signals + +Traffic signals such as: `highway=traffic_signals`, `highway=stop` or `barrier=toll_booth` as well as `traffic_calming=*` are considered during routing. The `type=restriction` more commonly referred to as **turn restrictions** are traffic signage which prohibits certain turns in intersections are also a crucial part of a great `routing` engine. + +More details on mapping `traffic signals` for cars and pedestrians can be found in the [OpenStreetMap wiki](http://wiki.openstreetmap.org/wiki/Tag:highway%3Dtraffic_signals). + +Street view photos from Mapillary, local mapping drives using [OpenStreetMap tracker](http://wiki.openstreetmap.org/wiki/OpenStreetMapTracker_(Android)) can be used as sources to map traffic signals in OpenStreetMap. + +![800px-led_traffic_lights](https://cloud.githubusercontent.com/assets/13744156/18049581/cc237796-6e06-11e6-8d51-b8d446b2c3dc.jpg) + +*Traffic signal in a junction* + + +## Guidance features + +## 1. Exit & destination signs + +**What are exit numbers?** + * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. + + ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) + +**Different tags for exit numbers:** +* `ref=*` is used when the exit has a specific number assigned to it. +* `noref=yes` is used when the exit doesn't have any official number assigned to it. + +**What are destination tags?** + +* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. +* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. + +![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) + +#### Different tags for destinations: +* `destination` tag refers to the place that the way exiting from the freeway leads to. +* `destination:ref` is the reference of the roads directly ahead. +* `destination:ref:to` is to specify the reference of a major highway ahead. +* `destination:street` refers to the main street the way exiting from the freeway leads to. + +An example of a place with good exit/destination coverage in OpenStreetMap is [Ottawa, Canada](http://www.openstreetmap.org/#map=11/45.4283/-75.8331). These overpass queries for [destination](http://overpass-turbo.eu/s/i61) and [exit numbers](http://overpass-turbo.eu/s/i78) can be used to extract exit/destination data from OpenStreetMap. + +The [detailed guide](/mapping/mapping-to-improve-navigation/adding-exit-and-destination-signs/) on adding exit and destination numbers can be followed for adding exit/destinations. This guide is specifically focused on North America (US/Canada) for now. + +### 2. Turn Lanes + +As discussed in `Modeling Roads for navigation` page, there are two types of roads: unidirectional and bidirectional. `lanes=*` tag is used to count the number of lanes in both these type of roads. + +To set number of [lanes](http://wiki.openstreetmap.org/wiki/Key:lanes) for roads which carry traffic in both directions use [`:backward` and `:forward` suffixes](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right#Forward_and_backward) + +`Forward` means the direction in which the way is drawn in OpenStreetMap, while `backward` means the opposite direction. + +``` xml +Example: + highway=tertiary + lanes=5 + lanes:forward=3 + lanes:backward=2 +``` + +In the image below, the number of lanes is two - `lanes=2`. Orange line is the center line of bidirectional way which is the main way direction. When the extra lane starts in a bidirectional way, that segment is tagged as `lanes=3`+`lanes:forward=2`+`lanes:backward=1`. Optionally, we specify [placement](https://wiki.openstreetmap.org/wiki/Proposed_features/placement) of the lanes relative to the way. + + ![residential_road_2](https://cloud.githubusercontent.com/assets/369696/13228435/ae570094-d9a4-11e5-9f3c-4737112a7932.png) + +The below image have two tagging variants: + 1. `lanes=2` - 1 lane for each direction, or + 2. `lanes=3` - denote middle lane for left turn as (:point_left: _this is [discussed](http://wiki.openstreetmap.org/wiki/Proposed_features/Suffix_both_ways)_) + + ``` +highway=residential +lanes=3 +lanes:forward=1 +lanes:backward=1 +lanes:both_ways=1 +turn:lanes:both_ways=left + ``` + ![residential_road_3](https://cloud.githubusercontent.com/assets/369696/13229045/ab01d6f0-d9a7-11e5-8d8a-1fe5518c84a5.png) + + IN case the number of lanes is even but numbers of lanes for each direction not equal. :point_down: + + ![trunk_link](https://cloud.githubusercontent.com/assets/369696/13229897/b09a811c-d9ab-11e5-935e-25906c94585b.png) + +[Turn lanes](http://wiki.openstreetmap.org/wiki/Key:turn#Turning_indications_per_lane) have an influence on the path finding and are one of the most vital components for proper guidance. Choosing the correct turn lane can have a big influence in navigation. Oftentimes, they only help to illustrate a turn better but other times, they are vitally important. In guidance, the aim is to provide a set of instructions, like keep right or keep left by describing the optimum route found by the routing algorithm to a driver. + +![screen shot 2016-03-08 at 7 51 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604319/236e84dc-e568-11e5-850a-cf398719db11.png) + +*How a driver views turn lanes from the car. For a single direction way, it will be tagged `turn:lanes=left|left;through` while for a bidirectional way it will be tagged `turn:lanes:forward/turn:lanes:backward=left|left|through` depending upon OpenStreetMap way direction* + +There are three turn lanes tags in OpenStreetMap: + +``` xml +turn:lanes=* +turn:lanes:forward=* +turn:lanes:backward=* +``` + +Turn lanes can be mapped from high-resolution satellite imagery sources and street level photos. An example of the high density turn lane area in OpenStreetMap is [Los Angeles](https://www.openstreetmap.org/#map=11/33.9883/-118.3303). This [overpass query](http://overpass-turbo.eu/s/ipk) can be used to extract turn lanes data from OpenStreetMap + +[Mapping guide for mapping turn lanes](/mapping/mapping-to-improve-navigation/adding-turn-lanes/): This is a detailed mapping guide for adding turn lanes in general with specific focus on the US. It will be updated as more and more countries are mapped for lane information in OpenStreetMap. + + +-- + +The other important attributes in besides `turn:lanes` and `exit/destination` data required to provide the better guidance using OpenStreetMap data are: +``` xml +lanes=* +name=* +ref=* +relation:route +``` + +Information for [lanes](http://wiki.openstreetmap.org/wiki/Key:lanes), [highway names](http://wiki.openstreetmap.org/wiki/Highways), [highway ref](http://wiki.openstreetmap.org/wiki/Key:ref) and [relation:route](http://wiki.openstreetmap.org/wiki/Relation:route) can be found in their respective OpenStreetMap wikis. \ No newline at end of file diff --git a/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md b/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md new file mode 100644 index 0000000..b193dec --- /dev/null +++ b/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md @@ -0,0 +1,251 @@ +--- +title: Adding turn restrictions +--- +## What are turn restrictions? + +A turn restriction at a junction is represented by a [relation](http://wiki.openstreetmap.org/wiki/Relation) that has a set of tags describing the type of turn restriction. Turn restrictions, like `No-left-turn` and `No-U-turn`, regulate traffic flow at intersections and accurately mapping them is critical for calculating valid routes on a map. + +![image](https://cloud.githubusercontent.com/assets/3423533/15504805/5d678d70-21de-11e6-8290-d20db2380d4d.png) + +## Traffic signs to be added + +Refer to the table given below to spot/match the traffic sign in the Mapillary image against the list of traffic signs and it also consists of the OSM tags: + + +Symbol | Description | OSM Tag | Node/Way/Relation | +------ | ----------- | ------- | ----------------- | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a9/MUTCD_R3-27.svg/80px-MUTCD_R3-27.svg.png)| No straight through | restriction=no_straight_on | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/8/8f/MUTCD_R3-1.svg/80px-MUTCD_R3-1.svg.png)| No Right Turn | restriction=no_right_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/MUTCD_R3-2.svg/80px-MUTCD_R3-2.svg.png)| No Left Turn | restriction=no_left_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/2/2b/MUTCD_R3-3.svg/80px-MUTCD_R3-3.svg.png)| No Turns | restriction=only_straight_on | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/d/d1/MUTCD_R3-4.svg/80px-MUTCD_R3-4.svg.png)| No U-turn | restriction=no_u_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a1/MUTCD_R3-18.svg/80px-MUTCD_R3-18.svg.png)| No Left or U-turn | restriction=no_left_turn; restriction=no_u_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | + + _The last two columns of the table enlists the correct tagging convention for adding the traffic data to OpenStreetMap._ + + +## Using OSM Navigation Map + +The [Navigation map](http://mapbox.github.io/osm-navigation-map/) helps us in recognizing the detected signage overlay from Mapillary on the map. These signage are represented using small circles in 3 colours: + +- **Green** - to be validated +- **Blue** - Reviewed and found valid +- **Yellow** - Reviewed and found redundant +- **Red** - Reviewed and found invalid + +When we click on the green circle, the area is automatically opened in JOSM and popup to select the review is opened in the Navigation map. The same can be opened in iD editor by clicking on **Edit Map** button on top right of the popup. Once done with the review, please add your OSM username. + +![](https://cloud.githubusercontent.com/assets/126868/16987647/ffa78c4a-4eaa-11e6-8bfd-b509b20e482b.gif) + + +## Mapping turn restrictions with iD editor + +The new version of iD, the web editor for OpenStreetMap, makes it even simpler to add turn restrictions to OpenStreetMap. + +### Adding Absolute Turn Restriction: +![epl4xsg](https://cloud.githubusercontent.com/assets/17887418/17285386/fe7453f6-57df-11e6-9d1d-e65ba060bc0b.gif) + +### Adding Conditional Turn Restriction: + ![conditional tr](https://cloud.githubusercontent.com/assets/17887418/17285391/055b6240-57e0-11e6-9c9f-16880b5c6cd2.gif) + +#### Mapillary overlay and Traffic Sign Overlay: + Mapillary has an efficient tool in iD that helps in seeing detected restrictions. Here's how you enable it: + + ![traffic overlay mapillary](https://cloud.githubusercontent.com/assets/17887418/17285393/069163a8-57e0-11e6-9564-293d91b276bc.gif) + +#### Pain Points in adding Turn Restrictions in iD editor: +1. iD editor provides no way of adding a `no_u_turn` restrictions via way. If there is a via way `no_u_turn`, you have to add it using JOSM editor. + + ![image](https://cloud.githubusercontent.com/assets/17887418/17285567/1a145830-57e1-11e6-8e2f-0581bc16695e.png) + +2. In certain cases, adding [no_u_turn turn via node](https://github.com/mapbox/mapping/issues/213#issuecomment-234221535) is also not possible. For such cases, it is better to add it using JOSM. + + +# Mapping turn restrictions with JOSM + +In order to be able to map traffic data easily, there are some plugins that JOSM needs to be configured with: + + - **Plugins to be downloaded**: + - [Mapillary plugin for JOSM](http://blog.mapillary.com/update/2015/06/25/josm-mapillary.html): This plugin allows the user to view mapillary images in JOSM. + - [Turn restrictions plugin for JOSM](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Turnrestrictions): This plugin allows to add turn restrictions to the selected roads with ease. + + ![mapi_plugins](https://cloud.githubusercontent.com/assets/1933377/11438854/cf4768fa-951d-11e5-819a-737d2e03342c.gif) + + - **Map-paint styles to be added**: + - traffic_signs: It displays all the existing traffic signs that have been already mapped on OSM. + + ![mapi_paint](https://cloud.githubusercontent.com/assets/1933377/11442184/3493f780-9539-11e5-985a-ac6a9095dcee.gif) + +## Guide to use the mapillary and turn restriction plugins + + **Using the Mapillary plugin** + + - The Mapillary imagery can be added by clicking on `imagery -> Mapillary` in JOSM. This will add the mapillary layer + over the dataset layer. + - The explanation for how the plugin works can be found [here](http://blog.mapillary.com/update/2015/06/25/josm-mapillary.html). + + **Note**: Every time a new data layer is added, you need to delete the existing **Mapillary layer** and add a new one + +**Using the turn restriction plugin** + - The explanation for how the turn restriction plugin works + can be found [here](http://overpass-turbo.eu/s/gTO). + + +## Start mapping Turn Restrictions + +- This **[Over-pass query](http://overpass-turbo.eu/s/grv)** can be used to get the current count of turn-restrictions present in a city that one is going to work on. This will help us in determining the current state of restrictions and further help in calculating the number of restrictions added by the team. + +**Note:** Change the city name in the above query + +- Use the **[navigation data coverage on OSM](http://mapbox.github.io/osm-navigation-map/#9.56/37.8188/-122.5575) map** to spot the Mapillary signage detections. +- Turn on the `Turn Restrictions`, `Oneways` and `Mapillary Street Photos` layers in the above map +- Click on the turn-restriction traffic symbols detected by Mapillary (which are denoted by green dots on the map) for it to open in JOSM. + + ![navigation](https://cloud.githubusercontent.com/assets/4470913/15466843/26bd5588-20f9-11e6-9eaa-0126e5c83c39.gif) + +- In the Mapillary layer in JOSM, detected traffic signs are represented by a tiny `red triangle` next to the green arrow. Please note that this layer might not be up-to-date. + + ![screen shot 2015-11-27 at 1 41 55 pm](https://cloud.githubusercontent.com/assets/4470913/11436699/1fa70b72-950d-11e5-8e05-9e09013c1f64.png) + +- Probe the previous and next images as well as the satellite imagery data to get a clear idea of the surroundings and then compare them with the existing Mapillary image to find the exact location of the `traffic-sign`. + + ![turn_res](https://cloud.githubusercontent.com/assets/1933377/11443497/a109430c-9543-11e5-8ef9-6907269d6145.gif) + +- Be cautious while adding an `U-turn` via a way in OSM, here is how you add it: + - Select the participating ways + - Go to `Presets -> Relations -> Turn Restrictions` + - Select `no_u_turn` in the `Restriction` field from the drop-down and click on `New Relation` + - In the `Members` section add the respective roles for all the ways enlisted + + + ![u-turn](https://cloud.githubusercontent.com/assets/4470913/15538899/ae22ff9c-229c-11e6-8d82-08b9e18c5540.gif) + + + **Note** + - To get a better idea about the area/road and to see the clear image, always inspect multiple consecutive images. + - With the help of the plugins, look for **traffic restrictions icons** at junctions which are already present on the road/area. + - We should avoid adding `turn restriction` to roads that are leading to one-ways going in the opposite direction, like the example below. It will only result in redundant data: + + ![screen_shot_2015-11-30_at_11_36_26_pm](https://cloud.githubusercontent.com/assets/4470913/11480317/deeac0c6-97bc-11e5-8d0a-852e3ae2f69f.png) + _Here we should avoid adding `turn-restriction` as it will result in redundant data_ + ![screen shot 2016-05-24 at 6 37 06 pm](https://cloud.githubusercontent.com/assets/4470913/15538956/1a068350-229d-11e6-9931-56770c643131.png) + _This situation is a clear indication of a redundant restriction_ + - Add a conditional restrictions when specific conditions are written on the turn-restriction sign-board. + - On certain times of the day. eg. Restriction during peak hours 7AM-10AM + - On a certain day of the year. eg. Restriction on baseball game days only + +## Adding Conditional turn restrictions + +**Special cases** +* [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions) during peak hours are common in SF. Tag them as `restriction:conditional=no_left_turn @ (Mo-Sa 07:00-09:00,16:00-18:00)`
![](https://cloud.githubusercontent.com/assets/4470913/14850426/9d4643f8-0c96-11e6-8c0c-dc94887e1613.png) +* Conditional restriction during baseball games. Ignore
+screenshot 2016-04-27 16 51 33 + +* In the case below, we are leaning towards adding this as a regular `restriction` since it applies for all regular personal vehicles. + + ![screenshot 2016-05-02 12 01 18](https://cloud.githubusercontent.com/assets/12103383/14948422/b9f1838a-105d-11e6-9604-2781de0d6d96.png) + +* If you come across the below instance where the restriction is applicable only on `School Days`. Per discussion we will be adding the restriction for `Monday - Friday` + + ![screen shot 2016-05-06 at 2 57 43 pm](https://cloud.githubusercontent.com/assets/1933377/15074787/7c6594d4-13be-11e6-9c01-1d277070960e.png) + +## QA for turn restrictions + +During turn restrictions mapping in various cities, we have come across certain special cases where we need to pay more attention while mapping. These cases are noted down here for your reference. + +---- + +# Be cautious when you come across these turn restrictions + +**1. Restrictions on Red** + +Be careful with interpreting signage and always verify Mapillary signage overlay with the image and the kind of restriction. The image below shows a sign for no free right that Mapillary interpreted as `no-right-turn`. This is NOT a turn restriction. If you are not sure, consult the community before mapping. +
screenshot 2016-04-26 21 39 06 + +A similar restriction found in Canada depicts that **left turn** cannot be taken when the signal is red, otherwise it is permitted to turn left. We are **not** adding such turn restrictions. + +![no_right_turn_on_red_sign](https://cloud.githubusercontent.com/assets/4470913/17021102/28acf658-4f63-11e6-8266-b380071706c4.jpeg) +_Picture by Share Bear - Own work - [Public Domain](https://commons.wikimedia.org/w/index.php?curid=8626974)_ + +**2. Location and bearing of Mapillary Signage overlay** + +The location and bearing of the Mapillary photo is not reliable and is prone to usual GPS errors. Cross check the photograph with the map to confirm you are looking at the intersection from the correct bearing. This photograph is facing the reverse of actual heading. +
screenshot 2016-04-27 12 28 12 + +**3. Single restriction per image detection** + +Mapillary will detect only one sign type per image. Lookout for multiple restrictions in the image
+screenshot 2016-04-27 17 49 34 + +**4. Careful with Turn restrictions plugin in JOSM** + +Sometimes the **Turn restrictions plugin** does not detect the correct signs i.e. even though it's a `no-right-turn`, the plugin detects it as `no-left-turn`. So be extra sure before adding the restriction +![turn_restrictions_plugin_bug](https://cloud.githubusercontent.com/assets/4470913/15529626/4f438044-226c-11e6-919e-02481acb5ad1.gif) + +**5. Advantage of previous/next images** + +There might be an offset in the Mapillary images, that is the image may appear after/before the actual location. It is ideal to inspect the previous and next images and also look for road names and other clues from the satellite imagery to verify it's exact location and bearing. +![offset_mapillary](https://cloud.githubusercontent.com/assets/4470913/15539155/712f0296-229e-11e6-8675-fecc95f4be51.png) + +**6. Temporary turn restrictions** + +When the roads are in construction or under repair, you might see temporary turn restrictions placed similar to shown in the below image. We are not adding temporary turn restrictions. +![pjimage](https://cloud.githubusercontent.com/assets/8921295/17290390/d8808ac2-57fb-11e6-8816-d681033e2a8f.jpg) + + + +**7. Restriction-ahead warnings** + +In the below image, there is a no_left_turn sign board as detected from the Mapillary image. This sign board means that there is a ```no_turn_restriction``` ahead. But this signage itself is **not** a turn restriction, so we do not map this. +[![screenshot 2016-07-26 15 31 15](https://cloud.githubusercontent.com/assets/8921295/17133998/03bf2e10-5346-11e6-949f-dcd4f554560b.png)](https://cloud.githubusercontent.com/assets/8921295/17133964/e83159fc-5345-11e6-935a-5b535390f730.jpg) + + +# Different conventions for turn restrictions in different countries + +### Canada + +**Case:1** + +The image below shows two signages, the first one is in French and translates to 'Wait for arrow to turn left' and the second one is a `no_u_turn`. In such cases, we ignore the the first signage and go ahead mapping `no_u_turn`. + +[![screenshot 2016-07-26 14 34 36](https://cloud.githubusercontent.com/assets/8921295/17132558/efc2a398-533f-11e6-93d7-7dc0e87978ae.png)](https://d1cuyjsrcm0gby.cloudfront.net/4ZA3OT0nHoDQ7F7JILG-pg/thumb-2048.jpg) + + +**Case:2** + + +In the below image, the first board for ```no_left_turn``` says Monday to Friday 8am-10am and 3pm-7pm (Lun-Ven 8h-10h,15h-19h in French). The second board is a ```no_u_turn``` **except authorized vehicles**. In this case, first one would be a conditional turn restriction; second, an absolute ```no_u_turn``` turn restriction. + +[![screenshot 2016-07-26 14 48 15](https://cloud.githubusercontent.com/assets/8921295/17132580/093ab860-5340-11e6-9863-ffe150f7c8c8.png)](https://d1cuyjsrcm0gby.cloudfront.net/IYi6WjwOQDnPW1HTTGyh8A/thumb-2048.jpg) + +**Case:3** + +The below image indicates that all the drivers (no matter the lane they are on) must follow this/these direction(s) at the intersection. This means that the driver needs to only turn right/left on the days mentioned in the sign and during that duration of the day. + +![image](https://cloud.githubusercontent.com/assets/3423533/17128539/0b5166e0-532b-11e6-96e6-69d21603f183.png) + +**Syntax to be used:** `restriction:conditional=only_right_turn @ (Mo-Fr 07:00-09:00,16:00-18:00)` + +### Germany + +In Germany, instead of signages to prohibit turns, the signages describe the legally allowed turns at the junction. Hence a signage for a no right turn will indicate only turns for left and straight. + +![screen shot 2016-08-17 at 4 12 05 pm](https://cloud.githubusercontent.com/assets/11845908/17733853/568ce2b6-6496-11e6-8665-8983fe1c94db.png) + +_An example of a `restriction=no_right_turn` traffic sign in Germany_ + +### Turn restriction signs of Germany and what it means: + +![screen shot 2016-08-17 at 4 27 33 pm](https://cloud.githubusercontent.com/assets/11845908/17734070/a6125f5e-6497-11e6-8d70-d55248e938ec.png) + +*Courtesy: [German wiki](http://wiki.openstreetmap.org/wiki/DE:Relation:restriction)* + + +**Reference** + +- OSM tags for routing http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing +- Turn restrictions http://wiki.openstreetmap.org/wiki/Relation:restriction +- Access restrictions http://wiki.openstreetmap.org/wiki/Key:access +- Conditional restrictions http://wiki.openstreetmap.org/wiki/Conditional_restrictions + +**Spanish version [here](https://github.com/mapbox/mapping/wiki/Gu%C3%ADa-de-mapeo-para-a%C3%B1adir-restricciones-de-giro-utilizando-mapillary)!** \ No newline at end of file diff --git a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md new file mode 100644 index 0000000..1a62fe6 --- /dev/null +++ b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md @@ -0,0 +1,135 @@ +--- +title: Adding exit and destination signs +--- + +![5138660996_1957ee06ed_o](https://cloud.githubusercontent.com/assets/17887418/15180552/ec541b64-179f-11e6-88d7-4b3074f161e4.jpg) + +## What are exit numbers? + * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. + + ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) + +### Different tags for exit numbers: +* `ref=*` is used when the exit has a specific number assigned to it. +* `noref=yes` is used when the exit doesn't have any official number assigned to it. + +## How to add exit numbers? + +* Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. + +* Select the assigned highway from the dropdown and click on the `download` button. + + ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) + +### Verify the exits on the route for missing information + +* Load the route in JOSM + +![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) + + ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) + + * Browse along the route and check the ways on both directions at every exit location for the following: + - There is a `motorway_junction` at the start of every `motorway_link` exiting the highway + - The `motorway_junction` has a correct exit number `ref` value as per the source. + - The exit number on both directions are the same + - There is only one exit in a direction for every exit number + +**Add missing exit numbers** + +* Download the data and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) around the blue marker in the imagery. + +* Use a combination of Mapillary, Department of Transportation (DoT) documents and Wikipedia to add the `ref=*` tag on `highway=motorway_junction` (stick to using Mapillary and DoT doc as primary source and move to others in case of unavailability of information) + +* If it is confirmed there is no exit number for the `motorway_junction` add another tag `noref=yes` to indicate the exit does not have an official reference number. + + + +## Analyzing signboards in mapillary + +Look out of Highway sign boards on imagery. They may look something like this- + +![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) + +Places to look for- +- near a `motorway_junction` +- near **start** of a `motorway_link` + +![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) + + + +### Do's and don'ts +- It is not necessary that exit numbers are sequential. It might find 45 after 41. +- There are some `motorway_junction` which don't have any associated exit number. Add `noref=yes` on these nodes. +![no ref](https://cloud.githubusercontent.com/assets/17470597/15071466/65aff514-13a9-11e6-9392-3677c8b193a0.jpg) + +- If there are multiple exits on the same [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) then you can tag them as `ref=* ; *` instead of `ref:left=*` and `ref:right=*` until you are confirmed with that. + +- In the case of discrepancy between mapillary and DoT document, look out for the recent change in exit numbers on the web. Many states changes/in a process to change the exit numbers. +- **Ignore the `highway=motorway_junction` where the traffic flow is towards the motorway** + + +## What are destination tags? + +* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. +* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. + +![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) + +### Different tags for destinations: +* `destination` tag refers to the place that the way exiting from the freeway leads to. +* `destination:ref` is the reference of the roads directly ahead. +* `destination:ref:to` is to specify the reference of a major highway ahead. +* `destination:street` refers to the main street the way exiting from the freeway leads to. + +## How to add destination tags? + +### Assign a highway and use Checkautopista2 to map features + +1. Open the destination reference document for your assigned city area. Pick a highway to check and assign it on the spreadsheet to avoid conflict. + +2. Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. + +3. Select the assigned highway from the dropdown and click on the `download` button. + + ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) + + +4. Look out for red outer circle for missing destination. Use `open in JOSM` button to open the node in JOSM. Orange outer circle represents `exit_to` tag and we don't need to add destination tags in the way. Green outer circle represent that the concern way already has destination tag. + + + ![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) + + ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) + + +5. Download the data around the `motorway_junction` and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs). + +7. Use combination Mapillary images, DoT documents, and Wikipedia to add destination as `destination=*` on `motorway_link` ways and the destination highway as `destination:ref=*`. + **Below is a an example** + ![screen shot 2016-03-14 at 6 28 27 pm](https://cloud.githubusercontent.com/assets/12744420/13745188/a12098bc-ea12-11e5-8ffc-9fb839ed5aa2.png) + **On the `highway=motorway_link`(represented by red line) add `destination=Daly City` and `destination:ref=I 280 South`. This can be confirmed with [DoT document](http://www.dot.ca.gov/hq/traffops/engineering/calnexus/pdf/101.pdf) and [wikipedia](https://en.wikipedia.org/wiki/U.S._Route_101_in_California) while searching for exit number 431** + +8. Add any highway missing in the highway spreadsheet. Mark the highway done if all destination tags are mapped/review + + + +## Analyzing signboards in mapillary + +Look out of Highway sign boards on imagery. They may look something like this- + +![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) + +Places to look for- +- near a `motorway_junction` +- near **start** of a `motorway_link` + +![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) + + + +### Do's and don'ts +- Use `;` to separate multiple destination and refs. +- Read more on [Highway intersection](https://en.wikipedia.org/wiki/Interchange_(road)) to understand them better. + diff --git a/mapping-for-navigation/_posts/0000-01-06-adding-turn-lanes.md b/mapping-for-navigation/_posts/0000-01-06-adding-turn-lanes.md new file mode 100644 index 0000000..24c5b7d --- /dev/null +++ b/mapping-for-navigation/_posts/0000-01-06-adding-turn-lanes.md @@ -0,0 +1,247 @@ +--- +title: Adding turn lanes +--- + +## What is a turn lane + +A turn lane is an auxiliary lane demarcated on the road to specify directions to ongoing vehicles. +Turn lanes serve two purposes: + * Provide directional information to the ongoing vehicles and + * Provide the lane information to be chosen for the vehicles changing their direction + +### Types of turn lanes + +There are a total of 12 different turn lanes demarcated on the roads. They are: + +Turn Lane | Representation +--- | --- +turn:lanes = left | ![left](https://cloud.githubusercontent.com/assets/8401827/13217928/1d2fc24e-d98c-11e5-9d20-c526fe6e7f01.jpg) +turn:lanes = right | ![right](https://cloud.githubusercontent.com/assets/8401827/13217945/424f36e0-d98c-11e5-99e7-9d178f2529a1.jpg) +turn:lanes = through | ![through](https://cloud.githubusercontent.com/assets/8401827/13214156/f885d4b4-d973-11e5-9fb7-e9ecb70a932b.jpg) +turn:lanes = left;through | ![through left](https://cloud.githubusercontent.com/assets/8401827/13217986/80786072-d98c-11e5-99c6-db8665977550.png) +turn:lanes = right;through | ![through_right](https://cloud.githubusercontent.com/assets/8401827/13218022/b8aa9352-d98c-11e5-87c2-d8c17ee68305.jpg) +turn:lanes = left;through;right | ![leftthroughright](https://cloud.githubusercontent.com/assets/8401827/13218061/027e10ee-d98d-11e5-9747-c6867e0787b0.JPG) +turn:lanes = left;right | ![left_right](https://cloud.githubusercontent.com/assets/8401827/13217579/8f833c66-d989-11e5-9b2c-dc98fdff09b2.png) +turn:lanes = slight_left | ![slightleft](https://cloud.githubusercontent.com/assets/8401827/13218207/e450feaa-d98d-11e5-938c-a3956de2f7ba.png) +turn:lanes = slight_right | ![slightright](https://cloud.githubusercontent.com/assets/8401827/13218219/07052b56-d98e-11e5-8fc0-82b945fb95c6.png) +turn:lanes = merge_to_left | ![merge to left](https://cloud.githubusercontent.com/assets/8401827/13218244/2ca1fd6c-d98e-11e5-8be9-cb64271f5991.png) +turn:lanes = merge_to_right | ![fahrbahn_2](https://cloud.githubusercontent.com/assets/8401827/13218183/bc5d0790-d98d-11e5-9781-307f80cc0732.png) +turn:lanes:bothways = * | ![turn lanes both ways](https://cloud.githubusercontent.com/assets/8401827/13217721/a2594d48-d98a-11e5-87f1-11e11ebf57ec.png) + + ![](http://pdd.ua/r/r/EEB7A996-D8DC-40FC-87EA-01F3E115BC7C/m_1.18_4.jpg) + _road markings on the ground_ - © [pdd.ua](http://pdd.ua/ua/34/1.18/) + +### Pre-requirements for mapping a turn lane in JOSM + +Before mapping turn lanes activate the following preferences in JOSM to visualize the mapped turn lanes: `preferences > Map Settings` +* *`Map Paint Styles > Lane and road attributes`* + + ![lane_and_road_attributes](https://cloud.githubusercontent.com/assets/13744156/13218788/c55fab96-d991-11e5-89b2-b281986d704e.gif) + +* *`Tagging Presets > lane attributes`* + + ![tagging_presets](https://cloud.githubusercontent.com/assets/13744156/13218902/ad15c902-d992-11e5-872b-1bde24f27f5b.gif) + +* Filter out non-road features with inverse filter: `boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:` + +**Plugins** + +* Knife-tool: https://gist.github.com/jothirnadh/a10daeaef1498537ea56f0a65f7fdbc2 +* TurnLanes-tagging plugin: `JOSM Preferences > Plugins > turnlanes-tagging` + +### Mapping a turn lane + +* Check all roads in the imagery for turn lanes at junction points + + ![roads_markings](https://cloud.githubusercontent.com/assets/126868/11710074/b58b52e4-9f42-11e5-971a-000a699a0b6d.png) + +* Split the road into segments based on the total number of lanes for the segment. The easiest way for splitting the road is by using [Knife_tool](https://gist.github.com/jothirnadh/a10daeaef1498537ea56f0a65f7fdbc2) + + ![residential_road](https://cloud.githubusercontent.com/assets/369696/13223732/34cf7ffa-d98e-11e5-9a33-8f40f6498004.png) + +* For each road segment tag the turn lanes based on the road markings in the direction of the way. Eg. `turn:lanes=left|left;through|through`. Check [OSM turn:lanes](http://wiki.openstreetmap.org/wiki/Key:turn:lanes) for reference. + + ![oneway_turn:lanes_tagging](https://cloud.githubusercontent.com/assets/8401827/13252110/a6bdea8a-da5a-11e5-8c79-aa15c0c15f68.gif) + +* For bi-directional segments, use `turn:lanes:backward=` and `turn:lanes:forward=` to specify turn lanes in each direction. + + ![bidirectional_tagging](https://cloud.githubusercontent.com/assets/13744156/13219545/acd78f62-d996-11e5-85eb-3e05a7b79d3b.gif) + +* Verify correct tagging using the `Lane attributes` style + + ![lane_attributes](https://cloud.githubusercontent.com/assets/8401827/13251884/ddcbdd54-da58-11e5-86ae-c4a2918c9577.gif) + +* The simplest way to add turn lanes is by using **[turnlanes-tagging plugin](https://www.mapbox.com/blog/turnlanes-tagging/)** + +![turnlenes](https://cloud.githubusercontent.com/assets/8401827/17246767/d086ef48-55ab-11e6-8bce-46c434cb9005.gif) + +### `turn:lanes` and relations + +We use [relations](http://wiki.openstreetmap.org/wiki/Relation) for different purpose – for indicating [turn restriction](http://wiki.openstreetmap.org/wiki/Relation:restriction) or collect separate ways into solid [route](http://wiki.openstreetmap.org/wiki/Relation:route). +​ +JOSM help us to handle them. But sometimes we are faced with not properly denoted relations. JOSM will inform about it while uploading our changes. You may [ignore messages of level "Warnings"](https://github.com/mapbox/mapping/issues/153#issuecomment-185679507) (if you only split ways and didn't edit relations manually) but you have to fix all "Errors". + +## QA for turn lanes mapping + +While mapping turn lanes, there are a lot of scenarios are encountered in [#153](https://github.com/mapbox/mapping/issues/153) and [#144](https://github.com/mapbox/mapping/issues/144) mapping repos. All these scenarios are drafted in one place for validation purposes. + +## Different scenarios we came across while mapping + +### 1. Parking lanes + +In the U.S., when parallel parking spaces are marked, they are marked in one of [three ways](http://mutcd.fhwa.dot.gov/htm/2009/part3/fig3b_21_longdesc.htm): + + ![parking_lanes](https://cloud.githubusercontent.com/assets/8401827/13172245/326a7bb6-d71d-11e5-8617-a2516f75144b.png) + +Here’s an example of the box marking style: + + [![boxes](https://upload.wikimedia.org/wikipedia/commons/thumb/0/03/J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG/320px-J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG)](https://commons.wikimedia.org/wiki/File:J.S._Shingler_Bldg_%28East_face%29,_McLendon_St,_Ashburn.JPG) + +### 2. Counting number of turn lanes + +If there are no clear cut demarcations on the road and yet cars are parked on either sides of the road, consider them as drive lanes. Case below: + + ![number_of_lanes](https://cloud.githubusercontent.com/assets/8401827/13142482/5b26d0a0-d663-11e5-90cd-4a65d75e7248.png) + +### 3. Starting a turn lane + + Turn lanes should begin exactly as per the marking in the imagery, not before or after. + + ![turn:lanes_start](https://cloud.githubusercontent.com/assets/8401827/13110125/0fe83ad0-d5a4-11e5-82ff-00245d0ba043.png) + +### 4. Ending a turn lane + +Turn lanes should terminate at the first highway junction after the start of the turn lane. + + ![turn:lanes_end](https://cloud.githubusercontent.com/assets/8401827/13143057/4ff2b3c6-d667-11e5-8069-b028fabf7587.png) + +### 5. Turn lane forward + +In case of bi-directional ways, the key [turn:lanes:forward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the same direction as the osm-way; while adding this we must view the road in the direction to the osm-way(**on the direction where the osm-way arrow is pointing**). + + ![turn:lanes:forward](https://cloud.githubusercontent.com/assets/8401827/13175904/c5c922fc-d733-11e5-91b1-c0f9e5181fda.gif) + +### 6. Turn lane backward + +In case of bi-directional ways, the key [turn:lanes:backward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the opposite direction as the osm-way; while adding this we must view the road in the oppoiste direction to the osm-way(**opposite to direction where the osm-way arrow is pointing**). + + ![turn:lanes:backward](https://cloud.githubusercontent.com/assets/13744156/13172709/859957c4-d71f-11e5-8cd9-ea154ad5d2e8.gif) + + *Adding a `turn:lanes:backward` tag* + +### 7. Adding dual carriageways: + +When finding roads mapped as single carriageway while the imagery shows clear separation between roads, split the road where the physical separation starts and add dual carriageways. + +![dualcarriageway](https://cloud.githubusercontent.com/assets/8401827/13393542/117b59aa-df08-11e5-8fd3-21a931531f84.png) + + +**When to add dual carriageway?** +- Add Dual-carriage when + - you see physical separation betweens roads + - **no relation is attached to the way.** +- Add `turn:lanes` tag to both the ways. + + +### 8. Bicycle lanes and road shoulders + +Road shoulders and bicycle lanes are ignored from the lane count. Both these roads are `lanes=2` + + ![bicycle+shoulders](https://cloud.githubusercontent.com/assets/126868/11715007/628dd90a-9f64-11e5-9e22-58614d2afbf6.png) + + ![bicycle_lanes](https://cloud.githubusercontent.com/assets/13744156/13172922/adc69f08-d720-11e5-8600-7a606d2e9bae.png) + + *lanes=3 for the above example, ignoring the two cycle ways* + +* Ignore bicycle lanes even though they are in the middle;example below: + + ![xyz2](https://cloud.githubusercontent.com/assets/8401827/13495220/79a65aca-e16f-11e5-83e7-24d3e4f53ad0.png) + + *The middle way is also a bicycle lane which is not counted while adding the `lanes` tag* + +* Additionally, `Strava global-heat cycle` layer can used to verify if a particular lane is a cycle-way. +`tms[16]:http://globalheat.strava.com/tiles/cycling/color3/{zoom}/{x}/{y}.png` + +### 9. Lane marked as a separate way + +Do not add turn lanes in these cases where the only turn lane is already a mapped as a separate way. + + ![lane_as_separate_way](https://cloud.githubusercontent.com/assets/13744156/13173428/6694c468-d723-11e5-96be-b95502b9f58a.png) + +### 10. Bidirectional turn lanes + +These are the lanes marked with symbol representing both directions at a time. + + ![turn:lanes:both_ways](https://cloud.githubusercontent.com/assets/8401827/12642951/0162ff9c-c5df-11e5-8a14-a41f263ae086.png) + +Tag used for such lanes are `turn:lanes:both_ways=*` + +Yellow lines on both sides of a lane also gives an indication of `turn:lanes:both_ways=*` + +![screen shot 2016-05-16 at 4 12 49 pm](https://cloud.githubusercontent.com/assets/1933377/15287587/8dd24396-1b81-11e6-8527-b84814804175.png) + +![screen shot 2016-05-16 at 4 13 00 pm](https://cloud.githubusercontent.com/assets/1933377/15287591/9165c50a-1b81-11e6-9521-93cea4b7be16.png) +### 11. Mapillary Plugin to verify turn lanes + +The imagery at some places is not very clear and at-times the turn-lanes are covered by cars. In situations like these `Mapillary plugin` can be used. If there is Mapillary imagery coverage in that area, they can used to verify the presence of turn-lanes. + +**Name of the plugin:** Mapillary + + ![turnlanes_mapillary](https://cloud.githubusercontent.com/assets/4470913/12884912/6b405d1e-ce87-11e5-8d0f-cd8a8a8b3dfd.gif) + +### 12. Lanes with restricted access + +These are the areas on streets which are restricted for vehicular traffic. + +![screen shot 2016-03-15 at 3 36 36 pm](https://cloud.githubusercontent.com/assets/8401827/13776503/84c34002-ead0-11e5-911d-0581fe9173b7.png) + +![screen shot 2016-03-14 at 4 46 03 pm](https://cloud.githubusercontent.com/assets/8401827/13776504/84e64138-ead0-11e5-81f0-7918311ec6dc.png) + +![screen shot 2016-03-14 at 4 46 29 pm](https://cloud.githubusercontent.com/assets/8401827/13776505/84e71888-ead0-11e5-9135-553c11d99d12.png) + +In the above cases the areas with markings on the roads are not considered as a lane + +### 13. Reverse direction turn lanes + +These are the lanes specifically categorized to take U-turn or reverse-turn. + +![screen shot 2016-03-14 at 2 25 28 pm](https://cloud.githubusercontent.com/assets/8401827/13776502/84944b6c-ead0-11e5-92fa-0bb2951760ef.png) + +### 14. The order of the directions and valid combinations of values + + - `none` itself is valid value but **not** in conjunction with other + + - ✅ `turn:lanes=none|right` is equal to `turn:lanes=|right` - we use `none` for "_better readability_" + + - 👎 `turn:lanes=left||none|merge_to_right` - this combination of values is valid but there is mixing `none` and `||` (empty) - this is not good choice. + + - 👍 `turn:lanes=left|none|none|merge_to_right` or `turn:lanes=left|||merge_to_right` + + - ❎ `turn:lanes=none|none|none` or `turn:lanes=||` - in this case `turn:lanes=*` tag is redundant, just specify `lanes=3` or real number of lanes + + - ❎ `turn:lanes=none|none;slight_right` - isn't valid combination - "_there are no turn indications_" on the rightmost lane. Instead, must be used (based on https://github.com/mapbox/mapping/issues/180#issuecomment-225574666) + +``` +lanes=2 +turn:lanes=none|through;slight_right +transit:lanes=continue|new_on_right +``` + +- using `*right` | `*left` values + + - ✅ `turn:lanes=left|none|none` or `turn:lanes=||right` or `turn:lanes=merge_to_right||` or `turn:lanes=left|left;through|none|slight_right|right|right`- 👍 + + - ❎ `turn:lanes=|right|left|` or `turn:lanes=none|right|left|through` or `turn:lanes=none|left|none`- 👎 lanes that go in one direction should not cross with each other + +- using `reverse` value + + - `reverse` (u-turn) have to be on the leftmost lane for right-hand traffic or on the rightmost lane for right-hand + +### 15. + +_to be continued …_ + +### Further reading: +* [Mapping turn lanes: OSM wiki](http://wiki.openstreetmap.org/wiki/Key:turn) +* [Mapping turn lanes in OpenStreetMap by Andrey Golovin](https://www.mapbox.com/blog/turn-lanes-mapping/) +* Diary post by @Andygol : [Mapping turn lanes in OpenStreetMap](http://www.openstreetmap.org/user/andygol/diary/35489#) diff --git a/mapping-for-navigation/_posts/0000-01-07-resources-and-references.md b/mapping-for-navigation/_posts/0000-01-07-resources-and-references.md new file mode 100644 index 0000000..1c9eed5 --- /dev/null +++ b/mapping-for-navigation/_posts/0000-01-07-resources-and-references.md @@ -0,0 +1,49 @@ +--- +title: Resources and References +--- + +**Mapbox navigation mapping projects** + +Navigation mapping forms a large part of Mapbox's mapping sprints in recent times. Given below are a few examples of some of the latest navigation mapping efforts across US, Canada, and Europe. To get an idea about all our historical mapping projects related to navigation in OSM, look into the [mapping repository](https://github.com/mapbox/mapping/issues). Our mapping projects are conducted in the open with active participation, feedback, and validation from the community. + +#### Examples + +Location | Description|Start|End(ETA)|Validation +---|---|---|---|---| +[Mapping turn lanes in 30 US cities](https://github.com/mapbox/mapping/issues/180)| Mapping all the turn lanes from satellite imagery in 30 US cities from secondary and above|04/05/2016|Continuing|Continuing +[Updating turn restrictions in Germany](https://github.com/mapbox/mapping/issues/226)| Updating missing turn restriction coverage in 3 german cities: Berlin, Stuttgart, Wolfsburg|29/08/2016|Continuing|Continuing +[Mapping turn restrictions in Canada](https://github.com/mapbox/mapping/issues/213)|Mapping turn restrictions from mapillary in top 5 cities in Canada|22/07/2016|05/08/2016|Completed +[Exit and destination mapping in Canada](https://github.com/mapbox/mapping/issues/220)|Map the exit and destination numbers in top 5 Canada cities using mapillary|11/08/2016|17/08/2016|Completed + +**Navigation data tools** + +* [OpenStreetMap navigation map](http://mapbox.github.io/osm-navigation-map/#11.63/37.7896/-122.4363): This map is used to add turn restrictions in OSM. It has a detected signage mapillary layer for easy detection of turn restrictions, oneways and a dataset which displays all the valid, invalid and redundant turn restrictions added. Get more [instructions](https://github.com/mapbox/osm-navigation-map/blob/gh-pages/MAPPING.md) on `how to use the OSM navigation map`. +* [CheckAutopista2](http://k1wiosm.github.io/checkautopista2/): It is a tool to investigate and add highway signboard features on motorways and freeways. For more details look into the [github repository](https://github.com/k1wiosm/checkautopista2) for `checkautopista`. +* [Overpass](https://overpass-turbo.eu/): The place to query and extract all OSM data related to a specific feature. It has a simple query builder feature that helps in querying each and every feature in OSM. Details about [overpass](http://wiki.openstreetmap.org/wiki/Overpass_turbo) can be found [here](http://wiki.openstreetmap.org/wiki/Overpass_API) and [here](http://wiki.openstreetmap.org/wiki/Overpass_API/Language_Guide). +* [Knife tool](https://www.mapbox.com/blog/knife-tool/): The knife tool can be used for quick splitting of ways while adding navigation features such as turn lanes. For more details, look [here](https://github.com/mapbox/auto-tools/tree/split) +* [Turn lanes tagging plugin](https://www.mapbox.com/blog/turnlanes-tagging/): With this plugin, you can add complex tag combinations for turn lanes at road junctions with ease, and minimize errors. For more details, look [here](https://github.com/JOSM/turnlanes-tagging) + + + +**Country specific navigation guide** + - Images of traffic signs and road markings : Traffic signs and road markings may undergo small changes and specific cases when mapping turn restrictions using Mapillary. There are subtle differences in turn restrictions between Canada, US, and Germany. *(This section is to be kept updated with new signages every time mapping is done in a separate country with new conventions)* + +1. **[Turn restriction images in US](https://gist.github.com/abhisheksaikia/7c9329a985816c128aabcba092747816)** + +2. **[Turn restrictions images in Germany](https://gist.github.com/abhisheksaikia/646b918fc64f9d8109b5d62a8137e86a)** + +3. **[Turn restrictions in Canada](https://gist.github.com/abhisheksaikia/bcfbf4ea0dc1e100337244867b2524fc)** + +4. **[Turn restrictions in France](https://gist.github.com/jothirnadh/3d0245816dabbf395c447130877c538c)** + + +For more details on cases for turn restrictions and signages in different countries take a look at [QA for mapping turn restrictions](https://gist.github.com/abhisheksaikia/6e12973daa5be78da3ef9ba6d21b8562) + +**Data sources and references for navigation data** + +* [Mapillary](https://www.mapillary.com/) + +* [OpenStreetView](http://openstreetview.org/map/) +- **DOT documents/websites**: Local official websites, documents released by local `Department of Transportation` bodies. +- **Wikipedia**: Exit and destination numbers, highways, highway refs. *(must be verified on ground or with official sources)* +- High resolution satellite imagery: Bing, Mapbox, USGS, open satellite datasets ([Landsat](http://landsat.usgs.gov/), [Sentinel2](http://www.esa.int/Our_Activities/Observing_the_Earth/Copernicus/Sentinel-2/Data_products), [LISS](http://bhuvan.nrsc.gov.in/data/download/index.php), government opendata portals). From 89dbad933134b085c3fe0fd03f2a46212f52a3d1 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Mon, 24 Oct 2016 20:01:58 +0530 Subject: [PATCH 28/66] fixing broken links --- .../_posts/0000-01-03-road-features-mapping-guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md b/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md index 44660bc..8c1f1bf 100644 --- a/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md +++ b/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md @@ -57,7 +57,7 @@ The best source of mapping oneways are again street level photos. * `type=restriction` * [OSM Wiki](http://wiki.openstreetmap.org/wiki/Relation:restriction) -* [Mapping guide](/mapping/mapping-to-improve-navigation/adding-turn-restrictions/) +* [Mapping guide](../adding-turn-restrictions/) `type=restriction` is added to a relation in OpenStreetMap which is used to describe turn restrictions at junctions. The relation has a set of tags that describes the type of restriction, for example. `no_left_turn`, `no_right_turn`, `no_u_turn`, etc. These are traffic signs at junctions and this information must be present on the map to find the best route by the routing engine while planning a route. @@ -145,7 +145,7 @@ Street view photos from Mapillary, local mapping drives using [OpenStreetMap tra An example of a place with good exit/destination coverage in OpenStreetMap is [Ottawa, Canada](http://www.openstreetmap.org/#map=11/45.4283/-75.8331). These overpass queries for [destination](http://overpass-turbo.eu/s/i61) and [exit numbers](http://overpass-turbo.eu/s/i78) can be used to extract exit/destination data from OpenStreetMap. -The [detailed guide](/mapping/mapping-to-improve-navigation/adding-exit-and-destination-signs/) on adding exit and destination numbers can be followed for adding exit/destinations. This guide is specifically focused on North America (US/Canada) for now. +The [detailed guide](../adding-exit-and-destination-signs/) on adding exit and destination numbers can be followed for adding exit/destinations. This guide is specifically focused on North America (US/Canada) for now. ### 2. Turn Lanes @@ -201,7 +201,7 @@ turn:lanes:backward=* Turn lanes can be mapped from high-resolution satellite imagery sources and street level photos. An example of the high density turn lane area in OpenStreetMap is [Los Angeles](https://www.openstreetmap.org/#map=11/33.9883/-118.3303). This [overpass query](http://overpass-turbo.eu/s/ipk) can be used to extract turn lanes data from OpenStreetMap -[Mapping guide for mapping turn lanes](/mapping/mapping-to-improve-navigation/adding-turn-lanes/): This is a detailed mapping guide for adding turn lanes in general with specific focus on the US. It will be updated as more and more countries are mapped for lane information in OpenStreetMap. +[Mapping guide for mapping turn lanes](../adding-turn-lanes/): This is a detailed mapping guide for adding turn lanes in general with specific focus on the US. It will be updated as more and more countries are mapped for lane information in OpenStreetMap. -- From ebb8db759f9bd6ccee1381417b1a7c8f65661e36 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Thu, 27 Oct 2016 17:32:57 +0530 Subject: [PATCH 29/66] changes to incorrect formatting --- .../_posts/0000-01-04-adding-turn-restrictions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md b/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md index b193dec..621b78d 100644 --- a/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md +++ b/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md @@ -54,11 +54,11 @@ The new version of iD, the web editor for OpenStreetMap, makes it even simpler t ![traffic overlay mapillary](https://cloud.githubusercontent.com/assets/17887418/17285393/069163a8-57e0-11e6-9564-293d91b276bc.gif) #### Pain Points in adding Turn Restrictions in iD editor: -1. iD editor provides no way of adding a `no_u_turn` restrictions via way. If there is a via way `no_u_turn`, you have to add it using JOSM editor. +* iD editor provides no way of adding a `no_u_turn` restrictions via way. If there is a via way `no_u_turn`, you have to add it using JOSM editor. ![image](https://cloud.githubusercontent.com/assets/17887418/17285567/1a145830-57e1-11e6-8e2f-0581bc16695e.png) -2. In certain cases, adding [no_u_turn turn via node](https://github.com/mapbox/mapping/issues/213#issuecomment-234221535) is also not possible. For such cases, it is better to add it using JOSM. +* In certain cases, adding [no_u_turn turn via node](https://github.com/mapbox/mapping/issues/213#issuecomment-234221535) is also not possible. For such cases, it is better to add it using JOSM. # Mapping turn restrictions with JOSM From 21ea553c0839ca1cbd61918340752f8b5201bff3 Mon Sep 17 00:00:00 2001 From: Katy DeCorah Date: Thu, 6 Apr 2017 14:36:37 -0400 Subject: [PATCH 30/66] add swiftype tags --- _layouts/default.html | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/_layouts/default.html b/_layouts/default.html index f80e680..1110973 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -9,6 +9,15 @@ {% if page.description %}{% endif %} {% if page.title == 'Mapbox' %}{{page.title}} | Design and publish beautiful maps{% else %}{{page.title}} | Mapbox{% endif %} + + + {% if page.date and site.baseurl == '/blog' %} + {% endif %}{% if page.tags %} + {% for tags in page.tags %} + {% endfor %}{% endif %}{% if page.category and page.category !='none' %} + {% endif %}{% if page.author %} + {% endif %}{% if page.excerpt or page.description %} + {% endif %} {% if page.card %} From 3fe00f0201575399e3a80cb8fed6761b114a5258 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Tue, 9 May 2017 13:13:16 +0530 Subject: [PATCH 31/66] adding fast mapping documentation for buildings and roads --- ...ilding-and-road-mapping-tricks-and-tips.md | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md diff --git a/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md b/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md new file mode 100644 index 0000000..83f1b29 --- /dev/null +++ b/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md @@ -0,0 +1,30 @@ +### Buildings: + +* For selecting intersecting buildings and combining them use, `I and Shift+J` +* Alternatively, the mapper can use the `Combine LA buildings` tool. +* In extrusion mode, do `control+command` to do redraw/reshape buildings for irregularly shaped buildings +* In extrusion mode, add four nodes in a segment and then `control+command`, and drag the middle segment for pyramidal structures in buildings +* Double tap A to draw complicated buildings and do not use the building plugin. +* For buildings with numerous extrusions: Draw a building> draw an extrusion> copy paste for all the extrusions> add intersecting nodes (shift+I)> join (shift+J) +* For buildings sharing the same wall, draw buildings using B and then select intersecting nodes and then join (J) and/or join way to node (N) +* Use terracer plugin for multiple same shaped buildings sharing the same wall (shortcut shift+T) +* Use resize tool `control+alt` to resize shapes e.g circles + +Videos: + +* [Drawing different types of buildings](https://www.youtube.com/watch?v=VNPfKh_ZI58&feature=youtu.be) +* [Tracing touching buildings in JOSM](https://www.youtube.com/watch?v=7GQtNnjIO0Q&feature=youtu.be) + +**Validation buildings** +* Run the validator +* Select all to highlight all the buildings to review + + +### Roads + +* Install and use Fast draw plugin (shortcut: shift+F) +* Press down arrow to simplify way, up arrow to add more complexity and then `enter` +* `Q` to simplify straight segments of roads +* Shortcuts to tag each type of road classification `Preferences > customize the icons in the toolbar > Presets > highways/ features that require shortcut > highways/streets > select the road you want to add as shortcut > right click on the shortcut and add a shortcut` + +Video: [Faster draw in JOSM](https://youtu.be/xqDd-Crk3o4) From 7a413029260e3f6199d68556621a0b2a61b7c1e4 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Tue, 9 May 2017 13:31:31 +0530 Subject: [PATCH 32/66] text edits and added title --- ...0-01-06-fast-building-and-road-mapping-tricks-and-tips.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md b/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md index 83f1b29..62e1a28 100644 --- a/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md +++ b/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md @@ -1,3 +1,8 @@ +--- +title: Fast mapping tips and tricks for buildings and roads +--- + + ### Buildings: * For selecting intersecting buildings and combining them use, `I and Shift+J` From f0642ff8f9dfc1850271a3636844a0ddb4951df3 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Tue, 9 May 2017 14:45:58 +0530 Subject: [PATCH 33/66] adding gaming mouse configuration document --- .../_posts/0000-01-01-getting-started.md | 45 +++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index ee1b19c..c46b493 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -85,3 +85,48 @@ By default JOSM is allocated with 247-1024 MB of memory depending on the operati ![increasing memory]({{site.baseurl}}/images/increasing-memory.png) To get rid of this error increase the default allocated memory for JOSM by following [these steps](https://gist.github.com/jothirnadh/00352fff58ce2628cc4f#supply-parameters). If you are not sure of fixing this, do contact someone from the data team. + +## How to configure tha gaming mouse? + +**Systems:** Linux and Mac + +**Equipment:** Razer Gaming mouse + +**General guidelines:** Increase mouse speed in `System Preferences> Mouse` for Mac + +**Example Feature** + +**Buildings** + +**Configure gaming mouse and keyboard** + +1. Install Razer Naga config software: https://www.razerzone.com/synapse/ +2. Create an account in razer ID: https://razer-id.razerzone.com/new +3. Build your profile using email id +4. Configure the mouse: + +**Common shortcuts essential to configure in your gaming mouse for buildings**: enter, extrude (keyboard:X), building tracing (keyboard:B), upload and download data to OSM (use the default keyboard shortcuts in your JOSM). + +**Good to have**: Join and merge shortcuts (J and M), selection of overlapping ways(I), Join overlapping areas (SHift+J), split objects (alt+X) + +**Note**: Pattern to follow in setting up your mouse: + +**Left hand(shortcuts in the keyboard)**: + * Upload + * Select + * Orthogonalize + * Rotate + +**Right hand(shortcuts in your mouse)**: + * enter + * X + * B + * Merge two nodes(M) + * Join node to way (N) + * Select intersecting ways (I) + * Join overlapping ways (shift+J) + + Configure any other shortcut according to the mapper choices. + +**Note**: For mapping other features like roads and to fix task, create separate configurations with the shortcuts required exclusively for those features. + From c0b96fccda5cbdb05a04863334aeb10e59a77306 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Tue, 9 May 2017 14:50:45 +0530 Subject: [PATCH 34/66] text edit --- getting-started/_posts/0000-01-01-getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index c46b493..9fd8eea 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -86,7 +86,7 @@ By default JOSM is allocated with 247-1024 MB of memory depending on the operati To get rid of this error increase the default allocated memory for JOSM by following [these steps](https://gist.github.com/jothirnadh/00352fff58ce2628cc4f#supply-parameters). If you are not sure of fixing this, do contact someone from the data team. -## How to configure tha gaming mouse? +## How to configure the gaming mouse? **Systems:** Linux and Mac From 068ea01e4b2aaa114193eefc09161f443e75e54a Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Tue, 9 May 2017 16:19:37 +0530 Subject: [PATCH 35/66] formatting edits --- getting-started/_posts/0000-01-01-getting-started.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index 9fd8eea..b10e3ed 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -112,18 +112,29 @@ To get rid of this error increase the default allocated memory for JOSM by follo **Note**: Pattern to follow in setting up your mouse: **Left hand(shortcuts in the keyboard)**: + * Upload + * Select + * Orthogonalize + * Rotate **Right hand(shortcuts in your mouse)**: + * enter + * X + * B + * Merge two nodes(M) + * Join node to way (N) + * Select intersecting ways (I) + * Join overlapping ways (shift+J) Configure any other shortcut according to the mapper choices. From 62f2b42de4f3a5b3dbff774cb379117db3dc6e6a Mon Sep 17 00:00:00 2001 From: maning Date: Tue, 9 May 2017 17:39:22 +0530 Subject: [PATCH 36/66] move tips and tricks to advance mapping --- .../josm/0000-01-06-advanced-mapping-guide.md | 96 +++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md diff --git a/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md b/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md new file mode 100644 index 0000000..da118c1 --- /dev/null +++ b/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md @@ -0,0 +1,96 @@ +--- +title: Advanced mapping guide +--- + +## Roads + +**Neighborhood grid** + +Residential buildings are usually located on a `residential` or `living_street` and has access to a road only on one side, and optionally on the backside via a `service alleyway`. A building with residential roads on multiple sides is a sign of mistaking building shadows for streets. The street grid in an an area will have repeating patterns that make it easy to guess how the roads are laid even if they are obscured by trees. +![untitled](https://cloud.githubusercontent.com/assets/126868/9808707/434854d4-587f-11e5-9132-c9e0824bd9e5.gif) + +* Install and use Fast draw plugin (shortcut: shift+F) +* Press down arrow to simplify way, up arrow to add more complexity and then `enter` +* `Q` to simplify straight segments of roads +* Shortcuts to tag each type of road classification `Preferences > customize the icons in the toolbar > Presets > highways/ features that require shortcut > highways/streets > select the road you want to add as shortcut > right click on the shortcut and add a shortcut` + +*Video* [Faster draw in JOSM](https://youtu.be/xqDd-Crk3o4) + +## Buildings + +**Parallel buildings** can be traced using the [building tools plugin](). Select a building and using the tool align subsequent buildings to the first one in one step. +![untitled](https://cloud.githubusercontent.com/assets/126868/9729213/73f5971e-562b-11e5-8c86-a1fa91eb969e.gif) +You can use the area extrude tool (x), to quickly add details to the outlines by creating new nodes (double click) and then dragging the faces. +![untitled](https://cloud.githubusercontent.com/assets/126868/9730603/419f04bc-5635-11e5-8ab8-bda7b1223892.gif) + +**Compound buildings** can be constructed using simple primitives and joining the overlapping areas (Shift+J) +![untitled](https://cloud.githubusercontent.com/assets/126868/9731646/c5816cd8-563b-11e5-84c4-497d9ac7536f.gif) + +* To combine overlapping buildings, select both building and click *Join overlapping Areas* (`Shift + J`). For muiltiple intersecting buildings, use `I and Shift+J`. Or, use the *Auto Tools > Combine LA buildings*. + +![gif](gif) + +* In *Extrusion mode* (`X`), do `Ctrl + Cmd` to redraw/reshape buildings for irregularly shaped buildings. + +![gif](gif) + +* In *Extrusion mode* (`X`), add four nodes in a segment, hold the `Ctrl + Cmd` key, and drag the middle segment to create pyramidal extrusions. + +![gif](gif) + +* Double tap `A` to draw buildings with irregular sized extrusions. Or create several smaller builsdings + +![gif](gif) + +* For buildings sharing the same wall, draw buildings (`B`) and, select intersecting node and click *Join Node to a Way* (`J`) or *Move Node unto Way* (`N`). + + +* To split a single building into two, select two nodes and select *Split Object* (`Alt + X`) + +![gif](gif) + +* Use *Terracer* plugin for multiple same shaped buildings sharing the same wall (`Shift + T`) + +![terrace](https://cloud.githubusercontent.com/assets/353700/25843868/63539886-34c6-11e7-9ac1-84419da6e512.gif) + +* For circular features, draw the diameter, select the way, and click *Tools > Create Circle* (`Shift + O`). + +* Use *Resize* tool (`Ctrl + Alt`) to re-size shape. + +Read also the blog post [Fast building tracing with JOSM](https://www.mapbox.com/blog/fast-building-tracing/) + +*Videos* + +* [Drawing different types of buildings](https://www.youtube.com/watch?v=VNPfKh_ZI58&feature=youtu.be) +* [Tracing touching buildings in JOSM](https://www.youtube.com/watch?v=7GQtNnjIO0Q&feature=youtu.be) + +### Others + +**Individual parking spaces** + +Draw a box enclosing the parking spaces and use the [terracer plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Terracer) to create a grid. Replace the default `building=yes` tag with `amenity=parking_space`. If you created adjacent grids, you would want to use the validator to automatically merge the overlapping nodes. +![untitled](https://cloud.githubusercontent.com/assets/126868/9601159/7ae06fd6-50bd-11e5-85ac-4fc3d00d7fbb.gif) + +**Tagging driveway through a building** + +![screen shot 2015-05-28 at 12 40 31 pm](https://cloud.githubusercontent.com/assets/10308123/7854419/f19e7898-0536-11e5-8e57-ffa455325588.png) + +Relevant tagging option for building would be + + `building=roof` and `layer=1` + +Highway road under the roof tagging options + + covered=yes + highway=footway + highway=residential + highway=service + +**Tagging stadium tracks** + +![image](https://cloud.githubusercontent.com/assets/369696/7835918/184508f2-0485-11e5-8378-b7b405c7c843.png) + +Relevant tagging option for Stadium would be + +- trace centerline of track as line (`leisure=track;area=no`) +- connect centerlines with surrounding foot paths or streets where possible From 0f56d7ce8e1abf498bf35f07576606204b9519a0 Mon Sep 17 00:00:00 2001 From: maning Date: Tue, 9 May 2017 17:48:54 +0530 Subject: [PATCH 37/66] formatting --- .../josm/0000-01-06-advanced-mapping-guide.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md b/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md index da118c1..c759ada 100644 --- a/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md +++ b/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md @@ -9,26 +9,28 @@ title: Advanced mapping guide Residential buildings are usually located on a `residential` or `living_street` and has access to a road only on one side, and optionally on the backside via a `service alleyway`. A building with residential roads on multiple sides is a sign of mistaking building shadows for streets. The street grid in an an area will have repeating patterns that make it easy to guess how the roads are laid even if they are obscured by trees. ![untitled](https://cloud.githubusercontent.com/assets/126868/9808707/434854d4-587f-11e5-9132-c9e0824bd9e5.gif) -* Install and use Fast draw plugin (shortcut: shift+F) -* Press down arrow to simplify way, up arrow to add more complexity and then `enter` -* `Q` to simplify straight segments of roads -* Shortcuts to tag each type of road classification `Preferences > customize the icons in the toolbar > Presets > highways/ features that require shortcut > highways/streets > select the road you want to add as shortcut > right click on the shortcut and add a shortcut` + +**Using Fast draw plugin** + +* Install and use **Fast draw** plugin (`shift + F`). +* Press down arrow to simplify way, up arrow to add more complexity and then `Enter`. +* `Q` to simplify straight segments of roads. +* Shortcuts to tag each type of road classification **Preferences > Customize the icons in the toolbar > Presets > highways/ features that require shortcut > highways/streets > select the road you want to add as shortcut > right click on the shortcut and add a shortcut**. *Video* [Faster draw in JOSM](https://youtu.be/xqDd-Crk3o4) ## Buildings -**Parallel buildings** can be traced using the [building tools plugin](). Select a building and using the tool align subsequent buildings to the first one in one step. +* **Parallel buildings** can be traced using the **building tools** plugin (`B`). Select a building and using the tool align subsequent buildings to the first one in one step. ![untitled](https://cloud.githubusercontent.com/assets/126868/9729213/73f5971e-562b-11e5-8c86-a1fa91eb969e.gif) -You can use the area extrude tool (x), to quickly add details to the outlines by creating new nodes (double click) and then dragging the faces. + +* You can use the **Area extrude** tool (`x`), to quickly add details to the outlines by creating new nodes (double click) and then dragging the faces. ![untitled](https://cloud.githubusercontent.com/assets/126868/9730603/419f04bc-5635-11e5-8ab8-bda7b1223892.gif) -**Compound buildings** can be constructed using simple primitives and joining the overlapping areas (Shift+J) -![untitled](https://cloud.githubusercontent.com/assets/126868/9731646/c5816cd8-563b-11e5-84c4-497d9ac7536f.gif) +* **Compound buildings** * To combine overlapping buildings, select both building and click *Join overlapping Areas* (`Shift + J`). For multiple intersecting buildings, use `I > Shift+J`. Or, use the *Auto Tools > Combine LA buildings*. -* To combine overlapping buildings, select both building and click *Join overlapping Areas* (`Shift + J`). For muiltiple intersecting buildings, use `I and Shift+J`. Or, use the *Auto Tools > Combine LA buildings*. +![untitled](https://cloud.githubusercontent.com/assets/126868/9731646/c5816cd8-563b-11e5-84c4-497d9ac7536f.gif) -![gif](gif) * In *Extrusion mode* (`X`), do `Ctrl + Cmd` to redraw/reshape buildings for irregularly shaped buildings. @@ -57,14 +59,12 @@ You can use the area extrude tool (x), to quickly add details to the outlines by * Use *Resize* tool (`Ctrl + Alt`) to re-size shape. -Read also the blog post [Fast building tracing with JOSM](https://www.mapbox.com/blog/fast-building-tracing/) - *Videos* * [Drawing different types of buildings](https://www.youtube.com/watch?v=VNPfKh_ZI58&feature=youtu.be) * [Tracing touching buildings in JOSM](https://www.youtube.com/watch?v=7GQtNnjIO0Q&feature=youtu.be) -### Others +## Others **Individual parking spaces** From 25ec8b59af6cd5a87b91fc3334c8b44f825203a1 Mon Sep 17 00:00:00 2001 From: maning Date: Tue, 9 May 2017 18:01:09 +0530 Subject: [PATCH 38/66] add intro to gaming mouse --- getting-started/_posts/0000-01-01-getting-started.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index b10e3ed..d357421 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -86,7 +86,9 @@ By default JOSM is allocated with 247-1024 MB of memory depending on the operati To get rid of this error increase the default allocated memory for JOSM by following [these steps](https://gist.github.com/jothirnadh/00352fff58ce2628cc4f#supply-parameters). If you are not sure of fixing this, do contact someone from the data team. -## How to configure the gaming mouse? +## Using a gaming mouse + +Using a gaming can increase your productivity by assigning shortcuts to common mapping tasks. This section outlines the basic configuration to use a gaming in JOSM. **Systems:** Linux and Mac @@ -121,7 +123,7 @@ To get rid of this error increase the default allocated memory for JOSM by follo * Rotate -**Right hand(shortcuts in your mouse)**: +**Right hand (shortcuts in your mouse)**: * enter @@ -140,4 +142,3 @@ To get rid of this error increase the default allocated memory for JOSM by follo Configure any other shortcut according to the mapper choices. **Note**: For mapping other features like roads and to fix task, create separate configurations with the shortcuts required exclusively for those features. - From b1883b3bf6dd03dfb903954f5fb720fe97cde14f Mon Sep 17 00:00:00 2001 From: maning Date: Tue, 9 May 2017 18:04:01 +0530 Subject: [PATCH 39/66] reformat subheadings --- .../_posts/0000-01-01-getting-started.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index d357421..a32b67e 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -29,18 +29,18 @@ Here is a good example: We are using the Java OpenStreetMap Editor (JOSM) for most tasks. Here's how to get set up. -### 1. Download and install JRE +**1. Download and install JRE** JOSM requires the Java Runtime Environment - JRE. [Download and install JRE]( http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html). -### 2. Download JOSM +**2. Download JOSM** Go to the [JOSM website](https://josm.openstreetmap.de/wiki/Download) to download the `tested` version. Place it in a common location for applications on your operating system. - OSX: `/Applications/` - Windows: `C:\Program Files\` -### 3. Open JOSM +**3. Open JOSM** Open the JOSM application you downloaded with a double click. @@ -52,13 +52,13 @@ Once JOSM is up and running it looks like this. Go find the **Preferences** dial ![josm-preferences]({{site.baseurl}}/images/josm-preferences.png) -### 4. Enable expert mode +**4. Enable expert mode** Open the **Preferences** dialog and enable **Expert mode**. ![check-expert-mode]({{site.baseurl}}/images/check-expert-mode.png) -### 5. Add user and password +**5. Add user and password** Now it's time to connect to OpenStreetMap. Add the user name and password of the account you just created on OpenStreetMap to JOSM. @@ -68,7 +68,7 @@ Now you should be able to retrieve data from OpenStreetMap by clicking on the bu ![download-data]({{site.baseurl}}/images/download-data.gif) -### 6. Enable Remote Control +**6. Enable Remote Control** Remote control allows you to launch JOSM directly from the map on OpenStreetMap.org. To enable Remote Control, check this box in the settings: @@ -78,7 +78,7 @@ Also check the **Download objects to a new layer** option. Now you should be abl ![retrieve-data]({{site.baseurl}}/images/retrieve-data.gif) -### 7. Increasing the allocated memory for JOSM +**7. Increasing the allocated memory for JOSM** By default JOSM is allocated with 247-1024 MB of memory depending on the operating system. When JOSM reaches its maximum handling limit it pops up an error highlighting `JOSM is out of memory` From 0571f574d6f580d3c84d6b610f4b6fced14ce1a4 Mon Sep 17 00:00:00 2001 From: Abhishek Saikia Date: Thu, 11 May 2017 19:34:06 +0530 Subject: [PATCH 40/66] added gifs --- .../josm/0000-01-06-advanced-mapping-guide.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md b/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md index c759ada..d8e7076 100644 --- a/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md +++ b/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md @@ -34,22 +34,25 @@ Residential buildings are usually located on a `residential` or `living_street` * In *Extrusion mode* (`X`), do `Ctrl + Cmd` to redraw/reshape buildings for irregularly shaped buildings. -![gif](gif) + +![x-ctrl cmd](https://cloud.githubusercontent.com/assets/13744156/25951924/cf3403da-367c-11e7-84d7-fa43187b38f4.gif) + * In *Extrusion mode* (`X`), add four nodes in a segment, hold the `Ctrl + Cmd` key, and drag the middle segment to create pyramidal extrusions. -![gif](gif) +![pyramidal buildings](https://cloud.githubusercontent.com/assets/13744156/25951031/190971be-367a-11e7-9de1-12bae8b9a056.gif) -* Double tap `A` to draw buildings with irregular sized extrusions. Or create several smaller builsdings +* Double tap `A` to draw buildings with irregular sized extrusions. Or create several smaller buildings -![gif](gif) +![double tap a](https://cloud.githubusercontent.com/assets/13744156/25951540/aab0855c-367b-11e7-814d-e874320fc4ab.gif) * For buildings sharing the same wall, draw buildings (`B`) and, select intersecting node and click *Join Node to a Way* (`J`) or *Move Node unto Way* (`N`). +![join j](https://cloud.githubusercontent.com/assets/13744156/25953311/90f74560-3680-11e7-8936-254744c3aeb3.gif) * To split a single building into two, select two nodes and select *Split Object* (`Alt + X`) -![gif](gif) +![alt x_split_buildings1](https://cloud.githubusercontent.com/assets/13744156/25953093/03458b0a-3680-11e7-91dc-b5e1bfc81e12.gif) * Use *Terracer* plugin for multiple same shaped buildings sharing the same wall (`Shift + T`) From 5ba8deba8ffd8c4b947a08feec49f26b5bb648fe Mon Sep 17 00:00:00 2001 From: maning Date: Sat, 20 May 2017 16:56:32 +0530 Subject: [PATCH 41/66] more edits --- ...ilding-and-road-mapping-tricks-and-tips.md | 35 ------------ .../0000-01-06-advanced-mapping-guide.md | 53 ------------------- 2 files changed, 88 deletions(-) delete mode 100644 becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md delete mode 100644 becoming-a-power-mapper/_posts/reference/0000-01-06-advanced-mapping-guide.md diff --git a/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md b/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md deleted file mode 100644 index 62e1a28..0000000 --- a/becoming-a-power-mapper/_posts/josm/0000-01-06-fast-building-and-road-mapping-tricks-and-tips.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Fast mapping tips and tricks for buildings and roads ---- - - -### Buildings: - -* For selecting intersecting buildings and combining them use, `I and Shift+J` -* Alternatively, the mapper can use the `Combine LA buildings` tool. -* In extrusion mode, do `control+command` to do redraw/reshape buildings for irregularly shaped buildings -* In extrusion mode, add four nodes in a segment and then `control+command`, and drag the middle segment for pyramidal structures in buildings -* Double tap A to draw complicated buildings and do not use the building plugin. -* For buildings with numerous extrusions: Draw a building> draw an extrusion> copy paste for all the extrusions> add intersecting nodes (shift+I)> join (shift+J) -* For buildings sharing the same wall, draw buildings using B and then select intersecting nodes and then join (J) and/or join way to node (N) -* Use terracer plugin for multiple same shaped buildings sharing the same wall (shortcut shift+T) -* Use resize tool `control+alt` to resize shapes e.g circles - -Videos: - -* [Drawing different types of buildings](https://www.youtube.com/watch?v=VNPfKh_ZI58&feature=youtu.be) -* [Tracing touching buildings in JOSM](https://www.youtube.com/watch?v=7GQtNnjIO0Q&feature=youtu.be) - -**Validation buildings** -* Run the validator -* Select all to highlight all the buildings to review - - -### Roads - -* Install and use Fast draw plugin (shortcut: shift+F) -* Press down arrow to simplify way, up arrow to add more complexity and then `enter` -* `Q` to simplify straight segments of roads -* Shortcuts to tag each type of road classification `Preferences > customize the icons in the toolbar > Presets > highways/ features that require shortcut > highways/streets > select the road you want to add as shortcut > right click on the shortcut and add a shortcut` - -Video: [Faster draw in JOSM](https://youtu.be/xqDd-Crk3o4) diff --git a/becoming-a-power-mapper/_posts/reference/0000-01-06-advanced-mapping-guide.md b/becoming-a-power-mapper/_posts/reference/0000-01-06-advanced-mapping-guide.md deleted file mode 100644 index 202b7da..0000000 --- a/becoming-a-power-mapper/_posts/reference/0000-01-06-advanced-mapping-guide.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Advanced mapping guide ---- - -## Roads - -**Neighborhood grid** - -Residential buildings are usually located on a `residential` or `living_street` and has access to a road only on one side, and optionally on the backside via a `service alleyway`. A building with residential roads on multiple sides is a sign of mistaking building shadows for streets. The street grid in an an area will have repeating patterns that make it easy to guess how the roads are laid even if they are obscured by trees. -![untitled](https://cloud.githubusercontent.com/assets/126868/9808707/434854d4-587f-11e5-9132-c9e0824bd9e5.gif) - -## Buildings - -**Parallel buildings** can be traced using the [building tools plugin](). Select a building and using the tool align subsequent buildings to the first one in one step. -![untitled](https://cloud.githubusercontent.com/assets/126868/9729213/73f5971e-562b-11e5-8c86-a1fa91eb969e.gif) -You can use the area extrude tool (x), to quickly add details to the outlines by creating new nodes (double click) and then dragging the faces. -![untitled](https://cloud.githubusercontent.com/assets/126868/9730603/419f04bc-5635-11e5-8ab8-bda7b1223892.gif) - -**Compound buildings** can be constructed using simple primitives and joining the overlapping areas (Shift+J) -![untitled](https://cloud.githubusercontent.com/assets/126868/9731646/c5816cd8-563b-11e5-84c4-497d9ac7536f.gif) - -Read also the blog post [Fast building tracing with JOSM](https://www.mapbox.com/blog/fast-building-tracing/) - -## Parking - -**Individual parking spaces** - -Draw a box enclosing the parking spaces and use the [terracer plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Terracer) to create a grid. Replace the default `building=yes` tag with `amenity=parking_space`. If you created adjacent grids, you would want to use the validator to automatically merge the overlapping nodes. -![untitled](https://cloud.githubusercontent.com/assets/126868/9601159/7ae06fd6-50bd-11e5-85ac-4fc3d00d7fbb.gif) - -## Tagging driveway through a building - -![screen shot 2015-05-28 at 12 40 31 pm](https://cloud.githubusercontent.com/assets/10308123/7854419/f19e7898-0536-11e5-8e57-ffa455325588.png) - -Relevant tagging option for building would be - - `building=roof` and `layer=1` - -Highway road under the roof tagging options - - covered=yes - highway=footway - highway=residential - highway=service - -## Tagging stadium tracks - -![image](https://cloud.githubusercontent.com/assets/369696/7835918/184508f2-0485-11e5-8378-b7b405c7c843.png) - -Relevant tagging option for Stadium would be - -- trace centerline of track as line (`leisure=track;area=no`) -- connect centerlines with surrounding foot paths or streets where possible From d1f6815f3973552cbf347f160ca00cd37d9b4ff5 Mon Sep 17 00:00:00 2001 From: maning Date: Sat, 20 May 2017 18:02:27 +0530 Subject: [PATCH 42/66] copy edits --- .../josm/0000-01-06-advanced-mapping-guide.md | 2 +- .../_posts/0000-01-01-getting-started.md | 15 +++++++-------- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md b/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md index d8e7076..f04d3f9 100644 --- a/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md +++ b/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md @@ -27,7 +27,7 @@ Residential buildings are usually located on a `residential` or `living_street` * You can use the **Area extrude** tool (`x`), to quickly add details to the outlines by creating new nodes (double click) and then dragging the faces. ![untitled](https://cloud.githubusercontent.com/assets/126868/9730603/419f04bc-5635-11e5-8ab8-bda7b1223892.gif) -* **Compound buildings** * To combine overlapping buildings, select both building and click *Join overlapping Areas* (`Shift + J`). For multiple intersecting buildings, use `I > Shift+J`. Or, use the *Auto Tools > Combine LA buildings*. +* **Compound buildings** To combine overlapping buildings, select both building and click *Join overlapping Areas* (`Shift + J`). For several intersecting buildings, use `I > Shift+J`. Or, use the *Auto Tools > Combine LA buildings*. ![untitled](https://cloud.githubusercontent.com/assets/126868/9731646/c5816cd8-563b-11e5-84c4-497d9ac7536f.gif) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index a32b67e..a579b93 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -24,7 +24,6 @@ Here is a good example: ![osm-profile-description-example]({{site.baseurl}}/images/osm-profile-description-example.png) - ## Installing JOSM We are using the Java OpenStreetMap Editor (JOSM) for most tasks. Here's how to get set up. @@ -60,7 +59,7 @@ Open the **Preferences** dialog and enable **Expert mode**. **5. Add user and password** -Now it's time to connect to OpenStreetMap. Add the user name and password of the account you just created on OpenStreetMap to JOSM. +Now it's time to connect to OpenStreetMap. Add the user name and password of the account you created on OpenStreetMap to JOSM. ![set-osm-username-and-password]({{site.baseurl}}/images/set-osm-username-and-password.png) @@ -104,16 +103,16 @@ Using a gaming can increase your productivity by assigning shortcuts to common m 1. Install Razer Naga config software: https://www.razerzone.com/synapse/ 2. Create an account in razer ID: https://razer-id.razerzone.com/new -3. Build your profile using email id +3. Build your profile using your email id 4. Configure the mouse: -**Common shortcuts essential to configure in your gaming mouse for buildings**: enter, extrude (keyboard:X), building tracing (keyboard:B), upload and download data to OSM (use the default keyboard shortcuts in your JOSM). +**Common shortcuts essential to configure in your gaming mouse for buildings**: Enter, Extrude (`X`), building tracing (`B`), upload and download data to OSM (use the default keyboard shortcuts in your JOSM). -**Good to have**: Join and merge shortcuts (J and M), selection of overlapping ways(I), Join overlapping areas (SHift+J), split objects (alt+X) +**Good to have**: Join and merge nodes/ways (`J` and `M`), selec overlapping ways (`I`), join overlapping areas (`Shift + J`), Split objects (`Alt + X`) **Note**: Pattern to follow in setting up your mouse: -**Left hand(shortcuts in the keyboard)**: +**Left hand (shortcuts in the keyboard)**: * Upload @@ -125,7 +124,7 @@ Using a gaming can increase your productivity by assigning shortcuts to common m **Right hand (shortcuts in your mouse)**: - * enter + * Enter * X @@ -141,4 +140,4 @@ Using a gaming can increase your productivity by assigning shortcuts to common m Configure any other shortcut according to the mapper choices. -**Note**: For mapping other features like roads and to fix task, create separate configurations with the shortcuts required exclusively for those features. +**Note**: For mapping other features like roads and to fix task, create separate configurations with the shortcuts required only for those features. From 05ecd4007245ab34cbf060d436d120ee7141cfab Mon Sep 17 00:00:00 2001 From: maning Date: Sat, 20 May 2017 18:03:13 +0530 Subject: [PATCH 43/66] copy edits --- getting-started/_posts/0000-01-01-getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index a579b93..293dd57 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -108,7 +108,7 @@ Using a gaming can increase your productivity by assigning shortcuts to common m **Common shortcuts essential to configure in your gaming mouse for buildings**: Enter, Extrude (`X`), building tracing (`B`), upload and download data to OSM (use the default keyboard shortcuts in your JOSM). -**Good to have**: Join and merge nodes/ways (`J` and `M`), selec overlapping ways (`I`), join overlapping areas (`Shift + J`), Split objects (`Alt + X`) +**Good to have**: Join and merge nodes/ways (`J` and `M`), select overlapping ways (`I`), join overlapping areas (`Shift + J`), Split objects (`Alt + X`) **Note**: Pattern to follow in setting up your mouse: From 14551e4013833ad325a438e056829958e74a48d4 Mon Sep 17 00:00:00 2001 From: nyampire Date: Tue, 23 May 2017 18:04:16 +0900 Subject: [PATCH 44/66] create jp dir --- .../_posts/josm/0000-01-02-josm-shortcuts.md | 137 ++++++++++ ...editing-saving-and-loading-josm-session.md | 28 ++ .../josm/0000-01-04-reverting-changes.md | 6 + .../0000-01-05-advanced-josm-customization.md | 12 + .../josm/0000-01-06-advanced-mapping-guide.md | 99 +++++++ .../0000-01-01-reviewing-your-edits.md | 49 ++++ ...0000-01-07-fixing-common-mapping-issues.md | 20 ++ .../0000-01-08-useful-overpass-queries.md | 16 ++ .../0000-01-09-useful-osm-resources.md | 69 +++++ jp/becoming-a-power-mapper/index.md | 17 ++ .../_posts/0000-01-01-getting-started.md | 143 ++++++++++ jp/getting-started/index.md | 8 + .../0000-01-01-mapping-common-features.md | 258 ++++++++++++++++++ jp/mapping-common-features/index.md | 8 + .../_posts/0000-01-01-introduction.md | 86 ++++++ ...01-02-modeling-roads-for-map-navigation.md | 86 ++++++ .../0000-01-03-road-features-mapping-guide.md | 217 +++++++++++++++ .../0000-01-04-adding-turn-restrictions.md | 251 +++++++++++++++++ ...01-05-adding-exit-and-destination-signs.md | 135 +++++++++ .../_posts/0000-01-06-adding-turn-lanes.md | 247 +++++++++++++++++ .../0000-01-07-resources-and-references.md | 49 ++++ jp/mapping-for-navigation/index.md | 10 + .../_posts/0000-01-01-mapping-with-josm.md | 210 ++++++++++++++ jp/mapping-with-josm/index.md | 8 + .../_posts/0000-01-01-osm-data-model.md | 65 +++++ jp/osm-data-model/index.md | 8 + .../_posts/0000-01-01-validating-osm.md | 247 +++++++++++++++++ jp/validating-osm/index.md | 8 + 28 files changed, 2497 insertions(+) create mode 100644 jp/becoming-a-power-mapper/_posts/josm/0000-01-02-josm-shortcuts.md create mode 100644 jp/becoming-a-power-mapper/_posts/josm/0000-01-03-editing-saving-and-loading-josm-session.md create mode 100644 jp/becoming-a-power-mapper/_posts/josm/0000-01-04-reverting-changes.md create mode 100644 jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md create mode 100644 jp/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md create mode 100644 jp/becoming-a-power-mapper/_posts/mapping/0000-01-01-reviewing-your-edits.md create mode 100644 jp/becoming-a-power-mapper/_posts/reference/0000-01-07-fixing-common-mapping-issues.md create mode 100644 jp/becoming-a-power-mapper/_posts/reference/0000-01-08-useful-overpass-queries.md create mode 100644 jp/becoming-a-power-mapper/_posts/reference/0000-01-09-useful-osm-resources.md create mode 100644 jp/becoming-a-power-mapper/index.md create mode 100644 jp/getting-started/_posts/0000-01-01-getting-started.md create mode 100644 jp/getting-started/index.md create mode 100644 jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md create mode 100644 jp/mapping-common-features/index.md create mode 100644 jp/mapping-for-navigation/_posts/0000-01-01-introduction.md create mode 100644 jp/mapping-for-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md create mode 100644 jp/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md create mode 100644 jp/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md create mode 100644 jp/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md create mode 100644 jp/mapping-for-navigation/_posts/0000-01-06-adding-turn-lanes.md create mode 100644 jp/mapping-for-navigation/_posts/0000-01-07-resources-and-references.md create mode 100644 jp/mapping-for-navigation/index.md create mode 100644 jp/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md create mode 100644 jp/mapping-with-josm/index.md create mode 100644 jp/osm-data-model/_posts/0000-01-01-osm-data-model.md create mode 100644 jp/osm-data-model/index.md create mode 100644 jp/validating-osm/_posts/0000-01-01-validating-osm.md create mode 100644 jp/validating-osm/index.md diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-02-josm-shortcuts.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-02-josm-shortcuts.md new file mode 100644 index 0000000..499044b --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-02-josm-shortcuts.md @@ -0,0 +1,137 @@ +--- +title: JOSM shortcuts +--- + +As you draw using the JOSM editor, or correct map errors on to-fix, keyboard shortcuts can save help you save a great deal of time and increase the quality of your mapping [strokes replaced] if used correctly. Here we'll cover keyboard shortcuts on JOSM - default settings, how you can customize these to suit your preferences, and shortcuts most popular with the data team. + +![](https://scontent-frt3-1.xx.fbcdn.net/hphotos-xfl1/t31.0-8/920735_554891274669057_2113729309314231818_o.jpg) +*Use the [JOSM cheatsheet](http://www.openstreetmap.org/user/baditaflorin/diary/37606) by user:baditaflorin* + + +## Basic Shortcuts [Default] + +By default, the JOSM editor comes pre-loaded with approximately 100+ shortcuts which cover everything from downloading/uploading map data from the OpenStreetMap server, adding/editing/deleting tags, validating results, and working with nodes, ways, and polygons. See the [Common Keyboard Shortcuts](https://josm.openstreetmap.de/wiki/Presets/CommonKeyboardShortcuts) on the JOSM wiki for more details. + +![image](https://cloud.githubusercontent.com/assets/8562256/7113237/5beb62a8-e1ef-11e4-832d-0fa5e827503e.png) + +_Under **Tools** on the menu bar, you can see some of the basic default shortcuts on JOSM_ + +The default shortcuts on JOSM are a great way to get started, but once you are familiar and start speed mapping, you may want to consider customizing the JOSM shortcuts to fit your mapping preferences. For example, you can customize shortcuts to allow you to map quickly without having to take your right hand off the mouse. + +Action | Keyboard Shortcut +---- | ---- +Uploading the edit | ` +Downloading data | Q +Deleting data | D + +To access the Shortcuts Menu, go to **Preferences** on the JOSM menu bar. Within **Preferences**, click **Options** on the left (seventh button). + +![configure_image_shortcuts](https://cloud.githubusercontent.com/assets/353700/11626533/8cbfdb90-9d09-11e5-8641-8a1260e232a8.png) + + +Here is a comprehensive categorized list of shortcuts everyone should be familiar with. + +### JOSM Shortcuts + +#### DATA + +ACTION | DESCRIPTION | Mac | Win/Linux +---- | ---- | ---- | ---- +OPEN | open a file | `Cmd+O` | +SAVE | save current data | `Cmd+S` | +DATA DOWNLOAD | download map data from OSM server | `Cmd+Shift+Down` | +DATA UPLOAD | upload all changes in the active data layer to the OSM server | `Cmd+Shift+Up` | + +----- + +### Basic map editing + +ACTION | DESCRIPTION | Mac | Win/Linux +---- | ---- | ---- | ---- +SELECTION | select, move, scale, and rotate objects | `S`| `S` +NODES | draw nodes | `A`| `A` +BUILDINGS | draw building | `B`| `B` +DRAW | fast drawing mode | `Shift + F` | +ZOOM | zoom and move map | `Z`| `Z` +DELETE | delete nodes or ways | `Cmd + D` +SPLIT WAY | split a way at a selected node | `P`| `P` +COMBINE WAY | combine several ways into one | `C`| `C` +REVERSE WAY | reverse the direction of all selected ways | `R`| `R` +SIMPLIFY WAY | delete unnecessary nodes from a way | `Shift+Y` +ALIGN NODES IN CIRCLE | move the selected nodes into a circle | `O`| `O` +ALIGN NODES IN LINE | move the selected nodes into a line | `L`| `L` +MIRROR | mirror selected nodes and ways | `Shift+M` | +FOLLOW LINE | continues drawing a line that shares nodes with another line | `F`| `F` +ADD NODE | add a node by adding latitude/longitude or easting/northing | `Shift+D` | +CREATE CIRCLE | create a circle from three selected nodes | `Shift+O` | +MERGE NODES | merge nodes into the oldest one | `M`| `M` +JOIN NODE TO WAY | include a node into the nearest way segment | `J`| `J` +MOVE NODE INTO WAY | move node into the nearest way segments and include it | `N`| `N` +DISCONNECT NODE FROM WAY | disconnect nodes from a way they currently belong to | `Alt+J` | +UNGLUE WAYS | duplicate nodes that are used by multiple ways | `G`| `G` +JOIN OVERLAPPING AREAS | join areas that overlap each other | `Shift+J` | +CREATE MULTIPOLYGON | create a multipolygon | `Cmd + B` | +UPDATE MULTIPOLYGON | update a multipolygon | `Cmd+Shift+B` | + +---- + +## Accuracy & precision + +ACTION | DESCRIPTION | SHORTCUT +---- | ---- | ---- +PARALLEL WAYS | make parallel copies of ways | `Shift+P` +WAY ACCURACY | improve the accuracy of ways | `W` +ORTHOGONALIZE SHAPE | move nodes so all angles are 90 or 180 degrees | `Q` +DISTRIBUTE NODES | distribute the selected nodes to equal distances along a line | `Shift+B` +EXTRUSION | create areas | `X` +BUILDING SIZE | set building size | `Cmd+Alt+B` + +---- + +## Presets + +ACTION | DESCRIPTION | SHORTCUT +---- | ---- | ---- +SEARCH PRESETS | show preset search dialogue | `F3` + + +## User interface + +ACTION | DESCRIPTION | SHORTCUT +---- | ---- | ---- +PREFERENCES | open a preferences dialogue for global settings | `Cmd + ,` +LAYERS WINDOW | open a list of all loaded layers | `Alt+Shift+L` +TAGS/MEMBERSHP WINDOW | open tags window for selected objects | `Alt+Shift+P` +SELECTION WINDOW | open a selection list window | `Alt+Shift+T` +RELATIONS WINDOW | open a list of all relations | `Alt+Shift+R` +WIREFRAME VIEW | enable/disable rendering the map as wireframe only | `Cmd+W` + +---- + +## Imagery + +ACTION | DESCRIPTION | SHORTCUT +---- | ---- | ---- +IMAGERY OFFSET | download offset for current imagery from a server | `Cmd+Alt+I` + +---- + +## Conflicts resolution + +ACTION | DESCRIPTION | SHORTCUT +---- | ---- | ---- +CHECK AUTHOR | open list of people working on a selected object | `Alt+Shift+A` +RESOLVE CONFLICT | resolve a conflict | `Alt+Shift+C` + +---- + +## Review/validation + +ACTION | DESCRIPTION | SHORTCUT +---- | ---- | ---- +CHANGESET MANAGER | toggle visibility of changeset manager window | `Cmd+Alt+C` +VALIDATION WINDOW | open validation window | `Alt+Shift+V` +VALIDATE | performs data validation | `Shift+V` +FILTERS | filter objects and hide/disable them | `Alt+Shift+F` +HISTORY JOSM | check history of an object | `Ctrl+H` +HISTORY WEB | check the history of object on web | `Cmd+Shift+H` diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-03-editing-saving-and-loading-josm-session.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-03-editing-saving-and-loading-josm-session.md new file mode 100644 index 0000000..5f0e5f5 --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-03-editing-saving-and-loading-josm-session.md @@ -0,0 +1,28 @@ +--- +title: Saving and loading a JOSM session +--- + +It is possible to save a JOSM session similar most GIS software (in QGIS we call it a project file). The JOSM session saves your current map view, OSM data and loaded layers such as imagery. + +The JOSM session is available in **File** menu. You need to be in **Expert mode** to access this feature. +To activate Expert mode, go to JOSM Preferences, activate **Expert mode** by clicking the checkbox. + +## Saving a JOSM session + +Load any of your preferred layers in JOSM. +Save the JOSM session file clicking, **File > Session > Save session as ...** +Select any layers you want loaded when you start a new JOSM session. + +![josm_session_save2]({{site.baseurl}}/images/saving-a-josm-session.gif) + +## Loading a JOSM session + +To load a previously saved JOSM session, click **File > Session > Load session**. +Select the `.jos` you saved. + +![josm_session_load2]({{site.baseurl}}/images/loading-a-josm-session.gif) + +NOTE: Do not save any OSM data within your `.jos` file. Always load new data to avoid data conflicts. + +Examples of session files we use in the [/mapping repo](https://github.com/mapbox/mapping/tree/master/JOSM/sessions). + diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-04-reverting-changes.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-04-reverting-changes.md new file mode 100644 index 0000000..c272d4c --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-04-reverting-changes.md @@ -0,0 +1,6 @@ +--- +title: Reverting changes +--- + +* https://help.openstreetmap.org/questions/731/how-can-i-revert-a-changeset +* http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md new file mode 100644 index 0000000..0905d04 --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md @@ -0,0 +1,12 @@ +--- +title: Advanced JOSM customization +--- + + +Hidden settings in JOSM can be configured directly from the advanced preferences panel. This also gives you access to export and import your configuration profiles. + +The panel is hidden by default and is shown as the last option when `Expert mode` is enabled. + +![screenshot 2015-10-15 14 42 52](https://cloud.githubusercontent.com/assets/126868/10509569/890e64b8-734b-11e5-988f-26596f9d42d9.png) + +**Note** JOSM will need to be restarted for any changes to take effect. \ No newline at end of file diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md new file mode 100644 index 0000000..f04d3f9 --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md @@ -0,0 +1,99 @@ +--- +title: Advanced mapping guide +--- + +## Roads + +**Neighborhood grid** + +Residential buildings are usually located on a `residential` or `living_street` and has access to a road only on one side, and optionally on the backside via a `service alleyway`. A building with residential roads on multiple sides is a sign of mistaking building shadows for streets. The street grid in an an area will have repeating patterns that make it easy to guess how the roads are laid even if they are obscured by trees. +![untitled](https://cloud.githubusercontent.com/assets/126868/9808707/434854d4-587f-11e5-9132-c9e0824bd9e5.gif) + + +**Using Fast draw plugin** + +* Install and use **Fast draw** plugin (`shift + F`). +* Press down arrow to simplify way, up arrow to add more complexity and then `Enter`. +* `Q` to simplify straight segments of roads. +* Shortcuts to tag each type of road classification **Preferences > Customize the icons in the toolbar > Presets > highways/ features that require shortcut > highways/streets > select the road you want to add as shortcut > right click on the shortcut and add a shortcut**. + +*Video* [Faster draw in JOSM](https://youtu.be/xqDd-Crk3o4) + +## Buildings + +* **Parallel buildings** can be traced using the **building tools** plugin (`B`). Select a building and using the tool align subsequent buildings to the first one in one step. +![untitled](https://cloud.githubusercontent.com/assets/126868/9729213/73f5971e-562b-11e5-8c86-a1fa91eb969e.gif) + +* You can use the **Area extrude** tool (`x`), to quickly add details to the outlines by creating new nodes (double click) and then dragging the faces. +![untitled](https://cloud.githubusercontent.com/assets/126868/9730603/419f04bc-5635-11e5-8ab8-bda7b1223892.gif) + +* **Compound buildings** To combine overlapping buildings, select both building and click *Join overlapping Areas* (`Shift + J`). For several intersecting buildings, use `I > Shift+J`. Or, use the *Auto Tools > Combine LA buildings*. + +![untitled](https://cloud.githubusercontent.com/assets/126868/9731646/c5816cd8-563b-11e5-84c4-497d9ac7536f.gif) + + +* In *Extrusion mode* (`X`), do `Ctrl + Cmd` to redraw/reshape buildings for irregularly shaped buildings. + + +![x-ctrl cmd](https://cloud.githubusercontent.com/assets/13744156/25951924/cf3403da-367c-11e7-84d7-fa43187b38f4.gif) + + +* In *Extrusion mode* (`X`), add four nodes in a segment, hold the `Ctrl + Cmd` key, and drag the middle segment to create pyramidal extrusions. + +![pyramidal buildings](https://cloud.githubusercontent.com/assets/13744156/25951031/190971be-367a-11e7-9de1-12bae8b9a056.gif) + +* Double tap `A` to draw buildings with irregular sized extrusions. Or create several smaller buildings + +![double tap a](https://cloud.githubusercontent.com/assets/13744156/25951540/aab0855c-367b-11e7-814d-e874320fc4ab.gif) + +* For buildings sharing the same wall, draw buildings (`B`) and, select intersecting node and click *Join Node to a Way* (`J`) or *Move Node unto Way* (`N`). + +![join j](https://cloud.githubusercontent.com/assets/13744156/25953311/90f74560-3680-11e7-8936-254744c3aeb3.gif) + +* To split a single building into two, select two nodes and select *Split Object* (`Alt + X`) + +![alt x_split_buildings1](https://cloud.githubusercontent.com/assets/13744156/25953093/03458b0a-3680-11e7-91dc-b5e1bfc81e12.gif) + +* Use *Terracer* plugin for multiple same shaped buildings sharing the same wall (`Shift + T`) + +![terrace](https://cloud.githubusercontent.com/assets/353700/25843868/63539886-34c6-11e7-9ac1-84419da6e512.gif) + +* For circular features, draw the diameter, select the way, and click *Tools > Create Circle* (`Shift + O`). + +* Use *Resize* tool (`Ctrl + Alt`) to re-size shape. + +*Videos* + +* [Drawing different types of buildings](https://www.youtube.com/watch?v=VNPfKh_ZI58&feature=youtu.be) +* [Tracing touching buildings in JOSM](https://www.youtube.com/watch?v=7GQtNnjIO0Q&feature=youtu.be) + +## Others + +**Individual parking spaces** + +Draw a box enclosing the parking spaces and use the [terracer plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Terracer) to create a grid. Replace the default `building=yes` tag with `amenity=parking_space`. If you created adjacent grids, you would want to use the validator to automatically merge the overlapping nodes. +![untitled](https://cloud.githubusercontent.com/assets/126868/9601159/7ae06fd6-50bd-11e5-85ac-4fc3d00d7fbb.gif) + +**Tagging driveway through a building** + +![screen shot 2015-05-28 at 12 40 31 pm](https://cloud.githubusercontent.com/assets/10308123/7854419/f19e7898-0536-11e5-8e57-ffa455325588.png) + +Relevant tagging option for building would be + + `building=roof` and `layer=1` + +Highway road under the roof tagging options + + covered=yes + highway=footway + highway=residential + highway=service + +**Tagging stadium tracks** + +![image](https://cloud.githubusercontent.com/assets/369696/7835918/184508f2-0485-11e5-8378-b7b405c7c843.png) + +Relevant tagging option for Stadium would be + +- trace centerline of track as line (`leisure=track;area=no`) +- connect centerlines with surrounding foot paths or streets where possible diff --git a/jp/becoming-a-power-mapper/_posts/mapping/0000-01-01-reviewing-your-edits.md b/jp/becoming-a-power-mapper/_posts/mapping/0000-01-01-reviewing-your-edits.md new file mode 100644 index 0000000..72d7b0e --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/mapping/0000-01-01-reviewing-your-edits.md @@ -0,0 +1,49 @@ +--- +title: Reviewing your edits +--- + +## JOSM Validator + +The easiest way to [fix common mapping issues]({{site.baseurl}}/becoming-a-power-mapper/fixing-common-mapping-issues/) is to use the inbuilt validator in JOSM. All edits made in a session are automatically validated and a warning will be displayed before upload if any suspicious data is found. + +![screenshot 2015-12-11 14 30 37](https://cloud.githubusercontent.com/assets/126868/11739757/c77832c0-a013-11e5-8568-c6dd6624e127.png) + +### Usage + +* Select the data you want validated and press `Shift+V` or hit `Validate` from the Validator panel. If no data is selected, the Validator will run on all the data in the active layer. +* A *Validation errors* layer will be added to your *Layers* to highlight features with errors. +* The *Validation Results* panel will display all the detected errors. Select any of the detected errors to fix. You can right click an entry and zoom to the location if needed. + +![using validator]({{site.baseurl}}/images/validator_using.gif) + +The **Validation Results** have several buttons activated to navigate and fix errors: +* **Select** – Select the objects of the selected error. +* **Lookup** – Looks up the selected primitives in the error list. +* **Validation** – Start validation process for current selection or all objects (when nothing selected). +* **Fix** – Fix an error (only when automatically fixable). +* **Ignore** – Ignore an error or a group of errors in future tests. + +### Customizing error detection + +By default the validator checks against a wide range of [data issues](https://josm.openstreetmap.de/wiki/Help/Preferences/Validator), many of which may not be important or may contain false positives. You can customize the settings from *Preferences > Data Validator* + +![validator settings]({{site.baseurl}}/images/validator_settings.gif) + + +For more details check the [OSM Wiki](http://wiki.openstreetmap.org/wiki/JOSM/Validator) and the [LearnOSM Guide](http://learnosm.org/en/coordination/review/#data-validation) + +## Overpass Turbo + +You can quickly query and visualize OSM data live using **[Overpass Turbo](http://overpass-turbo.eu/s/ddp)**. + +![screenshot 2015-12-11 16 14 31](https://cloud.githubusercontent.com/assets/126868/11741952/4795d602-a022-11e5-8043-0e7014baebbc.png) + +### Usage + +- [Browse the map](http://overpass-turbo.eu) to the area of interest or alternatively set a bounding box using the map tool on the left. +- Write an [Overpass Query](http://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL) in the query editor or use the *Wizard* for simple tag queries like `highway=motorway or highway=trunk` +- Optionally add a [MapCSS](http://wiki.openstreetmap.org/wiki/Overpass_turbo/MapCSS) style to visualize the results +- Hit `Run` to execute the query on the OSM data and display the results. +*Tip: By default small ways are rendered as circles. To fix this check the `Don't display small features as POIs` option from `Settings > Map`* + +For more details check the [OSM Wiki](http://wiki.openstreetmap.org/wiki/Overpass_turbo), [Learn Overpass](http://osmlab.github.io/learnoverpass//en/) or some common [example queries](https://gist.github.com/ramyaragupathy/ffb3f225ccba4545398f). diff --git a/jp/becoming-a-power-mapper/_posts/reference/0000-01-07-fixing-common-mapping-issues.md b/jp/becoming-a-power-mapper/_posts/reference/0000-01-07-fixing-common-mapping-issues.md new file mode 100644 index 0000000..0d824e1 --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/reference/0000-01-07-fixing-common-mapping-issues.md @@ -0,0 +1,20 @@ +--- +title: Fixing common mapping issues +--- + +Identifying common mistakes made by beginner mappers and knowing how to fix them is important to improve the quality of the map. If you spot something which needs fixing, send a friendly message on the users' changeset on what was wrong and how it could be fixed. You can use this guide as a reference. + +| Issue | Whats wrong | How to fix it | Tips | +| ----- |------------ | ------------- | ---- | +| **Overlapping ways** | [![](https://cloud.githubusercontent.com/assets/11504548/7966913/a0edc5a6-09ec-11e5-9583-fd510c0ab6fd.png)](https://cloud.githubusercontent.com/assets/11504548/7966913/a0edc5a6-09ec-11e5-9583-fd510c0ab6fd.png) A linear way goes over itself or another way with the exact same tags (note the arrows on the selected way) | Delete the overlapping way, make sure there are no gaps or missing pieces left behind. | You can use the [JOSM validator](http://wiki.openstreetmap.org/wiki/JOSM/Validator) to detect these issues | +| **Add `layer=1` for bridges**|[![bridgefilter](https://cloud.githubusercontent.com/assets/6770741/11365662/e2c2b5bc-92cd-11e5-830d-2a165b896181.gif)](https://cloud.githubusercontent.com/assets/6770741/11365662/e2c2b5bc-92cd-11e5-830d-2a165b896181.gif)If there is a lot bridges without `layer=1` tag, you can filter bridges easily.|Go to every bridge and look into imagery for it's layers (layer=1, layer=2 etc) and add |OSM Wiki on [bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)| +|**Overlapping buildings**|[![screen shot 2015-11-24 at 5 50 20 pm](https://cloud.githubusercontent.com/assets/6770741/11366588/222087f6-92d4-11e5-8a45-2189e3b2e961.png)](https://cloud.githubusercontent.com/assets/6770741/11366588/222087f6-92d4-11e5-8a45-2189e3b2e961.png) Buildings which are overlapping, should be separated | Run Validator and separate manually, use 'Q' to orthogonalise it| Check OSM wiki on [building](http://wiki.openstreetmap.org/wiki/Buildings) for more information.| +|**Add junction=roundabout**|[![junction](https://cloud.githubusercontent.com/assets/6770741/11375904/cd5a8336-9303-11e5-8cb3-2ea99a610142.gif)](https://cloud.githubusercontent.com/assets/6770741/11375904/cd5a8336-9303-11e5-8cb3-2ea99a610142.gif)|Add `junction=roundabout` for circle| OSM Wiki for [roundabout](http://wiki.openstreetmap.org/wiki/Tag:junction%3Droundabout)| +|**Split bridge at exact location**|[![image](https://cloud.githubusercontent.com/assets/1152236/7830938/6a645932-046f-11e5-8f6b-560054ac584c.png)](https://cloud.githubusercontent.com/assets/1152236/7830938/6a645932-046f-11e5-8f6b-560054ac584c.png) Should split bridge exactly to match imagery| Switch between Bing/Mapbox to clear confusion| OSM wiki on [bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)| +|**Untagged Ways**|[![untagged](https://cloud.githubusercontent.com/assets/6770741/11389187/c0354348-9363-11e5-9441-5c9833d8b4b2.gif)](https://cloud.githubusercontent.com/assets/6770741/11389187/c0354348-9363-11e5-9441-5c9833d8b4b2.gif)| Run `shift+v` and select the ways and add appropriate highway tags| OSM wiki on [highway](http://wiki.openstreetmap.org/wiki/Key:highway)| +|**Crossing waterways/highways**|[![crossingwater](https://cloud.githubusercontent.com/assets/6770741/11389332/779fd81c-9365-11e5-9467-7cdd96b3a2a3.gif)](https://cloud.githubusercontent.com/assets/6770741/11389332/779fd81c-9365-11e5-9467-7cdd96b3a2a3.gif)| Run `shift+v` to get all crossing waterways and highways| Add `layer=1` to bridges to solve the issue|[bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)| +|**Missing highway names**|[![missingnames](https://cloud.githubusercontent.com/assets/6770741/11389598/44b162d8-9368-11e5-8b53-7228fd992ebc.gif)](https://cloud.githubusercontent.com/assets/6770741/11389598/44b162d8-9368-11e5-8b53-7228fd992ebc.gif) The names of highways should be added using recent TIGER (Only for USA) data| Steps to add predefined [imagery sources](https://josm.openstreetmap.de/wiki/Help/Preferences/Imagery) in JOSM | OSM wiki on [TIGER](http://wiki.openstreetmap.org/wiki/TIGER)| +|**Abbreviated road names**|[![abbreviated](https://cloud.githubusercontent.com/assets/6770741/11389977/8352e5a4-936b-11e5-9b0c-c3b01e9e7857.gif)](https://cloud.githubusercontent.com/assets/6770741/11389977/8352e5a4-936b-11e5-9b0c-c3b01e9e7857.gif)| Do not abbreviate street names, write full name| E.g: Boulevard as Blvd, Street as St, Court as Ct, Drive as Dr etc| +|**Way end node near other highway**|[![screenshot 2015-11-25 12 21 54](https://cloud.githubusercontent.com/assets/6770741/11390480/90f90710-9370-11e5-9ea7-05bcaf1ffc85.png)](https://cloud.githubusercontent.com/assets/6770741/11390480/90f90710-9370-11e5-9ea7-05bcaf1ffc85.png)Nodes which ends near to other highways| Select the node and press `shift+j` to connect it.|| +|**Possibility to improve alignment**|[![improvement](https://cloud.githubusercontent.com/assets/6770741/11390603/e4807660-9371-11e5-94e8-fabf25e62fa4.gif)](https://cloud.githubusercontent.com/assets/6770741/11390603/e4807660-9371-11e5-94e8-fabf25e62fa4.gif)| Use `W` to align the lines/polygons to the imagery| | +| \ No newline at end of file diff --git a/jp/becoming-a-power-mapper/_posts/reference/0000-01-08-useful-overpass-queries.md b/jp/becoming-a-power-mapper/_posts/reference/0000-01-08-useful-overpass-queries.md new file mode 100644 index 0000000..787e1de --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/reference/0000-01-08-useful-overpass-queries.md @@ -0,0 +1,16 @@ +--- +title: Useful Overpass queries +--- + + +Need | Query +---|--- +Newer than a given date| `[out:xml][timeout:600];(way["highway"](newer:"2015-05-30T07:00:00Z")({{bbox}}););out body;>;out skel qt;` +Changes in a given time period|`[out:xml][timeout:600];(way["highway"](changed:"2015-05-14T07:00:00Z","2015-05-30T07:01:00Z")({{bbox}}););out body;>;out skel qt;` +provide two dates and generate a difference between the two| `[diff: "2015-06-30T15:00:00Z","2015-09-21T15:00:00Z"][out:xml][timeout:25];(way["highway"]({{bbox}}););out body;>;out skel qt;` +extract edits of a user| `[out:json][timeout:25];(node(user:"ramyaragupathy")({{bbox}});way(user:"ramyaragupathy")({{bbox}});relation(user:"ramyaragupathy")({{bbox}}););out body;>;out skel qt;` +extract a particular tag| `[out:json][timeout:25];(node["amenity"="hospital"]({{bbox}});way["amenity"="hospital"]({{bbox}});relation["amenity"="hospital"]({{bbox}}););out body;>;out skel qt;` +extract all amenities| `[out:json][timeout:25];(node["amenity"]({{bbox}});way["amenity"]({{bbox}});relation["amenity"]({{bbox}}););out body;>;out skel qt;` +find a particular tag without someother key value| `[out:json][timeout:25];(node["highway"="footway"]["footway"!~"."]({{bbox}});way["highway"="footway"]["footway"!~"."]({{bbox}});relation["highway"="footway"]["footway"!~"."]({{bbox}}););out body;>;out skel qt;` +query within query| `[out:json][timeout:250];((way({{bbox}})[highway='primary'];relation({{bbox}})[highway='primary'])->.a;node.a[name='Sand Hill Road'];);out body;>;out skel qt;` +search for a tag in an area| `[out:json][timeout:250];(area[name="Palo Alto"];way(area)["building"];relation(area)["building"];);out body;>;out skel qt;` \ No newline at end of file diff --git a/jp/becoming-a-power-mapper/_posts/reference/0000-01-09-useful-osm-resources.md b/jp/becoming-a-power-mapper/_posts/reference/0000-01-09-useful-osm-resources.md new file mode 100644 index 0000000..af5ec84 --- /dev/null +++ b/jp/becoming-a-power-mapper/_posts/reference/0000-01-09-useful-osm-resources.md @@ -0,0 +1,69 @@ +--- +title: Useful OSM resources +--- +The OSM ecosystem has an array of tools that you can use to extract, modify, visualize data, and contribute to! + +## Mapping +- [OSM Map features](http://wiki.openstreetmap.org/wiki/Map_Features) +- [Taginfo - tagging stats](http://taginfo.openstreetmap.org/) + +## Survey tools +- [Fieldpapers](http://fieldpapers.org) for paper based surveying +- [Mapillary](http://mapillary.com/) for crowdsourcing streetview imagery + +### Tasking Tools +- [To-fix](http://osmlab.github.io/to-fix/) +- [Map Roulette](http://maproulette.org/) +- [Map tasking manager](http://tasks.openstreetmap.us/) for coordinating mapping in a continuos area + +## Data +- [Awesome GeoJSON](https://github.com/tmcw/awesome-geojson) - list of some awesome tools around GeoJSON +- [Overpass Turbo](http://overpass-turbo.eu/) for querying OSM by properties +- [GeoJSON.io](http://geojson.io/) for creating / editing GeoJSON data +- [Dropchop](http://dropchop.io/) for GIS based actions +- [Flatten GeoJSON attributes](http://batpad.github.io/geojson-flatten-tags/) Converter +- [Merge GeoJSONs](https://github.com/mapbox/geojson-merge) +- [Minjur](https://github.com/mapbox/minjur) for converting large OSM data to GeoJSON +- [tippecanoe](https://github.com/mapbox/tippecanoe) Builds vector tilesets from large collections of GeoJSON features +- [Collection of useful GeoJSON tools](https://github.com/tmcw/awesome-geojson) +- [toGeoJSON](http://mapbox.github.io/togeojson/) toGeoJSON turns KML & GPX into GeoJSON + + +### Visualization +- [OSM Changes Visualization](https://github.com/ericfischer/osm-animate) +- [Compare OSM and Google Maps](http://lxbarth.com/compare/#17/33.81196/-117.91879) + +### Extracts +- [OSM planet extracts](http://planet.osm.org) +- [Geofabrik region extracts](http://download.geofabrik.de/openstreetmap/) +- [Mapzen metro extracts](https://mapzen.com/data/metro-extracts) +- [OSM QA Tiles](http://osmlab.github.io/osm-qa-tiles/) + +### QA and Activity Tracking +- [OSM Inspector](http://wiki.openstreetmap.org/wiki/OSM_Inspector) +- [WHODIDIT](http://zverik.osm.rambler.ru/whodidit/) OpenStreetMap Changeset Analyzer +- [Heatmap](http://yosmhm.neis-one.org/) + +For full list check the [OSM Wiki](http://wiki.openstreetmap.org/wiki/Quality_assurance) + + +## Community +- Use the [history tab on the map](http://www.openstreetmap.org/history#map=14/51.5150/-0.0972) to find and message active mappers nearby +- Write on your [OSM Diaries](http://www.openstreetmap.org/diary) to bring up issues for community discussion +- Join your local [community mailing list]() for discussions on various topics +- [Who is around me?](http://resultmaps.neis-one.org/oooc) Find local mappers + +### Contribute +- To the [OSM Homepage](https://github.com/openstreetmap/openstreetmap-website) +- To the development of the [OSM map style and cartography](https://github.com/gravitystorm/openstreetmap-carto/issues) +- By publishing your tool on [osmlab](https://github.com/osmlab) +- [OSM wiki: Contribute](http://wiki.openstreetmap.org/wiki/How_to_contribute) + +### Guides and FAQ +- [OSM wiki FAQ](http://wiki.openstreetmap.org/wiki/FAQ) +- [OSM help](https://help.openstreetmap.org) +- [LearnOSM mapping guides](http://learnosm.org) +- [HOT OSM tracing guides](http://hotosm.github.io/tracing-guides/) +- [Mapbox Guides](https://www.mapbox.com/guides/) +- [State of Satellite imagery](http://satsummit.github.io/landscape/) +- [Satellite and Sensor Database](https://www.itc.nl/research/products/sensordb/searchsat.aspx) \ No newline at end of file diff --git a/jp/becoming-a-power-mapper/index.md b/jp/becoming-a-power-mapper/index.md new file mode 100644 index 0000000..a4f7d40 --- /dev/null +++ b/jp/becoming-a-power-mapper/index.md @@ -0,0 +1,17 @@ +--- +title: Becoming a power mapper +layout: category +order: 7 +color: purple +# these section refer to the subfolders in _posts/ +# the subfolder names and the section list names must match exactly +# these are not case sensitive +sections: +- Mapping +- JOSM +- Reference +description: These advanced topics will allow you to take your mapping skills to the next level. +image: becoming-a-power-mapper.svg +--- + +These advanced topics will allow you to take your mapping skills to the next level. \ No newline at end of file diff --git a/jp/getting-started/_posts/0000-01-01-getting-started.md b/jp/getting-started/_posts/0000-01-01-getting-started.md new file mode 100644 index 0000000..293dd57 --- /dev/null +++ b/jp/getting-started/_posts/0000-01-01-getting-started.md @@ -0,0 +1,143 @@ +--- +title: Getting started +--- + +To [get started editing OpenStreetMap using JOSM](https://www.mapbox.com/blog/making-the-most-josm/), set up your work environment with the tools you would need. + +## Setting up an OpenStreetMap Account + +1. Go to OpenStreetMap.org and create an account: [https://www.openstreetmap.org/user/new](https://www.openstreetmap.org/user/new). +2. **IMPORTANT** add a picture of yourself to your profile. +3. Add a profile description like below: + +### Profile description + +It is useful to include: + +- The areas you are interested in mapping; +- A nice message that allows others to get in touch; +- Links to your homepage/twitter etc that allows people to follow you. + +*(format in [Markdown]( http://en.wikipedia.org/wiki/Markdown))* + +Here is a good example: + +![osm-profile-description-example]({{site.baseurl}}/images/osm-profile-description-example.png) + +## Installing JOSM + +We are using the Java OpenStreetMap Editor (JOSM) for most tasks. Here's how to get set up. + +**1. Download and install JRE** + +JOSM requires the Java Runtime Environment - JRE. [Download and install JRE]( http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html). + +**2. Download JOSM** + +Go to the [JOSM website](https://josm.openstreetmap.de/wiki/Download) to download the `tested` version. Place it in a common location for applications on your operating system. + +- OSX: `/Applications/` +- Windows: `C:\Program Files\` + +**3. Open JOSM** + +Open the JOSM application you downloaded with a double click. + +If you want JOSM to use more memory and you're using [Linux](http://wiki.openstreetmap.org/wiki/JOSM/Linux) you can also run it with: + + ~$ java -Xmx1024M -DproxyHost=$PROXY -DproxyPort=8080 -jar josm-tested.jar + +Once JOSM is up and running it looks like this. Go find the **Preferences** dialog, you'll need it for the next couple of steps. You can access it from under the light switch icon. + +![josm-preferences]({{site.baseurl}}/images/josm-preferences.png) + +**4. Enable expert mode** + +Open the **Preferences** dialog and enable **Expert mode**. + +![check-expert-mode]({{site.baseurl}}/images/check-expert-mode.png) + +**5. Add user and password** + +Now it's time to connect to OpenStreetMap. Add the user name and password of the account you created on OpenStreetMap to JOSM. + +![set-osm-username-and-password]({{site.baseurl}}/images/set-osm-username-and-password.png) + +Now you should be able to retrieve data from OpenStreetMap by clicking on the button with the green down error in the top left: + +![download-data]({{site.baseurl}}/images/download-data.gif) + +**6. Enable Remote Control** + +Remote control allows you to launch JOSM directly from the map on OpenStreetMap.org. To enable Remote Control, check this box in the settings: + +![enable-remote-control]({{site.baseurl}}/images/enable-remote-control.png) + +Also check the **Download objects to a new layer** option. Now you should be able to retrieve data directly starting on OpenStreetMap.org like this: + +![retrieve-data]({{site.baseurl}}/images/retrieve-data.gif) + +**7. Increasing the allocated memory for JOSM** + +By default JOSM is allocated with 247-1024 MB of memory depending on the operating system. When JOSM reaches its maximum handling limit it pops up an error highlighting `JOSM is out of memory` + +![increasing memory]({{site.baseurl}}/images/increasing-memory.png) + +To get rid of this error increase the default allocated memory for JOSM by following [these steps](https://gist.github.com/jothirnadh/00352fff58ce2628cc4f#supply-parameters). If you are not sure of fixing this, do contact someone from the data team. + +## Using a gaming mouse + +Using a gaming can increase your productivity by assigning shortcuts to common mapping tasks. This section outlines the basic configuration to use a gaming in JOSM. + +**Systems:** Linux and Mac + +**Equipment:** Razer Gaming mouse + +**General guidelines:** Increase mouse speed in `System Preferences> Mouse` for Mac + +**Example Feature** + +**Buildings** + +**Configure gaming mouse and keyboard** + +1. Install Razer Naga config software: https://www.razerzone.com/synapse/ +2. Create an account in razer ID: https://razer-id.razerzone.com/new +3. Build your profile using your email id +4. Configure the mouse: + +**Common shortcuts essential to configure in your gaming mouse for buildings**: Enter, Extrude (`X`), building tracing (`B`), upload and download data to OSM (use the default keyboard shortcuts in your JOSM). + +**Good to have**: Join and merge nodes/ways (`J` and `M`), select overlapping ways (`I`), join overlapping areas (`Shift + J`), Split objects (`Alt + X`) + +**Note**: Pattern to follow in setting up your mouse: + +**Left hand (shortcuts in the keyboard)**: + + * Upload + + * Select + + * Orthogonalize + + * Rotate + +**Right hand (shortcuts in your mouse)**: + + * Enter + + * X + + * B + + * Merge two nodes(M) + + * Join node to way (N) + + * Select intersecting ways (I) + + * Join overlapping ways (shift+J) + + Configure any other shortcut according to the mapper choices. + +**Note**: For mapping other features like roads and to fix task, create separate configurations with the shortcuts required only for those features. diff --git a/jp/getting-started/index.md b/jp/getting-started/index.md new file mode 100644 index 0000000..89512b3 --- /dev/null +++ b/jp/getting-started/index.md @@ -0,0 +1,8 @@ +--- +title: Getting started +layout: category +order: 1 +color: purple +description: To get started editing OpenStreetMap using JOSM, set up your work environment with the tools you would need. +image: getting-started.svg +--- diff --git a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md new file mode 100644 index 0000000..e5ed2f1 --- /dev/null +++ b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md @@ -0,0 +1,258 @@ +--- +title: Mapping common features +--- + +This is a walkthrough of how to create and edit the most common features on OpenStreetMap. It's an introduction to get you started mapping but not meant to be comprehensive. We're going to use some OpenStreetMap specific terms here, if you're not familiar with what "nodes", "way" and "relations" are, read the previous guides first. + +## How do I map X? + +We're focusing in this section on the most common map features. For full documentation, refer to the [OpenStreetMap Map Features](http://wiki.openstreetmap.org/wiki/Map_Features) guide or [Feature categories](http://wiki.openstreetmap.org/wiki/Category:Features). To look up a specific map feature fast, for instance how to map a bus stop, google with a query like "tag bus stop site:wiki.openstreetmap.org": + +![](https://s3.amazonaws.com/f.cl.ly/items/3C3A0S3k011k1P3b2J0N/google.gif) + +A valuable complimentary resource is [taginfo.openstreetmap.org](http://taginfo.openstreetmap.org/). Tag info shows you the number of times a specific tag has been used, which lets you find out how established a tag is. + +## Roads and paths + +Roads are some of the most significant features we map. While roads are easy to trace off of Satellite imagery there is a large vocabulary for classifying different types of roads. + +### Tracing roads + +Tracing a road is simple. Use the **Draw** (`A`) tool in JOSM or the **Line** tool in iD and draw the road following its course. The trick is to use the right amount of nodes to describe a way. Too few make the road appear very jagged. Too many are unnecessary data and make the road hard to edit later. + +Look at the picture below, the first example was traced with too few nodes, it is too jagged; the second example was traced with too many nodes adding redundant information; the last one is traced right: + +![mapbox guide big](https://cloud.githubusercontent.com/assets/693781/10158378/f3a4b3fc-6691-11e5-9738-58ad86a5a525.png) + +Roads must be connected where they intersect. On the left you can see two roads just crossing each other, on the right note how a node connects the two roads. This is important for navigation, where vehicles must be guided from one road to the other. + +![](https://s3.amazonaws.com/f.cl.ly/items/180r0E2l0P2H0m0Z3m07/Screen%20Shot%202015-01-04%20at%208.55.14%20PM.png) + +And follow the flow of roads where possible. On the left, the road was traced with a "detour" for no apparent reason. On the right you see how the road tracing follows the logical flow of the road. + +![wrong: "map around corners", right: follow flow](https://s3.amazonaws.com/f.cl.ly/items/0k1F3Y0m0y081H3v0W07/Screen%20Shot%202015-01-04%20at%208.48.54%20PM.png) + +Trace every *physically* separated lane as a separate way. See for example this dual carriage way (orange): + +![dual carriage way](https://s3.amazonaws.com/f.cl.ly/items/0f0z0i391l0C0e0X3d0b/Screen%20Shot%202015-01-04%20at%209.01.42%20PM.png) + +When mapping a dual carriage way, make sure that connecting roads are properly connecting to both carriages *if* this connection is possible in reality: + +![show 2 examples of connecting roads to a carriage way: one connecting to both lanes, one to only one lane](https://s3.amazonaws.com/f.cl.ly/items/07043M2U0H093c2q1r3m/Screen%20Shot%202015-01-04%20at%209.01.4222%20PM.png) + +### Everything's a highway + +No matter whether it's an overland road, a city street, a foot path or a cycleway, you'll find it tagged with the `highway` key. Here are some examples of common tags: + +- `highway=residential` - a residential road in a city +- `highway=motorway` - a fast restricted access road +- `highway=footway` - a foot path +- `highway=cycleway` - a cycleway + +Roads often come with secondary tags, further specifying type or attribute of a road: + +- `oneway=yes` says a road is a one way +- `lanes=2` says how many lanes a road has +- `name=Broadway` designates a street name +- `access=private|permissive` describes the level of access on a road +- `service=parking_aisle|driveway` further specifies the type of `highway=service` + +### Oneways + +Oneways are mapped by simply adding a `oneway=yes` tag to the road's way. Keep in mind that ways have a directionality. So the road will be a oneway in the direction of the way. If you need to change the flow of the one way, you have two options: + +- Change the direction of the way (`Tool > Reverse Ways` in JOSM or the `<<` context icon on iD) +- Or tag with `oneway=-1` - use this approach where the way's directionality already governs another attribute such as bus route. + +![tagging a oneway](https://s3.amazonaws.com/f.cl.ly/items/1W0M081C2W3K0j0p1I2r/oneway.gif) + +OpenStreetMap Wiki: [Key:oneway](http://wiki.openstreetmap.org/wiki/Key:oneway) + +### Turn restrictions + +Turn restrictions are rules that disallow certain turn maneuvers. Here's for instance a "no right turn" sign. + +![](https://farm3.staticflickr.com/2900/14360050862_ef35f7ffa8_b.jpg) + +To map turn restrictions in JOSM, use the **turnrestrictions** plugin. Once enabled, you can activate a new turn restriction panel from the `Windows > Turn Restriction` menu item. + +Once enabled, create new turn restrictions or edit existing ones from the panel. Here is an example of how to create a simple "no right turn" restriction. We're selecting the way we can't take the right turn from as "from" object, the way we can't take the right turn to as "to" object and then we specify that the restriction is a "no right turn" restriction. As we save the turnrestrictions dialog warns us that there is no "via" object defined. It is not strictly required to have one, but is good practice, so we define one. + +![](https://s3.amazonaws.com/f.cl.ly/items/24173W1U033a193q2l1F/turn.gif) + +Turn restrictions can get more complex quickly, so before you create or edit turn restrictions, make sure you read through and understand all available documentation on the OpenStreetMap wiki. + +*Video: [How to edit turn restrictions in JOSM](https://www.youtube.com/watch?v=0SdixDJAED0)* + +*OpenStreetMap Wiki: [Relation:restriction](http://wiki.openstreetmap.org/wiki/Relation:restriction)* + +### Simple classification guide + +One of the more subtle skills to learn in OpenStreetMap is how to properly classify roads. The `highway` tag has more than eight values for roads, another five-plus for non-vehicular traffic, and a series of secondary tags. What's more, highway classifications are highly country specific and follow different conventions on a country by country basis. + +Here's a quick guide on how to go about working with road classifications in OpenStreetMap. + +1. Follow existing classifications. Don't change classifications and follow the conventions you see on the local map for new data. +2. The smallest roads in a network are the easiest ones to identify and also the ones you'll wind up adding most. For minor roads, prefer `highway=residential` in built up residential areas, `highway=unclassified` for everything else. +3. For all other cases, use `highway=road` + +For a full reference on highway mapping, look at the *[wiki entry for the highway tag](http://wiki.openstreetmap.org/wiki/Key:highway)*. + +### Intersections + +The intersection between a road and another feature must always be defined. Where they meet, there is either an intersection, a tunnel or a bridge. + +#### Simple intersections between two roads + +To create a simple intersection between two roads, just make sure to connect the two roads with a node. + +![show how 2 roads connect](https://s3.amazonaws.com/f.cl.ly/items/1b0K0E2b401E0U2U1H1A/intersect.gif) + +#### Tunnel + +A tunnel carries the `tunnel=yes` and a `layer=` tag that is one lower than the `layer=` tag of the feature it intersects with (default `layer` value is 0). The road is *not* connected with the other feature. Split ways where the tunnel starts + +![show how to map a tunnel](https://s3.amazonaws.com/f.cl.ly/items/0e3S3F3j1N000w1R1d2x/tunnel.gif) + +A building passage is a special type of tunnel that passes through a building. To map a building passage, connect the road where it intersects with the building outline with nodes, then tag the portion of the road that intersects with the building with `tunnel=building_passage`. + +![map a building passage](https://s3.amazonaws.com/f.cl.ly/items/1v1E0Z2P0C3X1K1h0Q1M/building-passage.gif) + +*OpenStreetMap Wiki: [Key:tunnel](http://wiki.openstreetmap.org/wiki/Key:tunnel)* + +#### Bridge + +In addition to the road's `highway=*` tag, a bridge carries the `bridge=yes` and a `layer=` tag that is one higher than the `layer=` tag of the feature it intersects with (default `layer` value is 0). + +![show how to map a bridge](https://s3.amazonaws.com/f.cl.ly/items/1v1P2S3P35292a1m2a0m/bridge.gif) + +*OpenStreetMap Wiki: [Key:bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)* + +#### Railroad crossing + +Map a railroad crossing similar to an intersection between two roads by connecting the road and the railroad with a node. Then tag the node with `railway=level_crossing`. Do not confuse this tag with `railway=crossing` which is only for pedestrian crossings. + +![map a level crossing](https://s3.amazonaws.com/f.cl.ly/items/1q3o381b0K3r3x291J0E/level_crossing.gif) + +*OpenStreetMap Wiki: [Tag:railway=level_crossing](http://wiki.openstreetmap.org/wiki/Tag:railway%3Dlevel_crossing)* + +#### Roundabouts + +Map a roundabout by tracing the circular road and tag it with `junction=roundabout`. For the road classification, use the highest classification of all roads connected to the roundabout. The `junction=roundabout` tag implies a oneway - make sure that the directionality of the way is correct. + +![ezgif-1791703736](https://cloud.githubusercontent.com/assets/12744420/10310207/745ec272-6c5e-11e5-8d4c-5727e8b5d42e.gif)) + +#### Complex intersections + +In a complex intersection involving multiple carriage ways trace the roads so that they reflect the flow along the main carriages and make sure that oneways make sense. + +![](https://s3.amazonaws.com/f.cl.ly/items/0M3S232n2V342Y3T2n1Y/Screen%20Shot%202015-01-04%20at%2010.34.51%20PM.png) + +## Buildings + +Tracing buildings takes good imagery and patience. Take your time and pay attention to angularity, alignment between buildings and reflecting the regularities between buildings. Buildings are traced as outlines of *where the building meets the ground*. This last piece is important. The roof outline is often easier to see in the imagery so you'll find it often traced in OpenStreetMap but it's wrong and needs to be shifted to the ground outline. + +![505kyfalbo](https://cloud.githubusercontent.com/assets/126868/6914386/8d115556-d7a7-11e4-9f04-7291331e7ef8.gif) + +The main challenge with tracing buildings is lack of detail in imagery. Where you don't find good enough imagery for tracing a building, just don't trace it. + +Here are a couple of JOSM specific tips to trace buildings effectively. + +For tracing buildings, use the **buildings plugin**. Once enabled, a new building tool will be available in the edit toolbar on the left. The building tool `B` will draw rectangular shapes tagged `building=yes` for you. To draw buildings parallel to each other, draw the first building, select it, then draw subsequent buildings. + +![](https://s3.amazonaws.com/f.cl.ly/items/3A2T0l0Y3x0N030w090F/building.gif) + +If you draw closed ways free hand, use `Tools > Orthogonalize Shape` or press `Q` to square out buildings like so: + +![](https://s3.amazonaws.com/f.cl.ly/items/3U3c1S1V2X1Q1h3s0845/Screen%20Shot%202014-12-15%20at%206.35.04%20PM.png) + +Use auxiliary lines to align protruding portions of a building: + +![](https://s3.amazonaws.com/f.cl.ly/items/0s3G3T200b1C3d3i0x2Y/buildingalignment.gif) + +To align previously traced buildings neatly, select them, and then select two reference nodes to create an alignment axis and orthoganalize `Q` the selection. + +![3zpk8nxbdt](https://cloud.githubusercontent.com/assets/126868/6900081/d65cf23c-d721-11e4-82f9-7084b11bb41f.gif) + +You can use split buildings temporarily with `Tools > Split Way` or pressing `P` to orthogonalize portions of a building before reconnecting the with `Tools > Connect Way` or pressing `C`: + +![](https://s3.amazonaws.com/f.cl.ly/items/151R161W3i2c043q1z0B/straightenc.gif) + +Here is a quick end to end walkthrough of how to trace a building: + +![](https://s3.amazonaws.com/f.cl.ly/items/3T0Y0h390L3l19000s2h/buildings.gif) + +*OpenStreetMap Wiki: [Key:building](http://wiki.openstreetmap.org/wiki/Key:building)* + +*Video: [Tracing buildings with JOSM](https://www.youtube.com/watch?v=9GRIHSAAkSs)* + +## Points of interest + +"Point of interest" is a general term for a real world point-like feature noteworthy enough to include it on a map. Some examples are restaurants, cafés, shops, banks, churches, public toilets and water fountains. There's not a single point of interest tag key in OpenStreetMap but a variety that can be used for mapping a point of interest: `amenity=`, `shop=`, `tourism=` are some examples. + +*OpenStreetMap Wiki: [Key:amenity](http://wiki.openstreetmap.org/wiki/Key:amenity), [Key:tourism](http://wiki.openstreetmap.org/wiki/Key:tourism), [Key:shop](http://wiki.openstreetmap.org/wiki/Key:shop), [Key:leisure](http://wiki.openstreetmap.org/wiki/Key:leisure)* + +### Simple point of interest + +The simplest way to map a point of interest is to create a single node and add corresponding tags. Here's an example of a fountain mapped in OpenStreetMap: + +![](https://s3.amazonaws.com/f.cl.ly/items/2a0E2w0u2U0D0t2b1Z3Y/fountain.gif) + +Here's an example of a restaurant: + +![](https://s3.amazonaws.com/f.cl.ly/items/1R3K0A1p0C1G043n1o3d/komi.gif) + +### Areas as points of interest + +Wherever you can clearly determine the extent of a "point" of interest, map it. A good example are parks, here is Folger Park in Washington DC. The Park is mapped as a closed way tagged `leisure=park`. Note how the way follows the exact outline of the park. + +![](https://s3.amazonaws.com/f.cl.ly/items/0V2N0n290Z1L0H1h2b1e/Screen%20Shot%202015-01-10%20at%208.29.39%20AM.png) + +### Building as point of interest + +Sometimes the building itself is considered the point of interest. Think for instance of a MacDonalds restaurant in an urban multi-use building versus a MacDonalds drive through in a suburban strip mall. Or - often easy to spot from satellite imagery - think of a place of worship like a church. In such cases the building itself should be tagged as a point of interest. Here's a church that has first been mapped as a single node in a building. The example shows how all tags from the node are transferred to the building and then the node is removed. + +![](https://s3.amazonaws.com/f.cl.ly/items/2m0k0v333M1H0i1t3p1V/church.gif) + +### Schools and universities + +Schools can just be mapped as a simple node tagged `amenity=school`. But often schools occupy an entire building or a piece of land. School grounds, the terrain on which a school sits, are mapped as `amenity=school`. The buildings of a school are mapped as `building=school`. Mapping schools as just a simple node is fine. However, wherever appropriate, map a school's ground and buildings as ways. + +An example where a school *does not* occupy the entire building: + +![](https://s3.amazonaws.com/f.cl.ly/items/0H2W3b401X3H0r0O011s/Screen%20Shot%202015-01-09%20at%206.09.01%20PM.png) + +An example where a school *does* occupy an entire building: + +![](https://s3.amazonaws.com/f.cl.ly/items/0r3q0C0w2L0C3n3d2f11/Screen%20Shot%202015-01-09%20at%206.18.28%20PM.png) + +An example where a school occupies its own school grounds: + +![](https://s3.amazonaws.com/f.cl.ly/items/1W1A1p0U3z3D3E3g183M/highschool.gif) + +Universities are similar: + +![](https://s3.amazonaws.com/f.cl.ly/items/102S1D1Z472x213M2b0Y/university.gif) + +*OpenStreetMap Wiki: [Tag:amenity=school](http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dschool), [Tag:building=school](http://wiki.openstreetmap.org/wiki/Tag:building%3Dschool), [Tag:amenity=university](http://wiki.openstreetmap.org/wiki/Tag:amenity%3Duniversity), [Tag:building=university](http://wiki.openstreetmap.org/wiki/Tag:building%3Duniversity), [Tag:amenity=college](http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dcollege)* + +## Streams and Rivers + +Trace small streams as just a way tagged with `waterway=stream`. The way's direction signals the direction in which the water flows. For larger rivers, trace the center of the river as `waterway=river` and in addition the river banks with `natural=water` and `water=river` tags. The name of the river always sits on the waterway. See here for an example: + +![](https://s3.amazonaws.com/f.cl.ly/items/460R352M0H301L2Y1Q3T/river.gif) + +Islands in rivers are mapped as relations of `type=multipolygon`. Observe how on a multipolygon the `natural=water` and `water=river` tags sit on the multipolygon relation and not on the way: + +![](https://s3.amazonaws.com/f.cl.ly/items/0t0A0q06130m0O1c3I19/multiriver.gif) + +*Video: [Map a river island](http://cl.ly/0M0m2C2t2T3g)* + +*OpenStreetMap Wiki: [Tag:waterway=river](http://wiki.openstreetmap.org/wiki/Tag:waterway%3Driver)* + +## Coming soon + +- Walking and cycling paths +- Places (city versus village versus suburb versus neighborhood) +- Lakes +- Tracing highway areas \ No newline at end of file diff --git a/jp/mapping-common-features/index.md b/jp/mapping-common-features/index.md new file mode 100644 index 0000000..6676654 --- /dev/null +++ b/jp/mapping-common-features/index.md @@ -0,0 +1,8 @@ +--- +title: Mapping common features +layout: category +order: 5 +color: orange +description: A walkthrough of how to create and edit the most common features on OpenStreetMap. +image: mapping-common-features.svg +--- diff --git a/jp/mapping-for-navigation/_posts/0000-01-01-introduction.md b/jp/mapping-for-navigation/_posts/0000-01-01-introduction.md new file mode 100644 index 0000000..5e42863 --- /dev/null +++ b/jp/mapping-for-navigation/_posts/0000-01-01-introduction.md @@ -0,0 +1,86 @@ +--- +title: Introduction +--- + +The most basic use of a map is to find out where one is located. After that, one usually wants to use the map to find the best route to another location. On a [digital map](https://en.wikipedia.org/wiki/Digital_mapping), this is usually provided with [turn by turn navigation](https://en.wikipedia.org/wiki/Turn-by-turn_navigation) using a [navigation device](https://en.wikipedia.org/wiki/GPS_navigation_device). + +![navigation_optimized](https://cloud.githubusercontent.com/assets/13744156/18119269/76493c6c-6f77-11e6-8c18-a1daf7845f0b.gif) +_Let the computer find the best route for you!_ + +## Components of map navigation + +A navigations system has user facing components that interact with the user and back end components that computes the best route based on the user input and available data. In this guide we will focus on the back end components that rely on map data. + +**User facing components** +- User interface controls for setting the the origin and destination +- Map display that visually represents the route to take +- Turn by turn instructions that accurately describe the navigation maneuvers at the appropriate time +- Route status that includes current progress and the estimated time of arrival (ETA) at the destination + +**Back end components** +- A navigation profile that describes the mode of transport to use for the routing algorithm (eg. truck, cycle or foot) +- A route finder that finds the best possible route between the origin and destination for the selected navigation profile +- A guidance system that converts the route into instructions for turn by turn navigation + +### Navigation profile + +The navigation profile accurately describes the preferred types of roads to take based on the mode of transport used. A walking profile will have a fairly constant walking speed on any type of road, while a car profile will have avery high traveling speed on a motorway and will be much slower on a residential road. This has a large influence on the route finder. + +![screenshot_20160831-124644](https://cloud.githubusercontent.com/assets/8401827/18120537/b392baac-6f7d-11e6-9e36-480b3145c429.png) + +*Different routing profiles: cars, walking, bicycle.* + +### Routing + +[Routing](http://wiki.openstreetmap.org/wiki/Routing) is the process of selecting the best path in a network interconnected of roads on the map. Every road segment on the map has a traveling speed calculated based on various road factors, and the fastest and safest route is selected from all possible combinations. + +![](https://farm4.staticflickr.com/3814/12241013316_df99a4ff83_o.png)
+_Finding the route between two points involves complex calculations on a [routing graph](https://www.mapbox.com/blog/smart-directions-with-osrm-graph-model/)_ + +The calculation of an accurate route depends on a variety of factors which are taken into account by the routing algorithm: + +* Personal factors: fastest route, most scenic route, quietest route, shortest route, facilities needed, toll rates +* Vehicle factors: mode of transport, physical category of vehicle, optimum traveling speed, riding surface requirements, fueling requirements +* Route factors (static): classification of road, access restrictions, speed limits, turn restrictions, oneway rules, number of lanes +* Traffic factors (dynamic): traffic conditions, traffic signal cycle duration, weather conditions +* Riding surface factors: surface material, smoothness, barriers, speed breakers, road width, lane width, age + +### Guidance + +![](https://cloud.githubusercontent.com/assets/12932279/16989362/402b3f44-4e94-11e6-8e8a-a60cf0b08705.png) +_A route is converted into a series of easy to follow instructions for the user_ + +Route guidance is used to lead a person through the determined path. Once the routing algorithm determines the best path, that route is converted into a set of human-readable instructions known as guidance. The guidance represents the street names, the turn lanes marked on the roads, exit numbers, and destinations shown on sign boards. Accurate and relevant guidance can greatly enhance the user experience of using the map for navigation. + +## Navigating the future + +Providing accurate navigation using maps is dependent on having detailed and updated data about the world. The world is transforming every second and the next generation of navigation will need to have the latest information about the world that will come from various sources. + +### Telemetry + +screenshot 2016-09-15 21 27 43 +_Telemetry traces of Strava users from [Strava Globalheatmap](http://labs.strava.com/heatmap/#14/-74.02871/40.70159/blue/both)_ + +Telemetry is the remote collection of data which can be physical, environmental or biological. Most internet and GPS enabled phones collect location and other environmental data and reports it to a central service that can aggregate the data to determine traffic conditions on a road. + + +### Forward facing cameras & Street-view + +![untitled2](https://cloud.githubusercontent.com/assets/126868/18557457/a667474c-7b8c-11e6-844b-e308c650a8b1.gif) +_Crowdsourced streetview photographs from [narrow alleys in India using Mapillary](https://www.mapillary.com/app/?lat=23.018631999999997&lng=72.595325&z=17&pKey=4tjlrGmABA2sxmLLmAIq9Q&focus=photo)_ + +Street view images from dashcams, mounted cameras in vehicles using apps gives highly detailed 360° view of streets. This can help detect traffic signage, access restrictions, traffic signals, road markings to help add and confirm ground features into a map. Opensource street view photos include [Mapillary](https://www.mapillary.com/) and [OpenStreetView](http://openstreetview.com/). + +### Live Aerial & Drone Imagery + +screenshot 2016-09-15 21 34 33
+_High resolution imagery captured from [UAVs in Srilanka](https://www.mapbox.com/blog/sri-lanka-drone-imagery/)_ + +[Aerial imagery](https://en.wikipedia.org/wiki/Aerial_photography) using drones can capture the changing surface of the earth at a much higher resolution and lower cost compared to traditional satellite imagery that is expensive to acquire and are updated less frequently. + +### Machine learning and image recognition + +![untitled2](https://cloud.githubusercontent.com/assets/126868/18557642/4fba4e8e-7b8d-11e6-85fb-c30092aac39b.gif)
+_Automatic image segmentation by [Mapillary](http://blog.mapillary.com/update/2016/05/19/austria.html)_ + +Advances in [machine learning](https://en.wikipedia.org/wiki/Machine_learning) opens up opportunities to automate manual tasks like [digitization of roads from satellite](http://stateofthemap.us/2016/skynet/) imagery and can accelerate the creation and maintenance of map data. \ No newline at end of file diff --git a/jp/mapping-for-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md b/jp/mapping-for-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md new file mode 100644 index 0000000..90f2f3c --- /dev/null +++ b/jp/mapping-for-navigation/_posts/0000-01-02-modeling-roads-for-map-navigation.md @@ -0,0 +1,86 @@ +--- +title: Modeling Roads for Map Navigation +--- + +A navigation map is influenced by several road characteristics, such as the turn restrictions, improper way of road tracing and road classification. The most important ones among those are: + +### Road geometry +Roads are the main features that are used for rendering a route in all navigational applications. Correct road mapping leads not only to the well-looking map but also to better navigation experience. With the change in the shape of the traced road, the distance covered will be altered which affects the route. The common approach for road mapping is to trace roads following the center-line from satellite imagery. + +![road_with_two_lanes](https://cloud.githubusercontent.com/assets/369696/13230189/1bc4b308-d9ad-11e5-88b7-f85fcd290926.png) + +*Roads on satellite imagery* + +### Road connectivity / topology: +If you want to travel from point A to point E as shown in the below image, you can either travel from `A to B, B to C and then C to E` or `A to B, B to D and then D to E`. + +![screen shot 2016-08-30 at 6 51 58 pm](https://cloud.githubusercontent.com/assets/8401827/18090553/e4e4eabc-6ee2-11e6-9908-8c9064c833af.png) + +But, if you have a restriction to enter D from A, the only possible route will be `A to B, B to C and then C to E`. This is where connectivity plays a major role in deciding the final route. + +### Road attributes / properties: +If `A to C` is a primary road which is crossing through a service road `B to D` and you want to travel from `A to E`, the navigation map comes up with the route traveling from `A to B, B to C and then C to E` and completely avoids `A to B, B to D and then D to E` because the travel on Primary road is much efficient than a narrow service road. This is how the attributes / properties with which the road is assigned with plays a crucial role in deciding the final route. + +![screen shot 2016-08-30 at 8 30 14 pm](https://cloud.githubusercontent.com/assets/8401827/18094299/9d9f5454-6ef0-11e6-85de-4f74a43d5657.png) + +## OpenStreetMap data model: + +The OpenStreetMap data model consists of nodes, ways, relations, and tags. A detailed description of the data model can be found in the [The OpenStreetMap Data Model](https://github.com/mapbox/mapping/wiki/The%20OpenStreetMap%20Data%20Model) guide. + +Navigation data is similarly a combination of nodes, ways, relations, and tags. Some of the examples are illustrated below: + +### Examples + +* Nodes: + - Exit numbers: + +![screen shot 2016-08-30 at 5 20 44 pm](https://cloud.githubusercontent.com/assets/13744156/18088263/517c2cf0-6ed7-11e6-8485-2d2761c42e84.png) + +* Ways: + - Highway=* + +![screen shot 2016-08-30 at 6 17 55 pm](https://cloud.githubusercontent.com/assets/13744156/18089616/6d060d0e-6ede-11e6-829d-47fc464a53a1.png) + +*An way tagged with highway=secondary tag* + +* Relations: + - Turn restrictions are a combination of nodes, ways, tags, and relations. It consists of `from way` `via node` and `to way`, tied together by a `restriction=*` relation. + + +![tr_relation](https://cloud.githubusercontent.com/assets/13744156/18089141/0c296c9e-6edc-11e6-916f-716e41c9f685.gif) + +* Tags: All the navigation features are differentiated and defined based on how they are tagged. Tags can be on any element: on nodes, ways, and relations. + +Examples are: `destination=*`, `ref=*`, `turn:lanes=*`, `restriction=*`, etc. + +## Tracing roads + +Before tracing, we need to inspect the start and endpoints of the road segment. We need to identify the road direction, general numbers of lanes and the places where there are extra lanes. Based on this we choose our strategy for tracing. + +We are not able to draw a road on its center line, especially if roads join/fork or the number of lanes change. Imagine two roads which join: how would you draw the OSM-way around the point where the roads join? + + ![center_line](https://wiki.openstreetmap.org/w/images/4/47/Lane_Placement_2.png) + + _Center line tracing_ + + ![main_direction](https://wiki.openstreetmap.org/w/images/e/e4/Lane_Placement_3.png) + + _Tracing based on road direction_ + +### Tracing roads with more than two lanes + +There are two cases: +- Dual carriageway roads + + ![dual_carriageway_road](https://cloud.githubusercontent.com/assets/369696/13230427/fe21579c-d9ad-11e5-86ba-38107d469c54.png) + +These are bidirectional roads which have a physical separation between the lanes in both the directions. Both the ways will be counted for lanes and will be tagged with `lanes=*`. Dual carriageways are always `oneway` roads. + +![motorway](https://cloud.githubusercontent.com/assets/369696/13231932/5b417e00-d9b5-11e5-854e-dbed2d209d7c.png) +*Placement of nodes of the lines in each direction, opposite to each other* + +- Roads which carry traffic in both directions (Bidirectional roads) + + ![bidirectional_road](https://cloud.githubusercontent.com/assets/369696/13230341/9f9db6c0-d9ad-11e5-9f5d-53dd80b40f67.png) +*Road carrying traffic in both directions* + diff --git a/jp/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md b/jp/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md new file mode 100644 index 0000000..8c1f1bf --- /dev/null +++ b/jp/mapping-for-navigation/_posts/0000-01-03-road-features-mapping-guide.md @@ -0,0 +1,217 @@ +--- +title: Road Features Mapping Guide +--- + +*Detailed guide mapping features for navigation on the OpenStreetMap project. Before you start, please read the guide on [Mapping with OpenStreetMap](https://www.mapbox.com/mapping/)* + +[Query OpenStreetMap for Navigation Data via Overpass](http://overpass-turbo.eu/s/iyB) + +## Routing features + +These are features that help the routing engine find the safest and fastest route between two points. + + +### 1. Functional Road Class + +* `highway=*` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:highway) + +Roads are categorized according to its order of importance. They are tagged with the `highway=*`. The general order of importance for way types are: + +``` xml +highway= motorway > trunk > primary > secondary > ... > living streets > ... > footway +``` +![screen shot 2016-08-29 at 1 50 04 pm](https://cloud.githubusercontent.com/assets/13744156/18045336/ff8f31ea-6def-11e6-8692-bb4e082b94b8.png) + +*`highway=primary` in San Francisco* + +The value of the key helps show the importance of the highway within the road network as a whole. The importance ranges from the most important `motorway` to the least important `service`. The routing engine takes into account this importance of classification when determining optimum routes. + +Road classification may varies from country to country. The country specific use cases can be found in detail on separate wiki pages. For example, when mapping roads in India, the local community refer to the [India road tagging wiki](http://wiki.openstreetmap.org/wiki/India:Tags/Highway). + +Examples: + +* [US roads classification](http://wiki.openstreetmap.org/wiki/United_States_Road_Classification) +* [UK roads classification/numbering](https://en.wikipedia.org/wiki/Great_Britain_road_numbering_scheme) + +For an example of an area with a good concentration of different classes of roads on OpenStreetMap, look at [San Francisco](https://www.openstreetmap.org/#map=14/37.7788/-122.4375) area. This [osm query](http://overpass-turbo.eu/s/i4y) can be used to extract and gather numbers of all the highways present in a given bounding box on OpenStreetMap. + +[Department of Transportation](https://www.fhwa.dot.gov/about/webstate.cfm) websites and [wikipedia](https://en.wikipedia.org/wiki/United_States_Numbered_Highways) are some of the primary sources for highway information. + +### 2. Oneways + +* `oneway=yes` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:oneway) + +Oneways generally refer to road segments which allow traffic in only one direction. There are also streets which have oneway characteristics for only on certain times of the day to regulate traffic. + +![screen shot 2016-08-29 at 5 47 47 pm](https://cloud.githubusercontent.com/assets/13744156/18051463/5fdc162c-6e12-11e6-8984-c48da11bf73f.png) + +*`oneway=yes` shown in Mapillary* + +The best source of mapping oneways are again street level photos. + +[San Francisco](https://www.openstreetmap.org/#map=12/37.7574/-122.4845) is one area which has been well mapped for oneways in OpenStreetMap. This [overpass query](http://overpass-turbo.eu/s/i50) can be used to extract oneways from OpenStreetMap data. + +### 3. Turn-Restrictions + +* `type=restriction` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Relation:restriction) +* [Mapping guide](../adding-turn-restrictions/) + +`type=restriction` is added to a relation in OpenStreetMap which is used to describe turn restrictions at junctions. The relation has a set of tags that describes the type of restriction, for example. `no_left_turn`, `no_right_turn`, `no_u_turn`, etc. These are traffic signs at junctions and this information must be present on the map to find the best route by the routing engine while planning a route. + +![screen shot 2016-03-08 at 8 05 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604633/ad8bff4a-e569-11e5-9198-3ac9c88e5619.png) + +*Turn restriction denoting `no left turn` along with conditions: opening and closing times* + +The main resource for turn restriction data is [street view level images](https://www.mapbox.com/blog/safer-market-street/), local mapping drives, [DOT websites](http://www1.toronto.ca/wps/portal/contentonly?vgnextoid=83f6e69ae554e410VgnVCM10000071d60f89RCRD) + +![turn_restriction](https://cloud.githubusercontent.com/assets/13744156/18047415/7d9254c8-6dfa-11e6-94e6-9d85b58627c1.jpg) +*turn restriction which denotes `no right turn` at the junction* + +[San Francisco](https://www.openstreetmap.org/#map=13/37.7696/-122.4891) in OpenStreetMap has an excellent coverage of turn by turn restrictions at junctions. This [overpass query](http://overpass-turbo.eu/s/i4G) can be used to extract current turn restriction in a bounding box. + +### 4. Speed limits + +* `maxspeed=60` or `maxpseed=40 mph` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:maxspeed) + +The `maxspeed=*` tag defines the maximum legal speed limit for general traffic on a particular road, railway or waterway. The max speed values will be interpreted as kilometers per hour by default. The `maxspeed=*` is an important part of routing as it is used in determining the shortest time taken by a specific route to reach a destination. In the case of two routes, the one with the shortest time (higher maxspeed) and shortest distance will be considered as the optimum route. + + +![maxspeed](https://cloud.githubusercontent.com/assets/13744156/18046639/6602224c-6df6-11e6-8884-18a58bf4835a.jpg) + +*Maxspeed sign shown in Mapillary* + +The main data sources for detecting maxspeed signs are: [street view photos](https://www.mapbox.com/blog/mapillary-mapping/), [wikipedia](https://en.wikipedia.org/wiki/Speed_limits_in_Canada), [DOT documents](http://www.qld.gov.au/transport/safety/rules/speed-limits/index.html). + +The `maxspeed=*` data on OpenStreetMap (for example, in [London](https://www.openstreetmap.org/#map=14/51.5059/-0.1061)) in an area can be extracted by this [overpass query](http://overpass-turbo.eu/s/i4z). + + +### 5. Access-Restrictions + +* `access=*` +* [OSM Wiki](http://wiki.openstreetmap.org/wiki/Key:access) + +Apart from turn restrictions, there are access restrictions for different parts of highways. Some of these tags are `access=no`, `access=private` etc which will end up altering the route to be taken during the journey. For more information on the various kinds of `access=*` tags take a look at [Key:access](http://wiki.openstreetmap.org/wiki/Key:access) and [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions) and [access restrictions](http://wiki.openstreetmap.org/wiki/OpenStreetMap_tags_for_routing/Access-Restrictions) + +![749px-mutcd_r5-7](https://cloud.githubusercontent.com/assets/13744156/18048743/b688e696-6e01-11e6-80ae-e65ce6743830.png) + +*An `access=no` for non-motorized traffic, ends up altering the route for bicycle profiles, source: US MUTDC* + +All the `access=private` tags on OpenStreetMap ways, which will not allow that segment of the way to be used in a route can be extracted from this [overpass query](http://overpass-turbo.eu/s/i4J). An example of well-mapped access restrictions in OpenStreetMap can be found in [London](https://www.openstreetmap.org/#map=13/51.5061/-0.1366). + +The sources for mapping access restrictions in OpenStreetMap are: [street view photos](http://blog.mapillary.com/update/2016/05/24/use-mapillary-editing-OpenStreetMap.html), local mapping drives. + +### 6. Traffic signals + +Traffic signals such as: `highway=traffic_signals`, `highway=stop` or `barrier=toll_booth` as well as `traffic_calming=*` are considered during routing. The `type=restriction` more commonly referred to as **turn restrictions** are traffic signage which prohibits certain turns in intersections are also a crucial part of a great `routing` engine. + +More details on mapping `traffic signals` for cars and pedestrians can be found in the [OpenStreetMap wiki](http://wiki.openstreetmap.org/wiki/Tag:highway%3Dtraffic_signals). + +Street view photos from Mapillary, local mapping drives using [OpenStreetMap tracker](http://wiki.openstreetmap.org/wiki/OpenStreetMapTracker_(Android)) can be used as sources to map traffic signals in OpenStreetMap. + +![800px-led_traffic_lights](https://cloud.githubusercontent.com/assets/13744156/18049581/cc237796-6e06-11e6-8d51-b8d446b2c3dc.jpg) + +*Traffic signal in a junction* + + +## Guidance features + +## 1. Exit & destination signs + +**What are exit numbers?** + * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. + + ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) + +**Different tags for exit numbers:** +* `ref=*` is used when the exit has a specific number assigned to it. +* `noref=yes` is used when the exit doesn't have any official number assigned to it. + +**What are destination tags?** + +* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. +* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. + +![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) + +#### Different tags for destinations: +* `destination` tag refers to the place that the way exiting from the freeway leads to. +* `destination:ref` is the reference of the roads directly ahead. +* `destination:ref:to` is to specify the reference of a major highway ahead. +* `destination:street` refers to the main street the way exiting from the freeway leads to. + +An example of a place with good exit/destination coverage in OpenStreetMap is [Ottawa, Canada](http://www.openstreetmap.org/#map=11/45.4283/-75.8331). These overpass queries for [destination](http://overpass-turbo.eu/s/i61) and [exit numbers](http://overpass-turbo.eu/s/i78) can be used to extract exit/destination data from OpenStreetMap. + +The [detailed guide](../adding-exit-and-destination-signs/) on adding exit and destination numbers can be followed for adding exit/destinations. This guide is specifically focused on North America (US/Canada) for now. + +### 2. Turn Lanes + +As discussed in `Modeling Roads for navigation` page, there are two types of roads: unidirectional and bidirectional. `lanes=*` tag is used to count the number of lanes in both these type of roads. + +To set number of [lanes](http://wiki.openstreetmap.org/wiki/Key:lanes) for roads which carry traffic in both directions use [`:backward` and `:forward` suffixes](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right#Forward_and_backward) + +`Forward` means the direction in which the way is drawn in OpenStreetMap, while `backward` means the opposite direction. + +``` xml +Example: + highway=tertiary + lanes=5 + lanes:forward=3 + lanes:backward=2 +``` + +In the image below, the number of lanes is two - `lanes=2`. Orange line is the center line of bidirectional way which is the main way direction. When the extra lane starts in a bidirectional way, that segment is tagged as `lanes=3`+`lanes:forward=2`+`lanes:backward=1`. Optionally, we specify [placement](https://wiki.openstreetmap.org/wiki/Proposed_features/placement) of the lanes relative to the way. + + ![residential_road_2](https://cloud.githubusercontent.com/assets/369696/13228435/ae570094-d9a4-11e5-9f3c-4737112a7932.png) + +The below image have two tagging variants: + 1. `lanes=2` - 1 lane for each direction, or + 2. `lanes=3` - denote middle lane for left turn as (:point_left: _this is [discussed](http://wiki.openstreetmap.org/wiki/Proposed_features/Suffix_both_ways)_) + + ``` +highway=residential +lanes=3 +lanes:forward=1 +lanes:backward=1 +lanes:both_ways=1 +turn:lanes:both_ways=left + ``` + ![residential_road_3](https://cloud.githubusercontent.com/assets/369696/13229045/ab01d6f0-d9a7-11e5-8d8a-1fe5518c84a5.png) + + IN case the number of lanes is even but numbers of lanes for each direction not equal. :point_down: + + ![trunk_link](https://cloud.githubusercontent.com/assets/369696/13229897/b09a811c-d9ab-11e5-935e-25906c94585b.png) + +[Turn lanes](http://wiki.openstreetmap.org/wiki/Key:turn#Turning_indications_per_lane) have an influence on the path finding and are one of the most vital components for proper guidance. Choosing the correct turn lane can have a big influence in navigation. Oftentimes, they only help to illustrate a turn better but other times, they are vitally important. In guidance, the aim is to provide a set of instructions, like keep right or keep left by describing the optimum route found by the routing algorithm to a driver. + +![screen shot 2016-03-08 at 7 51 36 pm](https://cloud.githubusercontent.com/assets/8401827/13604319/236e84dc-e568-11e5-850a-cf398719db11.png) + +*How a driver views turn lanes from the car. For a single direction way, it will be tagged `turn:lanes=left|left;through` while for a bidirectional way it will be tagged `turn:lanes:forward/turn:lanes:backward=left|left|through` depending upon OpenStreetMap way direction* + +There are three turn lanes tags in OpenStreetMap: + +``` xml +turn:lanes=* +turn:lanes:forward=* +turn:lanes:backward=* +``` + +Turn lanes can be mapped from high-resolution satellite imagery sources and street level photos. An example of the high density turn lane area in OpenStreetMap is [Los Angeles](https://www.openstreetmap.org/#map=11/33.9883/-118.3303). This [overpass query](http://overpass-turbo.eu/s/ipk) can be used to extract turn lanes data from OpenStreetMap + +[Mapping guide for mapping turn lanes](../adding-turn-lanes/): This is a detailed mapping guide for adding turn lanes in general with specific focus on the US. It will be updated as more and more countries are mapped for lane information in OpenStreetMap. + + +-- + +The other important attributes in besides `turn:lanes` and `exit/destination` data required to provide the better guidance using OpenStreetMap data are: +``` xml +lanes=* +name=* +ref=* +relation:route +``` + +Information for [lanes](http://wiki.openstreetmap.org/wiki/Key:lanes), [highway names](http://wiki.openstreetmap.org/wiki/Highways), [highway ref](http://wiki.openstreetmap.org/wiki/Key:ref) and [relation:route](http://wiki.openstreetmap.org/wiki/Relation:route) can be found in their respective OpenStreetMap wikis. \ No newline at end of file diff --git a/jp/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md b/jp/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md new file mode 100644 index 0000000..621b78d --- /dev/null +++ b/jp/mapping-for-navigation/_posts/0000-01-04-adding-turn-restrictions.md @@ -0,0 +1,251 @@ +--- +title: Adding turn restrictions +--- +## What are turn restrictions? + +A turn restriction at a junction is represented by a [relation](http://wiki.openstreetmap.org/wiki/Relation) that has a set of tags describing the type of turn restriction. Turn restrictions, like `No-left-turn` and `No-U-turn`, regulate traffic flow at intersections and accurately mapping them is critical for calculating valid routes on a map. + +![image](https://cloud.githubusercontent.com/assets/3423533/15504805/5d678d70-21de-11e6-8290-d20db2380d4d.png) + +## Traffic signs to be added + +Refer to the table given below to spot/match the traffic sign in the Mapillary image against the list of traffic signs and it also consists of the OSM tags: + + +Symbol | Description | OSM Tag | Node/Way/Relation | +------ | ----------- | ------- | ----------------- | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a9/MUTCD_R3-27.svg/80px-MUTCD_R3-27.svg.png)| No straight through | restriction=no_straight_on | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/8/8f/MUTCD_R3-1.svg/80px-MUTCD_R3-1.svg.png)| No Right Turn | restriction=no_right_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/MUTCD_R3-2.svg/80px-MUTCD_R3-2.svg.png)| No Left Turn | restriction=no_left_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/2/2b/MUTCD_R3-3.svg/80px-MUTCD_R3-3.svg.png)| No Turns | restriction=only_straight_on | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/d/d1/MUTCD_R3-4.svg/80px-MUTCD_R3-4.svg.png)| No U-turn | restriction=no_u_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | +![](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a1/MUTCD_R3-18.svg/80px-MUTCD_R3-18.svg.png)| No Left or U-turn | restriction=no_left_turn; restriction=no_u_turn | [Relation](http://wiki.openstreetmap.org/wiki/Relation:restriction) | + + _The last two columns of the table enlists the correct tagging convention for adding the traffic data to OpenStreetMap._ + + +## Using OSM Navigation Map + +The [Navigation map](http://mapbox.github.io/osm-navigation-map/) helps us in recognizing the detected signage overlay from Mapillary on the map. These signage are represented using small circles in 3 colours: + +- **Green** - to be validated +- **Blue** - Reviewed and found valid +- **Yellow** - Reviewed and found redundant +- **Red** - Reviewed and found invalid + +When we click on the green circle, the area is automatically opened in JOSM and popup to select the review is opened in the Navigation map. The same can be opened in iD editor by clicking on **Edit Map** button on top right of the popup. Once done with the review, please add your OSM username. + +![](https://cloud.githubusercontent.com/assets/126868/16987647/ffa78c4a-4eaa-11e6-8bfd-b509b20e482b.gif) + + +## Mapping turn restrictions with iD editor + +The new version of iD, the web editor for OpenStreetMap, makes it even simpler to add turn restrictions to OpenStreetMap. + +### Adding Absolute Turn Restriction: +![epl4xsg](https://cloud.githubusercontent.com/assets/17887418/17285386/fe7453f6-57df-11e6-9d1d-e65ba060bc0b.gif) + +### Adding Conditional Turn Restriction: + ![conditional tr](https://cloud.githubusercontent.com/assets/17887418/17285391/055b6240-57e0-11e6-9c9f-16880b5c6cd2.gif) + +#### Mapillary overlay and Traffic Sign Overlay: + Mapillary has an efficient tool in iD that helps in seeing detected restrictions. Here's how you enable it: + + ![traffic overlay mapillary](https://cloud.githubusercontent.com/assets/17887418/17285393/069163a8-57e0-11e6-9564-293d91b276bc.gif) + +#### Pain Points in adding Turn Restrictions in iD editor: +* iD editor provides no way of adding a `no_u_turn` restrictions via way. If there is a via way `no_u_turn`, you have to add it using JOSM editor. + + ![image](https://cloud.githubusercontent.com/assets/17887418/17285567/1a145830-57e1-11e6-8e2f-0581bc16695e.png) + +* In certain cases, adding [no_u_turn turn via node](https://github.com/mapbox/mapping/issues/213#issuecomment-234221535) is also not possible. For such cases, it is better to add it using JOSM. + + +# Mapping turn restrictions with JOSM + +In order to be able to map traffic data easily, there are some plugins that JOSM needs to be configured with: + + - **Plugins to be downloaded**: + - [Mapillary plugin for JOSM](http://blog.mapillary.com/update/2015/06/25/josm-mapillary.html): This plugin allows the user to view mapillary images in JOSM. + - [Turn restrictions plugin for JOSM](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Turnrestrictions): This plugin allows to add turn restrictions to the selected roads with ease. + + ![mapi_plugins](https://cloud.githubusercontent.com/assets/1933377/11438854/cf4768fa-951d-11e5-819a-737d2e03342c.gif) + + - **Map-paint styles to be added**: + - traffic_signs: It displays all the existing traffic signs that have been already mapped on OSM. + + ![mapi_paint](https://cloud.githubusercontent.com/assets/1933377/11442184/3493f780-9539-11e5-985a-ac6a9095dcee.gif) + +## Guide to use the mapillary and turn restriction plugins + + **Using the Mapillary plugin** + + - The Mapillary imagery can be added by clicking on `imagery -> Mapillary` in JOSM. This will add the mapillary layer + over the dataset layer. + - The explanation for how the plugin works can be found [here](http://blog.mapillary.com/update/2015/06/25/josm-mapillary.html). + + **Note**: Every time a new data layer is added, you need to delete the existing **Mapillary layer** and add a new one + +**Using the turn restriction plugin** + - The explanation for how the turn restriction plugin works + can be found [here](http://overpass-turbo.eu/s/gTO). + + +## Start mapping Turn Restrictions + +- This **[Over-pass query](http://overpass-turbo.eu/s/grv)** can be used to get the current count of turn-restrictions present in a city that one is going to work on. This will help us in determining the current state of restrictions and further help in calculating the number of restrictions added by the team. + +**Note:** Change the city name in the above query + +- Use the **[navigation data coverage on OSM](http://mapbox.github.io/osm-navigation-map/#9.56/37.8188/-122.5575) map** to spot the Mapillary signage detections. +- Turn on the `Turn Restrictions`, `Oneways` and `Mapillary Street Photos` layers in the above map +- Click on the turn-restriction traffic symbols detected by Mapillary (which are denoted by green dots on the map) for it to open in JOSM. + + ![navigation](https://cloud.githubusercontent.com/assets/4470913/15466843/26bd5588-20f9-11e6-9eaa-0126e5c83c39.gif) + +- In the Mapillary layer in JOSM, detected traffic signs are represented by a tiny `red triangle` next to the green arrow. Please note that this layer might not be up-to-date. + + ![screen shot 2015-11-27 at 1 41 55 pm](https://cloud.githubusercontent.com/assets/4470913/11436699/1fa70b72-950d-11e5-8e05-9e09013c1f64.png) + +- Probe the previous and next images as well as the satellite imagery data to get a clear idea of the surroundings and then compare them with the existing Mapillary image to find the exact location of the `traffic-sign`. + + ![turn_res](https://cloud.githubusercontent.com/assets/1933377/11443497/a109430c-9543-11e5-8ef9-6907269d6145.gif) + +- Be cautious while adding an `U-turn` via a way in OSM, here is how you add it: + - Select the participating ways + - Go to `Presets -> Relations -> Turn Restrictions` + - Select `no_u_turn` in the `Restriction` field from the drop-down and click on `New Relation` + - In the `Members` section add the respective roles for all the ways enlisted + + + ![u-turn](https://cloud.githubusercontent.com/assets/4470913/15538899/ae22ff9c-229c-11e6-8d82-08b9e18c5540.gif) + + + **Note** + - To get a better idea about the area/road and to see the clear image, always inspect multiple consecutive images. + - With the help of the plugins, look for **traffic restrictions icons** at junctions which are already present on the road/area. + - We should avoid adding `turn restriction` to roads that are leading to one-ways going in the opposite direction, like the example below. It will only result in redundant data: + + ![screen_shot_2015-11-30_at_11_36_26_pm](https://cloud.githubusercontent.com/assets/4470913/11480317/deeac0c6-97bc-11e5-8d0a-852e3ae2f69f.png) + _Here we should avoid adding `turn-restriction` as it will result in redundant data_ + ![screen shot 2016-05-24 at 6 37 06 pm](https://cloud.githubusercontent.com/assets/4470913/15538956/1a068350-229d-11e6-9931-56770c643131.png) + _This situation is a clear indication of a redundant restriction_ + - Add a conditional restrictions when specific conditions are written on the turn-restriction sign-board. + - On certain times of the day. eg. Restriction during peak hours 7AM-10AM + - On a certain day of the year. eg. Restriction on baseball game days only + +## Adding Conditional turn restrictions + +**Special cases** +* [Conditional restrictions](http://wiki.openstreetmap.org/wiki/Conditional_restrictions) during peak hours are common in SF. Tag them as `restriction:conditional=no_left_turn @ (Mo-Sa 07:00-09:00,16:00-18:00)`
![](https://cloud.githubusercontent.com/assets/4470913/14850426/9d4643f8-0c96-11e6-8c0c-dc94887e1613.png) +* Conditional restriction during baseball games. Ignore
+screenshot 2016-04-27 16 51 33 + +* In the case below, we are leaning towards adding this as a regular `restriction` since it applies for all regular personal vehicles. + + ![screenshot 2016-05-02 12 01 18](https://cloud.githubusercontent.com/assets/12103383/14948422/b9f1838a-105d-11e6-9604-2781de0d6d96.png) + +* If you come across the below instance where the restriction is applicable only on `School Days`. Per discussion we will be adding the restriction for `Monday - Friday` + + ![screen shot 2016-05-06 at 2 57 43 pm](https://cloud.githubusercontent.com/assets/1933377/15074787/7c6594d4-13be-11e6-9c01-1d277070960e.png) + +## QA for turn restrictions + +During turn restrictions mapping in various cities, we have come across certain special cases where we need to pay more attention while mapping. These cases are noted down here for your reference. + +---- + +# Be cautious when you come across these turn restrictions + +**1. Restrictions on Red** + +Be careful with interpreting signage and always verify Mapillary signage overlay with the image and the kind of restriction. The image below shows a sign for no free right that Mapillary interpreted as `no-right-turn`. This is NOT a turn restriction. If you are not sure, consult the community before mapping. +
screenshot 2016-04-26 21 39 06 + +A similar restriction found in Canada depicts that **left turn** cannot be taken when the signal is red, otherwise it is permitted to turn left. We are **not** adding such turn restrictions. + +![no_right_turn_on_red_sign](https://cloud.githubusercontent.com/assets/4470913/17021102/28acf658-4f63-11e6-8266-b380071706c4.jpeg) +_Picture by Share Bear - Own work - [Public Domain](https://commons.wikimedia.org/w/index.php?curid=8626974)_ + +**2. Location and bearing of Mapillary Signage overlay** + +The location and bearing of the Mapillary photo is not reliable and is prone to usual GPS errors. Cross check the photograph with the map to confirm you are looking at the intersection from the correct bearing. This photograph is facing the reverse of actual heading. +
screenshot 2016-04-27 12 28 12 + +**3. Single restriction per image detection** + +Mapillary will detect only one sign type per image. Lookout for multiple restrictions in the image
+screenshot 2016-04-27 17 49 34 + +**4. Careful with Turn restrictions plugin in JOSM** + +Sometimes the **Turn restrictions plugin** does not detect the correct signs i.e. even though it's a `no-right-turn`, the plugin detects it as `no-left-turn`. So be extra sure before adding the restriction +![turn_restrictions_plugin_bug](https://cloud.githubusercontent.com/assets/4470913/15529626/4f438044-226c-11e6-919e-02481acb5ad1.gif) + +**5. Advantage of previous/next images** + +There might be an offset in the Mapillary images, that is the image may appear after/before the actual location. It is ideal to inspect the previous and next images and also look for road names and other clues from the satellite imagery to verify it's exact location and bearing. +![offset_mapillary](https://cloud.githubusercontent.com/assets/4470913/15539155/712f0296-229e-11e6-8675-fecc95f4be51.png) + +**6. Temporary turn restrictions** + +When the roads are in construction or under repair, you might see temporary turn restrictions placed similar to shown in the below image. We are not adding temporary turn restrictions. +![pjimage](https://cloud.githubusercontent.com/assets/8921295/17290390/d8808ac2-57fb-11e6-8816-d681033e2a8f.jpg) + + + +**7. Restriction-ahead warnings** + +In the below image, there is a no_left_turn sign board as detected from the Mapillary image. This sign board means that there is a ```no_turn_restriction``` ahead. But this signage itself is **not** a turn restriction, so we do not map this. +[![screenshot 2016-07-26 15 31 15](https://cloud.githubusercontent.com/assets/8921295/17133998/03bf2e10-5346-11e6-949f-dcd4f554560b.png)](https://cloud.githubusercontent.com/assets/8921295/17133964/e83159fc-5345-11e6-935a-5b535390f730.jpg) + + +# Different conventions for turn restrictions in different countries + +### Canada + +**Case:1** + +The image below shows two signages, the first one is in French and translates to 'Wait for arrow to turn left' and the second one is a `no_u_turn`. In such cases, we ignore the the first signage and go ahead mapping `no_u_turn`. + +[![screenshot 2016-07-26 14 34 36](https://cloud.githubusercontent.com/assets/8921295/17132558/efc2a398-533f-11e6-93d7-7dc0e87978ae.png)](https://d1cuyjsrcm0gby.cloudfront.net/4ZA3OT0nHoDQ7F7JILG-pg/thumb-2048.jpg) + + +**Case:2** + + +In the below image, the first board for ```no_left_turn``` says Monday to Friday 8am-10am and 3pm-7pm (Lun-Ven 8h-10h,15h-19h in French). The second board is a ```no_u_turn``` **except authorized vehicles**. In this case, first one would be a conditional turn restriction; second, an absolute ```no_u_turn``` turn restriction. + +[![screenshot 2016-07-26 14 48 15](https://cloud.githubusercontent.com/assets/8921295/17132580/093ab860-5340-11e6-9863-ffe150f7c8c8.png)](https://d1cuyjsrcm0gby.cloudfront.net/IYi6WjwOQDnPW1HTTGyh8A/thumb-2048.jpg) + +**Case:3** + +The below image indicates that all the drivers (no matter the lane they are on) must follow this/these direction(s) at the intersection. This means that the driver needs to only turn right/left on the days mentioned in the sign and during that duration of the day. + +![image](https://cloud.githubusercontent.com/assets/3423533/17128539/0b5166e0-532b-11e6-96e6-69d21603f183.png) + +**Syntax to be used:** `restriction:conditional=only_right_turn @ (Mo-Fr 07:00-09:00,16:00-18:00)` + +### Germany + +In Germany, instead of signages to prohibit turns, the signages describe the legally allowed turns at the junction. Hence a signage for a no right turn will indicate only turns for left and straight. + +![screen shot 2016-08-17 at 4 12 05 pm](https://cloud.githubusercontent.com/assets/11845908/17733853/568ce2b6-6496-11e6-8665-8983fe1c94db.png) + +_An example of a `restriction=no_right_turn` traffic sign in Germany_ + +### Turn restriction signs of Germany and what it means: + +![screen shot 2016-08-17 at 4 27 33 pm](https://cloud.githubusercontent.com/assets/11845908/17734070/a6125f5e-6497-11e6-8d70-d55248e938ec.png) + +*Courtesy: [German wiki](http://wiki.openstreetmap.org/wiki/DE:Relation:restriction)* + + +**Reference** + +- OSM tags for routing http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing +- Turn restrictions http://wiki.openstreetmap.org/wiki/Relation:restriction +- Access restrictions http://wiki.openstreetmap.org/wiki/Key:access +- Conditional restrictions http://wiki.openstreetmap.org/wiki/Conditional_restrictions + +**Spanish version [here](https://github.com/mapbox/mapping/wiki/Gu%C3%ADa-de-mapeo-para-a%C3%B1adir-restricciones-de-giro-utilizando-mapillary)!** \ No newline at end of file diff --git a/jp/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md b/jp/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md new file mode 100644 index 0000000..1a62fe6 --- /dev/null +++ b/jp/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md @@ -0,0 +1,135 @@ +--- +title: Adding exit and destination signs +--- + +![5138660996_1957ee06ed_o](https://cloud.githubusercontent.com/assets/17887418/15180552/ec541b64-179f-11e6-88d7-4b3074f161e4.jpg) + +## What are exit numbers? + * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. + + ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) + +### Different tags for exit numbers: +* `ref=*` is used when the exit has a specific number assigned to it. +* `noref=yes` is used when the exit doesn't have any official number assigned to it. + +## How to add exit numbers? + +* Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. + +* Select the assigned highway from the dropdown and click on the `download` button. + + ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) + +### Verify the exits on the route for missing information + +* Load the route in JOSM + +![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) + + ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) + + * Browse along the route and check the ways on both directions at every exit location for the following: + - There is a `motorway_junction` at the start of every `motorway_link` exiting the highway + - The `motorway_junction` has a correct exit number `ref` value as per the source. + - The exit number on both directions are the same + - There is only one exit in a direction for every exit number + +**Add missing exit numbers** + +* Download the data and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) around the blue marker in the imagery. + +* Use a combination of Mapillary, Department of Transportation (DoT) documents and Wikipedia to add the `ref=*` tag on `highway=motorway_junction` (stick to using Mapillary and DoT doc as primary source and move to others in case of unavailability of information) + +* If it is confirmed there is no exit number for the `motorway_junction` add another tag `noref=yes` to indicate the exit does not have an official reference number. + + + +## Analyzing signboards in mapillary + +Look out of Highway sign boards on imagery. They may look something like this- + +![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) + +Places to look for- +- near a `motorway_junction` +- near **start** of a `motorway_link` + +![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) + + + +### Do's and don'ts +- It is not necessary that exit numbers are sequential. It might find 45 after 41. +- There are some `motorway_junction` which don't have any associated exit number. Add `noref=yes` on these nodes. +![no ref](https://cloud.githubusercontent.com/assets/17470597/15071466/65aff514-13a9-11e6-9392-3677c8b193a0.jpg) + +- If there are multiple exits on the same [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) then you can tag them as `ref=* ; *` instead of `ref:left=*` and `ref:right=*` until you are confirmed with that. + +- In the case of discrepancy between mapillary and DoT document, look out for the recent change in exit numbers on the web. Many states changes/in a process to change the exit numbers. +- **Ignore the `highway=motorway_junction` where the traffic flow is towards the motorway** + + +## What are destination tags? + +* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. +* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. + +![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) + +### Different tags for destinations: +* `destination` tag refers to the place that the way exiting from the freeway leads to. +* `destination:ref` is the reference of the roads directly ahead. +* `destination:ref:to` is to specify the reference of a major highway ahead. +* `destination:street` refers to the main street the way exiting from the freeway leads to. + +## How to add destination tags? + +### Assign a highway and use Checkautopista2 to map features + +1. Open the destination reference document for your assigned city area. Pick a highway to check and assign it on the spreadsheet to avoid conflict. + +2. Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. + +3. Select the assigned highway from the dropdown and click on the `download` button. + + ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) + + +4. Look out for red outer circle for missing destination. Use `open in JOSM` button to open the node in JOSM. Orange outer circle represents `exit_to` tag and we don't need to add destination tags in the way. Green outer circle represent that the concern way already has destination tag. + + + ![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) + + ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) + + +5. Download the data around the `motorway_junction` and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs). + +7. Use combination Mapillary images, DoT documents, and Wikipedia to add destination as `destination=*` on `motorway_link` ways and the destination highway as `destination:ref=*`. + **Below is a an example** + ![screen shot 2016-03-14 at 6 28 27 pm](https://cloud.githubusercontent.com/assets/12744420/13745188/a12098bc-ea12-11e5-8ffc-9fb839ed5aa2.png) + **On the `highway=motorway_link`(represented by red line) add `destination=Daly City` and `destination:ref=I 280 South`. This can be confirmed with [DoT document](http://www.dot.ca.gov/hq/traffops/engineering/calnexus/pdf/101.pdf) and [wikipedia](https://en.wikipedia.org/wiki/U.S._Route_101_in_California) while searching for exit number 431** + +8. Add any highway missing in the highway spreadsheet. Mark the highway done if all destination tags are mapped/review + + + +## Analyzing signboards in mapillary + +Look out of Highway sign boards on imagery. They may look something like this- + +![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) + +Places to look for- +- near a `motorway_junction` +- near **start** of a `motorway_link` + +![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) + + + +### Do's and don'ts +- Use `;` to separate multiple destination and refs. +- Read more on [Highway intersection](https://en.wikipedia.org/wiki/Interchange_(road)) to understand them better. + diff --git a/jp/mapping-for-navigation/_posts/0000-01-06-adding-turn-lanes.md b/jp/mapping-for-navigation/_posts/0000-01-06-adding-turn-lanes.md new file mode 100644 index 0000000..24c5b7d --- /dev/null +++ b/jp/mapping-for-navigation/_posts/0000-01-06-adding-turn-lanes.md @@ -0,0 +1,247 @@ +--- +title: Adding turn lanes +--- + +## What is a turn lane + +A turn lane is an auxiliary lane demarcated on the road to specify directions to ongoing vehicles. +Turn lanes serve two purposes: + * Provide directional information to the ongoing vehicles and + * Provide the lane information to be chosen for the vehicles changing their direction + +### Types of turn lanes + +There are a total of 12 different turn lanes demarcated on the roads. They are: + +Turn Lane | Representation +--- | --- +turn:lanes = left | ![left](https://cloud.githubusercontent.com/assets/8401827/13217928/1d2fc24e-d98c-11e5-9d20-c526fe6e7f01.jpg) +turn:lanes = right | ![right](https://cloud.githubusercontent.com/assets/8401827/13217945/424f36e0-d98c-11e5-99e7-9d178f2529a1.jpg) +turn:lanes = through | ![through](https://cloud.githubusercontent.com/assets/8401827/13214156/f885d4b4-d973-11e5-9fb7-e9ecb70a932b.jpg) +turn:lanes = left;through | ![through left](https://cloud.githubusercontent.com/assets/8401827/13217986/80786072-d98c-11e5-99c6-db8665977550.png) +turn:lanes = right;through | ![through_right](https://cloud.githubusercontent.com/assets/8401827/13218022/b8aa9352-d98c-11e5-87c2-d8c17ee68305.jpg) +turn:lanes = left;through;right | ![leftthroughright](https://cloud.githubusercontent.com/assets/8401827/13218061/027e10ee-d98d-11e5-9747-c6867e0787b0.JPG) +turn:lanes = left;right | ![left_right](https://cloud.githubusercontent.com/assets/8401827/13217579/8f833c66-d989-11e5-9b2c-dc98fdff09b2.png) +turn:lanes = slight_left | ![slightleft](https://cloud.githubusercontent.com/assets/8401827/13218207/e450feaa-d98d-11e5-938c-a3956de2f7ba.png) +turn:lanes = slight_right | ![slightright](https://cloud.githubusercontent.com/assets/8401827/13218219/07052b56-d98e-11e5-8fc0-82b945fb95c6.png) +turn:lanes = merge_to_left | ![merge to left](https://cloud.githubusercontent.com/assets/8401827/13218244/2ca1fd6c-d98e-11e5-8be9-cb64271f5991.png) +turn:lanes = merge_to_right | ![fahrbahn_2](https://cloud.githubusercontent.com/assets/8401827/13218183/bc5d0790-d98d-11e5-9781-307f80cc0732.png) +turn:lanes:bothways = * | ![turn lanes both ways](https://cloud.githubusercontent.com/assets/8401827/13217721/a2594d48-d98a-11e5-87f1-11e11ebf57ec.png) + + ![](http://pdd.ua/r/r/EEB7A996-D8DC-40FC-87EA-01F3E115BC7C/m_1.18_4.jpg) + _road markings on the ground_ - © [pdd.ua](http://pdd.ua/ua/34/1.18/) + +### Pre-requirements for mapping a turn lane in JOSM + +Before mapping turn lanes activate the following preferences in JOSM to visualize the mapped turn lanes: `preferences > Map Settings` +* *`Map Paint Styles > Lane and road attributes`* + + ![lane_and_road_attributes](https://cloud.githubusercontent.com/assets/13744156/13218788/c55fab96-d991-11e5-89b2-b281986d704e.gif) + +* *`Tagging Presets > lane attributes`* + + ![tagging_presets](https://cloud.githubusercontent.com/assets/13744156/13218902/ad15c902-d992-11e5-872b-1bde24f27f5b.gif) + +* Filter out non-road features with inverse filter: `boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:` + +**Plugins** + +* Knife-tool: https://gist.github.com/jothirnadh/a10daeaef1498537ea56f0a65f7fdbc2 +* TurnLanes-tagging plugin: `JOSM Preferences > Plugins > turnlanes-tagging` + +### Mapping a turn lane + +* Check all roads in the imagery for turn lanes at junction points + + ![roads_markings](https://cloud.githubusercontent.com/assets/126868/11710074/b58b52e4-9f42-11e5-971a-000a699a0b6d.png) + +* Split the road into segments based on the total number of lanes for the segment. The easiest way for splitting the road is by using [Knife_tool](https://gist.github.com/jothirnadh/a10daeaef1498537ea56f0a65f7fdbc2) + + ![residential_road](https://cloud.githubusercontent.com/assets/369696/13223732/34cf7ffa-d98e-11e5-9a33-8f40f6498004.png) + +* For each road segment tag the turn lanes based on the road markings in the direction of the way. Eg. `turn:lanes=left|left;through|through`. Check [OSM turn:lanes](http://wiki.openstreetmap.org/wiki/Key:turn:lanes) for reference. + + ![oneway_turn:lanes_tagging](https://cloud.githubusercontent.com/assets/8401827/13252110/a6bdea8a-da5a-11e5-8c79-aa15c0c15f68.gif) + +* For bi-directional segments, use `turn:lanes:backward=` and `turn:lanes:forward=` to specify turn lanes in each direction. + + ![bidirectional_tagging](https://cloud.githubusercontent.com/assets/13744156/13219545/acd78f62-d996-11e5-85eb-3e05a7b79d3b.gif) + +* Verify correct tagging using the `Lane attributes` style + + ![lane_attributes](https://cloud.githubusercontent.com/assets/8401827/13251884/ddcbdd54-da58-11e5-86ae-c4a2918c9577.gif) + +* The simplest way to add turn lanes is by using **[turnlanes-tagging plugin](https://www.mapbox.com/blog/turnlanes-tagging/)** + +![turnlenes](https://cloud.githubusercontent.com/assets/8401827/17246767/d086ef48-55ab-11e6-8bce-46c434cb9005.gif) + +### `turn:lanes` and relations + +We use [relations](http://wiki.openstreetmap.org/wiki/Relation) for different purpose – for indicating [turn restriction](http://wiki.openstreetmap.org/wiki/Relation:restriction) or collect separate ways into solid [route](http://wiki.openstreetmap.org/wiki/Relation:route). +​ +JOSM help us to handle them. But sometimes we are faced with not properly denoted relations. JOSM will inform about it while uploading our changes. You may [ignore messages of level "Warnings"](https://github.com/mapbox/mapping/issues/153#issuecomment-185679507) (if you only split ways and didn't edit relations manually) but you have to fix all "Errors". + +## QA for turn lanes mapping + +While mapping turn lanes, there are a lot of scenarios are encountered in [#153](https://github.com/mapbox/mapping/issues/153) and [#144](https://github.com/mapbox/mapping/issues/144) mapping repos. All these scenarios are drafted in one place for validation purposes. + +## Different scenarios we came across while mapping + +### 1. Parking lanes + +In the U.S., when parallel parking spaces are marked, they are marked in one of [three ways](http://mutcd.fhwa.dot.gov/htm/2009/part3/fig3b_21_longdesc.htm): + + ![parking_lanes](https://cloud.githubusercontent.com/assets/8401827/13172245/326a7bb6-d71d-11e5-8617-a2516f75144b.png) + +Here’s an example of the box marking style: + + [![boxes](https://upload.wikimedia.org/wikipedia/commons/thumb/0/03/J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG/320px-J.S._Shingler_Bldg_%28East_face%29%2C_McLendon_St%2C_Ashburn.JPG)](https://commons.wikimedia.org/wiki/File:J.S._Shingler_Bldg_%28East_face%29,_McLendon_St,_Ashburn.JPG) + +### 2. Counting number of turn lanes + +If there are no clear cut demarcations on the road and yet cars are parked on either sides of the road, consider them as drive lanes. Case below: + + ![number_of_lanes](https://cloud.githubusercontent.com/assets/8401827/13142482/5b26d0a0-d663-11e5-90cd-4a65d75e7248.png) + +### 3. Starting a turn lane + + Turn lanes should begin exactly as per the marking in the imagery, not before or after. + + ![turn:lanes_start](https://cloud.githubusercontent.com/assets/8401827/13110125/0fe83ad0-d5a4-11e5-82ff-00245d0ba043.png) + +### 4. Ending a turn lane + +Turn lanes should terminate at the first highway junction after the start of the turn lane. + + ![turn:lanes_end](https://cloud.githubusercontent.com/assets/8401827/13143057/4ff2b3c6-d667-11e5-8069-b028fabf7587.png) + +### 5. Turn lane forward + +In case of bi-directional ways, the key [turn:lanes:forward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the same direction as the osm-way; while adding this we must view the road in the direction to the osm-way(**on the direction where the osm-way arrow is pointing**). + + ![turn:lanes:forward](https://cloud.githubusercontent.com/assets/8401827/13175904/c5c922fc-d733-11e5-91b1-c0f9e5181fda.gif) + +### 6. Turn lane backward + +In case of bi-directional ways, the key [turn:lanes:backward=*](http://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right) describes only the turning indications on the lanes in the opposite direction as the osm-way; while adding this we must view the road in the oppoiste direction to the osm-way(**opposite to direction where the osm-way arrow is pointing**). + + ![turn:lanes:backward](https://cloud.githubusercontent.com/assets/13744156/13172709/859957c4-d71f-11e5-8cd9-ea154ad5d2e8.gif) + + *Adding a `turn:lanes:backward` tag* + +### 7. Adding dual carriageways: + +When finding roads mapped as single carriageway while the imagery shows clear separation between roads, split the road where the physical separation starts and add dual carriageways. + +![dualcarriageway](https://cloud.githubusercontent.com/assets/8401827/13393542/117b59aa-df08-11e5-8fd3-21a931531f84.png) + + +**When to add dual carriageway?** +- Add Dual-carriage when + - you see physical separation betweens roads + - **no relation is attached to the way.** +- Add `turn:lanes` tag to both the ways. + + +### 8. Bicycle lanes and road shoulders + +Road shoulders and bicycle lanes are ignored from the lane count. Both these roads are `lanes=2` + + ![bicycle+shoulders](https://cloud.githubusercontent.com/assets/126868/11715007/628dd90a-9f64-11e5-9e22-58614d2afbf6.png) + + ![bicycle_lanes](https://cloud.githubusercontent.com/assets/13744156/13172922/adc69f08-d720-11e5-8600-7a606d2e9bae.png) + + *lanes=3 for the above example, ignoring the two cycle ways* + +* Ignore bicycle lanes even though they are in the middle;example below: + + ![xyz2](https://cloud.githubusercontent.com/assets/8401827/13495220/79a65aca-e16f-11e5-83e7-24d3e4f53ad0.png) + + *The middle way is also a bicycle lane which is not counted while adding the `lanes` tag* + +* Additionally, `Strava global-heat cycle` layer can used to verify if a particular lane is a cycle-way. +`tms[16]:http://globalheat.strava.com/tiles/cycling/color3/{zoom}/{x}/{y}.png` + +### 9. Lane marked as a separate way + +Do not add turn lanes in these cases where the only turn lane is already a mapped as a separate way. + + ![lane_as_separate_way](https://cloud.githubusercontent.com/assets/13744156/13173428/6694c468-d723-11e5-96be-b95502b9f58a.png) + +### 10. Bidirectional turn lanes + +These are the lanes marked with symbol representing both directions at a time. + + ![turn:lanes:both_ways](https://cloud.githubusercontent.com/assets/8401827/12642951/0162ff9c-c5df-11e5-8a14-a41f263ae086.png) + +Tag used for such lanes are `turn:lanes:both_ways=*` + +Yellow lines on both sides of a lane also gives an indication of `turn:lanes:both_ways=*` + +![screen shot 2016-05-16 at 4 12 49 pm](https://cloud.githubusercontent.com/assets/1933377/15287587/8dd24396-1b81-11e6-8527-b84814804175.png) + +![screen shot 2016-05-16 at 4 13 00 pm](https://cloud.githubusercontent.com/assets/1933377/15287591/9165c50a-1b81-11e6-9521-93cea4b7be16.png) +### 11. Mapillary Plugin to verify turn lanes + +The imagery at some places is not very clear and at-times the turn-lanes are covered by cars. In situations like these `Mapillary plugin` can be used. If there is Mapillary imagery coverage in that area, they can used to verify the presence of turn-lanes. + +**Name of the plugin:** Mapillary + + ![turnlanes_mapillary](https://cloud.githubusercontent.com/assets/4470913/12884912/6b405d1e-ce87-11e5-8d0f-cd8a8a8b3dfd.gif) + +### 12. Lanes with restricted access + +These are the areas on streets which are restricted for vehicular traffic. + +![screen shot 2016-03-15 at 3 36 36 pm](https://cloud.githubusercontent.com/assets/8401827/13776503/84c34002-ead0-11e5-911d-0581fe9173b7.png) + +![screen shot 2016-03-14 at 4 46 03 pm](https://cloud.githubusercontent.com/assets/8401827/13776504/84e64138-ead0-11e5-81f0-7918311ec6dc.png) + +![screen shot 2016-03-14 at 4 46 29 pm](https://cloud.githubusercontent.com/assets/8401827/13776505/84e71888-ead0-11e5-9135-553c11d99d12.png) + +In the above cases the areas with markings on the roads are not considered as a lane + +### 13. Reverse direction turn lanes + +These are the lanes specifically categorized to take U-turn or reverse-turn. + +![screen shot 2016-03-14 at 2 25 28 pm](https://cloud.githubusercontent.com/assets/8401827/13776502/84944b6c-ead0-11e5-92fa-0bb2951760ef.png) + +### 14. The order of the directions and valid combinations of values + + - `none` itself is valid value but **not** in conjunction with other + + - ✅ `turn:lanes=none|right` is equal to `turn:lanes=|right` - we use `none` for "_better readability_" + + - 👎 `turn:lanes=left||none|merge_to_right` - this combination of values is valid but there is mixing `none` and `||` (empty) - this is not good choice. + + - 👍 `turn:lanes=left|none|none|merge_to_right` or `turn:lanes=left|||merge_to_right` + + - ❎ `turn:lanes=none|none|none` or `turn:lanes=||` - in this case `turn:lanes=*` tag is redundant, just specify `lanes=3` or real number of lanes + + - ❎ `turn:lanes=none|none;slight_right` - isn't valid combination - "_there are no turn indications_" on the rightmost lane. Instead, must be used (based on https://github.com/mapbox/mapping/issues/180#issuecomment-225574666) + +``` +lanes=2 +turn:lanes=none|through;slight_right +transit:lanes=continue|new_on_right +``` + +- using `*right` | `*left` values + + - ✅ `turn:lanes=left|none|none` or `turn:lanes=||right` or `turn:lanes=merge_to_right||` or `turn:lanes=left|left;through|none|slight_right|right|right`- 👍 + + - ❎ `turn:lanes=|right|left|` or `turn:lanes=none|right|left|through` or `turn:lanes=none|left|none`- 👎 lanes that go in one direction should not cross with each other + +- using `reverse` value + + - `reverse` (u-turn) have to be on the leftmost lane for right-hand traffic or on the rightmost lane for right-hand + +### 15. + +_to be continued …_ + +### Further reading: +* [Mapping turn lanes: OSM wiki](http://wiki.openstreetmap.org/wiki/Key:turn) +* [Mapping turn lanes in OpenStreetMap by Andrey Golovin](https://www.mapbox.com/blog/turn-lanes-mapping/) +* Diary post by @Andygol : [Mapping turn lanes in OpenStreetMap](http://www.openstreetmap.org/user/andygol/diary/35489#) diff --git a/jp/mapping-for-navigation/_posts/0000-01-07-resources-and-references.md b/jp/mapping-for-navigation/_posts/0000-01-07-resources-and-references.md new file mode 100644 index 0000000..1c9eed5 --- /dev/null +++ b/jp/mapping-for-navigation/_posts/0000-01-07-resources-and-references.md @@ -0,0 +1,49 @@ +--- +title: Resources and References +--- + +**Mapbox navigation mapping projects** + +Navigation mapping forms a large part of Mapbox's mapping sprints in recent times. Given below are a few examples of some of the latest navigation mapping efforts across US, Canada, and Europe. To get an idea about all our historical mapping projects related to navigation in OSM, look into the [mapping repository](https://github.com/mapbox/mapping/issues). Our mapping projects are conducted in the open with active participation, feedback, and validation from the community. + +#### Examples + +Location | Description|Start|End(ETA)|Validation +---|---|---|---|---| +[Mapping turn lanes in 30 US cities](https://github.com/mapbox/mapping/issues/180)| Mapping all the turn lanes from satellite imagery in 30 US cities from secondary and above|04/05/2016|Continuing|Continuing +[Updating turn restrictions in Germany](https://github.com/mapbox/mapping/issues/226)| Updating missing turn restriction coverage in 3 german cities: Berlin, Stuttgart, Wolfsburg|29/08/2016|Continuing|Continuing +[Mapping turn restrictions in Canada](https://github.com/mapbox/mapping/issues/213)|Mapping turn restrictions from mapillary in top 5 cities in Canada|22/07/2016|05/08/2016|Completed +[Exit and destination mapping in Canada](https://github.com/mapbox/mapping/issues/220)|Map the exit and destination numbers in top 5 Canada cities using mapillary|11/08/2016|17/08/2016|Completed + +**Navigation data tools** + +* [OpenStreetMap navigation map](http://mapbox.github.io/osm-navigation-map/#11.63/37.7896/-122.4363): This map is used to add turn restrictions in OSM. It has a detected signage mapillary layer for easy detection of turn restrictions, oneways and a dataset which displays all the valid, invalid and redundant turn restrictions added. Get more [instructions](https://github.com/mapbox/osm-navigation-map/blob/gh-pages/MAPPING.md) on `how to use the OSM navigation map`. +* [CheckAutopista2](http://k1wiosm.github.io/checkautopista2/): It is a tool to investigate and add highway signboard features on motorways and freeways. For more details look into the [github repository](https://github.com/k1wiosm/checkautopista2) for `checkautopista`. +* [Overpass](https://overpass-turbo.eu/): The place to query and extract all OSM data related to a specific feature. It has a simple query builder feature that helps in querying each and every feature in OSM. Details about [overpass](http://wiki.openstreetmap.org/wiki/Overpass_turbo) can be found [here](http://wiki.openstreetmap.org/wiki/Overpass_API) and [here](http://wiki.openstreetmap.org/wiki/Overpass_API/Language_Guide). +* [Knife tool](https://www.mapbox.com/blog/knife-tool/): The knife tool can be used for quick splitting of ways while adding navigation features such as turn lanes. For more details, look [here](https://github.com/mapbox/auto-tools/tree/split) +* [Turn lanes tagging plugin](https://www.mapbox.com/blog/turnlanes-tagging/): With this plugin, you can add complex tag combinations for turn lanes at road junctions with ease, and minimize errors. For more details, look [here](https://github.com/JOSM/turnlanes-tagging) + + + +**Country specific navigation guide** + - Images of traffic signs and road markings : Traffic signs and road markings may undergo small changes and specific cases when mapping turn restrictions using Mapillary. There are subtle differences in turn restrictions between Canada, US, and Germany. *(This section is to be kept updated with new signages every time mapping is done in a separate country with new conventions)* + +1. **[Turn restriction images in US](https://gist.github.com/abhisheksaikia/7c9329a985816c128aabcba092747816)** + +2. **[Turn restrictions images in Germany](https://gist.github.com/abhisheksaikia/646b918fc64f9d8109b5d62a8137e86a)** + +3. **[Turn restrictions in Canada](https://gist.github.com/abhisheksaikia/bcfbf4ea0dc1e100337244867b2524fc)** + +4. **[Turn restrictions in France](https://gist.github.com/jothirnadh/3d0245816dabbf395c447130877c538c)** + + +For more details on cases for turn restrictions and signages in different countries take a look at [QA for mapping turn restrictions](https://gist.github.com/abhisheksaikia/6e12973daa5be78da3ef9ba6d21b8562) + +**Data sources and references for navigation data** + +* [Mapillary](https://www.mapillary.com/) + +* [OpenStreetView](http://openstreetview.org/map/) +- **DOT documents/websites**: Local official websites, documents released by local `Department of Transportation` bodies. +- **Wikipedia**: Exit and destination numbers, highways, highway refs. *(must be verified on ground or with official sources)* +- High resolution satellite imagery: Bing, Mapbox, USGS, open satellite datasets ([Landsat](http://landsat.usgs.gov/), [Sentinel2](http://www.esa.int/Our_Activities/Observing_the_Earth/Copernicus/Sentinel-2/Data_products), [LISS](http://bhuvan.nrsc.gov.in/data/download/index.php), government opendata portals). diff --git a/jp/mapping-for-navigation/index.md b/jp/mapping-for-navigation/index.md new file mode 100644 index 0000000..00e5a9c --- /dev/null +++ b/jp/mapping-for-navigation/index.md @@ -0,0 +1,10 @@ +--- +title: Mapping for navigation +layout: category +order: 6 +color: orange +description: Learn the guidelines to map different components to help build a great navigational engine. +image: mapping-to-improve-navigation.svg +--- + +This guide was designed to help anyone add navigation features in OpenStreetMap from scratch. Let's dive in: diff --git a/jp/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md b/jp/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md new file mode 100644 index 0000000..fe95a49 --- /dev/null +++ b/jp/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md @@ -0,0 +1,210 @@ +--- +title: Mapping with JOSM +--- + +This guide will get you started [mapping with the Java OpenStreetMap editor (JOSM)](https://www.mapbox.com/blog/making-the-most-josm/) - a powerful and popular desktop editor for OpenStreetMap. Another popular editor is [iD](https://www.mapbox.com/blog/new-map-editor-launches-openstreetmap/), commonly used for short and simple, browser based editing sessions. Note that this section only focuses on the mechanics of editing with JOSM. + +## Downloading from OpenStreetMap + +To start editing, download an area from OpenStreetMap by using the green down-arrow button on the left in the menu bar. + +## Using imagery + +You will routinely use imagery for mapping. JOSM comes with a variety of pre-configured satellite imagery layers - the Bing and Mapbox layers being the most popular ones. Bing and Mapbox may have different levels of detail and clarity in different places, so often worth checking both. Simply select one of them from the imagery menu and you're ready to go. + +![](https://s3.amazonaws.com/f.cl.ly/items/0E463a191T1R182t0o09/imagery.gif) + +When using imagery, keep in mind that imagery may be offset. That is, due to complexities in processing satellite imagery, features on imagery may not be at the same location as they are in the real world. For reference, check existing features on the map and compare them with the imagery or download GPS tracks. To download GPS tracks from OpenStreetMap, check the "Raw GPS" box in the download dialog. If you observe an offset in the imagery, you can correct for it by selecting the "New offset" item in the "Imagery" menu. + +## Creating data + +Click the "Draw nodes" button to enter the data creation mode. Subsequent clicks on the map will set nodes connected by a way. Double click to finish drawing the way. For drawing single nodes, simply double click on the map. To draw a closed way, finish a way with a click on the first node you drew. + +![](https://s3.amazonaws.com/f.cl.ly/items/1w3i0p411R2b0s0y1r2R/trace.gif) + +## Modifying data + +Click the "Select" button to select existing nodes or ways. To move nodes or ways click on them, hold the mouse button pressed and drag them. Then release the mouse button where you'd like to drop them. + +![](https://s3.amazonaws.com/f.cl.ly/items/2r3h0m1E262s3j3M191q/edit.gif) + +To delete data, use the `del` key of your keyboard or on a mac, use `fn+delete`. + +If you ever make a mistake, `ctrl+Z`, or `command+Z` on mac, will undo the last change. + +Ways can be connected to each other. In JOSM speak, you can glue, unglue, split and combine them. This is useful to create logical connections, for instance between roads of different type. To prevent ways from connecting when drawing, say when drawing a road close to buildings, hold the `ctrl` key, while clicking the mouse. + +![](https://s3.amazonaws.com/f.cl.ly/items/2p3Y2x461o390V3q1E22/split.gif) + +## Tagging + +You can add, modify or delete tags directly in the tagging panel in JOSM's side bar. If for some reason this panel is not visible, you can enabled it under the "Windows" menu. The example below tags two ways at the same time. Simply hold shift to select multiple objects. + +![screenshot from 2014-11-24 16 15 10](https://s3.amazonaws.com/f.cl.ly/items/0C2X2O3I0l2K0X3G2P00/tagging.gif) + +**Presets** are common tags or tagging combinations that can be applied to objects. They can be found in the "Presets" menu where they are organized into logical categories. Try adding a preset and then review the modifications in the tagging panel. + +![ssasa](https://cloud.githubusercontent.com/assets/1152236/5173525/5bf9022a-73f7-11e4-97b8-89203488adca.png) + +** Copy & pasting tags ** + +You can copy and paste tags from one object to another. Just select one object, copying with `ctr + c`. Then select the other object and paste with `ctrl + shift + v`. This will copy _only tags_ - not the geometry. + +## Uploading to OpenStreetMap + +To upload the data, click on the green up-arrow button on the left in the menu bar. This will automatically trigger *validation*. Review all validation warnings and resolve all errors before you upload. If there are any errors or warnings, do your best to fix them. Before you upload, **add a proper changeset comment and specify what source you used**. This is important as it will show other users who see your changesets what this changeset was intended to modify and from where you took the information. + +The upload will take a few seconds. The data is live on OpenStreetMap immediately. The map usually takes a couple of minutes to clear through all caches. + +![](https://s3.amazonaws.com/f.cl.ly/items/390y0t3A1M2i260F2n0k/upload.gif) + +Once you uploaded the data, you and everyone else can see a corresponding entry on your OpenStreetMap user profile under "My Edits": + +![](https://s3.amazonaws.com/f.cl.ly/items/3T141H1W1b1y1m301T0v/Screen%20Shot%202014-12-16%20at%2011.44.27%20AM.png) + +## Productivity tips + +### Filters + +Filters are very powerful and can speed up your work tremendously. Take a look at the [JOSM filter documentation](https://josm.openstreetmap.de/wiki/Help/Dialog/Filter) and at [AJ's blog post about filters](https://www.mapbox.com/blog/2012-08-15-using-filters-josm/) to learn how they work. + +Here are some of the most common filter selectors in use for editing: + +`boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:` + +### Pull out common highway classifications into toolbar + +When you work on OpenStreetMap, you will use highway classifications a lot, bring them all into the toolbar: + + ![screenshot from 2014-11-24 15 59 41](https://cloud.githubusercontent.com/assets/1152236/5173024/fd25da56-73f2-11e4-805f-ff3a321ca15a.png) + +### Use keyboard shortcuts + +When you're editing, you will be a lot faster using keyboard short cuts. Take a moment to familiarize yourself with them and start using them! You can find keyboard shortcuts in the menus like in the screenshot below, but there's also [a full reference of keyboard shortcuts on the JOSM web site](https://josm.openstreetmap.de/wiki/Shortcuts) ([en español](https://josm.openstreetmap.de/wiki/Es%3AShortcuts)). + +![screenshot from 2014-11-25 22 25 06](https://cloud.githubusercontent.com/assets/1152236/5195894/23afd078-74f2-11e4-9735-640cefcbfe0c.png) + +### Plugins + +There are many JOSM plugins that will help you to map faster. Here are a couple that used most commonly. You find all plugins in the settings panel: + +![](https://s3.amazonaws.com/f.cl.ly/items/3Q2T452P2j0H3t2F1h1b/plugins.gif) + +**Buildings plugin** + +For tracing buildings, always use the buildings plugin. It speeds up editing by creating rectangular boxes with a tag `building=yes` by default. To quickly draw buildings that are aligned to each other, draw the first building, select it, and draw subsequent parallel buildings. + +![](https://s3.amazonaws.com/f.cl.ly/items/0Y2T1s0x0M2t3C24363A/buildings.gif) + +To align existing buildings neatly, you can select multiple buildings, then two extra nodes to set the alignment axis and [orthoganalize shape (keyboard shortcut `q`)](http://josm.openstreetmap.de/wiki/Help/Action/OrthogonalizeShape) + +![3zpk8nxbdt](https://cloud.githubusercontent.com/assets/126868/6900081/d65cf23c-d721-11e4-82f9-7084b11bb41f.gif) + +**turnrestrictions plugin** + +This plugin makes it really easy to add [turn restrictions](http://wiki.openstreetmap.org/wiki/Relation:restriction) such as "no left turn" to roads. + +![edit a new turn restriction in layer data layer 1 2015-12-11 17-02-26](https://cloud.githubusercontent.com/assets/369696/11742854/fb630938-a028-11e5-88cf-c03a6e175abf.png) + +Read more in JOSM help - https://josm.openstreetmap.de/wiki/Help/Plugin/TurnRestrictions + +**Fast draw plugin** + +This plugin is great for tracing areas like forests, lakes, waterways or landuse and linear features like roads. + +To start, press `shift + f`, then click with the mouse to start drawing. Whenever you'd like to set a node, press the space bar. For free hand drawing, keep the space bar or mouse button pressed. + +![untitled](https://cloud.githubusercontent.com/assets/126868/8275787/b1ffb342-18bd-11e5-8262-c2fba62b05b9.gif) + +To delete the latest created nodes, just hit `backspace`. + +To determine how many nodes are set automatically in freehand mode, use the up and down arrow keys. + +To finish drawing, press enter to go into the simplification mode (feature will turn yellow), press the up or down arrow for the desired level of simplification and press enter again to create the way. + +While tracing you can press `Q` to set some preferences for "FastDraw" + +![fastdraw configuration 2015-12-14 22-55-16](https://cloud.githubusercontent.com/assets/369696/11788197/c9ec99d4-a2b5-11e5-9ab7-9c0c3530d963.png) + +*[Video Tutorial](https://www.youtube.com/watch?v=xqDd-Crk3o4)* + +**Utilsplugin2** + +Utilsplugin2 comes with a series of tools that you can all find in the new menu "More tools", after the plugin is installed. The most used one is "Add nodes at Intersections" which gives you a fast way to add nodes at places where ways intersect in the current selection. + +![screenshot from 2014-11-25 17 03 51](https://cloud.githubusercontent.com/assets/1152236/5193091/698be05e-74cb-11e4-8dcb-1a1a228daa07.png) + +*[Video Tutorial](https://www.youtube.com/watch?v=F5NsYpKC6G4)* + +**Notes** + +Notes are a great way to post questions for others on the map. When mapping, observe notes that others left in the area and if you have a specific question or a suggestion on how the map could be improved, consider leaving a note. + +Activate the notes plugin: + +![screenshot from 2014-11-25 16 49 25](https://cloud.githubusercontent.com/assets/1152236/5192168/3f6704c8-74c3-11e4-9c69-d214b95d78cc.png) + +Now you should see a list of notes in the side bar for the area you're mapping in: + +![screenshot from 2014-11-25 16 52 11](https://cloud.githubusercontent.com/assets/1152236/5192216/8abfc5f4-74c3-11e4-8a5d-89bce76c7039.png) + +### Validation + +JOSM automatically validates your data when uploading, but you can run validation at any point by clicking 'Validation' in the Validation panel. + +![](https://s3.amazonaws.com/f.cl.ly/items/2i0I3E3I3m0r3u2F1f2x/validate.gif) + +### Configuring drawing styles + +Sometimes it's useful to tweak drawing stiles to help improve visibility of certain features. + +For example, if you're working with addresses, activate "Address Tags Validator": + +![screenshot from 2014-11-25 15 10 03](https://cloud.githubusercontent.com/assets/1152236/5190603/3fcd89a4-74b5-11e4-8513-62c3747ddb2c.png) + +Or if you'd like to see clearly what you've edited in your session, activate "Modified objects": + +![screenshot from 2014-11-25 15 13 59](https://cloud.githubusercontent.com/assets/1152236/5190658/d136243c-74b5-11e4-9218-092e402179ed.png) + +Try different drawing styles yourself and figure out which ones help you do your work better. + +#### Highlight data freshness + +You can use [this style](https://raw.githubusercontent.com/Andygol/josm-styles/master/recent%20changes_2016.mapcss) to highlight features that are created or modified in 2016. To configure this: + +![](https://cloud.githubusercontent.com/assets/369696/9634340/e596f890-5199-11e5-8335-55d63a9b11d2.gif) + +### Custom imagery + +You can also add custom imagery from Tile Map Service (TMS) or Web Map Service (WMS) endpoints. Here is how: + +- [Adding a TMS imagery endpoint](https://www.youtube.com/watch?v=JvM0aP3vVr0) +`http://{switch:a,b,c}.tile.thunderforest.com/cycle/{zoom}/{x}/{y}.png` +- [Adding a WMS imagery endpoint](https://www.youtube.com/watch?v=VJqVsV0MXpw) `http://www.geosur.info/arcgis/services/maps/GeoSUR_WMS_hidrografia/MapServer/WMSServer` + +### Resolving conflicts + +If you upload a change to OpenStreetMap and someone has changed one of the same features in the meantime, a conflict will occur. In this case OpenStreetMap will refuse your changes. Follow these steps to resolve the conflicts: + +1. Download new data from OpenStreetMap for the area in which the conflict occured. +2. Run validation and review the conflicts. +3. Fix them. +4. Attempt upload again. + +As a last resort, you can attempt to upload changes one by one. This is not recommended though. + +![screenshot from 2014-11-25 16 43 40](https://cloud.githubusercontent.com/assets/1152236/5192070/3e43555c-74c2-11e4-9c7a-87bb52120ddc.png) + +### Scripting JOSM + +You can script JOSM to automate certain workflows. For example: + +- Expand abbreviations (US): https://gist.github.com/Rub21/feb83f57a727ac0d8a34 +- Capitalize names and eliminate "name=S/N": https://gist.github.com/Rub21/47838797856566a8b6ba +- Expand abbreviations (Peru): https://gist.github.com/Rub21/cc055320c925c855926e + +**[Video](https://www.youtube.com/watch?v=Cpi_5dB1NLQ)** + +## Further reading and questions + +For further information, take a look at the [JOSM help](https://josm.openstreetmap.de/wiki/Help). diff --git a/jp/mapping-with-josm/index.md b/jp/mapping-with-josm/index.md new file mode 100644 index 0000000..8a9a973 --- /dev/null +++ b/jp/mapping-with-josm/index.md @@ -0,0 +1,8 @@ +--- +title: Mapping with JOSM +layout: category +order: 4 +color: darkblue +description: Get started mapping with the Java OpenStreetMap editor (JOSM) - a powerful and popular desktop editor for OpenStreetMap. +image: mapping-with-josm.svg +--- diff --git a/jp/osm-data-model/_posts/0000-01-01-osm-data-model.md b/jp/osm-data-model/_posts/0000-01-01-osm-data-model.md new file mode 100644 index 0000000..3fe68eb --- /dev/null +++ b/jp/osm-data-model/_posts/0000-01-01-osm-data-model.md @@ -0,0 +1,65 @@ +--- +title: The OpenStreetMap data model +--- + +In OpenStreetMap, each feature is described as one or more geometries (think for instance of a river's shape) with attached attribute data (think of the river's name). Geometries are described with three different *elements*: *nodes*, *ways* and *relations*. Attributes are described as *tags* that can be part of a node, a way or a relation. + +Nodes are the equivalent of a point, ways are like lines that connect points and relations are collections of points or ways that represent a larger whole. This is easiest to understand with a couple of examples. + +## Nodes + +Nodes are used to represent any kind of point type feature or just to designate a name for a point of interest in the vicinity. Here's a node representing a café: + +![node-example1]({{site.baseurl}}/images/node-example1.png) +and here's one representing New York City: + +![node-example-2]({{site.baseurl}}/images/node-example-2.png) + +## Ways + +A way is a line feature *connecting two or more nodes* - like a road here: + +![way-example-1]({{site.baseurl}}/images/way-example-1.png) + +If you close a way - by connecting its end to its start, you can map area type features like this building here: + +![way-example-2]({{site.baseurl}}/images/way-example-2.png) + +or this park: + +![way-example-3]({{site.baseurl}}/images/way-example-3.png) + +Nodes are usually just the items that define a way. But nodes sitting on a way can have their own significance. In this example the node is part of 14th Street and R Street and it also denotes that there's a traffic light. + + +![way-example-4]({{site.baseurl}}/images/way-example-4.gif) + +## Tags + +Before we hop to the third element next to nodes and ways - relations, let's look at tags. You've seen them now already a couple of times in the examples above, like in this café node: + +![osm-tag]({{site.baseurl}}/images/osm-tag.png) + +Any point type feature is a node. Whether the node designates a café, a school, a fire hydrant, a tree, a park, a mountainpeak is entirely up to how the node is tagged. Any line type feature is a way. Whether the way is a road, a building, a lake, a railway, a cycleway is again, defined by how it is tagged. + +Tags can be on any element: on nodes, ways and relations. + +## Relations + +Relations are used to organize multiple nodes or ways into a larger whole. Take here for instance the bus route 23 running through 3 different ways. + +![relations]({{site.baseurl}}/images/relations.gif) + +The type of relation that you'll probably deal most with describes an area with punched out holes - a so called *multipolygon*. Here is an example of a multipolygon building with a yard. It consists of 2 ways with each multiple nodes. One way describes the *outer* wall of the building, the other one the *inner* wall. The ways are part of a relation of the type `type=multipolygon`, the outer way has the role `outer` and the and the inner way has the role `inner`. Note: the `building=yes` tag is on the relation (not on the way). + +Your OpenStreetMap editor will take care of creating multipolygons for you so don't worry if this seems dense for now. If you need to fix a multipolygon, this is a good section to come back and review. + + +![multipolygon]({{site.baseurl}}/images/multipolygon.gif) + +## Further reading + +To learn more about the OpenStreetMap data structure, take a look at these resources: + +- OpenStreetMap Elements http://wiki.openstreetmap.org/wiki/Elements +- Multipolygons http://wiki.openstreetmap.org/wiki/Relation:multipolygon \ No newline at end of file diff --git a/jp/osm-data-model/index.md b/jp/osm-data-model/index.md new file mode 100644 index 0000000..b0b6ef8 --- /dev/null +++ b/jp/osm-data-model/index.md @@ -0,0 +1,8 @@ +--- +title: The OpenStreetMap data model +layout: category +order: 3 +color: blue-light +description: In OpenStreetMap, each feature is described as one or more geometries with attached attribute data. +image: the-openstreetmap-data-model.svg +--- diff --git a/jp/validating-osm/_posts/0000-01-01-validating-osm.md b/jp/validating-osm/_posts/0000-01-01-validating-osm.md new file mode 100644 index 0000000..1074763 --- /dev/null +++ b/jp/validating-osm/_posts/0000-01-01-validating-osm.md @@ -0,0 +1,247 @@ +--- +title: Validating OpenStreetMap Data +--- + +At Mapbox, we map as well as inspect the data that is coming into OpenStreetMap for quality. This is the definitive guide that we follow - from detecting potentially harmful changes to inspecting them and eventually fixing the map. + +## What is a problematic edit? + +Every change to OpenStreetMap is contained in a [changeset](http://wiki.openstreetmap.org/wiki/Changeset). They consist of either additions (new feature), modifications (change existing tags, feature location, or location of a referred feature) or deletions by a mapper. + +When working with data in OpenStreetMap, you sometimes come across places where another mapper might have added bad features or tags, changed or moved or deleted a large set of data or an important set of tags. Changes that spoil the quality of OpenStreetMap data are considered problematic edits. + +There are several kinds of potentially problematic changes. For example: + +* Use of proprietary data (like Google Maps) to add data in OpenStreetMap. +* Modification to significant tags like `place`, `boundary`, `highway`, etc. +* Undocumented imports. +* Modifications with outdated imagery. +* Unintentional dragging of nodes in way that results in geometry changes. + +Creation and deletion of features, modification to tags and modification to a node's location, result in a `version` increment. Every change by every user is retained as a separate version of the object in the OpenStreetMap database. Changes to nodes within a way, or to members of a relation, result in displayed changes to the way/relation but do *not* increment `version`. + +## Identifying problematic edits. + + * **OSMCha**: Changeset level notification, giving an overview of how many objects were affected in a changeset. A set of suspects words automatically flag some suspicious changes. Custom filters can be used with changeset comment, source, and other combinations to look for suspicious edits. Read more about [using OSMCha to identify and inspect OpenStreetMap data.](#finding-suspicious-map-edits-using-osmcha) + * **Linting** + * **Map Feedback from Mapbox users**: Sometimes we receive notice through [Map feedback](https://www.mapbox.com/map-feedback/) where the Mapbox users report the changes. + * **OSM communication channels.** + +## Investigation + +After identifying potentially problematic data on the map, you will want to determine few things to start: + +* the *user* responsible +* the *time* they made the edit +* what made the changes - the *changeset id* +* the *features edited* + +This information will help us investigate the change and identify the cause and type of change. Let's follow an example of misaligned roads in New York City. + +![screenshot 2016-04-14 12 56 09](https://cloud.githubusercontent.com/assets/3423533/14520241/0c277554-0241-11e6-8695-7a76c9cd0683.png) + +### Inspecting the change + +1. Open the area in `JOSM`. +2. Select the problematic feature, and check the modified object's history using `Ctrl+H`. +3. The History window displays how that selected object was changed over time by different mappers. The display will vary based on the type of object (node/way/relation) selected. The left panel shows the object's versions, modification dates, and responsible users. + - The `Tags` tab of History window has the history of tags changed between versions. + - The `Nodes` tab of History window has the history of addition/deletion/modification of nodes associated with a way's geometry between versions. + - The `Coordinates` tab of history window has the history of the object if its moved for a significant distance. + +![history](https://cloud.githubusercontent.com/assets/3423533/15171329/52dca16a-176b-11e6-8b78-ce3220c62d40.png) + +*JOSM History window* + +In this example, someone moved a node a significant distance. From the JOSM history window, you can see the change was made by user `osm_user_name`, in changeset `38544431`, dated `04/14/2016`. + +### Understand the mapper + +The mapper's OSM user profile and [HDYC](http://hdyc.neis-one.org) profile gives an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. + +Click on the OSM username in the JOSM History window, and load the OSM user page where you can view the user's `Edits` history, any `Active Blocks`, any other details on the user, and `Diary` entries. + +You cal also gauge a mapper's experience by looking at the number of project days, type of mapper and other points in [HDYC](http://hdyc.neis-one.org/). + +![hdyc](https://cloud.githubusercontent.com/assets/3423533/15170921/ee9fbe6a-1767-11e6-8601-e74f7891a88f.png) + +### Investigate the changeset + +Click on the changeset ID in the JOSM History window to open the OpenStreetMap changeset page, and load details on how many objects were added/modified/deleted. You'll also see the changeset comment, which may contain more self-reported details from the user, as well as information on the editor and sources used. + +The OpenStreetMap changeset pages list the objects touched by the user in that particular changeset, but it won't highlight the specific details of changed objects. + +![screenshot 2016-04-14 17 35 26](https://cloud.githubusercontent.com/assets/3423533/14527442/b721eacc-0267-11e6-9fe4-807e6271ccf4.png) + + +This is where [Changeset Map](http://osmlab.github.io/changeset-map/) comes in handy. Changeset Map visualizes all specific features changes made to OpenStreetMap in a changeset. + +- Submit the changeset id to changeset-map to see the changes affected in that changeset. + + `Example`: + +- Changeset Map shows the features added/modified/deleted or touched during the changeset. Identify all the problematic changed objects by exploring the edits. + +![vali](https://cloud.githubusercontent.com/assets/3423533/14984377/f28d4942-115f-11e6-9c28-956faab784a3.gif) + +## Response + +At this point, you know who, when, and which changeset are associated with the problematic change. + +Most bad edits are accidental, and the general strategy to respond to such changes is education. Work to share knowledge with the mapper about the mistake and how they can avoid the mistake in the future. Communicate feedback through public changeset comments, visible to all, or sometimes direct messages if more direct contact is helpful. This helps build our community and improve the quality of future contributions to the map. + +In cases where it is determined that the intent of the mapper was to damage the map, an urgent response may be required by reverting the change and reporting the issue to an OSM administrator or Data Working Group. + +### Communicate + +* Leave a comment on the changeset with a description of what was wrong and how it can be fixed. Link to an OpenStreetMap wiki or link to help material that is relevant. +* If the user does not respond or fix non-urgent issues within a week, alert a nearby active mapper of the issue. +* Also look for help on IRC or the local forums or mailing list of the area. + +### Repair + +* For specific malicious changes, consider fixing the issue (and reporting it immediately). +* For a changeset that is wholly inaccurate, revert it. Send a message to the mapper responsible and ask for a description of what happened. +* For simple issues, communicate with the mapper to discuss on how they can fix it. + +#### Revert using the JOSM Plugin + +The JOSM [Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter) is a convenient way to revert changes in OpenStreetMap. After every revert, make sure you upload the changes by sharing a changeset comment on why you reverted the changeset. + +Reverting changesets can be tricky, and you can unintentionally break things yourself. Attempt to revert a changeset if you are 100% sure that the changeset is bad and if something goes wrong -- you should be able to fix it. + +![revert](https://cloud.githubusercontent.com/assets/3423533/14527229/25b55a52-0266-11e6-847d-b9601f8fae8d.gif) + +*Using the revert plugin* + +### Report + +* For urgent issues that require an experienced response, contact the [Data Working Group](http://wiki.openstreetmap.org/wiki/Data_working_group). + +### How to assess urgency to respond + +The level of response depends on how severe the change is to OpenStreetMap. Urgency is somewhat subjective, but here is some guidance. + +1. Changes to significant features like the following should trigger an immediate repair. + - Major boundaries + - Highway connectivity + - Highway hierarchy + - Highways misalignment (like our NYC example) + - Broken multipolygons (water/border) which effect admin boundaries + - Landmarks + +2. Changes to important but less critical features should start with communication, and repair later only if the user does not respond. + - Land use features like forests + - Buildings + - Water bodies + +3. If the mapper is using the proprietary data sources like Google, Bing Maps, Here Maps or other sources which are not open licensed then comment on the user changeset and mention [Copyright guidance for OpenStreetMap](http://www.openstreetmap.org/copyright). Encourage them to revert the changes and follow local knowledge, or stick to Bing and Mapbox Satellite Imagery. + +## Common Scenarios + +Here are a few common scenarios of bad edits in OpenStreetMap. + +#### Mistakes by inexperienced mappers + +New users are always welcome to edit OpenStreetMap! During their learning process sometimes they may mistakingly attempt to modify/delete major land features like boundaries, important place tags, highways, and relations which can cause faulty data. In cases like this it's good to educate the users by directing them to proper guides, and instructions they need to follow while mapping and encourage them to correct their mistakes. Revert immediately if it's a serious error. + +#### Humanitarian OpenStreetMap Team projects + +Many new mappers join OpenStreetMap during HOT Activation. HOT tasks have custom imagery; the changeset review should be done using them. If data added does not match either imagery or the custom imagery, or added data is not of good quality, comment on user changeset to help improve their edits and mapping skills. + +#### Intentional bad edits + +There are few users who intentionally add bad data to OpenStreetMap which should be reverted immediately. +One such example is shown below. Here the user intentionally added family names to towns, buildings, and footpaths. + +![screenshot 2016-05-03 18 47 00](https://cloud.githubusercontent.com/assets/3423533/14984342/d96fe7ee-115f-11e6-9af5-28ac515d9b28.png) + +#### Undocumented imports + +You can import open datasets into OpenStreetMap. Imports should follow the [Import Guidelines](http://wiki.openstreetmap.org/wiki/Import_guidelines) and add proper documentation to the [Imports catalogue](http://wiki.openstreetmap.org/wiki/Import/Catalogue), and use a dedicated import accounts. If you see any undocumented imports, comment on the changeset to request documentation details. + +#### Automated edits + +Automated edits are changes made to OpenStreetMap with less direct human involvement which involves bots, algorithmic imports, etc. + + +## Finding suspicious map edits using OSMCha + +**[OSM Changeset Analyzer](http://osmcha.mapbox.com/)** or OSMCha is a tool to filter and analyze changesets on OpenStreetMap using the [changeset metadata](https://www.openstreetmap.org/api/0.6/changeset/41775489/download). The tool has a live listing of every changeset on the map, flags potentially suspicious edits and has various filters to find changesets that match certain criteria. + +![screenshot 2016-09-06 16 00 06](https://cloud.githubusercontent.com/assets/8921295/18270541/0de8330c-744b-11e6-8582-7e49d6acec9d.png) +_Latest changesets listed in OSMCha_ + +The changeset is shown with id, date and time of creation, OSM user, creations in green, modification in yellow, deletions in red, a keyword describing if the changeset fits any set behaviors along with a cross mark to signify that the changeset is unreviewed. + +### Filtering changesets + +The filters available in OSMCha allow for a various combination of searches to help find problematic edits. + +![screenshot 2016-08-30 16 37 31](https://cloud.githubusercontent.com/assets/8921295/18086930/1a28da0c-6ed0-11e6-8eed-5a0b7ee6cf72.png) +_OSMCha filter dialog_ + +OSMCha automatically tags changeset with certain parameters like `Mass creations` or `Possible import`. + +![screenshot 2016-08-30 16 48 17](https://cloud.githubusercontent.com/assets/8921295/18087208/932c74c6-6ed1-11e6-8176-d6a1a6bb9f93.png)
+_Filter based on automatic flagging_ + + +### Examining the quality of the changeset + +OSMCha uses [Changeset map](https://github.com/osmlab/changeset-map/) to visually represent the features that were added, modified and deleted along with tag changes. This helps check the quality of the edits for obvious mistakes. + +screenshot 2016-08-22 15 16 17
+_A [changeset](http://osmlab.github.io/changeset-map/#41576998/way/24464264) showing an object that incorrectly made into a circle_ + +### Workflow to find suspicious changes + +#### Suspicious editing behavior + +Inexperienced users, deletions, and imports: + +- [Edits from Maps.me editor](http://osmcha.mapbox.com/?editor__icontains=Maps.Me&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) +- [Mass deletions](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) +- [Mass deletions + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) +- [Mass modifications + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=4) +- [Mass creations + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2)/ [Possible import](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2) + +Strategy for filters: + +1. iD editor is targeted towards simple editing from new users, and any advanced editing happens in JOSM. So, if a mass deletion takes place using iD editor, there is a probability that the user could be inexperienced and the deletions unreasonable. [Example of a harmful changeset.](http://osmcha.mapbox.com/41628531/) +2. Maps.me users tend to be new to OSM. It is suggested to look for changesets that add an unreasonable amount of similar POIs in one area. This could be due to a lack experience of the user in mapping coupled with a lack of amenities available through the app preset. [Example of a harmful changeset.](http://osmcha.mapbox.com/40927770/) + - Edits from Maps.me editor are automatically uploaded through the app. The app generates an automatic changeset comment based on the kind of amenities that were added. Filtering Maps.me edits with most creations first as sort order helped us in finding most of the bad edits from Maps.me users so far. +3. This is similar to the first assumption. Mass modifications using iD editor could be a suspicious changeset. Mass modification could be two scenarios: + - When the user modifies tags of a long way (coastline, administrative boundaries, long motorway, etc.) and polygons, these edits are registered to the way/polygon and all the nodes in the feature object. + - When the user changes the geometry of an object on OSM, even though only one node is added the whole way/polygon is updated to be modified. [Example of a harmful changeset.](http://osmcha.mapbox.com/41991749/) +4. Mass creations can also be coupled with the iD editor in the filters. The idea is to review changesets which have most creations and see if all the editions fall under the [OSM editing standards and conventions](http://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions). [Example of a harmful changeset.](http://osmcha.mapbox.com/38282141/) +5. Sometimes, we were able to detect suspicious changesets by going through reason filters such as `edited an object with a significant place tag`, `edited an object with a significant tag`, `edited a wikipedia landmark`. [Example of a harmful changeset.](http://osmcha.mapbox.com/38534916/) +6. Clever acts of vandalism are hard to detect as the changesets may not be big. We can verify these modifications to `name` tags, deletion of tags from [small changesets that are iD editor contributions](http://osmcha.mapbox.com/?modify__lte=50&editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) or through [random search in OSMCha](http://osmcha.mapbox.com/). Examples harmful changesets: [1](http://www.openstreetmap.org/node/4331919989), [2](http://www.openstreetmap.org/node/4353068192/history). + + +#### Suspicious changeset keywords + +There are [certain keywords we have stored](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085) to quickly look through changesets that have these words in the changeset comments. For example "Google" and any profane language. + + +#### Finding vandalism detected by the community and reverted by Data Working Group + +The community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map then the community will inform Data Working Group and Data Working Group will revert these changesets with a changeset comment. + + +- Using **Keywords** + - Using keywords such as `revert`, `cleanup`, `fix` in changeset comment filter, we can find most of the changesets community has taken action on. This list in OSMCha includes fixes, reverts Data Working Group as well. + +- Using [**OSM - comments**](https://www.mapbox.com/osm-comments/) + - OSM-comments API allows querying changesets with specific parameters + - Link to see changeset comments from all users in OSM - [URL for web view](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) + +Currently, there is no direct way of using OSM-Comments-API to see all the changesets on which Data Working Group members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) + +**Finding reverts by Data Working Group** + +![documentations1](https://cloud.githubusercontent.com/assets/8921295/18270714/0cc820da-744c-11e6-8db8-71421c956e07.gif) +_Finding Data Working Group reverts using OSMCha_ + +- OSMCha allows us to query changesets from specific users. +- We can query all changesets from revert accounts of Data Working Group members such `Woodpeck_repair`, `pnorman_mechanical`, etc. \ No newline at end of file diff --git a/jp/validating-osm/index.md b/jp/validating-osm/index.md new file mode 100644 index 0000000..1bf1b5c --- /dev/null +++ b/jp/validating-osm/index.md @@ -0,0 +1,8 @@ +--- +title: Validating OpenStreetMap +layout: category +order: 8 +color: orange +description: A walkthrough of how to detect, inspect and fix potentially harmful changes in OpenStreetMap. +image: validating-osm.svg +--- From 6ce19db545e9e73ed48815ae41e97bc445d36a5c Mon Sep 17 00:00:00 2001 From: nyampire Date: Wed, 24 May 2017 18:12:39 +0900 Subject: [PATCH 45/66] add mapping-common-features.md --- .../0000-01-01-mapping-common-features.md | 177 ++++++++++-------- 1 file changed, 96 insertions(+), 81 deletions(-) diff --git a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md index e5ed2f1..be0b562 100644 --- a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md +++ b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md @@ -2,183 +2,191 @@ title: Mapping common features --- -This is a walkthrough of how to create and edit the most common features on OpenStreetMap. It's an introduction to get you started mapping but not meant to be comprehensive. We're going to use some OpenStreetMap specific terms here, if you're not familiar with what "nodes", "way" and "relations" are, read the previous guides first. +このチュートリアルでは、OpenStreetMapでよく作成・編集される地物の編集方法について解説します。これはあくまでもイントロダクションであり、包括的なマッピング方法の解説ではないことに注意してください。解説ではOpenStreetMap特有の用語を使います。もし"ノード"や"ウェイ"、"リレーション"といった用語の意味がわからない場合は、このガイドの前項を先にお読みください。 -## How do I map X? +## Xをマッピングするには？ + +この項目では、最もよく編集される地物について解説します。すべての地物の解説については[OpenStreetMap Map Features](http://wiki.openstreetmap.org/wiki/Map_Features) ([日本語版](http://wiki.openstreetmap.org/wiki/JA:Map_Features)) のガイドや、[Feature categories](http://wiki.openstreetmap.org/wiki/Category:Features)を参照してください。特定の地物、例えばバス停のマッピング方法を知りたい場合は、"tag bus stop site:wiki.openstreetmap.org" や "タグ バス停 openstreetmap.org" などのような単語で Google検索してください。 -We're focusing in this section on the most common map features. For full documentation, refer to the [OpenStreetMap Map Features](http://wiki.openstreetmap.org/wiki/Map_Features) guide or [Feature categories](http://wiki.openstreetmap.org/wiki/Category:Features). To look up a specific map feature fast, for instance how to map a bus stop, google with a query like "tag bus stop site:wiki.openstreetmap.org": ![](https://s3.amazonaws.com/f.cl.ly/items/3C3A0S3k011k1P3b2J0N/google.gif) A valuable complimentary resource is [taginfo.openstreetmap.org](http://taginfo.openstreetmap.org/). Tag info shows you the number of times a specific tag has been used, which lets you find out how established a tag is. -## Roads and paths +[taginfo.openstreetmap.org](http://taginfo.openstreetmap.org/)は、資料的価値が高く、よく参照されるサイトです。Taginfoでは、特定のタグが何回使われているかを表示することが可能で、既存の確立したタグの使い方を教えてくれます。 + +## 道路と歩道 -Roads are some of the most significant features we map. While roads are easy to trace off of Satellite imagery there is a large vocabulary for classifying different types of roads. +道路は私たちがマップする地物の中で非常に重要なものです。道路は航空写真から容易にトレース可能であり、その分類は非常に多岐にわたります。 -### Tracing roads +### 道路のトレース -Tracing a road is simple. Use the **Draw** (`A`) tool in JOSM or the **Line** tool in iD and draw the road following its course. The trick is to use the right amount of nodes to describe a way. Too few make the road appear very jagged. Too many are unnecessary data and make the road hard to edit later. +道路のトレース作業はたいへんシンプルです。JOSMでは **描画** (`Aキー`) 、iDでは **ライン** ツールを使って道路のコースに沿って線を描きます。道路を描く際には、適切な量のノードを配置するのがコツです。ノードの量が少なすぎると道路の線が雑になります。逆に、ノードの量が多すぎると後の編集で道路を修正することが困難になります。 Look at the picture below, the first example was traced with too few nodes, it is too jagged; the second example was traced with too many nodes adding redundant information; the last one is traced right: +以下の図を見てみてください。左の図はノードの数が少なすぎる状態で、線がギザギザになっています。マンな中の図はノードが多すぎて、冗長な情報が含まれています。右の図が最も望ましいトレース状態です。 + ![mapbox guide big](https://cloud.githubusercontent.com/assets/693781/10158378/f3a4b3fc-6691-11e5-9738-58ad86a5a525.png) -Roads must be connected where they intersect. On the left you can see two roads just crossing each other, on the right note how a node connects the two roads. This is important for navigation, where vehicles must be guided from one road to the other. +それぞれの道路は、交差する点で接続されています。左の図は単に2つの道路が交差している状態で、右の図では2つの道路が接続されている状態です。これは乗り物が道路から道路を伝って移動することになるナビゲーション（経路探索）を行う際に非常に重要な情報となります。 ![](https://s3.amazonaws.com/f.cl.ly/items/180r0E2l0P2H0m0Z3m07/Screen%20Shot%202015-01-04%20at%208.55.14%20PM.png) -And follow the flow of roads where possible. On the left, the road was traced with a "detour" for no apparent reason. On the right you see how the road tracing follows the logical flow of the road. +道路の流れはできるだけ再現してください。左の図では、道路が明確な理由なく"回り道"にされています。右の図では道路の論理的な流れに沿ってトレースが行われています。 ![wrong: "map around corners", right: follow flow](https://s3.amazonaws.com/f.cl.ly/items/0k1F3Y0m0y081H3v0W07/Screen%20Shot%202015-01-04%20at%208.48.54%20PM.png) -Trace every *physically* separated lane as a separate way. See for example this dual carriage way (orange): +*物理的に* 分離された車道は別々のウェイとしてトレースしてください。サンプルの二車線道路（オレンジ）のトレース方法を参考にしてください。 ![dual carriage way](https://s3.amazonaws.com/f.cl.ly/items/0f0z0i391l0C0e0X3d0b/Screen%20Shot%202015-01-04%20at%209.01.42%20PM.png) -When mapping a dual carriage way, make sure that connecting roads are properly connecting to both carriages *if* this connection is possible in reality: +二車線道路に対して道路が接続されている状況をマッピングする場合、実際の道路の接続状況を確認して、それぞれの車線に適切に道路が接続されているかを確認してください。 ![show 2 examples of connecting roads to a carriage way: one connecting to both lanes, one to only one lane](https://s3.amazonaws.com/f.cl.ly/items/07043M2U0H093c2q1r3m/Screen%20Shot%202015-01-04%20at%209.01.4222%20PM.png) -### Everything's a highway +### 道路として描くもの色々 -No matter whether it's an overland road, a city street, a foot path or a cycleway, you'll find it tagged with the `highway` key. Here are some examples of common tags: +車道だけではなく、歩道や小道、自転車道にもタグとして `highway` キーが使われています。よく使われる例は以下のとおりです。 -- `highway=residential` - a residential road in a city -- `highway=motorway` - a fast restricted access road -- `highway=footway` - a foot path -- `highway=cycleway` - a cycleway +- `highway=residential` - 住宅地区内の道路 +- `highway=motorway` - 高速走行専用道路 +- `highway=footway` - 歩道 +- `highway=cycleway` - 自転車道 -Roads often come with secondary tags, further specifying type or attribute of a road: +道路にはしばしば補助的なタグが付与され、道路の種別の指定や属性の表現が行われます。 -- `oneway=yes` says a road is a one way -- `lanes=2` says how many lanes a road has -- `name=Broadway` designates a street name -- `access=private|permissive` describes the level of access on a road -- `service=parking_aisle|driveway` further specifies the type of `highway=service` +- `oneway=yes` は一方通行に付与されます +- `lanes=2` は、分離されていない二車線道路を意味します +- `name=Broadway` は道路の名前を指定しています +- `access=private|permissive` は道路の通行制限を表現しています +- `service=parking_aisle|driveway` は、`highway=service`の中の特定のタイプを指定しています -### Oneways +### 一方通行 -Oneways are mapped by simply adding a `oneway=yes` tag to the road's way. Keep in mind that ways have a directionality. So the road will be a oneway in the direction of the way. If you need to change the flow of the one way, you have two options: +一方通行を表現するには、単純に `oneway=yes` タグを道路のウェイに適用してください。適用する際には、ウェイの向きに注意してください。一方通行の方向は、ウェイの向きのとおりに設定されます。一方通行の方向を変更したい場合には2つの方法があります。 -- Change the direction of the way (`Tool > Reverse Ways` in JOSM or the `<<` context icon on iD) -- Or tag with `oneway=-1` - use this approach where the way's directionality already governs another attribute such as bus route. +- ウェイの向きを変更 (JOSMでは`ツール > ウェイの方向転換`、iDでは操作アイコンの `<<`) +- タグとして`oneway=-1`を適用 - この方法は、例えばバスルートなど他の属性によってウェイの向きが指定されてしまっている場合に使います ![tagging a oneway](https://s3.amazonaws.com/f.cl.ly/items/1W0M081C2W3K0j0p1I2r/oneway.gif) OpenStreetMap Wiki: [Key:oneway](http://wiki.openstreetmap.org/wiki/Key:oneway) -### Turn restrictions +### 方向転回制限 Turn restrictions are rules that disallow certain turn maneuvers. Here's for instance a "no right turn" sign. +方向転回制限は、特定の方向へ曲がることを不許可にするルールです。例えば、"右方向転回禁止"の道路標識は以下のようになります。 + ![](https://farm3.staticflickr.com/2900/14360050862_ef35f7ffa8_b.jpg) -To map turn restrictions in JOSM, use the **turnrestrictions** plugin. Once enabled, you can activate a new turn restriction panel from the `Windows > Turn Restriction` menu item. +JOSMを使って方向転回制限をマップするには、 **turnrestrictions** プラグインを使用します。プラグインを有効化すると、 `ウィンドウ > 方向転回制限` メニューウィンドウに方向転回制限用のパネルが追加されます。 -Once enabled, create new turn restrictions or edit existing ones from the panel. Here is an example of how to create a simple "no right turn" restriction. We're selecting the way we can't take the right turn from as "from" object, the way we can't take the right turn to as "to" object and then we specify that the restriction is a "no right turn" restriction. As we save the turnrestrictions dialog warns us that there is no "via" object defined. It is not strictly required to have one, but is good practice, so we define one. +有効化を行い、方向転回制限の新規作成や既存設定の編集をパネルから行ってみましょう。以下はシンプルな "右方向転回禁止" の作成例です。右方向転回が禁止されている元の道路を "from" オブジェクトとして選択し、その道路から展開できない先の道路を "to" オブジェクトとして選択することによって、この制限設定が "右方向転回禁止" を意味するようになります。turnrestrictionsダイアログを閉じようとすると "via" オブジェクトが指定されていないという警告が表示されます。その設定は必須というわけではありませんが、グッドプラクティスではありますので、念の為指定をしておきましょう。 ![](https://s3.amazonaws.com/f.cl.ly/items/24173W1U033a193q2l1F/turn.gif) -Turn restrictions can get more complex quickly, so before you create or edit turn restrictions, make sure you read through and understand all available documentation on the OpenStreetMap wiki. +方向転回制限はあっという間に指定が複雑化します。そのため、制限を作成したり編集したりする場合は、OpenStreetMap wikiのドキュメントはあらかじめすべて読み、理解するようにしてから実施するようにしてください。 *Video: [How to edit turn restrictions in JOSM](https://www.youtube.com/watch?v=0SdixDJAED0)* *OpenStreetMap Wiki: [Relation:restriction](http://wiki.openstreetmap.org/wiki/Relation:restriction)* -### Simple classification guide +### シンプルな道路階層設定ガイド -One of the more subtle skills to learn in OpenStreetMap is how to properly classify roads. The `highway` tag has more than eight values for roads, another five-plus for non-vehicular traffic, and a series of secondary tags. What's more, highway classifications are highly country specific and follow different conventions on a country by country basis. +OpenStreetMapを学ぶにあたってもうひとつややこしいスキルは、道路の階層付けを適切に行う方法です。`highway`タグでは車道が8つ以上の階層に分類されており、乗り物以外の通行を表現するにも5つ以上、補助的なタグについても数多く指定がされています。さらに道路の階層構造は各国で異なり、それぞれの国ごとに異なる基準を使って作業が行われています。 -Here's a quick guide on how to go about working with road classifications in OpenStreetMap. +OpenStreetMapで道路階層の作業を行う場合のクイックガイドは以下のとおりです。 -1. Follow existing classifications. Don't change classifications and follow the conventions you see on the local map for new data. -2. The smallest roads in a network are the easiest ones to identify and also the ones you'll wind up adding most. For minor roads, prefer `highway=residential` in built up residential areas, `highway=unclassified` for everything else. -3. For all other cases, use `highway=road` +1. 既存の階層構造に従う。階層構造を変更せず、新しいデータを作成する際にはその土地のローカルのやり方に従う +2. 道路ネットワークの中で最も小さい道路は特定が簡単で、普段の編集で一番よく入力するものでしょう。そうした道路に対しては、道路が居住区域内にある場合は `highway=residential` 、その他の場合は`highway=unclassified`を指定します +3. どうしても種別がわからない場合は `highway=road`を使用します -For a full reference on highway mapping, look at the *[wiki entry for the highway tag](http://wiki.openstreetmap.org/wiki/Key:highway)*. +道路マッピングのより詳しい方法については、[highwayタグのwikiエントリー](http://wiki.openstreetmap.org/wiki/Key:highway)を参照してください。 -### Intersections +### 道路と他の地物の交差 -The intersection between a road and another feature must always be defined. Where they meet, there is either an intersection, a tunnel or a bridge. +道路と他の地物が交差する場合、常になんらかの追加作業が行われるべきです。そうした交差が行われている場所には、交差点か、トンネルか、橋があるはずです。 -#### Simple intersections between two roads +#### 2つの道路の交差点 -To create a simple intersection between two roads, just make sure to connect the two roads with a node. +2つの道路の交差点を作成するには、その2つの交差点が1つのノードで結節させてください。 ![show how 2 roads connect](https://s3.amazonaws.com/f.cl.ly/items/1b0K0E2b401E0U2U1H1A/intersect.gif) -#### Tunnel +#### トンネル -A tunnel carries the `tunnel=yes` and a `layer=` tag that is one lower than the `layer=` tag of the feature it intersects with (default `layer` value is 0). The road is *not* connected with the other feature. Split ways where the tunnel starts +トンネルには、 `tunnel=yes` タグと `layer=` タグを付与します。`layer=`の値には、交差する地物のレイヤーの値（`layer`のデフォルト値は0）よりも1低い値を割り当ててください。道路は他の地物と接続 *しません*。トンネルの開始点と終了点でウェイを分割します。 ![show how to map a tunnel](https://s3.amazonaws.com/f.cl.ly/items/0e3S3F3j1N000w1R1d2x/tunnel.gif) -A building passage is a special type of tunnel that passes through a building. To map a building passage, connect the road where it intersects with the building outline with nodes, then tag the portion of the road that intersects with the building with `tunnel=building_passage`. +建物内を道路が通過する場合にも、トンネルとして扱います。その場合、建物の外郭と道路をノードで接続させ、建物内を通過している部分の道路ウェイに `tunnel=building_passage` を付与してください。 ![map a building passage](https://s3.amazonaws.com/f.cl.ly/items/1v1E0Z2P0C3X1K1h0Q1M/building-passage.gif) *OpenStreetMap Wiki: [Key:tunnel](http://wiki.openstreetmap.org/wiki/Key:tunnel)* -#### Bridge +#### 橋 -In addition to the road's `highway=*` tag, a bridge carries the `bridge=yes` and a `layer=` tag that is one higher than the `layer=` tag of the feature it intersects with (default `layer` value is 0). +道路を表す `highway=*`に加え、`bridge=yes` タグと `layer=` タグを付与します。`layer=`の値には、交差する地物のレイヤーの値（`layer`のデフォルト値は0）よりも1高い値を割り当ててください。 ![show how to map a bridge](https://s3.amazonaws.com/f.cl.ly/items/1v1P2S3P35292a1m2a0m/bridge.gif) *OpenStreetMap Wiki: [Key:bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)* -#### Railroad crossing +#### 線路との交差 + +鉄道の線路との交差をマップするには、道路との交差を表現する方法と同様、道路と線路をノードで結節します。結節点のノードには `railway=level_crossing` タグを付与してください。類似のタグとして `railway=crossing` がありますが、こちらは歩行者用の踏切ですので間違えないよう注意してください。 -Map a railroad crossing similar to an intersection between two roads by connecting the road and the railroad with a node. Then tag the node with `railway=level_crossing`. Do not confuse this tag with `railway=crossing` which is only for pedestrian crossings. ![map a level crossing](https://s3.amazonaws.com/f.cl.ly/items/1q3o381b0K3r3x291J0E/level_crossing.gif) *OpenStreetMap Wiki: [Tag:railway=level_crossing](http://wiki.openstreetmap.org/wiki/Tag:railway%3Dlevel_crossing)* -#### Roundabouts +#### ラウンドアバウト -Map a roundabout by tracing the circular road and tag it with `junction=roundabout`. For the road classification, use the highest classification of all roads connected to the roundabout. The `junction=roundabout` tag implies a oneway - make sure that the directionality of the way is correct. +ラウンドアバウトをマップするには円形の道路を描き、そこに `junction=roundabout` を付与してください。道路の種別は、そのラウンドアバウトに接続されている全ての道路のうち最も高い階層を割り当てます。 `junction=roundabout`タグは一方通行であることも意味します。道路のウェイの向きにも注意してください。 ![ezgif-1791703736](https://cloud.githubusercontent.com/assets/12744420/10310207/745ec272-6c5e-11e5-8d4c-5727e8b5d42e.gif)) -#### Complex intersections +#### 複雑な交差点 -In a complex intersection involving multiple carriage ways trace the roads so that they reflect the flow along the main carriages and make sure that oneways make sense. +複数の車線が関係する複雑な形状の交差点を表現するには、まず道路のトレースを行い、メインとなる車線の交通フローが正しく反映できるようにした後で一方通行を適切に配置してください。 ![](https://s3.amazonaws.com/f.cl.ly/items/0M3S232n2V342Y3T2n1Y/Screen%20Shot%202015-01-04%20at%2010.34.51%20PM.png) -## Buildings +## 建物 -Tracing buildings takes good imagery and patience. Take your time and pay attention to angularity, alignment between buildings and reflecting the regularities between buildings. Buildings are traced as outlines of *where the building meets the ground*. This last piece is important. The roof outline is often easier to see in the imagery so you'll find it often traced in OpenStreetMap but it's wrong and needs to be shifted to the ground outline. +建物のトレースには品質の高い航空写真と忍耐が必要です。建物の角の位置や建物同士の角度に注意を払い、建物配置の規則性を反映しましょう。建物は、その外郭部分が *地面と接している場所* をトレースするようにします。この点は非常に重要です。航空写真をもとにすると建物の屋根の形状はわかりやすいことが多く、OpenStreetMapではその位置に建物がトレースされてしまうことが多いのですが、それは間違いであり、本来は建物が地面と接地している部分をトレースすることが正しいです。 ![505kyfalbo](https://cloud.githubusercontent.com/assets/126868/6914386/8d115556-d7a7-11e4-9f04-7291331e7ef8.gif) -The main challenge with tracing buildings is lack of detail in imagery. Where you don't find good enough imagery for tracing a building, just don't trace it. +建物のトレースで最も困難なのは、航空写真の画像から形状の詳細が読み取れないことです。航空写真から建物の形状が充分に認識できない場合、無理にトレースはしないでください。 -Here are a couple of JOSM specific tips to trace buildings effectively. +いくつか、JOSMで建物のトレースを行う際のTIPSを紹介します。 -For tracing buildings, use the **buildings plugin**. Once enabled, a new building tool will be available in the edit toolbar on the left. The building tool `B` will draw rectangular shapes tagged `building=yes` for you. To draw buildings parallel to each other, draw the first building, select it, then draw subsequent buildings. +建物のトレースを行うには、 *buildings plugin* を使います。プラグインを有効化すると、画面左の編集ツールバーに building toolが追加されます。 building tool は `B` キーで利用でき、四角形を描画した上でそのオブジェクトに `building=yes`タグを追加してくれます。位置が並行に配置されている建物をトレースするには、1つめの建物を選択し、その状態で他の建物をトレースしてください。 ![](https://s3.amazonaws.com/f.cl.ly/items/3A2T0l0Y3x0N030w090F/building.gif) -If you draw closed ways free hand, use `Tools > Orthogonalize Shape` or press `Q` to square out buildings like so: +閉じたウェイをフリーハンドで描く場合には、 `ツール > 直交化` を選択するか `Q` キーを押して、以下のような感じで建物の角が直角になるようにしてください。 ![](https://s3.amazonaws.com/f.cl.ly/items/3U3c1S1V2X1Q1h3s0845/Screen%20Shot%202014-12-15%20at%206.35.04%20PM.png) -Use auxiliary lines to align protruding portions of a building: +建物の突き出た部分を描くには、補助線を活用します。 ![](https://s3.amazonaws.com/f.cl.ly/items/0s3G3T200b1C3d3i0x2Y/buildingalignment.gif) -To align previously traced buildings neatly, select them, and then select two reference nodes to create an alignment axis and orthoganalize `Q` the selection. +既にトレース済みの建物の向きを簡単に修正するには、対象の建物オブジェクトを選択し、さらにその状態で向きのもとになる参照点ノードを2つ選択した状態で `Q` キーを押すことによって、そのノードの角度に合わせてオブジェクトの向きが調整されます。 ![3zpk8nxbdt](https://cloud.githubusercontent.com/assets/126868/6900081/d65cf23c-d721-11e4-82f9-7084b11bb41f.gif) -You can use split buildings temporarily with `Tools > Split Way` or pressing `P` to orthogonalize portions of a building before reconnecting the with `Tools > Connect Way` or pressing `C`: +建物オブジェクトを一時的に分割するには `ツール > ウェイの分割` を選択するか、 `P` キーを押してください。該当部分を直交化した後に建物を再接続するには `ツール > ウェイの接続` を選択するか、 `C` キーを押します。 ![](https://s3.amazonaws.com/f.cl.ly/items/151R161W3i2c043q1z0B/straightenc.gif) -Here is a quick end to end walkthrough of how to trace a building: +簡単ですが、建物のトレース方法に関するチュートリアルはここまでです。 ![](https://s3.amazonaws.com/f.cl.ly/items/3T0Y0h390L3l19000s2h/buildings.gif) @@ -186,71 +194,78 @@ Here is a quick end to end walkthrough of how to trace a building: *Video: [Tracing buildings with JOSM](https://www.youtube.com/watch?v=9GRIHSAAkSs)* -## Points of interest +## Points of interest / POI -"Point of interest" is a general term for a real world point-like feature noteworthy enough to include it on a map. Some examples are restaurants, cafés, shops, banks, churches, public toilets and water fountains. There's not a single point of interest tag key in OpenStreetMap but a variety that can be used for mapping a point of interest: `amenity=`, `shop=`, `tourism=` are some examples. +"Point of interest （ポイント・オブ・インタレスト、POI）"とは、現実世界の中で地図に含められるべき価値のある地物とその地点を表現するための一般名詞です。例えばレストランや喫茶店、店舗、銀行、教会や寺院、公衆トイレや噴水などが挙げられます。OpenStreetMapでPOIを表現するためのタグは1つではなく、`amenity=`、 `shop=`、 `tourism=` など、さまざまな種類のPOIを表現するために多様なタグが用意されています。 *OpenStreetMap Wiki: [Key:amenity](http://wiki.openstreetmap.org/wiki/Key:amenity), [Key:tourism](http://wiki.openstreetmap.org/wiki/Key:tourism), [Key:shop](http://wiki.openstreetmap.org/wiki/Key:shop), [Key:leisure](http://wiki.openstreetmap.org/wiki/Key:leisure)* -### Simple point of interest +### ノードとしてのPOI -The simplest way to map a point of interest is to create a single node and add corresponding tags. Here's an example of a fountain mapped in OpenStreetMap: +POIをマップするための最も簡単な方法は、単一のノードを配置し、そこに適切なタグを付与する方法です。以下は、OpenStreetMapで噴水をマップする方法の例です。 ![](https://s3.amazonaws.com/f.cl.ly/items/2a0E2w0u2U0D0t2b1Z3Y/fountain.gif) -Here's an example of a restaurant: +レストランをマップするには以下のようにします。 ![](https://s3.amazonaws.com/f.cl.ly/items/1R3K0A1p0C1G043n1o3d/komi.gif) -### Areas as points of interest +### エリアとしてのPOI Wherever you can clearly determine the extent of a "point" of interest, map it. A good example are parks, here is Folger Park in Washington DC. The Park is mapped as a closed way tagged `leisure=park`. Note how the way follows the exact outline of the park. +"ポイント" オブ・インタレストの中には、その境界線が明確に確定できる地物があります。そうしたPOIもマップしてみましょう。わかりやすい例として公園をあげます。以下はワシントンDCにあるFolger Parkの例です。この公園は閉じたウェイとして描かれ、そこに `leusure=park`タグが付与されています。 + ![](https://s3.amazonaws.com/f.cl.ly/items/0V2N0n290Z1L0H1h2b1e/Screen%20Shot%202015-01-10%20at%208.29.39%20AM.png) -### Building as point of interest +### POIとしての建物 + +時折、建物そのものがPOIとして扱われる場合があります。例えば駅前の多用途施設の中にあるマクドナルドレストランの建物や、郊外のショッピングセンターに併設しているドライブスルー専用マクドナルドのことを考えてみてください。あるいは、衛星写真を使って判別可能な地物としては、教会や寺院のような礼拝施設を考えてみてください。このようなケースでは、建物そのものがPOIとしてタグづけされるべきです。以下は、既存のマッピングとして建物のなかのノードとして書かれていた教会の例です。この場合、ノードに付与されていた全てのタグを建物に転記し、その後ノードを削除しています。 + -Sometimes the building itself is considered the point of interest. Think for instance of a MacDonalds restaurant in an urban multi-use building versus a MacDonalds drive through in a suburban strip mall. Or - often easy to spot from satellite imagery - think of a place of worship like a church. In such cases the building itself should be tagged as a point of interest. Here's a church that has first been mapped as a single node in a building. The example shows how all tags from the node are transferred to the building and then the node is removed. ![](https://s3.amazonaws.com/f.cl.ly/items/2m0k0v333M1H0i1t3p1V/church.gif) -### Schools and universities +### 学校、大学 -Schools can just be mapped as a simple node tagged `amenity=school`. But often schools occupy an entire building or a piece of land. School grounds, the terrain on which a school sits, are mapped as `amenity=school`. The buildings of a school are mapped as `building=school`. Mapping schools as just a simple node is fine. However, wherever appropriate, map a school's ground and buildings as ways. +学校はシンプルに、`amenity=school`タグ付きのノードとしてマップすることが可能です。ただし、学校は建物全体や一定の広さの土地を専有していることがしばしばあります。学校の校庭や校舎が建っている敷地などは `amenity=school`としてマップすることができます。学校を地図上に配置するだけであればノードを置くだけで十分です。しかしながら、もし適切であるならば、学校の工程や建物をウェイとしてマップしてみましょう。 -An example where a school *does not* occupy the entire building: +以下は、学校が建物全体を *専有していない* 場合の例です。 ![](https://s3.amazonaws.com/f.cl.ly/items/0H2W3b401X3H0r0O011s/Screen%20Shot%202015-01-09%20at%206.09.01%20PM.png) An example where a school *does* occupy an entire building: +学校が建物全体を *専有している* 場合は以下のようになります。 + ![](https://s3.amazonaws.com/f.cl.ly/items/0r3q0C0w2L0C3n3d2f11/Screen%20Shot%202015-01-09%20at%206.18.28%20PM.png) -An example where a school occupies its own school grounds: +学校が自身で校庭を所有している場合は以下のようにします。 ![](https://s3.amazonaws.com/f.cl.ly/items/1W1A1p0U3z3D3E3g183M/highschool.gif) -Universities are similar: +大学も同様です。 ![](https://s3.amazonaws.com/f.cl.ly/items/102S1D1Z472x213M2b0Y/university.gif) *OpenStreetMap Wiki: [Tag:amenity=school](http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dschool), [Tag:building=school](http://wiki.openstreetmap.org/wiki/Tag:building%3Dschool), [Tag:amenity=university](http://wiki.openstreetmap.org/wiki/Tag:amenity%3Duniversity), [Tag:building=university](http://wiki.openstreetmap.org/wiki/Tag:building%3Duniversity), [Tag:amenity=college](http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dcollege)* -## Streams and Rivers +## 水路と河川 + +小さな河川をトレースする場合には、ウェイを描き `waterway=stream`でタグ付けしてください。ウェイの向きは水が流れる向きを表します。大きな河川を描く場合、河川の中心線をトレースして `waterway=river`としてタグ付けし、河川の流域を `natural=water` と `water=river`を使ってタグ付けしてください。河川の名前は waterwayタグを付与したウェイに対して与えます。以下が描画例です。 -Trace small streams as just a way tagged with `waterway=stream`. The way's direction signals the direction in which the water flows. For larger rivers, trace the center of the river as `waterway=river` and in addition the river banks with `natural=water` and `water=river` tags. The name of the river always sits on the waterway. See here for an example: ![](https://s3.amazonaws.com/f.cl.ly/items/460R352M0H301L2Y1Q3T/river.gif) -Islands in rivers are mapped as relations of `type=multipolygon`. Observe how on a multipolygon the `natural=water` and `water=river` tags sit on the multipolygon relation and not on the way: +河川に中洲がある場合は、`type=multipolygon`のリレーションを使ってマップします。`natural=water` と `water=river`を付与したエリアを使ってマルチポリゴンを使うようにします。河川の中心線を表すウェイをマルチポリゴンに含めないでください。 ![](https://s3.amazonaws.com/f.cl.ly/items/0t0A0q06130m0O1c3I19/multiriver.gif) -*Video: [Map a river island](http://cl.ly/0M0m2C2t2T3g)* +*ビデオ: [中洲のマッピング方法](http://cl.ly/0M0m2C2t2T3g)* *OpenStreetMap Wiki: [Tag:waterway=river](http://wiki.openstreetmap.org/wiki/Tag:waterway%3Driver)* -## Coming soon +## 以下続編 - Walking and cycling paths - Places (city versus village versus suburb versus neighborhood) From 88658676c797a0d34df30b74bbadb44fd058afa5 Mon Sep 17 00:00:00 2001 From: nyampire Date: Wed, 24 May 2017 18:40:14 +0900 Subject: [PATCH 46/66] mod mapping-common-features.md --- .../_posts/0000-01-01-mapping-common-features.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md index be0b562..59f0622 100644 --- a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md +++ b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md @@ -11,8 +11,6 @@ title: Mapping common features ![](https://s3.amazonaws.com/f.cl.ly/items/3C3A0S3k011k1P3b2J0N/google.gif) -A valuable complimentary resource is [taginfo.openstreetmap.org](http://taginfo.openstreetmap.org/). Tag info shows you the number of times a specific tag has been used, which lets you find out how established a tag is. - [taginfo.openstreetmap.org](http://taginfo.openstreetmap.org/)は、資料的価値が高く、よく参照されるサイトです。Taginfoでは、特定のタグが何回使われているかを表示することが可能で、既存の確立したタグの使い方を教えてくれます。 ## 道路と歩道 @@ -23,8 +21,6 @@ A valuable complimentary resource is [taginfo.openstreetmap.org](http://taginfo. 道路のトレース作業はたいへんシンプルです。JOSMでは **描画** (`Aキー`) 、iDでは **ライン** ツールを使って道路のコースに沿って線を描きます。道路を描く際には、適切な量のノードを配置するのがコツです。ノードの量が少なすぎると道路の線が雑になります。逆に、ノードの量が多すぎると後の編集で道路を修正することが困難になります。 -Look at the picture below, the first example was traced with too few nodes, it is too jagged; the second example was traced with too many nodes adding redundant information; the last one is traced right: - 以下の図を見てみてください。左の図はノードの数が少なすぎる状態で、線がギザギザになっています。マンな中の図はノードが多すぎて、冗長な情報が含まれています。右の図が最も望ましいトレース状態です。 ![mapbox guide big](https://cloud.githubusercontent.com/assets/693781/10158378/f3a4b3fc-6691-11e5-9738-58ad86a5a525.png) @@ -75,8 +71,6 @@ OpenStreetMap Wiki: [Key:oneway](http://wiki.openstreetmap.org/wiki/Key:oneway) ### 方向転回制限 -Turn restrictions are rules that disallow certain turn maneuvers. Here's for instance a "no right turn" sign. - 方向転回制限は、特定の方向へ曲がることを不許可にするルールです。例えば、"右方向転回禁止"の道路標識は以下のようになります。 ![](https://farm3.staticflickr.com/2900/14360050862_ef35f7ffa8_b.jpg) @@ -212,8 +206,6 @@ POIをマップするための最も簡単な方法は、単一のノードを ### エリアとしてのPOI -Wherever you can clearly determine the extent of a "point" of interest, map it. A good example are parks, here is Folger Park in Washington DC. The Park is mapped as a closed way tagged `leisure=park`. Note how the way follows the exact outline of the park. - "ポイント" オブ・インタレストの中には、その境界線が明確に確定できる地物があります。そうしたPOIもマップしてみましょう。わかりやすい例として公園をあげます。以下はワシントンDCにあるFolger Parkの例です。この公園は閉じたウェイとして描かれ、そこに `leusure=park`タグが付与されています。 ![](https://s3.amazonaws.com/f.cl.ly/items/0V2N0n290Z1L0H1h2b1e/Screen%20Shot%202015-01-10%20at%208.29.39%20AM.png) @@ -222,8 +214,6 @@ Wherever you can clearly determine the extent of a "point" of interest, map it. 時折、建物そのものがPOIとして扱われる場合があります。例えば駅前の多用途施設の中にあるマクドナルドレストランの建物や、郊外のショッピングセンターに併設しているドライブスルー専用マクドナルドのことを考えてみてください。あるいは、衛星写真を使って判別可能な地物としては、教会や寺院のような礼拝施設を考えてみてください。このようなケースでは、建物そのものがPOIとしてタグづけされるべきです。以下は、既存のマッピングとして建物のなかのノードとして書かれていた教会の例です。この場合、ノードに付与されていた全てのタグを建物に転記し、その後ノードを削除しています。 - - ![](https://s3.amazonaws.com/f.cl.ly/items/2m0k0v333M1H0i1t3p1V/church.gif) ### 学校、大学 @@ -234,8 +224,6 @@ Wherever you can clearly determine the extent of a "point" of interest, map it. ![](https://s3.amazonaws.com/f.cl.ly/items/0H2W3b401X3H0r0O011s/Screen%20Shot%202015-01-09%20at%206.09.01%20PM.png) -An example where a school *does* occupy an entire building: - 学校が建物全体を *専有している* 場合は以下のようになります。 ![](https://s3.amazonaws.com/f.cl.ly/items/0r3q0C0w2L0C3n3d2f11/Screen%20Shot%202015-01-09%20at%206.18.28%20PM.png) From 344832aaff64738fdd033464f1e194bfa1138bd2 Mon Sep 17 00:00:00 2001 From: nyampire Date: Fri, 26 May 2017 07:44:49 +0900 Subject: [PATCH 47/66] add jp resources --- _config.yml | 13 ++- .../_posts/josm/0000-01-02-josm-shortcuts.md | 45 ++++---- .../0000-01-05-advanced-josm-customization.md | 10 +- .../0000-01-01-reviewing-your-edits.md | 48 ++++---- jp/becoming-a-power-mapper/index.md | 4 +- .../_posts/0000-01-01-getting-started.md | 106 +++++++++--------- jp/getting-started/index.md | 2 +- jp/mapping-common-features/index.md | 2 +- jp/mapping-for-navigation/index.md | 4 +- jp/mapping-with-josm/index.md | 2 +- .../_posts/0000-01-01-osm-data-model.md | 43 ++++--- jp/osm-data-model/index.md | 2 +- jp/sources/_posts/0000-01-01-sources.md | 58 ++++++++++ jp/sources/index.md | 8 ++ jp/validating-osm/index.md | 2 +- 15 files changed, 216 insertions(+), 133 deletions(-) create mode 100644 jp/sources/_posts/0000-01-01-sources.md create mode 100644 jp/sources/index.md diff --git a/_config.yml b/_config.yml index a0f624b..d4d6584 100644 --- a/_config.yml +++ b/_config.yml @@ -38,4 +38,15 @@ defaults: path: "es" type: "posts" values: - lang: "es" \ No newline at end of file + lang: "es" +# JAPANESE +- scope: + path: "jp" + type: "pages" + values: + lang: "jp" +- scope: + path: "jp" + type: "posts" + values: + lang: "jp" \ No newline at end of file diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-02-josm-shortcuts.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-02-josm-shortcuts.md index 499044b..89cd0a9 100644 --- a/jp/becoming-a-power-mapper/_posts/josm/0000-01-02-josm-shortcuts.md +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-02-josm-shortcuts.md @@ -2,49 +2,50 @@ title: JOSM shortcuts --- -As you draw using the JOSM editor, or correct map errors on to-fix, keyboard shortcuts can save help you save a great deal of time and increase the quality of your mapping [strokes replaced] if used correctly. Here we'll cover keyboard shortcuts on JOSM - default settings, how you can customize these to suit your preferences, and shortcuts most popular with the data team. +JOSMエディタを使って編集を行う場合、あるいはto-fixを使って地図データのエラーを修正する場合、もしキーボードショートカットを正しく使うことができれば、時間の短縮とマッピングの品質向上を見込むことができます。ここではJOSMのショートカット - 特にそのデフォルト設定とあなたの環境に合わせたカスタマイズ方法、データチームでよく使われるキー操作について説明します。 ![](https://scontent-frt3-1.xx.fbcdn.net/hphotos-xfl1/t31.0-8/920735_554891274669057_2113729309314231818_o.jpg) -*Use the [JOSM cheatsheet](http://www.openstreetmap.org/user/baditaflorin/diary/37606) by user:baditaflorin* +*[JOSM cheatsheet](http://www.openstreetmap.org/user/baditaflorin/diary/37606) by user:baditaflorin も参照してください* -## Basic Shortcuts [Default] +## 基本のショートカット [デフォルト] + +JOSMエディタにはデフォルトで、OpenStreetMapデータのダウンロード/アップロードやタグの追加/編集/削除、編集結果の妥当性検証を含め、ノードやウェイ、ポリゴンを対象として100以上のショートカットが設定されています。詳細はJOSM wikiの[一般的なキーボードショートカット](https://josm.openstreetmap.de/wiki/Presets/CommonKeyboardShortcuts)ページを参照ください。 -By default, the JOSM editor comes pre-loaded with approximately 100+ shortcuts which cover everything from downloading/uploading map data from the OpenStreetMap server, adding/editing/deleting tags, validating results, and working with nodes, ways, and polygons. See the [Common Keyboard Shortcuts](https://josm.openstreetmap.de/wiki/Presets/CommonKeyboardShortcuts) on the JOSM wiki for more details. ![image](https://cloud.githubusercontent.com/assets/8562256/7113237/5beb62a8-e1ef-11e4-832d-0fa5e827503e.png) -_Under **Tools** on the menu bar, you can see some of the basic default shortcuts on JOSM_ +_メニューバーの **ツール** を選択すると、JOSMの基本的なデフォルトショートカットを表示する事が可能です_ + +まずこれらJOSMの基本的なデフォルトショートカットを覚えるとよいのですが、JOSMでの高速編集に慣れてくるにつれ、より自身のマッピング環境に合わせたカスタマイズが便利になってきます。例えばカスタマイズを行うことで、マウスから右手を離すことなくショートカットを押してマッピングを行うような設定も可能です。 -The default shortcuts on JOSM are a great way to get started, but once you are familiar and start speed mapping, you may want to consider customizing the JOSM shortcuts to fit your mapping preferences. For example, you can customize shortcuts to allow you to map quickly without having to take your right hand off the mouse. -Action | Keyboard Shortcut +アクション | キーボードショートカット ---- | ---- -Uploading the edit | ` -Downloading data | Q -Deleting data | D +編集アップロード | ` +データダウンロード | Q +データ削除 | D -To access the Shortcuts Menu, go to **Preferences** on the JOSM menu bar. Within **Preferences**, click **Options** on the left (seventh button). +ショートカットメニューを表示するにはJOSMの **設定** メニューを表示してください。 **設定**の中の左側にある **オプション** (上から7つめのボタン)をクリックしてください。 ![configure_image_shortcuts](https://cloud.githubusercontent.com/assets/353700/11626533/8cbfdb90-9d09-11e5-8641-8a1260e232a8.png) +以下、慣れ親しんでいるマッパーの多いであろうショートカットです。 -Here is a comprehensive categorized list of shortcuts everyone should be familiar with. +### JOSMショートカット -### JOSM Shortcuts +#### データ -#### DATA - -ACTION | DESCRIPTION | Mac | Win/Linux +アクション | 解説 | Mac | Win/Linux ---- | ---- | ---- | ---- -OPEN | open a file | `Cmd+O` | -SAVE | save current data | `Cmd+S` | -DATA DOWNLOAD | download map data from OSM server | `Cmd+Shift+Down` | -DATA UPLOAD | upload all changes in the active data layer to the OSM server | `Cmd+Shift+Up` | +開く | ファイルを開く | `Cmd+O` | +保存 | 現在のデータを保存 | `Cmd+S` | +データダウンロード | OSMサーバからの地図データダウンロード | `Cmd+Shift+Down` | +データアップロード | 現在選択しているデータレイヤの変更箇所をOSMサーバへアップロード | `Cmd+Shift+Up` | ----- -### Basic map editing +### 基本的な地図編集 ACTION | DESCRIPTION | Mac | Win/Linux ---- | ---- | ---- | ---- @@ -75,7 +76,7 @@ UPDATE MULTIPOLYGON | update a multipolygon | `Cmd+Shift+B` | ---- -## Accuracy & precision +## 位置精度、正確さ ACTION | DESCRIPTION | SHORTCUT ---- | ---- | ---- diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md index 0905d04..fecaf24 100644 --- a/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md @@ -2,11 +2,17 @@ title: Advanced JOSM customization --- - Hidden settings in JOSM can be configured directly from the advanced preferences panel. This also gives you access to export and import your configuration profiles. +JOSMの各市設定として、拡張設定パネルからいくつかの設定を行うことが可能です。JOSMに設定したプロファイル情報をインポートしたり、エクスポートしたりすることもできます。 + The panel is hidden by default and is shown as the last option when `Expert mode` is enabled. +デフォルトでは設定パネルは隠されており、`上級者モード`を有効化した時だけ最後のオプションが表示されるようになっています。 + ![screenshot 2015-10-15 14 42 52](https://cloud.githubusercontent.com/assets/126868/10509569/890e64b8-734b-11e5-988f-26596f9d42d9.png) -**Note** JOSM will need to be restarted for any changes to take effect. \ No newline at end of file +**Note** JOSM will need to be restarted for any changes to take effect. + +**注意事項** 設定の変更を反映させるにはJOSMの再起動が必要です + diff --git a/jp/becoming-a-power-mapper/_posts/mapping/0000-01-01-reviewing-your-edits.md b/jp/becoming-a-power-mapper/_posts/mapping/0000-01-01-reviewing-your-edits.md index 72d7b0e..72110f6 100644 --- a/jp/becoming-a-power-mapper/_posts/mapping/0000-01-01-reviewing-your-edits.md +++ b/jp/becoming-a-power-mapper/_posts/mapping/0000-01-01-reviewing-your-edits.md @@ -2,48 +2,48 @@ title: Reviewing your edits --- -## JOSM Validator +## JOSM妥当性検証 -The easiest way to [fix common mapping issues]({{site.baseurl}}/becoming-a-power-mapper/fixing-common-mapping-issues/) is to use the inbuilt validator in JOSM. All edits made in a session are automatically validated and a warning will be displayed before upload if any suspicious data is found. +[よくあるマッピングの間違い修正]({{site.baseurl}}/becoming-a-power-mapper/fixing-common-mapping-issues/)を行う最も簡単な方法は、JOSMに実装されている妥当性検証機能を使うことです。作業中のセッションで行われたすべての編集内容が自動的にチェックされ、間違いと疑われるデータがもしあればアップロード前にそれらの間違いを警告してくれます。 ![screenshot 2015-12-11 14 30 37](https://cloud.githubusercontent.com/assets/126868/11739757/c77832c0-a013-11e5-8568-c6dd6624e127.png) -### Usage +### 使い方 -* Select the data you want validated and press `Shift+V` or hit `Validate` from the Validator panel. If no data is selected, the Validator will run on all the data in the active layer. -* A *Validation errors* layer will be added to your *Layers* to highlight features with errors. -* The *Validation Results* panel will display all the detected errors. Select any of the detected errors to fix. You can right click an entry and zoom to the location if needed. +* 検証したいデータを選択し、`Shift+V`キーを押すか、あるいは妥当性検証パネルから`妥当性検証`を押してください。特定のオブジェクトを選択していない場合、現在選択されているレイヤ内のすべての情報が検証対象になります。 +* *妥当性エラー*レイヤが、*レイヤ*に追加され、エラーの可能性がある地物が強調表示されます。 +* 検知されたすべてのエラーが*検証結果*パネルに表示されます。それぞれのエラーを選択し、修正を行ってください。エラー表示を右クリックすると、エラーが存在する場所にズームします。 ![using validator]({{site.baseurl}}/images/validator_using.gif) -The **Validation Results** have several buttons activated to navigate and fix errors: -* **Select** – Select the objects of the selected error. -* **Lookup** – Looks up the selected primitives in the error list. -* **Validation** – Start validation process for current selection or all objects (when nothing selected). -* **Fix** – Fix an error (only when automatically fixable). -* **Ignore** – Ignore an error or a group of errors in future tests. +**検証結果**にはエラー修正に関係したいくつかのボタンが表示されます。 +* **選択** - 選択したエラーが発生しているオブジェクトを選択 +* **表示移動** - エラーリストの中から選択した内容へ表示移動 +* **妥当性検証** - 選択中の地物、あるいは（選択していない場合）表示しているすべての地物を対象に妥当性検証を開始 +* **修正** - エラーを修正 (自動的に修正が可能な場合) +* **無視** - 以降のテストで対象のエラー検知を無視 -### Customizing error detection +### エラー検知のカスタマイズ -By default the validator checks against a wide range of [data issues](https://josm.openstreetmap.de/wiki/Help/Preferences/Validator), many of which may not be important or may contain false positives. You can customize the settings from *Preferences > Data Validator* +デフォルトで行う検知では、[データ問題](https://josm.openstreetmap.de/wiki/Help/Preferences/Validator)であげられている非常に幅広い内容について、すべてチェックが行われます。ですが、そのなかのいくつかはさほど重要ではなかったり、問題のないデータを誤検知することがあります。*設定 > データの妥当性検証*から設定を変更することが可能です。 ![validator settings]({{site.baseurl}}/images/validator_settings.gif) - -For more details check the [OSM Wiki](http://wiki.openstreetmap.org/wiki/JOSM/Validator) and the [LearnOSM Guide](http://learnosm.org/en/coordination/review/#data-validation) +より詳しい情報は[OSM Wiki](http://wiki.openstreetmap.org/wiki/JOSM/Validator) や [LearnOSM Guide](http://learnosm.org/en/coordination/review/#data-validation) も参照ください。 ## Overpass Turbo -You can quickly query and visualize OSM data live using **[Overpass Turbo](http://overpass-turbo.eu/s/ddp)**. +**[Overpass Turbo](http://overpass-turbo.eu/s/ddp)**を使うことで、現在のOSMデータを素早く検索し、状況を可視化することが可能です。 ![screenshot 2015-12-11 16 14 31](https://cloud.githubusercontent.com/assets/126868/11741952/4795d602-a022-11e5-8043-0e7014baebbc.png) -### Usage +### 使い方 + +- 対象のエリアまで[マップの表示位置を移動](http://overpass-turbo.eu)させるか、画面左側のツールから対象地域選択の矩形指定を行います +- クエリエディタに[Overpassクエリ](http://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL)を書くか、あるいは簡単なタグ検索であれば*ウィザード*から`highway=motorway or highway=trunk`のように指定を行います +- オプションで[MapCSS](http://wiki.openstreetmap.org/wiki/Overpass_turbo/MapCSS)を使って、結果表示にスタイルを適用することも可能です +- `実行`をクリックするとクエリが実行され、OSMデータの検索と結果表示が行われます +*TIP: デフォルトでは、小さなウェイが円として表示されます。ウェイとして表示させたい場合は、`設定 > 地図`から `POIなどの小さな地物を表示しない`をチェックしてください* -- [Browse the map](http://overpass-turbo.eu) to the area of interest or alternatively set a bounding box using the map tool on the left. -- Write an [Overpass Query](http://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL) in the query editor or use the *Wizard* for simple tag queries like `highway=motorway or highway=trunk` -- Optionally add a [MapCSS](http://wiki.openstreetmap.org/wiki/Overpass_turbo/MapCSS) style to visualize the results -- Hit `Run` to execute the query on the OSM data and display the results. -*Tip: By default small ways are rendered as circles. To fix this check the `Don't display small features as POIs` option from `Settings > Map`* +より詳しい使い方については [OSM Wiki](http://wiki.openstreetmap.org/wiki/Overpass_turbo), [Learn Overpass](http://osmlab.github.io/learnoverpass//en/) あるいはよく使われる [クエリサンプル](https://gist.github.com/ramyaragupathy/ffb3f225ccba4545398f)も参照してください。 -For more details check the [OSM Wiki](http://wiki.openstreetmap.org/wiki/Overpass_turbo), [Learn Overpass](http://osmlab.github.io/learnoverpass//en/) or some common [example queries](https://gist.github.com/ramyaragupathy/ffb3f225ccba4545398f). diff --git a/jp/becoming-a-power-mapper/index.md b/jp/becoming-a-power-mapper/index.md index a4f7d40..a04258e 100644 --- a/jp/becoming-a-power-mapper/index.md +++ b/jp/becoming-a-power-mapper/index.md @@ -10,8 +10,8 @@ sections: - Mapping - JOSM - Reference -description: These advanced topics will allow you to take your mapping skills to the next level. +description: マッピングスキルを一段向上させるための中上級者向けトピック image: becoming-a-power-mapper.svg --- -These advanced topics will allow you to take your mapping skills to the next level. \ No newline at end of file +マッピングスキルを一段向上させるための中上級者向けトピック \ No newline at end of file diff --git a/jp/getting-started/_posts/0000-01-01-getting-started.md b/jp/getting-started/_posts/0000-01-01-getting-started.md index 293dd57..b3b7804 100644 --- a/jp/getting-started/_posts/0000-01-01-getting-started.md +++ b/jp/getting-started/_posts/0000-01-01-getting-started.md @@ -2,117 +2,117 @@ title: Getting started --- -To [get started editing OpenStreetMap using JOSM](https://www.mapbox.com/blog/making-the-most-josm/), set up your work environment with the tools you would need. +[OpenStreetMap編集を始める](https://www.mapbox.com/blog/making-the-most-josm/)ために、まずは編集に必要となるツールと環境を整えましょう。 -## Setting up an OpenStreetMap Account +## OpenStreetMapアカウントの設定Setting up an OpenStreetMap Account -1. Go to OpenStreetMap.org and create an account: [https://www.openstreetmap.org/user/new](https://www.openstreetmap.org/user/new). -2. **IMPORTANT** add a picture of yourself to your profile. -3. Add a profile description like below: +1. OpenStreetMap.orgを表示し、アカウントを作成: [https://www.openstreetmap.org/user/new](https://www.openstreetmap.org/user/new) +2. **重要** プロフィール画面に写真を登録 +3. 以下を参考に、プロフィール文章を作成 -### Profile description +### Profile description　プロフィールの書き方 -It is useful to include: +以下の情報が含まれると有用です。 -- The areas you are interested in mapping; -- A nice message that allows others to get in touch; -- Links to your homepage/twitter etc that allows people to follow you. +- マッピングに興味があるエリア +- 他のユーザからの連絡を受け入れることを示すナイスな一言 +- ホームページやTwitterなど、他のユーザがあなたのことを知るために手掛かりとなるリンク -*(format in [Markdown]( http://en.wikipedia.org/wiki/Markdown))* +* (記載は[Markdown](http://en.wikipedia.org/wiki/Markdown)形式で行います)* -Here is a good example: +以下は良いプロフィールの一例です。 ![osm-profile-description-example]({{site.baseurl}}/images/osm-profile-description-example.png) -## Installing JOSM +## JOSMのインストール -We are using the Java OpenStreetMap Editor (JOSM) for most tasks. Here's how to get set up. +ここでは多くのタスクをJava OpenStreetMap Editor (JOSM)を使って行います。以下の手順でセットアップしてください。 -**1. Download and install JRE** +**1. JREのダウンロードとインストール** -JOSM requires the Java Runtime Environment - JRE. [Download and install JRE]( http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html). +JOSMはJava Runtime Environment - JREを必要とします。[JREのダウンロードとインストール]( http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html)を行います。 -**2. Download JOSM** +**2. JOSMのダウンロード** -Go to the [JOSM website](https://josm.openstreetmap.de/wiki/Download) to download the `tested` version. Place it in a common location for applications on your operating system. +[JOSMのウェブサイト](https://josm.openstreetmap.de/wiki/Download)を表示し、 `テスト済み`バージョンをダウンロードしてください。利用中のOS環境に合わせて、アプリケーションの配置場所としてよく使われる場所に移動させてください。 - OSX: `/Applications/` - Windows: `C:\Program Files\` -**3. Open JOSM** +**3. JOSMを起動** -Open the JOSM application you downloaded with a double click. +ダウンロードしたJOSMアプリケーションをダブルクリックすると起動します。 -If you want JOSM to use more memory and you're using [Linux](http://wiki.openstreetmap.org/wiki/JOSM/Linux) you can also run it with: +JOSMへのメモリ割り当てを多くする場合、[Linux環境](http://wiki.openstreetmap.org/wiki/JOSM/Linux)であれば以下のコマンドでも起動可能です ~$ java -Xmx1024M -DproxyHost=$PROXY -DproxyPort=8080 -jar josm-tested.jar -Once JOSM is up and running it looks like this. Go find the **Preferences** dialog, you'll need it for the next couple of steps. You can access it from under the light switch icon. +JOSMが起動すると、以下のような画面が表示されます。**設定/Preference**ダイアログを選択し、次のステップに進んでください。ダイアログは証明スイッチの形をしたアイコンの下にあります。 ![josm-preferences]({{site.baseurl}}/images/josm-preferences.png) -**4. Enable expert mode** +**4. 上級者モードの有効化** -Open the **Preferences** dialog and enable **Expert mode**. +**設定**ダイアログを開き、 **上級者モード**を有効化します。 ![check-expert-mode]({{site.baseurl}}/images/check-expert-mode.png) -**5. Add user and password** +**5. ユーザ名とパスワードの設定** -Now it's time to connect to OpenStreetMap. Add the user name and password of the account you created on OpenStreetMap to JOSM. +OpenStreetMapへの接続を行います。あなたがOpenStreetMapで取得したユーザ名とパスワードをJOSMに入力します。 ![set-osm-username-and-password]({{site.baseurl}}/images/set-osm-username-and-password.png) -Now you should be able to retrieve data from OpenStreetMap by clicking on the button with the green down error in the top left: +これでOpenStreetMapからデータをダウンロードすることができるようになりました。画面左上の緑色の矢印ボタンをクリックするとダウンロードを行うことができます。 ![download-data]({{site.baseurl}}/images/download-data.gif) -**6. Enable Remote Control** +**6. 遠隔コントロールの有効化** -Remote control allows you to launch JOSM directly from the map on OpenStreetMap.org. To enable Remote Control, check this box in the settings: +遠隔コントロールを有効化することで、OpenStreetMap.orgの地図表示からJOSMを直接起動することができるようになります。遠隔コントロールを有効化するには、設定にある以下のボックスをチェックしてください。 ![enable-remote-control]({{site.baseurl}}/images/enable-remote-control.png) -Also check the **Download objects to a new layer** option. Now you should be able to retrieve data directly starting on OpenStreetMap.org like this: +その際、**オブジェクトを新規レイヤーでダウンロードする**のオプションもチェックしておきましょう。これでOpenStreetMap.orgから直接データをダウンロードし、編集作業を開始する準備が整ったはずです。 ![retrieve-data]({{site.baseurl}}/images/retrieve-data.gif) -**7. Increasing the allocated memory for JOSM** +**7. JOSMの割り当てメモリを追加** -By default JOSM is allocated with 247-1024 MB of memory depending on the operating system. When JOSM reaches its maximum handling limit it pops up an error highlighting `JOSM is out of memory` +JOSMはOS環境により、デフォルトで247～1024MBのメモリを割り当てる設定になっています。JOSMがメモリの利用可能上限に近づくと、以下のポップアップとともに `JOSMのメモリ不足`エラーが表示されます。 ![increasing memory]({{site.baseurl}}/images/increasing-memory.png) -To get rid of this error increase the default allocated memory for JOSM by following [these steps](https://gist.github.com/jothirnadh/00352fff58ce2628cc4f#supply-parameters). If you are not sure of fixing this, do contact someone from the data team. +このエラーを回避するには、[こちらの手順](https://gist.github.com/jothirnadh/00352fff58ce2628cc4f#supply-parameters)に従い、JOSMへのメモリ割り当てを増やしてください。やりかたがよくわからない場合は、Mapboxのデータチームの誰かに問い合わせてください。 -## Using a gaming mouse +## ゲーミングマウスの利用 -Using a gaming can increase your productivity by assigning shortcuts to common mapping tasks. This section outlines the basic configuration to use a gaming in JOSM. +ゲーミングマウスを使い、よく使うマッピング動作のショートカットを登録しておくことで、作業効率が向上します。この項目では、JOSMでゲーミングマウスを使うための基本的な設定の概要を解説します。 -**Systems:** Linux and Mac +**システム:** Linux and Mac -**Equipment:** Razer Gaming mouse +**利用するマウス:** Razer Gaming mouse -**General guidelines:** Increase mouse speed in `System Preferences> Mouse` for Mac +**全般的なガイドライン:** Macの場合、`システム設定 > マウス`からマウスの速度を早くする -**Example Feature** +**機能の例** -**Buildings** +**建物** -**Configure gaming mouse and keyboard** +**ゲーミングマウスとキーボードの設定** -1. Install Razer Naga config software: https://www.razerzone.com/synapse/ -2. Create an account in razer ID: https://razer-id.razerzone.com/new -3. Build your profile using your email id -4. Configure the mouse: +1. Razer Naga config softwareをインストール: https://www.razerzone.com/synapse/ +2. razer IDでアカウント作成: https://razer-id.razerzone.com/new +3. メールアドレスを使ってプロファイルを作成 +4. マウスを設定: -**Common shortcuts essential to configure in your gaming mouse for buildings**: Enter, Extrude (`X`), building tracing (`B`), upload and download data to OSM (use the default keyboard shortcuts in your JOSM). +**建物を描く際にゲーミングマウスに設定しておくとよいショートカット**: Enter, Extrude (`X`), building tracing (`B`), OSMのデータアップロードとダウンロード (JOSMのデフォルトキーボードショートカットを利用). -**Good to have**: Join and merge nodes/ways (`J` and `M`), select overlapping ways (`I`), join overlapping areas (`Shift + J`), Split objects (`Alt + X`) +**登録推奨**: Join and merge nodes/ways (`J` and `M`), select overlapping ways (`I`), join overlapping areas (`Shift + J`), Split objects (`Alt + X`) -**Note**: Pattern to follow in setting up your mouse: +**注意事項**: マウスの設定例: -**Left hand (shortcuts in the keyboard)**: +**左利き (キーボードショートカット設定)**: * Upload @@ -122,7 +122,7 @@ Using a gaming can increase your productivity by assigning shortcuts to common m * Rotate -**Right hand (shortcuts in your mouse)**: +**右利き (マウスへのショートカット設定)**: * Enter @@ -138,6 +138,6 @@ Using a gaming can increase your productivity by assigning shortcuts to common m * Join overlapping ways (shift+J) - Configure any other shortcut according to the mapper choices. - -**Note**: For mapping other features like roads and to fix task, create separate configurations with the shortcuts required only for those features. +　マッパーの好みに応じて他のショートカットも設定ください。 + +**注意事項**: 道路の修正や、to fixを使ったタスク作業を行う場合、それらの地物に対応したショートカット・プロファイルを別途設定しておくことを推奨 diff --git a/jp/getting-started/index.md b/jp/getting-started/index.md index 89512b3..74e5b6a 100644 --- a/jp/getting-started/index.md +++ b/jp/getting-started/index.md @@ -3,6 +3,6 @@ title: Getting started layout: category order: 1 color: purple -description: To get started editing OpenStreetMap using JOSM, set up your work environment with the tools you would need. +description: JOSMを使ったOpenStreetMap編集をはじめる方法。必要となるツールと環境のセットアップ方法。 image: getting-started.svg --- diff --git a/jp/mapping-common-features/index.md b/jp/mapping-common-features/index.md index 6676654..a9a1b33 100644 --- a/jp/mapping-common-features/index.md +++ b/jp/mapping-common-features/index.md @@ -3,6 +3,6 @@ title: Mapping common features layout: category order: 5 color: orange -description: A walkthrough of how to create and edit the most common features on OpenStreetMap. +description: OpenStreetMapでよく作業することになる地物の作成と編集に関するチュートリアル。 image: mapping-common-features.svg --- diff --git a/jp/mapping-for-navigation/index.md b/jp/mapping-for-navigation/index.md index 00e5a9c..d39ebf7 100644 --- a/jp/mapping-for-navigation/index.md +++ b/jp/mapping-for-navigation/index.md @@ -3,8 +3,8 @@ title: Mapping for navigation layout: category order: 6 color: orange -description: Learn the guidelines to map different components to help build a great navigational engine. +description: 強力なナビゲーションエンジンを形作るさまざまな構成物を編集するためのガイドライン image: mapping-to-improve-navigation.svg --- -This guide was designed to help anyone add navigation features in OpenStreetMap from scratch. Let's dive in: +強力なナビゲーションエンジンを形作るさまざまな構成物を編集するためのガイドライン。さぁ始めましょう: diff --git a/jp/mapping-with-josm/index.md b/jp/mapping-with-josm/index.md index 8a9a973..6e39e17 100644 --- a/jp/mapping-with-josm/index.md +++ b/jp/mapping-with-josm/index.md @@ -3,6 +3,6 @@ title: Mapping with JOSM layout: category order: 4 color: darkblue -description: Get started mapping with the Java OpenStreetMap editor (JOSM) - a powerful and popular desktop editor for OpenStreetMap. +description: OpenStreetMap編集のパワフルでポピュラーなデスクトップエディタ Java OpenStreetMap editor (JOSM)を使ったマッピングについて image: mapping-with-josm.svg --- diff --git a/jp/osm-data-model/_posts/0000-01-01-osm-data-model.md b/jp/osm-data-model/_posts/0000-01-01-osm-data-model.md index 3fe68eb..2be7bee 100644 --- a/jp/osm-data-model/_posts/0000-01-01-osm-data-model.md +++ b/jp/osm-data-model/_posts/0000-01-01-osm-data-model.md @@ -2,64 +2,63 @@ title: The OpenStreetMap data model --- -In OpenStreetMap, each feature is described as one or more geometries (think for instance of a river's shape) with attached attribute data (think of the river's name). Geometries are described with three different *elements*: *nodes*, *ways* and *relations*. Attributes are described as *tags* that can be part of a node, a way or a relation. +OpenStreetMapにおいて、それぞれの地物は1つ以上のジオメトリ（位置情報。例えば、河川の形状そのものを思い浮かべてください）と、そこに付属する属性データ（例えば、河川の名称など）を保有しています。ジオメトリは3つの異なる *要素* で記述されます。*ノード/node*、*ウェイ/way*そして*リレーション/relation*です。属性は*タグ*として記述され、ノードやウェイ、リレーションの一部となることができます。 -Nodes are the equivalent of a point, ways are like lines that connect points and relations are collections of points or ways that represent a larger whole. This is easiest to understand with a couple of examples. +ノードはポイント/pointとも呼ばれ、ウェイはライン/lineと同様ノードが接続されたもの、リレーションはノードやウェイの集合体でより大きな地物全体を表現するために使われます。実際に例を見てみるのがわかりやすいでしょう。 -## Nodes +## ノード -Nodes are used to represent any kind of point type feature or just to designate a name for a point of interest in the vicinity. Here's a node representing a café: +ノードは、ポイント形状を持つあらゆる地物や、その地点のPOIの名前を指定するために使われます。以下のノードは、喫茶店を表しています。 ![node-example1]({{site.baseurl}}/images/node-example1.png) -and here's one representing New York City: + +以下はニューヨーク市を表している例です。 ![node-example-2]({{site.baseurl}}/images/node-example-2.png) -## Ways +## ウェイ -A way is a line feature *connecting two or more nodes* - like a road here: +ウェイは *2つ以上のノードが接続された* 線状の地物 - 例えば道路を表すために使われます。 ![way-example-1]({{site.baseurl}}/images/way-example-1.png) -If you close a way - by connecting its end to its start, you can map area type features like this building here: +ウェイを始点と終点で閉じた場合、建物などのエリアを表すことが可能です。 ![way-example-2]({{site.baseurl}}/images/way-example-2.png) -or this park: +以下は公園の例です ![way-example-3]({{site.baseurl}}/images/way-example-3.png) -Nodes are usually just the items that define a way. But nodes sitting on a way can have their own significance. In this example the node is part of 14th Street and R Street and it also denotes that there's a traffic light. - +ノードは通常、ウェイの一部を構成するための構成要素として使われます。しかし、ウェイの中に組み込まれたノードそれ自体が何らかの意味合いを持つことも可能です。この例では、ノードは14thストリートとRストリートの一部であり、なおかつこの場所に信号機があることも意味しています。 ![way-example-4]({{site.baseurl}}/images/way-example-4.gif) -## Tags +## タグ -Before we hop to the third element next to nodes and ways - relations, let's look at tags. You've seen them now already a couple of times in the examples above, like in this café node: +ノード、ウェイに続いてリレーションという3つめの要素の解説を行う前に、タグについて解説します。これまでに出てきた喫茶店の例などを見てみましょう。 ![osm-tag]({{site.baseurl}}/images/osm-tag.png) -Any point type feature is a node. Whether the node designates a café, a school, a fire hydrant, a tree, a park, a mountainpeak is entirely up to how the node is tagged. Any line type feature is a way. Whether the way is a road, a building, a lake, a railway, a cycleway is again, defined by how it is tagged. +ポイント形状の地物はノードと呼ばれます。喫茶店や学校、消火栓、木、公園、山頂などノードが表現できる地物は様々であり、どのようなタグを付与するかによってその内容は変わってきます。ライン形状の地物はすべてウェイと呼ばれます。道路や建物、湖沼、線路、自転車道など、そのウェイが何を表現するかはタグによって変わってきます。 -Tags can be on any element: on nodes, ways and relations. +タグは、ノード、ウェイ、リレーションといったすべての要素に付与することができます。 -## Relations +## リレーション -Relations are used to organize multiple nodes or ways into a larger whole. Take here for instance the bus route 23 running through 3 different ways. +リレーションは複数のノードやウェイの集合体であり、大きな地物全体を表現するために使われます。例として、3つの異なるウェイから成立する、バス経路23系統を見てみましょう。 ![relations]({{site.baseurl}}/images/relations.gif) -The type of relation that you'll probably deal most with describes an area with punched out holes - a so called *multipolygon*. Here is an example of a multipolygon building with a yard. It consists of 2 ways with each multiple nodes. One way describes the *outer* wall of the building, the other one the *inner* wall. The ways are part of a relation of the type `type=multipolygon`, the outer way has the role `outer` and the and the inner way has the role `inner`. Note: the `building=yes` tag is on the relation (not on the way). - -Your OpenStreetMap editor will take care of creating multipolygons for you so don't worry if this seems dense for now. If you need to fix a multipolygon, this is a good section to come back and review. +編集中にもっともよく見かけるリレーションは、穴の開いたエリアを表現するために使われる *マルチポリゴン/multipolygon*と呼ばれるリレーションと思われます。以下は中庭を持ったマルチポリゴンの建物の例です。この例では、複数のノードを持ったウェイが2つ使われています。1つのウェイは*外側/outer*の建物の壁を表し、もうひとつは*内側/inner*の壁を表現しています。2つのウェイは`type=multipolygon`というタイプのリレーションの一部で、外側のウェイは `outer`のロール、内側のウェイは `inner`のロールを割り当てられています。注意：`building=yes`のタグは、リレーションに対して付与されています（ウェイではありません）。 +現在利用可能なOpenStreetMapエディタの多くはマルチポリゴンの作成機能を持っていますので、内容を濃く感じても心配する必要はありません。マルチポリゴンを編集することになった場合、またもう一度この文章を読み直してみてください。 ![multipolygon]({{site.baseurl}}/images/multipolygon.gif) -## Further reading +## 参考文献 -To learn more about the OpenStreetMap data structure, take a look at these resources: +OpenStreetMapのデータ構造についてより詳しい解説は以下の資料を参照してください。 - OpenStreetMap Elements http://wiki.openstreetmap.org/wiki/Elements - Multipolygons http://wiki.openstreetmap.org/wiki/Relation:multipolygon \ No newline at end of file diff --git a/jp/osm-data-model/index.md b/jp/osm-data-model/index.md index b0b6ef8..b3a5dd4 100644 --- a/jp/osm-data-model/index.md +++ b/jp/osm-data-model/index.md @@ -3,6 +3,6 @@ title: The OpenStreetMap data model layout: category order: 3 color: blue-light -description: In OpenStreetMap, each feature is described as one or more geometries with attached attribute data. +description: OpenStreetMapでの地物は、1つ以上の位置情報と属性データを使って表現されます。 image: the-openstreetmap-data-model.svg --- diff --git a/jp/sources/_posts/0000-01-01-sources.md b/jp/sources/_posts/0000-01-01-sources.md new file mode 100644 index 0000000..d9ac051 --- /dev/null +++ b/jp/sources/_posts/0000-01-01-sources.md @@ -0,0 +1,58 @@ +--- +title: Sources +--- + +ストリートや建物、川や町そのものといった現実世界の地物を思い浮かべてください。OpenStreetMapに描かれているそれぞれの地物は、現実世界を観察した結果の産物です。観察行為は現地調査やGPSなどのセンサー、衛星写真、写真に映った光景から行うこが可能で、場合によってはサードパーティの団体が保有するデータのコピーなども行うことができます。 _適切な_ 情報源を選択し、それらデータの _現在状況_ をOpenStreetMapに記載することは非常に重要であり、それこそが素晴らしいマッピングの定義と言えます。 + +## 適切な情報源 + +マッピングを行う際には、マッピングの元情報として使う内容が適切であるかどうかを確認することが非常に重要です。その重要性は、トレースであってもデータのインポートであっても変わりません。私たちが適切に利用することができない情報源からの情報追加は行うことができません。もし利用しようとする情報源が使ってよいかどうかよくわからない場合、その情報源は利用しないでください。 + +OpenStreetMapに情報を追加する際に利用可能な情報源の例は以下の通りです。 + +- 現地調査などを通じてあなたが知っている **地元知識** +- OpenStreetMapに対して明示的にトレースの許可が与えられた **衛星写真**。例えば、BingやMapbox Satelliteなどが該当します +- **[Mapillary](http://mapillary.com/)**に掲載された写真 +- 店舗の住所文字列など、ウェブサイトに掲載された **原典情報** (訳註：日本でも事実情報として著作性はありませんが、念のためとして文字情報の転記も嫌うマッパーは少なくないことに注意ください) +- **ライセンス互換性のあるデータセット**、例えば[Wikidata](http://www.wikidata.org/wiki/Wikidata:Main_Page)など - 互換性のあるライセンスとは、[CC0](https://creativecommons.org/publicdomain/zero/1.0/)か、あるいは[open definition](http://opendefinition.org/)に記載がありなおかつ継承条件（share-alike）を持たないライセンス、を指します。（訳註：この記載は誤りです。CC-BY4.0であってもODbLとのライセンス互換はありません。詳しくはOSMFのブログを参照し、データ配布元から明示的な利用許可を得てください。CC0は許諾なく利用可能です） + +**以下の情報源は利用しないでください** + +- 商業用地図 - ほとんどの種類の紙地図、あるいは例えばGoogle Maps（Google Street Viewを含む） +- 明示的に許可が指定されていない情報源 +- その情報源が利用可能かどうか、判断に迷う場合 + + +## グループ調査 + +OpenStreetMapには、オリジナルの、つまりコミュニティメンバーによって収集されたデータが多く含まれています。こうしたデータはほとんどが現地調査の結果であり、調査とは別工程として、リモートマッピングを行う際に使われるものと同じエディタを使ってOpenStreetMapへの入力が行われます。以下は現地調査でよく使われるテクニックです。 + +- [GPSトラックの収集](http://wiki.openstreetmap.org/wiki/Recording_GPS_tracks) +- [印刷した地図を使ってのデータ収集](http://wiki.openstreetmap.org/wiki/Field_Papers) +- [Mapillary](https://www.mapillary.com/osm.html)など、位置情報付きの写真を利用 + +OpenStreetMapを始めるにあたって最も簡単な方法は衛星画像からのトレースですが、現地を調査した結果として得られるデータはその地域をマップするにあたって非常に価値が高く、なおかつ収集に最も多くの時間を必要とします。 + +![mapping-party]({{site.baseurl}}/images/mapping-party.png) + +*Ônibus Hackerと共にリオデジャネイロで2012年に開かれたマッピングパーティ* + + +## 衛星写真のトレース + +高解像度の衛星写真が利用可能になったことにより、OpenStreetMapのデータボリュームは爆発的に増加しました。画像を使った地物のトレースなど、OpenStreetMapへのデータ投入は飛躍的に速く簡潔になっています。現地調査の手法と比較して、衛星写真のトレースは非常に短時間で実施することができます。ただし、道路の名称や地名、学校や喫茶店などPOIに関する情報などは写真から読み取ることができませんので、すべての情報が得られるわけではありません。実際のところ、OpenStreetMapを構成しているデータの多くはトレースと現地調査の双方を組み合わせる　- 最初に画像から得られる情報をなるべくトレースしておき、現地調査を行って詳細を追記するという手法で作成されています。 + +画像を使ってどのような分析が行われているかは、世界銀行が提供している [衛星画像に関する現状](http://satsummit.github.io/landscape/) を参照ください。 + +![satellite-tracing]({{site.baseurl}}/images/satellite-tracing.gif) + +## サードパーティ・データ + +現在、行政や政府からを中心として、サードパーティによる様々なデータが利用可能になっています。もしそうしたデータが、ライセンス的に互換のある状態で提供されており、なおかつ品質もよいものであれば、それらを地図データの改善に利用することが可能です。インポートは既存のOpenStreetMapデータとの結合やデータクレンジングが必要でなり、複雑な手順が取られます。また、現地調査や衛星画像のトレースによるOpenStreetMapへのデータ編集は他のコミュニティメンバーとの調整を行わなくても実施できますが、インポートを行う際には正式な作業提案とコミュニティによる相互レビューが必須となります。これまでに行われたインポートは、私たちが主導したニューヨーク市の建物と住所情報のインポートや、アメリカで行われたアメリカ国勢調査局の[TIGERデータ](http://wiki.openstreetmap.org/wiki/TIGER)インポートが例としてあげられます。以下のアニメーションは、[ニューヨーク市で行われたデータインポート作業](https://www.mapbox.com/blog/nyc-buildings-openstreetmap/)の進捗を表しています。 + +![data-import](https://cloud.githubusercontent.com/assets/6770741/11623986/9baad488-9cf6-11e5-9922-0511f4971a80.gif) + + +## GPSプローブデータ + +GPSトラックの収集については現地調査テクニックの項目で一度触れています。そうした手法以外に、例えば車両からシステム的に収集される大量のGPSデータも使われることがあります。そうしたデータは集計処理が行われ、地図上で書かれていなかったり位置がずれたりしている道路の存在や、間違った方向の一方通行データ、平均速度や最高速度の推定に利用されます。この手法は非常に高度な技術を要しますが、インポートとは違ってデータを直接的に編集するわけではないけれどもOpenStreetMapのデータを改善するための間接的な手法のひとつとしてここで紹介しておきます。 diff --git a/jp/sources/index.md b/jp/sources/index.md new file mode 100644 index 0000000..75a72d2 --- /dev/null +++ b/jp/sources/index.md @@ -0,0 +1,8 @@ +--- +title: Sources +layout: category +order: 2 +color: pink +description: マッピングを行う際には、マッピングの元情報として使う内容が適切であるかどうかを確認することが非常に重要で、それこそが素晴らしいマッピングの定義と言えます。 +image: sources.svg +--- diff --git a/jp/validating-osm/index.md b/jp/validating-osm/index.md index 1bf1b5c..7463b04 100644 --- a/jp/validating-osm/index.md +++ b/jp/validating-osm/index.md @@ -3,6 +3,6 @@ title: Validating OpenStreetMap layout: category order: 8 color: orange -description: A walkthrough of how to detect, inspect and fix potentially harmful changes in OpenStreetMap. +description: OpenStretMapにおいて害のある編集を発見し、調査し、修正する方法に関するチュートリアル。 image: validating-osm.svg --- From 935364e77304effd54373055c230030ef2b081d7 Mon Sep 17 00:00:00 2001 From: nyampire Date: Thu, 8 Jun 2017 09:48:35 +0900 Subject: [PATCH 48/66] add translation.yml for Japanese --- _data/translations.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/_data/translations.yml b/_data/translations.yml index 0e493ac..c8b4445 100644 --- a/_data/translations.yml +++ b/_data/translations.yml @@ -5,33 +5,44 @@ - en: guide es: guía + jp: ガイド - en: Mapping es: Mapeando + jp: マッピング - en: Mapping with es: Mapeando con + jp: マッピングツール - en: back to es: de regreso + jp: 戻る - en: Next es: Siguiente + jp: 進む - en: This is the last guide in this category. es: Esta es la última guía en esta categoría. + jp: 次の記事はありません - en: Mapping guides es: Guías de mapeo + jp: マッピングガイド - en: Search es: Buscar + jp: 検索 - en: results for es: resultados para + jp: 件 - en: Clear search es: Limpia la búsqueda + jp: 検索結果をクリア - en: Read this guide es: Lee esta guía + jp: ガイドを表示 From 1bffdf321a74bf51bf7feb22633ce2ae5b591663 Mon Sep 17 00:00:00 2001 From: nyampire Date: Sat, 10 Jun 2017 17:08:53 +0900 Subject: [PATCH 49/66] add _includes/intro/jp.html --- _includes/intro/jp.html | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 _includes/intro/jp.html diff --git a/_includes/intro/jp.html b/_includes/intro/jp.html new file mode 100644 index 0000000..8442bad --- /dev/null +++ b/_includes/intro/jp.html @@ -0,0 +1,3 @@ +

OpenStreetMapは自由で編集可能な世界地図であり、世界各国から参加しているボランティアの手によって作成され、メンテナンスが行われています。私達のMapbox Streetは、OpenStreetMapが提供する全世界の道路や建物、地名などのオープンデータを利用して作成されている、カスタマイズ可能な地図レイヤです。アカウントの作成と編集は OpenStreetMap.orgから、数分程度で開始することができます。

+ +

私達のデータチームは、品質分析や皆様からのフィードバックをもとに、OpenStreetMapを更新しています。私達の活動はオープンに公開して行っています。参加はどなたでも可能です。マッピングプロジェクトへの参加は、オープン状態になっているIssueからお願いします。また、マッピングのベストプラクティスガイドも公開中です。

\ No newline at end of file From 082ca800fc60fcf63c4646afe5b31be17d22ec32 Mon Sep 17 00:00:00 2001 From: nyampire Date: Sat, 10 Jun 2017 21:04:38 +0900 Subject: [PATCH 50/66] add jp/index.md --- jp/index.md | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 jp/index.md diff --git a/jp/index.md b/jp/index.md new file mode 100644 index 0000000..98de229 --- /dev/null +++ b/jp/index.md @@ -0,0 +1,4 @@ +--- +layout: home +title: OpenStreetMapマッピング +--- From 2a0a47f87751fb234a882574a8e56cdfd7b65115 Mon Sep 17 00:00:00 2001 From: Katy DeCorah Date: Tue, 13 Jun 2017 09:50:39 -0400 Subject: [PATCH 51/66] new language fixes (#302) --- CONTRIBUTING.md | 1 + _config.yml | 5 +++++ _includes/intro/jp.html | 0 _layouts/default.html | 11 +++++++--- _layouts/home.html | 2 +- en/index.html | 9 ++++++++ site.css | 4 +--- test/mapping.test.js | 46 ++++++++++++++++++++++++----------------- 8 files changed, 52 insertions(+), 26 deletions(-) create mode 100644 _includes/intro/jp.html create mode 100644 en/index.html diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d760780..fd6bd4b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -104,5 +104,6 @@ The guides are also offered in Spanish. All files are found under the `es/` fold 1. Create a folder with the language abbreviation. For example, `fr/` for French and `de/` for German. 2. Update `_config.yml` to add the new language to the `defaults`. Follow the pattern of the English and Spanish scopes. 3. Update `translations.yml` and add to each set of words the new translation using the language abbreviation from step 1. If you don't add a translation, it will appear in English. +4. Add the new language abbreviation and name of language to `languages` in `_config.yml`. Follow the patterns mentioned above in creating categories and posts. diff --git a/_config.yml b/_config.yml index d4d6584..e00802d 100644 --- a/_config.yml +++ b/_config.yml @@ -11,6 +11,11 @@ exclude: - CONTRIBUTING.md - test +languages: + en: English # abbreviation: Name of native language + es: Español + #jp: 日本語 + defaults: - scope: path: "" # an empty string here means all files in the project diff --git a/_includes/intro/jp.html b/_includes/intro/jp.html new file mode 100644 index 0000000..e69de29 diff --git a/_layouts/default.html b/_layouts/default.html index 1110973..e6fb001 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -93,7 +93,7 @@

Mapbox OpenStreetMap

-
+
{% include svgs/logo.svg %} @@ -102,8 +102,13 @@

{{page.title}}

{% include translate.html swap='Mapping guides' lang=page.lang %}

- {% if lang == 'en' %}Español{% else %}English{% endif %} - +
+ {% for lang in site.languages %} + {% if lang[0] != page.lang %} + {{lang[1]}} + {% endif %} + {% endfor %} +
diff --git a/_layouts/home.html b/_layouts/home.html index df163d9..ff38644 100644 --- a/_layouts/home.html +++ b/_layouts/home.html @@ -18,7 +18,7 @@ {% assign langDir = page.lang | append: '/' %} {% assign title = page.dir | downcase | replace: langDir,'' | replace: '/','' %} - {% assign guideCount = 0 %}{% for post in site.categories[title] %}{% assign guideCount = guideCount | plus: 1 %}{% endfor %} + {% assign guideCount = 0 %}{% for post in site.categories[title] %}{% if post.lang == page.lang %}{% assign guideCount = guideCount | plus: 1 %}{% endif %}{% endfor %}
diff --git a/en/index.html b/en/index.html new file mode 100644 index 0000000..707eeed --- /dev/null +++ b/en/index.html @@ -0,0 +1,9 @@ +--- +--- + + + + + + + \ No newline at end of file diff --git a/site.css b/site.css index 273cccf..bf8efd2 100644 --- a/site.css +++ b/site.css @@ -55,7 +55,6 @@ h1, h2 { } .icon.heart:before { - content: "\e63e"; margin-top: -1px; width: 30px; height: 30px; @@ -117,8 +116,7 @@ svg { } #search .icon.search:before { - content: "\e66f"; - color: #A1ABD0; + color: #A1ABD0; } #guide-search .on { diff --git a/test/mapping.test.js b/test/mapping.test.js index ef55d37..b571ddc 100644 --- a/test/mapping.test.js +++ b/test/mapping.test.js @@ -22,6 +22,14 @@ getES.forEach(function(e) { }); // combine paths + spanish paths var paths = paths.concat(es); +// get jp dirs +var getJP = getDir('jp'); +var jp = []; +getJP.forEach(function(e) { + jp.push('jp/' + e); +}); +// combine paths + jp paths +var paths = paths.concat(jp); var categories = []; var posts = []; @@ -33,7 +41,7 @@ paths.forEach(function(dir) { categories.push(dir +'/' + file); } else if (file == '_posts') { // get _posts/ var post_path = dir + '/' + file; - + // get any subdirs and then files var foundSubDirs = getDir(post_path); if (foundSubDirs) { @@ -45,9 +53,9 @@ paths.forEach(function(dir) { posts.push(this_path +'/' + file); } }); - }); + }); } - + // get the files post_path = fs.readdirSync(post_path).filter(function(file) { var isFile = fs.statSync(path.join(post_path, file)).isFile(); @@ -55,7 +63,7 @@ paths.forEach(function(dir) { posts.push(post_path +'/' + file); } }); - + } else if (file[0] != '.' && !isFile) { // get folder/_posts/ var post_path = dir + '/' + file + '/_posts'; post_path = fs.readdirSync(post_path).filter(function(file) { @@ -78,11 +86,11 @@ function getDir(srcpath) { function readPost(filename) { var buffer = fs.readFileSync(filename), file = buffer.toString('utf8'); - + try { var parts = file.split(/---\s*[\n^]/), frontmatter = parts[1]; - + return { name: filename, file: file, @@ -97,16 +105,16 @@ function readPost(filename) { function readData(dir, filename) { var buffer = fs.readFileSync(dir + filename), file = buffer.toString('utf8'); - + try { - + return { name: filename, file: file, metadata: jsyaml.load(file) }; } catch(err) {} - + } //////////////////////////////////////////////// @@ -117,12 +125,12 @@ function readData(dir, filename) { categories.forEach(function(post){ var file = readPost(post); - + var metadata = file.metadata; var content = file.content; - + test(post, function(t) { - + t.ok(metadata.title,'must have a title'); t.equal(metadata.layout,'category','layout must equal "category"'); t.ok(metadata.color,'must have a color'); @@ -130,17 +138,17 @@ categories.forEach(function(post){ t.equal(typeof metadata.order,'number','order must be a number'); t.ok(metadata.description,'must have a description'); t.ok(metadata.image,'must have an image'); - + t.equal(post.indexOf(' '),-1,'file name must not contain spaces'); t.equal(post.toLowerCase(),post,'file name must be lowercase'); if (!post.match('index.md')) { t.fail('file name must be index.md'); } - + if (metadata.section) { t.equal(typeof metadata, 'array', 'section must be formatted as a list'); } - + t.end(); }); }); @@ -154,19 +162,19 @@ categories.forEach(function(post){ posts.forEach(function(post){ var file = readPost(post); - + var metadata = file.metadata; var content = file.content; - + test(post, function(t) { - + t.ok(metadata.title,'must have a title'); t.equal(post.indexOf(' '),-1,'file name must not contain spaces'); t.equal(post.toLowerCase(),post,'file name must be lowercase'); if (!post.match('0000-01-')) { t.fail('file name must start with 0000-01-'); } - + t.end(); }); }); From 50b69dc4fdba9ff47ee38bce609e9872403223b4 Mon Sep 17 00:00:00 2001 From: nyampire Date: Tue, 13 Jun 2017 23:25:11 +0900 Subject: [PATCH 52/66] enable Japanese translation --- _config.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index e00802d..d4882ce 100644 --- a/_config.yml +++ b/_config.yml @@ -14,7 +14,7 @@ exclude: languages: en: English # abbreviation: Name of native language es: Español - #jp: 日本語 + jp: 日本語 defaults: - scope: @@ -54,4 +54,4 @@ defaults: path: "jp" type: "posts" values: - lang: "jp" \ No newline at end of file + lang: "jp" From 70c2b7df13cdde02e9e0849d4dc18ede9f447fc7 Mon Sep 17 00:00:00 2001 From: nyampire Date: Tue, 13 Jun 2017 23:32:13 +0900 Subject: [PATCH 53/66] fix typo on Japanese translation --- .../_posts/0000-01-01-mapping-common-features.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md index 59f0622..4937235 100644 --- a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md +++ b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md @@ -21,7 +21,7 @@ title: Mapping common features 道路のトレース作業はたいへんシンプルです。JOSMでは **描画** (`Aキー`) 、iDでは **ライン** ツールを使って道路のコースに沿って線を描きます。道路を描く際には、適切な量のノードを配置するのがコツです。ノードの量が少なすぎると道路の線が雑になります。逆に、ノードの量が多すぎると後の編集で道路を修正することが困難になります。 -以下の図を見てみてください。左の図はノードの数が少なすぎる状態で、線がギザギザになっています。マンな中の図はノードが多すぎて、冗長な情報が含まれています。右の図が最も望ましいトレース状態です。 +以下の図を見てみてください。左の図はノードの数が少なすぎる状態で、線がギザギザになっています。中央の図はノードが多すぎて、冗長な情報が含まれています。右の図が最も望ましいトレース状態です。 ![mapbox guide big](https://cloud.githubusercontent.com/assets/693781/10158378/f3a4b3fc-6691-11e5-9738-58ad86a5a525.png) @@ -69,19 +69,19 @@ title: Mapping common features OpenStreetMap Wiki: [Key:oneway](http://wiki.openstreetmap.org/wiki/Key:oneway) -### 方向転回制限 +### 進行方向制限 -方向転回制限は、特定の方向へ曲がることを不許可にするルールです。例えば、"右方向転回禁止"の道路標識は以下のようになります。 +進行方向制限は、特定の方向へ曲がることを不許可にするルールです。例えば、"右折禁止"の道路標識は以下のようになります。 ![](https://farm3.staticflickr.com/2900/14360050862_ef35f7ffa8_b.jpg) -JOSMを使って方向転回制限をマップするには、 **turnrestrictions** プラグインを使用します。プラグインを有効化すると、 `ウィンドウ > 方向転回制限` メニューウィンドウに方向転回制限用のパネルが追加されます。 +JOSMを使って進行方向制限をマップするには、 **turnrestrictions** プラグインを使用します。プラグインを有効化すると、 `ウィンドウ > 進行方向制限` メニューウィンドウに進行方向制限用のパネルが追加されます。 -有効化を行い、方向転回制限の新規作成や既存設定の編集をパネルから行ってみましょう。以下はシンプルな "右方向転回禁止" の作成例です。右方向転回が禁止されている元の道路を "from" オブジェクトとして選択し、その道路から展開できない先の道路を "to" オブジェクトとして選択することによって、この制限設定が "右方向転回禁止" を意味するようになります。turnrestrictionsダイアログを閉じようとすると "via" オブジェクトが指定されていないという警告が表示されます。その設定は必須というわけではありませんが、グッドプラクティスではありますので、念の為指定をしておきましょう。 +有効化を行い、進行方向制限の新規作成や既存設定の編集をパネルから行ってみましょう。以下はシンプルな "右折禁止" の作成例です。右折が禁止されている元の道路を "from" オブジェクトとして選択し、その道路から展開できない先の道路を "to" オブジェクトとして選択することによって、この制限設定が "右折禁止" を意味するようになります。turnrestrictionsダイアログを閉じようとすると "via" オブジェクトが指定されていないという警告が表示されます。その設定は必須というわけではありませんが、グッドプラクティスではありますので、念の為指定をしておきましょう。 ![](https://s3.amazonaws.com/f.cl.ly/items/24173W1U033a193q2l1F/turn.gif) -方向転回制限はあっという間に指定が複雑化します。そのため、制限を作成したり編集したりする場合は、OpenStreetMap wikiのドキュメントはあらかじめすべて読み、理解するようにしてから実施するようにしてください。 +進行方向制限はあっという間に指定が複雑化します。そのため、制限を作成したり編集したりする場合は、OpenStreetMap wikiのドキュメントはあらかじめすべて読み、理解するようにしてから実施するようにしてください。 *Video: [How to edit turn restrictions in JOSM](https://www.youtube.com/watch?v=0SdixDJAED0)* From dd5b8a28fcc38f5c84870d618c6ed155bfeaa479 Mon Sep 17 00:00:00 2001 From: Satoshi IIDA Date: Wed, 14 Jun 2017 00:37:49 +0900 Subject: [PATCH 54/66] fix translation.yml to fit Japanese translation (#301) * add translation.yml for Japanese * add _includes/intro/jp.html * add jp/index.md * enable Japanese translation * fix typo on Japanese translation --- _config.yml | 4 ++-- _data/translations.yml | 11 +++++++++++ _includes/intro/jp.html | 3 +++ jp/index.md | 4 ++++ .../_posts/0000-01-01-mapping-common-features.md | 12 ++++++------ 5 files changed, 26 insertions(+), 8 deletions(-) create mode 100644 jp/index.md diff --git a/_config.yml b/_config.yml index e00802d..d4882ce 100644 --- a/_config.yml +++ b/_config.yml @@ -14,7 +14,7 @@ exclude: languages: en: English # abbreviation: Name of native language es: Español - #jp: 日本語 + jp: 日本語 defaults: - scope: @@ -54,4 +54,4 @@ defaults: path: "jp" type: "posts" values: - lang: "jp" \ No newline at end of file + lang: "jp" diff --git a/_data/translations.yml b/_data/translations.yml index 0e493ac..c8b4445 100644 --- a/_data/translations.yml +++ b/_data/translations.yml @@ -5,33 +5,44 @@ - en: guide es: guía + jp: ガイド - en: Mapping es: Mapeando + jp: マッピング - en: Mapping with es: Mapeando con + jp: マッピングツール - en: back to es: de regreso + jp: 戻る - en: Next es: Siguiente + jp: 進む - en: This is the last guide in this category. es: Esta es la última guía en esta categoría. + jp: 次の記事はありません - en: Mapping guides es: Guías de mapeo + jp: マッピングガイド - en: Search es: Buscar + jp: 検索 - en: results for es: resultados para + jp: 件 - en: Clear search es: Limpia la búsqueda + jp: 検索結果をクリア - en: Read this guide es: Lee esta guía + jp: ガイドを表示 diff --git a/_includes/intro/jp.html b/_includes/intro/jp.html index e69de29..8442bad 100644 --- a/_includes/intro/jp.html +++ b/_includes/intro/jp.html @@ -0,0 +1,3 @@ +

OpenStreetMapは自由で編集可能な世界地図であり、世界各国から参加しているボランティアの手によって作成され、メンテナンスが行われています。私達のMapbox Streetは、OpenStreetMapが提供する全世界の道路や建物、地名などのオープンデータを利用して作成されている、カスタマイズ可能な地図レイヤです。アカウントの作成と編集は OpenStreetMap.orgから、数分程度で開始することができます。

+ +

私達のデータチームは、品質分析や皆様からのフィードバックをもとに、OpenStreetMapを更新しています。私達の活動はオープンに公開して行っています。参加はどなたでも可能です。マッピングプロジェクトへの参加は、オープン状態になっているIssueからお願いします。また、マッピングのベストプラクティスガイドも公開中です。

\ No newline at end of file diff --git a/jp/index.md b/jp/index.md new file mode 100644 index 0000000..98de229 --- /dev/null +++ b/jp/index.md @@ -0,0 +1,4 @@ +--- +layout: home +title: OpenStreetMapマッピング +--- diff --git a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md index 59f0622..4937235 100644 --- a/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md +++ b/jp/mapping-common-features/_posts/0000-01-01-mapping-common-features.md @@ -21,7 +21,7 @@ title: Mapping common features 道路のトレース作業はたいへんシンプルです。JOSMでは **描画** (`Aキー`) 、iDでは **ライン** ツールを使って道路のコースに沿って線を描きます。道路を描く際には、適切な量のノードを配置するのがコツです。ノードの量が少なすぎると道路の線が雑になります。逆に、ノードの量が多すぎると後の編集で道路を修正することが困難になります。 -以下の図を見てみてください。左の図はノードの数が少なすぎる状態で、線がギザギザになっています。マンな中の図はノードが多すぎて、冗長な情報が含まれています。右の図が最も望ましいトレース状態です。 +以下の図を見てみてください。左の図はノードの数が少なすぎる状態で、線がギザギザになっています。中央の図はノードが多すぎて、冗長な情報が含まれています。右の図が最も望ましいトレース状態です。 ![mapbox guide big](https://cloud.githubusercontent.com/assets/693781/10158378/f3a4b3fc-6691-11e5-9738-58ad86a5a525.png) @@ -69,19 +69,19 @@ title: Mapping common features OpenStreetMap Wiki: [Key:oneway](http://wiki.openstreetmap.org/wiki/Key:oneway) -### 方向転回制限 +### 進行方向制限 -方向転回制限は、特定の方向へ曲がることを不許可にするルールです。例えば、"右方向転回禁止"の道路標識は以下のようになります。 +進行方向制限は、特定の方向へ曲がることを不許可にするルールです。例えば、"右折禁止"の道路標識は以下のようになります。 ![](https://farm3.staticflickr.com/2900/14360050862_ef35f7ffa8_b.jpg) -JOSMを使って方向転回制限をマップするには、 **turnrestrictions** プラグインを使用します。プラグインを有効化すると、 `ウィンドウ > 方向転回制限` メニューウィンドウに方向転回制限用のパネルが追加されます。 +JOSMを使って進行方向制限をマップするには、 **turnrestrictions** プラグインを使用します。プラグインを有効化すると、 `ウィンドウ > 進行方向制限` メニューウィンドウに進行方向制限用のパネルが追加されます。 -有効化を行い、方向転回制限の新規作成や既存設定の編集をパネルから行ってみましょう。以下はシンプルな "右方向転回禁止" の作成例です。右方向転回が禁止されている元の道路を "from" オブジェクトとして選択し、その道路から展開できない先の道路を "to" オブジェクトとして選択することによって、この制限設定が "右方向転回禁止" を意味するようになります。turnrestrictionsダイアログを閉じようとすると "via" オブジェクトが指定されていないという警告が表示されます。その設定は必須というわけではありませんが、グッドプラクティスではありますので、念の為指定をしておきましょう。 +有効化を行い、進行方向制限の新規作成や既存設定の編集をパネルから行ってみましょう。以下はシンプルな "右折禁止" の作成例です。右折が禁止されている元の道路を "from" オブジェクトとして選択し、その道路から展開できない先の道路を "to" オブジェクトとして選択することによって、この制限設定が "右折禁止" を意味するようになります。turnrestrictionsダイアログを閉じようとすると "via" オブジェクトが指定されていないという警告が表示されます。その設定は必須というわけではありませんが、グッドプラクティスではありますので、念の為指定をしておきましょう。 ![](https://s3.amazonaws.com/f.cl.ly/items/24173W1U033a193q2l1F/turn.gif) -方向転回制限はあっという間に指定が複雑化します。そのため、制限を作成したり編集したりする場合は、OpenStreetMap wikiのドキュメントはあらかじめすべて読み、理解するようにしてから実施するようにしてください。 +進行方向制限はあっという間に指定が複雑化します。そのため、制限を作成したり編集したりする場合は、OpenStreetMap wikiのドキュメントはあらかじめすべて読み、理解するようにしてから実施するようにしてください。 *Video: [How to edit turn restrictions in JOSM](https://www.youtube.com/watch?v=0SdixDJAED0)* From 8720172e4cd684459bea69b9fde0a9febe113153 Mon Sep 17 00:00:00 2001 From: nyampire Date: Thu, 15 Jun 2017 12:43:59 +0900 Subject: [PATCH 55/66] Add more Japanese translation --- ...editing-saving-and-loading-josm-session.md | 24 +- .../0000-01-05-advanced-josm-customization.md | 8 +- .../josm/0000-01-06-advanced-mapping-guide.md | 69 ++- ...0000-01-07-fixing-common-mapping-issues.md | 25 +- .../0000-01-08-useful-overpass-queries.md | 18 +- .../0000-01-09-useful-osm-resources.md | 59 ++- .../_posts/0000-01-01-mapping-with-josm.md | 151 +++--- jp/sources/_posts/0000-01-01-sources.md | 3 +- .../_posts/0000-01-01-validating-osm.md | 492 +++++++++--------- 9 files changed, 419 insertions(+), 430 deletions(-) diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-03-editing-saving-and-loading-josm-session.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-03-editing-saving-and-loading-josm-session.md index 5f0e5f5..9cce645 100644 --- a/jp/becoming-a-power-mapper/_posts/josm/0000-01-03-editing-saving-and-loading-josm-session.md +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-03-editing-saving-and-loading-josm-session.md @@ -2,27 +2,25 @@ title: Saving and loading a JOSM session --- -It is possible to save a JOSM session similar most GIS software (in QGIS we call it a project file). The JOSM session saves your current map view, OSM data and loaded layers such as imagery. +他の多くのGISソフトウェアと同様、JOSMでもセッションを保存することが可能です（QGISでいうところのプロジェクトファイルと同等です）。JOSMのセッションでは、現在の地図表示位置とOSMデータ、読み込み中の地図画像レイヤなどが保存されます。 -The JOSM session is available in **File** menu. You need to be in **Expert mode** to access this feature. -To activate Expert mode, go to JOSM Preferences, activate **Expert mode** by clicking the checkbox. +JOSMセッションは**ファイル**メニューから利用可能です。この機能にアクセスするには**上級者モード**を有効化している必要があります。 +上級者モードを有効化するには、JOSMの設定を表示させ、**上級者モード**のチェックボックスにチェックを入れてください。 -## Saving a JOSM session +## JOSMセッションの保存 -Load any of your preferred layers in JOSM. -Save the JOSM session file clicking, **File > Session > Save session as ...** -Select any layers you want loaded when you start a new JOSM session. +JOSMで任意のレイヤを表示させます。 +**ファイル > セッション > 別名でセッションを保存**をクリックし、JOSMのセッションをファイルとして保存します。 +新しくJOSMのセッションを開始する際に、読み込みを行うレイヤを選択してください。 ![josm_session_save2]({{site.baseurl}}/images/saving-a-josm-session.gif) -## Loading a JOSM session +## JOSMセッションの読み込み -To load a previously saved JOSM session, click **File > Session > Load session**. -Select the `.jos` you saved. +以前に保存したJOSMセッションを読み込むには、 **ファイル > セッション > セッションの読み込み**をクリックします。保存した`.jos`ファイルを選択してください。 ![josm_session_load2]({{site.baseurl}}/images/loading-a-josm-session.gif) -NOTE: Do not save any OSM data within your `.jos` file. Always load new data to avoid data conflicts. - -Examples of session files we use in the [/mapping repo](https://github.com/mapbox/mapping/tree/master/JOSM/sessions). +注意: `.jos`ファイルとしてOSMデータは保存しないでください。データの競合を避けるため、データは常に新しいものを読み込むようにします。 +現在チームで利用しているセッションファイルの例は [/mapping repo](https://github.com/mapbox/mapping/tree/master/JOSM/sessions)から利用可能です。 diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md index fecaf24..472fe9e 100644 --- a/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-05-advanced-josm-customization.md @@ -2,17 +2,11 @@ title: Advanced JOSM customization --- -Hidden settings in JOSM can be configured directly from the advanced preferences panel. This also gives you access to export and import your configuration profiles. - -JOSMの各市設定として、拡張設定パネルからいくつかの設定を行うことが可能です。JOSMに設定したプロファイル情報をインポートしたり、エクスポートしたりすることもできます。 - -The panel is hidden by default and is shown as the last option when `Expert mode` is enabled. +JOSMの隠し設定として、拡張設定パネルからいくつかの設定を行うことが可能です。JOSMに設定したプロファイル情報をインポートしたり、エクスポートしたりすることもできます。 デフォルトでは設定パネルは隠されており、`上級者モード`を有効化した時だけ最後のオプションが表示されるようになっています。 ![screenshot 2015-10-15 14 42 52](https://cloud.githubusercontent.com/assets/126868/10509569/890e64b8-734b-11e5-988f-26596f9d42d9.png) -**Note** JOSM will need to be restarted for any changes to take effect. - **注意事項** 設定の変更を反映させるにはJOSMの再起動が必要です diff --git a/jp/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md b/jp/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md index f04d3f9..9849158 100644 --- a/jp/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md +++ b/jp/becoming-a-power-mapper/_posts/josm/0000-01-06-advanced-mapping-guide.md @@ -2,98 +2,97 @@ title: Advanced mapping guide --- -## Roads +## 道路 -**Neighborhood grid** - -Residential buildings are usually located on a `residential` or `living_street` and has access to a road only on one side, and optionally on the backside via a `service alleyway`. A building with residential roads on multiple sides is a sign of mistaking building shadows for streets. The street grid in an an area will have repeating patterns that make it easy to guess how the roads are laid even if they are obscured by trees. -![untitled](https://cloud.githubusercontent.com/assets/126868/9808707/434854d4-587f-11e5-9132-c9e0824bd9e5.gif) +**住宅区域、造成地** +住宅地に建築されている建物は通常、 `住居区域内道路/residential`か`生活道路/living_street`に沿って建てられており、時折、家の後ろ側には`路地用の私道/service alleyway`が配置されていることがありますが、基本的に道路には1つの面しか接していない状態になります。2つ以上の住居区域内道路に面している場合は、建物の影を道路と間違えている可能性のサインです。その地域内の道路グリッドは一定であり、樹木で見えなくなっていたとしても道路が存在しているかどうか推測することは非常に容易です。 -**Using Fast draw plugin** +![untitled](https://cloud.githubusercontent.com/assets/126868/9808707/434854d4-587f-11e5-9132-c9e0824bd9e5.gif) -* Install and use **Fast draw** plugin (`shift + F`). -* Press down arrow to simplify way, up arrow to add more complexity and then `Enter`. -* `Q` to simplify straight segments of roads. -* Shortcuts to tag each type of road classification **Preferences > Customize the icons in the toolbar > Presets > highways/ features that require shortcut > highways/streets > select the road you want to add as shortcut > right click on the shortcut and add a shortcut**. +**Fast drawプラグインの活用** +* **Fast draw**プラグインをインストールします (`shift + F`). +* ウェイの単純化は矢印ボタンで行います。上向きの矢印を押すと複雑な形状になりますので、`Enter`キーを押してください。 +* 道路のセグメントを単純化し、直線にするには `Q`を押します。 +* 各階層の道路のタグをショートカットに登録するには、**設定 > ツールバーのアイコンカスタマイズ > プリセット > 道路 > 道路/ショートカットを設定する地物 > 道路/街路 > ショートカットに登録したい道路を選択 > 右クリックしてショートカットに追加** を行います。 *Video* [Faster draw in JOSM](https://youtu.be/xqDd-Crk3o4) -## Buildings +## 建物 + +* **building plugin** (`B`)を使うことで、**並行した建物**のトレースができます。建物を1つ選択した状態でツールを使うことで、その建物と並行に他の建物を描くことが可能です。 -* **Parallel buildings** can be traced using the **building tools** plugin (`B`). Select a building and using the tool align subsequent buildings to the first one in one step. ![untitled](https://cloud.githubusercontent.com/assets/126868/9729213/73f5971e-562b-11e5-8c86-a1fa91eb969e.gif) -* You can use the **Area extrude** tool (`x`), to quickly add details to the outlines by creating new nodes (double click) and then dragging the faces. +* **Area extrude** ツール (`x`)を使うことで、詳細情報を建物の外郭に対して素早く付与することが可能です。ダブルクリックしてノードを作成し、ドラッグしてください。 + ![untitled](https://cloud.githubusercontent.com/assets/126868/9730603/419f04bc-5635-11e5-8ab8-bda7b1223892.gif) -* **Compound buildings** To combine overlapping buildings, select both building and click *Join overlapping Areas* (`Shift + J`). For several intersecting buildings, use `I > Shift+J`. Or, use the *Auto Tools > Combine LA buildings*. +* **建物の合成** 一部重複する建物を結合させるには、対象の建物オブジェクトをどちらも選択し、*重複するエリアの結合* (`Shift + J`)をクリックします。建物の交差が入り組んでいる場合は、`I > Shift + J`の順で押します。あるいは、 *Auto Tools > Combine LA buildings*を使ってみましょう。 ![untitled](https://cloud.githubusercontent.com/assets/126868/9731646/c5816cd8-563b-11e5-84c4-497d9ac7536f.gif) - -* In *Extrusion mode* (`X`), do `Ctrl + Cmd` to redraw/reshape buildings for irregularly shaped buildings. - +* *Extrusion mode* (`X`)を実行している際に`Ctrl + Cmd`を押すことで、イレギュラーな形状の建物の再描画/形状修正することができます。 ![x-ctrl cmd](https://cloud.githubusercontent.com/assets/13744156/25951924/cf3403da-367c-11e7-84d7-fa43187b38f4.gif) - -* In *Extrusion mode* (`X`), add four nodes in a segment, hold the `Ctrl + Cmd` key, and drag the middle segment to create pyramidal extrusions. +* *Extrusion mode* (`X`)を実行している際に`Ctrl + Cmd`を押し、その状態で区域の中心部分をドラッグすると、ピラミッド状に形状を押し出すことが可能です。 ![pyramidal buildings](https://cloud.githubusercontent.com/assets/13744156/25951031/190971be-367a-11e7-9de1-12bae8b9a056.gif) -* Double tap `A` to draw buildings with irregular sized extrusions. Or create several smaller buildings +* `A`をダブルタップすると、イレギュラーな大きさの建物を押し出すことが可能です。同様に、同じ形を小さくすることもできます。 ![double tap a](https://cloud.githubusercontent.com/assets/13744156/25951540/aab0855c-367b-11e7-814d-e874320fc4ab.gif) -* For buildings sharing the same wall, draw buildings (`B`) and, select intersecting node and click *Join Node to a Way* (`J`) or *Move Node unto Way* (`N`). +* 1つの外壁を共有している建物を描くには、建物を描き(`B`)、そして交差するノードを選択して*ウェイにノードを結合*(`J`)か、*ノードをウェイの一部に移動* (`N`)をクリックします。 ![join j](https://cloud.githubusercontent.com/assets/13744156/25953311/90f74560-3680-11e7-8936-254744c3aeb3.gif) -* To split a single building into two, select two nodes and select *Split Object* (`Alt + X`) +* 1つの建物を2つに分割するには、ノードを2つ選択し、*オブジェクトを分割* (`Alt + X`)を選択します。 ![alt x_split_buildings1](https://cloud.githubusercontent.com/assets/13744156/25953093/03458b0a-3680-11e7-91dc-b5e1bfc81e12.gif) -* Use *Terracer* plugin for multiple same shaped buildings sharing the same wall (`Shift + T`) +* *Terracer*プラグインを使うことで、1つの外壁を共有する同じ形の建物を作成できます (`Shift + T`) ![terrace](https://cloud.githubusercontent.com/assets/353700/25843868/63539886-34c6-11e7-9ac1-84419da6e512.gif) -* For circular features, draw the diameter, select the way, and click *Tools > Create Circle* (`Shift + O`). +* 円形の地物を描くには、まず円の直径を直線で描き、ウェイを選択し、*ツール > 円形を作成* (`Shift + O`)を選択します。 * Use *Resize* tool (`Ctrl + Alt`) to re-size shape. -*Videos* +*ビデオ* + +* [異なるタイプの建物を描く方法](https://www.youtube.com/watch?v=VNPfKh_ZI58&feature=youtu.be) +* [JOSMで接触している建物を描く](https://www.youtube.com/watch?v=7GQtNnjIO0Q&feature=youtu.be) -* [Drawing different types of buildings](https://www.youtube.com/watch?v=VNPfKh_ZI58&feature=youtu.be) -* [Tracing touching buildings in JOSM](https://www.youtube.com/watch?v=7GQtNnjIO0Q&feature=youtu.be) +## その他 -## Others +**個別のパーキングスペース** -**Individual parking spaces** +パーキングスペース全てに対する外周を描き、[terracer plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Terracer)を使ってグリッドを作成。自動的に設定されてしまう `building=yes`タグを取り除き、`amenity=parking_space`を追加。隣接するグリッドを作成した場合は、妥当性検証を行うことで自動的に重複したノードをマージ可能。 -Draw a box enclosing the parking spaces and use the [terracer plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Terracer) to create a grid. Replace the default `building=yes` tag with `amenity=parking_space`. If you created adjacent grids, you would want to use the validator to automatically merge the overlapping nodes. ![untitled](https://cloud.githubusercontent.com/assets/126868/9601159/7ae06fd6-50bd-11e5-85ac-4fc3d00d7fbb.gif) -**Tagging driveway through a building** +**建物内を通過するドライブウェイ** ![screen shot 2015-05-28 at 12 40 31 pm](https://cloud.githubusercontent.com/assets/10308123/7854419/f19e7898-0536-11e5-8e57-ffa455325588.png) -Relevant tagging option for building would be +この建物について関連するタグは、多くの場合、 `building=roof` and `layer=1` -Highway road under the roof tagging options +屋根の下を走る道路のタグオプション covered=yes highway=footway highway=residential highway=service -**Tagging stadium tracks** +**スタジアムのトラックへのタグ** ![image](https://cloud.githubusercontent.com/assets/369696/7835918/184508f2-0485-11e5-8378-b7b405c7c843.png) -Relevant tagging option for Stadium would be +スタジアムに対する関連タグのオプション - trace centerline of track as line (`leisure=track;area=no`) - connect centerlines with surrounding foot paths or streets where possible diff --git a/jp/becoming-a-power-mapper/_posts/reference/0000-01-07-fixing-common-mapping-issues.md b/jp/becoming-a-power-mapper/_posts/reference/0000-01-07-fixing-common-mapping-issues.md index 0d824e1..8559f5c 100644 --- a/jp/becoming-a-power-mapper/_posts/reference/0000-01-07-fixing-common-mapping-issues.md +++ b/jp/becoming-a-power-mapper/_posts/reference/0000-01-07-fixing-common-mapping-issues.md @@ -2,19 +2,20 @@ title: Fixing common mapping issues --- -Identifying common mistakes made by beginner mappers and knowing how to fix them is important to improve the quality of the map. If you spot something which needs fixing, send a friendly message on the users' changeset on what was wrong and how it could be fixed. You can use this guide as a reference. +初心者が行ってしまいがちな間違い編集を認識し、それらの修正方法を理解することは、地図の品質を向上させるうえで非常に重要です。修正が必要な場所を見つけたら、そのユーザの変更セットに対し、何が間違っていてどうやって直せばよいのか、優しい文体でメッセージを送りましょう。以下はよくある間違い編集の一例です。 -| Issue | Whats wrong | How to fix it | Tips | + +| 課題 | 間違っている点 | 修正方法 | TIPS | | ----- |------------ | ------------- | ---- | -| **Overlapping ways** | [![](https://cloud.githubusercontent.com/assets/11504548/7966913/a0edc5a6-09ec-11e5-9583-fd510c0ab6fd.png)](https://cloud.githubusercontent.com/assets/11504548/7966913/a0edc5a6-09ec-11e5-9583-fd510c0ab6fd.png) A linear way goes over itself or another way with the exact same tags (note the arrows on the selected way) | Delete the overlapping way, make sure there are no gaps or missing pieces left behind. | You can use the [JOSM validator](http://wiki.openstreetmap.org/wiki/JOSM/Validator) to detect these issues | -| **Add `layer=1` for bridges**|[![bridgefilter](https://cloud.githubusercontent.com/assets/6770741/11365662/e2c2b5bc-92cd-11e5-830d-2a165b896181.gif)](https://cloud.githubusercontent.com/assets/6770741/11365662/e2c2b5bc-92cd-11e5-830d-2a165b896181.gif)If there is a lot bridges without `layer=1` tag, you can filter bridges easily.|Go to every bridge and look into imagery for it's layers (layer=1, layer=2 etc) and add |OSM Wiki on [bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)| -|**Overlapping buildings**|[![screen shot 2015-11-24 at 5 50 20 pm](https://cloud.githubusercontent.com/assets/6770741/11366588/222087f6-92d4-11e5-8a45-2189e3b2e961.png)](https://cloud.githubusercontent.com/assets/6770741/11366588/222087f6-92d4-11e5-8a45-2189e3b2e961.png) Buildings which are overlapping, should be separated | Run Validator and separate manually, use 'Q' to orthogonalise it| Check OSM wiki on [building](http://wiki.openstreetmap.org/wiki/Buildings) for more information.| -|**Add junction=roundabout**|[![junction](https://cloud.githubusercontent.com/assets/6770741/11375904/cd5a8336-9303-11e5-8cb3-2ea99a610142.gif)](https://cloud.githubusercontent.com/assets/6770741/11375904/cd5a8336-9303-11e5-8cb3-2ea99a610142.gif)|Add `junction=roundabout` for circle| OSM Wiki for [roundabout](http://wiki.openstreetmap.org/wiki/Tag:junction%3Droundabout)| +| **ウェイを重複して描いている** | [![](https://cloud.githubusercontent.com/assets/11504548/7966913/a0edc5a6-09ec-11e5-9583-fd510c0ab6fd.png)](https://cloud.githubusercontent.com/assets/11504548/7966913/a0edc5a6-09ec-11e5-9583-fd510c0ab6fd.png) ラインが自分自身の上、あるいは別のウェイの上に、全く同じラインで同じタグのオブジェクトを描画（選択したウェイの矢印に注目） (note the arrows on the selected way) | 重複した部分のラインを削除し、ギャップや重複の残りが無いことを確認 | [JOSM validator](http://wiki.openstreetmap.org/wiki/JOSM/Validator) を使うことで検知可能 | +| **橋への `layer=1` 付与忘れ**|[![bridgefilter](https://cloud.githubusercontent.com/assets/6770741/11365662/e2c2b5bc-92cd-11e5-830d-2a165b896181.gif)](https://cloud.githubusercontent.com/assets/6770741/11365662/e2c2b5bc-92cd-11e5-830d-2a165b896181.gif)If 橋のラインに対して `layer=1`タグが付与されていないケースが多数あります。橋（bridge）をフィルタすると簡単に発見できます。|それぞれの橋を航空写真で確認し、layerタグ (layer=1, layer=2 など)を付与 |OSM Wiki on [bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)| +|**建物オブジェクトの重複**|[![screen shot 2015-11-24 at 5 50 20 pm](https://cloud.githubusercontent.com/assets/6770741/11366588/222087f6-92d4-11e5-8a45-2189e3b2e961.png)](https://cloud.githubusercontent.com/assets/6770741/11366588/222087f6-92d4-11e5-8a45-2189e3b2e961.png) 建物が重複しており、分割が必要 | 妥当性検証を実施し、手動で分割作業を実施。建物の角を直角にするに`Q`キーを使う| OSM wikiの[building]もチェック(http://wiki.openstreetmap.org/wiki/Buildings) for more information.| +|** junction=roundabout追加**|[![junction](https://cloud.githubusercontent.com/assets/6770741/11375904/cd5a8336-9303-11e5-8cb3-2ea99a610142.gif)](https://cloud.githubusercontent.com/assets/6770741/11375904/cd5a8336-9303-11e5-8cb3-2ea99a610142.gif)|円形部分に`junction=roundabout`を追加| OSM Wiki for [roundabout](http://wiki.openstreetmap.org/wiki/Tag:junction%3Droundabout)| |**Split bridge at exact location**|[![image](https://cloud.githubusercontent.com/assets/1152236/7830938/6a645932-046f-11e5-8f6b-560054ac584c.png)](https://cloud.githubusercontent.com/assets/1152236/7830938/6a645932-046f-11e5-8f6b-560054ac584c.png) Should split bridge exactly to match imagery| Switch between Bing/Mapbox to clear confusion| OSM wiki on [bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)| -|**Untagged Ways**|[![untagged](https://cloud.githubusercontent.com/assets/6770741/11389187/c0354348-9363-11e5-9441-5c9833d8b4b2.gif)](https://cloud.githubusercontent.com/assets/6770741/11389187/c0354348-9363-11e5-9441-5c9833d8b4b2.gif)| Run `shift+v` and select the ways and add appropriate highway tags| OSM wiki on [highway](http://wiki.openstreetmap.org/wiki/Key:highway)| -|**Crossing waterways/highways**|[![crossingwater](https://cloud.githubusercontent.com/assets/6770741/11389332/779fd81c-9365-11e5-9467-7cdd96b3a2a3.gif)](https://cloud.githubusercontent.com/assets/6770741/11389332/779fd81c-9365-11e5-9467-7cdd96b3a2a3.gif)| Run `shift+v` to get all crossing waterways and highways| Add `layer=1` to bridges to solve the issue|[bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)| -|**Missing highway names**|[![missingnames](https://cloud.githubusercontent.com/assets/6770741/11389598/44b162d8-9368-11e5-8b53-7228fd992ebc.gif)](https://cloud.githubusercontent.com/assets/6770741/11389598/44b162d8-9368-11e5-8b53-7228fd992ebc.gif) The names of highways should be added using recent TIGER (Only for USA) data| Steps to add predefined [imagery sources](https://josm.openstreetmap.de/wiki/Help/Preferences/Imagery) in JOSM | OSM wiki on [TIGER](http://wiki.openstreetmap.org/wiki/TIGER)| -|**Abbreviated road names**|[![abbreviated](https://cloud.githubusercontent.com/assets/6770741/11389977/8352e5a4-936b-11e5-9b0c-c3b01e9e7857.gif)](https://cloud.githubusercontent.com/assets/6770741/11389977/8352e5a4-936b-11e5-9b0c-c3b01e9e7857.gif)| Do not abbreviate street names, write full name| E.g: Boulevard as Blvd, Street as St, Court as Ct, Drive as Dr etc| -|**Way end node near other highway**|[![screenshot 2015-11-25 12 21 54](https://cloud.githubusercontent.com/assets/6770741/11390480/90f90710-9370-11e5-9ea7-05bcaf1ffc85.png)](https://cloud.githubusercontent.com/assets/6770741/11390480/90f90710-9370-11e5-9ea7-05bcaf1ffc85.png)Nodes which ends near to other highways| Select the node and press `shift+j` to connect it.|| -|**Possibility to improve alignment**|[![improvement](https://cloud.githubusercontent.com/assets/6770741/11390603/e4807660-9371-11e5-94e8-fabf25e62fa4.gif)](https://cloud.githubusercontent.com/assets/6770741/11390603/e4807660-9371-11e5-94e8-fabf25e62fa4.gif)| Use `W` to align the lines/polygons to the imagery| | +|**タグが無いウェイ**|[![untagged](https://cloud.githubusercontent.com/assets/6770741/11389187/c0354348-9363-11e5-9441-5c9833d8b4b2.gif)](https://cloud.githubusercontent.com/assets/6770741/11389187/c0354348-9363-11e5-9441-5c9833d8b4b2.gif)|`shift+v`を実行し、ウェイを選択、適切なhighwayタグを付与| OSM wiki on [highway](http://wiki.openstreetmap.org/wiki/Key:highway)| +|**水路/道路が交差**|[![crossingwater](https://cloud.githubusercontent.com/assets/6770741/11389332/779fd81c-9365-11e5-9467-7cdd96b3a2a3.gif)](https://cloud.githubusercontent.com/assets/6770741/11389332/779fd81c-9365-11e5-9467-7cdd96b3a2a3.gif)| `shift+v`を実行し、水路と道路の交差部分を把握| 橋の部分に `layer=1` を付与して解決|[bridge](http://wiki.openstreetmap.org/wiki/Key:bridge)| +|**highwayに名称が無い**|[![missingnames](https://cloud.githubusercontent.com/assets/6770741/11389598/44b162d8-9368-11e5-8b53-7228fd992ebc.gif)](https://cloud.githubusercontent.com/assets/6770741/11389598/44b162d8-9368-11e5-8b53-7228fd992ebc.gif) 最新のTIGERデータ（米国の場合）を使って道路の名称を入力| JOSMで[背景画像](https://josm.openstreetmap.de/wiki/Help/Preferences/Imagery)を追加する方法| OSM wiki on [TIGER](http://wiki.openstreetmap.org/wiki/TIGER)| +|**略語化された道路名称**|[![abbreviated](https://cloud.githubusercontent.com/assets/6770741/11389977/8352e5a4-936b-11e5-9b0c-c3b01e9e7857.gif)](https://cloud.githubusercontent.com/assets/6770741/11389977/8352e5a4-936b-11e5-9b0c-c3b01e9e7857.gif)| ストリート名称の省略は行わない。フルネームで入力する| 例: Boulevard as Blvd, Street as St, Court as Ct, Drive as Dr etc| +|**他の道路のすぐ近くでウェイが途切れている**|[![screenshot 2015-11-25 12 21 54](https://cloud.githubusercontent.com/assets/6770741/11390480/90f90710-9370-11e5-9ea7-05bcaf1ffc85.png)](https://cloud.githubusercontent.com/assets/6770741/11390480/90f90710-9370-11e5-9ea7-05bcaf1ffc85.png)他の道路のすぐ近くでウェイが途切れている| ノードを選択して `shift+j` で接続|| +|**確度の改善可能性**|[![improvement](https://cloud.githubusercontent.com/assets/6770741/11390603/e4807660-9371-11e5-94e8-fabf25e62fa4.gif)](https://cloud.githubusercontent.com/assets/6770741/11390603/e4807660-9371-11e5-94e8-fabf25e62fa4.gif)| `W`キーを押して、ライン/ポリゴンを航空写真と合わせる| | | \ No newline at end of file diff --git a/jp/becoming-a-power-mapper/_posts/reference/0000-01-08-useful-overpass-queries.md b/jp/becoming-a-power-mapper/_posts/reference/0000-01-08-useful-overpass-queries.md index 787e1de..62c3f62 100644 --- a/jp/becoming-a-power-mapper/_posts/reference/0000-01-08-useful-overpass-queries.md +++ b/jp/becoming-a-power-mapper/_posts/reference/0000-01-08-useful-overpass-queries.md @@ -5,12 +5,12 @@ title: Useful Overpass queries Need | Query ---|--- -Newer than a given date| `[out:xml][timeout:600];(way["highway"](newer:"2015-05-30T07:00:00Z")({{bbox}}););out body;>;out skel qt;` -Changes in a given time period|`[out:xml][timeout:600];(way["highway"](changed:"2015-05-14T07:00:00Z","2015-05-30T07:01:00Z")({{bbox}}););out body;>;out skel qt;` -provide two dates and generate a difference between the two| `[diff: "2015-06-30T15:00:00Z","2015-09-21T15:00:00Z"][out:xml][timeout:25];(way["highway"]({{bbox}}););out body;>;out skel qt;` -extract edits of a user| `[out:json][timeout:25];(node(user:"ramyaragupathy")({{bbox}});way(user:"ramyaragupathy")({{bbox}});relation(user:"ramyaragupathy")({{bbox}}););out body;>;out skel qt;` -extract a particular tag| `[out:json][timeout:25];(node["amenity"="hospital"]({{bbox}});way["amenity"="hospital"]({{bbox}});relation["amenity"="hospital"]({{bbox}}););out body;>;out skel qt;` -extract all amenities| `[out:json][timeout:25];(node["amenity"]({{bbox}});way["amenity"]({{bbox}});relation["amenity"]({{bbox}}););out body;>;out skel qt;` -find a particular tag without someother key value| `[out:json][timeout:25];(node["highway"="footway"]["footway"!~"."]({{bbox}});way["highway"="footway"]["footway"!~"."]({{bbox}});relation["highway"="footway"]["footway"!~"."]({{bbox}}););out body;>;out skel qt;` -query within query| `[out:json][timeout:250];((way({{bbox}})[highway='primary'];relation({{bbox}})[highway='primary'])->.a;node.a[name='Sand Hill Road'];);out body;>;out skel qt;` -search for a tag in an area| `[out:json][timeout:250];(area[name="Palo Alto"];way(area)["building"];relation(area)["building"];);out body;>;out skel qt;` \ No newline at end of file +特定日付より前| `[out:xml][timeout:600];(way["highway"](newer:"2015-05-30T07:00:00Z")({{bbox}}););out body;>;out skel qt;` +特定期間中の編集|`[out:xml][timeout:600];(way["highway"](changed:"2015-05-14T07:00:00Z","2015-05-30T07:01:00Z")({{bbox}}););out body;>;out skel qt;` +日時を2つ指定し、その間の差分を作成| `[diff: "2015-06-30T15:00:00Z","2015-09-21T15:00:00Z"][out:xml][timeout:25];(way["highway"]({{bbox}}););out body;>;out skel qt;` +特定ユーザによる編集抽出| `[out:json][timeout:25];(node(user:"ramyaragupathy")({{bbox}});way(user:"ramyaragupathy")({{bbox}});relation(user:"ramyaragupathy")({{bbox}}););out body;>;out skel qt;` +特定タグの抽出| `[out:json][timeout:25];(node["amenity"="hospital"]({{bbox}});way["amenity"="hospital"]({{bbox}});relation["amenity"="hospital"]({{bbox}}););out body;>;out skel qt;` +全てのamenityを抽出| `[out:json][timeout:25];(node["amenity"]({{bbox}});way["amenity"]({{bbox}});relation["amenity"]({{bbox}}););out body;>;out skel qt;` +特定のタグと一緒に、別の値やタグが付与されていない地物| `[out:json][timeout:25];(node["highway"="footway"]["footway"!~"."]({{bbox}});way["highway"="footway"]["footway"!~"."]({{bbox}});relation["highway"="footway"]["footway"!~"."]({{bbox}}););out body;>;out skel qt;` +クエリの中から再帰してクエリ| `[out:json][timeout:250];((way({{bbox}})[highway='primary'];relation({{bbox}})[highway='primary'])->.a;node.a[name='Sand Hill Road'];);out body;>;out skel qt;` +特定地域の中でタグ検索| `[out:json][timeout:250];(area[name="Palo Alto"];way(area)["building"];relation(area)["building"];);out body;>;out skel qt;` \ No newline at end of file diff --git a/jp/becoming-a-power-mapper/_posts/reference/0000-01-09-useful-osm-resources.md b/jp/becoming-a-power-mapper/_posts/reference/0000-01-09-useful-osm-resources.md index af5ec84..676ceb3 100644 --- a/jp/becoming-a-power-mapper/_posts/reference/0000-01-09-useful-osm-resources.md +++ b/jp/becoming-a-power-mapper/_posts/reference/0000-01-09-useful-osm-resources.md @@ -1,65 +1,64 @@ --- title: Useful OSM resources --- -The OSM ecosystem has an array of tools that you can use to extract, modify, visualize data, and contribute to! -## Mapping +OSMのエコシステムでは、データの抽出や改変、可視化、そして参加のためのツールが揃っています！ + +## マッピング - [OSM Map features](http://wiki.openstreetmap.org/wiki/Map_Features) - [Taginfo - tagging stats](http://taginfo.openstreetmap.org/) -## Survey tools +## 現地調査ツール - [Fieldpapers](http://fieldpapers.org) for paper based surveying - [Mapillary](http://mapillary.com/) for crowdsourcing streetview imagery -### Tasking Tools +### タスク管理ツール - [To-fix](http://osmlab.github.io/to-fix/) - [Map Roulette](http://maproulette.org/) -- [Map tasking manager](http://tasks.openstreetmap.us/) for coordinating mapping in a continuos area +- [Map tasking manager](http://tasks.openstreetmap.us/) 特定エリアを複数人で継続的にマッピングする際に便利 -## Data -- [Awesome GeoJSON](https://github.com/tmcw/awesome-geojson) - list of some awesome tools around GeoJSON -- [Overpass Turbo](http://overpass-turbo.eu/) for querying OSM by properties -- [GeoJSON.io](http://geojson.io/) for creating / editing GeoJSON data -- [Dropchop](http://dropchop.io/) for GIS based actions -- [Flatten GeoJSON attributes](http://batpad.github.io/geojson-flatten-tags/) Converter +## データ +- [Awesome GeoJSON](https://github.com/tmcw/awesome-geojson) - GeoJSONまわりの便利なツール +- [Overpass Turbo](http://overpass-turbo.eu/) プロパティ別にOSMデータへクエリ実施 +- [GeoJSON.io](http://geojson.io/) GeoJSONデータの作成と編集 +- [Dropchop](http://dropchop.io/) GISベースの作業 +- [Flatten GeoJSON attributes](http://batpad.github.io/geojson-flatten-tags/) データ形式変換 - [Merge GeoJSONs](https://github.com/mapbox/geojson-merge) -- [Minjur](https://github.com/mapbox/minjur) for converting large OSM data to GeoJSON -- [tippecanoe](https://github.com/mapbox/tippecanoe) Builds vector tilesets from large collections of GeoJSON features +- [Minjur](https://github.com/mapbox/minjur) 大容量のOSMデータをGeoJSONに変換する際に利用 +- [tippecanoe](https://github.com/mapbox/tippecanoe) 複数のGeoJSONファイルからベクトルタイルセットを構築 - [Collection of useful GeoJSON tools](https://github.com/tmcw/awesome-geojson) -- [toGeoJSON](http://mapbox.github.io/togeojson/) toGeoJSON turns KML & GPX into GeoJSON - +- [toGeoJSON](http://mapbox.github.io/togeojson/) toGeoJSONではKMLとGPXをGeoJSONに変換可能 -### Visualization +### 可視化 - [OSM Changes Visualization](https://github.com/ericfischer/osm-animate) - [Compare OSM and Google Maps](http://lxbarth.com/compare/#17/33.81196/-117.91879) -### Extracts +### 抽出 - [OSM planet extracts](http://planet.osm.org) - [Geofabrik region extracts](http://download.geofabrik.de/openstreetmap/) - [Mapzen metro extracts](https://mapzen.com/data/metro-extracts) - [OSM QA Tiles](http://osmlab.github.io/osm-qa-tiles/) -### QA and Activity Tracking +### 品質管理、活動追跡 - [OSM Inspector](http://wiki.openstreetmap.org/wiki/OSM_Inspector) - [WHODIDIT](http://zverik.osm.rambler.ru/whodidit/) OpenStreetMap Changeset Analyzer - [Heatmap](http://yosmhm.neis-one.org/) -For full list check the [OSM Wiki](http://wiki.openstreetmap.org/wiki/Quality_assurance) - +[OSM Wiki](http://wiki.openstreetmap.org/wiki/Quality_assurance)に全リストあり -## Community -- Use the [history tab on the map](http://www.openstreetmap.org/history#map=14/51.5150/-0.0972) to find and message active mappers nearby -- Write on your [OSM Diaries](http://www.openstreetmap.org/diary) to bring up issues for community discussion -- Join your local [community mailing list]() for discussions on various topics -- [Who is around me?](http://resultmaps.neis-one.org/oooc) Find local mappers +## コミュニティ +- [地図の履歴機能](http://www.openstreetmap.org/history#map=14/51.5150/-0.0972)を使ってその地域で活動しているアクティブマッパーを見つけ、メッセージを送付 +- [OSMダイアリー](http://www.openstreetmap.org/diary)を書いて、コミュニティとの議論の機会を展開 +- [自分が住んでいる地域のメーリングリスト]()で、様々なトピックについて相談 +- [Who is around me?](http://resultmaps.neis-one.org/oooc) 地域のマッパーを検索 -### Contribute -- To the [OSM Homepage](https://github.com/openstreetmap/openstreetmap-website) -- To the development of the [OSM map style and cartography](https://github.com/gravitystorm/openstreetmap-carto/issues) -- By publishing your tool on [osmlab](https://github.com/osmlab) +### 活動参加 +- [OSMウェブページ](https://github.com/openstreetmap/openstreetmap-website)への参加方法 +- [OSM地図スタイル](https://github.com/gravitystorm/openstreetmap-carto/issues)の開発参加 +- [osmlab](https://github.com/osmlab)でツール公開 - [OSM wiki: Contribute](http://wiki.openstreetmap.org/wiki/How_to_contribute) -### Guides and FAQ +### ガイドとFAQ - [OSM wiki FAQ](http://wiki.openstreetmap.org/wiki/FAQ) - [OSM help](https://help.openstreetmap.org) - [LearnOSM mapping guides](http://learnosm.org) diff --git a/jp/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md b/jp/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md index fe95a49..eb12b5e 100644 --- a/jp/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md +++ b/jp/mapping-with-josm/_posts/0000-01-01-mapping-with-josm.md @@ -2,127 +2,127 @@ title: Mapping with JOSM --- -This guide will get you started [mapping with the Java OpenStreetMap editor (JOSM)](https://www.mapbox.com/blog/making-the-most-josm/) - a powerful and popular desktop editor for OpenStreetMap. Another popular editor is [iD](https://www.mapbox.com/blog/new-map-editor-launches-openstreetmap/), commonly used for short and simple, browser based editing sessions. Note that this section only focuses on the mechanics of editing with JOSM. +このガイドでは、[Java OpenStreetMap editor (JOSM)を使ってマッピング](https://www.mapbox.com/blog/making-the-most-josm/)を始める方法について解説します。JOSMはOpenStreetMapで使われる、パワフルでポピュラーなデスクトップ環境です。もうひとつポピュラーなエディタとして、シンプルで短時間のマッピングによく使われる、ブラウザベースのエディタ[iD](https://www.mapbox.com/blog/new-map-editor-launches-openstreetmap/)があります。この章では、JOSMを使った編集のみを取り扱います。 -## Downloading from OpenStreetMap +## OpenStreetMapからのデータダウンロード -To start editing, download an area from OpenStreetMap by using the green down-arrow button on the left in the menu bar. +編集を始めるには、メニューバーの左側にある緑色の下側矢印をクリックし、編集対象のエリアのデータをOpenStreetMapからダウンロードしてください。 -## Using imagery +## 衛星写真の使い方 -You will routinely use imagery for mapping. JOSM comes with a variety of pre-configured satellite imagery layers - the Bing and Mapbox layers being the most popular ones. Bing and Mapbox may have different levels of detail and clarity in different places, so often worth checking both. Simply select one of them from the imagery menu and you're ready to go. +マッピングを行う際には、衛星写真や航空写真を日常的に利用することになります。JOSMには、よく使われる画像としてBingやMapboxレイヤなど、さまざまな画像レイヤがあらかじめ設定されています。BingとMapboxでは、地域ごとに画像の詳細さや鮮明度が異なっており、両方を見比べることは有用です。画像メニューからそれらのうちの1つを選択するだけで準備は完了です。 ![](https://s3.amazonaws.com/f.cl.ly/items/0E463a191T1R182t0o09/imagery.gif) -When using imagery, keep in mind that imagery may be offset. That is, due to complexities in processing satellite imagery, features on imagery may not be at the same location as they are in the real world. For reference, check existing features on the map and compare them with the imagery or download GPS tracks. To download GPS tracks from OpenStreetMap, check the "Raw GPS" box in the download dialog. If you observe an offset in the imagery, you can correct for it by selecting the "New offset" item in the "Imagery" menu. +衛星画像を利用する際には、画像のズレ（オフセット）に注意してください。これは衛星画像に対して複雑な処理を行った結果、地表に存在する場所の位置と画像の位置がずれてしまうために発生します。試しに、OpenStreetMapで描かれている既存の地物や地図と、衛星画像やGPSトラックを重ね合わせて比較してみましょう。OpenStreetMapからGPSトラックをダウンロードするには、ダウンロードを行う際のダイアログで "生のGPS"ボックスにチェックを入れてください。もし画像とデータの間にズレが生じていた場合、"画像"メニューの"新規オフセット"項目を選択することで画像の位置を修正することができます。 -## Creating data +## データの作成 -Click the "Draw nodes" button to enter the data creation mode. Subsequent clicks on the map will set nodes connected by a way. Double click to finish drawing the way. For drawing single nodes, simply double click on the map. To draw a closed way, finish a way with a click on the first node you drew. +"ノードを描く"ボタンをクリックし、データ作成モードに移ってください。地図上をクリックすると、その位置にノードが配置され、連続して複数のノードを置くことでウェイが描かれます。ウェイの描画を完了するにはダブルクリックしてください。ノードを1つだけ描きたい場合は、ダブルクリックだけを行ってください。閉じたウェイを描く場合は、最初に描いたノードをもう一度クリックしてください。 ![](https://s3.amazonaws.com/f.cl.ly/items/1w3i0p411R2b0s0y1r2R/trace.gif) -## Modifying data +## データ修正 -Click the "Select" button to select existing nodes or ways. To move nodes or ways click on them, hold the mouse button pressed and drag them. Then release the mouse button where you'd like to drop them. +"選択"ボタンをクリックすると、既存のノードやウェイを選択することができます。ノードやウェイを移動させるには、一度それらのオブジェクトをクリックし、マウスの左ボタンを押したままドラッグさせてください。ボタンを離した場所にノードやウェイが移動します。 ![](https://s3.amazonaws.com/f.cl.ly/items/2r3h0m1E262s3j3M191q/edit.gif) -To delete data, use the `del` key of your keyboard or on a mac, use `fn+delete`. +データを削除する場合、キーボードの`del`キーを押すか、macの場合は `fn+delete`を押してください。 -If you ever make a mistake, `ctrl+Z`, or `command+Z` on mac, will undo the last change. +入力を間違えてしまった場合は、`ctrl+Z`あるいはmacなら`command+Z`で最後に行った作業をやり直しできます。 -Ways can be connected to each other. In JOSM speak, you can glue, unglue, split and combine them. This is useful to create logical connections, for instance between roads of different type. To prevent ways from connecting when drawing, say when drawing a road close to buildings, hold the `ctrl` key, while clicking the mouse. +ウェイはお互いに接続することができます。JOSMでは、接着（glue）、引き剥がし（unglue）、分割（split）、結合（combine）と表現します。論理的な接合を行うことは、例えば異なるタイプの道路を接続する場合など、非常に有益な機能です。ウェイを接続せずに編集を行う場合、例えば建物の近くまで道路を描く場合などは、`ctrl`キーを押したままマウスをクリックしてください。 ![](https://s3.amazonaws.com/f.cl.ly/items/2p3Y2x461o390V3q1E22/split.gif) -## Tagging +## タグ付け -You can add, modify or delete tags directly in the tagging panel in JOSM's side bar. If for some reason this panel is not visible, you can enabled it under the "Windows" menu. The example below tags two ways at the same time. Simply hold shift to select multiple objects. +タグの追加や編集、削除はJOSMサイドバーから行います。なんらかの理由によってパネルが見えなくなっている場合、"ウィンドウ"メニューから表示設定を行ってください。以下の例では、2つのウェイに対して同時にタグを付与しています。複数のオブジェクトを選択するには、Shiftキーを押しながら選択するだけです。 ![screenshot from 2014-11-24 16 15 10](https://s3.amazonaws.com/f.cl.ly/items/0C2X2O3I0l2K0X3G2P00/tagging.gif) -**Presets** are common tags or tagging combinations that can be applied to objects. They can be found in the "Presets" menu where they are organized into logical categories. Try adding a preset and then review the modifications in the tagging panel. +**プリセット**とは、オブジェクトに対してよく使われるタグや、複数タグの組み合わせについて定めているものです。利用は"プリセット"メニューから行うことができ、論理的に構成されたカテゴリ構造で整理されています。プリセットを使ってみて、タグパネルに表示される内容がどのように変化するか、確認してみましょう。 ![ssasa](https://cloud.githubusercontent.com/assets/1152236/5173525/5bf9022a-73f7-11e4-97b8-89203488adca.png) -** Copy & pasting tags ** +** タグのコピー＆ペースト ** -You can copy and paste tags from one object to another. Just select one object, copying with `ctr + c`. Then select the other object and paste with `ctrl + shift + v`. This will copy _only tags_ - not the geometry. +オブジェクト間でタグをコピーすることも可能です。まず1つのオブジェクトを選択し、`Ctrl + c`でコピーを行います。次にペースト先のオブジェクトを選択し、 `ctrl + shift + v`で貼り付けます。この操作ではタグ _だけ_ がコピーされます。位置情報はコピーされません。 -## Uploading to OpenStreetMap +## OpenStreetMapへのアップロード -To upload the data, click on the green up-arrow button on the left in the menu bar. This will automatically trigger *validation*. Review all validation warnings and resolve all errors before you upload. If there are any errors or warnings, do your best to fix them. Before you upload, **add a proper changeset comment and specify what source you used**. This is important as it will show other users who see your changesets what this changeset was intended to modify and from where you took the information. +データのアップロードを行うには、メニューバーの左側にある上向きの緑矢印をクリックします。アップロードを行おうとすると、自動的に *妥当性検証*が行われます。検証の結果を確認し、アップロードを行う際にはすべてのエラーを解決してください。エラー（赤色）や警告（黄色）が複数検知された場合は、できるだけそれらを修正してからアップロードしましょう。また、アップロードを行う際には **適切な変更セットコメントと、利用した情報源に関する情報を書くようにしましょう。** これにより、他のユーザが後でデータの編集を検討する際に、既存のデータがどのようなデータをもとに編集されたかを知ることができ、たいへん重要な情報となります。 -The upload will take a few seconds. The data is live on OpenStreetMap immediately. The map usually takes a couple of minutes to clear through all caches. +アップロードは数秒で終わり、データは即座にOpenStreetMapに反映されます。キャッシュがクリアされるまでには通常、数分間程度かかります。 ![](https://s3.amazonaws.com/f.cl.ly/items/390y0t3A1M2i260F2n0k/upload.gif) -Once you uploaded the data, you and everyone else can see a corresponding entry on your OpenStreetMap user profile under "My Edits": +データのアップロードを行うと、あなたのOpenStreetMapプロフィールの"ユーザの編集"から、あなたが行った編集を誰でも閲覧することができるようになります。 ![](https://s3.amazonaws.com/f.cl.ly/items/3T141H1W1b1y1m301T0v/Screen%20Shot%202014-12-16%20at%2011.44.27%20AM.png) -## Productivity tips +## 生産性向上のためのTIPS -### Filters +### フィルタ -Filters are very powerful and can speed up your work tremendously. Take a look at the [JOSM filter documentation](https://josm.openstreetmap.de/wiki/Help/Dialog/Filter) and at [AJ's blog post about filters](https://www.mapbox.com/blog/2012-08-15-using-filters-josm/) to learn how they work. +フィルタは非常にパワフルな機能で、利用することによって作業の効率がまったく変わります。[JOSMフィルタドキュメント](https://josm.openstreetmap.de/wiki/Help/Dialog/Filter)と、[フィルタ関するAJ氏のブログ記事](https://www.mapbox.com/blog/2012-08-15-using-filters-josm/)を読むと、フィルタの動作について知ることができます。 -Here are some of the most common filter selectors in use for editing: +以下、編集の際に使い勝手のよいフィルタをいくつか紹介します。 `boundary: | leisure: | landuse: | waterway: | amenity: | natural: | building:` -### Pull out common highway classifications into toolbar +### よく使う道路階層をツールバーに登録 -When you work on OpenStreetMap, you will use highway classifications a lot, bring them all into the toolbar: +OpenStreetMapの編集では、道路の階層構造の情報を多用します。すべてツールバーに登録しておくとよいでしょう。 ![screenshot from 2014-11-24 15 59 41](https://cloud.githubusercontent.com/assets/1152236/5173024/fd25da56-73f2-11e4-805f-ff3a321ca15a.png) -### Use keyboard shortcuts +### キーボードショートカット -When you're editing, you will be a lot faster using keyboard short cuts. Take a moment to familiarize yourself with them and start using them! You can find keyboard shortcuts in the menus like in the screenshot below, but there's also [a full reference of keyboard shortcuts on the JOSM web site](https://josm.openstreetmap.de/wiki/Shortcuts) ([en español](https://josm.openstreetmap.de/wiki/Es%3AShortcuts)). +編集を行う際にはショートカットを使うことで作業が非常に速くなります。いくつか練習してみて、ぜひ使ってみてください！ キーボードショートカットは、スクリーンショットのようにメニューの中にいくつか表示されますが、その他、[JOSMウェブサイトにはすべてのキーボードショートカットが一覧化](https://josm.openstreetmap.de/wiki/Shortcuts) ([en español](https://josm.openstreetmap.de/wiki/Es%3AShortcuts))されています。 ![screenshot from 2014-11-25 22 25 06](https://cloud.githubusercontent.com/assets/1152236/5195894/23afd078-74f2-11e4-9735-640cefcbfe0c.png) -### Plugins +### プラグイン -There are many JOSM plugins that will help you to map faster. Here are a couple that used most commonly. You find all plugins in the settings panel: +JOSMのプラグインを使うことで、マッピングを素早く行うことが可能です。以下は非常によく使われるプラグインです。設定パネルから、すべてのプラグインを参照することができます。 ![](https://s3.amazonaws.com/f.cl.ly/items/3Q2T452P2j0H3t2F1h1b/plugins.gif) -**Buildings plugin** +**Buildings plugin（建物プラグイン）** -For tracing buildings, always use the buildings plugin. It speeds up editing by creating rectangular boxes with a tag `building=yes` by default. To quickly draw buildings that are aligned to each other, draw the first building, select it, and draw subsequent parallel buildings. +建物のトレースを行う場合は、この building pluginが常に利用されます。このプラグインを利用することにより、`building=yes`がデフォルトで付与された四角形のボックスを、素早く描くことが可能になります。同じ向きを向いている建物を大量に描く場合は、最初に建物を1つ選択し、その状態で建物を描くことで、その建物と並行に描画を行うことができます。 ![](https://s3.amazonaws.com/f.cl.ly/items/0Y2T1s0x0M2t3C24363A/buildings.gif) -To align existing buildings neatly, you can select multiple buildings, then two extra nodes to set the alignment axis and [orthoganalize shape (keyboard shortcut `q`)](http://josm.openstreetmap.de/wiki/Help/Action/OrthogonalizeShape) +既存の建物の向きをそろえるには、対象となる複数の建物を選択し、追加でノードを2つ選択した状態で [形状の直行化、キーボードショートカット`Q`](http://josm.openstreetmap.de/wiki/Help/Action/OrthogonalizeShape)を押してください。 ![3zpk8nxbdt](https://cloud.githubusercontent.com/assets/126868/6900081/d65cf23c-d721-11e4-82f9-7084b11bb41f.gif) -**turnrestrictions plugin** +**turnrestrictions plugin（進行方向制限プラグイン）** -This plugin makes it really easy to add [turn restrictions](http://wiki.openstreetmap.org/wiki/Relation:restriction) such as "no left turn" to roads. +このプラグインを使うことで、例えば"左折禁止"などの[進行方向制限（turn restrictions）](http://wiki.openstreetmap.org/wiki/Relation:restriction)を簡単に追加することが可能になります。 ![edit a new turn restriction in layer data layer 1 2015-12-11 17-02-26](https://cloud.githubusercontent.com/assets/369696/11742854/fb630938-a028-11e5-88cf-c03a6e175abf.png) -Read more in JOSM help - https://josm.openstreetmap.de/wiki/Help/Plugin/TurnRestrictions +詳しくはJOSMのヘルプを参照ください - https://josm.openstreetmap.de/wiki/Help/Plugin/TurnRestrictions -**Fast draw plugin** +**Fast draw plugin（高速描画プラグイン）** -This plugin is great for tracing areas like forests, lakes, waterways or landuse and linear features like roads. +このプラグインでは、森林や湖沼、河川の流域や土地利用や、その他道路などライン状の地物を高速でトレースすることが可能になります。 -To start, press `shift + f`, then click with the mouse to start drawing. Whenever you'd like to set a node, press the space bar. For free hand drawing, keep the space bar or mouse button pressed. +利用を開始するには `shift + f`を押し、マウスをクリックします。ノードを配置したい場合は、キーボードのスペースバーを押します。フリーハンドで描画を行う場合、スペースバーやマウスのボタンをクリックしたままマウスを動かしてください。 ![untitled](https://cloud.githubusercontent.com/assets/126868/8275787/b1ffb342-18bd-11e5-8262-c2fba62b05b9.gif) -To delete the latest created nodes, just hit `backspace`. +最後に作成したノードを削除するには、`backspace`を押します。 -To determine how many nodes are set automatically in freehand mode, use the up and down arrow keys. +フリーハンドモードで自動的に配置されるノードの数を調整するには、上下の夜市汁キーを使います。 -To finish drawing, press enter to go into the simplification mode (feature will turn yellow), press the up or down arrow for the desired level of simplification and press enter again to create the way. +描画を完了するにはエンターキーを押し、簡素化モードに移行（地物が黄色に変わります）し、上下の矢印キーを押して簡素化のレベルを調整、もう一度エンターキーを押してウェイの作成を行ってください。 -While tracing you can press `Q` to set some preferences for "FastDraw" +トレースしている間に `Q`を押すことで、"FastDraw"の設定を行うことが可能です。 ![fastdraw configuration 2015-12-14 22-55-16](https://cloud.githubusercontent.com/assets/369696/11788197/c9ec99d4-a2b5-11e5-9ab7-9c0c3530d963.png) @@ -130,81 +130,82 @@ While tracing you can press `Q` to set some preferences for "FastDraw" **Utilsplugin2** -Utilsplugin2 comes with a series of tools that you can all find in the new menu "More tools", after the plugin is installed. The most used one is "Add nodes at Intersections" which gives you a fast way to add nodes at places where ways intersect in the current selection. +Utilsplugin2をインストールすることにより、メニューの"他のツール"項目に大量のツールが追加されます。その中で最もよく使われる "交差点にノードを追加" 機能は、現在選択中のウェイの交点に対して素早くノードを追加することができます。 ![screenshot from 2014-11-25 17 03 51](https://cloud.githubusercontent.com/assets/1152236/5193091/698be05e-74cb-11e4-8dcb-1a1a228daa07.png) *[Video Tutorial](https://www.youtube.com/watch?v=F5NsYpKC6G4)* -**Notes** +**Notes（地図メモ）** -Notes are a great way to post questions for others on the map. When mapping, observe notes that others left in the area and if you have a specific question or a suggestion on how the map could be improved, consider leaving a note. +Notes （訳：日本語では地図メモ）機能は、閲覧者からの地図に関する質問を受け付ける非常に良い手段です。マッピングを行う際には、その地域に残された地図メモをチェックし、もし逆に、自分がなにか地図の改善について残しておいたほうがよい情報があれば、地図メモとして残しておくようにしましょう。 -Activate the notes plugin: +noteプラグインの有効化 ![screenshot from 2014-11-25 16 49 25](https://cloud.githubusercontent.com/assets/1152236/5192168/3f6704c8-74c3-11e4-9c69-d214b95d78cc.png) -Now you should see a list of notes in the side bar for the area you're mapping in: +地図編集画面のサイドバーとして、表示中の地域の地図メモがリスト表示されるようになります。 ![screenshot from 2014-11-25 16 52 11](https://cloud.githubusercontent.com/assets/1152236/5192216/8abfc5f4-74c3-11e4-8a5d-89bce76c7039.png) -### Validation +### 妥当性検証 -JOSM automatically validates your data when uploading, but you can run validation at any point by clicking 'Validation' in the Validation panel. +JOSMではデータのアップロードを行う際に自動的に妥当性検証が行われますが、それとは別に、パネルから'妥当性検証'ボタンをクリックすることにより、任意のタイミングで検証処理を実行することが可能です。 ![](https://s3.amazonaws.com/f.cl.ly/items/2i0I3E3I3m0r3u2F1f2x/validate.gif) -### Configuring drawing styles +### 描画スタイルの設定 -Sometimes it's useful to tweak drawing stiles to help improve visibility of certain features. +状況によっては、データの表示スタイルを変更することにより、特定の地物の視認性が改善する場合があります。 -For example, if you're working with addresses, activate "Address Tags Validator": +例えば住所データの作業を行っている場合には、"Address Tags Validator"を使うことができます。 ![screenshot from 2014-11-25 15 10 03](https://cloud.githubusercontent.com/assets/1152236/5190603/3fcd89a4-74b5-11e4-8513-62c3747ddb2c.png) -Or if you'd like to see clearly what you've edited in your session, activate "Modified objects": +また、現在のセッション中に編集を行ったオブジェクトをわかりやすく表示するには、"Modified objects"を有効化します。 ![screenshot from 2014-11-25 15 13 59](https://cloud.githubusercontent.com/assets/1152236/5190658/d136243c-74b5-11e4-9218-092e402179ed.png) -Try different drawing styles yourself and figure out which ones help you do your work better. +他にもさまざまなスタイルがありますので、作業の内容に合わせて自身が見やすい表示スタイルを試してみてください。 -#### Highlight data freshness +#### データの新鮮さをハイライト表示 -You can use [this style](https://raw.githubusercontent.com/Andygol/josm-styles/master/recent%20changes_2016.mapcss) to highlight features that are created or modified in 2016. To configure this: +[このスタイル](https://raw.githubusercontent.com/Andygol/josm-styles/master/recent%20changes_2016.mapcss)を使うと、2016年に作成された地物がハイライト表示されます。設定方法は以下のとおりです。 ![](https://cloud.githubusercontent.com/assets/369696/9634340/e596f890-5199-11e5-8335-55d63a9b11d2.gif) -### Custom imagery +### 背景画像のカスタマイズ -You can also add custom imagery from Tile Map Service (TMS) or Web Map Service (WMS) endpoints. Here is how: +Tile Map Service (TMS)や、あるいはWeb Map Service (WMS)エンドポイントを追加することにより、背景画像のカスタマイズを行うことが可能です。追加方法は以下のとおりです。 - [Adding a TMS imagery endpoint](https://www.youtube.com/watch?v=JvM0aP3vVr0) `http://{switch:a,b,c}.tile.thunderforest.com/cycle/{zoom}/{x}/{y}.png` - [Adding a WMS imagery endpoint](https://www.youtube.com/watch?v=VJqVsV0MXpw) `http://www.geosur.info/arcgis/services/maps/GeoSUR_WMS_hidrografia/MapServer/WMSServer` -### Resolving conflicts +### 競合の解決 -If you upload a change to OpenStreetMap and someone has changed one of the same features in the meantime, a conflict will occur. In this case OpenStreetMap will refuse your changes. Follow these steps to resolve the conflicts: +あなたがOpenStreetMapに変更をアップロードし、それと同時に誰かが1つ以上の地物を変更すると、競合が発生します。その場合、OpenStreetMapはあなたがアップロードした変更の適用を拒絶します。以下の手順で競合の解決を行ってください。 -1. Download new data from OpenStreetMap for the area in which the conflict occured. -2. Run validation and review the conflicts. -3. Fix them. -4. Attempt upload again. +1. 競合が発生した区域に対して、OpenStreetMapから新しいデータをダウンロード +2. 妥当性検証を行い、競合の内容をレビュー +3. データの修正を実施 +4. 再度アップロードを試行 -As a last resort, you can attempt to upload changes one by one. This is not recommended though. +最終手段として、実施した変更を1つずつアップロードすることも可能です。ただし、その方法は推奨しません。 ![screenshot from 2014-11-25 16 43 40](https://cloud.githubusercontent.com/assets/1152236/5192070/3e43555c-74c2-11e4-9c7a-87bb52120ddc.png) -### Scripting JOSM +### JOSMのスクリプト化 -You can script JOSM to automate certain workflows. For example: +JOSMにスクリプトを設定し、特定のワークフローを自動化する事もできます。例えば、 -- Expand abbreviations (US): https://gist.github.com/Rub21/feb83f57a727ac0d8a34 -- Capitalize names and eliminate "name=S/N": https://gist.github.com/Rub21/47838797856566a8b6ba -- Expand abbreviations (Peru): https://gist.github.com/Rub21/cc055320c925c855926e +- 略称表記の正規化 (US): https://gist.github.com/Rub21/feb83f57a727ac0d8a34 +- nameの一文字目を大文字化し、"name=S/N"を削除: https://gist.github.com/Rub21/47838797856566a8b6ba +- 略称表記の正規化 (ペルー): https://gist.github.com/Rub21/cc055320c925c855926e **[Video](https://www.youtube.com/watch?v=Cpi_5dB1NLQ)** -## Further reading and questions +## 参考文献と質問 + +より詳しい情報は[JOSM help](https://josm.openstreetmap.de/wiki/Help)を参照してください。 -For further information, take a look at the [JOSM help](https://josm.openstreetmap.de/wiki/Help). diff --git a/jp/sources/_posts/0000-01-01-sources.md b/jp/sources/_posts/0000-01-01-sources.md index d9ac051..5a6465f 100644 --- a/jp/sources/_posts/0000-01-01-sources.md +++ b/jp/sources/_posts/0000-01-01-sources.md @@ -14,7 +14,7 @@ OpenStreetMapに情報を追加する際に利用可能な情報源の例は以 - OpenStreetMapに対して明示的にトレースの許可が与えられた **衛星写真**。例えば、BingやMapbox Satelliteなどが該当します - **[Mapillary](http://mapillary.com/)**に掲載された写真 - 店舗の住所文字列など、ウェブサイトに掲載された **原典情報** (訳註：日本でも事実情報として著作性はありませんが、念のためとして文字情報の転記も嫌うマッパーは少なくないことに注意ください) -- **ライセンス互換性のあるデータセット**、例えば[Wikidata](http://www.wikidata.org/wiki/Wikidata:Main_Page)など - 互換性のあるライセンスとは、[CC0](https://creativecommons.org/publicdomain/zero/1.0/)か、あるいは[open definition](http://opendefinition.org/)に記載がありなおかつ継承条件（share-alike）を持たないライセンス、を指します。（訳註：この記載は誤りです。CC-BY4.0であってもODbLとのライセンス互換はありません。詳しくはOSMFのブログを参照し、データ配布元から明示的な利用許可を得てください。CC0は許諾なく利用可能です） +- **ライセンス互換性のあるデータセット**、例えば[Wikidata](http://www.wikidata.org/wiki/Wikidata:Main_Page)など - 互換性のあるライセンスとは、[CC0](https://creativecommons.org/publicdomain/zero/1.0/)か、あるいは[open definition](http://opendefinition.org/)に記載がありなおかつ継承条件（share-alike）を持たないライセンス、を指します。（訳註：この記載は誤りです。CC-BY4.0であってもODbLとのライセンス互換はありません。詳しくは[OSMFのブログ](https://blog.openstreetmap.org/2017/03/21/openstreetmap%e3%81%ab%e3%81%8a%e3%81%91%e3%82%8bcc-by-4-0%e3%83%a9%e3%82%a4%e3%82%bb%e3%83%b3%e3%82%b9%e9%81%a9%e7%94%a8%e3%83%87%e3%83%bc%e3%82%bf%e3%81%ae%e5%88%a9%e7%94%a8%e3%81%ab%e3%81%a4/?lang=ja)を参照し、データ配布元から明示的な利用許可を得てください。CC0はライセンス互換があり、許諾なく利用可能です） **以下の情報源は利用しないでください** @@ -22,7 +22,6 @@ OpenStreetMapに情報を追加する際に利用可能な情報源の例は以 - 明示的に許可が指定されていない情報源 - その情報源が利用可能かどうか、判断に迷う場合 - ## グループ調査 OpenStreetMapには、オリジナルの、つまりコミュニティメンバーによって収集されたデータが多く含まれています。こうしたデータはほとんどが現地調査の結果であり、調査とは別工程として、リモートマッピングを行う際に使われるものと同じエディタを使ってOpenStreetMapへの入力が行われます。以下は現地調査でよく使われるテクニックです。 diff --git a/jp/validating-osm/_posts/0000-01-01-validating-osm.md b/jp/validating-osm/_posts/0000-01-01-validating-osm.md index 1074763..a5c13f6 100644 --- a/jp/validating-osm/_posts/0000-01-01-validating-osm.md +++ b/jp/validating-osm/_posts/0000-01-01-validating-osm.md @@ -1,247 +1,245 @@ ---- -title: Validating OpenStreetMap Data ---- - -At Mapbox, we map as well as inspect the data that is coming into OpenStreetMap for quality. This is the definitive guide that we follow - from detecting potentially harmful changes to inspecting them and eventually fixing the map. - -## What is a problematic edit? - -Every change to OpenStreetMap is contained in a [changeset](http://wiki.openstreetmap.org/wiki/Changeset). They consist of either additions (new feature), modifications (change existing tags, feature location, or location of a referred feature) or deletions by a mapper. - -When working with data in OpenStreetMap, you sometimes come across places where another mapper might have added bad features or tags, changed or moved or deleted a large set of data or an important set of tags. Changes that spoil the quality of OpenStreetMap data are considered problematic edits. - -There are several kinds of potentially problematic changes. For example: - -* Use of proprietary data (like Google Maps) to add data in OpenStreetMap. -* Modification to significant tags like `place`, `boundary`, `highway`, etc. -* Undocumented imports. -* Modifications with outdated imagery. -* Unintentional dragging of nodes in way that results in geometry changes. - -Creation and deletion of features, modification to tags and modification to a node's location, result in a `version` increment. Every change by every user is retained as a separate version of the object in the OpenStreetMap database. Changes to nodes within a way, or to members of a relation, result in displayed changes to the way/relation but do *not* increment `version`. - -## Identifying problematic edits. - - * **OSMCha**: Changeset level notification, giving an overview of how many objects were affected in a changeset. A set of suspects words automatically flag some suspicious changes. Custom filters can be used with changeset comment, source, and other combinations to look for suspicious edits. Read more about [using OSMCha to identify and inspect OpenStreetMap data.](#finding-suspicious-map-edits-using-osmcha) - * **Linting** - * **Map Feedback from Mapbox users**: Sometimes we receive notice through [Map feedback](https://www.mapbox.com/map-feedback/) where the Mapbox users report the changes. - * **OSM communication channels.** - -## Investigation - -After identifying potentially problematic data on the map, you will want to determine few things to start: - -* the *user* responsible -* the *time* they made the edit -* what made the changes - the *changeset id* -* the *features edited* - -This information will help us investigate the change and identify the cause and type of change. Let's follow an example of misaligned roads in New York City. - -![screenshot 2016-04-14 12 56 09](https://cloud.githubusercontent.com/assets/3423533/14520241/0c277554-0241-11e6-8695-7a76c9cd0683.png) - -### Inspecting the change - -1. Open the area in `JOSM`. -2. Select the problematic feature, and check the modified object's history using `Ctrl+H`. -3. The History window displays how that selected object was changed over time by different mappers. The display will vary based on the type of object (node/way/relation) selected. The left panel shows the object's versions, modification dates, and responsible users. - - The `Tags` tab of History window has the history of tags changed between versions. - - The `Nodes` tab of History window has the history of addition/deletion/modification of nodes associated with a way's geometry between versions. - - The `Coordinates` tab of history window has the history of the object if its moved for a significant distance. - -![history](https://cloud.githubusercontent.com/assets/3423533/15171329/52dca16a-176b-11e6-8b78-ce3220c62d40.png) - -*JOSM History window* - -In this example, someone moved a node a significant distance. From the JOSM history window, you can see the change was made by user `osm_user_name`, in changeset `38544431`, dated `04/14/2016`. - -### Understand the mapper - -The mapper's OSM user profile and [HDYC](http://hdyc.neis-one.org) profile gives an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. - -Click on the OSM username in the JOSM History window, and load the OSM user page where you can view the user's `Edits` history, any `Active Blocks`, any other details on the user, and `Diary` entries. - -You cal also gauge a mapper's experience by looking at the number of project days, type of mapper and other points in [HDYC](http://hdyc.neis-one.org/). - -![hdyc](https://cloud.githubusercontent.com/assets/3423533/15170921/ee9fbe6a-1767-11e6-8601-e74f7891a88f.png) - -### Investigate the changeset - -Click on the changeset ID in the JOSM History window to open the OpenStreetMap changeset page, and load details on how many objects were added/modified/deleted. You'll also see the changeset comment, which may contain more self-reported details from the user, as well as information on the editor and sources used. - -The OpenStreetMap changeset pages list the objects touched by the user in that particular changeset, but it won't highlight the specific details of changed objects. - -![screenshot 2016-04-14 17 35 26](https://cloud.githubusercontent.com/assets/3423533/14527442/b721eacc-0267-11e6-9fe4-807e6271ccf4.png) - - -This is where [Changeset Map](http://osmlab.github.io/changeset-map/) comes in handy. Changeset Map visualizes all specific features changes made to OpenStreetMap in a changeset. - -- Submit the changeset id to changeset-map to see the changes affected in that changeset. - - `Example`: - -- Changeset Map shows the features added/modified/deleted or touched during the changeset. Identify all the problematic changed objects by exploring the edits. - -![vali](https://cloud.githubusercontent.com/assets/3423533/14984377/f28d4942-115f-11e6-9c28-956faab784a3.gif) - -## Response - -At this point, you know who, when, and which changeset are associated with the problematic change. - -Most bad edits are accidental, and the general strategy to respond to such changes is education. Work to share knowledge with the mapper about the mistake and how they can avoid the mistake in the future. Communicate feedback through public changeset comments, visible to all, or sometimes direct messages if more direct contact is helpful. This helps build our community and improve the quality of future contributions to the map. - -In cases where it is determined that the intent of the mapper was to damage the map, an urgent response may be required by reverting the change and reporting the issue to an OSM administrator or Data Working Group. - -### Communicate - -* Leave a comment on the changeset with a description of what was wrong and how it can be fixed. Link to an OpenStreetMap wiki or link to help material that is relevant. -* If the user does not respond or fix non-urgent issues within a week, alert a nearby active mapper of the issue. -* Also look for help on IRC or the local forums or mailing list of the area. - -### Repair - -* For specific malicious changes, consider fixing the issue (and reporting it immediately). -* For a changeset that is wholly inaccurate, revert it. Send a message to the mapper responsible and ask for a description of what happened. -* For simple issues, communicate with the mapper to discuss on how they can fix it. - -#### Revert using the JOSM Plugin - -The JOSM [Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter) is a convenient way to revert changes in OpenStreetMap. After every revert, make sure you upload the changes by sharing a changeset comment on why you reverted the changeset. - -Reverting changesets can be tricky, and you can unintentionally break things yourself. Attempt to revert a changeset if you are 100% sure that the changeset is bad and if something goes wrong -- you should be able to fix it. - -![revert](https://cloud.githubusercontent.com/assets/3423533/14527229/25b55a52-0266-11e6-847d-b9601f8fae8d.gif) - -*Using the revert plugin* - -### Report - -* For urgent issues that require an experienced response, contact the [Data Working Group](http://wiki.openstreetmap.org/wiki/Data_working_group). - -### How to assess urgency to respond - -The level of response depends on how severe the change is to OpenStreetMap. Urgency is somewhat subjective, but here is some guidance. - -1. Changes to significant features like the following should trigger an immediate repair. - - Major boundaries - - Highway connectivity - - Highway hierarchy - - Highways misalignment (like our NYC example) - - Broken multipolygons (water/border) which effect admin boundaries - - Landmarks - -2. Changes to important but less critical features should start with communication, and repair later only if the user does not respond. - - Land use features like forests - - Buildings - - Water bodies - -3. If the mapper is using the proprietary data sources like Google, Bing Maps, Here Maps or other sources which are not open licensed then comment on the user changeset and mention [Copyright guidance for OpenStreetMap](http://www.openstreetmap.org/copyright). Encourage them to revert the changes and follow local knowledge, or stick to Bing and Mapbox Satellite Imagery. - -## Common Scenarios - -Here are a few common scenarios of bad edits in OpenStreetMap. - -#### Mistakes by inexperienced mappers - -New users are always welcome to edit OpenStreetMap! During their learning process sometimes they may mistakingly attempt to modify/delete major land features like boundaries, important place tags, highways, and relations which can cause faulty data. In cases like this it's good to educate the users by directing them to proper guides, and instructions they need to follow while mapping and encourage them to correct their mistakes. Revert immediately if it's a serious error. - -#### Humanitarian OpenStreetMap Team projects - -Many new mappers join OpenStreetMap during HOT Activation. HOT tasks have custom imagery; the changeset review should be done using them. If data added does not match either imagery or the custom imagery, or added data is not of good quality, comment on user changeset to help improve their edits and mapping skills. - -#### Intentional bad edits - -There are few users who intentionally add bad data to OpenStreetMap which should be reverted immediately. -One such example is shown below. Here the user intentionally added family names to towns, buildings, and footpaths. - -![screenshot 2016-05-03 18 47 00](https://cloud.githubusercontent.com/assets/3423533/14984342/d96fe7ee-115f-11e6-9af5-28ac515d9b28.png) - -#### Undocumented imports - -You can import open datasets into OpenStreetMap. Imports should follow the [Import Guidelines](http://wiki.openstreetmap.org/wiki/Import_guidelines) and add proper documentation to the [Imports catalogue](http://wiki.openstreetmap.org/wiki/Import/Catalogue), and use a dedicated import accounts. If you see any undocumented imports, comment on the changeset to request documentation details. - -#### Automated edits - -Automated edits are changes made to OpenStreetMap with less direct human involvement which involves bots, algorithmic imports, etc. - - -## Finding suspicious map edits using OSMCha - -**[OSM Changeset Analyzer](http://osmcha.mapbox.com/)** or OSMCha is a tool to filter and analyze changesets on OpenStreetMap using the [changeset metadata](https://www.openstreetmap.org/api/0.6/changeset/41775489/download). The tool has a live listing of every changeset on the map, flags potentially suspicious edits and has various filters to find changesets that match certain criteria. - -![screenshot 2016-09-06 16 00 06](https://cloud.githubusercontent.com/assets/8921295/18270541/0de8330c-744b-11e6-8582-7e49d6acec9d.png) -_Latest changesets listed in OSMCha_ - -The changeset is shown with id, date and time of creation, OSM user, creations in green, modification in yellow, deletions in red, a keyword describing if the changeset fits any set behaviors along with a cross mark to signify that the changeset is unreviewed. - -### Filtering changesets - -The filters available in OSMCha allow for a various combination of searches to help find problematic edits. - -![screenshot 2016-08-30 16 37 31](https://cloud.githubusercontent.com/assets/8921295/18086930/1a28da0c-6ed0-11e6-8eed-5a0b7ee6cf72.png) -_OSMCha filter dialog_ - -OSMCha automatically tags changeset with certain parameters like `Mass creations` or `Possible import`. - -![screenshot 2016-08-30 16 48 17](https://cloud.githubusercontent.com/assets/8921295/18087208/932c74c6-6ed1-11e6-8176-d6a1a6bb9f93.png)
-_Filter based on automatic flagging_ - - -### Examining the quality of the changeset - -OSMCha uses [Changeset map](https://github.com/osmlab/changeset-map/) to visually represent the features that were added, modified and deleted along with tag changes. This helps check the quality of the edits for obvious mistakes. - -screenshot 2016-08-22 15 16 17
-_A [changeset](http://osmlab.github.io/changeset-map/#41576998/way/24464264) showing an object that incorrectly made into a circle_ - -### Workflow to find suspicious changes - -#### Suspicious editing behavior - -Inexperienced users, deletions, and imports: - -- [Edits from Maps.me editor](http://osmcha.mapbox.com/?editor__icontains=Maps.Me&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) -- [Mass deletions](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) -- [Mass deletions + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) -- [Mass modifications + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=4) -- [Mass creations + iD editor](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2)/ [Possible import](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2) - -Strategy for filters: - -1. iD editor is targeted towards simple editing from new users, and any advanced editing happens in JOSM. So, if a mass deletion takes place using iD editor, there is a probability that the user could be inexperienced and the deletions unreasonable. [Example of a harmful changeset.](http://osmcha.mapbox.com/41628531/) -2. Maps.me users tend to be new to OSM. It is suggested to look for changesets that add an unreasonable amount of similar POIs in one area. This could be due to a lack experience of the user in mapping coupled with a lack of amenities available through the app preset. [Example of a harmful changeset.](http://osmcha.mapbox.com/40927770/) - - Edits from Maps.me editor are automatically uploaded through the app. The app generates an automatic changeset comment based on the kind of amenities that were added. Filtering Maps.me edits with most creations first as sort order helped us in finding most of the bad edits from Maps.me users so far. -3. This is similar to the first assumption. Mass modifications using iD editor could be a suspicious changeset. Mass modification could be two scenarios: - - When the user modifies tags of a long way (coastline, administrative boundaries, long motorway, etc.) and polygons, these edits are registered to the way/polygon and all the nodes in the feature object. - - When the user changes the geometry of an object on OSM, even though only one node is added the whole way/polygon is updated to be modified. [Example of a harmful changeset.](http://osmcha.mapbox.com/41991749/) -4. Mass creations can also be coupled with the iD editor in the filters. The idea is to review changesets which have most creations and see if all the editions fall under the [OSM editing standards and conventions](http://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions). [Example of a harmful changeset.](http://osmcha.mapbox.com/38282141/) -5. Sometimes, we were able to detect suspicious changesets by going through reason filters such as `edited an object with a significant place tag`, `edited an object with a significant tag`, `edited a wikipedia landmark`. [Example of a harmful changeset.](http://osmcha.mapbox.com/38534916/) -6. Clever acts of vandalism are hard to detect as the changesets may not be big. We can verify these modifications to `name` tags, deletion of tags from [small changesets that are iD editor contributions](http://osmcha.mapbox.com/?modify__lte=50&editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) or through [random search in OSMCha](http://osmcha.mapbox.com/). Examples harmful changesets: [1](http://www.openstreetmap.org/node/4331919989), [2](http://www.openstreetmap.org/node/4353068192/history). - - -#### Suspicious changeset keywords - -There are [certain keywords we have stored](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085) to quickly look through changesets that have these words in the changeset comments. For example "Google" and any profane language. - - -#### Finding vandalism detected by the community and reverted by Data Working Group - -The community is very active in finding and commenting on suspicious changesets. If the edits in the changesets are destructive to the map then the community will inform Data Working Group and Data Working Group will revert these changesets with a changeset comment. - - -- Using **Keywords** - - Using keywords such as `revert`, `cleanup`, `fix` in changeset comment filter, we can find most of the changesets community has taken action on. This list in OSMCha includes fixes, reverts Data Working Group as well. - -- Using [**OSM - comments**](https://www.mapbox.com/osm-comments/) - - OSM-comments API allows querying changesets with specific parameters - - Link to see changeset comments from all users in OSM - [URL for web view](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) - -Currently, there is no direct way of using OSM-Comments-API to see all the changesets on which Data Working Group members have commented. [Issue #44](https://github.com/mapbox/osm-comments-api/issues/44) - -**Finding reverts by Data Working Group** - -![documentations1](https://cloud.githubusercontent.com/assets/8921295/18270714/0cc820da-744c-11e6-8db8-71421c956e07.gif) -_Finding Data Working Group reverts using OSMCha_ - -- OSMCha allows us to query changesets from specific users. -- We can query all changesets from revert accounts of Data Working Group members such `Woodpeck_repair`, `pnorman_mechanical`, etc. \ No newline at end of file +--- +title: Validating OpenStreetMap Data +--- + +Mapboxでは地図データを作成するだけではなく、OpenStreetMapへのデータ入力品質のデータチェックも実施しています。以下は私たちが行っている作業ガイドです - 害のある可能性が高い変更の検知から、最終的に地図データの修正までを対象としています。 + +## 問題のある編集とは何か + +OpenStreetMapに加えられる変更は全て、[変更セット](http://wiki.openstreetmap.org/wiki/Changeset)にまとめられています。変更セットには、マッパーによって行われるデータの追加（新規地物）や、変更（タグの修正、地物の位置変更、参照される地物の位置など）、あるいはデータ削除などが含まれます。 + +OpenStreetMapのデータを利用していると、誰か他のマッパーが間違った地物やタグを追加したり、大量のデータ削除を行ったり、特定のタグを含んだデータのインポートが行われていたりする場面に遭遇することがありあｍす。OpenStreetMapデータの品質を損なうこれらのデータ変更は、問題のある編集として扱われます。 + +問題のある可能性が高い変更にはいくつかの種類があります。例えば、 + +* プロプライエタリなデータ（例えばGoogle Maps）のデータを使って、OpenStreetMapへのデータ追加が行われている +* `place`や`boundary`、`highway`といった主要なタグの変更 +* ドキュメント化されていないインポート +* 非常に古い衛星写真を利用した変更 +* ウェイを構成するノードを意図せず引っ張ってしまい、結果として位置情報を変更 + +地物の作成や削除、タグの変更、ノードの位置の変更などは、`バージョン`が増えることにつながります。あらゆるユーザのすべての変更は、OpenStreetMapデータベースのオブジェクトの個別バージョンとして保持されます。ウェイに所属するノードの変更、あるいはリレーションのメンバー変更は、ウェイやリレーションの変更として表示されますが、`バージョン`の増加は*行われません*。 + +## 問題のある修正の発見 + + * **OSMCha**: 変更セットレベルの通知と、その変更セット内で影響が発生したオブジェクトの一覧。コメント内の疑わしい単語は自動的に疑わしい対象としてフラグ付けを実施。変更セットコメントや、利用している情報源、その他の内容などを使って疑わしい変更を発見できるよう、カスタマイズ可能なフィルタを設定可能。より詳しい情報については[using OSMCha to identify and inspect OpenStreetMap data.](#finding-suspicious-map-edits-using-osmcha)を参照のこと。 + * **Linting** + * **Mapbox利用者からの地図フィードバック**: Mapboxユーザが地図上の変更点をレポートした場所に、[Map feedback](https://www.mapbox.com/map-feedback/)経由で私たちに通知が行われる。 + * **OSMのコミュニケーションチャンネル経由** + +## 調査 + +地図上に発生した疑わしい可能性が高いデータを発見した後、いくつかの処理を行います + +* *ユーザ*が返答するかどうか +* 彼らが編集作業を行った*時間* +* *変更セットID*の特定 +* *編集された地物* + +これらの情報は変更内容の調査に役に立つとともに、変更のタイプや原因の特定に有用です。ニューヨーク市で道路が間違って編集された例をみてみましょう。 + +![screenshot 2016-04-14 12 56 09](https://cloud.githubusercontent.com/assets/3423533/14520241/0c277554-0241-11e6-8695-7a76c9cd0683.png) + +### 編集内容の分析 + +1. `JOSM`で対象のエリアを開く +2. 問題のある地物を選択し、`Ctrl+H`を押して編集されたオブジェクトの履歴を確認 +3. 選択した地に対して行われた変更と実施したユーザが履歴ウィンドウに表示される。選択したオブジェクトの種別（ノード、ウェイ、リレーション）によって表示内容は異なる。左側のパネルにはオブジェクトのバージョンや変更日時、変更を行ったユーザが表示される。 + - 履歴ウィンドウの`タグ`タブには、バージョンごとに行われたタグの変更履歴が表示される + - 履歴ウィンドウの`ノード`タブには、バージョンごとに行われた、ウェイを構成するノードの増減や変更履歴が表示される + - 履歴ウィンドウの`緯度経度`タブには、オブジェクトが大幅に移動されていた場合に、その移動距離が表示される + +![history](https://cloud.githubusercontent.com/assets/3423533/15171329/52dca16a-176b-11e6-8b78-ce3220c62d40.png) + +*JOSM履歴ウィンドウ* + +この例では、あるノードが大幅に移動させられています。JOSM履歴ウィンドウを参照すると、実施したユーザは`osm_user_name`、変更セットは`38544431`、日付は`04/14/2016`であることがわかります。 + +### マッパーを理解する + +The mapper's OSM user profile and [HDYC](http://hdyc.neis-one.org) profile gives an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. + +マッパーのOSMユーザプロフィール、および[HDYC](http://hdyc.neis-one.org)のプロフィールを参照することで、ユーザの活動内容と評価を知ることができます。新規マッパーは意図しない間違い編集を行ってしまいがちで、その結果、そのユーザが気が付かないうちに地図データを壊してしまうことがあります。経験豊かなマッパーは、より詳しい記述や、地域に対して信頼できる知識を持っていることがありますが、間違い編集の履歴もあることでしょう。 + +JOSM履歴ウィンドウのOSMユーザ名をクリックすると、OSMユーザページが表示され、そのユーザの`編集`履歴や、`主な活動範囲`、ユーザのその他活動、そして`日記`エントリを確認する事が可能です。 + +また、そのマッパーの経験量は、[HDYC](http://hdyc.neis-one.org/)から、プロジェクト参加日や、マッパーのタイプなどを元に推測することもできます。 + +![hdyc](https://cloud.githubusercontent.com/assets/3423533/15170921/ee9fbe6a-1767-11e6-8601-e74f7891a88f.png) + +### 変更セットの精査 + +JOSM履歴ウィンドウの変更セットIDをクリックすると、OpenStreetMapの変更セットページが表示され、追加や変更、削除となったオブジェクトの総数など、詳細情報が表示されます。その際、変更セットコメントも表示され、利用したエディタや情報源など、ユーザ自身が申告した内容詳細を表示させることも可能です。 + +OpenStreetMapの変更セットページでは、当該の変更セットの中でユーザによって修正が行われたオブジェクトが一覧化されています。しかし、変更されたオブジェクトの詳細について、詳しい情報までは記載されません。 + +![screenshot 2016-04-14 17 35 26](https://cloud.githubusercontent.com/assets/3423533/14527442/b721eacc-0267-11e6-9fe4-807e6271ccf4.png) + +[Changeset Map](http://osmlab.github.io/changeset-map/)では変更セットの内容を簡単に確認することができます。Changeset Mapは、特定の変更セットによってOpenStreetMapに対して行われたすべての地物を可視化して表示することができます。 + +- 変更セットのIDをChangeset Mapに入力することで、その変更セットで行われた変更を表示することができます。 + + `Example`: + +- Changeset Mapで、当該の変更セットで行われた地物の追加/変更/削除や修正箇所が表示されます。編集箇所を探して、問題のある変更が行われたオブジェクトを特定します。 + +![vali](https://cloud.githubusercontent.com/assets/3423533/14984377/f28d4942-115f-11e6-9c28-956faab784a3.gif) + +## 対応 + +この時点で、あなたは問題のある変更がどの変更セットに含まれ、誰によって、いつ行われたのかを知ることができます。 + +最もよくない編集は偶発的であり、そうした変更に対する一般的な対応方法はユーザへの教育です。失敗してしまったマッパーに対して知っていることを共有し、将来において同じ失敗を繰り返さない方法を教えましょう。全員に対して公開されている変更セットコメントへフィードバックを送るか、あるいは直接的なコンタクトのほうがより好ましい場合は、直接メッセージを送ってみましょう。こうすることで、コミュニティが構成され、地図に対する将来の貢献の品質を改善することにつながります。 + +もし万が一、マッパーの編集意図が地図に対してダメージを与えるものである場合、変更の巻き戻しや、OSM管理者あるいはデータワーキンググループへの問題報告といった緊急の対応が必要な場合もあります。 + + +### コミュニケーション + +* 変更セットに対し、その編集で間違っている点や修正方法についてコメントを残してください。必要に応じて、OpenStreetMap Wikiへのリンクや、編集の参考になる文章へのリンクを貼ります。 +* もし一週間程度ユーザからの反応が無かったり、緊急ではない問題である場合は、その近隣を編集しているアクティブなマッパーに対して注意喚起を行います。 +* 加えて、その地域のメーリングリストや地域フォーラム、IRCなどに対して協力を打診します。 + + +### 修復 + +* 特定の種類の悪意ある編集に対しては、問題の修正を検討（および即座の報告）します +* その変更セット全体が完全に不正確である場合、巻き戻し（リバート）を行います。対象のマッパーに対してメッセージを送付し、何が起きたのかについて説明を求めてください。 +* 単純な問題の場合、対象のマッパーと連絡を取り、どのように修正を行うかについて議論を行います。 + +#### JOSMプラグインを使った巻き戻し + +JOSMの[Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter)を使うことで、OpenStreetMapの変更を簡単に巻き戻すことが可能です。リバートを行った後は、その変更セットを何故巻き戻したのか、変更セットに対して理由を説明するコメントを残すようにします。 + +Reverting changesets can be tricky, and you can unintentionally break things yourself. Attempt to revert a changeset if you are 100% sure that the changeset is bad and if something goes wrong -- you should be able to fix it. + +変更セットの巻き戻しは複雑な作業であり、気が付かないうちに自分自身でデータを破壊してしまうことがあります。巻き戻し対象の変更セットが100％完全に間違いであったり、なにかよくないことが進行中でその修正をあなたが修正しなくてはならない場合にのみ、巻き戻し作業を行うようにしてください + +![revert](https://cloud.githubusercontent.com/assets/3423533/14527229/25b55a52-0266-11e6-847d-b9601f8fae8d.gif) + +*revert pluginの利用* + +### 報告 + +* 緊急の課題で、なおかつ熟練者による作業が必要な場合は、[データワーキンググループ/Data Working Group](http://wiki.openstreetmap.org/wiki/Data_working_group)にコンタクトを取ります。 + +### 対応の緊急度基準 + +OpenStreetMapに対して行われた変更の深刻度によって、対応のレベルは変動します。緊急であるかどうかはある意味主観的なものですが、ある程度のガイドラインはあります。 + +1. 以下のような主要な地物に対する変更は、即座に修復が必要なケース + - 主要な境界線 + - 道路の接続 + - 道路の種別 + - 道路に対する間違った位置修正（NYCの例を参照） + - 破壊されたマルチポリゴン（水域など）であり、行政界データに影響をあたえる場合 + - ランドマーク + +2. 重要ではあるが致命的とはいえず、即座にコミュニケーションをとり、ユーザからの反応がない場合にのみ修復作業を実施するケース + - 森林など、土地利用に関する地物 + - 建物 + - 河川流域 + +3. もしマッパーがGoogle MapsやBing Maps（訳注：Bing航空写真ではなくBing Mapsそのもの）、Here Mapsやその他、オープンなライセンスではないプロプライエタリのデータを参照して作業を行っている場合、ユーザの変更セットに対してコメントを行い、[OpenStreetMapの著作権ガイド](http://www.openstreetmap.org/copyright)についての言及を行ってください。また、対象のデータについての巻き戻しを喚起し、地域調査による編集あるいはBingやMapbox Satelliteなど利用が許可された画像を活用することを勧めます。 + +## よくあるシナリオ + +以下、OpenStreetMapで間違った編集を見つけた際のよくあるシナリオをいくつか例示します。 + +#### 初心者マッパーによる間違い編集 + +OpenStreetMapの新規ユーザによる編集はいつでも大歓迎です！ 初心者が編集方法を学ぶ過程の中で、境界線や重要な地名タグ、道路、リレーションといった主要な地物を間違って変更/削除してしまい、結果としてデータを破壊してしまうことがあります。そのようなケースでは、ユーザへの教育を行って正しく彼らを導き、マッピングを行う際のインストラクションを提供して、彼ら自身で間違った編集を修正できるようになるようにすることが重要です。もし間違いが申告な場合、即座に巻き戻しを行います。 + +#### Humanitarian OpenStreetMap Team (HOT, OpenStreetMap人道支援チーム)のプロジェクト + +HOT活動には多くのOpenStreetMap初心者マッパーが参加します。HOTでは独自の画像が使われることがあり、それらが使われているかどうか、変更セットのレビューが必須です。もしデータが航空写真やそれらのプロジェクト独自画像とかけ離れた内容であったり、品質に問題がある場合には、ユーザの変更セットに対してコメントを行い、彼らの編集作業の質とマッピングスキルの向上に協力してください。 + +#### 意図的な間違い編集 + +数は少ないのですが、OpenStreetMapに対して意図的に間違ったデータが追加されることがあり、そうしたデータは即座に巻き戻しが必要となります。 +一例を以下に挙げます。この例では、町や建物、歩道に対して、マッパーの名字が意図的に追加されています。 + +![screenshot 2016-05-03 18 47 00](https://cloud.githubusercontent.com/assets/3423533/14984342/d96fe7ee-115f-11e6-9af5-28ac515d9b28.png) + +#### ドキュメント化されていないインポート + +OpenStreetMapには、オープンなデータセットをインポートすることが可能です。インポートを行う際には[インポートガイドライン](http://wiki.openstreetmap.org/wiki/Import_guidelines)に沿って実施する必要があり、[インポートカタログ](http://wiki.openstreetmap.org/wiki/Import/Catalogue)に対する適切なドキュメンテーションや、インポート専用のアカウント作成などが必要です。もしあなたがドキュメンテーションされていないインポートを発見した場合、詳細なドキュメンテーションを行うよう、変更セットのコメントを通じてリクエストしてください。 + +#### 自動編集 + +OpenStreetMapへの自動的な編集作業は、botやアルゴリズムによるインポートなど、人間による関与が少ない編集作業のことを指します。 + +## OSMChaを利用した疑わしい地図編集の発見 + +**[OSM Changeset Analyzer](http://osmcha.mapbox.com/)**あるいはOSMChaは、[changeset metadata](https://www.openstreetmap.org/api/0.6/changeset/41775489/download)を利用して、OpenStreetMapの変更セットをフィルタし、分析するためのツールです。このツールは地図に行われた変更セットをすべて即時にリストアップし、疑わしい可能性が高い編集へのフラグ付けや、さまざまな観点から成るフィルタを活用して特定の評価基準にマッチする変更セットの抽出を行うことが可能です。 + +![screenshot 2016-09-06 16 00 06](https://cloud.githubusercontent.com/assets/8921295/18270541/0de8330c-744b-11e6-8582-7e49d6acec9d.png) +_Latest changesets listed in OSMCha_ + +変更セットは、そのIDや編集日時、OSMユーザを表示し、さらに、オブジェクトの作成を緑色、変更を黄色、削除を赤色として一覧化、さらにもし変更セットが特定の動き方をしており、なおかつレビューが行われていない場合、その内容が☓印と一緒に表示されます。 + +### 変更セットのフィルタリング + +OSMChaではフィルタを利用することができ、問題のある編集を発見するためにさまざまな観点から検索する機能をもっています。 + +![screenshot 2016-08-30 16 37 31](https://cloud.githubusercontent.com/assets/8921295/18086930/1a28da0c-6ed0-11e6-8eed-5a0b7ee6cf72.png) +_OSMCha filter dialog_ + +OSMChaは、その変更セットで実施された内容によって、`Mass creations（大量削除）` や `Possible import（インポートの可能性）`などのように、変更セットに対して自動的にタグを付与します。 + +![screenshot 2016-08-30 16 48 17](https://cloud.githubusercontent.com/assets/8921295/18087208/932c74c6-6ed1-11e6-8176-d6a1a6bb9f93.png)
+_Filter based on automatic flagging_ + +### 変更セットの品質査定 + +OSMChaでは、タグの変更や地物の追加、変更、削除などを[Changeset map](https://github.com/osmlab/changeset-map/)を使って可視化しています。これにより、明らかな編集ミスなどの品質チェックを簡単に行うことができます。 + +screenshot 2016-08-22 15 16 17
+_A [changeset](http://osmlab.github.io/changeset-map/#41576998/way/24464264) showing an object that incorrectly made into a circle_ + +### 疑わしい変更の発見作業フロー + +#### 疑わしい編集の傾向 + +作業に不慣れなユーザ、削除、インポート： + +- [Maps.meエディタを使った編集](http://osmcha.mapbox.com/?editor__icontains=Maps.Me&is_suspect=False&is_whitelisted=True&harmful=False&checked=False) +- [オブジェクト大量削除](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) +- [iDエディタによる大量削除](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=3) +- [iDエディタによる大量編集](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=4) +- [iDエディタによる大量作成](http://osmcha.mapbox.com/?editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2) +- [インポートの可能性](http://osmcha.mapbox.com/?is_suspect=False&is_whitelisted=True&harmful=False&checked=False&reasons=2) + +フィルタの考え方： + +1. iDエディタは、新規ユーザによるシンプルな編集作業を主な対象として設計されており、より高度な編集はJOSMを使って行われます。そのため、iDエディタを使って大量のデータ削除が行われた場合は、そのユーザが意図せずに削除を行ったか、特に理由なく削除を行った可能性があります。[害のある変更セットの例](http://osmcha.mapbox.com/41628531/) +2. Maps.meユーザはOSM初心者の可能性が高いです。特定のエリア内で、特段の理由もなく多数のPOIを追加している例を探すことを勧めます。これはユーザの経験が浅いことに加え、アプリのプリセットから利用できる施設の例が限られていることが原因としてあげられます。[害のある変更セットの例](http://osmcha.mapbox.com/40927770/) + - Maps.meエディタによる編集はアプリによって自動的にアップロードされます。変更セットコメントは、編集を行った内容に応じてアプリによって自動生成が行われます。Maps.meによる編集をフィルタするには、まずデータ作成のチェックを最初に行うことで、Maps.meユーザによる間違った編集をより見つけやすくすることができます。 +4. iDエディタを使った大量のデータ登録についてもフィルタすることができます。この場合、変更セットの中で作成されたデータのレビューを行い、それらがすべて[OSM編集の規範と慣習](http://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions)に沿って編集されているかどうかを確認してください。[害のある変更セットの例](http://osmcha.mapbox.com/38282141/) +5. これまでの経験からゆくと、`主要なplaceタグのオブジェクト編集/edited an object with a significant place tag`や`主要なタグのオブジェクト編集/edited an object with a significant tag`、`wikipediaランドマークの編集/edited a wikipedia landmark`などのフィルタを使って疑わしい変更セットの検知が可能なったこともありました。[害のある変更セットの例](http://osmcha.mapbox.com/38534916/) +6. 巧妙に行われた破壊行為は、変更セットの規模も小さく、検知が困難です。ただし、[iDエディタによる小規模な変更セット](http://osmcha.mapbox.com/?modify__lte=50&editor__icontains=iD&is_suspect=False&is_whitelisted=True&harmful=False&checked=False)で検索したり、[OSMChaでのランダム検索](http://osmcha.mapbox.com/)を使って、タグの削除や`name`タグの内容変更などを確認することで検知を行うことが可能です。Examples harmful changesets: [1](http://www.openstreetmap.org/node/4331919989), [2](http://www.openstreetmap.org/node/4353068192/history). + +#### 疑わしい変更セットのキーワード設定 + +[私達がこれまでに収集した特定のキーワード](https://docs.google.com/spreadsheets/d/1dqIKycRCwzrEnp-mFv6wnfPc0-V3XjOcm07BrI6kqkw/edit#gid=626639085)を使うことで、これらの単語を含む変更セットを素早く確認することが可能です。例えば"Google"などの厄介な単語などです。 + +#### コミュニティからのデータ破壊行為発見申請と、データワーキンググループによる巻き戻し作業 + +疑わしい変更セットの発見やコメントはコミュニティによっても積極的に行われています。変更セットで行われた編集内容により地図が破壊されてしまった場合、コミュニティはデータワーキンググループに対して情報提供を行い、データワーキンググループによって変更セットの巻き戻しと変更セットへのコメントが行われます。 + +- **キーワード**の活用 + - 変更セットのコメントとして`revert`や`cleanup`、`fix`といった単語を使うことで、コミュニティによって対応が行われている変更セットの大部分を発見する事が可能です。このリストには、データワーキンググループによる巻き戻しや修正作業も含まれます。 + +- [**OSM - comments**](https://www.mapbox.com/osm-comments/)の活用 + - OSM-comments APIを使うことで、特定のパラメータを含む変更セットをクエリすることができます + - OSMで行われたすべてのユーザの変更セットコメントのリンク - [URL for web view](https://www.mapbox.com/osm-comments/#/changesets/?q=users%3A%2A) + +現在のところ、データワーキンググループによってコメントが行われた変更セットを、OSM-Comments-APIだけを使ってすべて一覧表示することはできません。[Issue #44](https://github.com/mapbox/osm-comments-api/issues/44)を参照してください。 + +**データワーキンググループによる巻き戻し作業** + +![documentations1](https://cloud.githubusercontent.com/assets/8921295/18270714/0cc820da-744c-11e6-8db8-71421c956e07.gif) +_Finding Data Working Group reverts using OSMCha_ + +- 特定ユーザによって実施された変更セットをOSMChaでクエリする方法 +- `Woodpeck_repair`, `pnorman_mechanical`など、データワーキンググループのメンバーが巻き戻し作業を行う際に利用するアカウントによる変更セットの一覧家は可能です \ No newline at end of file From e653bf59f4789b1e54fbd48323fe6bd68a85ad6c Mon Sep 17 00:00:00 2001 From: jinalfoflia Date: Thu, 15 Jun 2017 17:51:14 +0530 Subject: [PATCH 56/66] Added license and intro --- _includes/intro/en.html | 4 +++- _includes/intro/jp.html | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/_includes/intro/en.html b/_includes/intro/en.html index a829eb4..c72cc73 100644 --- a/_includes/intro/en.html +++ b/_includes/intro/en.html @@ -1,3 +1,5 @@

OpenStreetMap is the free and editable map of the world, created and maintained by a huge international community. Mapbox Streets, our customizable map layer of streets, buildings, and places from all around the world, is powered by open data from OpenStreetMap. Anybody can create an account and start editing on OpenStreetMap.org within minutes.

-

Our data team updates OpenStreetMap based on quality analysis and customer feedback. Our principle is work in the open. You are welcome to join one of our open mapping projects over on the issue queue and use these best practice mapping guides.

\ No newline at end of file +

Our data team updates OpenStreetMap based on quality analysis and customer feedback. Our principle is work in the open. You are welcome to join one of our open mapping projects over on the issue queue and use these best practice mapping guides.

+ +

These mapping guides are primarily maintained and used by the data team at Mapbox for various mapping projects and in onboarding new team members. These guides are licensed under Public Domain (CC0)

\ No newline at end of file diff --git a/_includes/intro/jp.html b/_includes/intro/jp.html index 8442bad..2ee5cd8 100644 --- a/_includes/intro/jp.html +++ b/_includes/intro/jp.html @@ -1,3 +1,3 @@

OpenStreetMapは自由で編集可能な世界地図であり、世界各国から参加しているボランティアの手によって作成され、メンテナンスが行われています。私達のMapbox Streetは、OpenStreetMapが提供する全世界の道路や建物、地名などのオープンデータを利用して作成されている、カスタマイズ可能な地図レイヤです。アカウントの作成と編集は OpenStreetMap.orgから、数分程度で開始することができます。

-

私達のデータチームは、品質分析や皆様からのフィードバックをもとに、OpenStreetMapを更新しています。私達の活動はオープンに公開して行っています。参加はどなたでも可能です。マッピングプロジェクトへの参加は、オープン状態になっているIssueからお願いします。また、マッピングのベストプラクティスガイドも公開中です。

\ No newline at end of file +

私達のデータチームは、品質分析や皆様からのフィードバックをもとに、OpenStreetMapを更新しています。私達の活動はオープンに公開して行っています。参加はどなたでも可能です。マッピングプロジェクトへの参加は、オープン状態になっているIssueからお願いします。また、マッピングのベストプラクティスガイドも公開中です。These guides are maintained by Satoshi (nyampire) from OpenSteetMap Foundation Japan.

\ No newline at end of file From eb9ec70389f9908a4ddea77660aa7a0dad36d068 Mon Sep 17 00:00:00 2001 From: Andrey Golovin Date: Fri, 16 Jun 2017 17:50:57 +0300 Subject: [PATCH 57/66] Fixing misyping --- getting-started/_posts/0000-01-01-getting-started.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index 293dd57..67e5500 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -87,7 +87,7 @@ To get rid of this error increase the default allocated memory for JOSM by follo ## Using a gaming mouse -Using a gaming can increase your productivity by assigning shortcuts to common mapping tasks. This section outlines the basic configuration to use a gaming in JOSM. +Using a gaming mouse can increase your productivity by assigning shortcuts to common mapping tasks. This section outlines the basic configuration to use a gaming mouse in JOSM. **Systems:** Linux and Mac @@ -104,7 +104,7 @@ Using a gaming can increase your productivity by assigning shortcuts to common m 1. Install Razer Naga config software: https://www.razerzone.com/synapse/ 2. Create an account in razer ID: https://razer-id.razerzone.com/new 3. Build your profile using your email id -4. Configure the mouse: +4. Configure the mouse: **Common shortcuts essential to configure in your gaming mouse for buildings**: Enter, Extrude (`X`), building tracing (`B`), upload and download data to OSM (use the default keyboard shortcuts in your JOSM). @@ -118,7 +118,7 @@ Using a gaming can increase your productivity by assigning shortcuts to common m * Select - * Orthogonalize + * Orthogonalize * Rotate @@ -135,9 +135,9 @@ Using a gaming can increase your productivity by assigning shortcuts to common m * Join node to way (N) * Select intersecting ways (I) - + * Join overlapping ways (shift+J) - + Configure any other shortcut according to the mapper choices. - + **Note**: For mapping other features like roads and to fix task, create separate configurations with the shortcuts required only for those features. From 3157ae8ed473c37207dd97ea6b2658114d0424b5 Mon Sep 17 00:00:00 2001 From: Andrey Golovin Date: Sat, 17 Jun 2017 16:11:19 +0300 Subject: [PATCH 58/66] Mistyping --- getting-started/_posts/0000-01-01-getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/getting-started/_posts/0000-01-01-getting-started.md b/getting-started/_posts/0000-01-01-getting-started.md index 67e5500..4fe80c4 100644 --- a/getting-started/_posts/0000-01-01-getting-started.md +++ b/getting-started/_posts/0000-01-01-getting-started.md @@ -63,7 +63,7 @@ Now it's time to connect to OpenStreetMap. Add the user name and password of the ![set-osm-username-and-password]({{site.baseurl}}/images/set-osm-username-and-password.png) -Now you should be able to retrieve data from OpenStreetMap by clicking on the button with the green down error in the top left: +Now you should be able to retrieve data from OpenStreetMap by clicking on the button with the green down arrow in the top left: ![download-data]({{site.baseurl}}/images/download-data.gif) From 320acdf3242195db5ba3540b2b103ce103f86e57 Mon Sep 17 00:00:00 2001 From: Andrey Golovin Date: Sat, 17 Jun 2017 18:31:41 +0300 Subject: [PATCH 59/66] misc edits --- .../_posts/0000-01-01-osm-data-model.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/osm-data-model/_posts/0000-01-01-osm-data-model.md b/osm-data-model/_posts/0000-01-01-osm-data-model.md index 3fe68eb..c288f02 100644 --- a/osm-data-model/_posts/0000-01-01-osm-data-model.md +++ b/osm-data-model/_posts/0000-01-01-osm-data-model.md @@ -11,8 +11,9 @@ Nodes are the equivalent of a point, ways are like lines that connect points and Nodes are used to represent any kind of point type feature or just to designate a name for a point of interest in the vicinity. Here's a node representing a café: ![node-example1]({{site.baseurl}}/images/node-example1.png) + and here's one representing New York City: - + ![node-example-2]({{site.baseurl}}/images/node-example-2.png) ## Ways @@ -22,15 +23,14 @@ A way is a line feature *connecting two or more nodes* - like a road here: ![way-example-1]({{site.baseurl}}/images/way-example-1.png) If you close a way - by connecting its end to its start, you can map area type features like this building here: - + ![way-example-2]({{site.baseurl}}/images/way-example-2.png) or this park: - -![way-example-3]({{site.baseurl}}/images/way-example-3.png) -Nodes are usually just the items that define a way. But nodes sitting on a way can have their own significance. In this example the node is part of 14th Street and R Street and it also denotes that there's a traffic light. +![way-example-3]({{site.baseurl}}/images/way-example-3.png) +Nodes are usually just the items that define a way. But nodes sitting on a way can have their own significance. In this example the node is part of 10th Street and M Street and it also denotes that there's a traffic light. ![way-example-4]({{site.baseurl}}/images/way-example-4.gif) @@ -40,7 +40,7 @@ Before we hop to the third element next to nodes and ways - relations, let's loo ![osm-tag]({{site.baseurl}}/images/osm-tag.png) -Any point type feature is a node. Whether the node designates a café, a school, a fire hydrant, a tree, a park, a mountainpeak is entirely up to how the node is tagged. Any line type feature is a way. Whether the way is a road, a building, a lake, a railway, a cycleway is again, defined by how it is tagged. +Any point type feature is a node. Whether the node designates a café, a school, a fire hydrant, a tree, a park, a mountain peak is entirely up to how the node is tagged. Any line type feature is a way. Whether the way is a road, a building, a lake, a railway, a cycleway is again, defined by how it is tagged. Tags can be on any element: on nodes, ways and relations. @@ -50,11 +50,10 @@ Relations are used to organize multiple nodes or ways into a larger whole. Take ![relations]({{site.baseurl}}/images/relations.gif) -The type of relation that you'll probably deal most with describes an area with punched out holes - a so called *multipolygon*. Here is an example of a multipolygon building with a yard. It consists of 2 ways with each multiple nodes. One way describes the *outer* wall of the building, the other one the *inner* wall. The ways are part of a relation of the type `type=multipolygon`, the outer way has the role `outer` and the and the inner way has the role `inner`. Note: the `building=yes` tag is on the relation (not on the way). +The type of relation that you'll probably deal most with describes an area with punched out holes - a so called *multipolygon*. Here is an example of a multipolygon building with a yard. It consists of 2 ways with each multiple nodes. One way describes the *outer* wall of the building, the other one the *inner* wall. The ways are part of a relation of the type `type=multipolygon`, the outer way has the role `outer` and the inner way has the role `inner`. Note: the `building=yes` tag is on the relation (not on the way). Your OpenStreetMap editor will take care of creating multipolygons for you so don't worry if this seems dense for now. If you need to fix a multipolygon, this is a good section to come back and review. - ![multipolygon]({{site.baseurl}}/images/multipolygon.gif) ## Further reading @@ -62,4 +61,4 @@ Your OpenStreetMap editor will take care of creating multipolygons for you so do To learn more about the OpenStreetMap data structure, take a look at these resources: - OpenStreetMap Elements http://wiki.openstreetmap.org/wiki/Elements -- Multipolygons http://wiki.openstreetmap.org/wiki/Relation:multipolygon \ No newline at end of file +- Multipolygons http://wiki.openstreetmap.org/wiki/Relation:multipolygon From d3282c34a321372d027942a7edb735bbd51b0d31 Mon Sep 17 00:00:00 2001 From: Andrey Golovin Date: Sat, 17 Jun 2017 22:44:11 +0300 Subject: [PATCH 60/66] linting err --- osm-data-model/_posts/0000-01-01-osm-data-model.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/osm-data-model/_posts/0000-01-01-osm-data-model.md b/osm-data-model/_posts/0000-01-01-osm-data-model.md index c288f02..4d86387 100644 --- a/osm-data-model/_posts/0000-01-01-osm-data-model.md +++ b/osm-data-model/_posts/0000-01-01-osm-data-model.md @@ -60,5 +60,5 @@ Your OpenStreetMap editor will take care of creating multipolygons for you so do To learn more about the OpenStreetMap data structure, take a look at these resources: -- OpenStreetMap Elements http://wiki.openstreetmap.org/wiki/Elements -- Multipolygons http://wiki.openstreetmap.org/wiki/Relation:multipolygon +- OpenStreetMap Elements +- Multipolygons From 5d364f3060161db5f0414648676957d5e1308dc5 Mon Sep 17 00:00:00 2001 From: nyampire Date: Fri, 30 Jun 2017 14:25:22 +0900 Subject: [PATCH 61/66] fix typo on JP translation --- jp/validating-osm/_posts/0000-01-01-validating-osm.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/jp/validating-osm/_posts/0000-01-01-validating-osm.md b/jp/validating-osm/_posts/0000-01-01-validating-osm.md index a5c13f6..135ada4 100644 --- a/jp/validating-osm/_posts/0000-01-01-validating-osm.md +++ b/jp/validating-osm/_posts/0000-01-01-validating-osm.md @@ -8,7 +8,7 @@ Mapboxでは地図データを作成するだけではなく、OpenStreetMapへ OpenStreetMapに加えられる変更は全て、[変更セット](http://wiki.openstreetmap.org/wiki/Changeset)にまとめられています。変更セットには、マッパーによって行われるデータの追加（新規地物）や、変更（タグの修正、地物の位置変更、参照される地物の位置など）、あるいはデータ削除などが含まれます。 -OpenStreetMapのデータを利用していると、誰か他のマッパーが間違った地物やタグを追加したり、大量のデータ削除を行ったり、特定のタグを含んだデータのインポートが行われていたりする場面に遭遇することがありあｍす。OpenStreetMapデータの品質を損なうこれらのデータ変更は、問題のある編集として扱われます。 +OpenStreetMapのデータを利用していると、誰か他のマッパーが間違った地物やタグを追加したり、大量のデータ削除を行ったり、特定のタグを含んだデータのインポートが行われていたりする場面に遭遇することがあります。OpenStreetMapデータの品質を損なうこれらのデータ変更は、問題のある編集として扱われます。 問題のある可能性が高い変更にはいくつかの種類があります。例えば、 @@ -57,8 +57,6 @@ OpenStreetMapのデータを利用していると、誰か他のマッパーが ### マッパーを理解する -The mapper's OSM user profile and [HDYC](http://hdyc.neis-one.org) profile gives an overview of the user's activity and reputation. New mappers are more likely to make unintentional changes; though sometimes a new user account is used for intentional edits that break the map. Experienced mappers might have more detailed, trustworthy knowledge of an area, or sometimes a history of bad edits. - マッパーのOSMユーザプロフィール、および[HDYC](http://hdyc.neis-one.org)のプロフィールを参照することで、ユーザの活動内容と評価を知ることができます。新規マッパーは意図しない間違い編集を行ってしまいがちで、その結果、そのユーザが気が付かないうちに地図データを壊してしまうことがあります。経験豊かなマッパーは、より詳しい記述や、地域に対して信頼できる知識を持っていることがありますが、間違い編集の履歴もあることでしょう。 JOSM履歴ウィンドウのOSMユーザ名をクリックすると、OSMユーザページが表示され、そのユーザの`編集`履歴や、`主な活動範囲`、ユーザのその他活動、そして`日記`エントリを確認する事が可能です。 @@ -111,8 +109,6 @@ OpenStreetMapの変更セットページでは、当該の変更セットの中 JOSMの[Reverter Plugin](http://wiki.openstreetmap.org/wiki/JOSM/Plugins/Reverter)を使うことで、OpenStreetMapの変更を簡単に巻き戻すことが可能です。リバートを行った後は、その変更セットを何故巻き戻したのか、変更セットに対して理由を説明するコメントを残すようにします。 -Reverting changesets can be tricky, and you can unintentionally break things yourself. Attempt to revert a changeset if you are 100% sure that the changeset is bad and if something goes wrong -- you should be able to fix it. - 変更セットの巻き戻しは複雑な作業であり、気が付かないうちに自分自身でデータを破壊してしまうことがあります。巻き戻し対象の変更セットが100％完全に間違いであったり、なにかよくないことが進行中でその修正をあなたが修正しなくてはならない場合にのみ、巻き戻し作業を行うようにしてください ![revert](https://cloud.githubusercontent.com/assets/3423533/14527229/25b55a52-0266-11e6-847d-b9601f8fae8d.gif) From 31a7dc9b7dc4214df5fa77dbcee8c1c4c2a31a4f Mon Sep 17 00:00:00 2001 From: Jothirnadh Sai Guthula Date: Thu, 27 Jul 2017 15:40:53 +0530 Subject: [PATCH 62/66] deleted the older workflow --- ...01-05-adding-exit-and-destination-signs.md | 135 ------------------ 1 file changed, 135 deletions(-) delete mode 100644 mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md diff --git a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md deleted file mode 100644 index 1a62fe6..0000000 --- a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Adding exit and destination signs ---- - -![5138660996_1957ee06ed_o](https://cloud.githubusercontent.com/assets/17887418/15180552/ec541b64-179f-11e6-88d7-4b3074f161e4.jpg) - -## What are exit numbers? - * An exit number is a number assigned to a road junction, usually an exit from a freeway. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the gore. - - ![](https://slack-imgs.com/?c=1&url=https%3A%2F%2Fcloud.githubusercontent.com%2Fassets%2F17470597%2F15181512%2F4ff5546c-17a5-11e6-83ff-bea9cfa20493.jpg) - -### Different tags for exit numbers: -* `ref=*` is used when the exit has a specific number assigned to it. -* `noref=yes` is used when the exit doesn't have any official number assigned to it. - -## How to add exit numbers? - -* Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. - -* Select the assigned highway from the dropdown and click on the `download` button. - - ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) - -### Verify the exits on the route for missing information - -* Load the route in JOSM - -![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) - - ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) - - * Browse along the route and check the ways on both directions at every exit location for the following: - - There is a `motorway_junction` at the start of every `motorway_link` exiting the highway - - The `motorway_junction` has a correct exit number `ref` value as per the source. - - The exit number on both directions are the same - - There is only one exit in a direction for every exit number - -**Add missing exit numbers** - -* Download the data and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) around the blue marker in the imagery. - -* Use a combination of Mapillary, Department of Transportation (DoT) documents and Wikipedia to add the `ref=*` tag on `highway=motorway_junction` (stick to using Mapillary and DoT doc as primary source and move to others in case of unavailability of information) - -* If it is confirmed there is no exit number for the `motorway_junction` add another tag `noref=yes` to indicate the exit does not have an official reference number. - - - -## Analyzing signboards in mapillary - -Look out of Highway sign boards on imagery. They may look something like this- - -![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) - -Places to look for- -- near a `motorway_junction` -- near **start** of a `motorway_link` - -![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) - - - -### Do's and don'ts -- It is not necessary that exit numbers are sequential. It might find 45 after 41. -- There are some `motorway_junction` which don't have any associated exit number. Add `noref=yes` on these nodes. -![no ref](https://cloud.githubusercontent.com/assets/17470597/15071466/65aff514-13a9-11e6-9392-3677c8b193a0.jpg) - -- If there are multiple exits on the same [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs) then you can tag them as `ref=* ; *` instead of `ref:left=*` and `ref:right=*` until you are confirmed with that. - -- In the case of discrepancy between mapillary and DoT document, look out for the recent change in exit numbers on the web. Many states changes/in a process to change the exit numbers. -- **Ignore the `highway=motorway_junction` where the traffic flow is towards the motorway** - - -## What are destination tags? - -* Destination tags describe the content of signposts or ground writing indicating the names of the locations that a certain exit from the freeway or a highway is heading to. -* The key `destination=*` describes where a certain exit leads to. Thus navigation systems can refer to road signs that the driver actually sees. - -![24-wa_i-5_n_exit_164a__1_](https://cloud.githubusercontent.com/assets/17887418/15180428/2f96a4c4-179f-11e6-88ee-4b4e8857c441.jpg) - -### Different tags for destinations: -* `destination` tag refers to the place that the way exiting from the freeway leads to. -* `destination:ref` is the reference of the roads directly ahead. -* `destination:ref:to` is to specify the reference of a major highway ahead. -* `destination:street` refers to the main street the way exiting from the freeway leads to. - -## How to add destination tags? - -### Assign a highway and use Checkautopista2 to map features - -1. Open the destination reference document for your assigned city area. Pick a highway to check and assign it on the spreadsheet to avoid conflict. - -2. Open [checkautopista2](http://k1wiosm.github.io/checkautopista2) and zoom to the assigned state. In the search tab (top left corner) click on `search in map` button to load all the visible highways in the bounding box. - -3. Select the assigned highway from the dropdown and click on the `download` button. - - ![che](https://cloud.githubusercontent.com/assets/12744420/14307643/5ab948c2-fbee-11e5-9965-87541edee1a5.gif) - - -4. Look out for red outer circle for missing destination. Use `open in JOSM` button to open the node in JOSM. Orange outer circle represents `exit_to` tag and we don't need to add destination tags in the way. Green outer circle represent that the concern way already has destination tag. - - - ![che1](https://cloud.githubusercontent.com/assets/12744420/14307716/ccdb6296-fbee-11e5-823a-d55b2e66fc6c.gif) - - ![screen shot 2016-04-05 at 6 47 15 pm](https://cloud.githubusercontent.com/assets/12744420/14283008/e09e6a7a-fb5e-11e5-9f24-4f3f5110f3d7.png) - - -5. Download the data around the `motorway_junction` and mapillary layer to locate a [signboard](https://en.wikipedia.org/wiki/Road_signs_in_the_United_States#Interchange_signs). - -7. Use combination Mapillary images, DoT documents, and Wikipedia to add destination as `destination=*` on `motorway_link` ways and the destination highway as `destination:ref=*`. - **Below is a an example** - ![screen shot 2016-03-14 at 6 28 27 pm](https://cloud.githubusercontent.com/assets/12744420/13745188/a12098bc-ea12-11e5-8ffc-9fb839ed5aa2.png) - **On the `highway=motorway_link`(represented by red line) add `destination=Daly City` and `destination:ref=I 280 South`. This can be confirmed with [DoT document](http://www.dot.ca.gov/hq/traffops/engineering/calnexus/pdf/101.pdf) and [wikipedia](https://en.wikipedia.org/wiki/U.S._Route_101_in_California) while searching for exit number 431** - -8. Add any highway missing in the highway spreadsheet. Mark the highway done if all destination tags are mapped/review - - - -## Analyzing signboards in mapillary - -Look out of Highway sign boards on imagery. They may look something like this- - -![fotorcreated](https://cloud.githubusercontent.com/assets/12744420/13744230/6d841f7a-ea0c-11e5-8fdc-3758c39816a9.jpg) - -Places to look for- -- near a `motorway_junction` -- near **start** of a `motorway_link` - -![screen shot 2016-03-11 at 4 56 14 pm](https://cloud.githubusercontent.com/assets/12744420/13700961/3b7559f4-e7aa-11e5-9b57-519a5f7ee070.png) - - - -### Do's and don'ts -- Use `;` to separate multiple destination and refs. -- Read more on [Highway intersection](https://en.wikipedia.org/wiki/Interchange_(road)) to understand them better. - From f33abccd453b20fdee5ffa6a30dbfae9b2c0b0d1 Mon Sep 17 00:00:00 2001 From: Jothirnadh Sai Guthula Date: Thu, 27 Jul 2017 15:44:52 +0530 Subject: [PATCH 63/66] Adding new workflow to map exit destinations --- ...01-05-adding-exit-and-destination-signs.md | 80 +++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md diff --git a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md new file mode 100644 index 0000000..ed4a750 --- /dev/null +++ b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md @@ -0,0 +1,80 @@ +# Exit number and destination mapping +Exit numbers and destinations are used as a part of guidance in routing engine. They help the driver in navigation guidance through on-ramps and off-ramps while routing on major roads. + +![image](https://user-images.githubusercontent.com/8401827/28310471-359dfff4-6bca-11e7-85a9-7f2a4942c9b6.png) + +## What are exit numbers? + +An exit number is a unique alpha-numeric identity assigned to a road junction, usually an exit from where a freeway starts. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the [gore](https://en.wikipedia.org/wiki/Gore_(road)). OSM based guidance systems such as OSRM can use exit numbers as a way to guide drivers to take the right exit during navigation. + +![image](https://d2mxuefqeaa7sj.cloudfront.net/s_9E15E3C9473E7DCE0777B5A1E9261280CC984DAB5FF2C792D39F0C17D7C1920E_1499941784379_I-4_east_exits_111A-B.jpg) + + +### Different tags for mapping exit numbers: + +- `highway=motorway_junction` → is used in representing the specific node as a junction where the exiting way starts +- `ref=*` → is used when the exit has a specific number assigned to it + - Also tag `junction:ref=*` on the connecting `highway=motorway_link` way +- `noref=yes` → is used when the exit doesn’t have any official number assigned to it + +**In California**, exit number signage is inconsistent. The state is in the process of gradually adding exit numbers. In the meantime, it’s common for a freeway exit to lack any exit number sign, even if Wikipedia provides an exit number. If there’s already a `ref` tag on the `highway=motorway_junction` node but no exit number sign appears in Mapillary imagery from within the past year, replace the `ref` tag with `unsigned_ref`. Sometimes there’s no exit number at the exit, but an advance guide sign (the one that says “½ mile” or “1 mile”) does display an exit number. In that case, leave the exit number in `ref`, because a driver would be able to use that information while navigating. + +## What are destinations? + +Destination tags describe the content of road signposts or ground information indicating the names of the locations that a certain exit from the freeway or a highway is heading to, or that a certain entrance to the freeway is heading to. The `destination` tag refers to the place the entering/exiting way is leading to. Thus navigation systems can represent accurate guidance with the respect to road signs that the driver actually sees when driving. The destination references are also alpha-numeric identities which changes from state to state in US. For reference check [the shield dictionary](https://wiki.openstreetmap.org/wiki/United_States_roads_tagging/Routes) to understand how highway shields are represented in different states of US. If you can’t figure out how to map a particular highway shield, look at the `ref` tags on the way that the `motorway_link` way leads to. + +![image](https://d2mxuefqeaa7sj.cloudfront.net/s_9E15E3C9473E7DCE0777B5A1E9261280CC984DAB5FF2C792D39F0C17D7C1920E_1499946385542_I-4_east_exits_111A-B+1.jpg) + + +### Different tags for mapping destination signs: + +- `destination=*` → is referring to the place/street that the ramp (link way) leads to. +- `destination:ref=*` → is the route number of the roads that the ramp leads to +- `destination:ref:to=*` → is the route number of the roads that the ramp **indirectly** leads to +- `destination:street=*` → is an alternative name for the numbered route – **only use in Florida, Kentucky, and Maryland** +- `destination:lanes=*`, `destination:ref:lanes`, etc. → Often the destinations of a road differ from lane to lane. To specify those for every lane, `destination:lanes=*` is used. + + +## How to map exit numbers and destinations? + +Ground based imagery or a field survey is the only way one can verify freeway junctions and road signs. For imagery, Mapillary imagery can be used as a reference to verify and add exit numbers and destinations to mapped highways on OSM. Sometimes [the pavement is marked with a route shield in each lane](http://www.knoxnews.com/story/news/traffic/2016/10/27/knoxville-road-shields-guide--40-drivers/92823646/), indicating the destination ref, in which case you can also use aerial imagery. + +### Node: +Exit numbers are mapped as nodes at the junction's on highways where freeways have exit ways. + +| S.No | Mapillary Image | JOSM representation | OSM tags +---- | ---- | ---- | ---- +1| screen shot 2017-07-18 at 11 23 16 am | screen shot 2017-07-18 at 11 24 50 am |
  • `highway=motorway_junction`
  • `noref=yes`
+2| screen shot 2017-07-18 at 11 48 11 am | screen shot 2017-07-18 at 11 52 15 am |
  • `highway=motorway_junction`
  • `ref=414A`
+3| | |
  • `highway=motorway_junction`
  • `ref=51A;51B`
  • `ref:left=51A`
  • `ref:right=51B`
+4| screen shot 2017-07-20 at 12 28 02 pm | screen shot 2017-07-20 at 12 28 49 pm |
  • `highway=motorway_junction`
  • `ref=56`
Note: Some times exit numbers are placed separately + +### Way: +Destinations are mapped on the `highway=motorway_link` ways that start from the `highway=motorway_junction` node and connect with another road. These are called off-ramps or freeway exits. Destinations are also mapped on the `highway=motorway_link` ways that start from another road and end on the `highway=motorway` way (without a `highway=motorway_junction` node). These are called on-ramps or freeway entrances. + +S.No| Mapillary Image | JOSM representation | OSM tags +---- | ---- | ---- | ---- +1| screen shot 2017-07-18 at 11 48 11 am | screen shot 2017-07-18 at 11 49 17 am |
  • `destination=Hillsdale Boulevard`
  • junction:ref=414A
+2| screen shot 2017-07-18 at 12 25 22 pm | screen shot 2017-07-18 at 12 27 49 pm |
  • `destination=Woodward Avenue;Main Street;Detroit Zoo`
  • `destination:ref=M 1`
  • `junction:ref=16`
Note: `M` [represents](https://wiki.openstreetmap.org/wiki/United_States_roads_tagging/Routes#Michigan) that highway belongs to the state trunkline highways of Michigan state +3| screen shot 2017-07-18 at 1 02 35 pm | screen shot 2017-07-18 at 1 04 13 pm |
  • `destination:ref=I 71 North;US 50 East`
  • `destination:ref:to=I 471;US 52 East`
  • `junction:ref=1B`
Note: `I` [represents](https://wiki.openstreetmap.org/wiki/United_States_roads_tagging/Routes#Nationwide) Interstate highways and `US` represent U.S. Routes. North and East represent the [cardinal direction](https://wiki.openstreetmap.org/wiki/Highway_Directions_In_The_United_States) of the way. Only enter the cardinal direction that is used on the sign; do not guess based on the physical direction of the road. +4| screen shot 2017-07-18 at 2 16 52 pm | screen shot 2017-07-18 at 2 18 59 pm |
  • `destination:ref=KY 1072`
  • `destination:street=Kyles Lane`
  • `destination=Fort Wright;Park Hills`
  • `junction:ref=189`
Note: `KY` comes from the state of Kentucky, where [oval shields represents state routes](https://wiki.openstreetmap.org/wiki/United_States_roads_tagging/Routes#Kentucky). The small letter font represents `destination:street` and are only available in limited US states +5| [![dearborn2](https://user-images.githubusercontent.com/1231218/27760810-277b9be8-5e05-11e7-8f14-6568f83b2e5c.jpg)](https://www.mapillary.com/map/im/mUDqicHyq4in0_OMpYYdkw) | iD |
  • `destination=Dearborn Street;James Street;Madison Street;Spokane`
  • `destination:lanes=Dearborn Street;James Street;Madison Street\|Spokane`
  • `destination:ref=I 90 East`
  • `destination:ref:lanes=\|I 90 East`
  • `junction:ref=164A`
+6| | |
  • `destination=Pocatello`
  • `destination:ref=I 15 North`
Make sure to split the `highway=motorway_link` way at the intersection, so that the on-ramp and off-ramp are represented by separate ways. +7| | |
  • `destination:ref=I 275 West`
  • `destination:ref:to=I 74`
  • `destination=Indianapolis`
+ +### References: +* Shield marks of state routes changes from state to state. Refer to the [shield dictionary](https://wiki.openstreetmap.org/wiki/United_States_roads_tagging/Routes). +* Use [checkautopista2](https://k1wiosm.github.io/checkautopista2/) for identifying missing junctions + +### Abbreviations for texting on sign boards: +| **Shortform** | **Abbrivation** | +| ------ | ------ | +| Rd | Road | +| St | Street | +| Dr | Drive | +| Br | Bridge | +| Ave | Avenue | +| Blvd | Boulevard | +| Pt | Point | +| Pkwy | Parkway| +| Cr | Creek | \ No newline at end of file From 15bea2a65446dd86a1820e47cada78ac5ea92b13 Mon Sep 17 00:00:00 2001 From: Jothirnadh Sai Guthula Date: Thu, 27 Jul 2017 16:06:58 +0530 Subject: [PATCH 64/66] added title --- .../_posts/0000-01-05-adding-exit-and-destination-signs.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md index ed4a750..d02995f 100644 --- a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md +++ b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md @@ -1,4 +1,9 @@ +--- +title: Adding exit and destination signs +--- + # Exit number and destination mapping + Exit numbers and destinations are used as a part of guidance in routing engine. They help the driver in navigation guidance through on-ramps and off-ramps while routing on major roads. ![image](https://user-images.githubusercontent.com/8401827/28310471-359dfff4-6bca-11e7-85a9-7f2a4942c9b6.png) @@ -77,4 +82,4 @@ S.No| Mapillary Image | JOSM representation | OSM tags | Blvd | Boulevard | | Pt | Point | | Pkwy | Parkway| -| Cr | Creek | \ No newline at end of file +| Cr | Creek | From 6f08100b0425677bd50d97856c5607ba55703304 Mon Sep 17 00:00:00 2001 From: Jothirnadh Sai Guthula Date: Thu, 27 Jul 2017 17:02:33 +0530 Subject: [PATCH 65/66] Spell check --- ...01-05-adding-exit-and-destination-signs.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md index d02995f..f39d68e 100644 --- a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md +++ b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md @@ -10,7 +10,7 @@ Exit numbers and destinations are used as a part of guidance in routing engine. ## What are exit numbers? -An exit number is a unique alpha-numeric identity assigned to a road junction, usually an exit from where a freeway starts. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the [gore](https://en.wikipedia.org/wiki/Gore_(road)). OSM based guidance systems such as OSRM can use exit numbers as a way to guide drivers to take the right exit during navigation. +An exit number is a unique alpha-numeric identity assigned to a road junction, usually an exit from where a freeway starts. It is usually marked on the same sign as the destinations of the exit, as well as a sign in the [gore](https://en.wikipedia.org/wiki/Gore_(road)). OpenStreetMap based guidance systems such as OSRM can use exit numbers as a way to guide drivers to take the right exit during navigation. ![image](https://d2mxuefqeaa7sj.cloudfront.net/s_9E15E3C9473E7DCE0777B5A1E9261280CC984DAB5FF2C792D39F0C17D7C1920E_1499941784379_I-4_east_exits_111A-B.jpg) @@ -20,13 +20,13 @@ An exit number is a unique alpha-numeric identity assigned to a road junction, u - `highway=motorway_junction` → is used in representing the specific node as a junction where the exiting way starts - `ref=*` → is used when the exit has a specific number assigned to it - Also tag `junction:ref=*` on the connecting `highway=motorway_link` way -- `noref=yes` → is used when the exit doesn’t have any official number assigned to it +- `noref=yes` → is used when the exit does not have any official number assigned to it -**In California**, exit number signage is inconsistent. The state is in the process of gradually adding exit numbers. In the meantime, it’s common for a freeway exit to lack any exit number sign, even if Wikipedia provides an exit number. If there’s already a `ref` tag on the `highway=motorway_junction` node but no exit number sign appears in Mapillary imagery from within the past year, replace the `ref` tag with `unsigned_ref`. Sometimes there’s no exit number at the exit, but an advance guide sign (the one that says “½ mile” or “1 mile”) does display an exit number. In that case, leave the exit number in `ref`, because a driver would be able to use that information while navigating. +**In California**, exit number signage is inconsistent. The state is gradually adding exit numbers. In the meantime, it’s common for a freeway exit to lack any exit number sign, even if Wikipedia provides an exit number. If there’s already a `ref` tag on the `highway=motorway_junction` node but no exit number sign appears in Mapillary imagery from within the past year, replace the `ref` tag with `unsigned_ref`. Sometimes there’s no exit number at the exit, but an advance guide sign (the one that says “½ mile” or “1 mile”) does display an exit number. In that case, leave the exit number in `ref`, because a driver would be able to use that information while navigating. ## What are destinations? -Destination tags describe the content of road signposts or ground information indicating the names of the locations that a certain exit from the freeway or a highway is heading to, or that a certain entrance to the freeway is heading to. The `destination` tag refers to the place the entering/exiting way is leading to. Thus navigation systems can represent accurate guidance with the respect to road signs that the driver actually sees when driving. The destination references are also alpha-numeric identities which changes from state to state in US. For reference check [the shield dictionary](https://wiki.openstreetmap.org/wiki/United_States_roads_tagging/Routes) to understand how highway shields are represented in different states of US. If you can’t figure out how to map a particular highway shield, look at the `ref` tags on the way that the `motorway_link` way leads to. +Destination tags describe the content of road signposts or ground information indicating the names of the locations that a certain exit from the freeway or a highway is heading to, or that a certain entrance to the freeway is heading to. The `destination` tag refers to the place the entering/exiting way is leading to. Thus navigation systems can represent correct guidance with the respect to road signs that the driver actually sees when driving. The destination references are also alpha-numeric identities which changes from state to state in US. For reference check [the shield dictionary](https://wiki.openstreetmap.org/wiki/United_States_roads_tagging/Routes) to understand how highway shields are represented in different states of US. If you can’t figure out how to map a particular highway shield, look at the `ref` tags on the way that the `motorway_link` way leads to. ![image](https://d2mxuefqeaa7sj.cloudfront.net/s_9E15E3C9473E7DCE0777B5A1E9261280CC984DAB5FF2C792D39F0C17D7C1920E_1499946385542_I-4_east_exits_111A-B+1.jpg) @@ -42,12 +42,12 @@ Destination tags describe the content of road signposts or ground information in ## How to map exit numbers and destinations? -Ground based imagery or a field survey is the only way one can verify freeway junctions and road signs. For imagery, Mapillary imagery can be used as a reference to verify and add exit numbers and destinations to mapped highways on OSM. Sometimes [the pavement is marked with a route shield in each lane](http://www.knoxnews.com/story/news/traffic/2016/10/27/knoxville-road-shields-guide--40-drivers/92823646/), indicating the destination ref, in which case you can also use aerial imagery. +Ground based imagery or a field survey is the only way one can verify freeway junctions and road signs. For imagery, Mapillary imagery can be used as a reference to verify and add exit numbers and destinations to mapped highways on OpenStreetMap. Sometimes [the pavement is marked with a route shield in each lane](http://www.knoxnews.com/story/news/traffic/2016/10/27/knoxville-road-shields-guide--40-drivers/92823646/), indicating the destination ref, in which case you can also use aerial imagery. ### Node: Exit numbers are mapped as nodes at the junction's on highways where freeways have exit ways. -| S.No | Mapillary Image | JOSM representation | OSM tags +| S.No | Mapillary Image | JOSM representation | Tags ---- | ---- | ---- | ---- 1| screen shot 2017-07-18 at 11 23 16 am | screen shot 2017-07-18 at 11 24 50 am |
  • `highway=motorway_junction`
  • `noref=yes`
2| screen shot 2017-07-18 at 11 48 11 am | screen shot 2017-07-18 at 11 52 15 am |
  • `highway=motorway_junction`
  • `ref=414A`
@@ -71,8 +71,8 @@ S.No| Mapillary Image | JOSM representation | OSM tags * Shield marks of state routes changes from state to state. Refer to the [shield dictionary](https://wiki.openstreetmap.org/wiki/United_States_roads_tagging/Routes). * Use [checkautopista2](https://k1wiosm.github.io/checkautopista2/) for identifying missing junctions -### Abbreviations for texting on sign boards: -| **Shortform** | **Abbrivation** | +### Short forms of common words on sign boards: +| **Short-form** | **Full-form** | | ------ | ------ | | Rd | Road | | St | Street | @@ -83,3 +83,6 @@ S.No| Mapillary Image | JOSM representation | OSM tags | Pt | Point | | Pkwy | Parkway| | Cr | Creek | +| Mtn | Mountain | +| Mt | Mount | +| Jct | Junction | From 1389e762027967dd24b94a4820e3b1ea64cd70b7 Mon Sep 17 00:00:00 2001 From: Jothirnadh Sai Guthula Date: Mon, 31 Jul 2017 17:21:37 +0530 Subject: [PATCH 66/66] Added new case for mapping node --- .../_posts/0000-01-05-adding-exit-and-destination-signs.md | 1 + 1 file changed, 1 insertion(+) diff --git a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md index f39d68e..935e1ae 100644 --- a/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md +++ b/mapping-for-navigation/_posts/0000-01-05-adding-exit-and-destination-signs.md @@ -53,6 +53,7 @@ Exit numbers are mapped as nodes at the junction's on highways where freeways ha 2| screen shot 2017-07-18 at 11 48 11 am | screen shot 2017-07-18 at 11 52 15 am |
  • `highway=motorway_junction`
  • `ref=414A`
3| | |
  • `highway=motorway_junction`
  • `ref=51A;51B`
  • `ref:left=51A`
  • `ref:right=51B`
4| screen shot 2017-07-20 at 12 28 02 pm | screen shot 2017-07-20 at 12 28 49 pm |
  • `highway=motorway_junction`
  • `ref=56`
Note: Some times exit numbers are placed separately +5| screen shot 2017-07-31 at 1 42 19 pm |screen shot 2017-07-31 at 5 18 22 pm|
  • `highway=motorway_junction`
  • `ref=236`
  • `name=Gettysburg Pike`
### Way: Destinations are mapped on the `highway=motorway_link` ways that start from the `highway=motorway_junction` node and connect with another road. These are called off-ramps or freeway exits. Destinations are also mapped on the `highway=motorway_link` ways that start from another road and end on the `highway=motorway` way (without a `highway=motorway_junction` node). These are called on-ramps or freeway entrances.