Skip to content

Japanese Gecoder within PostgreSQL

active 2023-11-082025-03-13 (UTC)

Complete coverage26,587 / 26,587 hourly files (100%) · 2 absent upstream2023-08-152026-08-26 (UTC)
Events
196
Pushes
81
Pull requests
26
Issues
15
Stars
1
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 492 days from 2023-11-08 to 2025-03-13. Pushes: 81 total, peak 7 in a day. Pull requests: 26 total, peak 5 in a day. Issues: 15 total, peak 4 in a day. Comments: 12 total, peak 3 in a day. Stars: 1 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
mbasa8158101
sanak58231611

Recent activity

Latest issues, pull requests and releases

  • Releasegithub-actions[bot]2025-03-13 08:03
    PgGeocoder
  • Pull request#25mbasa2025-03-13 08:03
  • Pull request#25mbasa2025-03-13 07:23
  • Releasegithub-actions[bot]2024-07-25 04:03
    PgGeocoder
  • Issue comment#21sanak2024-07-24 11:31
    CI failure 'ERROR: duplicate key value violates unique constraint "address_o_u"'
  • Issue#21sanak2024-07-24 11:31
    CI failure 'ERROR: duplicate key value violates unique constraint "address_o_u"'
  • Releasegithub-actions[bot]2024-07-24 09:43
    PgGeocoder
  • Issue#20mbasa2024-07-24 09:43
    Handle Historical Address Data Set.
  • Issue#19mbasa2024-07-24 09:43
    Use ascending order for matching level like other OSS geocoders and allow specifing level when geocoding
  • Issue#17mbasa2024-07-24 09:43
    Support starting with `大字` or `字` Ooaza address search
  • Pull request#24mbasa2024-07-24 09:43
  • Pull request#24mbasa2024-07-24 09:43
  • Pull request#23sanak2024-07-24 07:56
  • Issue comment#23sanak2024-07-24 07:55
    Cleanup Tests and CI
  • Pull request#23sanak2024-07-24 05:24
  • Issue comment#22sanak2024-07-24 04:47
    Fix CI fixtures load error
  • Pull request#22sanak2024-07-24 04:47
  • Issue comment#17sanak2024-07-23 12:46
    Support starting with `大字` or `字` Ooaza address search
  • Pull request#22sanak2024-07-17 07:58
  • Issue#21sanak2024-07-16 03:32
    CI failure 'ERROR: duplicate key value violates unique constraint "address_o_u"'
  • Issue#20mbasa2024-07-02 13:38
    Handle Historical Address Data Set.
  • Issue#19sanak2024-06-25 09:19
    Use ascending order for matching level like other OSS geocoders and allow specifing level when geocoding
  • Pull request#18sanak2024-06-24 01:59
  • Issue comment#18sanak2024-06-24 01:59
    Support CI
  • Pull request#16sanak2024-06-21 09:16

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.