Diary Entries in English

Recent diary entries

Offset database for Bing satellite imagery in Taiwan

Posted by BharataHS on 26 October 2016 in English (English)

Our data team at Mapbox along with the OSM-TW community recently completed mapping and aligning road network in Taiwan. The realignment was carried out mainly based on newly rendered Mapbox satellite imagery and Bing imagery.

Progress over Taiwan during road network realignment.

During this project, we observed offsets in Bing imagery in several areas when compared with Strava and GPS traces. All these offsets are now included in the Imagery Offset Database for the wider community to use.

screen shot 2016-10-26 at 19 25 23Imagery offsets in Taiwan.

For details on how to use the Imagery Offset Database in JOSM, please read @krisna's diary post. For any feedback/suggestions, please comment below.

# Update my Village Road with Mapillary

Posted by Saikat Maiti on 26 October 2016 in English (English)

Today I am going to update my diary about the help of Mapillary photos to update my village roads. Because of canopy cover and poor resolution of Bing Imagery I missed these road before and now it's on map. It's a 10 minutes video.

French valley

Posted by Yawnz1 on 25 October 2016 in English (English)


Location: Gray Squirrel Road, GlenOak Hills, Riverside County, California, 92592, United States of America

Mapping considered Malicious (if Fire Hydrants)

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

In Mysterious Markers (22 Oct) I showed the following ancient markers from the NCWW:

mysterious markers identified

