Archive for the ‘Openstreetmap’ Category

Osmarender rules changed to render forest parcel names

Sunday, May 9th, 2010
Forest parcel name rendered in osmarender, zoom 17

Forest parcel name rendered in osmarender, zoom 17

At crossings of tracks in the woods, you often can find up to four name plates displaying the names of the adjacent wooden parcels. I usually placed a node tagged as place=locality and added the names. Of course this leads to a situation where the names will overlap each other, and after collecting some of those plates, it was desirable to draw the parcels as areas with the name rendered at the center, not as individual nodes at the vertices. I currently add a polygon tagged as landuse=forest.

While Mapnik renders the names of natural and landuse features in zoom levels 14 through 17, Osmarender only rendered them visibly at zoom level 17. It rendered natural names at zoom levels 16 and 15, but subsequently the caption was hidden by the rather huge surrounding wood polygon. landuse was missing in those levels.

I’ve thus adjusted the render rules so the names of natural and landuse features also get displayed at zoom levels 16 and 15. I hope this won’t mess up the map in densely populated areas. If so, please drop me a line and I’ll change the additional k="landuse" v="*" to something like k="landuse" v="forest|wood".

As soon as the changes are slurped by the tiles@home clients, I’ll start to convert the locality-nodes to something like amenity=nameplate or similar to finally clean up the map.

Mapping Hiking Routes

Saturday, May 1st, 2010
Hikingmap Route

Hikingmap Route

While curing some cold, I mapped a hiking route to make it appear on the Hiking and Bridlemap.
(more…)

Traveling along the french-german border

Monday, April 26th, 2010
Lœwenstein Castle

Lœwenstein Castle

As the weather is fine at the moment (and my bike is broken again), it is hiking time. Slowly it becomes difficult to find unmapped terrain, as openstreetmap.org meanwhile does not only attract car drivers but also hikers and (mountain) bikers. In the region where I grew up a lot of medieval castles can be found, and I visited them all. Time to resurrect the hobby of my youth as long there are still trails missing in the woods.

(more…)

Loosing the tracks of a hiking trip #9869

Sunday, April 25th, 2010
Jester (openclipart.org, by Johnny Automatic, public domain)

Jester (openclipart.org, by Johnny Automatic, public domain)

It’s not the first time it happened, but I was surprised anyway. I was hiking along the french-german border. I only ran Mæp and Waypointcatcher. I didn’t use osm2go to save some battery power. Even without Waypointcatcher not running, Mæp caused the device to crash four times. This usually happens when the device’s interface is locked, so you just notice that the device does not respond as soon as you try to unlock it. The only thing that helps is to remove the battery and boot anew. As data roaming is about 7¢ per 10KB of data (sic), I could not use AGPS. Thus the device needs up to twenty minutes to get a GPS fix after a reboot.

Unfortunately Mæp drops the recorded track after such a forced reboot. But hey, no prob, I have the WBT-201 running as a backup.

(more…)

Mapping applications for the N900

Saturday, April 24th, 2010
Fern near Blumenstein Castle

Fern near Blumenstein Castle

The N810 is a great device and the perfect mapper’s companion, but the N900 is even better and a joy to use. Here are some applications I use on a regular basis:
(more…)

2nd Mapping Tour by Bike

Monday, April 19th, 2010
Anguis fragilis

Anguis fragilis

This weekend was an excellent one, providing very good weather conditions to do some mapping by bike. The Bienwald, a huge area of wood where I still seem to be the (almost) only mapper who collects data, still serves me well to combine three hobbies of mine – nature, riding my bike and mapping for openstreetmap.org.

I really love the smell of the pines during warm days in spring. You can see all kinds of animals – including crane flies, though. The Bienwaldmühle, including a traditional german restaurant, serves great food. The rest in their biergarten took too long, so the way back home included twilight – which was a good thing, because you can see even more animals (like foxes, roe deers etc.) which usually are not seen during daylight.

I collected a lot of missing ways, names of ways and names of the wooden parcels. Though it is the third year I’m mapping there, still a lot of details are missing.

I used the WBT-201 as an autonomous logger to track the whole trip. The N900 did a good job, but I left it alone until I crossed the rhine to save some battery power. This is necessary as one of my two batteries only lasts for about three hours – though I switched the device to offline mode. The two batteries have been sufficient for the whole trip, but I now know I will need a third one for whole-day-trips.

Waypointcatcher resurrected for Maemo 5

Monday, April 12th, 2010
Waypointcatcher on Maemo 5 (aka Fremantle)

Waypointcatcher on Maemo 5 (aka Fremantle)

As the location API has changed in Fremantle from libgpsbt to liblocation, the previously released version of waypointcatcher won’t do the job on the N900.

