[OSM-dev] OpenStreetMap Carto release v2.41.0

[Paul Norman]

Dear all,

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

Changes include
* More consistent fonts for POI labels
* Less saturated stadiums
* Rendering obelisks and dog parks
* An updated list of font packages
* Cleaning up the font list
* Rewriting the road colours script for easier changes
* Various bug fixes

Thanks to all the contributors, including jdhoek, a new contributor.

For a full list of commits, see
https://github.com/gravitystorm/openstreetmap-carto/compare/v2.40.0...v2.41.0

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

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev-fr] Serveur de tuiles du cadastre

[Emmanuel Amador]

Merci !

2016-07-13 13:33 GMT+02:00 Frédéric Rodrigo :

> Le 13/07/2016 à 10:25, Emmanuel Amador a écrit :
>
>> Bonjour,
>> J'ai l'impression que le serveur proxy de tuiles du cadastre avec les
>> caractères joker est down depuis hier après midi.
>> les WMS du cadastre (testés sur quelques communes) semblent fonctionner.
>>
>
> C'est reparti.
>
>
>
> ___
> dev-fr mailing list
> dev-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev-fr
>



-- 
Flickr: http://www.flickr.com/photos/emmanuelamador/
___
dev-fr mailing list
dev-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev-fr

Re: [OSM-dev] Taginfo files from osm2pgsql style files

[Paul Norman]

On 7/13/2016 2:11 AM, Sven Geggus wrote:

Hm, looks like this does not make that much sense in case of a hstore-only
database like the one I am using in the german style setup.


Yes, I designed it for the defaults. If you add hstore options any tag 
can be
used and there's no way to indicate that a taginfo project uses all 
tags.It's

also not useful to say a project uses every possible tag.


One should at least pass the "nocolumn" entries to reflect, that these are
considered important tags. Not adding a column does not make them unused.


I considered adding delete, phstore, and nocolumn but decided against it.


I think the tool which will generate taginfo json should actually be
added to node-carto rarther than osm2pgsql.


I'm not adding it to osm2pgsql because it's very specialized. It's not a
tool for Mapnik styles or CartoCSS so it doesn't belong in node-carto.

Generating taginfo project JSON for a style is a much harder problem
andI don't think it's possible because tags are transformed when
turned into PostgreSQL columns, then again transformed by Mapnik layer
SQL queries, then some values can be used in the Mapnik XML or CartoCSS.[1]

I am working on generation of Taginfo project JSON for an osm2pgsql
multi-backend style[2] which is hard but might be possible.

[1]: 
https://github.com/gravitystorm/openstreetmap-carto/issues/961#issuecomment-56249411

[2]: https://github.com/ClearTables/ClearTables/issues/42

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev-fr] Serveur de tuiles du cadastre

[didier2020]

il y a aussi osm108 :
http://munin.openstreetmap.fr/osm-day.html

Le mercredi 13 juillet 2016 à 10:25 +0200, Emmanuel Amador a écrit : 
> Bonjour,
> J'ai l'impression que le serveur proxy de tuiles du cadastre avec les 
> caractères joker est down depuis hier après midi.
> les WMS du cadastre (testés sur quelques communes) semblent fonctionner.
> 
> 
> 
> ___
> dev-fr mailing list
> dev-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev-fr



___
dev-fr mailing list
dev-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev-fr

Re: [OSM-dev] Taginfo files from osm2pgsql style files

[Sven Geggus]

Paul Norman  wrote:

> It's not the most useful utility but there's a chance it might be useful 
> for someone else.

Hm, looks like this does not make that much sense in case of a hstore-only
database like the one I am using in the german style setup.

One should at least pass the "nocolumn" entries to reflect, that these are
considered important tags. Not adding a column does not make them unused.

I think the tool which will generate taginfo json should actually be
added to node-carto rarther than osm2pgsql.

Sven

-- 
"Thinking of using NT for your critical apps?
  Isn't there enough suffering in the world?"
   (Advertisement of Sun Microsystems in Wall Street Journal)
/me is giggls@ircnet, http://sven.gegg.us/ on the Web

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Modeling OSM sidewalk data

[Oleksiy Muzalyev]

On 12.07.2016 11:24, Martin Koppenhoefer wrote:

Il giorno 12 lug 2016, alle ore 11:15, Komяpa  ha scritto:

