Recent diary entries
How do we map areas that can be walked over but are not strictly a path?
For example, there may be a park or a green with grass that has no restriction on whether or not you can walk over it, but also has no path on it either. How do we map this so that routers could give walking directions over it, but without mapping a path that isn't actually there?
Looks like address quality in Oklahoma is going to continue to suffer, at least for a while. Some good news and bad news from the OKGIS community: First, the good news: Addresses are available under a license compatible with OSM. The bad news: $50 per county, and Oklahoma's got 77 counties, and only centroids. So, it's going to cost more than my truck did to be able to import a complete set of Oklahoma addresses. Damn!
Sinds gisterenavond ben ik vollop bezig om kaarten uit te werken van Nepal. De aanleiding? De grote aardbeving van vorige week.
Being a relative newcomer to OSM, I was surprised to find little data on Melbourne's tram stops. With the largest tram network in the world and over 1,760 stops on the network, it is a large project to complete.
With my local knowledge and some field trips, my aim is to input as much information as possible for each stop using tags. I have completed all of the route 48 stops as a sort of pilot, and many other routes will overlap.
I am particularly concentrating on the following attributes:
Any other attributes will be added as needed. I will record each route as I complete it, in no particular order.
Hopefully I can cover all 1,763 stops soon!
- Route 109
- Route 48
I've been trying to run through task "#1024 - Nepal Earthquake, 2015, Severely damaged housing areas and IDP Informal camps, Gorkha" using some of the post-quake imagery captured by DigitalGlobe on the Wednesday after the quake. I am looking at a tile of imagery from a very rural area.
Because it is monsoon season, Nepal was covered by quite a lot of cloud for a few days after the quake, and the imagery I am working on, from the 29th April 2015, isn't very clear. There is cloud cover over the majority of the tile and this image has very high off-nadir angle, so the recently digitised building footprints do not line up with this imagery very precisely. However, it's the best that is available, and it's what I have to use.
To my interpretation, it seems that most of the buildings that are visible on my specific tile held up pretty well. The majority of rooflines seem to be present and there doesn't appear to be rubble cascading away from the building sides.
Sadly, there is an exception. One particular building footprint stood alone, someway down a valley, and was clearly in the path of a landslide. Comparing the new imagery back to the pre-quake Bing image, it seems like this building has just gone. If anyone was inside when the landslide happened they wouldn't have had much of a chance.
I am sure when better imagery arrives we will see many many more damaged or destroyed buildings - but that doesn't make this one any better :(
Thanks Hedaja, SK53 and Alan for putting me right - The images are deceptive! I appreciate the hint to use OpenCycleMap to use the contours. Learning heaps!
It's now been around 2 years since I started editing OSM seriously. I've used Pascal's HDYC and YOSMHM to track my progress, with the goal of making a real contribution to OSM worldwide. One thing I always wondered about, as my OSM node rank went up. It would reach, for example, 300, and I would think, wow, I have been editing so much... who are these 299 people around the world who actually edit even more??
Recently, I set out to answer this question. I started looking at HDYC for well-known accounts, as well as their heatmaps, and gathering the results in a spreadsheet. When that got tedious, I wrote a C++ app on Osmium and ran it on the Planet.osm file, to find out the complete list of top-ranked accounts.
And the answer is... most of them are not actually people; a few are bots, and many are "import accounts", or user accounts that have been used for a large import at some point. (...but not all of them! Some are actual, live humans manually editing OSM longer and more extensively than me). Along the way, I learned some OSM history, and the diverse patterns in OSM in different countries.
Here is a link to the spreadsheet, sortable by rank, with my own notes on the where/what of around 400 accounts, including the top 100 in node and way ranks. The data is approximate... it's not auto-refreshed by a script (yet), so some ranks may be a little out of date.
In my next diary entry I'll share some of the stories and realizations I've had while gathering this data.
edits in Klettgau area, mainly on trees. Reminder: shape of natural reserve 'Widen'. To be checked.
Now we have at least 3 hard to detect version on the database. Can you spot a difference?
name="McDonald’s" ( count=126 ) U+2019 ’ e2 80 99 RIGHT SINGLE QUOTATION MARK
name="McDonald´s" ( count=40 ) U+00B4 ´ c2 b4 ACUTE ACCENT
name="McDonald's" ( count=14041) U+0027 ' 27 APOSTROPHE
see more: http://en.wikipedia.org/wiki/Apostrophe
With the drained out battery of GTA02 but a handy Sony CycleEnergy battery bank was able to trace from Midson to Marsden Rd. As usual the initial fix too bit of time(can't blame, it was cloudy). Got a lift too in Ashram car. The trace was immediately transferred to my laptop.
There was bit of a mess created at the time of submitting the trace in google map. It introduced a new layer concept which I couldn't understand and created a new layer which I found unusual and tried to delete the layer that I created which deleted the whole of the trace :( . There is no way to recover the trace.
The traces submitted here is going to help me to get the traces.
Apple has just approved Open GPX Tracker
Open GPX Tracker is a GPS logger for iOS (iPhone, iPad, iPod). Track your location, add waypoints and send your logs by email as GPX files.
This app has no annoying time restrictions, no ads and no in-app-purchases. Create unlimited GPX traces :)
Requires iOS 7.0 or above. Open GPX tracker is an open source app.
Note: Although, the app supports several tile sources such as OSM, the version published on the App Store, displays Apple Maps.
Here you have some links:
Details about iD editor users get publicly, permanently and silently logged with every edit – a privacy breachPosted by aseerel4c26 on 1 May 2015 in English (English)
Since the recent (estimated: two days ago) update to version 1.7.1 ("Add basic browser and platform info to changeset tags (#2559, #2449)") of our editor iD it publicly, permanently and silently logs operating system, browser and language details (+ more) for every user, for every edit by adding those tags to a changeset (example values follow; or see /history and pick a random one until you get one by iD):
browser = Chrome 37.0 locale = it-IT platform = Linux
- I could imagine good uses for this big pile of data ... e.g.
- it may help in debugging the editor
- one could potentially make nice statistics of our user base in total from this data (from a dump), or
- use it for quality assurance heuristics (e.g. it may be more suspicious if a foreign language user edits at a specific place),
- But I also could imagine bad uses for this big pile of data:
- it also enables everybody to create detailed statistics about a single user's browser update habits and browser name
- or operating system switching over time. Which all is not why people contribute to OSM.
- Language, Browser name, exact version and operating system name may make a contributor identifiable among a big group of persons, especially if some of those details are not very usual (think of someone speaking Lithuanian using Epiphany under Linux and editing in an Argentinian city – the expectation of only contributing under a pseudonym user name is quickly broken.
- The users have practically no chance to ever remove this information about them.
In the linked issues (found via the release comments) 2559 and 2449 I see no rationale at all why all this data needs to be saved 1. publicly, 2 permanently and 3. silently. Just reasons why the data could be useful are mentioned (similar to my ideas above) but not why the privacy and trust of our contributors needs to be hurt in this extent. Note: I have messaged the three involved developers/issue reporters via OSM mail about this post.
I think this recent change is really over the top and is doing harm, because to outsiders our project may seem as if it does not care about our contributors' privacy and fools new users by silently publishing information about them. I would hate it if, in the future, I would need to pass along a big warning about privacy when I try to attract new contributors.
Of course a simple workaround is to use another editor, e.g. JOSM, which I suggest doing for other reasons anyway.
Please, let's quickly remove this personal data canon before even more data is collected. By the way, I am intentionally not writing in a hidden bug tracker to make everybody aware of the problem and hopefully sensitise the developers a bit.
Update: on 16th May (15 days after writing this diary entry) iD's main code was modified and browser (browser name), version (browser version), platform (operating system) were removed again. Still, the locale (user's language setting) and host (the website at which iD is running at) are silently saved into the changeset tags. See https://github.com/openstreetmap/iD/pull/2643
Likely it will take some days until this new, partly fixed iD version appears on osm.org.
First day learning OSM today and can do it and digitise easily, Now familiarising with the terraced rural areas of nepal and digitising buildings paths and rivers.
IS THERE ANY API, DOCUMENTATION ON HOW TO GET STARTED ????
As a newbie, I am reluctant to comment, but I feel that some of the features tagged as rivers are in fact the tops of mountain ranges.
Hi am using a different approach navigation to use the search a good discussion
satellite image not updated. new roads not available for edit.
I have previous experience in identifying features in historic and modern maps and I didn't know that I could us this skill as a means of helping ... but I do now!
So here I am, I hope that I may be able to help in any little way that I can and I am learning so much in the process, what OSM is about and how it can be used to help.
This is a brief, but hopefully friendly opening to why I am here and my experience today.
Osm2pgsql 0.87.3 has been released. This development release primarily fixes bugs, but some of the bug fixes make other features usable.
Included is a bug fix for the lockfree queue implementation. Anyone using versions 0.87.0 to 0.87.3-dev, parallel processing, Boost 1.53 or newer, and not using --without-lockfree should immediately upgrade or stop using parallel processing. No data corruption issues have been observed, but the lockfree implementation may have been buggy on all systems.
There have been various fixes with moving hand-written C structures to C++ standard library equivalents and other code cleanups. The main user-facing changes are
The multi-backend should now be functional, with an example which creates separate tables for bus nodes, highways, and buildings
--without-lockfree is no longer needed on OS X, BSD and some Linux distributions and architectures. This should simplify downstream build scripts for multi-architecture builds and improve speed on any OS that required the option before.
nodecachereader should now work with node IDs > 2^31. This is a separate utility program, and obviously isn’t used much
Nominatim-related performance improvements
Many autoconf macros have been updated. This should ease configuration on non-standard systems.
This may be the last tagged release that does not require C++11. We have no current PRs which will require C++11, but would be willing to accept them.
A full list of commits is at https://github.com/openstreetmap/osm2pgsql/compare/0.87.2...0.87.3
As always, bugs can be raised at https://github.com/openstreetmap/osm2pgsql/issues. I’m particularly interested if package maintainers have concerns. If osm2pgsql isn’t packaged for your OS and you want to do so and have questions about the osm2pgsql side, please ask them too.
Many thanks to those who have contributed code to this and previous releases.
On behalf of the osm2pgsql maintainers
Minapa ko yung eskinita kung saan ako lumaki. Wala lang.
I love you Jen