De nuevo, depende mucho de qué dato s tenés y qué licencia tienen. Es un tema al que se le presta mucha atención; es el motivo por el cual por ejemplo no se pueden tracear datos a partir de las imágenes satelitales de google.

Googlestreetmaps? Estás mezclando cosas… :(

Si tenés datos que has obtenido de alguna forma y que pueden agregados a Open Steet Map, habría que ver primero qué licencia tienen esos datos y si son compatibles con los de OSM y sus usos.

However JOSM has a very useful “Download from Overpass API” feature

Also, what’s the name of the plugin who provides this?

What about just extending a previously existing relation? Should we just remove the filter in the second line? Another thing very common in Europe is very long rivers that go through several countries, hence having different names. The most clear example, the Danube, has all these names:

• Danube
• Donau
• Donau - Dunaj
• Duna
• Duna / Dunaj
• Dunaj
• Dunărea
• Dunărea - Дунав
• Dunav
• Дунав
• Дунай

Hola Ivana, bienvenida. Sólo un detalle: OSM no es una herramienta para editar mapas, es un proyecto que busca recopilar información necesaria para producir mapas. Para ello hay varios editores que pueden modificar dicha info; cuando haces una modificación, ésta queda registrada y se propaga a todos aquellos que usan los datos. Espero haber aclarado un poco el verdadero objetivo del proyecto.

It’s very nice, but I noticed that the colored border for one way streets are on the left side of the street, which looks weird to me. Probably a centered version? Is there a tag for left_or_right hand driving in OSM?

Another thing that makes the style somewhat unreadable on terms of roads is the pastel colors used to draw them. That’s why trunks get confused with parks and motorways with rivers, and that’s what lead me to do my own style and rendering: trying to use the standard tiles for navigation in my phone, in my car, in broad daylight, with sunglasses; or at night, was unfortunately bare useful.

Your approach essentially has two major problems:

• The USGS 1 arc second files contain bad quality void fill in some tiles that would need to be detected and removed for good quality results.
• The void filled 3 arc seconds data from the USGS/NGA vary strongly in quality of the void fill, in Europe they mostly just interpolate (slightly better than your gdal_fillnodata attempt but essentially similar).

I agree with this; they’re quite evident when you see the hillshading layer.

You can see that for example in your final image where the valley at the bottom appears dammed near Mollières.

If by dammed you mean that smooth looking slope, yes, of course, I’m using less accurate data to fill that void. What I’m saying that this is the better I get from what I have.

Here for comparison a rendering of my current basic processing in that area

I would like to know which data are you using. I downloaded deFerrantis 1 arc for that region (http://www.viewfinderpanoramas.org/dem1/N44E007.zip) and indeed they look good in this region, but if you check the plains to the NE, you’ll see not nice terracing, like the one I showed in my post. There are also several vertical and horizontal ‘cuts’. Just run gdaldem hillshade on it to see what I mean.

I prefer to balance a bit of accuracy for time saved (again, I’m not a professional cartographer like you, this is mostly for having fun… and useful offline maps in my phone) and better looking plains.

with OSM lakes flattened.

Well I don’t need this, as I’m drawing the lakes on top of the terrain anyways. See:

http://grulicueva.homenet.org/~mdione/Elevation/#13/44.1810/7.1582

(This is not the definite map; in that one, slope shades are too dark and confusing).