After I got some experience with hosting OpenStreetMap tiles during the revival of Openptmap, I wanted to dig deeper into the topic in order to firstly migrate Openptmap to the new flex output so that it can receive incremental updates, and secondly to be able to host some additional overlays.

I found that the only widely used way to host tiles is overv/openstreetmap-tile-server. On the first look, it is really easy to use. It takes care of importing and updating the OSM database and of rendering and serving the tiles. On the second look however, there are some major challenges and problems with it:

… See full entry

OSM History Viewer and OSM Route Manager are two ancient tools that help visualising and analysing changesets and route relations. In particular, they provide the following features: * Show the geographic and tag changes that a specific changeset has caused * Render a route relation (with support for nested relations), detect gaps and inconsistencies, and export the route as GPX * Analyze the history of relation members and show who last edited (and is thus to blame for) which section of the relation.

I have not maintained these services in many years and they frequently crashed or got overloaded. The user experience was also far from great.

I have decided to rewrite the logic of these tools and integrate it into FacilMap. While the don’t particularly fit the use case of FacilMap, the infrastructure (in particularly the UI elements) is there, making it convenient to integrate it there.

So far I have implemented the first functionality, changeset analysis. You can analyze a changeset by typing changeset <id> (for example changeset 6798641) into the search field, or by calling the URL https://facilmap.org/#q=changeset%20<id> (for example https://facilmap.org/#q=changeset%206798641) directly. As opposed to the legacy OSM History Viewer, the analysis and API requests are now entirely performed on the client side.

I will implement the other two features soon. Once done, the old services will be shut down and a redirect will be put in place.

Feel free to report any problems that you come across by writing to me or by creating an issue.

… See full entry

I really missed Openptmap ever since the service stopped working a few years ago. It was an important feature of FacilMap that I had used frequently in my daily life. This is why I have decided to invest in a bigger server to be able to render and host the tiles myself.

I have set up a tile server with the original Openptmap styles on https://pt.facilmap.org/. You can browse the tiles through FacilMap.

For now, tiles are generated when first requested, so rendering the map will be very slow when a region is first accessed. Also, there are no automatic updates of the map yet, so for now the state of the map will be frozen in time. When I find the time, I want to bring the setup up to date to enable automatic updates. If you have the skills and want to contribute, what would be needed would be to rewrite the filter and style into an osm2pgsql flex output Lua script.

If you find this service useful, a financial contribution would be greatly appreciated.

FacilMap 3 is a complete rewrite of FacilMap, with a focus on an improved, more stable and smartphone-friendly UI.

FacilMap is a privacy-friendly, open-source versatile online map that combines different services based on OpenStreetMap and makes it easy to find places, plan routes and create custom maps full of markers, lines and routes. Features include:

• Different map styles for roads, topography, cycling, hiking, public transportation, water navigation, …
• Search for places and show their information (website, opening hours, …)
• Calculate routes and adjust them by dragging. An elevation profile can be shown.
• Smartphone-friendly interface.
• Create and share custom maps with markers, lines and routes on them.
• Open GPX/KML/OSM/GeoJSON files and save them on a custom map.
• Define custom styles of markers, lines and routes and generate a legend automatically.
• Define custom form fields for the details of markers, lines and routes.
• API to embed custom maps into a website and to modify them programmatically.
• Extensive documentation.

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 https://facilmap.org/myMapName. 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).

There have been some API changes in OSM some months ago, which caused OSM History Viewer to fail with NumberFormatExceptions on all changesets where something was deleted. This basically meant that History Viewer had been unusable for several months now. The issue is now fixed.

I have finally had the time to build in a timeout for OSM Route Manager and History Viewer.

Previously, the only limit was the memory of the Java process, which caused some requests to take really really long. The queue got very long and the service became unusable. (And before that, there hadn’t even been a memory limit, the service would just dump cached items from the memory and re-fetch them from the API when needed.)

Now, I have set the timeout to 10 minutes. I know that this might not be enough for the “Relation blame” of medium to big relations, but at least it keeps the service usable.

Since the introduction of the queue in Route Manager and History Viewer, there have been several down-times where the queue became very very long without anything being processed. The reason why nothing was processed was that someone tried to use the “Relation Blame” on very big relations, such as osm.org/browse/relation/107796. I have therefore disabled the Relation Blame function for now.

The reason why the queue got so long (sometimes several thousand requests) is probably caused by bots. Probably beacuse of the links that the Wiki automatically creates to the two tools. I suppose I will have to add a robots.txt, and if that does not help, a Captcha.

With FacilMap (facilmap.org, Wiki), I try to create a map that has all the features of Google Maps but uses OpenStreetMap layers.