I’ve thus updated the python code, which despite its C&P nature just »works for me«. I’ll share the application on request, until I find the time to do the necessary cleanup and to offer a proper point and click installation link.

Its main purpose is to collect waypoints for openstreetmap, as Mapper does not record marks reliably ATM.

Battery Lifetime when mapping with the N900 #2

Thursday, April 8th, 2010

During my last trip, I avoided to use an audio player and osm2go on the N900. The only application running was Mapper (formerly known as Maemo Mapper). Again the big bug occured, requiring two reboots.

Nevertheless the battery only lasted for two and a half hours. This really is very poor. Maybe Mapper needs more CPU than on the N810. I’m curious whether I’ll get better results during the next trips or if the uptime will remain the same. In either case, I’m desperately wating for the second battery I purchased to arrive.

I logged the track both using the N900 and the WBT-201 (aka G-Rays 2 ). Surprisingly, the track of the N900′s built-in GPS receiver was more accurate as the one of the WBT.

Au Bord du Rhin

Thursday, April 8th, 2010
Quelques Guis

Quelques Guis

Aujourd’hui j’ai éte en Alsace, pour cartographier quelques chemins au bord du Rhin.

(more…)

Battery Lifetime when mapping with the N900

Tuesday, April 6th, 2010
Plane drawing curves on the sky

Plane drawing curves on the sky

Again I was mapping using the N900. I permanently had Mapper, osm2go, FM Radio (respectively an audio player) plus a text editor running. Additionally I took a couple of photos.

(more…)

Mapping Initiation of the N900

Friday, April 2nd, 2010
The Heilbach meanders the Bienwald

The Heilbach meanders the Bienwald

I grabbed the occasion of today’s excellent weather conditions for my first mapping tour with the N900. I used it for my continued effort to map the Heilbach for openstreetmap:

I left all the other gadgets I used until now (mp3 player, Canon camera, external bluetooth GPSr, N810) at home and only grabbed the N900 to check if it really can replace the previously used armada. To anticipate the result: yes it can. I’m quite impressed and really content with the device. It’s a great digital companion. You should read on, though, to learn more about some pitfalls and shortcomings to avoid frustration.

(more…)

OSM@Horizont OUTDOOR

Sunday, February 7th, 2010

Currently the »Horizont OUTDOOR« fair takes place at Messe Karlsruhe:

I’ll be at the OSM booth (which is 4.216, dm-arena, near the GPS-Village) tomorrow. Garmin maps on 2GB Micro-SD memory cards are available for sale at 10€ each (which basically is the cost of the hardware).

I hope I can share some photos tomorrow.

When it not is your (mapping) day

Sunday, January 24th, 2010
Frozen Tarn

Frozen Tarn

Every now and then, a mapping trip is not as successful as intended. And so was today’s. Here’s some C code describing my feelings :) :

Some code

Some code

(more…)

Paths and Tracks vs. Bridleways, Cycleways and Footways

Sunday, January 17th, 2010

My recent changes are more or less political. As always when it comes to presets, I will be accused to abuse my position as a software developer to influence the tagging done by mappers.

In the openstreetmap database, we have footway, cycleway and bridleway values for the highway tag for a very long time now. As they were not really sufficient to map trails in the woods, hills, or mountains, paths have been introduced back in 2007 to circumvent the limitations. During the introduction, it has been suggested that footways, cycleways and bridleways should be abandoned in favour of paths with some additional attributes. As many people objected, paths have been introduced and the other types are still “valid”.

This leads to the current situation where similar things are mapped differently. For example, a footway is tagged as

highway=footway

If bikes are allowed, a valid tagging scheme reads as

highway=footway
bicycle=yes

Unfortunately, this scheme does not really allow to map combined foot- and cycleways (as often found in germany). Thus some mappers use

highway=path
foot=designated
bicycle=designated

for such purposes.

As a consequence, we see

highway=path
foot=designated

as synonymous to

highway=footway

The three time-honoured tags still are very convenient to use, while the path tag combined with some additional tags is the more flexible one. I have no clear opinion on that matter, but I tend to sense that a single tagging scheme would be better when it comes to consumers (like renderers) of our data. If our editors were better and capable of hiding all the tagging stuff completely, I would clearly propose to abandon the legacy tags in favour of the path tag. But our editors aren’t, and mappers still must be aware of tags.

Besides the abovementioned tags, we also use

highway=track

sometimes accompanied by some surface or tracktype tags:

highway=track
tracktype=grade2
surface=gravel

This tag is for agricultural or silvicultural roads. Obviously the meaning of tracks, bridleways, cycleways, footways and the various flavours of paths is at least ambiguous. This sometimes leads to frustration of mappers.

