Glossary

From OpenStreetMap Wiki
Jump to navigation Jump to search
Glossary - Other languages

±

This page contains a list of technical and colloquial terms used in and around the OpenStreetMap project. It is mainly aimed at beginning mappers, or beginners in a particular area of the project: most definitions should be two lines at the most.

A · B · C · D · E · F · G · H ·  I  · J · K · L · M · N · O · P · Q · R · S · T · U · V · W · X

information sign

This article is a stub. You can help OpenStreetMap by expanding it.

Note: The list is certainly not complete, and there are many more jargon words in and around OpenStreetMap. The page titles used in the wiki are often short and sweet, with a definition appearing at the top of most pages: you may find your answer by doing a search.

Please improve the Glossary by adding terms useful to beginning mappers (especially if you are one!). If there's any term you'd like to include and aren't sure of the definition, please add it with [STUB] where the definition would be.

A

  • API : Application Programming Interface (aka OSM Protocol). The API allows computer programs to access the OpenStreetMap database. It follows the REST approach to web service construction.
  • Area : A shaded polygon representing, e.g., a park or a building. There is no data primitive for an area: they are represented as a closed ("circular") way having tags suited to areas.
  • Area of interest (AOI) : The region, big or small, in which you map or pay close attention to the map. In a Tasking Manager project or MapRoulette challenge, the geographic region in which the project operates.
  • Armchair mapping : The act of editing the map without surveying (without leaving your chair). This is often done by referencing aerial imagery.
  • Attribute : In the real world, the properties of a real-world object. In the database, the data points that define an element, such as its position or its visibility.
  • ATYL: Any tags you like - A guideline that allows users to freely invent new tags for objects that are verifiable and mappable in OpenStreetMap but for which there is no existing tagging scheme yet.

C

  • Cadastre : an official index map showing the location and extent of plots of land ('parcels') along with their ownership. For the UK example, see INSPIRE.
  • Carto : Properly, OSM Carto
  • Centroid: A mathematically derived point at the center of an area, often used by renderers to place labels. An area's centroid is not guaranteed to be inside it, especially in the case of multipolygons or horseshoe-shaped areas. See Wikipedia.
  • Changeset : A group of edits made by a single user over a certain (short) period of time.
  • Closed way : A way that ends where it begins, like a snake eating its tail. A closed way may represent
(1) a linear feature that also ends where it begins (such as a road forming a roundabout, highway=tertiary);
(2) an area feature (such as a sports pitch, leisure=pitch).
  • Contributor : People who contribute edits and improvements to the Map and other OSM projects. (People like you!)
  • CWG : Communication Working Group, a committee of the OSM Foundation dealing with the press and getting the word out about the current affairs, goals and future of the OSMF and the OpenStreetMap project.

D

  • Database : Where OSM's underlying map data is kept. In simple terms this means information about what things are where in the world; technically a PostgreSQL installation running on various servers, but most applications access it via the API.
  • data item
  • Data primitive : An obsolete term (in OSM) for Elements.
  • DWG : Data Working Group, a committee of the OSM Foundation dealing with copyright infringement, imports and vandalism.

E

  • Editors: software and applications to edit features in the OpenStreetMap database. The human doing the editing is a Contributor.
  • Elements : The basic components of OpenStreetMap's conceptual data model of the physical world. They consist of "Nodes", "Ways" and "Relations".
  • EWG : Engineering Working Group a committee of the OSM Foundation dealing with software development, among other things.
  • Extent: The portion of area of a region show in a map. See Wikipedia:Map extent.

F

G

  • Galileo : a GNSS funded and supported by the EU, through the European Space Agency.
  • Geocoder : a piece of software that converts a textual description into geographic coordinates (see also  Address geocoding)
  • GIS : Geographic information system (see also Wikipedia)
  • GLONASS : a GNSS developed by the Soviet Union, now run by Russia. Due to the geography of Russia, it has been designed to provide better accuracy at high latitudes than GPS.
  • GNSS: Global Navigation Satellite System. Uses signals from satellites to establish where you are. There are several systems: GPS is probably the best known.
  • GNSS tracelog : A collection of records from a satnav system, known as "tracelog".
  • GPS : Global Positioning System. GNSS built and run by the government of the USA.
  • GPS receiver : Device used to establish your position. See GPS.
  • GPS trace: A time series of location points recorded by a GPS receiver, from which the route taken can be inferred (i.e. a GNSS tracelog).
  • GPS track : Variant of GPS trace
  • GPS unit : A GPS receiver
  • GPX : GPS Exchange Format: an XML format used to represent data collected by GPS units. The OSM server accepts data in GPX format before processing it into the OSM data model.

H

I

J

  • Java may refer to these terms:
  • Java Applet : In an OpenStreetMap context you may hear mention of "the java applet" referring to a very old Editing interface which used to appear on the OpenStreetMap.org site superseded by Potlatch and then iD.
  • JOSM : The Java OpenStreetMap editor. It is a map viewing and editing tool written by Imi. It will run on most computers and allows a user to view, edit and upload data to the OpenStreetMap database.

K

  • key=value (also k=something v=something else; key/value pair) : Databases are arranged using "keys" (categories of information) and "values" (specific information). E.g., an object in the database may have the data building=school. Here there is a category of objects, buildings, that are denoted by the key building. The value school further specifies the object by indicating what type of building it is. Sometimes key=value is represented in the form k=building v=school, which is closer to the XML representation.

L

  • Layer : Is used to describe the relative height of map features, to separate different parts of style sheets, a way to show different things in JOSM, etc.
  • Licence : Usually the User Licence, the terms under which anyone can use OSM and its data. Sometimes refers to the Contributor Terms under which contributors licence their work to OSM and to the world in general.
  • Local traffic : Vehicles whose destination or point of origin is in the given area.
  • LWG : Licensing Working Group a committee of the OSM Foundation dealing with licencing and legal matters.

M

  • 'The map' : Strictly, the database (unreadable by humans) of all OSM data. Also used in the conventional sense, i.e., a visual representation of real-world geography. (Check the context.)
  • Map features : Physical features on the ground, that are represented in OSM.
  • Mapping : Ambiguous, but many of us use it anyway:
  • Mapnik : A GIS library; ie, a collection of computer code that does things like reprojecting and rendering geo-spatial data. OSM uses Mapnik to generate tiles for the slippy map.
  • Markup : A very simple computer language that allows an author to use special characters (e.g., ' / < >) to tell a computer how to display some text. Many different markup systems are in use across different OSM channels: it's optional, so don't let it put you off contributing!
  • Multipolygon or multipolygon relation : a relation composed of many polygons.
  • MUTCD: The Manual on Uniform Traffic Control Devices. The standard for traffic signs in the United States, with counterparts in several other countries, which differs markedly from the Vienna Convention.
  • MWG : Membership Working Group, a committee of the OpenStreetMap Foundation that deals with the membership register and fees, as well as promoting membership.

N

  • NMEA : Format used to represent data collected by GPS units.
  • Node : The simplest object in the database, consisting of a "point" with an ID, a latitude and a longitude. Nodes can also have tags.
  • note : a comment that can be added to the map on the home page to inform of an error or something missing on the map

O

  • Object : Often used synonymously with OpenStreetMap "Elements" (Nodes, Ways & Relations. See above.), but can also refer to other technical concepts (ambiguous).
  • OGC : The Open Geospatial Consortium (http://www.opengeospatial.org/). A non-profit body that defines standards for the use and storage of geospatial data.
  • Open : We try to do everything in the spirit of openness. Our maps are "open" in that anyone can use them (licensing issues notwithstanding), anyone can see how they were created, anyone can participate in that process. In addition most of our software is Open Source, meaning that software developers can participate in developing the project in that way.
  • Open Source : Software created in the spirit of openness, and with its source code open for downloading, modifying, and redistributing (for free). To avoid confusion, please don't refer to it as OS!
  • Operating System : Software such as Linux, Mac OS X, Windows or Solaris for low level management of a computer system. Hand-held devices also have one. To avoid confusion, please don't refer to it as OS!
  • Ordnance Survey : UK government mapping agency, with extremely detailed maps collected and funded by the taxpayer... and then sold back to them at prohibitively expensive prices. To avoid confusion, please don't refer to it as OS!
  • OS : May refer to any of three different things: "Open Source", "Operating System", and (in the UK) "Ordnance Survey".
  • OSGeo : The Open Source Geospatial Foundation. Promotes the development and use of Open Source, community-based Geospatial software.
  • OSM : OpenStreetMap. This whole project. See About.
  • OSMF : OpenStreetMap Foundation, a registered not-for-profit company which supports the OpenStreetMap project and serves as its legal identity.
  • .osm : The XML format that is produced by the OSM server. It is used for communication with the API and also for the weekly Planet dumps.
  • OSM Carto : The 'standard' rendering of the map used on the website openstreetmap.org. NB not an 'official' rendering (there isn't one), but influential nevertheless.
  • Overpass : See following entries.
  • Overpass API : A read-only API allowing human beings and machines to interface with the database. Allows for almost any analysis of the map database. Commonly used by contributors to check for mapping errors.
  • Overpass Turbo : An browser-based tool that makes it easier for human beings to extract information from the map database.
  • Overpass Turbo Wizard : A tool that lets you build Overpass queries more easily than writing the query yourself.
  • OWG : Operations Working Group a committee of the OpenStreetMap Foundation that deals with the running and budgeting of the OSMF servers.

P

  • Parameter : [stub]
  • Parcel : (legal or official) A piece of land with defined boundaries. Parcel data may be available from governments to help with mapping.
  • Planet.osm : An osm format file that contains all of the nodes, relations and ways that are stored in the OSM database.
  • Plugin (JOSM term): A smaller piece of software that expands the capabilities of a larger application, in this case, JOSM.
  • Preset: A user-customised list of tags from a pre-existing category, that can be quickly added to an element during editing. (Used in JOSM and iD alike, in slightly different ways.)
  • Projection: A method of translating the roughly spherical surface of the earth to a flat display. The standard projection of OSM material is Plate Carree (no transformation, EPSG:4326). The standard projection for rendering OSM data onto map tiles is Spherical Mercator (EPSG:900913)
  • Protocol : The API.

Q

  • Query: If you want information from a human being, you ask them a question. If you want information from a database you send it a query.
  • Query language (QL): Computers don't speak human, so your queries must be sent in a language the computer understands: in OSM this is usually Overpass QL. Queries consist of a limited set of pre-defined operations which a query server can use to locate data which meet certain criteria.

R

  • Redaction: Removing from view data where the user did not agree to the new OpenStreetMap contributor terms and license change to Open Database License (ODBL). See [1]
  • regex or regular expression : Roughly, a pattern. These are used in a database query when you want to find any and all strings that match the pattern you specify.
  • Ref : a Tag used to enter reference numbers to objects, usually from official sources. For example, all parts of the motorway that runs from London to Cambridge get the tag "ref=M11" see Map_Features on the wiki.
  • Relation : A group of Elements that together behave as if they were a single Element. Each discrete Element is assigned a 'role' within the larger Relation.
  • REST : Web development paradigm which we adopt with our protocol interface (API). It means we make objects available at unique URLs, and follow standard use of HTTP protocol features.
  • Revert: may refer both for undoing deletions and partial or complete changeset rollbacks
  • Router : A service/device for working out a route between two geographical points using OSM or other map data (often for use as a navigation aid).
  • Rendering (noun) : A visual representation of the database (which is itself a coded representation of 'on-the-ground' features). One set of data can be presented (rendered) in different ways: e.g., using different colours and fonts, or showing/suppressing different features.
  • Rendering (verb) : The process of turning raw geospatial data into a human-usable form. Usually the that form is a visual representation: a 'map' in ordinary language.
  • Renderer : Any piece of software that renders the map database into usable form. Usually this means as image files analogous to a traditional paper map, but routers and other specialist software are also renderers.
  • The Rails Port : OSM core components: The protocol interface (API) and the front end website components are often referred to as as "The Rails Port" because there was a large development effort to migrate the software to the Ruby on Rails web development framework. Prior to this, the OSM internals were implemented as a standalone program in the Ruby language.

S

  • Segment : Segments were an element in old versions of the OSM API.
  • SiRFstar III : A GPS chipset by SiRF Technologies.
  • Slippy map : The word 'slippy' (rather than 'static') is used to highlight that a map image can be dragged around allowing a user to see what's off the edge of the display.
  • SotM : The State of the Map is the annual, international conference of OpenStreetMap, organised by the OpenStreetMap Foundation. Also the name for local conferences, organised by local teams and not the OSMF. An example of this is SotM Europe.
  • String : Any sequence of letters and numbers that a computer program treats as a unit. May have a natural language meaning, a computer language meaning, both, or neither.
  • Survey
  • SVG : Scaleable Vector Grapics. XML format for representing vector graphics. SVG maps can exported using the export tab, or created by Osmarender.

T

  • Tag : A representation of an attribute of some object in terms that a database can store. Each tag is a key=value pair. E.g., if a gate is open to all traffic, it can be tagged access=yes. Tagging describes adding tags to elements.
  • Tagging scheme : (also schema) An established system for tagging a particular class of object. The Seamark Tagging Schema is a good example - although other schemes are much less complex than that one.
  • Talk page : A page for talking about a "main" page. E.g., this page is the Glossary. To talk about what's here, you can visit Talk:Glossary. Not to be confused with a User Talk page (see under "U").
  • Template : In the Wiki, a template is a piece of wiki markup that makes text display (render) in a special way (e.g., it may be in a different font). Using a template on a page is called "transcluding" a template: not only is it included, but it can later be changed centrally across (trans) all pages where it is found. See the MediaWiki manual: mw:Help:Templates
  • Tiles : Small image files that make up the slippy map. So called because of their arrangement in a grid.
  • Trace : (noun) Usually refers to a GPS trace (otherwise known a "GPS Track", see Recording GPS tracks), as on the website: traces. For the verb, see Tracing.
  • Tracing : (1) Following features visible in aerial imagery to add objects to the map (e.g. "tracing a building outline"); (2) Creating traces with a GPS receiver.
  • Transclude : See Template.
  • Track : (1) a "GPS track" (see Recording GPS tracks); (2) a type of footpath / rough road (see Track)
  • Tracklog : Yet another word for meaning the same as a GPS track / trace.
  • Transit traffic : vehicles which are only passing through a given area without stopping in it.

U

  • User ID : Strictly, an OSM user's unique identification number. May also refer to a user's User name. Every OSM user has one of each: the numerical user IDs are usually hidden, but are used in some downstream services as a more reliable identifier (they can't be changed).
  • User name (also "Display name") : The name you use to log in to OpenStreetMap. It also appears on your profile page, and in your profile page URL.
  • User talk page : A place where others can talk to you, in public, by posting messages to your personal page. The page address is User talk:<YourUsername>. Don't confuse it with a Talk page: see above under "T".

V

  • Validator : Person or programme that detects mapping errors made by other mappers.
  • Value : The second part of a tag, which goes under a "key". See key=value.
  • Vienna Convention: The Vienna Convention on Road Signs and Signals, which regulates traffic signs in many countries, especially in Europe.

W

  • Way : Technically, an ordered list of one or more Nodes in the database, used to represent a linear feature or an area. Ways are continuous (they cannot have breaks) and non-branching. In more everyday language, a 'way' is a line on the map, which has various properties depending on the tags added to it. (It need not be a 'way' that you can travel along: a fence, for example, is represented by a way with the tag barrier=fence.)
  • wiki : (noun) A website that anyone can edit, not just someone "official". See also here.
  • "Wiki, The" : This website, wiki.openstreetmap.org. The main reference point for information on everything in OSM. Mostly describes best/accepted practice but not always, and definitely not 'the last word'.
  • WGS84 : The geodetic datum that GPS is based upon. All geodata in OSM uses WGS84. This can be very different for geodata gathered from other sources. For example the Royal Observatory in Greenwich is at 0°0'0"E in the ellipsoid for OS maps, but at 0°0'5"W in WGS84.

X

  • XML : eXtensible Markup Language, a markup language that is used for encoding information in documents.

See also

External resources

Retrieved from "https://wiki.openstreetmap.org/w/index.php?title=Glossary&oldid=2770212"