Recent diary entries
This is a review test
Hello all, Namasthe! 🙏 We had an amazing HOT Mapathon on July 21st at Mapbox India office. We had the local OSM community along with folks who were mapping for the first time adding approximately 3000 buildings in Cambodia for Eliminate Malaria task.
The good thing about this event was that most of them knew about OpenStreetMap and very few people were new into mapping activity. At first, we introduced to OpenStreetMap, it’s data model, and good practices one should know while editing and a short demo of editing in iD editor.
Upendra introducing the HOT and it's objectives
Jinal Foflia helping the participant for mapping
Many of us discussed about ongoing mapping activities in Africa with more emphasis on FGM and Malaria issues and how non profit organisations are utilising the data that people produce to save many lives. Also, we've discussed about upcoming State of the Maps in Japan, US and Nepal. Some of the questions they asked are like, how data produced by many people been validated? who will take care of ground truth? and what is the community capacity right now? and so on. Hope we cleared all of them!
We hope to have many more events in the future with the community and help for humanitarian purposes.
هذا ملعب الفقيد علي اسعد المصري المضو مديرية الشعيب محافظة الضالع مع تحيات الشيخ غسان المصري
When we started mapping public transport stops, some people insisted on mapping them on nodes next to the way, others thought the right way to do it, was to add them as nodes being part of the highway, thereby losing the information on which side of the road the bus stop was.
Then somebody came by with the idea to unite both ways of mapping. In itself that sounds great. But where do we add the details then? On both? That doesn't really make sense. It's a maintenance nightmare.
So we still have some people adding the stops as stop_position nodes on the highways and others mapping them as isolated nodes next the ways as public_transport=platform. But of course a node is not a platform, so others map those as ways and areas. Nothing wrong with that, but why do we need to add all the details to these ways?
For some reason it was decided that both these stop_postion nodes and the platform ways/nodes need to be added over and over again to the route relations. These route relations represent each and every variation of the public transport lines, so there are thousands of them. Another maintenance nightmare.
Why can't we have a node next to the way, with all the relevant details and add those nodes to the route relations, then followed by a continuous string of ways? The node gets tagged public_transport=platform/highway=bus_stop.
The node isn't always representing an actual platform. If there is a platform, nothing wrong with representing it as a way or an area. But there is no real need to duplicate all the details like name/ref/route_ref/zone to these ways. And there isn't really a need to add them to the route relations.
For the simplest bus stops a node next to the way public_transport=platform/highway=bus_stop is all that is needed. It contains all the relevant information and it has coordinates, which makes it convenient to compare it to data from operators.
For more completely mapped bus stops, benches and waste_baskets can be added.
If you want to make explcit where the vehicle stops, a public_transport=stop_position can be added on the highway. For the first and last stops, the way should be split there, as it's the beginning or end of the route.
But these stop_position nodes are not all that important, so no real need to map them for every stop. Also no reason why the stop details should be repeated on them and no real need to add them to the route relations. It's enough to add them to stop_area relations.
Die Kartierung der Wanderrouten bzw. der Wanderwege ist dank der zahlreichen Mapper gut vorangekommen. In den Jahren sind aus lokalen Rundwegen sehr oft Themenwege geworden. Dabei sind nummerierte Wege auch entfernt worden. Zumindest auf den neuen Infotafeln. Im Gelände findet man weiterhin alte Markierungen aller Art, leider. Ein Schwachpunkt ist die Aktualität der Daten. Einmal erfasst, so lässt die Aktivität der Kartierung an den Wanderwegen nach. Es gibt zwar zwar Mapper, die sich darum kümmern, jedoch nicht so viele wie zur Zeit der Ersterfassung. Mir ist bisher nicht bekannt, dass von Gemeinden, Vereinen, Verbänden ein aktiver Beitrag zum Datenbestand stattgefunden hat.
heute findet in Lübeck der 100. Stammtisch für Lübeck und Umgebung statt.
ref = FS xx
highway = unclassified
- maintained as a through road connecting other roads OR lenghty and provides access to a significant point of interest
- generally maintained to a level usable by a standard passenger car without AWD/4WD (smoothness = bad, or better)
- paved or unpaved
- Example: Cooper Creek Road (FS 33) and Blue Ridge Road (FS 42), in Georgia
highway = track
- not a through road
- generally unmaintained, AWD/4WD is recommended or necessary (smoothness = very_bad, or worse)
highway = service
- not a through road
- paved or unpaved
- short or medium length
- provides access to a point of interest
He terminado de recopilar las relaciones tipo ruta de las líneas de transporte público en autobús de Málaga. Las he ido anotando todas en la tabla de la página wiki dedicada al transporte público de la ciudad.
En los próximos meses espero encontrar tiempo para revisarlas todas en detalle. Me puede llevar meses si pretendo hacerlo solo, así que me lo tomaré con calma. Habrá que comprobar si las líneas están completas y correctamente mapeadas, añadir las líneas que faltan y, sobre todo, mapear las paradas. Hay mucho trabajo por hacer, pero también debo reconocer que hay mucho trabajo previo hecho y bien mapeado por otros colaboradores. Casi todas las líneas de autobús de Málaga están en el mapa y etiquetadas correctamente.
Paralelamente, seguiré con el mapeado de edificios del casco urbano. También quiero retomar lo que fueron mis primeros trabajos de mapeo, los relativos al trazado de caminos, arroyos y localización de caseríos y lagares abandonados de los Montes de Málaga.
En las últimas semanas he tenido algunas experiencias ingratas en lo relativo a la traducción del wiki, así que me desentenderé un tanto de esa tarea por ahora. Tengo que replantearme esos trabajos. Supongo que lo mejor para no perder la ilusión del principio será volver a los orígenes, a mapear esos caminos solitarios de los montes por donde suelo salir a caminar.
A few weeks back I gave a talk in London which was a sneak preview of my "Diagrams Of OpenStreetMap" SoTM talk Yes! I'm heading to Japan for the conference soon! I'm the only one from the London crowd going, so this wasn't a spoiler for anyone in the audience, but this diary entry is a small spoiler. I thought I'd give some details of just one diagram from the talk. This one:
You may recognise it although I think its "Component Overview" home on the wiki is a bit hidden away these days. But anyway you wouldn't recognise the right hand side because this is newly redrawn as of last night! In fact I've done a few iterations which I am unveiling as part of the talk. The left hand side editors were given an update, but last night I was tackling the more tricky right hand side where we try to show different rendering stacks and map display approaches available and used in the wider ecosystem.
Up until last night this simply described one possible "TileMill" set-up. That technology is a bit obsoleted by Mapbox Studio these days, but more importantly it's only one of a range of new tools. So to iterate on this, redrawing a little bit, I've aimed for a more high level summary of tech concepts on the right.
A key new technology concept which is very much part of this landscape now is "vector tiles". Been around for a long time of course, but these days lots of folks are making very practical use of OSM vector tiles within commoditised rendering stacks and other tools. Time to bring it into the diagram. Hopefully I've connected things up reasonably correctly. Vector tiles can be used as a data source fed into good old raster tile rendering, but they can also be fed direct to the browser to be displayed there instead of raster tiles. That happens usually still with the use of LeafletJS via tools which I've collectively called "Vector plugins"
That's my understanding. But I'm a little unsure of the details. The level of abstract summarisation here is avoiding the details, but I would like to see a diagram which shows more specific technologies. Probably a different diagram, rather than trying to add it all on here. Something with boxes for: Mapbox studio, Mapbox GL, Tangram, Tangram Play, ThunderForest's stack, OpenMapTiles stack, and the different vector tile formats, schema formats, style sheet formats, etc, etc. A layered diagram summarising all things vector tiles. That's a difficult diagram for me to draw, because I am shaky on the details and generally finding some of the linkages unclear, but maybe that's a clue that this will be a useful diagram!
Maybe I'll create something myself in time for the conference, but maybe not. Do let me know if you know of any existing diagrammatic efforts in this area. In fact let me know if there's any diagrams you think deserve a mention, whether on similar tech topics or something completely different. I'm ruling out auto-generated "visualisations" from my definition of "diagrams", but other than that it's wide open to all sorts, and I'm hoping to give a bit of a tour of a wide variety of "diagrams of OpenStreetMap".
Technology and innovation have opened up tremendous amounts of opportunity for surveyors, map users and the GIS industry. but there is a lot of incorrect info about what is changing and how it’s changing. Nonetheless, there is a huge opportunity for surveyors that recognize the advantages associated with being early-movers. That’s just part of what’s so exhilarating about the future of the industry.
I’m most excited about how open streetmap is using technology in a way that enables the next generation of youths to use maps and change the environment. The GIS industry faces a growing age divide — there are not enough young enthusiast to take over for those who are approaching retirement. When we work with the younger generation of mappers, I love to encourage youth mappers to start capitalizing on web-based open geospatial technologies, together we can cultivate a generation of young leaders to create resilient communities and to define our world by mapping it. There is no better time than now.
Как правильно обозначать такие магазины? / How correctly to designate such shops?
I wanted to get to know my new neighbourhood better and try some new tools . So this weekend I tested Opencamera to take photos and good old OSMTracker for GPS traces. I took a peek on to the map, set camera to burst mode to click every 10s and set out to the direction of Bellandur lake. After passing HAL airport, the terrain seemed to change quickly. I went from paved roads to dirt roads and tracks (later I realised I cut right through the dried part of the lake). I wasn’t checking maps and ended up on the outer ring road, took a U-turn and managed to reach to the other side of the lake.
Spent some time enjoying the view and started back. It was nice to see calm and green place not far from the city, but felt sad that construction and pollution is eating it up.
After 4 hours of cycling I reached home loaded GPX on JOSM, and I was more sad. My phone didn't let osmtracker update location information in the background and most of the tracks were just straight lines. First I thought it was a bug (like one which causes osmand to crash on this) but later figured out that it was a power saving feature 😑 . But was lucky that I had geo-tagged photos, and recreated the track from them :)
After a small break I set off to Indiranagar to play cricket with friends. I was happy to know that I covered around 37 kms on cycle that day. 🚴
So learning from yesterday’s mistake, I turned off power saver for OsmTracker and locked the app from being closed automatically. It took around 1 hour for me to cycle to Cubbon park. As roads through the park are not open to motor-vehicles on Sundays, you can explore 300 acres on foot or cycle in peace. The place felt very calm and relaxing, you can engage in various activities there, rent a cycle and go around see kids play at the playground, watch flocks of pigeons feeding or sit and listen to the creaking bamboos. There’s even a fenced area for dogs and owners meet going on, so went in to spent some time with those fuzzballs.
I roamed the park for some more time and left for the day. I loaded the GPX on JOSM as soon as got home and found that they are all well mapped thanks to mappers like PlaneMad ,Praveen, Nagesh_Blr
Total mileage for two days was around 70 kms but usable data collected was low, I am currently adding details from my memory and photos I clicked. Will try to improve next expedition with Mapillary and OpenStreetCam.
Tagondaing is located in Myanmar
If you are an owner of a Garmin 520 device, you may have discovered the device has the capability to use custom maps in the standard Garmin .img format. Unfortunately the device has quite limited internal storage (up to around 100MB) and no external SD card capability.
Storage space can be increased by removing the default Basemap and maps of your choice (e.g. your local area) can be acquired via the excellent OSM Garmin Maps website.
Further information about doing this can be found via these blog posts:
However consider the needs of the long distance cyclist - such as a participant in London Edinburgh London, the premier Audax UK event - in this scenario the above available maps needed to cover the area being travelled will be too big to fit on this device.
One can use OSM data directly and process the data yourself using Open Source tools to generate a gmapsupp.img file that covers your area of interest. My operating system is Debian Linux so the tools needed are available, of a modern enough version and easy to install via the standard operating system 'apt-get' manner:
Those using Windows or Mac OS's can run these tools but installation is normally more intricate and one will need to refer to the individual websites for specific instructions.
My method for generating a suitable gmapsupp.img is thus:
- Download a OSM data extract in PBF format - Geofabrik
- Run osmosis to remove and contain only the relevant data wanted for the map.
- Create the map using mkgmap, using the default style.
- Transfer to your Garmin device and enjoy.
All these steps can be easily scripted to be able to run with different parameters, such as adjusting the data being used or for a newer dataset.
Note if you run mkgmap directly on an Great Britain extract, the resultant map is 220MB and thus too big to fit on a 520 device. Hence the osmosis commands are used.
Here are my osmosis and mgkmap commands in shell script with approximate timings of the operations on my desktop PC (1.4GHz).
export myPBF="great-britain-latest.osm.pbf" export poi_tags="amenity=toilets,fast_food,cafe,pub,shelter shop=convenience,supermarket,bicycle" osmosis \ --read-pbf "$myPBF" \ --tf accept-ways \ highway=* \ waterway=river,canal \ railway=rail,preserved \ natural=water landuse=reservoir \ $poi_tags \ --tf reject-ways highway=path,footway,track,bridleway,service \ --tf reject-relations \ --used-node \ --write-xml ways.osm # ~15 mins osmosis \ --read-pbf "$myPBF" \ --tag-filter accept-nodes place=* natural=peak $poi_tags \ --tf reject-nodes place=isolated_dwelling,farm \ --tf reject-ways \ --tf reject-relations \ --write-xml nodes.osm # ~2 mins osmosis --read-xml ways.osm \ --rx nodes.osm \ --merge \ --write-pbf \ reduced.pbf # ~3 mins mkgmap-splitter reduced.pbf # ~1 minute mkgmap --index --gmapsupp 63240*pbf # ~4 minutes
The resultant gmapsupp.img file is 77MB big, so fits easily on a Garmin Edge 520 device and can be transferred to the device by a file copy to the usual "Garmin" folder location on the device.
A copy of this specific gmapsupp.img is on Dropbox
Alternative strategies for creating a smaller map file could be to define a smaller data area via a simple bounding box or a more complex polygon or trying to customize the mkgmap style rules but I haven't tried these.
I will be participating in LEL next week - wish me luck :), but I will be using my trusty Garmin eTrex 20 - which having 2Gb internal storage - with the free standard map provided by https://talkytoaster.com - as per my normal outdoor cycling and walking (and on the side OSM surveying) activities.
I generated this mainly for a good friend who has a 520 device, but hopefully the above example will be useful for others to use directly or tailor this process for their needs.
Today I spent about 4 hours cruising the Täze Köşi, Parahat 7, and Gaža neighborhoods of Ashgabat to collect GPS traces of new streets and to identify new schools, kindergartens, and other public buildings. As the onset of the Asian Indoor and Martial Arts Games looms (due to begin September 17) a final big push is underway to commission new construction, so there are large numbers of changes in the city every week. In addition to GPS traces on my Garmin Nuvi, I collected imagery using Mapillary and am presently uploading it. There is also a new headquarters building for Rysgal Bank, plus two buildings flanking that building that include a shopping center and supermarket. I mapped them, too, along with the alleys and parking lot serving them.
After a short break I put in another couple of hours driving. I buzzed up to Choganly to collect house numbers in the new development that was commissioned last week, plus finished off the search for street names in Gämi, at least for now--there are a few streets with no signs at all on them, so they will have to wait. I also checked out the new apartment buildings in Anew and added the alleys behind them, now that they have been occupied. I finished with a run down Kulyyew to collect GPS traces on the newly opened frontage roads between Bitarap and Baba Annanow. All in all it was a productive Saturday. The Mapillary upload will take a while.
The mystery building in the middle of Täze Köşi now has a sign, Saglyk Öýi, which identifies it as a clinic (what in Russian is called a поликлиника or in English an outpatient clinic). One more puzzle solved!
I thought I would use the user diary as a means of introducing myself and my research activities. I am a Research Fellow in the Nottingham Geospatial Institute at the University of Nottingham interested in participation biases in geospatial crowdsourced projects such as OSM and other Volunteered Geographical Information (VGI) projects. I am also interested more broadly in biases in citizen science. My current research project is concerned with the way in which participation biases in OSM may potentially affect the usability of the data that is collected and subsequently what is available to location based service providers which use OSM as their primary geographical database.
It is my belief that a better understanding of participation biases in VGI can give us improved potential to contribute to the future sustainable planning of our urban environments and improve services in rural communities.
Having said this, my diary entry here is also an opportunity to set the scene for those of you who may be interested in getting involved in this work through participating in a survey which I will soon be publishing online.
My proposed survey will be aimed at collecting some brief demographic information about the OSM contributors who respond. I then intend to perform an analysis of the OSM database to try to identify differences between the activities and contributing behaviours of male and female contributors to OSM. This is of major interest to me. I hope that the results will enable me to make some important conclusions and observations about current VGI contribution practices and make useful and meaningful recommendations back to the OSM community and other crowdsourced data stakeholders around gender issues in participation. A key part of the dissemination of my research results will be making the outcomes of the work available to the OSM community via my OSM diary, the mailing list and hopefully an open-access journal paper.
I am hoping that many of you will be interested in the study, sufficiently so to take part! I am interested in the activities and behaviours of both male and female contributors and would encourage as many users as possible to participate. Identifying patterns of activity in the OSM database, based on which type of users contribute which type of information, could work to consider how to improve gender specific participation.
As soon as the survey is available I will publish it here as well as disseminate it through the OSM mailing system.
In the meantime, please don’t hesitate to contact me through the OSM messaging system if you wish to learn more about the survey or research project in general. Thank you for reading this far and I will post again with a link to the survey when it is open.
I can't believe I've been walking past this construction site and now new roundabout for about two months, and it only just occurred to me this morning that I should update the map!
Anyway, done now.
I began working with OSM in 2007 following my retirement from a life-long career in cartography, which I loved. I purchased a Garmin eTrex Legend and loaded it with an .img file from http://garmin.openstreetmap.nl/. I proceeded to walk and record the streets of Henley-on-Thames and its neighbouring villages for several years - they were poorly represented in OSM, then - and learnt how to digitise and upload subsequential data. I turned my attention to countryside walking, a long-standing love. I focused on the Chiltern Way and its extensions for two years, covering it all south of the M40. I was able to create worthwhile relations in JOSM.
An extremely fortunate occurrence led to my discovery of Locus Map a couple of years ago that, with its faithful rendering of maps and wealth of features, was a transformation. Installed on my Android 'phone with OSM mapping from OpenAndroMaps and Elevate themes from Tobias, then Voluntary UK from John Percy raised my involvement and enjoyment to a whole new level. It is a brilliant combination for working in the field. I felt encouraged to walk the countryside much more, using http://www.petes-walks.co.uk/ and http://fancyfreewalks.org/Chilterns.html with a great deal of pleasure. I came to recognise, however, there were paths in my immediate area I had not walked in my thirty-odd years here. My interest turned to them, which ignited my interest in Public Rights of Way (PRoW). I tasked myself with walking every PRoW, parish by parish, in my area of South Oxfordshire. The County Council offers a download of all of its PRoWs in MapInfo .tab format. I have used MapInfo Professional for many years and was able to create a table of PRoWs for my area by parish with the help of Ordnance Survey's parish-level boundaries in Boundary-Line, adding PRoW references as recommended in Robert Whittaker's http://wiki.openstreetmap.org/wiki/User:Rjw62/PRoW_Table, plus Chiltern Society references, courtesy of Nick Moon. I find QGIS very difficult to master, but it has proved an excellent means of converting .tab files to .kml. I have discovered .kml files are better than .gpx files in Locus Map because the column entries of the table can be seen fully. Robert Whittaker has created a reference, http://robert.mathmos.net/osm/prow/progress/, that, fortunately for me, contains my area. This has proved immensely valuable in highlighting errors in and omissions of PRoWs and their tags, using Overpass Turbo. Armed with this information, I can walk and check the parishes fully. I add/amend information and upload data using the offline editor, JOSM, which goes from strength to strength in my opinion. I have come to Vespucci a second time and respect it now as a very good reference source in the field. The benefits are twofold: my walks bring me a sense of purpose and newfound satisfaction and OSM finds itself with better and more complete information.
Niedawno z ciekawości przeglądałem ten rejon Arktyki, zauważyłem nie pasujące ścieżki GPS do widniejącej linii brzegu, na początku myślałem iż jest to ślad z dopływających statków czy łódek. Baza ta jest bardzo często odwiedzana przez turystów jak i załogi przepływających statków. Jednak postanowiłem sprawdzić czy przypadkiem obiekty nie są umieszczone "na oko". Jak się okazało mapa Bing jest tak złej jakości iż na fotografii nie widać zarówno dobrego odwzorowania linii brzegowej jak i żadnego z budynków. Obecne budynki zostały natrasowane na podstawie dostępnej mapy w JPG, mocno nie aktualnej. Postanowiłem poszukać danych geologicznych czy też pomiarów geodetów z tego rejonu. Natknąłem się na pracę badawczą: "Geodezyjne prace pomiarowo-badawcze wykonane przez Wydział Geodezji i Kartografii Politechniki Warszawskiej w ramach XXXIX Polskiej Wyprawy Antarktycznej na Wyspie Króla Jerzego". Kierownik pracy: dr inż. Marcin Rajner, Wykonawcy: dr inż. Krzysztof Bakuła, dr inż. Marcin Rajner, mgr inż. Sławomir Łapiński, mgr inż. Maria Kowalska, mgr inż. Mariusz Pasik. Jak się okazało, praca badawcza zawiera liczne dane GPS oparte o wyniki z wysokiej jakości aparatury pomiarowej.
Jako punkt nawiązania osnowy do globalnego układu odniesień wybrano zastabilizowany na betonowym słupie Punkt Jasnorzewskiego (JAS1), na którym w przeszłości prowadzono obserwacje astronomiczne (Rys. 4). Jego pozycję określono w oparciu o dwufazowe statyczne obserwacje GNSS zarejestrowane odbiornikiem Topcon HiPer Pro w interwale 30-sekundowym w dniu 14.03.2015 r. w trakcie 12-godzinnej sesji pomiarowej. ( strona 6 publikacji).
Poprzez plugin JOSM narzędzie Lat/Lon naniosłem dane kilku punktów dzięki którym poprawnie określiłem położenie najważniejszych obiektów.
- Punkt Lat2 (strona 13 publikacji) 62o 09’ 29.20219’’S, 58o 27’ 57.60892’’W
- Maszt meteorologicznej stacji pomiarowej 62 09 33.860158 S, 58 28 05.884617 W
- Środek krzyża mogiły Włodzimierza Puchalskiego 62 09 48.551369 S, 58 28 09.525487 W
To pozwoliło mi ustalić iż obiektyw OSM wymagają przesunięcia o ponad 20m na północ i około 50m na zachód. Po przesunięciu obiektów ślady GPS zaczęły pasować do ścieżki wzdłuż wybrzeża oraz dookoła latarni morskiej. Teraz trzeba poczekać na update linii brzegowej gdyż jak widać po zmianie położenia obiektów widoczna rozbieżność. Oraz zbieżność GPS po edycji: Jak widać pozostała również kwestia naniesienia poprawnych nazw obiektów, torfowisko - mszarnik jest pod nazwą "Ogrody Jasnorzewskiego" jeziorka nie mają nazw, były błędnie opisane. Budynki nazwane zgodnie z informacją dostępną w Internecie. Poprzez postępującą erozję jak podają badacze an Stacji Arctowski, zmieniła się an tyle iż w najwyższym stanie jest o niemal metr od głównego budynku bazy.
Budynki natrasowane dzięki danym skanów laserowych z publikacji oraz mapom dostępnym w Internecie jak i fotografiom bazy.