Given the current tagging scheme, I do it this way:

  • If, and only if it is a dedicated cycleway, I use highway=cycleway (footway and bridleway respectively).
  • If it is a dedicated, combined foot- and cycleway, I use highway=path foot=designated bicycle=designated.
  • If a path is not used (or usable) by 4-wheeled vehicles like cars or tractors, it’s a path. I add widths, MTB or hiking scales to my likings.
  • Tracks are usually used by tractors. If so, it’s a track. I always add tracktype or surface tags, too.

That’s surely not a perfect solution, but lets me map most things i find accurately.

JOSM Presets updated

Sunday, January 17th, 2010
JOSM Logo

JOSM Logo

I rearranged the presets in JOSM and am prepared for the usual bashing :) .

Tracks and paths have been reunified into one menu entry only, so the convenience menu shortcuts to the various types of tracks and paths are past. OTOH, I have introduced dedicated menu entries for combined foot and cycleways:

JOSM presets - cleanup and additions

JOSM presets - cleanup and additions

The types have been included as popup menus into the dialogs. Besides tracktypes and hiking scales, I also included mountainbike scales, while more special tags for mountain bikers can be used by including an existing set of externally maintained presets:

JOSM - Path Preset

JOSM - Path Preset

Obviously, the dialogs are completely overcrowded. We will not be able to stuff any and all tags that will develop in the future into JOSM. Be prepared that I will do some major cleanup work some day.

External Presets in JOSM

Sunday, January 17th, 2010
JOSM Logo

JOSM Logo

JOSM provides the capability to include presets from external sources. It is the perfect mechanism for a group of mappers to maintain a specialized set of presets. This way, »Special Interest« mappers like skiers, mountain bikers or seamen can feed menu entries they need directly into JOSM without polluting the default menu space of JOSM.

Some examples are available via JOSM’s wiki pages. There’s also a page how to create and use such presets.

LinuxTag 2010 – Call for Papers

Sunday, January 17th, 2010

Due to some talks I held at the LinuxTag, I received an electronic mail regarding this year’s call for papers. They are explicitely looking for papers about Openstreetmap, but I won’t write one and have no clue whether anyone already offered one. If you are interested, better ask them before writing the paper to avoid duplicated work.

The State of the Snow

Sunday, January 17th, 2010
Hiking Trail in the Bienwald

Hiking Trail in the Bienwald

As Daisy had even reached the Upper Rhine Plain, we had some snow for a couple of days. I used the occasion for three nice hiking trips in the Bienwald, mapping grade 4 and 5 tracks, hiking paths and, last but not least, the stream Heilbach and some drains alimenting it:
(more…)

SRTM tiles available online

Saturday, January 9th, 2010

SRTM contours in Navit

A couple of days back, I converted the SRTM dataset into tiles containing OSM contour lines. Meanwhile the tiles are available online. This service is provided by the Stuttgart University of applied Sciences, thanks to the support of Dr. Franz-Josef Behr.

I hope the data is useful for some community work, e.g. tile rendering for slippy maps or rendering contour lines into viewports of mobile devices. If you create publicy available stuff from the data, please drop me a line.

Openstreetmap Data Types

Saturday, January 9th, 2010

osm_logo.png

The data of openstreetmap is stored in a relatively simple manner. Basically, we have three base datatypes:

  • Nodes are the most basic datatype and the only objects that actually contain geographical coordinates. A node may simply look like
    node id='12345' lat='48.9955' lon='8.3948'.
  • Ways are ambiguous. More or less, ways are just polygons, and can either describe a way or an area. Ways have no geoinformation itself, as they are relying on nodes:
    way id='23456' nd ref='12345' nd ref='12346'.
  • Relations have been introduced with API 0.5 and can be seen as data objects glueing together either nodes, ways, or both. Relations are used to model turn restrictions, routes, multipolygons and the like:
    relation id='34567' member type='node' ref='12345' role='' member type='way' ref='23456' role=''.
    The members of a relation can take a role to describe what they mean. In simple relations (like route releations) the role attribute often is left blank.

Simple plain text Tags are used to determine what kind of map feature a node, way or relation represents. A tag consists of a key-value-combination like amenity=bench, natural=water, highway=residential or route=ski. Mappers are invited to invent new tags whenever necessary. This freedom plays an important role concerning the success of the project.

Prior to API 0.5, we had Segments. A segment connected two nodes. First, tags have been applied directly to segments. Then, ways have been introduced which joined segments together. Since then, the tags have been applied to the ways instead of the segments. Segments caused some trouble (namely “unordered segments” for the old dogs) and have been abandoned during the introduction of API 0.5.

So nowadays we have nodes, ways, relations and tags. Easy, isn’t it? True for nodes, ways and tags. Not true for relations, though. Relations are difficult to create and edit, because they most often have no direct graphical representation in the editors. More or less they appear a bit flange-mounted on top of nodes and ways. Nevertheless they allow us to map things that otherwise would be difficult or impossible to model.