For a long time, I’ve wanted to implement something similar to the relatively new Google Maps feature where you can click on POIs (such as companies or restaurants) and a popup displaying details opens.

Now I’ve come accross OpenLinkMap (olm.openstreetmap.de, Wiki), which seems to do exactly this. So I’ve created an OpenLayers layer for it and added it to the Beta version of FacilMap available on beta.facilmap.org. On zoom levels >= 13, you’ll see these transparent dark-blue circles around some POIs. Click on them and a popup appears with some information about the POI.

At the moment, OpenLinkMap seems to only contain POIs that have either a telephone number, a website or a Wikipedia article. Hopefully, in the future other POIs will be included as well so that one can see their address and opening hours.

If you want to include the OpenLinkMap layer into your OpenLayers map, include the FacilMap API JavaScript into your website:
<script type="text/javascript" src="http://beta.facilmap.org/api/facilmap.js"></script>
(Once the OpenLinkMap layer is considered stable, it will be added to the stable FacilMap API on http://api.facilmap.org/facilmap.js.)

Then add the layer to your map using the following code:
map.addLayer(new FacilMap.Layer.Markers.OpenLinkMap("OpenLinkMap"));

This feature is documented on osm.wiki/FacilMap/API/POIs.

OSM Route Manager and History Viewer are now hosted on the FOSSGIS development server under the new URLs http://osmrm.openstreetmap.de/ and http://osmhv.openstreetmap.de/. I will continue to use the old URL (http://osm.cdauth.eu/route-manager/ and http://osm.cdauth.eu/history-viewer/ ), which now redirect to the new locations.

I have implemented some new caching and queueing mechanism so that only one request is processed at each time (to avoid a too extensive use of resources and API calls). Hopefully, the service will finally run acceptably stably due to these changes.

Dominik Mahrer (http://www.teddy.ch/) has offered me to host OSM Route Manager and History Viewer, as I was experiencing a lack of resources that forced me to take them offline. Many thanks to him!

The tools are available on the old URLs (http://osm.cdauth.eu/route-manager/ and http://osm.cdauth.eu/history-viewer/‌ ). Some things don’t work quite right yet (such as the nasty Google Maps API key warning appearing all the time), but at least the tools are usable again.

I am currently working on improving the speed a little bit by using better caching, hopefully it will be as usable as it used to be some day again.

cdauth’s map and its API are now called FacilMap and is available on http://facilmap.org/. I will try to keep all old URLs alive. People who want to make use of new features have to migrate their code following the guide on osm.wiki/FacilMap/API/Migration_guide_from_cdauth%E2%80%99s_map.

The OpenStreetBugs layer is now hosted on http://api.facilmap.org/osblayer/ instead of http://osm.cdauth.eu/openstreetbugs/.

ajax-proxy now runs on http://api.facilmap.org/ajax-proxy/ instead of http://osm.cdauth.eu/ajax-proxy/.

The new OpenStreetBugs JavaScript client (osm.wiki/OpenStreetBugs/New_Client) is now being developed in a repository independent from cdauth’s map. The reason for this is that I can manage committers separately. I am planning to put the translations into TranslateWiki and hope to get automatic updates into the Git repository.

Everyone using the JavaScript library from http://osm.cdauth.de/map/openstreetbugs.js or http://osm.cdauth.eu/map/openstreetbugs.js should from now on use the new location http://osm.cdauth.eu/openstreetbugs/openstreetbugs.js.

The old locations will redirect to the new one for some time.

The source code is now developed on http://gitorious.org/cdauths-map/openstreetbugs.

OSM Route Manager and History Viewer have been down for about three months now. As I have written earlier, the reason for me to disable them was thir massive memory consumption. I have just put them online again, although they don’t work well yet.

Originally, Route Manager was entirely written in PHP. As splitting large relations into segments is a CPU-intensive operation, I rewrote the logic in Java but kept the PHP web pages. The PHP page would start the Route Manager Java executable for each request and after its completion read out the result from an SQLite database. I adapted the same concept for OSM History Viewer.

The problem with this approach was the massive memory consumption that had two reasons:
1. There was no limit on concurrent requests, so 10 concurrent route analysations would have caused 10 Java Virtual Machines to run, and each of them takes a lot of memory by itself.
2. To analyse a large relation or changeset, all of its members had to be loaded into memory.

I solved these problems more or less in the following way:
1. I rewrote the PHP pages in JSP so that both applications and all simultaneous requests would run in one JVM.
2. If too many objects are in the memory, some of them are dumped into a Postgres database (which increases the CPU usage and thus the analysation time).

The server I run the two applications on has 512 MB RAM and a very slow SAN hard disk connection (with 1–2 MB/s), so swapping is very slow. With the old PHP versions of the applications, my server would completely hang up when too many JVMs were running because of the lot of swapping to do. This was unacceptable because I also use the server for e-mails. With the new JSP versions, the memory usage of the applications is limited. I have not yet found a way to find out the actual memory consumption of a process under Linux, but the VIRT column currently shows 368 MB and the RES column 186 MB for the servlet container, so the actual usage must be somewhere in between.

… See full entry

The routing support of cdauth’s map, my OpenLayers map with additional features (routing beta preview on http://osm.cdauth.eu/map-routing/), has made some progress. I have switched the routing provider from YOURS to CloudMade, which is almost comparable to Google Maps in speed (the only problem seems to be that it cannot route over ferries yet).

I have fixed some bugs considering the drag and drop support. You can move the start and destination markers on the map as well as drag parts of the route to change its course (creating “via” points, remove them again by double-clicking them).

I have tested in the newest versions of Firefox, Opera and Konqueror. Some bugs are yet to be fixed:
* Removing “via” points by double-click does not work in Konqueror
* Very rarely, strange things happen after dragging “via” points: hundreds of JavaScript errors appear or the map itself is not draggable anymore.
* The different versions of Internet Explorer need to be tested (I suspect that it works in none of them properly.)
* Test in Opera 10.0.

As some of you might have noticed, Route Manager and History Viewer have been down for a while. I had to take them down because with the current implementation -- a PHP page starting a new Java Virtual Machine on each request -- my server would hang up at too many concurrent requests because of too little memory, which is unacceptable because I am expecting some very important mails on that server. I am on a journey right now with very limited Internet access and unfortunately did not quite manage to finish the new version, completely Java-based, before leaving home. I will be back not earlier than beginning or middle of July. Maybe someone manages to run the applications on their server until then? Sorry for the inconvenience and greetings from Greece, Candid

I was a bit upset about the fact that everytime you wanted to write an AJAX application using the OSM API or the Namefinder, you had to set up a local proxy on your server because of the Same Origin Policy.

Thus I have written an AJAX proxy that circumvents the Same Origin Policy by using HTML

I have added experimental routing support to my map. I am using the YOURS API to calculate the routes and try to provide an easy user interface that is similar to Google’s. You can drag and drop the route start and end point and also drag parts of the route to create Via points. It works pretty well (only tested on Firefox so far), but a few bugs still occurr some time.

You can try it out on http://osm.cdauth.de/map-routing/. Please be aware that this is a temporary URL, normally you can access my map on http://osm.cdauth.de/map/.

If you want to try this in your own map, include the JavaScript file http://osm.cdauth.de/map-routing/prototypes.js (remember: this is a temporary URL) and use the following code:

var layerRouting = new OpenLayers.Layer.cdauth.XML.Routing("Routing");
map.addLayer(layerRouting);
layerRouting.setType(OpenLayers.Layer.cdauth.XML.Routing.Type.FASTEST);
layerRouting.setMedium(OpenLayers.Layer.cdauth.XML.Routing.Medium.CAR);
layerRouting.setFrom(new OpenLayers.LonLat(5.963946, 52.215676));
layerRouting.setTo(new OpenLayers.LonLat(6.1799, 52.2573));

The drag’n’drop will work automatically.

Nominatim has a nice feature to provide an icon URL for search results, for example a shop icon if you search for supermarkets. I use these icons now for the search result markers on my map (http://osm.cdauth.de/map/). Although I don’t know if I will not restore the old marker icons, because these new icons aren’t very prominent on the map.

I have simplified the syntax to add Live Permalinks to an OpenLayers map with my cdauth’s map API. These Permalinks are stored in the part after the # in your browser’s address bar, so when you reload the page, everything will be exactly the same and you can easily send the link to your friends. You can then also use your browser history, so when you hit the “Back” button in your browser, the previous map view will be loaded. Try it out on http://osm.cdauth.de/map/.

To add the functionality to your map, include http://osm.cdauth.de/map/prototypes.js into your web page and replace the constructor “OpenLayers.Map” with “OpenLayers.Map.cdauth”. Then add an OpenLayers.Control.cdauth.URLHashHandler object to your map either by putting it into your controls array or by using the following code:
var hashHandler = OpenLayers.Control.cdauth.URLHashHandler();
map.addControl(hashHandler);
hashHandler.activate();

This will keep the location hash part in sync with the current map view, so the location will be updated when the map view is changed and the map view is updated when the user changes the location hash part manually (or opens a Permalink someone sent him).

Read more about my API on osm.wiki/Cdauth’s_map/API.