User:Phobie
This user submits data to OpenStreetMap under the name phobie. |
Something went wrong ...
... with the OSMF
The OSMF does not act like being part of the community,
it acts like a company which owns a community, like FB and MySpace do.
There should have been community votes about if and how we should change the license.
... with the ODbL
The ODbL should protect Data better than the CC-BY-SA does.
And yes, the protection of the data is better than before,
but at the same time it lowers protection a lot by not covering any derived works.
What is free about OSM, if a company can take the data to create unfree maps?
... with me
I did not close my eyes and blindly clicked accept like most other users did.
I thought about the consequences the ODbL would bring to us and
after reading a lot, I came to the conclusions that the new license will be bad for the project.
So I tried to slow down the planed data removal by rejecting the the new license for as long as possible.
Many community members did not liked that, because they wanted to remap data before the big removal.
IMHO it is a better idea to start remapping only after the removal to avoid work duplication and to slow down the destructive work of the OSMF.
I accepted the license only because the OSMF forces me to do so, not because I thing it is a good idea.
It would be better if we just mark CC-BY-SA-only-content as such and create several planet dumps in future.
With this solution data-consumers could decide which dump is better for their plans.
I think the best solution would be to add a license property to every OSM-object and let the users decide which licenses they want and can use.
After writing this I found a interesting page: User:TimSC/Quit
And please have a look at: Template:Multilicense
User phobie
phobie lives in Schleswig-Holstein, Germany and contributes to OSM since 2007.
Sources for GPS-traces:
- NMEALogger on a TomTom One of the 4th generation
- Openmoko on a Neo Freerunner.
- Nokia N900
Copyright
OSMF License Change
Während die Rechteabtretung an die OSMF eine gute Idee zu sein scheint, gibt es doch einige "Unschönheiten":
- Die OSM.org CTs sind inkompatibel zur ODbL! Man darf also keine Daten aus ODbL Quellen zu OSM.org hochladen. Man darf nur Public Domain Daten oder Daten, die Speziell für die Verwendung auf OSM.org freigegeben wurden, verwenden. Da sich OSM.org über die CTs die Veröffentlichung der OSM-Daten unter Public Domain vorbehält, muss jeder Datenspender damit rechnen, das seine Daten irgendwann ohne Copyleft angeboten werden.
- Durch den vollständigen Vollzug der geplanten Lizenzänderung wird es zu massivem Datenverlust und/oder Urheberrechtsverletzungen kommen. Statistiken dazu beziehen sich immer nur auf die neuste Revision eines Elements, es müssen aber alle Elemente gelöscht werden, bei denen sich in irgendeiner Revision ein Username befindet der gegen die Relizenzierung ist oder nicht reagiert hat. Bei kopierten Objekten, lässt sich teilweise gar nicht feststellen auf welchen Objekten sie beruhen.
- Wenn man beim Editieren CC-BY-SA Quellen verwendet hat, dann darf man seine Daten nicht unter der ODbL relizenzieren!
- Der Relizenzierungsprozess ist nicht mit dem rechtlich sauber durchgeführten Lizenzwechsel der Wikipedia vergleichbar!
- In der Entscheidungsfindung und der anschließenden Abstimmung, die die OSMF alleine vorgenommen hat, hätte die Community mit eingebunden werden müssen. Die in den neuen Mitmachbedingungen genannte 2/3 Mehrheit unter den aktiven Mappern, hätte der Entscheidung zur Lizenzänderung Rückhalt in der Community gegeben.
- ODbL == "Public Domain" - Dadurch, dass unter der ODbL Kacheln nicht lizenzgebunden sind, kann man durch automatisiertes Rendern und anschließendes tracen, die Lizenz komplett abstreifen. So ist es mit einigem technischen Aufwand möglich einen lizenzfreie 1zu1-Kopie der OSM-Datenbank anzufertigen! (Diese Aussage ist umstritten. Endgültige Sicherheit würde nur ein Gerichtsprozess bringen, aber auch nur für das jeweilige Land.)
- Mit dem Lizenzwechsel wurden gleichzeitig die Regeln in Bezug auf die Verwendung von Kacheln gelockert. Das wäre nicht nötig gewesen! Jetzt kann es passieren, das ich keine Rechte an Karten habe, die aus von mir erstellten Daten erzeugten wurden!
- OSMF kann aufgrund ihrer Größe und Aufnahmebedingungen problemlos infiltriert werden. Gerade für Kartenfirmen ist die einfache Einflussnahmemöglichkeit reizvoll. (Eine Verschwörungstheorie, im Auge behalten sollte man es aber dennoch!)
My tagging proposals
maxspeed values
Use implicit values in maxspeed: maxspeed=<country code>:[urban|rural|motorway]! It has been proposed to use source:maxspeed=*, but it will not always be tagged and that we will have many maxspeed-values without source:maxspeed. Also source* is used for free text comments about the used sources, not for real tags. Think about the mantra of tagging what you see and not what you interpret! Seeing traffic_sign=city_limit and interpreting maxspeed=50 from it, is more than a mapper should do.
access namespace
Prefix sub-keys from Key:access with 'access:'
- access:bicycle=no instead of bicycle=no
This could make parsing easier and avoid unclear interpretation. I do not use this yet because it would be a major change like renaming 'highway' to 'street'.
addr namespace
- Use the addr:* namespace
- addr:postcode=* instead of postal_code=*
- addr:housenumber=<number> - As single node or on the main entrance of a building
- addr:interpolation=odd/even/all - As a virtual way to interpolate between housenumbers.
- Relation collection, street or associatedStreet - Relation between street and housenumbers. They are all different names for the same thing, I would prefer collection and street because associatedStreet is a more difficult word.
- See also: Proposed_features/House_numbers/Karlsruhe_Schema
contact namespace
- Use the contact:* namespace
- contact:website=* instead of website=* or url=* (url cam mean everything so it is a no-go)
- contact:phone=* instead phone=*
- contact:fax=*
- contact:email=*
Railways
- railway=switch + control=manual;local/manual;remote/automatic;remote
- railway=derail + control=manual;local/manual;remote/automatic;remote - (Gleissperre)
Foot- and Cycleways (Rad- und Wanderwege)
Tag street escorting Cycle- and footways as separate line if:
- if is separated by grass verge or parking places or
- if you have very accurate sources or
- if traffic routing differs from the street
Bike/foot informations on the street
Key | Value | Note |
---|---|---|
footway[:left|:right] | [track|lane|no|yes] | Try to avoid yes and specify track or lane. Do not use cycleway=both/left/right as we do not have a separate key to store track vs. lane. |
cycleway[:left|:right] | [track|lane|no|yes] | Try to avoid yes and specify track or lane. Do not use cycleway=both/left/right as we do not have a separate key to store track vs. lane. Do not use opposite here as we have oneway:bicycle=*. |
cycleway[:left|:right]:oneway | [no|yes] | This should always be tagged as we do not have reasonable defaults. |
Bike/foot informations on separate line
- highway=cycleway/footway - like with other highway=*-values tag it by condition and not by right of way, use access=* for right of way. Do not use highway=path, it is useless and not well supported.
- oneway=yes/no - always set this tag as we do not have a usable default value
- surface=* - it is always good to know the surface type
- sac_scale=* - only for demanding foootways
- smoothness=* - as mtb:scale=* is only for demanding ways and we do not have a bike_scale yet
Roundabout (Kreisverkehr)
- junction=roundabout instead of highway=roundabout - does not interfere with the street type
general tagging help
- Map Features ENG GER - common tags explained {Erklerungen zu verbreiteten Tags}
- Road Signs ENG GER - list of signs and how to tag them {Liste von Straßenschildern und wie man sie tagged}
- Howto_Map GER - Like Map_Features but sorted by name {Wie Map_Features nur nach Namen sortiert}
- Proposed_features/barriers - better than using "gate" {Poller anstatt Tor}
- GpsDrive naming scheme {Wie GpsDrive Tags nutzt}
- Key:highway ENG GER - The main tag for streets {Der Wichtigste Tag zum beschreiben von Straßen}
- User:Florianheer - some ideas about tagging {Ein paar Ideen zum Taggen}
- Key:access ENG GER - how to set the access of streets {Benutzungsbedingungen/Verbote}
Links
Software
- Navit - Routing software
- GpsDrive - Routing software
- Gosmore
- Maperitive - OSM-Renderer, Windows,
- Viking GPS data editor and analyzer
OSM-Wiki Links
- DE:Germany roads tagging - how to tag roads in Germany
- WikiProject Germany
- Public Transport
- Networks
- Railway routes
- Proposed freight alternatives Lübeck–Puttgarden 2995797 2995797
- Süderbrarup–Kappeln 3009592 3009592
- Schleswig Altstadt–Süderbrarup 3009595 3009595
- Schleswig Altstadt–Schleswig 3009594 3009594
- Schleswig Altstadt–Satrup 3009593 3009593
- Friedrichstadt–Schleswig 3008295 3008295
- Husum–Erfde–Rendsburg 3009710 3009710
- Bahnstrecke Malente-Gremsmühlen–Lütjenburg 2896963 2896963
- Kleinbahn Kirchbarkau–Preetz–Lütjenburg 2896964 2896964
- Kleinbahn Kiel–Segeberg 2895695 2895695
- Bad Oldeslohe–Hagenow (Kaiserbahn) 2902987 2902987
- Mölln–Hollenbek (Hein Hollenbek) 2903104 2903104
- Boundaries
- Routes
External Links
- Waycheck by Gary68 (gary68.de)
- Tagwatch by stoecker.eu (stoecker.eu)
- Tagwatch, all used Tags in Germany (stoecker.eu)
- Tagwatch etricceline.de (etricceline.de)
- Tagproposals of GPSdrive (gpsdrive.de)
- relation browser (schunterscouts.de)
- OpenRoutingService (openrouteservice.org)
- OSM history at geofabrik (geofabrik.de)
- Downloadsite for worlddumps (openstreetmap.org)
- Splitted worlddumps by geofabrik (geofabrik.de)
- Waycheck Schleswig-Holstein (gary68.de)
Map services
Map-Links for Lübeck (latitude 53.8966, longitude 10.7487, zoom 12):
- General OSM Maps
- OpenStreetMap front page map
- OpenStreetBrowser
- OpenLinkMap (minzoom=14)
- OpenOrienteeringMap(minzoom=15)
- Cycle Map (OSM) at OpenCycleMap
- Hike & Bike Map
- Information Freeway (OSM)
- Wikipedia (OSM)
- FreieTonne Waterway Map (OSM)
- Mobile Map (OSM)
- MapSurfer (Road)
- MapSurfer (Topo)
- Address map (OSM)
- Blitzermap - Traffic enforcement map (minzoom=11)
- Surveillance map
- Quality assurance
- Local Maps
- Routing
- Aerial photos
- NON-OSM-Maps
Map-Links for Kiel (latitude 54.31066, longitude 10.14553, zoom 12):
- General OSM Maps
- OpenStreetMap front page map
- OpenStreetBrowser
- OpenLinkMap (minzoom=14)
- OpenOrienteeringMap(minzoom=15)
- Cycle Map (OSM) at OpenCycleMap
- Hike & Bike Map
- Information Freeway (OSM)
- Wikipedia (OSM)
- FreieTonne Waterway Map (OSM)
- Mobile Map (OSM)
- MapSurfer (Road)
- MapSurfer (Topo)
- Address map (OSM)
- Blitzermap - Traffic enforcement map (minzoom=11)
- Surveillance map
- Quality assurance
- Local Maps
- Routing
- Aerial photos
- NON-OSM-Maps
unlinkable
- tracks4bikers routing (OSM)
- Microsoft live (Navtech)
- suchen.de (Navtech)
- NL maxspeedmap
- maps-for-free.com
misc
- In addition to the CC-by-sa license, this user has granted (or hereby grants) permission to copy, distribute and/or modify all its contributions to OpenStreetMap under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
I support the existing CC-BY-SA 2.0 license and don't want data or active users to be abandoned.