Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Create a Geocoder comparison app

Aperta
#104 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@cmhodgson ci sta già lavorando.

Dal 22/9/2017.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement low priority new app

The Geocoder Comparison app lets you compare the BC Address Geocoder to other geocoders, primarily, the Google Maps API. The app does the following:

  1. A user has a choice of geocoders. For the first release of this app, google maps is the only choice.

  2. A user can choose to create a new random list of civic addresses or load a CSV file containing a list of civic addresses. If the user selects the creation of a new random address list, they specify the size of the list and initiate list generation. The list is created as per the route tab in the location services demo app. If the user wants to load an address list from a file, they are presented a file dialogue box, selects a file and the list of addresses is loaded from the file and geocoded. The list of addresses is then geocoded by the google maps API.

  3. The other geocoder's esults are then compared to the BC Address Geocoder results. Location and attribute faults are compared. Address locations are compared by computing the square of the distance between locations (e.g., the variance). The comparison should involve the BC Address Geocoder's parcelPoint or accessPoint, whichever is closer to the gmap point. Address elements are compared and the appropriate faults and match score are generated for gmap address elements (e.g. streetName.wrong).

  4. The app displays a summary of the comparison including
    number of points sampled
    bbox
    variance of positional accuracy
    RMSE of positional accuracy
    histogram of match precisions
    histogram of fault counts

  5. The app should also display DBC addresses as disc icons on map colour coded by positional accuracy interval as follows:
    green - variance < 9
    yellow - 9 < variance < 144
    red - variance > 144

    Each DBC address should be labelled with the gmaps match score

Lingua principale
Nessun dato sulla lingua
Stelle
7
Fork
6
Merge medio
12g 20h
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di bcgov/ols-devkit

Tutte le issue di bcgov/ols-devkit

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.