I agree that the tool requires some additional work. It seems almost all
of the criticism has been directed at the hypothetical "community clicking
rampage" - where the query is stored on a wiki, and some user runs it
thoughtlessly. At the same time, several skilled users have expressed their
desi
Hi,
On 10/16/2017 11:10 PM, Tobias Zwick wrote:
> Anyway, generally, with everyone raising the alarm about this tool, it
> would be a friendly gesture to either take the tool offline for now or
> set it to read-only mode
Or have it run on the dev API.
> So then, the solution is simple: Make the
Richard, thanks for the link and your analysis.
Eric Raymond once said that "Every good work of software starts by
scratching a developer's personal itch." Judging by how many different
individuals have created various challenges and fixers, there is clearly a
big irritation - highly messy, uncle
Michael, I can only judge by my own experience adding validation autofix
rules - I added a number of Wikipedia tag auto cleanups to JOSM, and they
were reviewed by one or two JOSM developers and merged, probably because
they were deemed benign. I don't know about the other rules, but I suspect
man
Number 2.
>> [...] This was a topic in this thread already and it was
>> voiced that inventing new tags just to be used by this tool in not
>> acceptable and I agree with that. The other tools also do not
>> require that.
>
> [...] Not showing it can also be easily done by a slight
> modification
Hi Yuri,
Am 16.10.2017 um 16:02 schrieb Yuri Astrakhan:
> Rory, most of those queries were copied from the current JOSM validator
> autofixes. I don't think they were discussed, but they might have been
> mass applied without much thought by all sorts of editors.
Could you please give examples f
I will split this into several answers, that is what a threaded
structure is for.
> JOSM fix button
I am not sure what is your point with JOSM's fix button. Let's not
deviate from the topic: your tool.
If you find, something is wrong with JOSM or any other tool in that
matter, better create an ow
Thanks - disabling auto zoom worked.
I'm working on the Puerto Rico project - they are using ESRI World
imagery as a base.
On 2017-10-16 11:22 AM, Nelson A. de Oliveira wrote:
On Mon, Oct 16, 2017 at 3:09 PM, Richard Nairn
wrote:
I'm just starting out and I had a question related to imager
> Except that's not true. In Ireland "handball" is Gaelic Handball¹
> which is a one-on-one game, not a team sport (which is apparently a
> different thing²). There are some sport=handball's tagged in Ireland.
> Now the tag is clearly wrong, and we need to figure out something about
> that. But
Sorry for the duplicated message, Richard. The first one didn't have talk on CC.
On Mon, Oct 16, 2017 at 3:09 PM, Richard Nairn
wrote:
> I'm just starting out and I had a question related to imagery. I am trying
> to do some digitizing of house footprints for HOT-OSM. I'm having issues
> when the
Sorry - Using JOSM - dev build
On 2017-10-16 11:09 AM, Richard Nairn wrote:
Hi,
I'm just starting out and I had a question related to imagery. I am
trying to do some digitizing of house footprints for HOT-OSM. I'm
having issues when the houses are very close together, or I'm trying
to digit
Hi,
I'm just starting out and I had a question related to imagery. I am
trying to do some digitizing of house footprints for HOT-OSM. I'm having
issues when the houses are very close together, or I'm trying to
digitize smaller features. When I try to zoom in beyond native
resolution to move,
Yuri Astrakhan wrote:
> For example, RU community wants to convert amenity=sanatorium
> -> leisure=resort + resort=sanatorium. Clicking on a dot shows a
> popup with the suggested edit. If you think the edit is correct, simply
> click Save.
I've been a bit loth to get involved with this one bu
Rory, most of those queries were copied from the current JOSM validator
autofixes. I don't think they were discussed, but they might have been
mass applied without much thought by all sorts of editors. What's worse,
there is no way to track those autofixes. The wiki page has a huge warning
box at
On 16/10/17 14:02, Yuri Astrakhan wrote:
Rory, thanks, and that's why I think it is a bad idea to do bot edits
without first running it through my tool. If we do a mass edit, we have
to go through a very lengthy community consensus study, which might
still miss things. Then the bot developer m
Rory, thanks, and that's why I think it is a bad idea to do bot edits
without first running it through my tool. If we do a mass edit, we have to
go through a very lengthy community consensus study, which might still miss
things. Then the bot developer might still make an error that is not likely
t
On 15/10/17 15:14, Tobias Zwick wrote:
> 1. If this does not require humans because both tagging schemes are
> mutually translatable (i.e. lets say for sport=handball <->
> sport=team_handball), then, the edit can be made automatically by a bot.
Except that's not true. In Ireland "handball" i
On Monday 16 October 2017, Marc Gemis wrote:
> I was thinking about possible changes to the tool that would make it
> a useful tool for the community, and at the same time not violating
> any policy.
Sure, if you want to do that.
In my opinion there is however not really a need for more tools in
I was thinking about possible changes to the tool that would make it a
useful tool for the community, and at the same time not violating any
policy.
On Mon, Oct 16, 2017 at 1:06 PM, Christoph Hormann wrote:
> On Monday 16 October 2017, Marc Gemis wrote:
>> Would Yuri's tool be OK, if the propose
On Monday 16 October 2017, Marc Gemis wrote:
> Would Yuri's tool be OK, if the proposed changes were limited to
> objects that were created/last edited after survey to the person that
> is using the tool ?
>
> I was thinking of a scenario where people try to help with a
> tag-renaming proposal.
> S
Martin, could you take a look at my last reply to Tobias - I have actually
expressed some concerns with bots in general (very surprisingly,
considering my heavy involvement with it previously). I think this tool
can actually make the path to bots easier for the community, making new
bots safer and
Would Yuri's tool be OK, if the proposed changes were limited to
objects that were created/last edited after survey to the person that
is using the tool ?
I was thinking of a scenario where people try to help with a
tag-renaming proposal.
Such a tool would be handy to help them locate all objects
Frederik:
> I am appalled that after your abysmal OSM editing history where you more
> often than not ignored existing customs rules, while *claiming* to
> follow them, you're now building a service that entices others to do the
> same.
>
> On Sat, Oct 14, 2017 at 6:09 AM Christoph Hormann wro
Lester, the naming of this service is still a work in progress, and might
have confused a few people. My apologies for that. I do plan to create a
proper name, logo, domain name, and SSL certificate once I have some spare
time. If anyone wants to take care of that, your help is appreciated.
The
On 16/10/17 05:24, Minh Nguyen wrote:
> When a Wikidata item is modified to link to a Wikipedia article (or
> Wikivoyage article etc.), the Wikipedia article automatically links back
> to the Wikidata item. This is a software feature made possible because
> Wikipedia and Wikidata are colocated in t
On 15/10/17 22:04, Frederik Ramm wrote:
> You've built a query engine to work with OSM and
> Wikidata and are pushing that relentlessly, to a point where the
> decision of just how much Wikiadata linking we want in OSM is totally
> taken out of our hands.
Seconded ... personally I have still to be
2017-10-16 4:26 GMT+02:00 Daniel Koć :
> Hi,
>
> I'm looking for partners with hardware resources in Poland to use it for
> some interesting OSM-related projects.
>
> I've made basic research with OSMF, French and German pages about hardware
> and network connectivity and it looks like they collab
27 matches
Mail list logo
