Re: [OSM-talk] openstreetmap-carto upgrade, new features, interesting issues
Hi Any changes to runways and taxiways? These seem to have an issue at the moment. Hard to tell at a glance due to cached tiles and rendering ques. But at least they were not rendered at zoom 15 at one recent point in time. best regards -gorm * Adjusting zoom levels where features are displayed to be more consistent ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] openstreetmap-carto upgrade, new features, interesting issues
On 7 September 2014 13:51, Gorm E. Johnsen osml...@gorm.cc wrote: Any changes to runways and taxiways? These seem to have an issue at the moment. Hard to tell at a glance due to cached tiles and rendering ques. But at least they were not rendered at zoom 15 at one recent point in time. There is indeed an issue with aeroways, which are currently not rendered when tagged as ways: https://github.com/gravitystorm/openstreetmap-carto/issues/927 A solution has already been written, but it hasn't been accepted yet: https://github.com/gravitystorm/openstreetmap-carto/pull/928 We hope to roll out the solution as soon as possible. -- Matthijs ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] openstreetmap-carto upgrade, new features, interesting issues
After a delay for hardware reasons (a drive having issues in a rendering server), the Standard stylesheet on OpenStreetMap.org has been upgraded to v2.20.0 of openstreetmap-carto. As always, a full list of changes can be found at github, via https://github.com/gravitystorm/openstreetmap-carto/compare/v2.18.0...v2.20.0 Significant changes include * Splitting ref tags to render refs as multi-line shields. This rendering is probably the best we can do until Mapnik 3 becomes common (#750) * Rendering crossroad names, a feature common in parts of Asia (#813) * Steps to fix the cyan from small water bodies at low zoom. This should also stop over-representing water at low zooms. (#878) * Migrating the last of the issues from the old style over from trac * Adjusting zoom levels where features are displayed to be more consistent * Improved ordering of POIs (#860) * Bugfixes A couple more interesting issues open include * Ways to move away from the .mml format. We are hitting limitations with the JSON layers file causiung difficult merge conflicts, as well as generally being a pain to edit, and are looking at alternatives: https://github.com/gravitystorm/openstreetmap-carto/issues/711 * Dealing with broken boundaries where the ways lack admin_level and boundary tags. Worldwide coverage is reasonable, but some countries are missing a lot of data, principally Poland, Azerbaijan, Uganda, and some untouched TIGER data: https://github.com/gravitystorm/openstreetmap-carto/issues/344#issuecomment-49535342 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] openstreetmap-carto upgrade, new features, interesting issues
Thanks Paul and to all those that are working on this. Clifford On Sat, Sep 6, 2014 at 11:57 AM, Paul Norman penor...@mac.com wrote: After a delay for hardware reasons (a drive having issues in a rendering server), the Standard stylesheet on OpenStreetMap.org has been upgraded to v2.20.0 of openstreetmap-carto. As always, a full list of changes can be found at github, via https://github.com/gravitystorm/openstreetmap- carto/compare/v2.18.0...v2.20.0 Significant changes include * Splitting ref tags to render refs as multi-line shields. This rendering is probably the best we can do until Mapnik 3 becomes common (#750) * Rendering crossroad names, a feature common in parts of Asia (#813) * Steps to fix the cyan from small water bodies at low zoom. This should also stop over-representing water at low zooms. (#878) * Migrating the last of the issues from the old style over from trac * Adjusting zoom levels where features are displayed to be more consistent * Improved ordering of POIs (#860) * Bugfixes A couple more interesting issues open include * Ways to move away from the .mml format. We are hitting limitations with the JSON layers file causiung difficult merge conflicts, as well as generally being a pain to edit, and are looking at alternatives: https://github.com/gravitystorm/openstreetmap-carto/issues/711 * Dealing with broken boundaries where the ways lack admin_level and boundary tags. Worldwide coverage is reasonable, but some countries are missing a lot of data, principally Poland, Azerbaijan, Uganda, and some untouched TIGER data: https://github.com/gravitystorm/openstreetmap- carto/issues/344#issuecomment-49535342 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
