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 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 OpenStreetMaps".

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.

Список товаров:

• комбикорм / combined feed (выглядит так / looks like that)

• зерно / grain

Как правильно обозначать такие магазины? / How correctly to designate such shops?

Saturday

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. 🚴

Sunday

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.

https://en.wikipedia.org/wiki/Tagondaing

Tagondaing Village is located in Myanmar

Wikipedia-https://en.wikipedia.org/wiki/Tagondaing

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:

• Garmin 520 mapping
• How to install bike maps on the Garmin Edge 520

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:

• mkgmap
• osmosis

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.

Overview

My method for generating a suitable gmapsupp.img is thus:

1. Download a OSM data extract in PBF format - Geofabrik
2. Run osmosis to remove and contain only the relevant data wanted for the map.
3. Create the map using mkgmap, using the default style.
4. 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.

Detailed Process

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

Postscript

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.

(Photo on Flickr.)

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.

1. Punkt Lat2 (strona 13 publikacji) 62o 09’ 29.20219’’S, 58o 27’ 57.60892’’W
2. Maszt meteorologicznej stacji pomiarowej 62 09 33.860158 S, 58 28 05.884617 W
3. Ś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.

Since I’m on a right-to-left-languages-and-mapping kick, I recently asked a language school in Malé to translate OpenStreetMap.org into Divehi, the local language of the Maldives. After a promising start and an initial quoted price, we had a month without communication. After determining it wasn’t just a Ramadan break, I texted a phone numbers on an ad on Ewity, a Maldivian Craigslist. Almost immediately I had the first translations:

OpenStreetMap About page — green text is a possible transliteration of “OpenStreetMap”

Font issues aside, bringing OSM Divehi coverage from zero to a few hundred words was a milestone. I’ve decided to pay for another 1,101 words to be translated — this covers most of what you’d see browsing OpenStreetMap, signing up, logging in, leaving a note on the map, and making your first edit.

Why translate Divehi?

This is a good question — even in the right-to-left languages theme, there are more speakers of Arabic, Persian, and Urdu who could use a completed translation of OpenStreetMap and the iD Editor.

Disappearing Islands

The Maldives are sinking. Long before they disappear, storms will damage crops, buildings, and local landmarks, and drive people to more protected cities or even out of the country. I believe that there’s value in mapping and documenting the Maldives and Maldivian way of life as it exists today, especially on more remote islands, and using community reports to monitor areas that are changing.

Malé, Maldives, by Shahee Ilyas, via Wikipedia

Don’t Ignore Existing Volunteers

When I started working on Arabic i18n I felt out of place, as I had limited knowledge and OpenStreetMap clearly has volunteer mappers who speak Arabic fluently. Eventually I realized that fixing these issues in the source code required knowledge of CSS, Unicode, and git, too. A mapper from the Middle East, North Africa, Iran, or Pakistan might not be available to fix these issues, but translations are much more accessible.

Volunteer translators are already doing great work — for iD Editor, Persian is 79% complete, and Arabic 60% complete.

Considering how few people speak Divehi, and how little the language is visible on OpenStreetMap today, it would be less likely that native speakers would be editing, and then that one of these editors would volunteer to translate the site from scratch. Providing the first chunk of translations for the site gives us a starting point to recruit mappers, translators, and organizing NGOs.

Local Language Content

Places in the Maldives ought to have a local-language name tag, combined Divehi-English name tag, or some other system, as seen in other countries. If the map is going to include local people, places, and knowledge, English-speaking tourists can’t be the only mapmakers.

A participant in the annual Divehi Oratory competition

Comparable Open Source Translation Efforts

Arabic, Persian, and Urdu have open content on the web. They also appear on Google Translate, though translation on this level requires a human touch.

I have seen precious few websites with open source translations into Divehi. Clearly there was work on Wikimedia and Wordpress, but opening OpenStreetMap translations with a Creative Commons Zero license could be useful to new developers.

How’s it going?

Up until I got an invoice from the translator, I was pessimistic. Now that translation is happening, I feel much better about it.

The OpenStreetMap website project uses TranslateWiki and the iD Editor uses Transifex. Neither site allows me to import translations directly.

• TranslateWiki tested me with random translations before I could join an OSM team. After some confusion, I decided to ‘translate’ five statements in Spanish to their existing translations, with little or no modification. About 24 hours later a mod approved my account, and I was able to add the first Divehi translations for the About page.

• Transifex made me request to add Divehi to the iD project, which was approved. There are separate repos for the ‘presets’ and the main editor. I submitted a few translations which are not yet reviewed, so I’m not sure if they will be added or if I need to nudge them through the process.

Context and Legalese

I made a spreadsheet on Google Drive with one column of translations and one column of ‘context’, explaining when I need Edit (verb) and Edits (noun, a list of changes). Or explaining map-editing terms like “circularize” and “shape is not square-ish”.

Another example is finding a translation for ‘Agree’, for the OpenStreetMap Contributor Terms. OpenStreetMap asserts that the English version of the agreement has the final legal standing, and I can’t be sure that a translation would represent that accurately. I decided not to include the Contributor Terms in my translation, though I do plan to include the title of the page, the option buttons, and the public domain checkbox.

Template Content

