Re: [OSM-talk] How to teach novices about optimal changeset size?

2018-01-18 Thread Michael Collinson
Hi Micah, I think you came up with a good answer to your conundrum in an earlier post in this thread: Don't explain what an optimal changeset IS, explain what it is NOT: Something like: "It helps other contributors understand your edits if you group what you are doing in a local area into o

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Paul Norman
On 1/17/2018 9:14 PM, Oleksiy Muzalyev wrote: What can I as a map editor do to keep these data files to a reasonable size without compromising  data quality? I mean in the sense, - take care of the pennies and the pounds will take care of themselves? I could think of the following three appr

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Andrew Hain
Or a mass change from Name=Untitled Polygon (wasteful but not wrong) to name=Untitled Polygon. -- Andrew From: Mark Wagner Sent: 18 January 2018 19:07:20 To: talk@openstreetmap.org Subject: Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonabl

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Oleksiy Muzalyev
On 18.01.2018 20:07, Mark Wagner wrote: On Thu, 18 Jan 2018 19:44:47 +0100 Oleksiy Muzalyev wrote: Imre, It is very good and surprising idea. I discovered on the page "Error categories" a tool https://www.keepright.at/ with the help of which I found already dozens obviously misspelled tags.

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Mark Wagner
On Thu, 18 Jan 2018 19:44:47 +0100 Oleksiy Muzalyev wrote: > Imre, > > It is very good and surprising idea. > > I discovered on the page "Error categories" a tool > https://www.keepright.at/ with the help of which I found already > dozens obviously misspelled tags. It functions quite intuitive

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Oleksiy Muzalyev
Imre, It is very good and surprising idea. I discovered on the page "Error categories" a tool https://www.keepright.at/ with the help of which I found already dozens obviously misspelled tags. It functions quite intuitively, just select "misspelled tags" check box and move the map to an area

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Imre Samu
>What can I as a map editor do to keep these data files to a reasonable size without compromising data quality? According to the "Lean thinking" ( https://en.wikipedia.org/wiki/Lean_thinking ) we should focus on " eliminating waste" Waste is: * Any polygon or tagging errors ( because we can't u

Re: [OSM-talk] How to teach novices about optimal changeset size?

2018-01-18 Thread althio
I looked for similar issues and apparently it was already discussed, considered back and forth and modified in iD. https://github.com/openstreetmap/iD/issues/703 https://github.com/openstreetmap/iD/issues/1598 https://github.com/openstreetmap/iD/issues/2251#issuecomment-180469055 I don't know the

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread john whelan
source=Bing ad source=bing aren't the same when it comes to data compression. So getting a little more consistency in the tags would help. Not so much the .osm format but certainly the compressed formats. Cheerio John On 18 January 2018 at 06:28, Martin Koppenhoefer wrote: > 2018-01-18 12:01 G

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Martin Koppenhoefer
2018-01-18 12:01 GMT+01:00 Oleksiy Muzalyev : > > > You make sound 1.7% as not much, however, in say civil aviation or > maritime industries, consistent 1.7% of fuel efficiency increase would be a > breakthrough. > > I do not suggest, speaking figuratively, not breathing to save air. On the > cont

Re: [OSM-talk] place=hamlet in cities

2018-01-18 Thread Dave F
On 18/01/2018 00:34, Mike N wrote: On 1/17/2018 6:53 PM, Dave F wrote: Have you been in contact with the two contributors to see if they can revoke/reupload? I presume it came from a database. If it's still available it can be amended as required. At this point it would be much better to j

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Komяpa
Hi, Please don't try to save on keeping data in text format, this is a path to removing source= tags and starting to use abbreviations in name for the sake of file size, ignoring the fact that each object has much longer iso8601 timestamp attached to it. Use proper format, like .osm.pbf, that emp

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Oleksiy Muzalyev
On 18.01.18 06:58, Mark Wagner wrote: On Thu, 18 Jan 2018 06:14:17 +0100 Oleksiy Muzalyev wrote: Good morning, I started to experiment with the OSM data [1] on a local computer, and I begin to realize how big these data files are. It takes quite a while to load into the local database just th

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Oleksiy Muzalyev
On 18.01.18 10:01, Martin Koppenhoefer wrote: 2018-01-18 6:14 GMT+01:00 Oleksiy Muzalyev mailto:oleksiy.muzal...@bluewin.ch>>: - deleting unnecessary nodes from a way (Shift-Y in JOSM) with consequent verification of its geometry; please do not use SHIFT+y (simplify way / DouglasPe

[OSM-talk] Invitation to Geo4All Webinar Fri Jan 19 - Get to know the YouthMappers

2018-01-18 Thread Suchith Anand
Dear colleagues, Reminder of tomorrow's GeoForAll webinar on YouthMappers. Details below. I thank University of Colorado for hosting GeoForAll webinars. All welcome. Best wishes, Suchith From: GeoForAll on behalf of Moreno-sanchez, Rafael Sent: 12 January 20

Re: [OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?

2018-01-18 Thread Martin Koppenhoefer
2018-01-18 6:14 GMT+01:00 Oleksiy Muzalyev : > > - deleting unnecessary nodes from a way (Shift-Y in JOSM) with consequent > verification of its geometry; please do not use SHIFT+y (simplify way / DouglasPeucker) because it doesn't know about the actual geometry, in particular sharp bends or c