Both ways are only applicable to cities with blocky structure.
In ex-USSR, architecture of cities is different, and footways / sidewalks graph 
is more complicated than a replica of roads for cars, so all the sidewalks have 
to be drawn separately.


There are sidewalks (alongside roads) and other footpaths, just like everywhere 
else (but in different proportions). You can decide to draw the sidewalks 
separately or not (like anywhere else), while you have in any case to draw the 
independent footways with their own geometry.

cheers,
Martin

To understand an architecture of a city, especially of a sidewalks 
system, we should realize that it was formed to a large degree by the 
auto industry lobbying [1]. Obviously, in North America and Western 
Europe this process began several decades earlier than in Eastern 
Europe, so sidewalks and footpaths system is indeed somewhat different.



However, an emerging global trend of Walkable Development is starting to 
transform cities once again [2].



[1] "Creeps and Weirdos: the auto industry agenda for keeping you on 
four wheels"


http://www.preventioninstitute.org/about-us/lp/800-creeps-and-weirdos-the-auto-industry-agenda-for-keeping-you-on-four-wheels.html

[2] KC Conspiracy Theorists: Walkable Development Will “Devastate” Auto 
Giants


http://usa.streetsblog.org/2016/05/24/kc-conspiracy-theorists-walkable-development-will-devastate-auto-giants/


Best regards,

Oleksiy



___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Taginfo files from osm2pgsql style files

[Paul Norman]

Taginfo allows projects to define a list of tags they use, which then 
appear in http://taginfo.openstreetmap.org/projects. Osm2pgsql style 
files define a list of tag keys that are used by osm2pgsql, if the keys 
are for nodes, ways, or both, and if the keys cause an object to be an area.


I wrote some code to turn style files into taginfo project json: 
https://github.com/osmlab/osm2pgsql_taginfo


Any project using osm2pgsql with default settings is using a subset of 
those tags.


It's not the most useful utility but there's a chance it might be useful 
for someone else.


___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Modeling OSM sidewalk data

[Paul Norman]

On 7/12/2016 3:44 AM, Andy Townsend wrote:

On 12/07/2016 08:42, Paul Norman wrote:

Rather than having sidewalk data available in a column, I instead with 
a different highway value for "this road has a usable sidewalk".  We 
already have a plethora of highway values, so the extra work to 
support isn't high, and has the advantage that you don't need to mess 
about with the schema (though you do need to reload the database) if 
anything changes:


https://github.com/SomeoneElseOSM/SomeoneElse-style/blob/master/style.lua#L258 



Don't you quickly start needing to have many many values for your 
highway column as you combine sidewalks, link status, cycleways, etc?


For me a sidewalk column is much easier to do than expand the highway 
class values and it avoids users downstream of me having to deal with 
sidewalks if they're not using them in their analysis or rendering.


My initial goal was to be able to render sidewalks on unclassified and 
tertiary roads.  Note that there are more values in that list than 
you're probably expecting - that was what was found to be in the data 
when I looked locally. 


I also see you're treating cycleways as sidewalks. I'm planning on 
handling them separately, which is another reason I'm using more columns.


From the readme of https://github.com/ClearTables/ClearTables it 
sounds like you're trying to process OSM data as it actually exists, 
not "as it ought to be tagged", which means you might have to do 
something "clever" to detect poorly mapped examples like the one 
above, perhaps based on proximity.  I'd be interested to see what you 
come up with...


I'm dealing with "tagging as it exists", which is slightly different 
than "data as it exists", so I don't have to worry about data errors 
like those disconnected ways. This is partially due to technical 
constraints, but even without them I'm not sure if I'd handle that case.


It's also going to a PostGIS database so there's no notion of if two 
linestrings are connected, only if they're touching.


___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Modeling OSM sidewalk data

[Paul Norman]

On 7/12/2016 2:15 AM, Komяpa wrote:


Both ways are only applicable to cities with blocky structure.
In ex-USSR, architecture of cities is different, and footways / 
sidewalks graph is more complicated than a replica of roads for cars, 
so all the sidewalks have to be drawn separately.


Yes, I should of been clearer, sidewalks in this context are highways 
tagged with a sidewalk=* tag.


It does bring up the question of how to handle something like 
highway=footway sidewalk=right - a footway with a sidewalk.


___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev