Diary Entries in English

Recent diary entries

Mapillary coverage on OsmAnd

Posted by GOwin on 29 November 2016 in English (English)
Location: Alvir Compound, Little Baguio, District 2, San Juan, Metro Manila, 1500, Philippines

My Area Needed a Lot of Work

Posted by DesertTrip on 29 November 2016 in English (English)

It appears people are using some overlay and just copying it. I live here. They are wrong. There was literally 4 or 5 duplicates of our roads all within a mile or two. Some going east-west and some north-south. Some even diagonally through houses! Several duplicates went straight through mountains. MANY roads were misnamed.

I do hope that people double check before editing in the future.

Go look at what the county GIS maps show!!! Go look at your own street signs. Just don't trust the overlay here. It is WRONG.

I still have many many hours of work to do on my area. This is NUTS.

Location: Cerro Pedrigoso, Mohave County, Arizona, United States of America

Towers and Masts

Posted by BushmanK on 29 November 2016 in English (English)

Browsing through the issues at Openstreetmap-carto (also known as OSM Standard style or "Mapnik" style) tracker on GitHub, I came across several issues, both open and closed, touching the topic of rendering vertical man-made structures such as poles, masts, and towers.

Communication engineering was my thing for awhile, so it always strikes me when at least two of these terms - mast and tower - are used in an uncertain manner. In one of the discussions on GitHub, the difference between masts and towers was called "philosophical". Actually, there is no philosophy (at least if you don't look at wrong and misleading examples in OSM Wiki). Because of that, I've added an engineering definition to pages of man_made=tower and man_made=mast both in English and Russian because what is in the first section of those pages makes zero sense and contradicts the basic principles of tagging, because it uses comparative terms such as "bigger" and "smaller" to distinguish between these structures. Tags tower:construction=guyed* are obviously redundant because if you need that, it means that object must be tagged as a mast, not as a tower.

I didn't want to rewrite the whole "definition" without discussing it, while I don't really believe that discussion could be successful, so I just added clear definition in case if someone would prefer it. Just for the reference:

Mast is a vertical man-made structure, supported by the guy lines and the anchoring system.

Tower is a vertical free-standing man-made structure, supported by its own foundation only.

(Anyone can find it even in Wikipedia, so it makes me wondering, how ignorant an author of these OSM Wiki articles was to write that.)

And it doesn't matter, that some contractors (and regular people after them) calling cellular communication towers "masts". It is not only wrong as it is to use "transistor" to call a radio receiver or "Xerox" to call a copy machine (which is common in some languages), but it makes it impossible to actually distinguish masts from towers for mapping purposes.

So, getting back to rendering, both "inverted T" and "inverted Y" are completely appropriate for tower symbols. Inverted T looks like a tower with a single stem or column, standing on its foundation, tower:construction=freestanding. Inverted Y looks more like a rough outline of a steel lattice tower (more strokes could be added to make it look fancier), tower:construction=lattice.

Masts are a bit more tricky, but just a bit. The most obvious symbol is an "inverted bird foot" symbol, similar to inverted Y with the central stroke, extended all the way to the bottom. It also looks like an inverted antenna symbol used for circuit diagrams. Central stroke represents the mast itself, diagonal strokes represent guy lines.

As a bottom line, rendering of masts and towers is not solely a question of style and preferred icons, it's also a question of using proper definitions. If definitions will get clarified one day, no philosophy will be involved in rendering and tagging anymore. (Personally, I really doubt that it will happen.)

Added from comments: These tags currently do not have "OSM-specific meaning", they are completely mixed into one mess - it is technically impossible to be sure if an object, tagged with man_made=mast is a mast and vice versa. So, changing anything can't do any harm, because it can't be messed up more than it currently is.

People are arguing about that only because almost every person has an own tradition of tagging and thinks that all others have a similar one. But it's not true - different objects are tagged similarly by different people as well as similar objects are tagged differently by them. Belief, that there is any global consistency in tagging masts and towers is just a fallacy.

Good Garden Sheds

Posted by alexkemp on 28 November 2016 in English (English)

The chap that I saw on Phoenix Farm Estate yesterday (Sunday 27 November) could not believe that I thought that his shed was worth a photo. My reasons were simple: partly it was the quality of the build: Google StreetView is October 2014 & shows a very nondescript garage, whilst the modern shed+garage is very smart. However, the reason that clinched it for me was the name that he had put upon the door of the shed next to the garage:

“The Man Cave”

man cave


Phoenix is actually the next estate and not the current one.

Location: Arnold and Carlton, Gedling, Nottinghamshire, East Midlands, England, United Kingdom

Good Gardens

Posted by alexkemp on 28 November 2016 in English (English)

There are some gardens that I come across whilst mapping that simply cry out to be featured in these Diary pages. There are two today, both located on an unadopted road (the householders have to pay for all road upkeep) in Gedling that I first walked on Wednesday 23 November on a truly dreadful day. The rain was interfering with the smartphone's capacitative action, so I went back on last Sunday 27 November.

The first garden below is included simply because I found it sweet (and why not?):


The next seemed to epitomise water action. It was pouring down from above and even flowing in a culvert below, so it seemed only fair to have galleons in a pond as well:

galleons ahoy pond 1

Location: Arnold and Carlton, Gedling, Nottinghamshire, East Midlands, England, United Kingdom

OpenStreetMap Carto release v2.45.0

Posted by kocio on 28 November 2016 in English (English)

Dear all,

Today, v2.45.0 of the openstreetmap-carto stylesheet (the default stylesheet on has been released.

Changes include:

  • Rendering all shops without a specific icon as a dot, not just a whitelist
  • Scrub pattern change to random
  • Changing pitch and track color
  • Railway stations rendering as major buildings
  • Rendering the name of man_made=bridge inside the polygon
  • Documentation updates (including cartography design goals and icon design guidelines)
  • Icons general code cleaning
  • Various bug fixes

Thanks to all the contributors for this release, including micahcochran, a new contributor.

For a full list of commits, see

As always, we welcome any bug reports at

You may also like to know that this release is the first with 3 new project maintainers on board. Please be aware that we're going to drop some legacy dependencies soon (like Mapnik 2), so we're approaching a big version change.

The Ostler Jennings & Scot Grave Farm, Gedling

Posted by alexkemp on 27 November 2016 in English (English)

There is a splendidly-named 1903 house & land called Scot Grave Farm (farmhouse, farmyard) on Arnold Lane that I revisited today (on the older maps it is called “Scotgrave Farm”):

Scot Grave Farm house

The owner has both an old BT red phonebox & red Postbox in his yard:

Scot Grave Farm phonebox

I called to try to find more information about the very odd name but, unfortunately, he was unable to help on that score.

The Farm & house were built 1903 & coincide with the establishment of what became Gedling Pit (originally Digby Coal Company — the slopes of the pit spoil heaps can be seen behind the farm in the photo above). According to a U3A pdf Gedling Colliery began in 1899 and the sinking of shafts 1 & 2 were started in 1900. 27 seams of coal of varying — mostly small — thickness were found until they hit paydirt with the 5’ 2” (1.57m) thick Top Hard seam at 1405’ 0” (428.3m) and the earlier 3’ 9” (1.14m) thick Main Bright at 329m. The colliery finally began to commercially produce coal in 1902.

The farm was used by the pit to house the pit ponies, who were walked to & from the pit each day in two different shifts to work there (one returning as the other walked out). The current owner told me of a Mr Jennings (the final Ostler) & his daughter (Mrs Harrison) who moved to Australia, and wrote him a letter informing him of some of her life & the farm history.

Here is a Nottingham Evening Post picture of the Gedling pit ponies, ready for their 2-week holiday in 1960:

gedling pit ponies

The farm was unoccupied during the strike (probably he was talking about the 1926 General Strike, which was precipitated by the country-wide coal-miners' dispute). Pickets were camped outside the pit & raided the house for it's floorboards as to feed the braziers.

The field next to the farm is being prepped ready for development, as are all the slopes behind the farm (he said 100,000 houses) (that will take a little while to map!).

Location: Scot Grave Farm, Arnold and Carlton, Gedling, Nottinghamshire, East Midlands, England, United Kingdom

Weekly roundup - common errors and unexplained edits observed

Posted by nammala on 27 November 2016 in English (English)

Here are the few observations from the OpenStreetMap edits between 11 November - 25 November. We looked into the filters like mass deletions, iD editor + mass deletions, possible imports, edited a name tag, mass modifications using OSMCHA for reviewing the changesets.


  • Deleted tracks: changeset
  • Added random pedestrian highways and buildings: changeset
  • Deleted highways and few buildings: changeset 1, 2, 3
  • Deleted buildings and some amenities: changeset 1, 2, 3
  • Incorrect tagging: changeset
  • Changed road classification: changeset
  • Deleted neighborhood tags: changeset
  • Added Korean names in name:en tag: changeset
  • Deleted streams: changeset

Community members commented on the following changesets:


  • Added province tags to address: Community member commented and reverted the changeset
  • Undiscussed import: Community member commented and reverted the changeset 1, 2
  • Deleted houses and residential roads: Reverted the changesets with a comment 1, 2, 3
  • Deleted buildings and roads. Community member commented and reverted the changeset.
  • Added orphan nodes over buildings and highways. we reverted the changeset with a comment

These were some of the inconsistent data for this week. Do keep an eye out and comment on changesets, which will make us maintain the quality of data in OpenStreetMap.

Look forward for another roundup next week.

New User Edits

Posted by Glassman on 26 November 2016 in English (English)

One of my goals is to increase the number of mappers in Washington State by contacting them after their first edit with suggestions to help them get involved. My message was taken from the Brussels community. I can't say it helps keep people mapping but it certainly doesn't hurt. At least no one has asked me not to send them messages. (Most just ignore me.)

Because my process is manual, I look at every first edit and fix many of them. Those first edits often have common quality errors. I don't believe they are from bad users, but from a process that could use improvement. We could insist that new users complete a course before they are allowed to edit. But that isn't going to get us new mappers. Having existing mappers validate new users edits takes time away from their normal mapping.

When I do fix an edit, I include the change in the Welcome message. Occasionally I'll leave a changeset message when I'm not sure what they were intending. Originally I was leaving a message and not fixing them, but after realizing that many didn't go back to fix the problem I just started to do it myself.

I tried to look at this from a quality improvement perspective. First collect data then define the problem and finally look at solutions. My new mapper process has been running for over a year. While I haven't done a proper job of documenting errors, something I'd like to do, some just keep reoccurring. Today I'm just focusing one one.

Problem Statement

New users edits do not include the lack of a tag to describe the business. For example, someone added an insurance office. The tag included the name, address, and phone number. Occasionally they will add a tag keyword to indicate what the business does. But no office=insurance. To the editor, this looks a good edit.

The developers did fix the problem of tags with just name=. It now notifies the user that they need to enter more information. We now need to take this to the next level.

Below are two possible solutions. The solutions are for iD since that is the editor most new users use.


  1. If the object is an area, provide two name fields, a building name and a business name. The text field should have appropriate tools tips to help the user select the right box for the name. If the business name is populated, then the user should be prompted to add an appropriate tag to the feature (besides the address.) Address point objects should not have a name field. Name fields should be only be provided with objects that have names such as businesses, places, etc.
  2. is a website to add businesses to OSM. The process doesn't actually add businesses to OSM but leaves a note for a mapper to add the business. The code is on github. I'd like to see the user interface enhanced to help select the correct tags for the business with a version of iD to have the user actually add the business. To move the website out of obscurity, include add business under the edit menu on the main website.

How you can help

  1. Look at new editors in your area. Determine the common errors in their edits.
  2. Is the problem correctly stated?
  3. What other improvements to the process would help?
  4. Are you or your company willing to fund development to improve the process?
  5. What would be a good tool to capture new edit quality errors?

Clifford Snow

OSM go on - Colours, Models and Shadow (EN)

Posted by -karlos- on 26 November 2016 in English (English)

Work is in progress, features are improved and added. See the OSM Wiki page for more details and read some background infos below.

There is an Twitter-Feed: @OSM__go (two underscores!). You may follow the latest activities, upcoming ideas and related things.

Tile processing

Overpass seemed to be slow but my measurement was wrong because Javascript even delays console.log while callback code is running. A close inspection showed: Overpass is great, my code with a lot of string copy was slow and is now replaced by jQuery.js and getJSON. Much better, much faster but there was still that “wait-cursor”. Again it was me. I had simple linear searches for already existing nodes or ways. I replaced them by arrays with the OSM-ID as index. Odd to debug but fast. Now, the default load radius is set up to 800m and still fast. Or fine, if you are in a dense city. Old hardware devices may have trouble and get slow. Now the download will stop.

Thats was not the end. I move the tile/tag decoding and the 3D object placing (not yet parseJSON) away from the callback into the render cycle, sliced in fast steps. Now, the default load radius is set up to 800m and still fine in a dense city. Old devices may break downloading. And you may even move already during the download. - One more thing: The first load will be more slow than thereafter of curse - because of the just in time compiling.

Overpass gives an array of elements, first all node-types, then all ways etc. “parseJSON" can only convert this to an single array with mixed types. Is this good? Building tags may be placed at ways or relations(multipoligon). Decoding code would be the same. So it may be good to have all types in one array. But OSM does not have ONE set of IDs!

What about an “overparseJSON" ?: It should convert to separate arrays, one for notes, ways, and relations. It shouldn’t be hard to morph the jquery-code. And there could be a callback for each node, way, etc. So I could immediately extend the node- and way-instances to my needs like adding the three-ja-mesh.


Even if the shape of buildings are fine, paint makes them more realistic. Handling the tags building:colour and roof:colour was easy. Chroma.js does convert the color tag strings and Three.js ExtrudeGeometry also handles different colours for the sides and the ends. So after 10 lines of code and 1-2h test it was done. But soon Murphy's law strikes back: There are quite a view named colours, not known form three (see wiki). Tags like light_brown or yellow-brown may be handled automatically. But what about spelling errors and unknown colours? That may be a task for the validators like Keepright.


Jan (OSMBuildings) asked me, how fast Three handles shadows: about 20% more rendering time. When you start now, the place around that point has shadows. To show the effect even more, a big disk flies over you. There are still some shadow options to investigate. In the Code, a virtual camera is placed at the shadow casting light. Mostly the graphic card is doing the hard work. This “camera” analyses the shapes, if they cast shadow and if this shadow is seen by the “real” camera. A greyscale bitmap is generated and placed between before the virtual world. Looks good. Todo: move the virtual with the real camera.

Placing Modells

For quite a view buildings, extruding doesn’t make much sense, especially for famous buildings like churches or monuments like the Eifel Tower. There are 3D-models of many of them. To place them in a virtual 3D OSM world doesn’t help for data visualisation but for an realistic view. And it’s cool anyway, if you move around by mouse or with VR glasses.

What to render: Where to store and get the model files?

  • I like the Idea of, but its offline :-( I got in contact, may be we will have the files and set up them on a new server and even extend the service to other formats.
  • Meanwhile I did the two models, OSMBuildings uses. (They are not perfect yet)
  • OSM2WORD and other 3D-viewer seems to have a lot. Who do the to that?
  • What about Google Scetchup? I will try to get and dynamically convert all the models. Three.js does have loaders for many file types, that seems to be no limit. But I am sure there is a copyright prohibiting a use.

How to place: My first answer to the following questions was an OSM relation for each model to place with special tags.

  • First the model file. The concept of OpenBuildingModels is great. A reference to an external server with the file. (server-code, model-name/ID and may be file type.
  • The model may be directed correctly already or we need a tag to do it, useful if a model is used more than once.
  • There may be a tag for scale to, and even a hight-offset.
  • Now we need the place. if there is no existing node to reference to, it has to be placed.
  • Usually there is one ore more building-ways in OSM, representing the building in a 2D map. They have to be removed/skipped by the 3D renderer. So wee need a reference list to them. The solution used by OpenBuildingModels is simpler: One Tag with Server and Model. No direction, size and height. And this tag is added to each building to be replaced by the model. I like that.

Other changes

  • The debug output now shows the FPS (add &hud=1 to the url) Disappointing: 40 down to 10 FPS with 3D models displayed. Strange: it doesn't feel slow.
  • Added new URL parameter: “&keep=1 or 0 for show/don’t Keepright error markers. Default is don’t
  • Level & Layer: Underground objects shouldn’t be seen above, bridges should be raised. Now the tags level and layer are used.
Location: Holborn, St Giles, London Borough of Camden, London, Greater London, England, WC1B, United Kingdom

Adding height to City of San Francisco buildings

Posted by Chetan_Gowda on 25 November 2016 in English (English)

The import team is working to add height data for buildings in the City of San Francisco.

Our goal is to add ONLY height tag to the existing OSM building footprints.


Why we are adding height tag?

Adding height to existing buildings will enhance the data especially when used with popular renderers like OSM Buildings and Mapbox GL JS.

What is the source of data?

We are using raw LIDAR derived building height data released by SF local government under a CC0 (Creative Commons) license (data download here).

How are we combining the height to existing buildings?

For each building in OSM, we compare the footprint from SF goverment buildings, if there is 70% overlap, we add the height. Buildings with existing height tag won't be touched.

The task is hosted in OSM-US. The importing has begun at

Note: Before jumping into the task, please read all the instructions carefully.

To know more about the project, or if you have ideas please post them here:

Fixing the invalid areas of the map

Posted by BharataHS on 25 November 2016 in English (English)

A previous diary post-The invalid areas of the map introduced us to invalid relations formed due to multipolygon relation being broken due to various errors. The post has a comprehensive discussions on different errors, its severity and respective simple fixes. It also has these interesting open questions which needs to be debated.

It seems like a huge majority of the issues need to be carefully reviewed by hand and cleaned up. What does a realistic approach to clean the map look like?

The flexibility of the current map editors allows mappers to continue to create features that don't make sense like a way tagged as a forest. Is it time for stricter validity checks on uploads?

The current diary post walks through the tools which aids in fixing these invalid multi polygon relations which not only remains erroneous part of the map but also affects the map rendering.

Start by reading this documentation on multipolygons if you are trying to understand the basics.

How to identify invalid multipolygons ?

An error debugging tool from Geofabrics - OSM Inspector tool aids in identifying these invalid relations in OpenStreetMap. The tool can be either used in a web browser interface or as a layer in JOSM editor.

To use OSM inspector in a web browser,

  1. Go to
  2. Select Areas from 'View' menu.
  3. Left panel contains the list of all possible errors which enables user to toggle between errors.
  4. The map window highlights the node causing error and allows user to pan, zoom over the map in order to inspect the affected portion of the relation.
  5. The Selection panel at the right edge of the page displays the selected object and the small icons on the top leads you to map editors where one can fix the issue and also to open OpenStreetMap.

screen shot 2016-11-24 at 7 33 41 pm Elements in OSM Inpector tool page

To use it the tool JOSM editor,

  1. Open Imagery preferences from the menu bar.
  2. Find OSM Inspector: Area and activate the layer from the list of available layers or add this as a WMS layer in JOSM
  3. Now, the layer will be listed under the imagery menu.
  4. Load the layer and you will have a layer showing all the broken geometries with nodes highlighting at the region of errors and also a text label which mention the error around the node.

Once the error is rectified, make sure to check the roles and sorting order of the relation from the relation window before uploading the data to OpenStreetMap. Along with the tool, JOSM validator can be used to validate the geometry once it has been fixed.

adding_osmi_josm4 Adding OSM Inspector layer to JOSM

This guide runs through a short tutorial on enabling the OSM Inspector 'Areas' layer and its usage in JOSM. Combination of both these validators results for a powerful error debugging tool to identify and fix errors in invalid relations.

Fixes by Mapbox team

The data team at Mapbox reviewed about 1024 invalid multipolygons and fixed around 70% of them with help of OSM inspector. Out of the rest, about 16% of them were unfixable issues. (Ex. Administrative boundaries of type=boundary and disputed borders; Segment missing in the relation causing ring not closed issues). 6% of them had a number of minor errors (Ex. Touching rings) which were not serious issues as it did neither harmed other data nor affect rendering of the map. Check out more at the fixing broken multipolygon issue.

There exists a huge number of broken/ invalid relations which needs to be fixed. These invalid areas of the map can only be fixed by the local community mappers. Would love to hear any suggestions or feedbacks and other tools that can be utilised to identify the broken multi polygon relations. Have any questions, leave a comment below.

Mapillary Have a Special Hell Reserved Just For Me

Posted by alexkemp on 25 November 2016 in English (English)

Mapillary is a Swedish organisation that, like Marvin the Paranoid Android in Hitchhiker's Guide to the Galaxy, has a Data Centre for storing photographs as big as the planet. When you Register with them you can store GPS-registered photos on their site (really useful when surveying for later mapping).

My profile on Mapillary shows that I've uploaded 3,500 photos and have travelled 179.6 km whilst doing that. It also shows that I've uploaded the last 81 photos 6 times (making 486 total uploads in that sequence).

I'm currently mapping in the north of Nottingham in a district called ‘Gedling’ (south of Arnold Lane and north of Westdale Lane). 81 is a very typical number for me to shoot in a morning or afternoon whilst mapping. I used to use the Mapillary app in JOSM to upload, but tend to upload directly from a browser these days (the JOSM app requires a confirmation within a browser, so I cut out the middleman).

The sequence went very normally with those 81 photos, except that the Mapillary browser did not confirm the uploads within my profile. At first, I also got zero reply from Mapillary support. I kept trying to upload...

I eventually got an email from Katrin at Mapillary support, and she copied the email to Peter. According to the email that Peter sent this morning, the issue was because the “harvester for manually uploaded images has not been running” (he restarted it, so all 6 identical sets of images were harvested at once). Problems with a Harvester seem the correct kind of issue for this time of year.


I sent an email to Peter saying “So, no-one could manually upload photos? And I'm the only one that manually uploads photos?? Good lord.” Fortunately, he seems to have a sense of humour. He replied that:

  • no web-uploaded images have been processed in the last 2 days
  • that affected ~200 people
  • it involved ~500k images
  • mobile apps use another method, so uploads did not actually stop
    (they halved, hence no-one at Mapillary noticed)


A Medical Doctor gets called out to a Sawmill. He has to push through a large crowd of sawmill workers all busily gawping at some scene occurring in the middle. As he gets closer the noise of the mechanical circular saw gets louder & louder...

At the centre is a man with the stump of his left arm wrapped in a bloody cloth. He is stood near the circular saw, whilst being comforted by some colleagues. His hand lies amidst the sawdust at the base of the saw.

The doctor: “Good lord, man, what happened to you?”

The man (a little unsteadily): “Well, doctor, I was working at the saw, and I went like this...” (gestures) “...and GOOD GOD! THERE GOES THE OTHER ONE!”

Coda: 100 million Mapillary Photos Uploaded

An email from Mapillary boasts that they now have 100 million photos on Mapillary. The link says that it has taken 2½ years & 2.1 million km, and was 10m photos last year. My calculation based on the numbers given earlier suggest that it is currently 500k uploads/day (from both mobile apps & web-uploads) = 182.5m/year.

This all suggests a large speed-up in the last year.

Location: Arnold and Carlton, Gedling, Nottinghamshire, East Midlands, England, United Kingdom

Mapping roads and buildings in Singapore!

Posted by poornibadrinath on 24 November 2016 in English (English)

In the last two weeks, as a part of improving the quality of base-map data of Singapore on OpenStreetMap, the Mapbox data team along with the community has completed adding missing streets and buildings in Singapore.

For this task, the team used a combination of Mapbox and Bing satellite imagery to improve the road network and building footprints data. We presently have managed to refresh more than ~1200 kilometers of roads. Additionally, we also have added close to ~40,280 buildings.

Take a look at the visualisation below which shows the buildings added during the last two weeks.



Issues with mapping in Singapore:

  • The main issue that the team encountered was the lack of good quality satellite imagery for both Bing and Mapbox. While Bing had better quality than Mapbox, it was not recent and had huge patches of cloud cover. So secondary sources like Strava were used for verification of major roads during adding missing roads.
  • Also due to the presence of huge number of high rise buildings, there often was distortion and the building footprint had to be very carefully aligned around the base and not the rooftop.

Singapore is a rapidly developing country and satellite imagery is often outdated. It would be great to have the community validate our edits and give any feedback regarding our process in our mapping ticket.

We thank the community for all the support. We look forward to more interactions with the Singapore community.


From Mapbox Data Team.

I want create map like this. based on OpenStreetMap?

Posted by mustafakamil on 24 November 2016 in English (English)


OSM Wiki Spanish Translation

Posted by dcapillae on 23 November 2016 in English (English)

I am collaborating on the OpenStreetMap Wiki Spanish translation. A lot of English articles of the OSM Wiki need a translation into Spanish. They are too many so I think that the best option is to choose the most important pages first, or those another articles that are more attractive depending on personal interests of each one (e. g., pages related to hiking, or mountain biking).

One of the first tasks that I did it was to translate the categories into Spanish following the wiki conventions. Most of people are using the OSM wiki to get help about a particular subject, so a suitable order for the documentation is as important as the translation itself.

OpenStreetMap Wiki Main Page Image: OpenStreetMap Wiki main page. Source: OpenStreetMap Wiki (CC BY-SA 2.0).

Experiments with an airport style

Posted by PlaneMad on 23 November 2016 in English (English)

Some late night weekend experiments resulted in this Airport map style.

Runway and taxiway lights

Terminal buildings

Airport boundaries

My laptop seems to heat up a bit trying to render it, but its great to see the detailed results of all the intricate work of the mappers (hooray runway and taxiway areas!). If you update your airport on OSM, you should see the result on the map in a few minutes. My previous experiment with adding runway lights to maps looked like this

PS: Feel free to build on top of the style, you can download this style.json and upload it into Mapbox Studio for a live map.

Location: Indiranagar 1st Stage, Indiranagar, Bengaluru, Bangalore Urban, Karnataka, 560001, India

mileage convertion when reading 2 points

Posted by 08201956 on 23 November 2016 in English (English)

Anyone know how to convert km into miles on scale reading for 2 points ?


Posted by Frank Munoz on 23 November 2016 in English (English)

Will see

Location: Foothill Road, Cuyama, Santa Barbara County, California, United States of America


Posted by Frank Munoz on 23 November 2016 in English (English)


Location: 8th Street, Sanger, Fresno County, California, 93657, United States of America
Older Entries | Newer Entries