"browser_notice": "This editor is supported in Firefox, Chrome, Safari, Opera, and Internet Explorer 11 and above. Please upgrade your browser or use Potlatch 2 to edit the map.",
"best_imagery": "Best known imagery source for this location",
"switch": "Switch back to this background",
"custom": "Custom",
- "custom_button": "Edit custom background",
- "custom_prompt": "Enter a tile URL template. Valid tokens are:\n - {zoom} or {z}, {x}, {y} for Z/X/Y tile scheme\n - {-y} or {ty} for flipped TMS-style Y coordinates\n - {u} for quadtile scheme\n - {switch:a,b,c} for DNS server multiplexing\n\nExample:\n{example}",
"overlays": "Overlays",
"imagery_source_faq": "Imagery Info / Report a Problem",
+ "instructions": "Enter a tile URL template. Valid tokens are:\n {zoom} or {z}, {x}, {y} for Z/X/Y tile scheme\n {-y} or {ty} for flipped TMS-style Y coordinates\n {u} for quadtile scheme\n {switch:a,b,c} for DNS server multiplexing\n\nExample:\n{example}",
+ "template": {
+ "placeholder": "Enter a url template"
+ }
+ },
+ "custom_data": {
+ "tooltip": "Edit custom data layer",
+ "header": "Custom Map Data Settings",
+ "file": {
+ "instructions": "Choose a local data file. Supported types are:\n .gpx, .kml, .geojson, .json",
+ "label": "Browse files"
+ },
+ "or": "Or",
+ "url": {
+ "instructions": "Enter a data file URL or vector tile URL template. Valid tokens are:\n {zoom} or {z}, {x}, {y} for Z/X/Y tile scheme",
+ "placeholder": "Enter a url"
+ }
+ }
+ },
"restore": {
"heading": "You have unsaved changes",
"description": "Do you wish to restore unsaved changes from a previous editing session?",
"disconnected_highway_tooltip": "Roads should be connected to other roads or building entrances.",
+ "generic_name": "Possible generic name",
+ "generic_name_tooltip": "This feature seems to have a generic name \"{name}\". Please only use the name field to record the official name of a feature.",
"old_multipolygon": "Multipolygon tags on outer way",
"old_multipolygon_tooltip": "This style of multipolygon is deprecated. Please assign the tags to the parent multipolygon instead of the outer way.",
+ "description": "There is more than one node in this spot. Node IDs: {var1}."
+ },
+ "30": {
+ "title": "Non-closed area",
+ "description": "{var1} is tagged with \"{var2}\" and should be a closed loop."
+ },
+ "40": {
+ "title": "Impossible oneway",
+ "description": "The first node {var1} of {var2} is not connected to any other way."
+ },
+ "41": {
+ "description": "The last node {var1} of {var2} is not connected to any other way."
+ },
+ "42": {
+ "description": "You cannot reach {var1} because all ways leading from it are oneway."
+ },
+ "43": {
+ "description": "You cannot escape from {var1} because all ways leading to it are oneway."
+ },
+ "50": {
+ "title": "Almost junction",
+ "description": "{var1} is very close but not connected to way {var2}."
+ },
+ "60": {
+ "title": "Deprecated tag",
+ "description": "{var1} uses deprecated tag \"{var2}\". Please use \"{var3}\" instead."
+ },
+ "70": {
+ "title": "Missing tag",
+ "description": "{var1} has an empty tag: \"{var2}\"."
+ },
+ "71": {
+ "description": "{var1} has no tags."
+ },
+ "72": {
+ "description": "{var1} is not member of any way and doesn't have any tags."
+ },
+ "73": {
+ "description": "{var1} has a \"{var2}\" tag but no \"highway\" tag."
+ },
+ "74": {
+ "description": "{var1} has an empty tag: \"{var2}\"."
+ },
+ "75": {
+ "description": "{var1} has a name \"{var2}\" but no other tags."
+ },
+ "90": {
+ "title": "Motorway without ref tag",
+ "description": "{var1} is tagged as a motorway and therefore needs a \"ref\", \"nat_ref\", or \"int_ref\" tag."
+ },
+ "100": {
+ "title": "Place of worship without religion",
+ "description": "{var1} is tagged as a place of worship and therefore needs a religion tag."
+ },
+ "110": {
+ "title": "Point of interest without name",
+ "description": "{var1} is tagged as a \"{var2}\" and therefore needs a name tag."
+ },
+ "120": {
+ "title": "Way without nodes",
+ "description": "{var1} has just one single node."
+ },
+ "130": {
+ "title": "Disconnected way",
+ "description": "{var1} is not connected to the rest of the map."
+ },
+ "150": {
+ "title": "Railway crossing without tag",
+ "description": "{var1} of a highway and a railway needs to be tagged as \"railway=crossing\" or \"railway=level_crossing\"."
+ },
+ "160": {
+ "title": "Railway layer conflict",
+ "description": "There are ways in different layers (e.g. tunnel or bridge) meeting at {var1}."
+ },
+ "170": {
+ "title": "FIXME tagged item",
+ "description": "{var1} has a FIXME tag: {var2}"
+ },
+ "180": {
+ "title": "Relation without type",
+ "description": "{var1} is missing a \"type\" tag."
+ },
+ "190": {
+ "title": "Intersection without junction",
+ "description": "{var1} intersects the {var2} {var3} but there is no junction node, bridge, or tunnel."
+ },
+ "200": {
+ "title": "Overlapping ways",
+ "description": "{var1} overlaps the {var2} {var3}."
+ },
+ "210": {
+ "title": "Self-intersecting way",
+ "description": "There is an unspecified issue with self intersecting ways."
+ },
+ "211": {
+ "description": "{var1} contains more than one node multiple times. Nodes are {var2}. This may or may not be an error."
+ },
+ "212": {
+ "description": "{var1} has only two different nodes and contains one of them more than once."
+ },
+ "220": {
+ "title": "Misspelled tag",
+ "description": "{var1} is tagged \"{var2}\" where \"{var3}\" looks like \"{var4}\"."
+ },
+ "221": {
+ "description": "{var1} has a suspicious tag \"{var2}\"."
+ },
+ "230": {
+ "title": "Layer conflict",
+ "description": "{var1} is a junction of ways on different layers."
+ },
+ "231": {
+ "description": "{var1} is a junction of ways on different layers: {var2}.",
+ "layer": "(layer: {layer})"
+ },
+ "232": {
+ "description": "{var1} is tagged with \"layer={var2}\". This need not be an error but it looks strange."
+ },
+ "270": {
+ "title": "Unusual motorway connection",
+ "description": "{var1} is a junction of a motorway and a highway other than \"motorway\", \"motorway_link\", \"trunk\", \"rest_area\", or \"construction\". Connection to \"service\" or \"unclassified\" is only valid if it has \"access=no/private\", or it leads to a motorway service area, or if it is a \"service=parking_aisle\"."
+ },
+ "280": {
+ "title": "Boundary issue",
+ "description": "There is an unspecified issue with this boundary."
+ },
+ "281": {
+ "title": "Boundary missing name",
+ "description": "{var1} has no name."
+ },
+ "282": {
+ "title": "Boundary missing admin level",
+ "description": "The boundary of {var1} has no valid numeric admin_level. Please do not mix admin levels (e.g. \"6;7\"). Always tag the lowest admin_level of all boundaries."
+ },
+ "283": {
+ "title": "Boundary not a closed loop",
+ "description": "The boundary of {var1} is not a closed loop."
+ },
+ "284": {
+ "title": "Boundary is split",
+ "description": "The boundary of {var1} splits here."
+ },
+ "285": {
+ "title": "Boundary admin_level too high",
+ "description": "{var1} has \"admin_level={var2}\" but belongs to a relation with lower \"admin_level\" (e.g. higher priority); it should have the lowest \"admin_level\" of all relations."
+ },
+ "290": {
+ "title": "Restriction issue",
+ "description": "There is an unspecified issue with this restriction."
+ },
+ "291": {
+ "title": "Restriction missing type",
+ "description": "{var1} has an unrecognized restriction type."
+ },
+ "292": {
+ "title": "Restriction missing \"from\" way",
+ "description": "{var1} has {var2} \"from\" members, but it should have 1."
+ },
+ "293": {
+ "title": "Restriction missing \"to\" way",
+ "description": "{var1} has {var2} \"to\" members, but it should have 1."
+ },
+ "294": {
+ "title": "Restriction \"from\" or \"to\" is not a way",
+ "description": "{var1} has \"from\" or \"to\" members which should be ways. {var2}."
+ },
+ "295": {
+ "title": "Restriction \"via\" is not an endpoint",
+ "description": "{var1} has a \"via\" (node {var2}) which is not the first or the last member of \"{var3}\" (way {var4})."
+ },
+ "296": {
+ "title": "Unusual restriction angle",
+ "description": "{var1} has a restriction type \"{var2}\" but the angle is {var3} degrees. Maybe the restriction type is not appropriate?"
+ },
+ "297": {
+ "title": "Wrong direction of \"to\" way",
+ "description": "{var1} does not match the direction of \"to\" way {var2}."
+ },
+ "298": {
+ "title": "Redundant restriction - oneway",
+ "description": "{var1} may be redundant. Entry already prohibited by \"oneway\" tag on {var2}."
+ },
+ "300": {
+ "title": "Missing maxspeed",
+ "description": "{var1} is missing a \"maxspeed\" tag and is tagged as motorway, trunk, primary, or secondary."
+ },
+ "310": {
+ "title": "Roundabout issue",
+ "description": "There is an unspecified issue with this roundabout."
+ },
+ "311": {
+ "title": "Roundabout not closed loop",
+ "description": "{var1} is part of a roundabout but is not closed-loop. (Split carriageways approaching a roundabout should not be tagged as roundabout)."
+ },
+ "312": {
+ "title": "Roundabout wrong direction",
+ "description": "If {var1} is in a country with {var2} traffic then its orientation goes the wrong way around."
+ },
+ "313": {
+ "title": "Roundabout weakly connected",
+ "description": "{var1} has only {var2} other road(s) connected. Roundabouts typically have 3 or more."
+ },
+ "320": {
+ "title": "Improper link connection",
+ "description": "{var1} is tagged as \"{var2}\" but doesn't have a connection to any other \"{var3}\" or \"{var4}\"."
+ },
+ "350": {
+ "title": "Improper bridge tag",
+ "description": "{var1} doesn't have a tag in common with its surrounding ways that shows the purpose of this bridge. There should be one of these tags: {var2}."
+ },
+ "360": {
+ "title": "Missing local name tag",
+ "description": "It would be nice if {var1} had a local name tag \"name:XX={var2}\" where XX shows the language of its common name \"{var2}\"."
+ },
+ "370": {
+ "title": "Doubled places",
+ "description": "{var1} has tags in common with the surrounding way {var2} {var3} and seems to be redundant.",
+ "including_the_name": "(including the name {name})"
+ },
+ "380": {
+ "title": "Non-physical use of sport tag",
+ "description": "{var1} is tagged \"{var2}\" but has no physical tag (e.g. \"leisure\", \"building\", \"amenity\", or \"highway\")."
+ },
+ "390": {
+ "title": "Missing tracktype",
+ "description": "{var1} doesn't have a \"tracktype\" tag."
+ },
+ "400": {
+ "title": "Geometry issue",
+ "description": "There is an unspecified issue with the geometry here."
+ },
+ "401": {
+ "title": "Missing turn restriction",
+ "description": "Ways {var1} and {var2} join in a very sharp angle here and there is no oneway tag or turn restriction that prevents turning."
+ },
+ "402": {
+ "title": "Impossible angle",
+ "description": "{var1} bends in a very sharp angle here."
+ },
+ "410": {
+ "title": "Website issue",
+ "description": "There is an unspecified issue with a contact website or URL."
+ },
+ "411": {
+ "description": "{var1} may have an outdated URL: {var2} returned HTTP status code {var3}."
+ },
+ "412": {
+ "description": "{var1} may have an outdated URL: {var2} contained suspicious text \"{var3}\"."
+ },
+ "413": {
+ "description": "{var1} may have an outdated URL: {var2} did not contain keywords \"{var3}\"."
+ }
+ }
+ }
},
"streetside": {
"tooltip": "Streetside photos from Microsoft",
"title": "Photo Overlay (Bing Streetside)",
- "report": "Report a privacy concern with this image"
+ "report": "Report a privacy concern with this image",
"navigation_zoom": "You can zoom in or out by scrolling with the mouse wheel or trackpad, or by clicking the {plus} / {minus} buttons along the side of the map. You can also use the `+`, `-` keys on your keyboard.",
"features_h": "Map Features",
"features": "We use the word *features* to describe things that appear on the map, such as roads, buildings, or points of interest. Anything in the real world can be mapped as a feature on OpenStreetMap. Map features are represented on the map using *points*, *lines*, or *areas*.",
- "nodes_ways": "In OpenStreetmap, points are sometimes called *nodes*, and lines and areas are sometimes called *ways*."
+ "nodes_ways": "In OpenStreetMap, points are sometimes called *nodes*, and lines and areas are sometimes called *ways*."
"boundary": "A *boundary* relation is a group of one or more line features that together form an administrative boundary.",
"boundary_add": "To add a feature to a boundary relation, select the feature and scroll down to the \"All relations\" section of the feature editor, then click the {plus} add button to add this feature to a nearby existing relation or a new relation."
},
+ "notes": {
+ "title": "Notes",
+ "intro": "*Notes* are used to alert other users that a feature requires fixing or attention. Notes mark a specific location on the map. To view existing notes or add new ones, click the {data} **Map data** panel to enable the OpenStreetMap notes layer.",
+ "add_note_h": "Adding Notes",
+ "add_note": "To add a new note, click the {note} **Note** button on the toolbar above the map, or press the shortcut key `4`. This will change the mouse cursor to a cross symbol. To place the new note on the map, position the mouse cursor where the note should go, then {leftclick} left-click or press `Space`.",
+ "move_note": "Only new notes can be moved. To move a note, place the mouse cursor over the new note, then press and hold the {leftclick} left mouse button while dragging the note to its new location.",
+ "update_note_h": "Closing, Reopening, and Commenting",
+ "update_note": "An existing note can be updated by closing it, reopening it, or adding a comment to it. Closing a note indicates that the problem has been resolved. Reopening a note indicates that the original issue is not resolved.",
+ "save_note_h": "Saving Notes",
+ "save_note": "You must save any note edits individually by clicking the buttons below the note comments. Note edits are **not** included in changesets that you upload to OpenStreetMap."
+ },
"imagery": {
"title": "Background Imagery",
"intro": "The background imagery that appears beneath the map data is an important resource for mapping. This imagery can be aerial photos collected from satellites, airplanes, and drones, or it can be scanned historical maps or other freely available source data.",
"sources": "By default, a [Bing Maps](https://www.bing.com/maps/) satellite layer is chosen as the background image. Depending on where you are editing, other imagery sources will be available. Some may be newer or have higher resolution, so it is always useful to check and see which layer is the best one to use as a mapping reference.",
"offsets_h": "Adjusting Imagery Offset",
"offset": "Imagery is sometimes offset slightly from accurate map data. If you see a lot of roads or buildings shifted from the background imagery, it may be the imagery that's incorrect, so don't move them all to match the background. Instead, you can adjust the background so that it matches the existing data by expanding the \"Adjust Imagery Offset\" section at the bottom of the Background Settings pane.",
- "offset_change": "Click on the small triangles to adjust the imagery offset in small steps, or hold the left mouse button and drag within the gray square to slide the imagery into alignment."
+ "offset_change": "Click on the small triangles to adjust the imagery offset in small steps, or hold the {leftclick} left mouse button and drag within the gray square to slide the imagery into alignment."
},
"streetlevel": {
"title": "Street Level Photos",
- "intro": "Street level photos are useful for mapping traffic signs, businesses, and other details that you can't see from satellite and aerial images. The iD editor supports street level photos from [Mapillary](https://www.mapillary.com) and [OpenStreetCam](https://www.openstreetcam.org).",
+ "intro": "Street level photos are useful for mapping traffic signs, businesses, and other details that you can't see from satellite and aerial images. The iD editor supports street level photos from [Bing Streetside](https://www.microsoft.com/en-us/maps/streetside), [Mapillary](https://www.mapillary.com), and [OpenStreetCam](https://www.openstreetcam.org).",
"using_h": "Using Street Level Photos",
"using": "To use street level photos for mapping, click the {data} **Map data** panel on the side of the map to enable or disable the available photo layers.",
"photos": "When enabled, the photo layer displays a line along the sequence of photos. At higher zoom levels, a circle marks at each photo location, and at even higher zoom levels, a cone indicates the direction the camera was facing when the photo was taken.",
"tracing": "The GPS track isn't sent to OpenStreetMap - the best way to use it is to draw on the map, using it as a guide for the new features that you add.",
"upload": "You can also [upload your GPS data to OpenStreetMap](https://www.openstreetmap.org/trace/create) for other users to use."
},
+ "qa": {
+ "title": "Quality Assurance",
+ "intro": "*Quality Assurance* (Q/A) tools can find improper tags, disconnected roads, and other issues with OpenStreetMap, which mappers can then fix. To view existing Q/A issues, click the {data} **Map data** panel to enable a specific Q/A layer.",
+ "tools_h": "Tools",
+ "tools": "The following tools are currently supported: [KeepRight](https://www.keepright.at/). Expect iD to support [Osmose](https://osmose.openstreetmap.fr/), [ImproveOSM](https://improveosm.org/en/), and more Q/A tools in the future.",
+ "issues_h": "Handling Issues",
+ "issues": "Handling Q/A issues is similar to handling notes. Click on a marker to view the issue details in the sidebar. Each tool has its own capabilities, but generally you can comment and/or close an issue."
"terms": "abbey,basilica,bethel,cathedral,chancel,chantry,chapel,church,fold,house of God,house of prayer,house of worship,minster,mission,monastery,mosque,oratory,parish,sacellum,sanctuary,shrine,synagogue,tabernacle,temple"
},
+ "amenity/money_transfer": {
+ "name": "Money Transfer Station",
+ "terms": "money order,check,bill,currency,finance,wire transfer,cable,person to person,cash to cash,exchange"
"terms": "christian,abbey,basilica,bethel,cathedral,chancel,chantry,chapel,fold,house of God,house of prayer,house of worship,minster,mission,oratory,parish,sacellum,sanctuary,shrine,tabernacle,temple"
+ "description": "DigitalGlobe-Premium is a mosaic composed of DigitalGlobe basemap with select regions filled with +Vivid or custom area of interest imagery, 50cm resolution or better, and refreshed more frequently with ongoing updates.",
+ "description": "DigitalGlobe-Standard is a curated set of imagery covering 86% of the earth’s landmass, with 30-60cm resolution where available, backfilled by Landsat. Average age is 2.31 years, with some areas updated 2x per year.",
"description": "At zoom level 16+, public domain map data from the US Census. At lower zooms, only changes since 2006 minus changes already incorporated into OpenStreetMap",
"description": "Talk-in is the official Mailinglist for Indian Community"
},
+ "osm-india-telegram": {
+ "name": "OpenStreetMap India Telegram",
+ "description": "Join our family: {url}"
+ },
"OSM-india-twitter": {
"name": "OpenStreetMap India Twitter",
"description": "We are just a tweet away: {url}"
},
+ "osm-india-website": {
+ "name": "OpenStreetMap India",
+ "description": "Mappers and OpenStreetMap users in India"
+ },
+ "osm-india-wiki": {
+ "name": "OpenStreetMap Wikiproject India",
+ "description": "Everything you need to know about mapping in India: {url}"
+ },
+ "osm-india-youtube": {
+ "name": "OpenStreetMap India Youtube",
+ "description": "Subscribe to our channel: {url}"
+ },
"OSM-India-Puducherry-Facebook": {
"name": "Free Software Hardware Movement - Facebook",
"description": "FSHM Facebook page to know about community events, activities",
"extendedDescription": "FSHM organizes events relating to free software/hardware, technology, activism and OpenStreetMap. Its FB page is the best way to keep in contact with its events."
},
+ "OSM-Puducherry-Mailing-List": {
+ "name": "Free Software Hardware Movement - Mailing List",
+ "description": "FSHM Puducherry mailing list to discuss mapping in Puducherry and other things.",
+ "extendedDescription": "FSHM organizes events relating to free software/hardware, technology, activism and OpenStreetMap."
+ },
"OSM-India-Puducherry-Matrix": {
"name": "Free Software Hardware Movement - Matrix",
"description": "FSHM Riot group to discuss, share and update mapping activities, events in and around Puducherry",
"description": "Improve OpenStreetMap in Indonesia",
"extendedDescription": "Mapping in Indonesia? Have questions, want to connect with the community here? Join us at {Url}. All are welcome!"
},
+ "osm-iran-aparat": {
+ "name": "OpenStreetMap Iran Aparat",
+ "description": "Subscribe to our channel at {url}",
+ "extendedDescription": "A good resource of videos about anything related to OpenStreetMap. Mainly in Persian."
+ },
+ "osm-iran-forum": {
+ "name": "OpenStreetMap Iran web forum",
+ "description": "OpenStreetMap Iran web forum",
+ "extendedDescription": "A web forum for OpenStreetMap users in Iran. Feel free to ask questions and discuss with others!"
+ },
+ "osm-iran-telegram": {
+ "name": "OpenStreetMap Iran Telegram",
+ "description": "You're welcome to join our Telegram channel at {url}. We also have a supergroup of many OSMers interested in Iran. Find its link in bio of channel."
+ },
"OSM-japan-facebook": {
"name": "OpenStreetMap Japan Community",
"description": "Mappers and OpenStreetMap users in Japan"
"description": "Talk-be is the official mailing list for the Belgian OSM community"
},
- "be-maptime": {
- "name": "Maptime Belgium",
- "description": "Social events organized around mapping - beginners most welcome!",
- "extendedDescription": "Maptime is an open learning environment for all levels and degrees of knowledge, offering intentional educational support for the beginner. Maptime is simultaneously flexible and structured, creating space for mapping tutorials, workshops, ongoing projects with a shared goal, and independent/collaborative work time."
"description": "Mappers and OpenStreetMap users, around Portland, ME",
"extendedDescription": "Maptime is, rather literally, time for mapmaking. Our mission is to open the doors of cartographic possibility to anyone interested by creating a time and space for collaborative learning, exploration, and map creation using mapping tools and technologies."
},
+ "MaptimeHRVA-twitter": {
+ "name": "MaptimeHRVA Twitter",
+ "description": "Follow us on Twitter at {url}"
+ },
+ "us-ma-mailinglist": {
+ "name": "Talk-us-massachusetts Mailing List",
+ "description": "Email mailing list for the Massachusetts OSM community"
+ },
"OpenCleveland-meetup": {
"name": "Open Cleveland",
"description": "Improve OpenStreetMap in the Cleveland area",
"description": "Mappers and OpenStreetMap users, developers and enthusiasts in the New York Metropolitan area"
},
+ "OSM-Portland-forum": {
+ "name": "OpenStreetMap PDX Google Group",
+ "description": "Forum and mailing list for OpenStreetMap users in the Portland area",
+ "extendedDescription": "This group is to facilitate improvements to OpenStreetMap in the Portland, Oregon area to support applications such as the Open Trip Planner."
+ },
"OSM-Portland": {
"name": "OpenStreetMap Portland",
"description": "Mappers and OpenStreetMap users in the Portland area",
"description": "We help grow and improve OpenStreetMap in the United States.",
- "extendedDescription": "We support OpenStreetMap by holding annual conferences, providing community resources, building partnerships, and by spreading the word. Join OpenStreetMap US here: {signupUrl}"
+ "extendedDescription": "We support OpenStreetMap by holding annual conferences, providing community resources, building partnerships, and by spreading the word. Join OpenStreetMap US here: {signupUrl}",
+ "events": {
+ "sotmus2018": {
+ "name": "State of the Map US 2018",
+ "description": "Join the OpenStreetMap community at State of the Map US in Detroit, Michigan. Connect with other mappers, businesses, government agencies, and non profits, all collaborating around the free and editable map of the world.",
"description": "News and resources for the OpenStreetMap Peru community"
},
+ "LATAM-Facebook": {
+ "name": "OpenStreetMap Latam Facebook",
+ "description": "OpenStreetMap Latam on Facebook"
+ },
+ "LATAM-Telegram": {
+ "name": "OpenStreetMap Latam Telegram",
+ "description": "OpenStreetMap Telegram for Latin America"
+ },
+ "LATAM-Twitter": {
+ "name": "OpenStreetMap Latam Twitter",
+ "description": "Follow us on Twitter at {url}"
+ },
+ "osm-latam": {
+ "name": "OpenStreetMap Latam",
+ "description": "Supporting OpenStreetMap in Latin America",
+ "events": {
+ "sotm-latam-2018": {
+ "name": "State of the Map Latam 2018",
+ "description": "State of the Map Latam is the annual conference for all mappers and users of OpenStreetMap in Latin America. The program includes talks, panels, workshops, and mapathons related to OpenStreetMap.",
+ "where": "Buenos Aires, Argentina"
+ }
+ }
+ },
+ "OSM-Discord": {
+ "name": "OpenStreetMap Discord",
+ "description": "Get in touch with other mappers via Discord"
+ },
"OSM-Facebook": {
"name": "OpenStreetMap on Facebook",
"description": "Like us on Facebook for news and updates about OpenStreetMap."
"description": "Ask a question and get answers on OSM's community-driven question and answer site.",
"extendedDescription": "{url} is for everyone who needs help with OpenStreetMap. Whether you are a beginner mapper or have a technical question, we're here to help!"
},
+ "OSM-IRC": {
+ "name": "OpenStreetMap IRC",
+ "description": "Join #osm on irc.oftc.net (port 6667)"
+ },
"OSM-Reddit": {
"name": "OpenStreetMap on Reddit",
"description": "/r/openstreetmap/ is a great place to learn more about OpenStreetMap. Ask us anything!"