[OSM-dev] OpenStreetMap Carto release v4.16.0
Dear all, Today, v4.16.0 of the OpenStreetMap Carto stylesheet (the default stylesheet on the OSM website) has been released. Once changes are deployed on the openstreetmap.org it will take couple of days before all tiles show the new rendering. Changes include - Changing societal amenities color to less intensive - Adding rendering for natural=strait - Adding rendering for leisure=track on lines - Adding icon for amenity=vehicle_inspection - Adding icon for leisure=sports_centre + sport=swimming and leisure=swimming_area - Adding icon for tourism=gallery - Changing color for aeroway=apron in aerodromes - Moving amenity=post_box to z19+ - Moving amenity=atm to z19+ - Replacing icon for information=tactile_model - Ordering amenity_lines by layer - Small documentation and code fixes Thanks to all the contributors for this release including dryo, a new contributor|.| For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.15.0...v4.16.0 As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues -- "My method is uncertain/ It's a mess but it's working" [F. Apple] ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: JOSM developers meetup at Karlsruhe?
Standards, some people can't seem to get enough of them :-) Polyglot Op do 18 okt. 2018 om 21:16 schreef Dirk Stöcker : > On Mon, 15 Oct 2018, Vincent Privat wrote: > > >> After 1 day INTERGEO on Wednesday and at least 1 day RTCM standards > >> committee meeting on Thursday the chances are pretty low that I'll visit > >> another conference voluntarily soon. :-) > > > > It's not really a conference, it's more likely coding, talking and > drinking > > beers :) And it's not often I come to Germany ;) > > Now it is 1 day fair and 2 days standards committee and I feel like > afterwards I need a months holidays :-) > > My advice to everybody: If you get asked to participate in > standardization, RUN, as fast as possible. Don't look back! > > I wish you all fun at the meeting. > > Ciao > -- > http://www.dstoecker.eu/ (PGP key available) > >
Re: JOSM developers meetup at Karlsruhe?
On Mon, 15 Oct 2018, Vincent Privat wrote: After 1 day INTERGEO on Wednesday and at least 1 day RTCM standards committee meeting on Thursday the chances are pretty low that I'll visit another conference voluntarily soon. :-) It's not really a conference, it's more likely coding, talking and drinking beers :) And it's not often I come to Germany ;) Now it is 1 day fair and 2 days standards committee and I feel like afterwards I need a months holidays :-) My advice to everybody: If you get asked to participate in standardization, RUN, as fast as possible. Don't look back! I wish you all fun at the meeting. Ciao -- http://www.dstoecker.eu/ (PGP key available)
Re: [OSM-dev] Detect and remove sharp angle/spiky configurations on buildings
oups, Resending previous incomplete message Sandor, you are looking only at spikes. My algorithm presented in recent threads on the talk list about Building Geometries detection will also detect regular geometries that have any irregular edge ( a difference of more then 2 degrees ). It cannot distinguish valid irregular geometries, but they are in general a small numbers, and most flagged buildings correspond to imprecise building traces. regular polygons- 90, 90, 90, 90 - 90, 270, 90, 90, 90, 90 - 120 * 6 (hexagon)- 135 * 8 (octagon) refhttps://lists.openstreetmap.org/pipermail/talk/2018-August/081274.htmlhttps://lists.openstreetmap.org/pipermail/talk/2018-September/081392.html Pierre Pierre Le jeudi 18 octobre 2018 09 h 15 min 53 s HAE, SandorS a écrit : Some days ago there was a question on an OSM forum whether such algorithm exists and used by some of the OSM users. Honestly I even did not know that such an issue exists and probably I am not alone. The reason to that is either that the spiky configurations are hardly visible in maps or that robust users handle them as a special case when process tiny outgrowths in their data generalisation programs. A closer look at the issue has shown that the issue is real and rather general. Spiky configurations exist on most of the area borders, roads, roundabouts and so on, there is a huge number of them and almost all are errors. To provide strong arguments about the former statement I have made an algorithm, a simplified version of the tiny outgrowths detection and removal, and applied the corresponding program to the OSM UK buildings. The algorithm on a certain abstraction level, its use and the processing results are described in details in an article here https://drive.google.com/open?id=1MaLdnSnc454xKjn3eL95vDQKeoIW8zGU . There are around 120K spiky buildings in OSM and out of these 2834 in the UK. In addition, the paper presents many examples how the spiky buildings look before and after the correction. Also, the paper contains links to the output data of the demo/test processing and how these could be used for visual analyses. So, if interested, enjoy the paper. Regards, Sandor. Sent from Mail for Windows 10 ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Detect and remove sharp angle/spiky configurations on buildings
Sandor, you are looking only at spikes. My algorithm presented in recent threads about Building Geometries detection will also detect either rectangular, ortogonal etc. geometries that have any irregular angle ( a difference of more then 2 degrees ).Regular geometry - 90, 90, 90, 90 refhttps://lists.openstreetmap.org/pipermail/talk/2018-August/081274.htmlhttps://lists.openstreetmap.org/pipermail/talk/2018-September/081392.html Pierre Le jeudi 18 octobre 2018 09 h 15 min 53 s HAE, SandorS a écrit : Some days ago there was a question on an OSM forum whether such algorithm exists and used by some of the OSM users. Honestly I even did not know that such an issue exists and probably I am not alone. The reason to that is either that the spiky configurations are hardly visible in maps or that robust users handle them as a special case when process tiny outgrowths in their data generalisation programs. A closer look at the issue has shown that the issue is real and rather general. Spiky configurations exist on most of the area borders, roads, roundabouts and so on, there is a huge number of them and almost all are errors. To provide strong arguments about the former statement I have made an algorithm, a simplified version of the tiny outgrowths detection and removal, and applied the corresponding program to the OSM UK buildings. The algorithm on a certain abstraction level, its use and the processing results are described in details in an article here https://drive.google.com/open?id=1MaLdnSnc454xKjn3eL95vDQKeoIW8zGU . There are around 120K spiky buildings in OSM and out of these 2834 in the UK. In addition, the paper presents many examples how the spiky buildings look before and after the correction. Also, the paper contains links to the output data of the demo/test processing and how these could be used for visual analyses. So, if interested, enjoy the paper. Regards, Sandor. Sent from Mail for Windows 10 ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Detect and remove sharp angle/spiky configurations on buildings
Some days ago there was a question on an OSM forum whether such algorithm exists and used by some of the OSM users. Honestly I even did not know that such an issue exists and probably I am not alone. The reason to that is either that the spiky configurations are hardly visible in maps or that robust users handle them as a special case when process tiny outgrowths in their data generalisation programs. A closer look at the issue has shown that the issue is real and rather general. Spiky configurations exist on most of the area borders, roads, roundabouts and so on, there is a huge number of them and almost all are errors. To provide strong arguments about the former statement I have made an algorithm, a simplified version of the tiny outgrowths detection and removal, and applied the corresponding program to the OSM UK buildings. The algorithm on a certain abstraction level, its use and the processing results are described in details in an article here https://drive.google.com/open?id=1MaLdnSnc454xKjn3eL95vDQKeoIW8zGU . There are around 120K spiky buildings in OSM and out of these 2834 in the UK. In addition, the paper presents many examples how the spiky buildings look before and after the correction. Also, the paper contains links to the output data of the demo/test processing and how these could be used for visual analyses. So, if interested, enjoy the paper. Regards, Sandor. Sent from Mail for Windows 10 ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
