Re: [OSM-talk] [tagging] Feature Proposal - Voting - boolean values
On Sat, 3 Oct 2009 09:02:07 +0200, Konrad Skeri wrote: > Time to end this debate > > http://wiki.openstreetmap.org/wiki/Proposed_features/boolean_values I do not think that jumping over "Draft" and "Proposed" stages directly to "Voting" stage for a Proposal is in accordance with http://wiki.openstreetmap.org/wiki/Proposed_features#Proposal_creation_guidelines If you're going to use the voting process (which might or might not be useful for a proposed change like this) , could you at least please stick to its own rules ? I don't think that trying to abuse it this way will help anyone. As it stands, I'm opposed to it, and with (not very major) modifications I could've been for it. But skipping appropriate Draft and RFC stages made made it impossible (for me or anyone else) to influence the proposal in time, so the effort is now wasted (as you cannot change the proposal once the voting has started, per rules above) -- Opinions above are GNU-copylefted. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Find all your unresolved Notes
OSM Notes are quite useful feature, and if you take advantage of it, you'd have a lots of Notes. Vast majority of them resolved and closed, of course, since you're an active mapper. However, those that remain open will likely be lost forever, as browsing your OSM user pages through dozens (and hundreds) of closed Notes (until you find open one) is very tedious. And if you have multiple accounts (and/or are tutoring your SO and friends in OSM), the pain in finding older unresolved Notes increases exponentially. So I've made a web script that shows you ONLY open notes for specified user (or several of them). You can use it at: http://my-notes.osm-hr.org/ (or go grab the source yourself at https://github.com/osm-hr/my-osm-notes ) -- Opinions above are GNU-copylefted. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Find all your unresolved Notes
On Wed, 4 Feb 2015 07:09:44 +0100, Stefan Baebler wrote: > Odlično / Excellent! thanks! > Just fix the case sensitivity of usernames during search. Done. It should be case insensitive during search now (yet remain case preserving during display). > Filtering for unresolved notes should be implemented also on the user's > notes page on the main OSM website somehow to encourage mappers to > follow-up on them and resolve them. Yes, it should. There is even a ticket opened for that: https://github.com/openstreetmap/openstreetmap-website/issues/832 -- Opinions above are GNU-copylefted. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Wiki - Croatian and Bosnian languages - mass-namespace editing notice
Today, User:Wynndale decided to do mass-rename of all pages in Croatian (Hr:) and Bosnian (Bs:) namespaces, moving them to so-called "Serbo-Croatian" (Sh:) namespace. He did that without even trying to contact interested parties (for Croatian pages, that would be http://lists.openstreetmap.org/listinfo/talk-hr list). Also, the so called Serbo-Croatian language does not exist (see links below). ISO 639-1 ( http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ) defines separate languages - Croatian (HR), Serbian (SR), Bosnian (BS). As he had not replied to his user talk page I don't know yet if it was done out of ignorance, or malice. I've managed to revert/undo most (I think) of the damage he'd done, wasting half a day to do it. Template:Languages damage will take some time to get regenerated :-( The (unasked-for) changes can be seen at: http://wiki.openstreetmap.org/w/index.php?title=Special:Contributions&limit=500&target=Wynndale (just look for "Sh:" and "Serbo-croat" strings) I've also documented the case with more info at: http://wiki.openstreetmap.org/wiki/User_talk:Wynndale http://wiki.openstreetmap.org/wiki/Template_talk:Languages#Languages_and_politics -- Opinions above are GNU-copylefted. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Torrents for planet.osm.bz2 are available (again)
As mentioned on the http://wiki.openstreetmap.org/wiki/Planet.osm#Bittorrent new full-planet torrent service has been set up at http://osm-torrent.torres.voyager.hr/ The torrent uses trackers which should be IPv6+IPv4 capable, and also supports webseed in case no clients are reachable. Your participation in the swarm and feedback are welcome. Thanks, Matija -- Opinions above are GNU-copylefted. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Torrents for planet.osm.bz2 are available (again)
On Fri, 17 Dec 2010 00:11:04 +0100 (CET), Stefan de Konink wrote: > Thanks for picking this project up :) I'm glad if people like it and use it ! BTW, there is now RSS feed at: http://osm-torrent.torres.voyager.hr/files/rss.xml so interested parties (and those willing to help to donate some bandwith to build better torrent swarm) can subscribe to. Your feedback of how well it works is also most welcome for this proof-of-conecept project. As I said before, it would however be very nice if OSMF would pick this up and setup on their server planet.openstreetmap.org (it is very easy procedure, and it would spare bandwith and completely remove [up to 48h] delay that is currently imposed) So some lobbying at OSMF to implement it would be most welcome :-) All scripts are available at http://osm-torrent.torres.voyager.hr/ and I'll help in any way I can to help implement it if needed (and the scripts are really very simple and only tiny amount of work is needed to implement those!) > Hopefully the PBF's can get seeded as well :) I'd love to, but: a) I'm lacking in disk space in machine on which I have enough bandwidth (and I can't add disks in it). This is the biggest showstopper ATM. And on the other machine which has enough disk space I can't spare the bandwidth for few dozen GB a day (or more). b) only PBFs I've been able to find are the ones at: http://download.geofabrik.de/osm/europe/ which has few problems: b1) torrent is not that big a gain on small files, it really shines on bigger ones (and geofabrik mostly provides country extracts which can be as small as one megabyte). It might be however possible to create multi-file torrent which contains all extract, and people could then cherry-pick what they need, which would solve most of this problem. b2) webseed feature of torrent files really expects that files don't change (the ones at planet.openstreetmap.org don't as they have date in filename, however the ones at geofabrik are overwriten daily AFAICT). This could however easily be fixed with a change if file naming policy at geofabrik (and/or other PBF provider). This could also be worked around if I had solution for (a). b3) torrents (especially delayed ones, as are any wh are not created directly at the same place of main PBF creation - like mine site) prefer files that change at slower rythm (weekly planets are fine, daily planets might be too frequent). Although this could also be fine if you can host dozen last versions at the same time - which also could be mostly worked around - if I had solution for (a) Most if not all of those issues would be alleviated or completely removed if geofabrik (and/or OSMF) would decide to implement those torrents directly at their servers. -- Opinions above are GNU-copylefted. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Proposed automated edit of some barrier=kerb kerb=raised nodes (forum crosspost)
In https://community.openstreetmap.org/t/proposed-edit-of-some-barrier-kerb-kerb-raised-nodes/98038 user @osmuser63783 proposed automated edit: -- If you’ve been reading my posts about kerb tagging (1, 2), then you already know that StreetComplete places kerb=raised by itself on a node where a footway meets a road to mean “you might expect a crossing and lowered kerb here but there isn’t one”. Whether there are better ways of tagging this is currently being discussed here. The problem is that iD users have added barrier=kerb to such nodes because the validator in iD told them to. This leads to issues, because it’s interpreted as a raised kerb across the road. For example it stops OSRM from routing cars along the road. The good news is that new nodes like this will no longer be created because of a recent change in iD, disabling the suggestion to add barrier=kerb to such nodes. I’m grateful to everyone involved that this has been fixed so soon after I spotted it. The bad news is that there are now about 1,500 nodes tagged barrier=kerb kerb=raised that really shouldn’t have the barrier=kerb tag. How would people feel about editing them all in one go, following the automated edit code of conduct? I propose doing something like this use Overpass (query) to get all barrier=kerb kerb=raised nodes on roads (i.e. highway ~ trunk|trunk_link|primary|primary_link|secondary|secondary_link|tertiary|tertiary_link|unclassified|residential), there are 1495 of them check a few dozen manually and only proceed if they are clear tagging mistakes for each suspicious node, retrieve the history (example API call) find the changeset that added barrier=kerb; retrieve the changeset metadata (example API call) and see if it was created_by iD with resolved:outdated_tags:incomplete_tags >= 1 if yes, go back further in the changeset history to find the changeset that added kerb=raised; retrieve the changeset metadata (example API call) to see if it was created_by StreetComplete with comment “Add whether there is a crossing” or “Specify whether there are crossings at intersections of paths and roads” generate a couple of OSC files, e.g. one for each grid square (which resolution is appropriate? in other words, how many changesets should there be vs. how big should they be?) upload here for scrutiny and check manually, then after people have had a chance to check it, commit using JOSM, with a changeset comment linking to the discussion, etc. Importantly, this excludes all situations where barrier=kerb was added before or at the same time as kerb=raised, or where they used a different editor than iD, or where kerb=raised wasn’t added by StreetComplete. We don’t want to retag anything where a human set the barrier=kerb tag on purpose. It would require a few read-only API calls (no more than 4500) that could be spread out over a few hours to make sure that service levels are not affected. Why not create a Maproulette challenge? I don’t have any experience with Maproulette, but from what I can see, I think it works best when some human intervention is required. Using the steps above we should be able rule out that someone added the barrier=kerb on purpose to mean that there is a kerb across the road, so checking each one manually would not be a good use of anyone’s time. Any thoughts on this? [1] https://community.openstreetmap.org/t/tagging-kerbs-on-crossings/9290/ [2] https://community.openstreetmap.org/t/improving-the-wiki-documentation-of-barrier-kerb-and-kerb/97042 -- (posted for more visibility in talk ML on @osmuser63783 request so people wouldn't get surprised. Go to top URL for better formating with all the links) -- Opinions above are GNU-copylefted. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
