Diary Entries in English

Recent diary entries

Mapper shirt

Posted by leodobrasil on 23 July 2015 in English (English)

To work better and safer in localities where a good identification of the mapper as a harmless person is advantageous, I made a "mapper´s shirt" in portuguese. Anyone who needs the files (front and back side, *.png and *.svg format, without the URL) to reprint your personal shirt in a local shirt manufacture, please send a message to my user account informing your mail adress. Camisa de mapeador / mapper shirt / Kartiererhemd

Location: Casas Populares, Residencial Moacyr Moura, Itapetinga, Microrregião de Itapetinga, Mesorregião do Centro-Sul Baiano, Bahia, Northeast Region, 45700000, Brazil

Working on Las Margaritas

Posted by Sunfishtommy on 23 July 2015 in English (English)

Got a little bored of mapping the back country of Chiapas so i began mapping Las Margaritas which i had started about a year ago but only placed a few of the many streets. I have now finished 2 out of the 4 main street quadrants. I am choosing to map it like this because the street names are divided into 4 quadrants. Once I complete the main streets within the city I plan to move to map the surrounding area and towns from Las Margaritas.

I may return to the Backcountry of Chiapas before I completely finish the Las Margaritas area. staying in one place too long can get boring.

Las Margaritas

Backcountry area of Chiapas I have been mapping

New road style for the Default map style - the second version

Posted by Mateusz Konieczny on 23 July 2015 in English (English)

"map styles: Default OSM vs Google Maps" included comparison of OSM Default map and Google maps. Now I present a similar comparison at the same location. But now with a third version - current version of new potential road style.

From left: (1) with changes developed as part of road redesign (2) currently used rendering on OSM website (3) Google maps

Maybe it would be a good idea to make landuse=residential darker on low zoom levels to better mark built up areas, but overall I consider this change as significant improvement.

Changes based on feedback:

Thanks to daganzdaanda for the idea of displaying highway=tertiary as white line, wider than highway=residential/unclassified. As tertiary roads are no longer using yellow it made possible to display secondaries using this color, what it turn allowed to move hue of primary toward yellow.

It was not simple as it sounds. For example, one of obvious consequences is that yellow roads are now rendered also on lower zoom levels. It is problem because the yellow roads are hard to keep visible both on landuse=farmland and unmapped land. For example using light yellow worked great on farmland but completely failed on unmapped land where it was really hard to notice.

Making highway=primary yellower allowed to render trunk in orange and keep road classes possible to differentiate.

So: highway=trunk and highway=motorway are now rendered differently.

See for example highway=trunk near Košice and D1 motorway.

and now with the new style. Game "spot highway=trunk" is now less challenging and it should be distinguishable from motorway.

And view at the preview location from readme

Using a grained fill pattern to indicate unpaved roads is an interesting idea that will be tested. I will also test idea of using dashed casing for unpaved roads with tunnels marked solely by colour change of fill and casing. There was also idea of displaying tunnels as without fill what is also worth testing - but it is likely that displaying unpaved roads as one with dashed casing and fill would be too close. Also, size of ref shields should be reconsidered - it seems possible to make them small without losing readability.


There are also changes to how railway are displayed. Some improvements of rendering railway=tram will be used after next update of map style on OSM servers. But there also problems with rendering railway=rail - both major and minor (marked by service=spur/siding/yard) rails are rendered really close. At lower zoom levels rendering of railway=rail is really close to rendering of minor roads.

I am experimenting with changes to rendering of railways. Some changes are ready to presentation and effects are visible on presented examples.

Accepted changes

I am trying to find as many improvements as possible that may be proposed, discussed, improved and accepted as an isolated change. It makes discussion easier and bugs are less likely.

