Hi,

Many of the municiapalities (major exceptions being Prishtina still only partially covered, Peja, Prizren, Podujeva) have put road names in the state geoportal.

Please help put these road names in the OSM,

See geoportal here http://geoportal.rks-gov.net/en/search?municipalityId=19

Under Address system activate layers Roads and Road names

Let me know if you need help.

Thanks,

Arianit

first exploration...

L'estate 2017 ha riservato una gradita stampa per tutti gli appassionati di OpenStreetMap: è stata pubblicata la nuova mappa turistica del comune di Albisola Superiore.

Commissionata dall'Ufficio Turismo del Comune è stata realizzata grazie al contributo di Albisola Servizi e Ideal Service ed è distribuita presso l'Ufficio Informazioni Turistiche. E' stata stampata in oltre 10.000 copie con dimensioni di cm 48 * 33 su due lati. Il lato principale rappresenta la città rivierasca con un piccolo riquadro che indivdua la frazione di Ellera situata nell'entroterra. Attraverso un legenda sono indicate le principali attrative turistiche e il corretto posizionamento dei parcheggi a pagamento gestiti da Albisola Servizi e l'Isola Ecologica e il Centro di Raccolta gestiti da Ideal Service. In basso al centro fa bella mostra la corretta attribuzione dei dati di provenienza della mappa ovvero OpenStreetMap con la dicitura "© OpenStreetMap contributors". Il retro della mappa descrive le principali informazioni di carattere turistico, sui parcheggi e la raccolta differenziata.

I dati della mappa sono liberamente accessibili su licenza ODbL ed aggiornati ogni giorno. Infine vorrei ringraziare e citare le seguenti persone che hanno reso possibile aggiornare la mappa di Albisola Superiore:

0rener, abrondi, Alecs01, Ale_Zena_IT, AlfredoSP, andreacelle, Andrea Musuruane, Anonix35, AnyFile, apetro, aytfadc, blastg, Bobuzzo, bubix, bvivi, castagnola, corfede, David Paleino, Davlak, daxxx1968, deprado63, dforsi, dgitto, diberton, ediyes, ericfesta, escada, favalex, fayor, filu, flavio burotto, folletto, Furry75, FvGordon, geow, ghiso983, Gigi, glaucos, GoOpti, grafite, Guidolux, gw davide, Heinz_V, jackthebest, jaimemd, KR-KRKR-KR, landfahrer, Lapp Kabel Romania, LLAQWA, lorenzoelsalsero, lucadelu, LucioGE, luschi, Marco_T, Martin Mystère, mcheck, mcheckimport, mike140, Morkosh, mttclv, Nicola Grenno, Niente0, niubii, noperante, nyuriks, Olyon, orbiter_25, Pab09, Pablo99, PeetTheEngineer, Peilscheibe, piligab, popeye, Puccia, ratrun, rockhock, sabas88, sabas-import, sbiribizio, sheg, Simone Piccardi, steko, telemaco81, user_5359, vancori, venerdi, wambacher, wheelmap_android, wild, WJtW, Yiyi (itwikipedia), yurasi.

In ultimo ma non per importanza vorrei ringraziare l'Assessore al Turismo, Luca Ottonello che ha sempre sostenuto il progetto di collaborative mapping di OpenStreetMap e che sia così da spunto anche per altre amministrazione locali.

Come sempre buon mapping a tutti!

Bubix

One of the tricks I've learned with ID editor is to try different satellite sources:

USGS Topographic Maps - may give you name of natural features.

USGS Large Scale Imagery - is low quality, but may show winter pictures, for example allowing to trace trail in a deciduous forest.

DigitalGlobe Standard Imagery - is low quality, but seems to be most up to date (20015?)

Esri World Imagery - new layer, high quality, just showed up a few days ago. Some places it is same as Bing, for some places it seemed newer.

As always, be mindful of only using sources that allow being used for OSM editing.

Hoy estuve mapeando la zona del acceso a la ciudad de Ayolas

just trying to improve the prescott region and prescott valley . .

Прочитать

Rather bleached under the Bulgarian sun scheme with hiking routes between Sv. Vlas and Elenite.

Me parece una herramienta más que valiosa. Estoy aprendiendo a utilizarla. De a poco. Hay muchas cosas por descubrir.

My Project

I was working with OpenStreetMap during the summer on the library called libosmscout. Libosmscout offers offline rendering and routing on OpenStreetMap data, and my project's aim was to expand the library by implementing an OpenGL based renderer.

My Work

Two components of the libosmscout project is my work:

• libosmscout-map-opengl is the OpenGL renderer.
• OSMScoutOpenGL is a simple demo application, that presents the usage of the OpenGL renderer.

Links to my commits, pull request, and issues:

• My commits on github can be viewed here: Commits by fannymonori.
• My pull requests can be viewed here: Pull requests by fannymonori. My work was constantly merged, rather than having one pull request at the end.
• The closed issues that were assigned to me: Closed issues by fannymonori
• A short description of the OpenGL renderer can be viewed here: libosmscout: OpenGL backend

