locationtech/geotrellis

0

/ 100

Documentation94
Engineering68
Health100
Scala1,372Other1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

GeoTrellis is a geographic data processing engine for high performance applications.

Documentation

94

Contributing guide5pt79

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

68

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt57

CI is configured (.github/workflows/ci.yml).

Tests18pt80

Test files detected (accumulo-spark/src/test).

Reproducibility6pt80

Lockfile present (website/yarn.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (website/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 361
    Forks
  • 25
    Releaseslatest 6y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,372
    Watchers

Responsiveness

  • 84d 6h
    Median issue response
  • <1h
    Median PR merge time
  • 247
    Open issues
Repository files50 root entries
  • .circleci
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Environment pinned via .github/docker-compose.yml.
    Good: Issue or PR templates present.
  • .locationtech
  • accumulo
  • accumulo-spark
    Good: Test files detected (accumulo-spark/src/test).
  • bench
  • cassandra
  • cassandra-spark
  • doc-examples
  • docs
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • docs-mdoc
  • gdal
  • gdal-spark
  • geotools
  • hbase
  • hbase-spark
  • layer
  • macros
  • proj4
  • project
  • publish
  • raster
  • raster-testkit
  • s3
  • s3-spark
  • scripts
  • shapefile
  • spark
  • spark-pipeline
  • spark-testkit
  • store
  • util
  • vector
  • vector-testkit
  • vectortile
  • website
    Good: Lockfile present (website/yarn.lock). Installs are reproducible.
    Good: Dependency manifest found (website/package.json).
  • .about.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .jvmopts
  • .sbtignore
  • .sbtopts
  • about.html
  • build.sbt
  • CHANGELOG.md
  • icon.png
  • LICENSE
    Good: Licensed under Other.
  • notice.html
  • package.html
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.