[OSM-dev] Taginfo files from osm2pgsql style files
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
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
Re: [OSM-dev] Taginfo files from osm2pgsql style files
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] Taginfo files from osm2pgsql style files
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
[OSM-dev] OpenStreetMap Carto release v2.41.0
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
