Re: [OSM-talk] Paper/Article about stagnation in OSM

Hi, On 31.07.2018 23:49, Frederik Ramm wrote: > I don't necessarily agree with all that's been written but I found > > http://journals.sagepub.com/doi/10.1177/2053951718790591 > > an interesting read: "The social construction of technological stasis: > The stagnating data structure in OpenStreet

Re: [OSM-talk] Paper/Article about stagnation in OSM

sent from a phone > On 4. Aug 2018, at 13:00, mmd wrote: > > Contrary to common belief, there isn't such a thing as a dedicated > "Area" object type (yet) There are multipoligon relations, which are clearly areas by definition, and there is the area key, if set on a way, it is unambiguously

Re: [OSM-talk] Paper/Article about stagnation in OSM

Hi I didn't read this article. I went out & mapped instead. DaveF On 31/07/2018 22:49, Frederik Ramm wrote: Hi, I don't necessarily agree with all that's been written but I found http://journals.sagepub.com/doi/10.1177/2053951718790591 an interesting read: "The social construction of techno

Re: [OSM-talk] Paper/Article about stagnation in OSM

On 08/01/18 01:08, john whelan wrote: > The report has lots of long words but doesn't seem to grasp basic > concepts well. > > OpenStreetMap to me has two primitives, nodes and ways.  These can and > are combined to create areas.  They have tags attached. > > I honestly can't see any need for mor

Re: [OSM-talk] Paper/Article about stagnation in OSM

Yes, I agree, - Share/Short Link is a great feature. I assume it is kind of an implementation of Geohash [1]. Both the Geohash and the 3-Words transmit just a location, the same as coordinates. 3-Words could be at least in Cyrillic letters. If I point just to a location of an apartment or an o

Re: [OSM-talk] Paper/Article about stagnation in OSM

> Then when we call in browser something like: osm.org/?address=hj3u878s This is already on website and available at "share - short link": https://osm.org/go/0lrHA3xsZ -- Darafei Praliaskouski Support me: http://patreon.com/komzpa ___ talk mailing l

Re: [OSM-talk] Paper/Article about stagnation in OSM

On 1 August 2018 at 08:37, oleksiy.muzalyev wrote: > > > At the same time it is possible to create 208 billion of 8-letter unique > quasi-words with 26 letters of English alphabet (26 in the power of 8 = > 208827064576). Even more if numbers are included. It's enough for all > dwellings on Earth.

Re: [OSM-talk] Paper/Article about stagnation in OSM

On 2018-08-02 22:14, john whelan wrote: Lat and long work quite well. If you have a smartphone with GPS it understands lat long. It may not understand 8 letter addresses. Some combination of letters may offend. How would you space them out? It is What3words all over again, and some people do

Re: [OSM-talk] Paper/Article about stagnation in OSM

isn't this just a variation on what3words [1] or Plus Codes from Google [2] ? Why would you enforce an address string made from 26 strange characters to people that might never have seen the English alphabet ? m. [1] https://what3words.com/ [2] https://plus.codes/ On Thu, Aug 2, 2018 at 9:45 P

Re: [OSM-talk] Paper/Article about stagnation in OSM

Just on lat long every building in OSM is labelled with its lat and long already. Cheerio John On Thu, 2 Aug 2018, 3:45 pm oleksiy.muzal...@bluewin.ch, < oleksiy.muzal...@bluewin.ch> wrote: > > Hi, > > I read the whole article. I agree with the author's main idea, - software > development and im

Re: [OSM-talk] Paper/Article about stagnation in OSM

Lat and long work quite well. If you have a smartphone with GPS it understands lat long. It may not understand 8 letter addresses. Some combination of letters may offend. How would you space them out? Lat and long also have the advantage that addresses with a similar first part are grouped toge

Re: [OSM-talk] Paper/Article about stagnation in OSM

Hi, I read the whole article. I agree with the author's main idea, - software development and implementation has got the invisible social undercurrents, which are as important as the technical issues. By the way, it is true for any human endeavor . Speaking of database structure, - I am thinking ab

Re: [OSM-talk] Paper/Article about stagnation in OSM

A lot can happen in 10 years... On Wed, Aug 1, 2018, 3:34 PM Mateusz Konieczny, wrote: > 1. Sierpień 2018 21:27 od matkoni...@tutanota.com: > > 31. Lipiec 2018 23:49 od frede...@remote.org: > > an interesting read: "The social construction of technological stasis: > The stagnating data structure

Re: [OSM-talk] Paper/Article about stagnation in OSM

1. Sierpień 2018 21:27 od matkoni...@tutanota.com : > 31. Lipiec 2018 23:49 od > frede...@remote.org > > : > > >> an interesting read: "The social construction of technological stasis: >> The stagnating data structure in OpenStreet

Re: [OSM-talk] Paper/Article about stagnation in OSM

31. Lipiec 2018 23:49 od frede...@remote.org : > an interesting read: "The social construction of technological stasis: > The stagnating data structure in OpenStreetMap." > It is hard for me to treat seriously something that has "Figure 6. Code revisions per mo

Re: [OSM-talk] Paper/Article about stagnation in OSM

My background is big databases, XML, ISO standards and such like. The report has lots of long words but doesn't seem to grasp basic concepts well. OpenStreetMap to me has two primitives, nodes and ways. These can and are combined to create areas. They have tags attached. I honestly can't see a

[OSM-talk] Paper/Article about stagnation in OSM

Hi, I don't necessarily agree with all that's been written but I found http://journals.sagepub.com/doi/10.1177/2053951718790591 an interesting read: "The social construction of technological stasis: The stagnating data structure in OpenStreetMap." Grossly simplified, the author tries to answer