Turning circles on highway=track are no longer too big, code was improved. In addition highway=proposed is no longer rendered (for discussion and reasoning behind decision see

Currently proposed changes

There are also active pull requests, some of mine are done as part of road redesign. For example there in pull request proposing better display of minor tram tracks It is open question whatever railway=tram with service=spur/siding/yard should be rendered on z14 and z15 - feedback is welcomed (more locations with rendered before/after are listed on github).

Examples of current work

Stopping too early rendering of highway=residential allows to achieve improvements like demonstrated in the first picture demonstrating changed rendering in London. But ceasing to render highway=residential on zoom levels 12 makes noise created by small buildings noticeable. These buildings are too small to be rendered in useful way but big enough to create noticeable changes.

The simplest solution would be to start rendering buildings from z13, one zoom levels later. But some of largest buildings may be usefully rendered on z12. Also, as usually there are additional complications (for example - moving only rendering of buildings to higher zoom level is not enough - it is necessary to move also rendering of amenity=place_of_worship).

On the left - current style. On the right - new style, including removal of highway=residential on this zoom level

And three examples of buildings may be handled:

stop rendering of all buildings (even the largest ones)

stop rendering of small buildings (threshold is arbitrary what is quite noticeable. In many places it is clear that some buildings are rendered and some not despite nearly the same size)

render only big buildings on z12 (my favourite - but it still arbitrary threshold and some big ones will not be rendered. But as rendered buildings are quite rare it is not so noticeable)

OSM Ottawa Summer Meetup 24 July 2015

Posted by Rps333 on 22 July 2015 in English (English)

OSM Ottawa, Summer Meetup will happen 1900 hrs, 24 July, @ Second Cup, 379 Richmond Road, Ottawa, ON

Denis: Will give a 30 min talk on how he used OSM during his 30 day deployment to Nepal as part of the DART. Tom: Will talk about mapping Ottawa heritage John: Will talk about Mapillary and handout some Mapillary swag.

More info:

Mapping Party in Tagbilaran, Bohol

Posted by maning on 21 July 2015 in English (English)

Once again, we had another mapping event. This time, in Tagbilaran City, Bohol. This is part of the series of crowdmapping events co-organized by The Asia Foundation and its local partners. The first was in Iloilo City last May 2015.

Tagbilaran mappers

During the event, Bohol Governor Edgardo Chatto welcomed all the mappers and expressed his support to implement this initiative for the whole province of Bohol.

Bohol's major income is tourism. However, when the 7.2 earthquake hit the island in 2013, the tourism industry was heavily affected. On the other hand, judging by the number of tourists (local and foreign) who was with me during the flight, I think tourism is now recovering. What a better way to help by providing a good map not only for the tourists but also for the local community!

The local partner of The Asia Foundation is the local chamber of commerce. Naturally, we focused on collecting business and tourism related map data during the field exercise.


Using phones powered by OSMAnd, we collected and updated pois: 451, lines: 94, polygons: 168.


I joined one of the field teams and also took the opportunity to kickstart crowdsourcing streetviews using Mapillary.


Other than several hiccups with the internet, the organizers did a very good job in managing the event. I hope the map data we collected will help in expanding the mapping community and help the province in revitalizing its tourism industry.

More notes/photos and map updates in this page:

Location: Taugihon Barangay Headquarters, Pisong, Bohol, Central Visayas, Philippines

About problems with [surface=unpaved; access=destination] roads

Posted by Mateusz Konieczny on 18 July 2015 in English (English)

Render paved/unpaved

Rendering surface value should reduce prevalence of using highway=track for any unpaved road. Unfortunately currently this tagging for renderer is really popular.


There are various styles typically used to depict important low quality roads:

  • (1) lack of fill, only casing is displayed. But it works well on maps where most roads are OK, and only some are of low quality (typical for maps of Australia with unpaved roads across the outback). In areas where all or nearly all roads are unpaved results would be weird - roads render as thin double lines. Also, there would be problems with OSM data model, as rendering of crossings and places where way is split would be poor

  • (2) lack of casing or dashed casing - this style is currently used for tunnels. It would make necessary to find a new style for tunnels what is not easier. Also, people would be highly confused by using of tunnel style with a new meaning.

  • (3) dashed fill (normal road colour & special colour) - it is style that seems the most promising and examples below show how it may work. Roads under contruction are currently using this style - it is also necessary to change it.

  • (4) new separate colours of fill/casing - changing only casing is not really noticeable and/or is ugly, changing colour of fill doubles number of road classes that should be distinguishable. What worse, unpaved and paved of the same class should be similar what is quite hard to achieve. This differentiation is used really rarely, with Humanitarian style as the most prominent example.

  • (5) display in style similar to current highway=track - this style is not working well for important roads of a low quality (there are situations where [highway=primary; surface=unpaved] is used)

  • (6) dashed casing & fill (normal road style & empty space) - this style works better for roads under construction. highway=construction may start using such style

Styling of unpaved roads should:

  • introduce easily noticeable difference between paved and unpaved roads
  • do not introduce highly busy styling
  • make clear that unpaved road is worse than paved road
  • do not make unpaved road more noticeable than paved one
  • keep unpaved and paved road of the same class similar

on the left - current rendering, on the right possible new rendering

Imgur Imgur Imgur

But situation is further complicated by fact that some roads are unpaved with set access=no/private/destination. Ideally it would be clear whatever given private road is also paved/unpaved. Unfortunately this part is not really successful.


On map above it is not immediately clear which road, if any is unpaved.

But in case of private roads it is more important that there is no access than surface value and unpaved roads with access=destination are quite rare so maybe this problem is outweighed by rendering surface value.

One thing that remains to be adjusted is how prominent dashes should be. Below are sets of images with various intensity of dashes. For each location there are four images

left: current rendering right: light dashes

left: light dashes right: moderate dashes

left: moderate dashes right: strong dashes

left: strong dashes right: really strong dashes

Unpaved primary road

City with some unpaved roads

Unpaved service roads. Such roads are very often mapped using highway=track

Paved and unpaved raceways.

City with curvy unpaved roads

Unpaved road with access=private

Unpaved road in the city

Unpaved road in suburbs

Unpaved roads in a village

Unpaved road with access=destination

Unpaved tertiary road

Currently I am planning to use moderate dashes.

Differentiating highway=trunk and highway=motorway

I am working on two version of differentiating of these road types. First keeps all road types in in white-yellow-red gradient, with an additional road class. Second is based on the German map style. Unfortunately, after days of tweaking I am still unhappy about results so I decided to avoid publishing preview.

highway=residential on z12?

flohoff proposed to keep highway=residential on z12

I love the z10 z11 residential road change. I'd like to keep them in z12 for the moment. Residentials often make one get an impression on residential areas and population density. That would get lost.

From my test (some comparison images are linked below) - rendering highway=residential on z12, less prominent than highway=unclassified improves map for locations without mapped landuse=residential. But for places where landuse=residential is mapped it is better to not render these roads.

New osm2pgsql long-term release

Posted by pnorman on 18 July 2015 in English (English)

A new long-term version of osm2pgsql has been released, 0.88.0. This includes the work done in the 0.87.x development series and the porting to C++.

Like all versions, 0.88.0 can be obtained from

Potentially breaking changes

Major new features

One potential use for this feature is matching an existing schema for data, to allow OSM data to be a drop-in replacement.

  • In-memory pending tracking instead of in-database, with significant performance gains.

  • Rendering tables are ordered by GeoHash when created, resulting in significant performance improvements.

  • z_logic has been improved, taking into account more recent work across multiple styles. has more information.

Other changes

  • The node storage has been improved, and out of order nodes and nodes at 0,0 should now always be handled correctly

  • A new test suite with unit tests

  • Many bug-fixes and cleanups

Known issues

  • Append mode is not supported with non-slim. This is suported in 0.89.0-dev, but is frequently a user error. Typically, when a user does this they should instead merge input files with osmosis/osmconvert and use --create

What's next?

osm2pgsql is switching to libosmium for parsing and will require a C++11 compiler. These changes are already in 0.89.0-dev. Beyond this, it depends on contributor time and interest and if anyone decides to pay for development.

Mailing list post:


Posted by Paul Johnson on 17 July 2015 in English (English)


Location: Mingo Trail, Tulsa, Tulsa County, Oklahoma, 74117, United States of America

Feasibility of using satellite night-light data for identifying potential rural settlements

Posted by geotheory on 17 July 2015 in English (English)


This reports the findings of a brief feasibility into the use of satellite night-time imagery data to aid the identification of rural settlements for humanitarian mapping purposes. The data in question is from the US Government's Earth Observation Group. I thought two products looked potentially useful: listed as Visible Infrared Imaging Radiometer Suite (VIIRS) and Defense Meteorological Satellite Program (DMSP). DMSP-OLS is a composite of visual imagery that's been filtered for e.g. cloud cover and moonlight interference (see metadata). VIIRS searches a specific spectral band to identify night-time fires, and comes both as a composite raster surface and a daily list of discrete points of identified fires.

To evaluate these I compare them to the OSM buildings layer of Unity State in South Sudan*, which was recently augmented quite thoroughly by a Missing Maps mapathon. The various EOG datasets come in tiff, png and kml formats, and have been visualised using R. The code for importing, reformatting and plotting the data is posted at Github. Results follow:

First a code demo - plotting the crop of London from the same data:

File F182012.v4c_web.avg_vis.tif

Alt text

South Kivu RGC pre-existing map - has anyone seen this yet?

Posted by Jose Cisneros on 17 July 2015 in English (English)

Looking into what geographic data already exists, I came across this South Kivu map by RGC. It is six years old (mise en carte 2009) and offers an overall perspective of the southern region.

RGC (Referentiel Geographique Commun) was created to "avoid dispersion of data, redundancy of actions and incompatibility of sources". It is administered by two DRC national institutions and many are the members/producers of data (Cluster Logistic, MONUSCO, UNMACC, OSFAC, UNOCHA, UNOPS, ISCO, etc).

The positive side is that the sources are many so perhaps this map could be used as a starting point for mapping the region with more accuracy. The negative side - and major problem - seems to be a lack of validation on the field, which affects its quality.

Has anybody used/seen this map before?

Microtasking from Disaster Mappers - help needed

Posted by pedrito1414 on 17 July 2015 in English (English)

As part of the planning for mapping South Kivu, the Disaster Mappers (and particularly a guy called Benni) have been developing a new microtasking platform for identifying human settlements and road networks before we go anywhere near the tasking manager.

This has been designed for two reasons. Firstly, so mappers don't have to spend hours scanning through the many, many, many square kilometres of jungle that exist in the province. The second is that, by using a much simpler tool for recognition of features, we hope to be able to engage a whole new audience of collaborators. People that might not want to learn iD - or might only have five minutes to spend. If they can do this painstaking work in a relatively easy (and fun?) way, it leaves mappers to... well, map.

Benni's first try at this was great, but we knew it could be better. We sent it out to the Humanitarian OpenStreetMap Team list and got some great feedback.

screenshot of the v2 pybossa microtasking platform

Now there is a version 2. Benni says he has taken this about as far as his skills allow and is asking for help to finish it off. If anyone is interested in collaborating on this, please get in touch by leaving a comment or by tweeting at Missing Maps.

Benni has left some comments on what he has done and the challenges he needs help solving on the original feedback form. Source code available via dropbox, here.

F4map Railway Station Minsk

Posted by shrddr on 16 July 2015 in English (English)

Location: Trinity Hill, Центральный район, Minsk, 220000, Belarus

Help us make a logo! (and win tickets to State of the Map 2016!)

Posted by RobJN on 16 July 2015 in English (English)

The State of the Map working group is pleased[1] to announce a call for logo designs. We need your help to build a strong recognisable logo for State of the Map 2016 (SotM) conference taking place in Brussels, Belgium. The conference is the OpenStreetMap Foundation’s annual gathering of the OSM community, interested parties and others.

We’ve put together a Design Brief which outlines what we’re looking for in a logo. Entrants can be an individual or team of people, even a design company.

The deadline for entries is 23:59 UTC (before midnight) on Saturday 15th August 2015 and we can’t wait to see your all your wonderful entries!

Good luck!

On behalf of the SotM WG

[1] In fact we're delighted - this has been something we've done for previous SotM's and it is always amazing to see your logo ideas :-D

garages and mounuvering forcouts k-points and areaisations

Posted by Govanus on 15 July 2015 in English (English)

Fix up data, defang or remove actively broken stuff. Closed 6 days ago by Andrew Chadwick Tags created_by JOSM/1.5 (8586 en_GB) source local_knowledge;Bing;OSM Discussion

Comment from Govanus about 1 hour ago

ok I just wote a very long essey about the tags that I need left and fetures I need to restore to make the systems I use that rely them to work and the deeaper phlosiphy behind the tags I'd used but moentarilly left the edit box an the text has just all been lost. So I'll try it chunks or put into a diary edit instead. I've been to repair the broken data links but my time is short and the diversion a waste of effort.
Comment from Govanus about 1 hour ago

ok in chunked formed:-

I intended to promote OSM to the garage management teams of operators like the council, whose then system was relient on google and was so week that it had confusion-making location descrepancies on it.
Comment from Govanus about 1 hour ago

next chunk:-
I did specific site surveys to collect the marks, numbers and and names on all the garages I've mannaged to put into osm plus other that ran out of time for.
Comment from Govanus about 1 hour ago

next chunk:-
I use three fields to carry the name or number or assoiciated marks of garages and referances to teach OSM about the offical groupings and blocks used by operators to manage there garages stocks {this was to allow better data services on to the back processing of annotated website maps for customers to pick and find new garages to rent}

Comment from Govanus about 1 hour ago

next chunk:-
I use name correctly to give things phisicaly marked or written on the garages (in the same way I use the name tag when reley legend or symbols on parking spots {such as Owens Way (Way: ♿ (342095176)) })

A data sorter or renderer can filiter away these names if not requied by selecting out names from garage or parking space features.
There are different common renders that do support named garages while others choose not to use them.
Comment from Govanus about 1 hour ago

ok next chunk:-
I found some garages such as most Oxford city gargages have postal addresses, oftern with a variation to the name phisicaly on the garage (to avoid confusion with dwellings with similar numbers or names).

So where I can find these I add the appropriate regular address tags, including a addr:housename or addr:housenumber depending which looks most appropriate for the idividual garage [or bay of they ever come up the same way].
Comment from Govanus about 1 hour ago

next chunk:-
finally I may have access to internal or customer faceing records that carry a referance number or other text string or symbols. These I add to OSM in a normal ref tag; as is normal tag usage.
Comment from Govanus about 1 hour ago

next chunk:-
Now as I use the tags based on the infomation found out about the site: I may have some tags unused where infomation is not confirmed (that might get included when it is found).
...and as the tags are chosen by purpose (not just variation) they may have the same or different values based on real-world usages, of them.
Comment from Govanus 36 minutes ago

next chunk:-
I've foun it usefull to have the HGV Turning head clearly marked on maps as the concreate was originaly relaid with their need in mind, and it helps encorage lorries to use it rather than belive they will need to reverse for meny 100's of meters around tight bends (tighter since some awkward person mistook the road for a car park (originaly a banned process {delivary HGV's ruled}, then ignored by car parkers. Before being allowed in a semi-controled way)), and down a hill with children sometimes out playing too.

This is aspecially trure for those systems that don't render the areas well so not installing confidence into dispatch and drives alike.
Comment from Govanus 20 minutes ago

After a lot of debate there seem to be two settled camps of thought on areaised highways entered into OSM (yes spent a lot of effort trying to the one true path but it isn't there in way I expected).

Some think they should be like other features that get an area=yes tag included to higlight they are area ways and not linear ways. While some think special tags should be used to more easily highlight the relationship between the midway routeing line and the areas by forming a new area:x style tag to form k=area:highway. Sometimes linked with this is the practice of K-nodeing witch which with the right rendering program can developed stop, giveway and simlar features markable on the road (I've been wondering how this works with advanced stop lines that allow bycycles to get to the front of the lights to turn easier accross the taffic flow when its slow or stopped (ithink the secret is in the cycle lane areaising like an L with two effective k-points of natually differing widths),
an example where I've prepared for this is at:-

on the crossroads just outside the King's Arms pub.
Comment from Govanus 14 minutes ago

next chunk:-
So prep the routeing line to give a currently blank(latter to be tagged-up) k-point and then adopt both the area=yes feature method and the area:highway tag system (that will learn to use more of when I look at more on street area details to enter)
this approach is in the wiki along side info on k-points see the links bounceing about oxford high street for more details on this.
Comment from Govanus 2 minutes ago

Finally I've adopted a new highway tag that I explained in a wiki page before using in appropriate places.
this the highway=manoeuvring_forecourt that use for a place that is like a turning_circle, a parking_aisle (service), a driveway (service) and a yard but as it blends the other roles or is enclosed (unlike a parking_aisle (service)) it isn't clearly explaned by any other them individually, and as osm dosn't like me to dump multiple versions of the highway tag into one feature I developed a the new manoeuvring_forecourt to cover it. manoeuvring_forecourt's also oftern have implied parking and loading rules that can be better expressed on a map with some clear differntiation, so I made the wiki page and started to use it. Now I tought of making a type of service but I had thought if turning_circles get top level then so should manoeuvring_forecourt's.
Before you say they aren't supported the Humanitairian renderer dose support them as an all black feature. So they are recognised as a highway type.
Comment from Govanus less than a minute ago

Ok I out of time so I'll fiish up about the indoor problems and lugging a desktop to a public libary to be able to use josm when id and portlatch failed me will be tomorrows continuation.

How to add a relation in OpenStreetMap

Posted by baditaflorin on 15 July 2015 in English (English)

In Romania, we are planning to add the relations for all the national Roads

I made this youtube video-clip to show how easy is to add a relation

Location: Gruia, Cluj-Napoca, Cluj, Romania

Mapping Agricultural areas

Posted by TuanIfan on 15 July 2015 in English (English)

Mapping the landuse items such as farmland and orchards have never been easier since the changes to these keys in OSM. However, it may still be a boring job if you are not patient enough to draw all agricultural zones which are often large and covering several other features like ponds (landuse = basin), house (landuse=residential), roads and meadows for grazing (landuse=meadow). These smaller areas are shown in different colours : orange, blue, gray, white and light green respectively. So, it is not a boring job at all when all of these are uploaded and rendered on the map.

Have a look at this farmland Alloway country south of Bundaberg City, QLD, Australia, which I have mapped in recent 3 days. The hardest challenge has been tagging forests - either natural=wood and landuse=forest, however, i prefer forest for protected areas, while wood are smaller, or riverside woodlands.

Alloway, QLD

Before mapping

After mapping Note: not all of the updates are loaded in this view. Zoom in to see more.

New road style for the Default map style - highway=path is evil

Posted by Mateusz Konieczny on 14 July 2015 in English (English)

changes based on feedback (comments on diary and github):

Reverted highway=footway, highway=path changes and restored currently used version. highway=motorway, highway=trunk rendering will be distinguishable. For oneway arrows old blue version also will be considered.

In addition feedback confirmed that it would be a good idea to: render motorway junction labels in red and rework widths of roads.

Example of current rendering of pedestrian area (left - current rendering, right - proposed new rendering). highway=footway styling was rolled back, but highway=pedestrian/living_street is changed.

pedestrian_living street in bratislava master-_new-road-style 18 18 350px master - new-road-style

Request for a testing place

I am looking for well mapped place where displaying highway=residential on z10/z11/z12 makes sense and is desirable. I am also looking place where rendering highway=unclassified at z10 is a good idea. According to my tests rendering these roads later improves situation, except places with badly mapped road types (highway=residential linking towns etc).

highway=residential rendering starting at z13, instead of z10 (on the right - rendering of minor roads starts later) sao paulo new-road-style-_hide-residential -23 591 -46 5642 350px new-road-style - hide-residential tunis tunisia new-road-style-_hide-residential 36 8481 10 2289 350px new-road-style - hide-residential

z10 without both highway=residential and highway=unclassified (on the right - rendering of minor roads starts later) sao paulo new-road-style-_also-un -23 591 -46 5642 350px new-road-style - also-un chennai india new-road-style-_also-un 13 07886 80 27261 350px new-road-style - also-un

After such change it would probably be a good idea to make landuse=residential darker on z10/z11/z12 to make area covered by settlements clear.

Testing road width

I am experimenting with resizing roads and I would welcome feeedback on these presented versions - what is a better version for highway=residential/living_street/pedestrian? Left or right side? Or maybe both are too narrow/wide?

rural area where highway footway are important narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow prague czech republic narrow-subtle-_narrow 50 0853 14 432 350px narrow-subtle - narrow helsinki finland narrow-subtle-_narrow 60 16827 24 93188 350px narrow-subtle - narrow chennai india narrow-subtle-_narrow 13 07886 80 27261 350px narrow-subtle - narrow bangkok thailand narrow-subtle-_narrow 13 7529438 100 4941219 350px narrow-subtle - narrow sao paulo narrow-subtle-_narrow -23 591 -46 5642 350px narrow-subtle - narrow fully mapped residential area narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow ciudad de mexico narrow-subtle-_narrow 19 4216 -99 0817 350px narrow-subtle - narrow roads with tram lines narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow large area with high road density of many types narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow city with high road density narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow krakow - stare miasto narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow european style town narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow european style city narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow extreme road density narrow-subtle-_narrow 14 14 350px narrow-subtle - narrow

Note - I would welcome examples of well mapped rural areas for testing locations.

highway=path, highway=footway problems

according to

highway=path is a generic path, either multi-use or unspecified usage, open to all non-motorized vehicles. The path may have any type of surface.

This includes walking and hiking trails, bike trails and paths, horse and stock trails, mountain bike trails, ski[disputed] and snowmobile trails[disputed] as well as combinations of the above

It is a big problem for designing rendering. Given that definition from wiki highway=path may be anything from paved cycleway, though paved footway or horse trail to mountain bike trail. Some even include snowmobile trails existing only during winter as acceptable feature to be mapped as highway=path.

yes, wiki mentions that it may be tagged highway=path

For general rendering it would be preferable to have two tags - one for footways/path/sidewalks open for pedestrians and second for weird cariations like mountain bike trails and snowmobile trails existing only during winder rather than currentt situation.

But in reality overhelming majority of highway=path is used to map paths that are not more open to non-motorized vehicles than highway=footway. It also seems that as result of difference in Default map style it is very common to consider highway=footway as paved and highway=path as unpaved. Confirmations/refutations are welcomed as my personal experience is mostly limited to Poland - elsewhere it is mostly guessing based on limited research.

So there are following possibilities that may work:

path/footway difference

  • consider highway=path to be unpaved and highway=footway to be paved (current situation)
  • stop differentiating between highway=path and highway=footway (render both using current styling of highway=footway or highway=path)
  • stop differentiating between highway=path and highway=footway, render them differently based on surface tag
  • invent a new tagging style (highly unlikely that something replacing highway=path/footway would be accepted, but current one may be improved - see for example )

special access on highway=path (cycleways, bike trails, snowmobile routes)

  • consider popular combinations equivalent to already rendered road types (curren situation, for example [highway=path; bicycle=designated] is considered to be equivalent of [bighway=cycleway]), ignore other)
  • detect popular combinations, in addition attempt to detect other special cases and do not display highway=path in such cases (foot=no would cause highway=path to not be rendered, except cases where it would be rendered thanks to fitting one of popular combinations)

I would welcome opinions on these possibilities and other ideas that would work. There possibilities that are not listed here because it would lead to poor results. For example differentiate rendering based on both highway=path/footway and surface value with four different stylings is not something that would work. Special rendering for every special case of highway=path is also impossible with style that is supposed to be usable. Ceasing to detect [highway=path; bicycle=designated] makes no sense.

In addition it may be considered to is to treat highway=bridleway as synonym of highway=path given relatively low importance of that way type and high similarity.

rendering highway=proposed

Related to current road restyling - see that contains proposal to stop rendering highway=proposed (in that case comments should be posted on github issue).


rendering highway=road

I am not sure how to display this road type. In some way that it would make clear that it should be changed to proper highway type? But it would make the map ugly. But maybe in situation like that it is acceptable?

Attempt to guess what is the most common proper type and render it in this style or close to it as it done currently? But it breaks The Mapper Feedback Loop, also it result in a confusing map where something that resembles highway=unclassified/residential may be anything.

Stop rendering of highway=road? Provided feedback is "you should not use this tag". It also would be highly confusing, this time for people editing map.

accepted changes

Next pull requests related to clutter on clutter around z10 were merged: start displaying minor rail from z13, fixes #1645 #1647. As result railway=rail ways with service=yard/siding/spur are no longer rendered on z11 and z12.

rail - moscow before after

Stop displaying really small zoos and theme parks After that change smaller ones will appear later and bigger on earlier zoom levels (before/after with current road styling).

In the next post, planned on Thursday (16 VII) I will show how trunk/motorway may be differentiated and proposed rendering of unpaved roads (EDIT: unfortunately this post will be delayed).

Organizing Malls and Medical Centres.

Posted by Excuit on 14 July 2015 in English (English)

Hi together,

I was updating the buildings in my home town and I came across two institutions that made me request a change for handling buildings that are centres for shopping (small scale) or medical purposes.

We have a medical centre just around the corner - a big house with 5 floors and fairly small medical businesses like dentists, optometrists, orthopaedics or just medical doctors. There is no sense in drawing every single doctor into that building - despite not being able to differ between the several floors.

But would it be possible to make a list? A list of doctors on every floor that appears after I click on the medical centre? I would like to write down what clinics can be found in that centre, but right now I'd only be able to create multiple markers that would make the whole thing very hard to understand.

Thanks for helping out.


Mark Waypoints on OSM

Posted by PeterGiant on 14 July 2015 in English (English)

I have been cycling in the Taurus Mountains in Turkey in the summer, and off course water is essentiel. Therefore I have made a waypoint everytime I met a water source, but how do I transfer it to OSM?

Thanks in advance


Potlatch without Flash

Posted by Amaroussi on 14 July 2015 in English (English)


Question for the developers: how will Potlatch be prepared for the day when Adobe Flash finally disappears from the webscape?

Thanks in advance.

Older Entries | Newer Entries