OpenStreetMap logo OpenStreetMap

Post When Comment
Berlin between Mollstraße and Karl-Marx-Allee

Just want to say it's appreciated to see posts in English. The Germans are fairly active on the OSM diaries, and although all those posts sound interesting, my German is so far away (~4 years) I can hardly understand anything.

Just a suggestion: maybe adding more direct links, either to a closer zoom, or to related nodes and ways (e.g. Lichtenberger Straße), because at zoom 14, locating the discussed area in a busy place like Berlin can be a pain.

Irritated by right of way issues

Yes, but this is not the UK (It's technically a parc-école, "playground park": a playground with enshrined public acces as a parc), and the point is moot anyway.

GeoBase import -notice update

It's not so much that talk-ca in particular is hard to keep up with. It's just that overall I don't feel I have much to contribute or gain from participating to mailing lists, and keeping up with the mails (as opposed to the discussions) is too much effort for me AFA I'm concerned.

GeoBase import -notice update

For what it's worth, I've been following this on the wiki and, occasionally, by looking at the list (though I don't subscribe to it). Haven't seen much to comment on, though I am indeed thrilled about the whole prospect.

You shall map the longest street in the village with … a herring!

OOOPS That should have been "access=destination"...

You shall map the longest street in the village with … a herring!

I'm fairly sure "local traffic only" is "access=designation" (Dangit, an access tags covering all road vehicles would be a good idea >_<)

landuse=grass tag

IMHO, the Serengeti would OBVIOUSLY be tagged with a form or another of natural= (My instinct would go for natural=prairie for wet/temperate ones and natural=savanna for drier ones, or simply natural=grassland). Most tags have significant British skews, hence why the closest values given are natural=fell/heath/scrub. landuse= is for HUMAN use of the land, hence why landuse=forest and natural=wood are quite distinct.

Maps for limited groups of people

The normal method would probably be a form of the access tag

Kommetjie, Cape Town, South Africa

I see two "Kommetjie" labels, is that normal?

Local Neighborhood labels

*squint*

I see two "Willow Glen". That normal?

Cycle map shortcoming

For some reason I've tagged that as network=rcn, ref=*. I know I had a reason but I can't find it again.

I don't think the many designated lanes (not all of which are even actually marked) in Quebec city can take one o those tags, though.

Fifth post - undergraduate geography dissertation

Although a gender bias is troublesome in any project where point of view may strongly influence content (the gender/geographical bias does, for example, very noticeably the way some content is presented in Wikipedia), this element has, as far as I cold tell, fairly little impact on the way content is added/selected for OSM.

osmarender and under water tunnel

Name rendering is on a strict way-by-way basis (hence why if you split a way because its segments have different characteristics, you get twice the name). The only way to prevent a name from being displayed is to not put one at all.

More street name updates

The new barriers proposal is passing with flying colors, so you might as well change it to barrier=gate already.

As for names, there is a proposal related to that.

Mapnik render modifications

Having had a better look, I think they are nice. They form a set that is, overall, better coordinated and less obnoxious. I was rather unhappy with either renderer's bus stops, but Mapnik's new ones are neat.

It seem new criteria are now applied for deciding which zoom level text matching zones and small POIs appear. I have three hospital in the same window, and the names are visible at different zoom levels.

Mapnik render modifications

I'm neutral for most of those I've noticed, though I'm not a fan of the new parking icon.

Why bother creating relations for Routes ?

I do believe there are external software that can take it into account. Personally, I'd use the "ref" tags on the segments themselves (cf. as is done with numbered highways) rather than an unwieldy relation (after all, IMHO the points is that there is a cycleway there, not that it is part of a specific network).

But then I'm working with bus routes only so far, and I don't do long-distance cycling, so I'm not clear what's the usefulness of having designated cycleways routed.

Bus route

I came up with an ad hoc system using the backward/forward tag already extant that is, IMHO both more functional and more intuitive. As far as I'm concerned, a bus route system that cannot handle loop/splitting route is virtually useless and should probably be rethought from scratches. (If I can't enter any route that goes along a double carriageway because of the formed loop, I'm virtually unable to enter ANY route in Quebec City, what would be the point??)

Relations going away ?

I was assuming he had to reconstruct it.

Potlatch splitting

Well, it does seem awfully frequent that, after a split, multiple overlapping ways mysteriously happen, and after messing around they're fix, I might find some ways have vanished entirely. And a connection error message is not always involved.