Decide whether Coastal means "on land" and Marine means "in water"

Abierto
  • ¿Algo no está bien?
#10 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
data

Línea de trabajo

Start by examining the existing Coastal and Marine classifications and how the group selector uses them; the issue does not name specific files or tests. Compare the categories against AVONET's breeding-habitat definitions and the bird examples in the issue, then determine whether to keep or add classifications. Done means agreeing on a consistent way to represent these birds for the intended viewing use.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

The addition of Coastal vs Marine by birdview might be wrong; the group selector masks this.

There are a few categories to consider:

  1. Birds that spend their time out at sea, rarely seen near coasts, like Petrels and Shearwaters
  2. Birds that spend their at sea but are also seen near coasts, but rarely on land, like sea ducks
  3. Birds seen near coasts and on beaches, like gulls, terns, and shorebirds

The current classifications of Coastal and Marine are inconsistent on these, and my recent manual additions might make them worse.
We need to understand how AVONET uses Coastal vs Marine to classify these birds and assess how we should use them. Part of what's hard is that AVONET focuses on breeding habitat, while most birders see these birds in migratory habitats.
We might need to introduce our own classifications to make it easy to see the birds you want.

Lenguaje dominante
Go
Estrellas
0
Forks
3
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de google/birdview

Todos los issues de google/birdview

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.