Results

I met the objectives that were given in my proposal.

• All the four main features of the map (areas, ways, labels, and ground) are rendered correctly.
• Most of the styling options are supported
• It is cross-platform
• There's a working desktop demo application

A few screenshot of my work:

Dear all,

Today, v4.2.0 of the openstreetmap-carto stylesheet (the default stylesheet on openstreetmap.org) has been released.

Changes include:

Major changes

• Water color and default water text color are changed to be more visible
• Medium zoom level (z8-z12) rework:
  • Landuses colors are faded and some of them are visible earlier
  • Most of the man related landuses are combined into one color and more visible
  • More important roads are better legible

Changes

• Leaf type rendering in woods and forests
• Cemetery symbols are not so dense now and Muslim cemetery has its own symbol
• Rendering of amenity=ferry_terminal
• Plaque rendering is now different and moved to z19
• Rendering railway labels
• Smaller line spaces in labels
• Junction names on areas
• Area color for railway=station is the same as for railways
• Database performance tuning available for Docker
• Different patterns and all remaining icons moved to SVG
• Some documentation and code cleaning

Thanks to all the contributors for this release, including littlebtc and giggls, new contributors. Special thanks for rrzefox for testing major changes on his server.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.1.0...v4.2.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues.

You may already have it on your device and this is old news, but yesterday we pushed the release version of Vespucci 0.9.9 to the google and amazon app stores.

The release notes list most of the changes including preliminary documentation on the opening hours editor.

I would specifically like to thank Mateusz Konieczny and Holger Jeromin for beta testing (Mateusz particularly for finding a last minute issue).

0.9.9 took a long time to get to this state, mainly due to a lot of under the hood work which should make upcoming releases much easier. I'll be trying to step up the release frequency again and expect 0.9.10 including C-mode to be available by the end of the next quarter.

Per il progetto VeloQuality - Città di Rho ciclabile è stata aggiunta la pista ciclabile di Via Alessandro Volta.

I've started getting into capturing on Mapillary and have found it to be incredibly helpful for mapping on OSM. I wanted to go through my setup in case it's interesting for others.

• I prefer to capture 360 images
• I use the LG360 (R105)
• I bought two LG360 cameras off ebay, $125USD and $90USD. The LG360 is on the cheaper end of the scale compared to some of the others on the market.
• Though there is a flaw in one of the cameras I bought which is a shame as you can see the left half of the image (front camera) is blurry.

• I'm happy with the image resolution and quality. I wouldn't want it any worse though. Most of the time street signs and parking signs aren't readable, but speed limits and destination signs are.

