Bitte doch die Mapper, die mit nicht korrigierten Bing Bildern arbeiten, einfach mal freundlich darauf hinweisen. Sonst machen die das im naechsten Ort genauso, und da merkt es vielleicht keiner.

Es steht inzwischen auf allen Wiki-Seiten, aber ehe nicht in Potlatch und JOSM grosse Warnungsdialoge kommen, werden trotzdem viele nicht darauf achtem.

Sorry :(

Ich wäre ja stark für die Einordnung unter den key “man_made“.
Dort gibt es schon so schöne Sachen wie antenna, rig, pylon, wall, cable usw.
Wenn man nicht direkt cable benutzen will, könnte man attachment, fixation oder anchoring erfinden.

Gruss,
Chaos

Ich wäre ja stark für die Einordnung unter den key “man_made“.
Dort gibt es schon so schöne Sachen wie antenna, rig, pylon, wall, cable usw.
Wenn man nicht direkt cable benutzen will, könnte man attachment, fixation oder anchoring erfinden.

Gruss,
Chaos

Ich wäre ja stark für die Einordnung unter den key “man_made“.
Dort gibt es schon so schöne Sachen wie antenna, rig, pylon, wall, cable usw.
Wenn man nicht direkt cable benutzen will, könnte man attachment, fixation oder anchoring erfinden.

Gruss,
Chaos

I've contacted them and mentioned the missing attribution. I also thanked them for choosing OSM and described the mutual benefits we may achieve.

I've also documented the missing attribution and the contact in the wiki, so that hopefully they don't get spammed by angry osm users.

I haven't talked about the usage policy though. They have that openstreetmap layer for a long time now and if they didn't hit the tile cut before, they likely won't hit it now. Also I don't remember seeing geocaching.com at top places in the usage statistics last time I took a look.

@Rovastar

Good point. The attribution for the new MapQuest map is clearly missing (the display it for the other map types).

Usage of the osm.org tiles is not strictly forbidden. It's just a fair use policy you should act according to. Osm.org will block tile usage if this is overused.

I'll see if I can get someone from the foundation to take a look at it. It's no good if everyone writes a mail or comment on its own and they get flooded with this. It's probably just a mistake. That's only their second day after all.

You don't hijack anything. Actually, the more fun you have, the more advertisement for OSM it generates.

So just keep on going. You can contact me directly through the OSM messaging system if you need any help. Just remember only to use 'legal' sources for your mapping. Don't use google maps to look up anything. Local knowledge and the bing image background in the editor are fine though.

Have fun!

Found the bug. I used this tool to find the spot:
http://tools.geofabrik.de/osmi/?view=multipolygon&lon=-81.38484&lat=34.02844&zoom=18&opacity=0.76&overlays=invalid_geometry_hull,duplicate_ways,intersections,intersection_lines,ring_not_closed_hull,ring_not_closed,unconnected_end_nodes,touching_inner_rings_hull,touching_inner_rings,role_mismatch_hull,role_mismatch,duplicate_tags_hull,duplicate_tags,multipolygons_type_is_boundary,type_is_boundary,ways,role_markers,way_end_nodes,way_nodes

(sorry for the mess, don't know if I can use html syntax here to shorten the link)

There were some un-aligned endpoints along the southern shore line. I fixed that. Let's wait if the map will re-render.

Just remember that OSM has a lot of communication channels: this blog, the offical osm blog, the wiki, the wiki-discussions, the zillion mailing lists, a forum and some bugtracker-like system at help.osm.org and statistical sites like taginfo. You might get help on all of these, but none of them is ultimatively right about anything. But you will get a good overview while browsing the wiki.

@GEOMSG
Hey,

the lake showed up fine first, but then vanished. Seems that I had a good version in my browser cache which is gone now. I'll take a look into it.

The lake itself is not tagged as the small ones are. Because lines have a maximum number of nodes, a lake as big as this can not be described by a single line along its shore.

So the tags like natural=water and name=Murray Lake are actually on a so called mutipolygon relation, a virtual element which lists all the separate pieces of shore line.

You might want to read up on this on these sites:
osm.wiki/Relation
osm.wiki/Relation:multipolygon

Maybe some small part of the shore line was deleted or removed from the multipolygon list. I will see if I can find out.

@GEOMSG

Hey, thanks for contributing! Editing maps will soon be as much fun as geocaching. You will see ;) The updates on the actual maps take a while, as these need to be re-rendered first. Depending on the server load it may take less than a minute or up to a day. Higher zoom levels tend to update faster than those far away.

@Hendric I think GEOMSG just proved your point to be valid.

@CraigRat Yes, a pity that this troll spoiled this rather prominent thread. But the commenters just keep feeding him..
Here in Germany we have rivaling geocaching sites too, but they only have rather poor user- (and cache-) numbers. I hope your site does better. (You didn't name it by the way.) Geocaching.com has a lot of things to improve, but as long as they still do enough things right, the majority of users will stay there. But if you keep an eye on their policy regarding API, restriction of basic users and tightening of cache placing rules, we might see a change there in the future...

Hi,

1. Ja, das ist ein Problem, weil OSM keine Hoehe kennt. Einen 'richtigen' Weg gibt es da momentan nicht.

2. Wo (und ob) bei POIs das Icon dargestellt wird, wenn die Infos an eine Flaeche gemappt sind, haengt vom Renderer/Router ab. Wenn in der Datenbank *nur* ein Punkt eingetragen ist, lagen meist einfach keine Infos zur Flaeche vor (kein Luftbild). Man kann auch einen node des ways als entrance=yes mappen und dort die amenity ranschreiben, dann hat man wieder Kontrolle ueber den konkreten Punkt.
Ich persoenlich mache das so, wenn die Nutzung des Gebaudes nicht ausschliesslich zugeordnet werden kann. (Geschaefte in Wohnhaeusern z.B., im Gegensatz zu z.B. Kirchen)

3. Ohne Fummeln wird das leider nix. Entweder Werte kopieren (dann geht dir aber die History dieses Punktes floeten), oder Node aus dem way heraustrennen und dann verschieben.

4. Ich lese die Blogeintraege und kommentiere auch, allerdings laeuft hier in letzter Zeit so viel Spam durch, dass man schon mal was uebersehen kann.

Gruss,
Chaos99

Technically, the speed limit, the surface, the road width and state of the shoulder are all present in the database (or at least they can be mapped).

If this is unsuitable or unwanted can only be judged by the user and should be an option at the cycle router.

I personally would say anything with asphalt on it is unsuitable for my bike. I also don't really like going uphill (because I'm lazy). My girlfriend does like smooth road surfaces, but doesn't like to use any road where motor traffic is allowed. My co-worker prefers really smooth, flat surfaces and doesn't want to slow down for 30km/h zones.

Cycling is so diverse, you can't possible press that into an bicycle=unsuitable tag. Just map the physical and legal conditions out there and leave the rest to to be implemented by the route planners.

my two cents,

Chaos

Nothing wrong with that.

Adding entrance nodes is the easier way, because it works every time, and it also adds the additional information of the location of the entry.

Splitting buildings is only a good idea if it *is* a separate building. (Like inner city houses build side-by-side along the street). You can mostly spot that by different kinds of roofs or wall decoration. It's not a good idea if it really is just one building with several entrances (like an apartment block), because the separation would be only *virtual* and doesn't represent any facts about the real world.

There is an ongoing discussion about this on the german mailing list, but it seems to not matter if you tag the entrance (or POI) node(s) or the building itself with the address if there is only one. Just don't tag the same address multiple times (like with multiple POIs inside the same building). Tag either just the building or use a relation to group them all together.

That's all just my opinion of course. At the end there is no *right* way to do things here.

Chaos99

@Richard I see your point in not wanting to write that on every picture page. Do you see my point in not wanting to hunt that info down on your profile page when I'm interested in a picture? It surely depends on your jurisdiction, but at least I'm forced to attribute and state the license directly where I use the picture. Even writing it just at the end of the document may be not allowed. I don't want to do this either, but I just have to. Also there are those pictures edited by several users .... Or pictures that are clearly not produced by the user who uploaded it ....

But actually, your PD case is a bit different: As I have understood, you license your work as PD, then openstreetmap.org immediately re-license it as CC-BY-SA without attributing you. So you are out of the equation. When I want to use your picture, I have to attribute osm, not you. But I have to know that. Unfortunately there is no difference on the image pages between content re-licensed by osm and content licensed by their original owners.

@!i! Oh no, we don't even have them for the press images?

@AndrewBuck Thanks for the link!

I'm fine with public domain. My point was that they have to *declare* it. Most pictures miss license information altogether.

Every wiki page declares its content to be CC-BY-SA 2.0 (see the page footer). So things without a specific license automatically become CC-BY-SA, attributed just to openstreetmap.org. But of course everybody knows that this is not true for every picture. (All those screenshots of external websites for instance.)

You might get away with fair use when using the picture in the wiki. But you also have to *declare* that. Just omitting the license brings us back to the default CC-BY-SA, which isn't right.

Very interesting. Could you also verify that the accuracy is indeed increased when choosing 0.00km instead of 0.01km?

Thanks to all of you for your recommendations. I will work those into my talk.

Seems that Android is the OS of choice for most mappers. Well, can't say I'm surprised.
But is there anyone with knowledge about iOS apps?

Leider ist mir keine Ein-Klick-Methode bekannt.

Du kannst entweder die Sache erst einmal nur in openstreetbugs markieren, das ist wenig Aufwand, bringt aber auch nicht sofort etwas.

Oder du traegst selbst die Sperrung ein, und zwar mit den ueblichen Tags. Also ganz normal als Einbahn, als access=no oder mit Abbiegebeschraenkungen. Das ist natuerlich aufwaendig.

Hilfreich waere es, wenn du irgendwo (openstreetbugs, osm.wiki/Tag:note=) dokumentierst, dass das temporaere Aenderungen sind. Oder, noch besser, es dir zur persoenlichen Aufgabe machst genau diese Aenderung auch wieder zurueckzunehmen, wenn die Baustelle wieder verschwunden ist.

So habe ich das zumindest bisher gehandhabt.