Some database lag again …

Update: everything is back to normal again, all caught up

Due to database maintenance work regular diff imports to the main OSM database are currently disabled, the current database state is that of July 5th noon (CEST).

The WayMarkedTrails route database is still getting its regular updates, but is currently falling behind a little bit (currently around 7-8 hours) due to the higher disk load during maintenance.

Rendering of maps is still possible, just don’t expect map data changed after Jul 5th noon to be taken into account for the next few days …


A Quest for Stylesheets

I’ve been collecting various map rendering styles for my MyOSMatic instance for quite a while now, integrating whatever I found useful and not too hard to integrate.

I’d now like to put a bit more systematic effort into this, and for this I need some “swarm intelligence” help.

So if you know of a map rendering style out there that you’d like to see supported please let me know.


  • The style files must be under a “sufficiently open” license
  • It needs to use Mapnik XML or CartoCSS as implementation language
  • … sorry, no MapCSS, unless someone can come up with a good converter to MapnikXML for that
  • It needs to be sufficiently distinct from the default CartoOSM style and other already supported styles so that it adds real value
  • It must be based on the standard osm2pgsql database style. If it adds some fields on top of that it’s ok, this can be solved by providing views that make use of the hstore-all tags column. But setting up a completely different database schema is not possible due to space and processing time restrictions.

If you know of any good map styles that match the criteria above please let me know in a comment on this post, or even better: create a feature request issue on Github

Improved GPX bounding box handling

I had added the option to upload a GPX track in the MapOSMatic instance a little while ago, but using that was a bit tricky. This has just been improved a little big.

So far you had to manually select the map area to render before adding a GPX track which could be a bit tricky.

Now it is possible to select one of three options:

  • keep original bounding box (default, as before)
  • extend (merge) the bounding box to fully contain the GPX track, too
  • replace the selected bounding box with that of the GPX track completely