Really, this was a case of “Nothing to see here, please move on” as they were simply older variations on the modern “Sluice Valve” (SV) & “Fire Hydrant” (H) ‘grave-stone’ wall plates used by Severn Trent elsewhere in Nottingham. As escada pointed out in the comments, both hydrants and sluice-valves can be mapped (though currently shown only on the specialist or The kicker came in a comment from Andy Mackey, giving a link to a blog post from Chris Hill in 2012. A 2016 comment in that blog post said that the UK authorities consider mapping Fire Hydrants to be a terrorist act (no kidding):

  1. 16 February 2015: Andy Mabbett made a FoI request to the West Midlands Fire Service for geo-locations of all FH within their area (see
  2. 11 March 2015: Request refused, citing “..for the purposes of safeguarding national security ... protecting potential targets ... protect the critical national infrastructure and national security”
  3. 11 March 2015: Andy requests an internal review of the decision
  4. 3 June 2015: The response “ relevant as the current threat level from terrorism in the United Kingdom is deemed to be SEVERE ... publishing information about water networks and other parts of the critical national infrastructure could expose vulnerabilities in the network and pose a serious risk to public health either through non availability of water resource or contamination of supplies”

I'm now up in arms at Severn Trent. I mean, HOW DARE THEY SUPPORT TERRORISTS? Just look at this public support for terrorists from ST that I found at the top of Moore Road just today (25 Oct):

ST support for terrorists

I mean, how dare they? You can walk down any road in Nottingham & find bright yellow signs clearly marking every vulnerability in the water network, making attacks from the Gestapo as easy as can be. And whilst we are at it, how come that all the street signs are still up?

I think that it is time that the bosses of Severn Trent were rounded up, before it's too late.

As my response, I'm making a point of mapping every Fire Hydrant that I can find. Stupid prats.

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

Cleaning up the streets.

Posted by lukys1 on 25 October 2016 in English (English)

Spent a good part of yesterday and today cleaning up names. In China, names should almost always be in Chinese. There are some exceptions like with certain shop names but things like road names should certainly always be in Chinese. I kept seeing the following problems cropping up:

  1. Abbreviated road names like "name:en=W. Shuncheng Str.".

  2. Mixed Chinese and English/pinyin like "name=文艺路 Wenyi Road".

  3. English road names using 'Lu' instead of 'Road' (Lu is the diacritic-less pinyin for 'road' in Chinese, often used by English speakers when naming Chinese roads even in English).

  4. English names in the name= tag rather than the name:en= tag.

Finding 2 and 4 could be done together. I initially tried to figure out how to use Overpass Turbo to find a mix of hanzi and Latin alphabet, but then I realised it was much simpler than that because no valid Chinese road name would contain Latin letters, so I just had to search name= for Latin letters. The query is as follows:

[out:json][timeout:25]; way["highway"]["name"~"[A-Za-z]"]({{bbox}}); out center;

Actually, as it turns out there might be some valid road names with Latin letters in them. Namely alphanumeric codes like 'G203' or whatever. Whether these should be tagged as name= or ref= I'll leave someone else to figure out. If the name was mixed English/Chinese and name:en= already existed, I just deleted the English from name=. If there was no existing name:en=, I created that tag and moved the English name into it.

Number 3 is also fairly easy to spot.

[out:json][timeout:25]; way["highway"]["name:en"~"Lu$"]({{bbox}}); out center;

Number 1 required a combination of queries (there's probably a way to search for them all in one go but I just did it one by one this time). For example:

[out:json][timeout:25]; way["highway"]["name:en"~"W\\."]({{bbox}}); out center;

This finds all roads like "W. Shuncheng Road" (full stops have to be escaped with two backslashes (and also turns out the markdown for OSM diary entries requires you to escape backslashes)).

The same principle applies for "E.", "S.", and "N.". Then "Rd" is just another simple search. "Str" is similar but needs to be searched as "Str$" to find only occurrences at the end of the line, or else it will match everything with "Str" in it.

Not the most fun in the world but it is certainly a lot more efficient thanks to Overpass Turbo, and I'm happy to say that as far as I can tell the walled part of Xi'an is now completely free of these errors!

Location: 西羊市, 北院门, Lianhu District, Xi'an City, Shaanxi, 710002, China


Posted by Annabil on 25 October 2016 in English (English)

25 TH 10 2016


What ave learnt

how to differentiate the road feature requirements suitable for different areas,

i.e remote areas have limited road tags to highway unclassified,

urban areas go up to primary ,

Location: Kigandazi, Bweyogerere, Kira, Wakiso, Central Region, Uganda

OSM go - 3D Render? (EN)

Posted by -karlos- on 24 October 2016 in English (English)

The improvements of “OSM go” are going on. I was quite proud, as the OSM weekly mentioned it. The handling and the control is usable now. There are keyboard- and URL-commands. The rendering includes building levels and train tracks. The first “Layer” is included: Keepright. It is motivating to clear the errors, marked in the 3D world. A object selector does show its OSM tags.

And did you ever see this in any tool or service?: OSM, rendered in stereo, to see it in a Google Cardboard? OSM go enables you to walk or fly through the virtual world of OSM


Read all details in the OSM-Wiki page for OSM go . There you will also find details to ongoing component states and rendering details. And a todo list at last.

The 3D rendering code was only a preliminary attempt. I wanted to use an existing renderer out of the box. In the last weeks I was no search but did not find a solution. There are really a lot of 2D renderer and even quite a view 3D renderer. Only some use Javascript and I found only one using the framework Three.js. Unfortunately, most of this renders are comertial, even if the code is open source. The client part at last. Often, important functions like OSM tag analysis are hidden in the tile server. They all use a 2D layer as Basis, bridges are not placed in the 3D space as I intend to have. Its almost impossible to read all the pages of so many projects, analyse all the supported features of all tools. I would like to make/have an overview as a table. A good start is the Wiki page for 3D_development.

  • First I had an eye on OSM2WORLD. It offers a more and more realistic view, less data visualisation as I intent. It is written in Java. I remember a framework to run Java in Javascript. May be I just could take the logic like tag analysis.
  • Next was OSMBuildings. Using Javascript but not Three.js but WebGL direct. I had some nice talk and mailing with its creator Jan. We even considered to do a re-implementation with Three. We still try to find a way to work together. But Mapbox seems to be a better place to go for Jan.
  • This days, Mapbox announced its 3D service. Their renderer also uses WebGL directly. The Tiles are binary and kind of a blackbox to me.
  • There is only one 3D render using Three, as far as I know: vizicities. I can’t see much there because the Mapzen tiles it uses are offline now. I will try to update it.

Because of the commercial character of the projects, I do have my doubts. If I add features, they may merge it out of my control, they may change their source incompatible to my code. And if the tile server does to much, I will not be able to do what I have in mind. At last, ist's a hard point to get into a big bunch of code. So I desided to stop my search and improve my simple renderer as much as long as it will be fun. Most renderer try to show a more or less realistic scene. That's not a aim of OSM go to become perfect, but do present the OSM data as a abstract, dynamical view with access to all tags and data. And to edit the data! That's why the next steps will be data and object selection and first edit features. To avoid bad newbie edits, I think about edits, related to the 3D visualisation, like building height and roof type.

Another aim of OSM go is, to experiment mit new features, i.e. a way to move through a augment or virtual world. So the meaning of “go” changed from “as Pokemon" to “go around in OSM and experiment with the data”. One next experiment will be a “Segway-Mode” for 3D glasses. May be avatars to meet other users virtual, chat and edit together. OSM go started as a diffuse gameplay idea and extended to something to “does anything”. But the Idea to improve the OSM data by players is still there. Add missing house numbers to get points, why not. A player will expect an experience with high scores, competitions, batches and motivating optical effects. I would love to code such things. But I need help, may be an artist and designer to develop the whole gameplay.

The Code is still in a beginning state, buggy sometimes, not tested with all devices. Please try it and tell me, how it went, what was nice, what was odd. What should be changed and how. Are you missing a feature or would like to try something special? Think about OSM go as a sandbox. Make a draft and I may implement it. Do you like a feature for your project? I would love to help to include it.


`exit_to` --> `destination` in Canada

Posted by mvexel on 24 October 2016 in English (English)

We had a discussion about retiring the use of exit_to in favor of destination for motorway / trunk exit tagging in the US a while ago. Since then, a shift has happened and a majority of exits is now mapped with destination instead of exit_to. This is great for navigation applications that rely on detailed signpost information, such as OsmAnd, and Scout.

With the situation in the U.S. so much improved, a next obvious target for mapping is Canada :) The situation there has been improved already by the community, but also by organized mapping by Mapbox and Telenav. Still, about 1200 exits remain that are tagged with the 'old' scheme. With the help of my colleagues at Telenav we put these in a MapRoulette challenge.


Because both OpenStreetView and Mapillary have good coverage in Canada, I think we should be able to update most of these exits to use the new scheme. Let's give this a go!

Imagery offset database in JOSM

Posted by nammala on 24 October 2016 in English (English)

Satellite imagery is one of our common source of data for mapping, however, not all imagery is exactly aligned to real world features. Every mapper should be aware of this and should consider adjusting imagery from aggregated GPS tracks or from features which we know have correct location.

Adjusting imagery offset

The usual approach is to align the imagery to GPS traces as best as possible using the Adjust imagery offset tool before making any edit. screen shot 2016-10-20 at 11 53 08 am

You can also save the defined offset as a bookmark so you can access them later on, for specific places. krishna

These offsets are stored in your local machine and only you can access them.

Using the Imagery Offset Database

The Imagery Offset Database allows a mapper not only to store imagery offsets but also to share them with the community. This crowdsourced approach for managing imagery offset is a great way to make sure that data derived from imagery have a consistent offset adjustment. This database can be accessed through a JOSM plugin.

Here is the wiki page for Imagery Offset Database and step by step tutorial with illustrations to install and use it in JOSM.

Aligning the imagery using aggregated GPS traces

  • In JOSM, load the imagery layer you wish to align (for example, Mapbox or Bing).
  • Load the Strava heat map or OpenStreetMap Traces layer.
  • Make sure the satellite or aerial imagery aligns as best as possible with aggregated GPS sources. how_to_offset3

  • To verify the alignment check the offset at a nearby area with a very high density of GPS data and wide roads. screen shot 2016-10-19 at 4 34 48 pm

Store the imagery offset

To record the offset for sharing with others and later use Imagery > Store Imagery Offset. Make sure the offset imagery is on top of other imagery or you would get a warning message. how_to_store

Using the stored offsets

To use the offsets stored in the database, download the area in JOSM and place the imagery on top and click on Imagery Offset DB icon to show the offsets stored in that area and select the best suitable offset corresponding to aggregate GPS traces. 222

Hope this database is useful for the community. Please do comment on this diary if you have any suggestions on storing and sharing the imagery offsets while mapping at different regions.

An Obsession with Stone Guardians

Posted by alexkemp on 24 October 2016 in English (English)

For those that do not already realise: I appear to be as obsessed with the stone creatures that Nottingham householders use to guard their homes as they are. Here is the latest one from Robinson Road, Porchester Gardens:—

Robinson Road stone guardian

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

Property worth a Billion £ GBP in Porchester Gardens

Posted by alexkemp on 23 October 2016 in English (English)

Current values for Porchester Gardens' houses seem to be somewhere north of £250,000 GBP each (5-bedroom detached houses are common on those slopes). With more than 800 properties in that neighbourhood, the total value is climbing rapidly towards the £billion GBP mark.

Of course, there's always someone that will let the side down...

a billion £ BGP in Porchester Gardens

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

Mysterious Markers Solved?

Posted by alexkemp on 22 October 2016 in English (English)

The latest survey of Porchester Gardens — just another couple of days surveying before it should be completed — has unearthed more of these lead markers and, possibly, has answered what they are. Here are two pictures from today's trip [1] [2]:

Kent Road 1 Kent Road 2

The second picture is, I think, the key to unlock this: they are more-ancient versions of the traditional grave-stone wall-plates used to indicate the presence of Fire Hydrants or Sluice Valves (sewage safety feature). So, the prize goes to EdLoach (commentator in Mysterious Marker #2).

Do we have any agreed method of mapping these markers?

This is the only Fire Hydrant marker that I've found so far in Porchester Gardens. Which is a little worrying.

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

Missing street names in Sardinia

Posted by dan980 on 22 October 2016 in English (English)

I'm currently updating Sardinia street names, using open data (IODL) from Regione Sardegna.

The best data source is the Geo Topographic Database ( . It covers 125 towns out of 377. The data is pretty accurate.

As a secondary data source I'm using DBT Elemento stradale ( It covers all the towns, but is older and many street names are missing, including main street names (e.g. they are called "Strada Provinciale 12" instead of "Via Roma").

I'm updating the names of existing OSM highways. For missing roads I'm using Mapbox Satellite first.

Access restriction data architecture

Posted by BushmanK on 22 October 2016 in English (English)

Currently, we have acceptable (but not ideal) tagging scheme for access restrictions. I'm talking about access=* key and its values. Here, I want to tell something about an application of this scheme in terms of topology, data interpretation, and data architecture.

OSM documentation says that it may be used on nodes, ways, closed ways (use on relations is unspecified, but it's not prohibited). And many people take that literally. Let's review some cases.

access=* is often assigned to a node, representing a barrier. Many mappers have an idea that it is way easier to add this tag to a gate, liftgate or another kind of barrier to indicate that access restriction starts here. In such cases, adding access=* to a highway=* is often omitted. A common argument for omitting it is that usually, navigation software starts the route planning from a point, which is publicly accessible. Then, analyzing the road network, it should avoid crossing those points with access=* restriction, if possible, just like it does with user-defined avoidance marks.

But there is a problem with this method. Having a road, divided into two parts by a node with access=* tag, it is impossible to tell, to which half this restriction is applied. This problem has only heuristical solutions, involving extensive analysis of road network. For example, it will be a nice educated guess to say that restricted portion is often a dead-end comprised of lower rank roads, while unrestricted portion likely has a connection with higher rank roads. But this kind of analysis is a problem with no definite depth, and it still doesn't give you 100% accurate result, which is unacceptable.

That argument about a route always starting from a publicly accessible point, is obviously false. There are enough cases when you have to calculate a route from a private property or limited access property. And the only universal way to deal with that is to disregard restrictions completely if no unrestricted route is possible. This solution is widely used, but it means devaluation of information about restrictions in the OSM database. Another known approach is to always avoid passing through the restricted portions of a road network by counting restriction points, but again, in a case of node-based restriction, it fails (requires a fallback to ignoring all restrictions) if both start and finish points are behind the restriction.

Applying access=* to a road itself eliminates any topological ambiguity since there is no question, to which part of a road restriction is applied. It is also clear if a route starts from or/and ends at a restricted portion. Therefore, no fallback is required.

Another option is to apply restrictions to a boundary, such as a fence or a land parcel, where a restriction is in effect. It helps to avoid tagging every road. However, it requires certain pre-processing to make data actually usable. Information about restrictions should be normalized by applying it to roads within a boundary using a spatial query (just like in the case of simplified address tagging, when addr:city is omitted on buildings, but can be easily propagated from a city boundary). To make it right, two additional operations should be performed: splitting roads at an intersection with a boundary, obtaining all members of a boundary contour. The latter one could be tricky if processing is performed offline.

So, it could be a drawback, but it doesn't create any problems with an indefinite depth.

The purpose of this diary entry is to explain how access restrictions work in case of being applied to every type of geometry and to demonstrate that existing node-based restrictions can not be reliably used.

Wikipedia and OSM collaboration

Posted by naveenpf on 21 October 2016 in English (English)

This something which we have been talking for years ;). Feels so happy that it is ready now.

Maps can be displayed in Wikipedia from OSM relation. Just done it for NH1

Wikipedia ---> Wikidata ---> OSM

How often OSM updates Wikidata id with Wikipedia tag ?

Cemeteries in Texas MapRoulette Challenge now powered by Texas Imagery Service

Posted by mvexel on 20 October 2016 in English (English)

Important note: The imagery I use as an example below is different in source from the imagery used for the MapRoulette imagery. The example below shows imagery that was commissioned by Texas itself, and is available in the public domain. The imagery in the MapRoulette challenge is licensed from Google by Texas and made available to MapRoulette specifically. So I can't say positively that it's OK to add this imagery to JOSM or iD, and removed specific instructions to do so.

Have you tried the Texas Cemetery challenge in MapRoulette? If you have not heard about it yet, I posted about it on my diary a few weeks ago. The short version: the friendly folks at TxDOT supplied me with a database of their known cemetery locations, we matched them with existing OSM, and if there was no match, we ask you to map it :)

If you tried it, you may have found though that it can be a bit frustrating :( Bing and Mapbox aerial imagery is often just not detailed enough to see if there is a cemetery or not in the location indicated. I discussed this problem with the friendly folks over at TxDOT, who are very excited about getting more data into OSM. They told me about some of the high resolution imagery that is available to the public through TNRIS, the Texas Natural Resources Information System. Here is an example of some of the amazing data they have:


If you compare that with Bing, it means the difference between seeing a vague blur or seeing the presence of a cemetery very clearly! Super exciting stuff. So we set out to create a TMS endpoint that we plugged into MapRoulette. See the difference!


Go give it another try! Thank you and thanks TxDOT!

Updated Contributor Statistics

Posted by SimonPoole on 20 October 2016 in English (English)

As at the begin of every new quarter since a couple of years, I've updated the Contributor Statistics on our wiki.

Naturally the most noticeable thing is the large jump in new users and active users starting in April 2016, which is naturally mainly due to new incoming edits from users. This is, on first principles, naturally not a bad thing, and annoyances due to bad edits aside, exposing more people to OSM is good.

What I have however noted in discussion is that the impact of the growth of the raw number of contributors is massively overestimated. For example the number of edits (not changesets) per month is essentially unchanged:

Which is not a surprise given that a maximum 0.18% of the edits per month in 2016 to date have been made with even though at least 1/4 of the active users used the app in the relevant periods. A preliminary comparison with editors that started off with iD show that over the same period the total number of edits per contributor using is smaller too.

There may be some longer term gains that we can't see yet, at least anecdotally I've seen one user do an initial edit and then switch to iD, but the numbers indicate that right now that is the absolute exception.

[Update] Small clarification: the 0.18% number includes all edits not just new contributors.

FacilMap 2 has been released

Posted by Candid Dauth on 20 October 2016 in English (English)

A new version of FacilMap has been released.

Everything has been rewritten from scratch. FacilMap is now based on Leaflet, AngularJS and Bootstrap.

FacilMap is an online map that aims to bring together many useful functions in a usable and pretty way onto an open-source map based on OpenStreetMap.

  • Different map styles: OpenMapSurfer, Mapnik, OpenCycleMap, Hike & Bike map, Public Transportation map, Hillshading overlay
  • Find places and calculate routes. Routes are fully draggable.
  • Show GPX/KML/OSM/GeoJSON files on the map (use Tools → Import File, type a URL into the search field, or simply drag and drop a file onto the map)
  • Show additional information about places (for example opening hours or a link to the website). Press the map for 1 second somewhere to show information about what is there. (Uses Nominatim.)
  • Zoom to the location of your device and follow it.
  • New: Create custom collaborative maps on Markers, lines, routes and even GPX/KML/OSM/GeoJSON files can be added to these maps by everyone who has the link to the editable version of the map (every map has a read-only and a read-write URL), and changes are displayed live to everyone who is looking at the map at the same time. Advanced features include the definition of custom marker/line types with custom form fields and styles and the automatic generation of a map key.
  • Can be easily run on your server or embedded into your website (see below).

The number of the month: 74.9 percent

Posted by drolbr on 20 October 2016 in English (English)

The most important news is that version 0.7.53 is now live on the and server. The Rambler server will follow in the next days.

I will give details on this further below. Also below I will explain how an incident with Pokemon Go shaked my mindset about quota policies.

Before this I will present the number of the month: 74.9 percent. From 74.9 percent of the total IPv4 /24 subnets of the entire world I have observed requests in the logfiles. Amongst some random IP block owners from the logfile: General Motors, Ford, Toyota, Daimler, BMW, Volkswagen. Media Outlets: New York Times, Guardian, Der Spiegel. Further starring: SNCF, Deutsche Bahn, SBB, numerous universities and even ESRI. Of course also long lists of telephone carriers. Remember that Overpass API is a quite deeply buried and highly technical service. It is almost sure that the popularity for the combined tile servers is even higher. This matches very good with the observation that half of the public administration in Germany is figuring out how to get OpenStreetMap in their workflow.

Punchline: OpenStreetMap is by no means small. It is the de-facto standard for general purpose geodata. And if there are limits to the growth of OpenStreetMap in sight, then these are most likley the size of mankind.

This does not mean that the majority of mankind is using OpenStreetMap. Please do not forget that you cannot eat geodata. Or substitute drugs. Geodata is in important field, but not the core of the world or the internet. The statistics from above say that whoever is involved in geodata is almost surely aware of OpenStreetMap.

Hence "irrelevant" is an adjective quite entirely unrelated to OpenStreetMap. Blog posts stating otherwise are simply wrong. This need not be a willful misinformation, but it may be an observation from a very unusal environment somewhere in the last 25.1 percent of the IPv4 space. Hence there is no need to have some obscure and complicated extra documents called "CoC" or so just to please unknown people that might not exist at all. Let aside that there is few to no precedence that extra bureaucracy pleases people.

But back to Overpass API. During the weekend around October 1st I have seen a spike in load. Such a spike is most of the time some developer trying to offload undue amounts of requests on the Overpass API. In this case it turns out that the only client responsible for a load spike is ([] - due to the highly technical nature of the tool this is more than unlikely.

It has taken some days until the search engines have delivered the evidence what was going on: has got credits from the remaining Pokemon Go community. Testing against that hypothesis, I found that people have accessed from 30'000 different IP adresses per each day of the weekend on Overpass API - roughly twice the normal. However, there is plenty of credit for OpenStreetMap. From the logs I can observe that a lot of users come from developing countries. And from my personal environment I know that more than half of Pokemon-Go-players are female. Actually I would call this as exactly what we like to achieve with outreach. Hence, neither blocking these users constituting the spike nor blocking altogether would be an option that makes sense.

So a second result of this weekend is that I should ask rather soon for more server capacity. The improvements by Mmd and me may help. But a second server at some point in 2017 would probably help to attract people. Maybe even people that do not yet have a relation to geodata.

Version 0.7.53 excels rather at having fewer bugs than at having new features. There are nonetheless some improvements: * [!key] can be used as shortcut for [key!~"."] * the user statement accepts multiple users as a comma separated list

Version 0.7.54 is hopefully ready at the end of the year. I have already started to develop some features. Others have been sketched in my SotM talk (video tba). So please stay tuned. And in the meantime, please spread the message that OpenStreetMap is already the standard choice for general purpose geodata.

OSM Bangladesh Pioneer Ahasanul Hoque's birthday

Posted by Ataur Rahman Shaheen on 19 October 2016 in English (English)

Ahasanul Hoque, a magical personality person & Pioneer of OpenStreetMap Bangladesh. He dreamed & work hard for his country and now OpenStreetMap successfully running in Bangladesh. 19 october was his birthday. YouthMappers, DhakaCollege president Sawan Shariar and vice president Atikur Rahman told me make a birthday wishing poster. I was so much busy those days. But I made it. At the same time one idea came to my head that I will made a video about his life. For that I am check out Ahasanul Hoque's facebook ID and website, collect some photo and information and made a video. In the video I’m trying to made a good combination of those photo and information that will remember him many good memories of his life. I hope that he like the video. Video link is

Older Entries | Newer Entries