I had many options on how to represent template phrases such as “{user}’s Profile” or “{user} posted about {topic} at {date}”. Should I include them in my word count? I asked the translator to do 50–100 words and then report back. He translated “number” in “{number} km” yesterday, so I tried to explain this better.

Quality Control and new NPM module

When I received my first translations, the translator asked how I would check the results. I didn’t really think about it until I was confronted with text.

• Words such as ސިނަމާ and ބޭންކު I can Google and/or Image Search and see that movie theaters and banks come up. I also check if ‘homepage’, ‘next’, ‘previous’ appear in similar places on other websites.

• I compared similar sentences for structure and subject-object-verb order.

• I found a GPL transliteration library in PHP, converted it to JS/Node, and published it on NPM with a command-line interface. Source code. This allowed me to find proper names such as ‘OpenStreetMap’ and loan words such as ‘GPS’.

To be continued…

I’m going to continue to work on both translation pages to make sure that it starts appearing on the map, then show it to the USDP office and other NGOs in the Maldives.

I know some Arabic, so I’m hopeful that I could read. Each letter contains a consonant and vowel sign. ބޭންކު is beynku. Going from right to left, ބ is b, ޭ _ is ey, ނ is n, ް_ is no-vowel, and so on.

In October I’ll be discussing right-to-left support in OpenStreetMap at the Unicode Conference. I hope to visit the Maldives sometime this year!

Remember that comment about the map being first finished when every blade of grass has been documented. Of course it was only meant to be figurative but some contributors do go to extraordinary extremes to map useless data.

Using OSMI I found this:

http://tools.geofabrik.de/osmi/?view=geometry&lon=6.96155&lat=51.66477&zoom=18&opacity=0.53&overlays=self_intersection_ways,self_intersection_points

When downloaded these ways are are tagged as barrier=line

They are the ground white lines of a tennis court: An entry from a contributor which has over 4,000 changesets to his/her credit. I know that there are no fixed set of attributes so what this contributor has done is within OSM rules but I think such data is redundant as they will never be rendered. But maybe this contributor is writing his own renderer.

So what's my problem: Well, it is that the data is not being entered without mistakes which the validation applications find. If not corrected then the users who try to clean-up the data base will be continually linked to these errors which is of course a waste of resources.

Basically it comes down to the fact that many POIs can be well enough documented with a single node or area with the applicable attributes. It would then be easier for everybody.

I don't like to delete the work of others but it give little pleasure to see redundant data like detailed water slides, etc where a single node would do the job better.

I discovered a new source of data to be added to OSM: notes.

Presumably notes are mostly created out on the field by busy bees with smartphone applications. I created a few notes to highlight areas that need a lot of work.

Helpfully, there is a way to get RSS for all notes in a given area, I will be trying that with RSS reader.

Notes, here I come. Time to go to bed.

Prawobrzeżna część Wieprzówki w sołectwie po małej korekcie. Pozostała część sołectwa też już zrobiona - drogi dojazdowe.

Dodano oznaczenia dróg: 1733K, 1734K, 1735K

https://pad.riseup.net/p/lista-tarefas-OSM-RS

With the front end design of the repository complete, I’ve been working on the backend. So far, most of the pages have been implemented, namely the homepage and the model information and search results pages.

The search page. Note that there's a single result per page, for testing.

The user page has also begun to be implemented.

The current state of the user page. Notice the presence of my avatar.

It was decided to use the PostgreSQL database, and the Django framework for quickly implementing all these pages. The database schema has also been agreed upon since the last diary entry.

The conceptual model that was decided on.

In terms of implementation of this schema into Django models, it was almost a direct conversion, except the tags: we used a HStore field for them, as suggested by pnorman on IRC. The banned_by and banned_date fields were also removed from the user, and a Ban Table was made instead.

Furthermore, since no major issues have come up, I’ve managed to add a commenting feature, so that users can comment on models, and model revisions, to serve as a beginning for editing models. Hopefully this feature will be present at the end of GSoC. I’ve also implemented the live preview, one of the most interesting parts of the project, using THREE.js so that users can see a preview of the model right in the repository, in their browsers, without explicitely downloading a file and opening it themselves. Starting off, it will just support the Wavefront OBJ format.

The current state of the model information page, showcasing the commenting feature and a model of the Eiffel Tower being displayed in the live preview.

The REST API is also progressing fairly well, most of the endpoints have been implemented, namely the info get and model get endpoints, search by latitude and longitude and the author, category and tag lookups. In the next couple weeks, I will be working on the upload model page, and the administration of the repository.

Copyright note: the Eiffel Tower model was taken from https://3dwarehouse.sketchup.com/model/98810fe9c4f57f1141ba0f9fe83c1fd/eiffel-tower, in OpenCOLLADA format, then converted with Blender to Wavefront OBJ.

Согласно http://osm.sbin.ru/stat/kz/latest/users.html Число добавленных узлов мной перевалило за сто тысяч. На это ушло 50 дней от первой моей правки в ОСМ и много движения мышкой. Наверное за год до миллиона доберусь. Надеюсь мои правки которые по Астане кому нибуть пригодятся, Особенно сильно улучшенный адресный поиск.

Плохо что я не могу видеть обратной связи от тех кому эти данные пригодились. Не знаешь пригодилось это кому нибуть. :(

Как здесь сказано http://osm.sbin.ru/stat/kz/latest/users.html Я все таки нанес более 16000 тегов addr