[Talk-br] Tags useful for rendering of roads in poor conditions

[Fernando Trebien]

Oi Gerald,

Estou jogando o assunto pra lista tagging primeiramente (pra ter certeza de
que o "significado" das tags é exatamente o que queremos capturar). Acho
que depois passaria pela lista design e por fim (quando já tiver um
protótipo funcional) o assunto seria com os designers do estilo Carto, no
Github. Até então, o assunto começou como um registro de incidente no
Github do Carto, daí alguém me respondeu em privado como instalar o
software pra começar a fazer testes e daí alguém respondeu a essa conversa
privada com essa informação sobre a tag tracktype. (Toda a conversa privada
vem no fim da mensagem.)

A sugestão me surpreendeu da mesma forma que surpreendeu a você, e penso da
mesma forma que você sobre os casos em que surface afetaria a renderização
e também quanto à idéia de passar a usar tracktype (e sugeri-la pros
demais) se isso resolver o problema da renderização dessas vias. Minha
dúvida agora é se essa prática dos australianos já "saiu da Austrália" (se
a idéia já passou por outros olhos), por isso passei adiante pra lista
tagging.

Abraço,

Fernando


On Tue, Dec 31, 2013 at 2:36 PM, Gerald Weber <gweberbh em gmail.com> wrote:

> Oi Fernando
>
> em qual lista está sendo debatido isto?
>
> tracktype é interessante, mas eu julgava que seria somente para
> highway=track como o nome sugere. Além disto requer uma vistoria para
> realmente saber em qual categoria encaixar.
>
> No meu entender o ideal é agrupar tudo que encaixa em unpaved
> (dirt,grass,sand,round etc) e fazer a renderização diferenciada.
>
> Agora, se adicionar tracktype resolver a renderização diferenciada eu topo
> passar a usar como os australianos propõem.
>
> abraço
>
> Gerald
>
>
> On 31 December 2013 14:10, Fernando Trebien <fernando.trebien em gmail.com>wrote:
>
>> Hello everyone,
>>
>> I've been interested in proposing a change to Carto's style (Mapnik's
>> main style) to allow visual identification of unpaved roads for any kind of
>> road, much like the Humanitarian style does, which bases this decision on
>> values of the surface tag. The Brazilian community has shown interest on
>> this many times, since lack of this feature causes unaware users to
>> classify roads incorrectly. David Bannon proposes (below) that we use the
>> tracktype tag for that instead, but I've never seen it being used for
>> anything besides roads with highway=track (therefore, not a very common
>> practice it seems). Do you think we should encourage its use in conjunction
>> with unclassified, tertiary, secondary and primary highways?
>>
>> It seems to me that surface=compacted is quite similar in meaning to
>> tracktype=grade1 (whereas surface=sand, surface=dirt, and others, could be
>> equated with other grades but rarely with grade1, particularly because the
>> "compacted" value exists) and so both tags could be used for the same
>> rendering purpose. Do you agree?
>>
>> I've seen people from different countries requesting different things on
>> this topic: some would consider even a sett street "unpaved" (therefore,
>> requiring special rendering), but it seems that a "compacted unpaved" road
>> is the limit with which few would disagree. Finding the right universal
>> threshold (if there is only one) is still pretty much debatable, so
>> opinions are appreciated.
>>
>> ---------- Forwarded message ----------
>> From: davidbannon <notifications em github.com>
>> Date: Tue, Dec 31, 2013 at 4:02 AM
>> Subject: Re: [openstreetmap-carto] Render paved/unpaved (#110)
>> To: gravitystorm/openstreetmap-carto <
>> openstreetmap-carto em noreply.github.com>
>> Cc: ftrebien <fernando.trebien em gmail.com>
>>
>>
>> I am not sure the tag surface= is the right one here. It has a lot of
>> possible values, and a lot of them in use. We'd need a look up table to
>> decide what to do. Better, in my humble opinion to use the tracktype= tag.
>> This tag is intended to show what state the road is likely to be in and
>> thats the information a user really needs. Further, this tag is very widely
>> used.
>>
>> The Australian Tagging Guidelines on OSM discusses this (
>> http://wiki.openstreetmap.org/wiki/Australian_Tagging_Guidelines#Unsealed_and_4wd_Roads_.28Dirt.2C_Gravel.2C_Formed.2C_etc.29) and believes that any road with tracktype= asserted needs to be shown so
>> people are aware its not a sealed road.
>>
>> Please remember that highway= type tags should show what a road is is
>> intended for, further information is needed if the surface of that road is
>> not what might be expected ! This is particularly important in places like
>> the Australian Outback where long distances are involved. Many people have
>> died as a result of them underestimating their ability to use a particular
>> road. I don't want to see OSM mentioned in a coroners report.
>>
>> David
>>
>> —
>> Reply to this email directly or view it on GitHub<https://github.com/gravitystorm/openstreetmap-carto/issues/110#issuecomment-31385094>
>> .
>>
>>
>>
>> --
>> Fernando Trebien
>> +55 (51) 9962-5409
>>
>> "The speed of computer chips doubles every 18 months." (Moore's law)
>> "The speed of software halves every 18 months." (Gates' law)
>>
>> _______________________________________________
>> Talk-br mailing list
>> Talk-br em openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-br
>>
>>
>
>
> --
>
> Dr. Gerald Weber
>
> gweberbh em gmail.com
>
> Personal website <https://sites.google.com/site/geraldweberufmg/>
>
>
>  Departamento de Física/Universidade Federal de Minas Gerais
>
> Department of Physics/Federal University of Minas Gerais
>
> Campus da Pampulha
>
> Av. Antônio Carlos, 6627, 31270-901 Belo Horizonte, MG, Brazil
>
> mobile: +55-(0)31-96462277 (mudou/changed 02/07/2013)
>
> _______________________________________________
> Talk-br mailing list
> Talk-br em openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-br
>
>


-- 
Fernando Trebien
+55 (51) 9962-5409

"The speed of computer chips doubles every 18 months." (Moore's law)
"The speed of software halves every 18 months." (Gates' law)
-------------- Próxima Parte ----------
Um anexo em HTML foi limpo...
URL: <http://lists.openstreetmap.org/pipermail/talk-br/attachments/20131231/5f7007bc/attachment-0001.html>