Yuri, I did not find a way to open an issue about the bot
(https://github.com/Sophox/sophox/tree/metabot/metabot is a branch, so
any issues would appear to be about Sophox). Is there an appropriate
place to request changes, besides Talk:Date_items?
- Joseph Eisenberg
On 2/19/20, Mateusz Konieczny
As Martin (@ dieterdreist) mentioned above, even 200 pixels is plenty
of space for the 15 character long "© Openstreetmap": that gives you
12 pixels per character width.
For example, our rendering of "Upper Hutchinson"... (field) in Chicago
is only 81 x 12 pixels for 16 characters at 10 point font
19 Feb 2020, 13:14 by o...@imagico.de:
> Anyway - while i am not surprised about this it is sobering how little
> of the feedback provided in previous conversation - in particular from:
>
> https://lists.openstreetmap.org/pipermail/talk/2019-August/thread.html#83068
>
> has found a substantial
19 Feb 2020, 21:05 by si...@poole.ch:
>
>
>
> Am 19.02.2020 um 20:17 schrieb Mateusz Konieczny via talk:
>
>> 19 Feb 2020, 17:22 by >> dieterdre...@gmail.com>> :
>>
>>> But I stick to the comment that 500px are far too many (=1000
>>> actual retina pixels or 1500 px on a retina@3
On 19/02/2020 12:14, Christoph Hormann wrote:
I am therfore
reluctant to newly review the document in detail because it seems a
waste of effort.
Don't bother then. No one will miss it.
--
Steve
___
talk mailing list
talk@openstreetmap.org
https://
sent from a phone
>> On 19. Feb 2020, at 21:10, Simon Poole wrote:
>
>
>
> Am 19.02.2020 um 20:17 schrieb Mateusz Konieczny via talk:
>> 19 Feb 2020, 17:22 by dieterdre...@gmail.com:
>> But I stick to the comment that 500px are far too many (=1000 actual retina
>> pixels or 1500 px on a re
Am 19.02.2020 um 20:17 schrieb Mateusz Konieczny via talk:
> 19 Feb 2020, 17:22 by dieterdre...@gmail.com:
>
> But I stick to the comment that 500px are far too many (=1000
> actual retina pixels or 1500 px on a retina@3).
>
> Yes, you may easily fit at least "© OSM"
> with link in such s
19 Feb 2020, 17:22 by dieterdre...@gmail.com:
> But I stick to the comment that 500px are far too many (=1000 actual retina
> pixels or 1500 px on a retina@3).
>
Yes, you may easily fit at least "© OSM"
with link in such space.
Suggesting that real attribution is
not required in such case is a
For the sake of the discussion about 'small map' size, a mockup on the wiki
would certainly help.
The 500dpi and 25% size seems quite big to me, there's room for (c)
Openstreetmap there.
Yves Cainaud ___
talk mailing list
talk@openstreetmap.org
https://
I believe there is actually a small issue with the definition here, as
there are two conflicting DIP definitions in use (one pixel on mobile
devices ~160 DPI vs one pixel for CSS 96 DPI), we need to state what we
are using.
Simon
Am 19.02.2020 um 17:22 schrieb Martin Koppenhoefer:
>
> sent from a
sent from a phone
> Il giorno 19 feb 2020, alle ore 16:37, Michal Migurski ha
> scritto:
>
> For our purposes, this is a better definition because it’s defined in terms
> of what a viewer can see rather than its implementation in hardware.
contrary to what I had written above I agree that
sent from a phone
> As pointed out in the guideline text, the difference is not only screen size,
> but how you interact with the device. Try clicking on your average watch.
>
watches are kind of an exception because of their really small screen, but they
are already perfectly covered by th
> On Feb 19, 2020, at 5:29 AM, Martin Koppenhoefer
> wrote:
>
> I am not sure what "device-independent pixels" means. Is this about points
> (i.e. physical, hardware screen pixels divided by the scale)? IMHO we should
> require actual, physical pixels, because it is them who determine whether
Joseph,
If you were talking of fast food restaurants, I would understand that we expect
to see these in hundred of countries. But there are features that yes are not
seen as intensively.
One fast food POI counts for one. One 500km route counts also for one.
This Overpass query shows that the ta
Am 19.02.2020 um 15:59 schrieb Martin Koppenhoefer:
> ..
> Imho we should not differentiate between mobile and desktop devices:
> either there is sufficient space and attribution should be permanent,
> or there isn’t and it is ok you have to click somewhere to see it. The
> constraints/conditions
There is a difference (a very big one), between saying "if you do X we
believe you are fulfilling the requirements of the licence" and saying
"you need to do Y to make us happy, even if it doesn't have any founding
in the licence". And that has nothing to do with winning court cases,
but all with s
sent from a phone
> Il giorno 19 feb 2020, alle ore 15:17, Simon Poole ha
> scritto:
>
>
> Am 19.02.2020 um 14:40 schrieb Joseph Eisenberg:
>>> IMHO attribution should always be required 1. on the map 2. in high
>>> contrast
>> Agreed.
>> The main problem is that mobile devices, which are
If the map says "Copyright BoxMap, imagery copyright IRSE" in bold in
the right corner, but the Openstreetmap notice is hidden behind a tiny
"i" or ony shown briefly on app startup (which only happens after your
phone crashes or the app updates), then this gives the impression that
the data is also
Am 19.02.2020 um 15:02 schrieb Frederik Ramm:
>
> In my mind I always ask the question: How essential was OSM for what is
> being done? How much of your hike remains if you remove OSM from the
> picture? How much of a trained AI remains if you remove OSM from the
> picture?
Assuming "essential" d
Am 19.02.2020 um 14:40 schrieb Joseph Eisenberg:
>> IMHO attribution should always be required 1. on the map 2. in high contrast
> Agreed.
>
> The main problem is that mobile devices, which are by far the most
> common ways of accessing maps around the world, are only required to
> provide attrib
Joseph, you deleted recently the link I added to the Map_features wiki page for
snowmobile routes. It seems you dont like such schema and want to impose your
views here.
Snowmobiles routes are as common as bike or hiking trails in nordic countries.
And the snowmobile wiki page describes it.
Hi,
On 19.02.20 14:38, Simon Poole wrote:
> As a thought experiment consider planning a trip around your fav place
> boundary with OSM, going for the walk with an OSM based map in your
> hand so that you stay on course, and then writing a a blog post about
> your experience. For the purpose of th
> IMHO attribution should always be required 1. on the map 2. in high contrast
Agreed.
The main problem is that mobile devices, which are by far the most
common ways of accessing maps around the world, are only required to
provide attribution after a click or swipe, or even just on app
startup w
Am 19.02.2020 um 13:50 schrieb Frederik Ramm:
> ...
> I acknowledge Kathleen Lu's recent remark about the ODbL being very
> clear on a derived product having to "contain" OSM in some way which
> would not be the case here; but I think this calls for working on ODbL
> 1.1 to rectify the issue, rath
Am Mi., 19. Feb. 2020 um 13:53 Uhr schrieb Frederik Ramm <
frede...@remote.org>:
> > Not to mention the most blatant attempts at sneaking corporate wishlist
> > items into the guideline are all still there - like the 1 m^2 map
> > area limit that has been conjured out of thin air
>
> True, thi
On Wednesday 19 February 2020, Frederik Ramm wrote:
>
> * "Except for small maps or multiple data sources, as described
> below, attribution must be visible without requiring the user to
> click on an icon or similar interaction." - Your critique focuses on
> the exceptions, but saying clearly that
Hi,
On 19.02.20 13:14, Christoph Hormann wrote:
> the document then almost exclusively presents
> supposed exceptions from the attribution requirement of the ODbL.
I've just read the document for the first time this morning, so I don't
have the context of prior discussions and I think your wholes
On Wednesday 19 February 2020, Simon Poole wrote:
>
> The updated document can be found here
> https://wiki.openstreetmap.org/wiki/Draft_Attribution_Guideline
I appreciate the draft document being available on the wiki - although
the lack of an edit history makes this fairly pointless for the pur
Paul Johnson wrote:
> Could we get some lane editing/rendering in these editors
> to cut down on this kind of unintentionally erratic mapping?
Sure, you're welcome to open a friendly issue at
https://github.com/systemed/potlatch2/issues listing the base case for what
you think is required.
> > N
The LWG has now integrated feedback from the initial airing in August
last year, from a total of three sessions at SOTM-US and SOTM in
Heidelberg, feedback from the OSMF board and from the wider OSM community.
Barring any major late developing issues, we intend to forward this to
the OSMF board fo
> I have occasionally moved such pages into the user's name space when I
found them to (by content, if not by name) to be proposals for
something, rather than a documentation of something already established.
That is fine if the tag has not been used, and the page is written
like a proposal sugges
Hi,
On 19.02.20 07:33, Rory McCann wrote:
> I don't know what your experience with the OSM wiki is, but I've created
> new wiki pages for new tags, without bothering with proposal pages.
I have occasionally moved such pages into the user's name space when I
found them to (by content, if not by na
32 matches
Mail list logo
