I came to write what ViriatoLusitano_import just wrote:

• footways are deliberate
• paths are emergent

While some renderings may consider this difference negligible, I believe that it most definitely warrants differentiated tagging.

I guess I could get over the motorways not being blue… But the lack of details (removal of buildings & residential highways) at low zoom levels disturbs me even more : the noise patterns they form talk to me very nicely and I would miss them a lot.

Kudos for the tertiaries rendered as same color but slightly wider - I believe declutters while not degrading readability.

generator:type=solar_photovoltaic_panel n’est-il pas redondant avec power=generator generator:source=solar generator:method=photovoltaic ?

To see who edits in the area you are interested in - and in your specific case to see who may be deleting objects, you might want to take a look at Whodidit: http://zverik.osm.rambler.ru/whodidit/index.html?zoom=12&lat=14.70973&lon=-17.30987&layers=BTT#

Joli spam… @vuu472

L’intérêt de Mapiliary est le partage des prises de vues: des photos prises avec OSMTracker ne sont que des notes personnelles tandis qu’un itinéraire photographié avec Mapiliary bénéficie à tous ceux qui s’y intéresseront plus tard.

Sorry for the misformated unordered lists…

Finding nearest neighbours is a question related to QGIS (or whatever is your tool of choice) rather than an Openstreetmap question… Openstreetmap provides all the data you require - all you need is a way to process it.

Here are a couple of approaches to answer your requirement: - http://www.qgistutorials.com/en/docs/find_neighbor_polygons.html - http://gis.stackexchange.com/questions/30011/qgis-polygon-layer-table-of-adjacent-polygons

I like the http://postgis.org/docs/ST_Touches.html Spatialite-based approach a lot. Here is another sample query using it : http://gis.stackexchange.com/questions/121943/how-to-use-st-touches-to-get-all-nearby-states

And if you are new to using Spatialite in QGIS: - http://docs.qgis.org/2.6/en/docs/training_manual/databases/spatialite.html - https://code.google.com/p/qspatialite/

All boundaries are boundary=administrative - what distinguishes them is admin_level, for example national borders are admin_level=2

Subnational borders are trickier because they are tagged slightly differently in each country - for example boundary=administrative shows that admin_level=4 is NUTS2 in many countries… But it is NUTS1 in Belgium.

Also, you may want to check if you really want to select all highways (highway=path ?) or if only some types (highway=primary, highway=motorway, highway=secondary etc.) are relevant.

So, how is your project going ?

Also, experiment with a small data set - download a few square kilometers using the QGIS Openstreetmap plugin and play with that until you are comfortable with the process I described… Better make mistakes with instant calculations and get immediate feedback rather than watch an hourglass for many minutes while your workstation processes such large dataset as the whole of Europe.

Get the OSM planet extract for Europe: http://download.geofabrik.de/europe-latest.osm.bz2

Load its highway ways into a QGIS layer: http://www.qgistutorials.com/en/docs/downloading_osm_data.html

Load its boundary ways into another QGIS layer. Select the national level. boundaries, drop the rest.

Select the highways that intersect boundaries (Vector>Geoprocessing Tools>Intersect)

Voilà.

Gourmet, pose ta question à François Lacombe - si quelque chose à été fait à ce sujet il est probablement au courant.

Some context: http://www.aukevisser.nl/supertankers/FPSO-FSO/id527.htm http://www.offshore-mag.com/articles/2014/05/sbm-offshore-outlines-fpso-conversion-decommissioning-program.html

I love FPSOs - that much extremely dense complex plumbing filled with dangerous stuff is pure geek excitement…

In Senegal where the mapper density is extremely low, I often stumble on the works of lonely enthusiastic novice mappers who sometimes make a hash of things with simply bad modeling - contacting them is usually the most productive course of action and they soon mend their ways… Their mistakes are part of a learning process that makes them better mappers - a system where mistakes are not possible is a system where there is no learning.

The other category of errors are ‘fat fingers’ from random iD users who inadvertently move a node some distance away from its original position - always spectacular when that node is at a crossroads and moved a kilometer from where it should be. That one might benefit from some tooling : just like JOSM, iD could validate a number of things - for instance a ‘crossing ways’ warning would catch most of those inadvertently moved nodes. Of course, such validation would have to be light enough for the web environment and pedagogical enough to guide the unsuspecting user - but focused on common errors it could be useful.

Same here - I used to consider mobile editing an experimental activity at best but having had a Galaxy S4 bestowed upon me by my employer I find that Vespucci is perfectly suitable for the occasional POI addition or tag editing while walking.

A share of that glory goes to Vespucci whose developers have definitely not stood idle since I had tried it on other devices.

However, none of that is integrated into the main service, and that is a necessity if OpenStreetMap is to attract more customers.

Openstreetmap does not have customers, it has contributors and users.

On the other hand, many Openstreetmap users do have customers.

Spam - once again cleverly disguised, but SEO spam nevertheless…

Spam !

Spam !