• The LG360 is unreliable, sometimes it stops capturing, connecting to your phone can take several minutes and attempts before finally working, there can be gaps in the GPS tagging where it will use the last location for maybe 30 seconds (even though the GPS log might have data; in this case I end up using gpscorrelate, however I've found you have to play around with the time offset and even then you might get it right for the start of the trip but it will be out at the end).
• I think the battery should last for around 1hr 45min at a 2 second capture interval.
• I'm happy with the 2 second capture interval, but wouldn't want anything not supporting at least 2 seconds.

• I'm using a 64GB Micro SD card XC I U1. Photos are about 5MB so you should get around 10,000 photos or 6 hours give or take.

• I capture on my bicycle. I have a rack mounted which I attached an old broom stick I found on the side of the road to, which I then attach the Monopod to. It's all held together with Duct tape. The broom stick I'm using is light weight but does give some flex (if the camera had a built in gyro it could correct for it in software, I mean it's a 360 camera after all!).

• I use this phone mount. It's great. Very easy to attach/detach your phone, has a Silicone band to hold you phone in place (I've had my phone come out of the claw once going over a pothole, and the band ensured it didn't come out). There is this ball joint which is stiff enough that you can just change the angle of your phone and it usually stays in place. I got mine for $2.10 USD.

• Originally I used a selfie stick like this http://www.ebay.com/itm/Extendable-Handheld-Monopod-Tripod-Mount-For-GoPro-Hero-4-3-3-2-1-Intriguing/282407340369, but you need to be careful as if used a while or if you run into tree branches it will come apart. I also found it would sometimes not stay extended. Lastly there are two kinds of this selfie stick, some don't have a ridge so the camera will start turning around which means the orientation ends up being wrong.

• I upgraded to this $12.60USD Yunteng YT-188 Self Picture Monopod. It's much better it doesn't feel flimsy and it's rigid with no flex. The clamps prevent it from collapsing or rotating. The only flaw is I needed to tape up the top as it was loose.

This pole is longer than the previous one. All the 360 photos on my Mapillary profile to date have been with the shorter pole. I'm still working out the best height to use. The higher the camera then the less I obstruct the view, but the more tree branches, signs etc I run into.

The main problem at the moment is it's a real pain uploading to Mapillary when you have something like 10GB a day and can only do around 90KB/second. I end up using rsync to a remote server as rsync doesn't mind being interrupted a hundred times and it's easy to limit the bandwidth. I also use lepton to compress the JPEGs further. WebP would be even better! The scripts I use for this are at https://github.com/andrewharvey/lg360-mapillary-helpers

If you get lucky on ebay parts are around $105 USD + duck tape, a bike, a phone and a Micro SD card.

Aunque ya llevo un tiempo editando un poco por instinto desde hace tiempo (no conozco muy bien como funciona todo), desde hoy me hago usuario del wiki.

Location

Peter Mooney, Frank Ostermann and I first met at a workshop about Crowdsourcing in National Mapping in Leuven. There were people from national mapping agencies from around Europe, who came to talk about their experience with working with crowdsourcing. I talked about the crowdsourcer’s perspective. It was a bit frustrating to be the only OSM-community representative, as I know that we’re defined by many points of views. With Peter and Frank the conversation soon went to the science aspect of that same relation. Professional scientists find it hard to talk to OSM, and OSM people find it hard to talk to scientists. We believe we can do better. And we want to do something about it. Rather than just start doing stuff, we want to invite you to discuss this with us. Below is our line of thinking, written by the three of us together.

Problem

This initiative is based on our observations that there is room for improvement in the interactions between the academic research and OSM communities. On the one hand, the OSM community often learns late (or never) about research results generated from academic research on OSM. For example, the OSM wiki pages on academic research are likely not to be up-to-date (with the majority of entries from the years 2010/2011, and little after 2014), but nevertheless quite cluttered, containing many non-English entries, and therefore difficult to search effectively. On the other hand, the academic research community has often little information on what are important concerns for the OSM community. As a result, very often academic research is carried out on OSM in complete isolation from the OSM community itself. There has been substantial interest from the academic research community into OSM since at least 2006/2007. This interest shows no signs of abating. One must acknowledge that the incredible success story of OSM is an intriguing source of potential research for academics.

Objective:

Our initiative has therefore two main objectives:

1. Improve communication structurally and in a sustainable way between both the OSM community and the academic research community. This includes communication about research needs within OSM, communication of research results from the academic community to the OSM community, and shared goals and interests.
2. Learn about the interests and needs of the OSM community to enable co-created research

Approach:

Our approach has two stages: First, this blog post aims to deliver some basic information on what we plan, why we want to go forward with it, and how we hope to reach our objectives. Further, it aims to gather feedback from the OSM community through comments, and invites members of the OSM community to contribute, and propose ideas for research studies. As a second stage, we envision a more structured survey that proposes research ideas based on suggestions from this blog post’s comments , e.g. through voting or multiple-choice questions, that offers some open questions to allow for free-form comments, and asks for ideas on how to keep any wiki pages on research ideas and results more up-to-date. However, we are open for suggestions for different approaches!

Outcomes:

We aim for the following outcomes, to be shared with both academic research and OSM communities:

1. A short report or evaluation of the procedure itself.
2. Publish the highest voted or most often requested research ideas on the OSM community pages.
3. Establish a mechanism that allows the update of these ideas and feedback any results, e.g. through finding champions or supporters from both the OSM and the academic research communities, or linking with discussion board on OSM research.

Some more info on why are doing this: Academics/Researchers must write papers and do research as a key component of their ‘day job’. OSM community members want to continue to make the OSM map/database even better, map new things, write OSM software, etc. There surely exists some research problems that the OSM community is interested in investigating - these research problems could also be of great interest to the Academic/Research community. This provides great potential for a collaborative platform between Academia and the OSM community to work on problems of mutual interest. Moreover it provides the potential for a new form of collaboration where the results of the research are directed back to the OSM community for discussion and debate BEFORE they are published in academic journals or conferences. We believe that this vision of co-created research between the two communities will be of interest to everyone involved.

Joost Schouppe, OSM Belgium Frank Ostermann, ITC, Faculty of Geo-Information Science and Earth Observation, University of Twente, The Netherlands Peter Mooney, Dept of Computer Science, Maynooth University, Ireland.

Note: this post was announced on the talk mailing list here

兵庫県にぽつんと枚方高槻線っていう橋が描かれている https://www.openstreetmap.org/way/374332108#map=19/34.81508/135.41507 多分間違いやねんけど、遠くて確認できへん 万が一ほんまにそういう橋なんかも… 近所の方、ご確認下さい〜

I noticed that the wiki describes City, Town, Village and Locality to be named based on a determined size.

Example: Use place=town to identify an important urban centre that is larger than a place=village, smaller than a place=city, and not a place=suburb. Towns normally have a good range of shops and facilities which are used by people from nearby villages.

My suggestion is that includes the local legal/administrative size denomination. Many countries have a legal/administrative approved size for naming for City, Town, Village, Locality.

Many new mappers will mistake similar classifications when mapping new features. For example, when I first started mapping, I would mark areas as "forest", when I meant "wood". I also marked "meadow" instead of "grass" in many places. Others confuse "footpath" and "path", "residential area" and "apartments", and "nature preserve" and "park". If OpenStreetMap could add a pop-up that would say "did you mean" followed by a similar tag to the one that the mapper just selected and a comparison of the two tags, then new mappers could more accurately map areas.