Executive summary
onthegomap/planetiler falls short of our standard for a preview release, in part because it has pipeline tools referenced by a changeable name. It scores 60.6 out of 100 and is rated Adequate, and all 66 of its critical findings are security problems.
Security and Compliance, at 51.0, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the four pipeline jobs with more access than they need, worth about 3.0 points. Declaring which values may be missing comes next, worth about 3.8 points. Raising Security and Compliance to 68 would lift the score to about 67.2.
Forty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and four secrets can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting each secret to its own step would close these risks. Correcting the flagged pipeline settings would fix the two weaknesses in the build pipeline's configuration, and the three passwords or keys in the code's history and the password or key in the code need replacing, with the old ones switched off.
The product code is 45,265 lines, about €87,000 to rebuild.
If Security and Compliance rose from 51.0 to 68, the lowest score rated Strong, the score would rise from 60.6 to about 67.2.
Rebuild cost: about €87,000 · Estimate
| Cost to rebuild | €29,000 to €140,000, for 481 to 1,524 hours of work, about 0.6 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 45,265 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 com.onthegomap.planetiler.util.log4j | 2 io.prometheus.client | 3 org.apache.hadoop.io.compress | 4 org.apache.parquet.filter2.predicate | 5 scripts | 6 scripts.shp2parquet | 7 com.onthegomap.planetiler.util | 8 com.onthegomap.planetiler.worker | 9 com.onthegomap.planetiler.reader.remote | 10 com.onthegomap.planetiler.stats | 11 com.onthegomap.planetiler.render | 12 com.onthegomap.planetiler.reader.osm | 13 com.onthegomap.planetiler.reader | 14 com.onthegomap.planetiler.expression | 15 com.onthegomap.planetiler.custommap.expression | 16 com.onthegomap.planetiler.geo | 17 com.onthegomap.planetiler.config | 18 com.onthegomap.planetiler.custommap.expression.stdlib | 19 com.onthegomap.planetiler.collection | 20 com.onthegomap.planetiler.archive | 21 com.onthegomap.planetiler | 22 com.onthegomap.planetiler.files | 23 com.onthegomap.planetiler.pmtiles | 24 com.onthegomap.planetiler.stream | 25 com.onthegomap.planetiler.custommap.configschema | 26 com.onthegomap.planetiler.mbtiles | 27 com.onthegomap.planetiler.reader.geojson | 28 com.onthegomap.planetiler.reader.parquet | 29 com.onthegomap.planetiler.reader.shapefile | 30 com.onthegomap.planetiler.validator | 31 com.onthegomap.planetiler.custommap | 32 com.onthegomap.planetiler.custommap.validator |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.onthegomap.planetiler.util.log4j | ||||||||||||||||||||||||||||||||
| 2 io.prometheus.client | ||||||||||||||||||||||||||||||||
| 3 org.apache.hadoop.io.compress | ||||||||||||||||||||||||||||||||
| 4 org.apache.parquet.filter2.predicate | ||||||||||||||||||||||||||||||||
| 5 scripts | ||||||||||||||||||||||||||||||||
| 6 scripts.shp2parquet | ||||||||||||||||||||||||||||||||
| 7 com.onthegomap.planetiler.util | 3 | 2 | 6 | 4 | 1 | 5 | 2 | |||||||||||||||||||||||||
| 8 com.onthegomap.planetiler.worker | 10 | 7 | ||||||||||||||||||||||||||||||
| 9 com.onthegomap.planetiler.reader.remote | 16 | |||||||||||||||||||||||||||||||
| 10 com.onthegomap.planetiler.stats | 7 | 7 | 3 | |||||||||||||||||||||||||||||
| 11 com.onthegomap.planetiler.render | 1 | 1 | 8 | 1 | 1 | 2 | ||||||||||||||||||||||||||
| 12 com.onthegomap.planetiler.reader.osm | 7 | 2 | 6 | 1 | 3 | 4 | 7 | 2 | ||||||||||||||||||||||||
| 13 com.onthegomap.planetiler.reader | 1 | 3 | 1 | 13 | 1 | 4 | 4 | 3 | ||||||||||||||||||||||||
| 14 com.onthegomap.planetiler.expression | 20 | 2 | ||||||||||||||||||||||||||||||
| 15 com.onthegomap.planetiler.custommap.expression | 2 | 3 | 7 | 2 | ||||||||||||||||||||||||||||
| 16 com.onthegomap.planetiler.geo | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||
| 17 com.onthegomap.planetiler.config | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 18 com.onthegomap.planetiler.custommap.expression.stdlib | 3 | 2 | ||||||||||||||||||||||||||||||
| 19 com.onthegomap.planetiler.collection | 19 | 1 | 3 | 2 | 4 | 3 | 5 | |||||||||||||||||||||||||
| 20 com.onthegomap.planetiler.archive | 9 | 1 | 5 | 7 | 6 | 3 | 6 | |||||||||||||||||||||||||
| 21 com.onthegomap.planetiler | 6 | 2 | 2 | 5 | 14 | 6 | 4 | 12 | 5 | 1 | 1 | |||||||||||||||||||||
| 22 com.onthegomap.planetiler.files | 1 | 2 | 6 | 3 | 7 | |||||||||||||||||||||||||||
| 23 com.onthegomap.planetiler.pmtiles | 3 | 2 | 8 | |||||||||||||||||||||||||||||
| 24 com.onthegomap.planetiler.stream | 1 | 1 | 1 | 3 | 16 | |||||||||||||||||||||||||||
| 25 com.onthegomap.planetiler.custommap.configschema | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 26 com.onthegomap.planetiler.mbtiles | 2 | 5 | 1 | 11 | 2 | |||||||||||||||||||||||||||
| 27 com.onthegomap.planetiler.reader.geojson | 2 | 1 | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||
| 28 com.onthegomap.planetiler.reader.parquet | 6 | 5 | 2 | 1 | 3 | 5 | 3 | 2 | 2 | |||||||||||||||||||||||
| 29 com.onthegomap.planetiler.reader.shapefile | 1 | 3 | 2 | 1 | 1 | |||||||||||||||||||||||||||
| 30 com.onthegomap.planetiler.validator | 1 | 1 | 3 | 4 | ||||||||||||||||||||||||||||
| 31 com.onthegomap.planetiler.custommap | 2 | 3 | 11 | 4 | 13 | 3 | 5 | 6 | ||||||||||||||||||||||||
| 32 com.onthegomap.planetiler.custommap.validator | 1 | 1 | 2 |
7→10 com.onthegomap.planetiler.util uses com.onthegomap.planetiler.stats part of a loop✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.util uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.util.TopOsmTiles→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.util.Wikidata→com.onthegomap.planetiler.stats.Readablecom.onthegomap.planetiler.util.Wikidata→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.util uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.util, while a change to com.onthegomap.planetiler.util can't break com.onthegomap.planetiler.stats.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→12 com.onthegomap.planetiler.util uses com.onthegomap.planetiler.reader.osm part of a loop✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.util uses a type in com.onthegomap.planetiler.reader.osm.
- The types involved
com.onthegomap.planetiler.util.Wikidata→com.onthegomap.planetiler.reader.osm.Blockcom.onthegomap.planetiler.util.Wikidata→com.onthegomap.planetiler.reader.osm.OsmInputFile
- Direction
- com.onthegomap.planetiler.util uses com.onthegomap.planetiler.reader.osm, so a change to com.onthegomap.planetiler.reader.osm can break com.onthegomap.planetiler.util, while a change to com.onthegomap.planetiler.util can't break com.onthegomap.planetiler.reader.osm.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→16 com.onthegomap.planetiler.util uses com.onthegomap.planetiler.geo part of a loop✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler.util uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.util.Cell→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.util.CompareArchives→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.util.LoopLineMerger→com.onthegomap.planetiler.geo.GeometryPipelinecom.onthegomap.planetiler.util.TileSummary→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.util.TileWeights→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.util.TsvSerializer→com.onthegomap.planetiler.geo.TileCoord
- Direction
- com.onthegomap.planetiler.util uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.util, while a change to com.onthegomap.planetiler.util can't break com.onthegomap.planetiler.geo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→17 com.onthegomap.planetiler.util uses com.onthegomap.planetiler.config part of a loop✕
- Connections
- 4 pairs of types, where a type in com.onthegomap.planetiler.util uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.util.CompareArchives→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.util.Downloader→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.util.OvertureStac→com.onthegomap.planetiler.config.Boundscom.onthegomap.planetiler.util.TopOsmTiles→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.util uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.util, while a change to com.onthegomap.planetiler.util can't break com.onthegomap.planetiler.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→19 com.onthegomap.planetiler.util uses com.onthegomap.planetiler.collection part of a loop✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.util uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.util.ResourceUsage→com.onthegomap.planetiler.collection.Storage
- Direction
- com.onthegomap.planetiler.util uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.util, while a change to com.onthegomap.planetiler.util can't break com.onthegomap.planetiler.collection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→20 com.onthegomap.planetiler.util uses com.onthegomap.planetiler.archive part of a loop✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler.util uses a type in com.onthegomap.planetiler.archive.
- The types involved
com.onthegomap.planetiler.util.1Batch→com.onthegomap.planetiler.archive.Tilecom.onthegomap.planetiler.util.1Diff→com.onthegomap.planetiler.archive.Tilecom.onthegomap.planetiler.util.CompareArchives→com.onthegomap.planetiler.archive.Tilecom.onthegomap.planetiler.util.CompareArchives→com.onthegomap.planetiler.archive.TileArchiveConfigcom.onthegomap.planetiler.util.CompareArchives→com.onthegomap.planetiler.archive.TileCompression
- Direction
- com.onthegomap.planetiler.util uses com.onthegomap.planetiler.archive, so a change to com.onthegomap.planetiler.archive can break com.onthegomap.planetiler.util, while a change to com.onthegomap.planetiler.util can't break com.onthegomap.planetiler.archive.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→21 com.onthegomap.planetiler.util uses com.onthegomap.planetiler part of a loop✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.util uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.util.TileSizeStats→com.onthegomap.planetiler.VectorTilecom.onthegomap.planetiler.util.Wikidata→com.onthegomap.planetiler.Profile
- Direction
- com.onthegomap.planetiler.util uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.util, while a change to com.onthegomap.planetiler.util can't break com.onthegomap.planetiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→10 com.onthegomap.planetiler.worker uses com.onthegomap.planetiler.stats part of a loop✕
- Connections
- 10 pairs of types, where a type in com.onthegomap.planetiler.worker uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.worker.Builder→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.worker.Empty→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.worker.ReaderForThread→com.onthegomap.planetiler.stats.Countercom.onthegomap.planetiler.worker.WorkQueue→com.onthegomap.planetiler.stats.MultiThreadCountercom.onthegomap.planetiler.worker.WorkQueue→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.worker.Worker→com.onthegomap.planetiler.stats.ProgressLoggerscom.onthegomap.planetiler.worker.Worker→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.worker.WorkerPipeline→com.onthegomap.planetiler.stats.ProgressLoggerscom.onthegomap.planetiler.worker.WorkerPipeline→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.worker.WriterForThread→com.onthegomap.planetiler.stats.Counter
- Direction
- com.onthegomap.planetiler.worker uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.worker, while a change to com.onthegomap.planetiler.worker can't break com.onthegomap.planetiler.stats.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→19 com.onthegomap.planetiler.worker uses com.onthegomap.planetiler.collection part of a loop✕
- Connections
- 7 pairs of types, where a type in com.onthegomap.planetiler.worker uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.worker.Builder→com.onthegomap.planetiler.collection.FeatureGroupcom.onthegomap.planetiler.worker.Builder→com.onthegomap.planetiler.collection.SortableFeaturecom.onthegomap.planetiler.worker.ReaderForThread→com.onthegomap.planetiler.collection.IterableOncecom.onthegomap.planetiler.worker.SinkStep→com.onthegomap.planetiler.collection.IterableOncecom.onthegomap.planetiler.worker.WeightedHandoffQueue→com.onthegomap.planetiler.collection.IterableOncecom.onthegomap.planetiler.worker.WorkQueue→com.onthegomap.planetiler.collection.IterableOncecom.onthegomap.planetiler.worker.WorkerStep→com.onthegomap.planetiler.collection.IterableOnce
- Direction
- com.onthegomap.planetiler.worker uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.worker, while a change to com.onthegomap.planetiler.worker can't break com.onthegomap.planetiler.collection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→7 com.onthegomap.planetiler.reader.remote uses com.onthegomap.planetiler.util✕
- Connections
- 16 pairs of types, where a type in com.onthegomap.planetiler.reader.remote uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.reader.remote.CachedRangeFile→com.onthegomap.planetiler.util.ByteRangecom.onthegomap.planetiler.reader.remote.CachedRangeFile→com.onthegomap.planetiler.util.Downloadercom.onthegomap.planetiler.reader.remote.CachedRangeFile→com.onthegomap.planetiler.util.Plancom.onthegomap.planetiler.reader.remote.CachedRangeFile→com.onthegomap.planetiler.util.RemoteVersioncom.onthegomap.planetiler.reader.remote.HttpRangeFile→com.onthegomap.planetiler.util.ByteRangecom.onthegomap.planetiler.reader.remote.HttpRangeFile→com.onthegomap.planetiler.util.Downloadercom.onthegomap.planetiler.reader.remote.HttpRangeFile→com.onthegomap.planetiler.util.Plancom.onthegomap.planetiler.reader.remote.HttpRangeFile→com.onthegomap.planetiler.util.RangeResponsecom.onthegomap.planetiler.reader.remote.HttpRangeFile→com.onthegomap.planetiler.util.RemoteVersioncom.onthegomap.planetiler.reader.remote.HttpRangeFile→com.onthegomap.planetiler.util.Sinkcom.onthegomap.planetiler.reader.remote.RangeFile→com.onthegomap.planetiler.util.ByteRangecom.onthegomap.planetiler.reader.remote.RangeFile→com.onthegomap.planetiler.util.Downloadercom.onthegomap.planetiler.reader.remote.RangeFile→com.onthegomap.planetiler.util.Plancom.onthegomap.planetiler.reader.remote.RequestedRange→com.onthegomap.planetiler.util.ByteRangecom.onthegomap.planetiler.reader.remote.ResultDispatcher→com.onthegomap.planetiler.util.ByteRangecom.onthegomap.planetiler.reader.remote.ResultDispatcher→com.onthegomap.planetiler.util.Sink
- Direction
- com.onthegomap.planetiler.reader.remote uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.reader.remote, while a change to com.onthegomap.planetiler.reader.remote can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.remote uses a module listed above it, which is the healthy direction.
10→2 com.onthegomap.planetiler.stats uses io.prometheus.client✕
- Connections
- 7 pairs of types, where a type in com.onthegomap.planetiler.stats uses a type in io.prometheus.client.
- The types involved
com.onthegomap.planetiler.stats.2→io.prometheus.client.Collectorcom.onthegomap.planetiler.stats.3→io.prometheus.client.Collectorcom.onthegomap.planetiler.stats.FileSizeCollector→io.prometheus.client.Collectorcom.onthegomap.planetiler.stats.HeapObjectSizeCollector→io.prometheus.client.Collectorcom.onthegomap.planetiler.stats.InProgressTasks→io.prometheus.client.Collectorcom.onthegomap.planetiler.stats.PostGcMemoryCollector→io.prometheus.client.Collectorcom.onthegomap.planetiler.stats.ThreadDetailsExports→io.prometheus.client.Collector
- Direction
- com.onthegomap.planetiler.stats uses io.prometheus.client, so a change to io.prometheus.client can break com.onthegomap.planetiler.stats, while a change to com.onthegomap.planetiler.stats can't break io.prometheus.client.
- Position
- Below the diagonal: com.onthegomap.planetiler.stats uses a module listed above it, which is the healthy direction.
10→7 com.onthegomap.planetiler.stats uses com.onthegomap.planetiler.util✕
- Connections
- 7 pairs of types, where a type in com.onthegomap.planetiler.stats uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.stats.InMemory→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.stats.ProgressLoggers→com.onthegomap.planetiler.util.DiskBackedcom.onthegomap.planetiler.stats.ProgressLoggers→com.onthegomap.planetiler.util.Formatcom.onthegomap.planetiler.stats.ProgressLoggers→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.stats.PrometheusStats→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.stats.Stats→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.stats.Timers→com.onthegomap.planetiler.util.Format
- Direction
- com.onthegomap.planetiler.stats uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.stats, while a change to com.onthegomap.planetiler.stats can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.stats uses a module listed above it, which is the healthy direction.
10→8 com.onthegomap.planetiler.stats uses com.onthegomap.planetiler.worker✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.stats uses a type in com.onthegomap.planetiler.worker.
- The types involved
com.onthegomap.planetiler.stats.ProgressLoggers→com.onthegomap.planetiler.worker.WorkQueuecom.onthegomap.planetiler.stats.ProgressLoggers→com.onthegomap.planetiler.worker.Workercom.onthegomap.planetiler.stats.ProgressLoggers→com.onthegomap.planetiler.worker.WorkerPipeline
- Direction
- com.onthegomap.planetiler.stats uses com.onthegomap.planetiler.worker, so a change to com.onthegomap.planetiler.worker can break com.onthegomap.planetiler.stats, while a change to com.onthegomap.planetiler.stats can't break com.onthegomap.planetiler.worker.
- Position
- Below the diagonal: com.onthegomap.planetiler.stats uses a module listed above it, which is the healthy direction.
11→7 com.onthegomap.planetiler.render uses com.onthegomap.planetiler.util✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.render uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.render.TiledGeometry→com.onthegomap.planetiler.util.Format
- Direction
- com.onthegomap.planetiler.render uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.render, while a change to com.onthegomap.planetiler.render can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.render uses a module listed above it, which is the healthy direction.
11→10 com.onthegomap.planetiler.render uses com.onthegomap.planetiler.stats✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.render uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.render.FeatureRenderer→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.render uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.render, while a change to com.onthegomap.planetiler.render can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.render uses a module listed above it, which is the healthy direction.
11→16 com.onthegomap.planetiler.render uses com.onthegomap.planetiler.geo part of a loop✕
- Connections
- 8 pairs of types, where a type in com.onthegomap.planetiler.render uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.render.1→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.render.CoveredTiles→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.render.CoveredTiles→com.onthegomap.planetiler.geo.TilePredicatecom.onthegomap.planetiler.render.FeatureRenderer→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.render.RenderedFeature→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.render.TiledGeometry→com.onthegomap.planetiler.geo.ForZoomcom.onthegomap.planetiler.render.TiledGeometry→com.onthegomap.planetiler.geo.MutableCoordinateSequencecom.onthegomap.planetiler.render.TiledGeometry→com.onthegomap.planetiler.geo.TileCoord
- Direction
- com.onthegomap.planetiler.render uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.render, while a change to com.onthegomap.planetiler.render can't break com.onthegomap.planetiler.geo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→17 com.onthegomap.planetiler.render uses com.onthegomap.planetiler.config part of a loop✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.render uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.render.FeatureRenderer→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.render uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.render, while a change to com.onthegomap.planetiler.render can't break com.onthegomap.planetiler.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→19 com.onthegomap.planetiler.render uses com.onthegomap.planetiler.collection part of a loop✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.render uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.render.TiledGeometry→com.onthegomap.planetiler.collection.IntRangeSet
- Direction
- com.onthegomap.planetiler.render uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.render, while a change to com.onthegomap.planetiler.render can't break com.onthegomap.planetiler.collection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→21 com.onthegomap.planetiler.render uses com.onthegomap.planetiler part of a loop✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.render uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.render.FeatureRenderer→com.onthegomap.planetiler.Featurecom.onthegomap.planetiler.render.RenderedFeature→com.onthegomap.planetiler.Feature
- Direction
- com.onthegomap.planetiler.render uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.render, while a change to com.onthegomap.planetiler.render can't break com.onthegomap.planetiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→7 com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.util✕
- Connections
- 7 pairs of types, where a type in com.onthegomap.planetiler.reader.osm uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.reader.osm.OsmInputFile→com.onthegomap.planetiler.util.DiskBackedcom.onthegomap.planetiler.reader.osm.OsmPhaser→com.onthegomap.planetiler.util.Formatcom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.util.Formatcom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.util.ResourceUsagecom.onthegomap.planetiler.reader.osm.OsmRelationInfo→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.reader.osm.OsmWaySplitter→com.onthegomap.planetiler.util.HasEstimate
- Direction
- com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.reader.osm, while a change to com.onthegomap.planetiler.reader.osm can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.osm uses a module listed above it, which is the healthy direction.
12→8 com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.worker✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.reader.osm uses a type in com.onthegomap.planetiler.worker.
- The types involved
com.onthegomap.planetiler.reader.osm.1BlockWithResult→com.onthegomap.planetiler.worker.WeightedHandoffQueuecom.onthegomap.planetiler.reader.osm.ForWorker→com.onthegomap.planetiler.worker.RunnableThatThrows
- Direction
- com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.worker, so a change to com.onthegomap.planetiler.worker can break com.onthegomap.planetiler.reader.osm, while a change to com.onthegomap.planetiler.reader.osm can't break com.onthegomap.planetiler.worker.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.osm uses a module listed above it, which is the healthy direction.
12→10 com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.stats✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler.reader.osm uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.reader.osm.ForWorker→com.onthegomap.planetiler.stats.Countercom.onthegomap.planetiler.reader.osm.OsmNodeBoundsProvider→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.reader.osm.OsmPhaser→com.onthegomap.planetiler.stats.MultiThreadCountercom.onthegomap.planetiler.reader.osm.OsmPhaser→com.onthegomap.planetiler.stats.Timercom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.stats.Readablecom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.reader.osm, while a change to com.onthegomap.planetiler.reader.osm can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.osm uses a module listed above it, which is the healthy direction.
12→11 com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.render✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.osm uses a type in com.onthegomap.planetiler.render.
- The types involved
com.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.render.FeatureRenderer
- Direction
- com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.render, so a change to com.onthegomap.planetiler.render can break com.onthegomap.planetiler.reader.osm, while a change to com.onthegomap.planetiler.reader.osm can't break com.onthegomap.planetiler.render.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.osm uses a module listed above it, which is the healthy direction.
12→13 com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.reader part of a loop✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.reader.osm uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.reader.osm.OsmElement→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.reader.osm.OsmFeature→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.reader.SourceFeature
- Direction
- com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler.reader.osm, while a change to com.onthegomap.planetiler.reader.osm can't break com.onthegomap.planetiler.reader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→17 com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.config part of a loop✕
- Connections
- 4 pairs of types, where a type in com.onthegomap.planetiler.reader.osm uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.reader.osm.OsmInputFile→com.onthegomap.planetiler.config.Providercom.onthegomap.planetiler.reader.osm.OsmNodeBoundsProvider→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.reader.osm.OsmNodeBoundsProvider→com.onthegomap.planetiler.config.Providercom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.reader.osm, while a change to com.onthegomap.planetiler.reader.osm can't break com.onthegomap.planetiler.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→19 com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.collection part of a loop✕
- Connections
- 7 pairs of types, where a type in com.onthegomap.planetiler.reader.osm uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.collection.Appendablecom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.collection.FeatureGroupcom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.collection.LongLongMapcom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.collection.Replaceablecom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.collection.SortableFeaturecom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.collection.Storagecom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.collection.Type
- Direction
- com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.reader.osm, while a change to com.onthegomap.planetiler.reader.osm can't break com.onthegomap.planetiler.collection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→21 com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler part of a loop✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.reader.osm uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.Factorycom.onthegomap.planetiler.reader.osm.OsmReader→com.onthegomap.planetiler.Profile
- Direction
- com.onthegomap.planetiler.reader.osm uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.reader.osm, while a change to com.onthegomap.planetiler.reader.osm can't break com.onthegomap.planetiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→8 com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.worker✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader uses a type in com.onthegomap.planetiler.worker.
- The types involved
com.onthegomap.planetiler.reader.SourceFeatureProcessor→com.onthegomap.planetiler.worker.WorkerStep
- Direction
- com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.worker, so a change to com.onthegomap.planetiler.worker can break com.onthegomap.planetiler.reader, while a change to com.onthegomap.planetiler.reader can't break com.onthegomap.planetiler.worker.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader uses a module listed above it, which is the healthy direction.
13→10 com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.stats✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.reader uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.reader.GeoPackageReader→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.reader.NaturalEarthReader→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.reader.SourceFeatureProcessor→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.reader, while a change to com.onthegomap.planetiler.reader can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader uses a module listed above it, which is the healthy direction.
13→11 com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.render✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader uses a type in com.onthegomap.planetiler.render.
- The types involved
com.onthegomap.planetiler.reader.SourceFeatureProcessor→com.onthegomap.planetiler.render.FeatureRenderer
- Direction
- com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.render, so a change to com.onthegomap.planetiler.render can break com.onthegomap.planetiler.reader, while a change to com.onthegomap.planetiler.reader can't break com.onthegomap.planetiler.render.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader uses a module listed above it, which is the healthy direction.
13→12 com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.reader.osm✕
- Connections
- 13 pairs of types, where a type in com.onthegomap.planetiler.reader uses a type in com.onthegomap.planetiler.reader.osm.
- The types involved
com.onthegomap.planetiler.reader.1→com.onthegomap.planetiler.reader.osm.Infocom.onthegomap.planetiler.reader.1→com.onthegomap.planetiler.reader.osm.OsmElementcom.onthegomap.planetiler.reader.1→com.onthegomap.planetiler.reader.osm.Typecom.onthegomap.planetiler.reader.SimpleFeature→com.onthegomap.planetiler.reader.osm.Infocom.onthegomap.planetiler.reader.SimpleFeature→com.onthegomap.planetiler.reader.osm.OsmRelationInfocom.onthegomap.planetiler.reader.SimpleFeature→com.onthegomap.planetiler.reader.osm.RelationMembercom.onthegomap.planetiler.reader.SimpleOsmFeature→com.onthegomap.planetiler.reader.osm.Infocom.onthegomap.planetiler.reader.SimpleOsmFeature→com.onthegomap.planetiler.reader.osm.OsmElementcom.onthegomap.planetiler.reader.SimpleOsmFeature→com.onthegomap.planetiler.reader.osm.OsmRelationInfocom.onthegomap.planetiler.reader.SimpleOsmFeature→com.onthegomap.planetiler.reader.osm.OsmSourceFeaturecom.onthegomap.planetiler.reader.SimpleOsmFeature→com.onthegomap.planetiler.reader.osm.RelationMembercom.onthegomap.planetiler.reader.SourceFeature→com.onthegomap.planetiler.reader.osm.OsmRelationInfocom.onthegomap.planetiler.reader.SourceFeature→com.onthegomap.planetiler.reader.osm.RelationMember
- Direction
- com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.reader.osm, so a change to com.onthegomap.planetiler.reader.osm can break com.onthegomap.planetiler.reader, while a change to com.onthegomap.planetiler.reader can't break com.onthegomap.planetiler.reader.osm.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader uses a module listed above it, which is the healthy direction.
13→16 com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.geo part of a loop✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.reader.SourceFeature→com.onthegomap.planetiler.geo.WithGeometry
- Direction
- com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.reader, while a change to com.onthegomap.planetiler.reader can't break com.onthegomap.planetiler.geo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→17 com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.config part of a loop✕
- Connections
- 4 pairs of types, where a type in com.onthegomap.planetiler.reader uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.reader.GeoPackageReader→com.onthegomap.planetiler.config.Boundscom.onthegomap.planetiler.reader.GeoPackageReader→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.reader.NaturalEarthReader→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.reader.SourceFeatureProcessor→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.reader, while a change to com.onthegomap.planetiler.reader can't break com.onthegomap.planetiler.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→19 com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.collection part of a loop✕
- Connections
- 4 pairs of types, where a type in com.onthegomap.planetiler.reader uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.reader.GeoPackageReader→com.onthegomap.planetiler.collection.FeatureGroupcom.onthegomap.planetiler.reader.NaturalEarthReader→com.onthegomap.planetiler.collection.FeatureGroupcom.onthegomap.planetiler.reader.SourceFeatureProcessor→com.onthegomap.planetiler.collection.FeatureGroupcom.onthegomap.planetiler.reader.SourceFeatureProcessor→com.onthegomap.planetiler.collection.SortableFeature
- Direction
- com.onthegomap.planetiler.reader uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.reader, while a change to com.onthegomap.planetiler.reader can't break com.onthegomap.planetiler.collection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→21 com.onthegomap.planetiler.reader uses com.onthegomap.planetiler part of a loop✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.reader uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.reader.GeoPackageReader→com.onthegomap.planetiler.Profilecom.onthegomap.planetiler.reader.NaturalEarthReader→com.onthegomap.planetiler.Profilecom.onthegomap.planetiler.reader.SourceFeatureProcessor→com.onthegomap.planetiler.Profile
- Direction
- com.onthegomap.planetiler.reader uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.reader, while a change to com.onthegomap.planetiler.reader can't break com.onthegomap.planetiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→13 com.onthegomap.planetiler.expression uses com.onthegomap.planetiler.reader✕
- Connections
- 20 pairs of types, where a type in com.onthegomap.planetiler.expression uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.expression.And→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.Constant→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.DataType→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.EmptyIndex→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.Expression→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.GeometryTypeIndex→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.Index→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.KeyIndex→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.MatchAny→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.MatchField→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.MatchSource→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.MatchSourceLayer→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.MatchType→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.Not→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.Or→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.PartialInput→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.SourceIndex→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.SourceLayerIndex→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.StringFieldIndex→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.expression.TypedGetter→com.onthegomap.planetiler.reader.WithTags
- Direction
- com.onthegomap.planetiler.expression uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler.expression, while a change to com.onthegomap.planetiler.expression can't break com.onthegomap.planetiler.reader.
- Position
- Below the diagonal: com.onthegomap.planetiler.expression uses a module listed above it, which is the healthy direction.
14→16 com.onthegomap.planetiler.expression uses com.onthegomap.planetiler.geo part of a loop✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.expression uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.expression.Expression→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.expression.PartialInput→com.onthegomap.planetiler.geo.GeometryType
- Direction
- com.onthegomap.planetiler.expression uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.expression, while a change to com.onthegomap.planetiler.expression can't break com.onthegomap.planetiler.geo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→7 com.onthegomap.planetiler.custommap.expression uses com.onthegomap.planetiler.util✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.custommap.expression uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.custommap.expression.ConfigExpressionScript→com.onthegomap.planetiler.util.Memoizedcom.onthegomap.planetiler.custommap.expression.ConfigExpressionScript→com.onthegomap.planetiler.util.Try
- Direction
- com.onthegomap.planetiler.custommap.expression uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.custommap.expression, while a change to com.onthegomap.planetiler.custommap.expression can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.expression uses a module listed above it, which is the healthy direction.
15→13 com.onthegomap.planetiler.custommap.expression uses com.onthegomap.planetiler.reader✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.custommap.expression uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.custommap.expression.BooleanExpressionScript→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.custommap.expression.ConfigExpression→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.custommap.expression.ScriptContext→com.onthegomap.planetiler.reader.WithTags
- Direction
- com.onthegomap.planetiler.custommap.expression uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler.custommap.expression, while a change to com.onthegomap.planetiler.custommap.expression can't break com.onthegomap.planetiler.reader.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.expression uses a module listed above it, which is the healthy direction.
15→14 com.onthegomap.planetiler.custommap.expression uses com.onthegomap.planetiler.expression✕
- Connections
- 7 pairs of types, where a type in com.onthegomap.planetiler.custommap.expression uses a type in com.onthegomap.planetiler.expression.
- The types involved
com.onthegomap.planetiler.custommap.expression.BooleanExpressionScript→com.onthegomap.planetiler.expression.Expressioncom.onthegomap.planetiler.custommap.expression.Cast→com.onthegomap.planetiler.expression.DataTypecom.onthegomap.planetiler.custommap.expression.ConfigExpression→com.onthegomap.planetiler.expression.DataTypecom.onthegomap.planetiler.custommap.expression.ConfigExpression→com.onthegomap.planetiler.expression.MultiExpressioncom.onthegomap.planetiler.custommap.expression.ConfigExpression→com.onthegomap.planetiler.expression.Simplifiablecom.onthegomap.planetiler.custommap.expression.ConfigExpression→com.onthegomap.planetiler.expression.TypedGettercom.onthegomap.planetiler.custommap.expression.Match→com.onthegomap.planetiler.expression.MultiExpression
- Direction
- com.onthegomap.planetiler.custommap.expression uses com.onthegomap.planetiler.expression, so a change to com.onthegomap.planetiler.expression can break com.onthegomap.planetiler.custommap.expression, while a change to com.onthegomap.planetiler.custommap.expression can't break com.onthegomap.planetiler.expression.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.expression uses a module listed above it, which is the healthy direction.
15→31 com.onthegomap.planetiler.custommap.expression uses com.onthegomap.planetiler.custommap part of a loop✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.custommap.expression uses a type in com.onthegomap.planetiler.custommap.
- The types involved
com.onthegomap.planetiler.custommap.expression.ScriptContext→com.onthegomap.planetiler.custommap.TagValueProducercom.onthegomap.planetiler.custommap.expression.ScriptEnvironment→com.onthegomap.planetiler.custommap.Root
- Direction
- com.onthegomap.planetiler.custommap.expression uses com.onthegomap.planetiler.custommap, so a change to com.onthegomap.planetiler.custommap can break com.onthegomap.planetiler.custommap.expression, while a change to com.onthegomap.planetiler.custommap.expression can't break com.onthegomap.planetiler.custommap.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→7 com.onthegomap.planetiler.geo uses com.onthegomap.planetiler.util✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.geo uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.geo.Base→com.onthegomap.planetiler.util.ToDoubleFunctionThatThrowscom.onthegomap.planetiler.geo.GeometryPipeline→com.onthegomap.planetiler.util.ZoomFunction
- Direction
- com.onthegomap.planetiler.geo uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.geo, while a change to com.onthegomap.planetiler.geo can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.geo uses a module listed above it, which is the healthy direction.
16→10 com.onthegomap.planetiler.geo uses com.onthegomap.planetiler.stats✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.geo uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.geo.GeoUtils→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.geo.GeometryException→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.geo uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.geo, while a change to com.onthegomap.planetiler.geo can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.geo uses a module listed above it, which is the healthy direction.
16→13 com.onthegomap.planetiler.geo uses com.onthegomap.planetiler.reader✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.geo uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.geo.WithGeometry→com.onthegomap.planetiler.reader.WithGeometryType
- Direction
- com.onthegomap.planetiler.geo uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler.geo, while a change to com.onthegomap.planetiler.geo can't break com.onthegomap.planetiler.reader.
- Position
- Below the diagonal: com.onthegomap.planetiler.geo uses a module listed above it, which is the healthy direction.
16→14 com.onthegomap.planetiler.geo uses com.onthegomap.planetiler.expression✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.geo uses a type in com.onthegomap.planetiler.expression.
- The types involved
com.onthegomap.planetiler.geo.GeometryType→com.onthegomap.planetiler.expression.Expression
- Direction
- com.onthegomap.planetiler.geo uses com.onthegomap.planetiler.expression, so a change to com.onthegomap.planetiler.expression can break com.onthegomap.planetiler.geo, while a change to com.onthegomap.planetiler.geo can't break com.onthegomap.planetiler.expression.
- Position
- Below the diagonal: com.onthegomap.planetiler.geo uses a module listed above it, which is the healthy direction.
16→21 com.onthegomap.planetiler.geo uses com.onthegomap.planetiler part of a loop✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.geo uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.geo.GeometryPipeline→com.onthegomap.planetiler.Feature
- Direction
- com.onthegomap.planetiler.geo uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.geo, while a change to com.onthegomap.planetiler.geo can't break com.onthegomap.planetiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→10 com.onthegomap.planetiler.config uses com.onthegomap.planetiler.stats✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.config uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.config.Arguments→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.config uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.config, while a change to com.onthegomap.planetiler.config can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.config uses a module listed above it, which is the healthy direction.
17→16 com.onthegomap.planetiler.config uses com.onthegomap.planetiler.geo✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.config uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.config.Bounds→com.onthegomap.planetiler.geo.TileExtents
- Direction
- com.onthegomap.planetiler.config uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.config, while a change to com.onthegomap.planetiler.config can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.config uses a module listed above it, which is the healthy direction.
17→20 com.onthegomap.planetiler.config uses com.onthegomap.planetiler.archive part of a loop✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.config uses a type in com.onthegomap.planetiler.archive.
- The types involved
com.onthegomap.planetiler.config.PlanetilerConfig→com.onthegomap.planetiler.archive.TileCompressioncom.onthegomap.planetiler.config.PlanetilerConfig→com.onthegomap.planetiler.archive.TileFormat
- Direction
- com.onthegomap.planetiler.config uses com.onthegomap.planetiler.archive, so a change to com.onthegomap.planetiler.archive can break com.onthegomap.planetiler.config, while a change to com.onthegomap.planetiler.config can't break com.onthegomap.planetiler.archive.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→7 com.onthegomap.planetiler.custommap.expression.stdlib uses com.onthegomap.planetiler.util✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.custommap.expression.stdlib uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.custommap.expression.stdlib.Field→com.onthegomap.planetiler.util.FunctionThatThrowscom.onthegomap.planetiler.custommap.expression.stdlib.GeometryVal→com.onthegomap.planetiler.util.FunctionThatThrowscom.onthegomap.planetiler.custommap.expression.stdlib.GeometryVal→com.onthegomap.planetiler.util.ToDoubleFunctionThatThrows
- Direction
- com.onthegomap.planetiler.custommap.expression.stdlib uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.custommap.expression.stdlib, while a change to com.onthegomap.planetiler.custommap.expression.stdlib can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.expression.stdlib uses a module listed above it, which is the healthy direction.
18→16 com.onthegomap.planetiler.custommap.expression.stdlib uses com.onthegomap.planetiler.geo✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.custommap.expression.stdlib uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.custommap.expression.stdlib.Field→com.onthegomap.planetiler.geo.WithGeometrycom.onthegomap.planetiler.custommap.expression.stdlib.GeometryVal→com.onthegomap.planetiler.geo.WithGeometry
- Direction
- com.onthegomap.planetiler.custommap.expression.stdlib uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.custommap.expression.stdlib, while a change to com.onthegomap.planetiler.custommap.expression.stdlib can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.expression.stdlib uses a module listed above it, which is the healthy direction.
19→7 com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.util✕
- Connections
- 19 pairs of types, where a type in com.onthegomap.planetiler.collection uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.collection.AppendStore→com.onthegomap.planetiler.util.DiskBackedcom.onthegomap.planetiler.collection.AppendStore→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.collection.ArrayLongLongMapMmap→com.onthegomap.planetiler.util.SlidingWindowcom.onthegomap.planetiler.collection.BenchmarkExternalMergeSort→com.onthegomap.planetiler.util.Formatcom.onthegomap.planetiler.collection.ExternalMergeSort→com.onthegomap.planetiler.util.CloseableConsumercom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.util.AsBytecom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.util.CloseableConsumercom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.util.CommonStringEncodercom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.util.DiskBackedcom.onthegomap.planetiler.collection.FeatureSort→com.onthegomap.planetiler.util.CloseableConsumercom.onthegomap.planetiler.collection.FeatureSort→com.onthegomap.planetiler.util.DiskBackedcom.onthegomap.planetiler.collection.FeatureSort→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.collection.LongLongMap→com.onthegomap.planetiler.util.DiskBackedcom.onthegomap.planetiler.collection.LongLongMap→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.collection.LongLongMultimap→com.onthegomap.planetiler.util.DiskBackedcom.onthegomap.planetiler.collection.LongLongMultimap→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.collection.SparseMonotonicLongMap→com.onthegomap.planetiler.util.HasEstimatecom.onthegomap.planetiler.collection.ThreadLocalWriter→com.onthegomap.planetiler.util.CloseableConsumercom.onthegomap.planetiler.collection.TileFeatures→com.onthegomap.planetiler.util.Updater
- Direction
- com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.collection, while a change to com.onthegomap.planetiler.collection can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.collection uses a module listed above it, which is the healthy direction.
19→8 com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.worker✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.collection uses a type in com.onthegomap.planetiler.worker.
- The types involved
com.onthegomap.planetiler.collection.ParallelIterator→com.onthegomap.planetiler.worker.Worker
- Direction
- com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.worker, so a change to com.onthegomap.planetiler.worker can break com.onthegomap.planetiler.collection, while a change to com.onthegomap.planetiler.collection can't break com.onthegomap.planetiler.worker.
- Position
- Below the diagonal: com.onthegomap.planetiler.collection uses a module listed above it, which is the healthy direction.
19→10 com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.stats✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.collection uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.collection.ExternalMergeSort→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.collection.FeatureSort→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.collection, while a change to com.onthegomap.planetiler.collection can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.collection uses a module listed above it, which is the healthy direction.
19→11 com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.render✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.collection uses a type in com.onthegomap.planetiler.render.
- The types involved
com.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.render.Groupcom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.render.RenderedFeature
- Direction
- com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.render, so a change to com.onthegomap.planetiler.render can break com.onthegomap.planetiler.collection, while a change to com.onthegomap.planetiler.collection can't break com.onthegomap.planetiler.render.
- Position
- Below the diagonal: com.onthegomap.planetiler.collection uses a module listed above it, which is the healthy direction.
19→16 com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.geo✕
- Connections
- 4 pairs of types, where a type in com.onthegomap.planetiler.collection uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.geo.TileOrdercom.onthegomap.planetiler.collection.TileFeatures→com.onthegomap.planetiler.geo.TileCoord
- Direction
- com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.collection, while a change to com.onthegomap.planetiler.collection can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.collection uses a module listed above it, which is the healthy direction.
19→17 com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.config✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.collection uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.collection.BenchmarkExternalMergeSort→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.collection.ExternalMergeSort→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.collection uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.collection, while a change to com.onthegomap.planetiler.collection can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.collection uses a module listed above it, which is the healthy direction.
19→21 com.onthegomap.planetiler.collection uses com.onthegomap.planetiler part of a loop✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler.collection uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.Featurecom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.Profilecom.onthegomap.planetiler.collection.FeatureGroup→com.onthegomap.planetiler.VectorGeometrycom.onthegomap.planetiler.collection.TileFeatures→com.onthegomap.planetiler.Featurecom.onthegomap.planetiler.collection.TileFeatures→com.onthegomap.planetiler.VectorTile
- Direction
- com.onthegomap.planetiler.collection uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.collection, while a change to com.onthegomap.planetiler.collection can't break com.onthegomap.planetiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→7 com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.util✕
- Connections
- 9 pairs of types, where a type in com.onthegomap.planetiler.archive uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.archive.Encoded→com.onthegomap.planetiler.util.LayerStatscom.onthegomap.planetiler.archive.InternalMapMixin→com.onthegomap.planetiler.util.VectorLayercom.onthegomap.planetiler.archive.ReadableTileArchive→com.onthegomap.planetiler.util.CloseableIteratorcom.onthegomap.planetiler.archive.TileArchiveMetadata→com.onthegomap.planetiler.util.VectorLayercom.onthegomap.planetiler.archive.TileArchiveMetadataJson→com.onthegomap.planetiler.util.VectorLayercom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.util.DiskBackedcom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.util.LayerAttrStatscom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.util.TilesetSummaryStatisticscom.onthegomap.planetiler.archive.VectorLayersToStringSerializer→com.onthegomap.planetiler.util.VectorLayer
- Direction
- com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.archive, while a change to com.onthegomap.planetiler.archive can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.archive uses a module listed above it, which is the healthy direction.
20→8 com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.worker✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.archive uses a type in com.onthegomap.planetiler.worker.
- The types involved
com.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.worker.SinkStep
- Direction
- com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.worker, so a change to com.onthegomap.planetiler.worker can break com.onthegomap.planetiler.archive, while a change to com.onthegomap.planetiler.archive can't break com.onthegomap.planetiler.worker.
- Position
- Below the diagonal: com.onthegomap.planetiler.archive uses a module listed above it, which is the healthy direction.
20→10 com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.stats✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler.archive uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.archive.JavaMltTileEncoder→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.stats.Countercom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.stats.Readablecom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.archive.TileEncoder→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.archive, while a change to com.onthegomap.planetiler.archive can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.archive uses a module listed above it, which is the healthy direction.
20→16 com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.geo✕
- Connections
- 7 pairs of types, where a type in com.onthegomap.planetiler.archive uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.archive.1→com.onthegomap.planetiler.geo.TileOrdercom.onthegomap.planetiler.archive.Format→com.onthegomap.planetiler.geo.TileOrdercom.onthegomap.planetiler.archive.ReadableTileArchive→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.archive.Tile→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.archive.TileEncodingResult→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.archive.WriteableTileArchive→com.onthegomap.planetiler.geo.TileOrder
- Direction
- com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.archive, while a change to com.onthegomap.planetiler.archive can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.archive uses a module listed above it, which is the healthy direction.
20→17 com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.config✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler.archive uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.archive.JavaMltTileEncoder→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.archive.TileArchiveConfig→com.onthegomap.planetiler.config.Argumentscom.onthegomap.planetiler.archive.TileArchiveMetadata→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.archive.TileArchives→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.archive.TileEncoder→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.archive, while a change to com.onthegomap.planetiler.archive can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.archive uses a module listed above it, which is the healthy direction.
20→19 com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.collection✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.archive uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.collection.FeatureGroupcom.onthegomap.planetiler.archive.TileArchiveWriter→com.onthegomap.planetiler.collection.TileFeaturescom.onthegomap.planetiler.archive.TileBatch→com.onthegomap.planetiler.collection.TileFeatures
- Direction
- com.onthegomap.planetiler.archive uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.archive, while a change to com.onthegomap.planetiler.archive can't break com.onthegomap.planetiler.collection.
- Position
- Below the diagonal: com.onthegomap.planetiler.archive uses a module listed above it, which is the healthy direction.
20→21 com.onthegomap.planetiler.archive uses com.onthegomap.planetiler part of a loop✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler.archive uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.archive.JavaMltTileEncoder→com.onthegomap.planetiler.VectorTilecom.onthegomap.planetiler.archive.MltInputBuilder→com.onthegomap.planetiler.FeatureVisitorcom.onthegomap.planetiler.archive.MltInputBuilder→com.onthegomap.planetiler.VectorGeometrycom.onthegomap.planetiler.archive.MvtTileEncoder→com.onthegomap.planetiler.VectorTilecom.onthegomap.planetiler.archive.TileArchiveMetadata→com.onthegomap.planetiler.Profilecom.onthegomap.planetiler.archive.TileEncoder→com.onthegomap.planetiler.VectorTile
- Direction
- com.onthegomap.planetiler.archive uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.archive, while a change to com.onthegomap.planetiler.archive can't break com.onthegomap.planetiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→7 com.onthegomap.planetiler uses com.onthegomap.planetiler.util✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.Feature→com.onthegomap.planetiler.util.CacheByZoomcom.onthegomap.planetiler.Feature→com.onthegomap.planetiler.util.ZoomFunctioncom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.util.Downloadercom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.util.OvertureStaccom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.util.Translationscom.onthegomap.planetiler.VectorTile→com.onthegomap.planetiler.util.ForZoom
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→8 com.onthegomap.planetiler uses com.onthegomap.planetiler.worker✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.worker.
- The types involved
com.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.worker.RunnableThatThrowscom.onthegomap.planetiler.Stage→com.onthegomap.planetiler.worker.RunnableThatThrows
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.worker, so a change to com.onthegomap.planetiler.worker can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.worker.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→9 com.onthegomap.planetiler uses com.onthegomap.planetiler.reader.remote✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.reader.remote.
- The types involved
com.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.reader.remote.DownloadModecom.onthegomap.planetiler.SourceArgs→com.onthegomap.planetiler.reader.remote.DownloadMode
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.reader.remote, so a change to com.onthegomap.planetiler.reader.remote can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.reader.remote.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→10 com.onthegomap.planetiler uses com.onthegomap.planetiler.stats✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.Factory→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.FeatureCollector→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.FeatureMerge→com.onthegomap.planetiler.stats.Statscom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.stats.Finishablecom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→12 com.onthegomap.planetiler uses com.onthegomap.planetiler.reader.osm✕
- Connections
- 14 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.reader.osm.
- The types involved
com.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.reader.osm.Nodecom.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.reader.osm.OsmRelationInfocom.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.reader.osm.Relationcom.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.reader.osm.Waycom.onthegomap.planetiler.OsmNodePreprocessor→com.onthegomap.planetiler.reader.osm.Nodecom.onthegomap.planetiler.OsmRelationPreprocessor→com.onthegomap.planetiler.reader.osm.OsmRelationInfocom.onthegomap.planetiler.OsmRelationPreprocessor→com.onthegomap.planetiler.reader.osm.Relationcom.onthegomap.planetiler.OsmWayPreprocessor→com.onthegomap.planetiler.reader.osm.Waycom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.reader.osm.OsmInputFilecom.onthegomap.planetiler.Profile→com.onthegomap.planetiler.reader.osm.Nodecom.onthegomap.planetiler.Profile→com.onthegomap.planetiler.reader.osm.OsmElementcom.onthegomap.planetiler.Profile→com.onthegomap.planetiler.reader.osm.OsmRelationInfocom.onthegomap.planetiler.Profile→com.onthegomap.planetiler.reader.osm.Relationcom.onthegomap.planetiler.Profile→com.onthegomap.planetiler.reader.osm.Way
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.reader.osm, so a change to com.onthegomap.planetiler.reader.osm can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.reader.osm.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→13 com.onthegomap.planetiler uses com.onthegomap.planetiler.reader✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.Factory→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.Feature→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.FeatureCollector→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.NullProfile→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.reader.ShapefileOptions
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.reader.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→14 com.onthegomap.planetiler uses com.onthegomap.planetiler.expression✕
- Connections
- 4 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.expression.
- The types involved
com.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.expression.Entrycom.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.expression.Indexcom.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.expression.PartialInputcom.onthegomap.planetiler.Profile→com.onthegomap.planetiler.expression.PartialInput
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.expression, so a change to com.onthegomap.planetiler.expression can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.expression.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→16 com.onthegomap.planetiler uses com.onthegomap.planetiler.geo✕
- Connections
- 12 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.CommandEncoder→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.Feature→com.onthegomap.planetiler.geo.GeometryPipelinecom.onthegomap.planetiler.Feature→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.Feature→com.onthegomap.planetiler.geo.SimplifyMethodcom.onthegomap.planetiler.FeatureMerge→com.onthegomap.planetiler.geo.GeometryPipelinecom.onthegomap.planetiler.FeatureMerge→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.Profile→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.TilePostProcessor→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.VectorGeometry→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.VectorGeometryMerger→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.VectorTile→com.onthegomap.planetiler.geo.GeometryType
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→17 com.onthegomap.planetiler uses com.onthegomap.planetiler.config✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.Factory→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.FeatureCollector→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.ForwardingProfile→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.config.Argumentscom.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→19 com.onthegomap.planetiler uses com.onthegomap.planetiler.collection✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.collection.FeatureGroup
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.collection.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
21→20 com.onthegomap.planetiler uses com.onthegomap.planetiler.archive✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler uses a type in com.onthegomap.planetiler.archive.
- The types involved
com.onthegomap.planetiler.Planetiler→com.onthegomap.planetiler.archive.TileArchiveConfig
- Direction
- com.onthegomap.planetiler uses com.onthegomap.planetiler.archive, so a change to com.onthegomap.planetiler.archive can break com.onthegomap.planetiler, while a change to com.onthegomap.planetiler can't break com.onthegomap.planetiler.archive.
- Position
- Below the diagonal: com.onthegomap.planetiler uses a module listed above it, which is the healthy direction.
22→7 com.onthegomap.planetiler.files uses com.onthegomap.planetiler.util✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.files uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.files.ReadableFilesArchive→com.onthegomap.planetiler.util.CloseableIterator
- Direction
- com.onthegomap.planetiler.files uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.files, while a change to com.onthegomap.planetiler.files can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.files uses a module listed above it, which is the healthy direction.
22→10 com.onthegomap.planetiler.files uses com.onthegomap.planetiler.stats✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.files uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.files.TileFilesWriter→com.onthegomap.planetiler.stats.Countercom.onthegomap.planetiler.files.WriteableFilesArchive→com.onthegomap.planetiler.stats.MultiThreadCounter
- Direction
- com.onthegomap.planetiler.files uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.files, while a change to com.onthegomap.planetiler.files can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.files uses a module listed above it, which is the healthy direction.
22→16 com.onthegomap.planetiler.files uses com.onthegomap.planetiler.geo✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler.files uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.files.ReadableFilesArchive→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.files.TileFilesWriter→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.files.TileSchemeEncoding→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.files.TileSchemeEncoding→com.onthegomap.planetiler.geo.TileOrdercom.onthegomap.planetiler.files.WriteableFilesArchive→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.files.WriteableFilesArchive→com.onthegomap.planetiler.geo.TileOrder
- Direction
- com.onthegomap.planetiler.files uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.files, while a change to com.onthegomap.planetiler.files can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.files uses a module listed above it, which is the healthy direction.
22→17 com.onthegomap.planetiler.files uses com.onthegomap.planetiler.config✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.files uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.files.FilesArchiveUtils→com.onthegomap.planetiler.config.Argumentscom.onthegomap.planetiler.files.ReadableFilesArchive→com.onthegomap.planetiler.config.Argumentscom.onthegomap.planetiler.files.WriteableFilesArchive→com.onthegomap.planetiler.config.Arguments
- Direction
- com.onthegomap.planetiler.files uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.files, while a change to com.onthegomap.planetiler.files can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.files uses a module listed above it, which is the healthy direction.
22→20 com.onthegomap.planetiler.files uses com.onthegomap.planetiler.archive✕
- Connections
- 7 pairs of types, where a type in com.onthegomap.planetiler.files uses a type in com.onthegomap.planetiler.archive.
- The types involved
com.onthegomap.planetiler.files.ReadableFilesArchive→com.onthegomap.planetiler.archive.ReadableTileArchivecom.onthegomap.planetiler.files.ReadableFilesArchive→com.onthegomap.planetiler.archive.TileArchiveMetadatacom.onthegomap.planetiler.files.TileFilesWriter→com.onthegomap.planetiler.archive.TileEncodingResultcom.onthegomap.planetiler.files.TileFilesWriter→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.files.WriteableFilesArchive→com.onthegomap.planetiler.archive.TileArchiveMetadatacom.onthegomap.planetiler.files.WriteableFilesArchive→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.files.WriteableFilesArchive→com.onthegomap.planetiler.archive.WriteableTileArchive
- Direction
- com.onthegomap.planetiler.files uses com.onthegomap.planetiler.archive, so a change to com.onthegomap.planetiler.archive can break com.onthegomap.planetiler.files, while a change to com.onthegomap.planetiler.files can't break com.onthegomap.planetiler.archive.
- Position
- Below the diagonal: com.onthegomap.planetiler.files uses a module listed above it, which is the healthy direction.
23→7 com.onthegomap.planetiler.pmtiles uses com.onthegomap.planetiler.util✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.pmtiles uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.pmtiles.JsonMetadata→com.onthegomap.planetiler.util.VectorLayercom.onthegomap.planetiler.pmtiles.ReadablePmtiles→com.onthegomap.planetiler.util.CloseableIteratorcom.onthegomap.planetiler.pmtiles.WriteablePmtiles→com.onthegomap.planetiler.util.SeekableInMemoryByteChannel
- Direction
- com.onthegomap.planetiler.pmtiles uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.pmtiles, while a change to com.onthegomap.planetiler.pmtiles can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.pmtiles uses a module listed above it, which is the healthy direction.
23→16 com.onthegomap.planetiler.pmtiles uses com.onthegomap.planetiler.geo✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.pmtiles uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.pmtiles.ReadablePmtiles→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.pmtiles.WriteablePmtiles→com.onthegomap.planetiler.geo.TileOrder
- Direction
- com.onthegomap.planetiler.pmtiles uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.pmtiles, while a change to com.onthegomap.planetiler.pmtiles can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.pmtiles uses a module listed above it, which is the healthy direction.
23→20 com.onthegomap.planetiler.pmtiles uses com.onthegomap.planetiler.archive✕
- Connections
- 8 pairs of types, where a type in com.onthegomap.planetiler.pmtiles uses a type in com.onthegomap.planetiler.archive.
- The types involved
com.onthegomap.planetiler.pmtiles.DeduplicatingTileWriter→com.onthegomap.planetiler.archive.TileEncodingResultcom.onthegomap.planetiler.pmtiles.DeduplicatingTileWriter→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.pmtiles.ReadablePmtiles→com.onthegomap.planetiler.archive.ReadableTileArchivecom.onthegomap.planetiler.pmtiles.ReadablePmtiles→com.onthegomap.planetiler.archive.Tilecom.onthegomap.planetiler.pmtiles.ReadablePmtiles→com.onthegomap.planetiler.archive.TileArchiveMetadatacom.onthegomap.planetiler.pmtiles.WriteablePmtiles→com.onthegomap.planetiler.archive.TileArchiveMetadatacom.onthegomap.planetiler.pmtiles.WriteablePmtiles→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.pmtiles.WriteablePmtiles→com.onthegomap.planetiler.archive.WriteableTileArchive
- Direction
- com.onthegomap.planetiler.pmtiles uses com.onthegomap.planetiler.archive, so a change to com.onthegomap.planetiler.archive can break com.onthegomap.planetiler.pmtiles, while a change to com.onthegomap.planetiler.pmtiles can't break com.onthegomap.planetiler.archive.
- Position
- Below the diagonal: com.onthegomap.planetiler.pmtiles uses a module listed above it, which is the healthy direction.
24→7 com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.util✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.stream uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.stream.WriteableProtoStreamArchive→com.onthegomap.planetiler.util.VectorLayer
- Direction
- com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.stream, while a change to com.onthegomap.planetiler.stream can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.stream uses a module listed above it, which is the healthy direction.
24→10 com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.stats✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.stream uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.stream.WriteableStreamArchive→com.onthegomap.planetiler.stats.MultiThreadCounter
- Direction
- com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.stream, while a change to com.onthegomap.planetiler.stream can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.stream uses a module listed above it, which is the healthy direction.
24→16 com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.geo✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.stream uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.stream.WriteableStreamArchive→com.onthegomap.planetiler.geo.TileOrder
- Direction
- com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.stream, while a change to com.onthegomap.planetiler.stream can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.stream uses a module listed above it, which is the healthy direction.
24→17 com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.config✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.stream uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.stream.StreamArchiveConfig→com.onthegomap.planetiler.config.Argumentscom.onthegomap.planetiler.stream.StreamArchiveConfig→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.stream.StreamArchiveUtils→com.onthegomap.planetiler.config.Arguments
- Direction
- com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.stream, while a change to com.onthegomap.planetiler.stream can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.stream uses a module listed above it, which is the healthy direction.
24→20 com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.archive✕
- Connections
- 16 pairs of types, where a type in com.onthegomap.planetiler.stream uses a type in com.onthegomap.planetiler.archive.
- The types involved
com.onthegomap.planetiler.stream.CsvTileWriter→com.onthegomap.planetiler.archive.TileEncodingResultcom.onthegomap.planetiler.stream.CsvTileWriter→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.stream.FinishEntry→com.onthegomap.planetiler.archive.TileArchiveMetadatacom.onthegomap.planetiler.stream.JsonTileWriter→com.onthegomap.planetiler.archive.TileEncodingResultcom.onthegomap.planetiler.stream.JsonTileWriter→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.stream.ProtoTileArchiveWriter→com.onthegomap.planetiler.archive.TileEncodingResultcom.onthegomap.planetiler.stream.ProtoTileArchiveWriter→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.stream.StreamArchiveUtils→com.onthegomap.planetiler.archive.Formatcom.onthegomap.planetiler.stream.WriteableCsvArchive→com.onthegomap.planetiler.archive.Formatcom.onthegomap.planetiler.stream.WriteableCsvArchive→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.stream.WriteableJsonStreamArchive→com.onthegomap.planetiler.archive.TileArchiveMetadatacom.onthegomap.planetiler.stream.WriteableJsonStreamArchive→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.stream.WriteableProtoStreamArchive→com.onthegomap.planetiler.archive.TileArchiveMetadatacom.onthegomap.planetiler.stream.WriteableProtoStreamArchive→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.stream.WriteableStreamArchive→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.stream.WriteableStreamArchive→com.onthegomap.planetiler.archive.WriteableTileArchive
- Direction
- com.onthegomap.planetiler.stream uses com.onthegomap.planetiler.archive, so a change to com.onthegomap.planetiler.archive can break com.onthegomap.planetiler.stream, while a change to com.onthegomap.planetiler.stream can't break com.onthegomap.planetiler.archive.
- Position
- Below the diagonal: com.onthegomap.planetiler.stream uses a module listed above it, which is the healthy direction.
25→14 com.onthegomap.planetiler.custommap.configschema uses com.onthegomap.planetiler.expression✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.custommap.configschema uses a type in com.onthegomap.planetiler.expression.
- The types involved
com.onthegomap.planetiler.custommap.configschema.FeatureGeometry→com.onthegomap.planetiler.expression.Expression
- Direction
- com.onthegomap.planetiler.custommap.configschema uses com.onthegomap.planetiler.expression, so a change to com.onthegomap.planetiler.expression can break com.onthegomap.planetiler.custommap.configschema, while a change to com.onthegomap.planetiler.custommap.configschema can't break com.onthegomap.planetiler.expression.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.configschema uses a module listed above it, which is the healthy direction.
25→16 com.onthegomap.planetiler.custommap.configschema uses com.onthegomap.planetiler.geo✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.custommap.configschema uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.custommap.configschema.FeatureGeometry→com.onthegomap.planetiler.geo.GeometryType
- Direction
- com.onthegomap.planetiler.custommap.configschema uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.custommap.configschema, while a change to com.onthegomap.planetiler.custommap.configschema can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.configschema uses a module listed above it, which is the healthy direction.
25→21 com.onthegomap.planetiler.custommap.configschema uses com.onthegomap.planetiler✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.custommap.configschema uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.custommap.configschema.FeatureGeometry→com.onthegomap.planetiler.Featurecom.onthegomap.planetiler.custommap.configschema.FeatureGeometry→com.onthegomap.planetiler.FeatureCollector
- Direction
- com.onthegomap.planetiler.custommap.configschema uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.custommap.configschema, while a change to com.onthegomap.planetiler.custommap.configschema can't break com.onthegomap.planetiler.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.configschema uses a module listed above it, which is the healthy direction.
26→7 com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler.util✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.mbtiles uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.util.CloseableIteratorcom.onthegomap.planetiler.mbtiles.QueryIterator→com.onthegomap.planetiler.util.CloseableIterator
- Direction
- com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.mbtiles, while a change to com.onthegomap.planetiler.mbtiles can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.mbtiles uses a module listed above it, which is the healthy direction.
26→16 com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler.geo✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler.mbtiles uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.geo.TileOrdercom.onthegomap.planetiler.mbtiles.TileShallowEntry→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.mbtiles.TilesDifferException→com.onthegomap.planetiler.geo.TileCoordcom.onthegomap.planetiler.mbtiles.Verify→com.onthegomap.planetiler.geo.TileCoord
- Direction
- com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.mbtiles, while a change to com.onthegomap.planetiler.mbtiles can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.mbtiles uses a module listed above it, which is the healthy direction.
26→17 com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler.config✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.mbtiles uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.config.Arguments
- Direction
- com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.mbtiles, while a change to com.onthegomap.planetiler.mbtiles can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.mbtiles uses a module listed above it, which is the healthy direction.
26→20 com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler.archive✕
- Connections
- 11 pairs of types, where a type in com.onthegomap.planetiler.mbtiles uses a type in com.onthegomap.planetiler.archive.
- The types involved
com.onthegomap.planetiler.mbtiles.BatchedCompactTileWriter→com.onthegomap.planetiler.archive.TileEncodingResultcom.onthegomap.planetiler.mbtiles.BatchedCompactTileWriter→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.mbtiles.BatchedNonCompactTileWriter→com.onthegomap.planetiler.archive.TileEncodingResultcom.onthegomap.planetiler.mbtiles.BatchedNonCompactTileWriter→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.mbtiles.BatchedTileTableWriter→com.onthegomap.planetiler.archive.Tilecom.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.archive.ReadableTileArchivecom.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.archive.Tilecom.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.archive.TileArchiveMetadatacom.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.archive.TileWritercom.onthegomap.planetiler.mbtiles.Mbtiles→com.onthegomap.planetiler.archive.WriteableTileArchivecom.onthegomap.planetiler.mbtiles.Metadata→com.onthegomap.planetiler.archive.TileArchiveMetadata
- Direction
- com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler.archive, so a change to com.onthegomap.planetiler.archive can break com.onthegomap.planetiler.mbtiles, while a change to com.onthegomap.planetiler.mbtiles can't break com.onthegomap.planetiler.archive.
- Position
- Below the diagonal: com.onthegomap.planetiler.mbtiles uses a module listed above it, which is the healthy direction.
26→21 com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.mbtiles uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.mbtiles.VectorTileFeatureForCmp→com.onthegomap.planetiler.Featurecom.onthegomap.planetiler.mbtiles.Verify→com.onthegomap.planetiler.Feature
- Direction
- com.onthegomap.planetiler.mbtiles uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.mbtiles, while a change to com.onthegomap.planetiler.mbtiles can't break com.onthegomap.planetiler.
- Position
- Below the diagonal: com.onthegomap.planetiler.mbtiles uses a module listed above it, which is the healthy direction.
27→7 com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.util✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.reader.geojson uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.reader.geojson.GeoJson→com.onthegomap.planetiler.util.CloseableIteratorcom.onthegomap.planetiler.reader.geojson.GeoJsonFeatureIterator→com.onthegomap.planetiler.util.CloseableIterator
- Direction
- com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.reader.geojson, while a change to com.onthegomap.planetiler.reader.geojson can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.geojson uses a module listed above it, which is the healthy direction.
27→10 com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.stats✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.geojson uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.reader.geojson.GeoJsonReader→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.reader.geojson, while a change to com.onthegomap.planetiler.reader.geojson can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.geojson uses a module listed above it, which is the healthy direction.
27→13 com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.reader✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.reader.geojson uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.reader.geojson.GeoJsonFeature→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.reader.geojson.GeoJsonReader→com.onthegomap.planetiler.reader.SimpleFeaturecom.onthegomap.planetiler.reader.geojson.GeoJsonReader→com.onthegomap.planetiler.reader.SimpleReader
- Direction
- com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler.reader.geojson, while a change to com.onthegomap.planetiler.reader.geojson can't break com.onthegomap.planetiler.reader.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.geojson uses a module listed above it, which is the healthy direction.
27→17 com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.config✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.geojson uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.reader.geojson.GeoJsonReader→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.reader.geojson, while a change to com.onthegomap.planetiler.reader.geojson can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.geojson uses a module listed above it, which is the healthy direction.
27→19 com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.collection✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.geojson uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.reader.geojson.GeoJsonReader→com.onthegomap.planetiler.collection.FeatureGroup
- Direction
- com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.reader.geojson, while a change to com.onthegomap.planetiler.reader.geojson can't break com.onthegomap.planetiler.collection.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.geojson uses a module listed above it, which is the healthy direction.
27→21 com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.geojson uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.reader.geojson.GeoJsonReader→com.onthegomap.planetiler.Profile
- Direction
- com.onthegomap.planetiler.reader.geojson uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.reader.geojson, while a change to com.onthegomap.planetiler.reader.geojson can't break com.onthegomap.planetiler.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.geojson uses a module listed above it, which is the healthy direction.
28→7 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.util✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.reader.parquet.FormatHandler→com.onthegomap.planetiler.util.FunctionThatThrowscom.onthegomap.planetiler.reader.parquet.GeometryReader→com.onthegomap.planetiler.util.FunctionThatThrowscom.onthegomap.planetiler.reader.parquet.ParquetInputFile→com.onthegomap.planetiler.util.ByteRangecom.onthegomap.planetiler.reader.parquet.ParquetInputFile→com.onthegomap.planetiler.util.Plancom.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.util.Downloadercom.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.util.FunctionThatThrows
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
28→9 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.reader.remote✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.reader.remote.
- The types involved
com.onthegomap.planetiler.reader.parquet.1→com.onthegomap.planetiler.reader.remote.Pendingcom.onthegomap.planetiler.reader.parquet.ParquetInputFile→com.onthegomap.planetiler.reader.remote.RangeFilecom.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.reader.remote.DownloadModecom.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.reader.remote.RangeFilecom.onthegomap.planetiler.reader.parquet.RangeInputFile→com.onthegomap.planetiler.reader.remote.RangeFile
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.reader.remote, so a change to com.onthegomap.planetiler.reader.remote can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.reader.remote.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
28→10 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.stats✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.stats.Finishablecom.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
28→11 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.render✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.render.
- The types involved
com.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.render.FeatureRenderer
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.render, so a change to com.onthegomap.planetiler.render can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.render.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
28→13 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.reader✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.reader.parquet.GeometryReader→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.reader.parquet.ParquetFeature→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.reader.parquet.ParquetFeature→com.onthegomap.planetiler.reader.Struct
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.reader.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
28→16 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.geo✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.reader.parquet.FormatHandler→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.reader.parquet.GeoParquetMetadata→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.reader.parquet.GeometryReader→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.reader.parquet.ParquetFeature→com.onthegomap.planetiler.geo.GeometryTypecom.onthegomap.planetiler.reader.parquet.ParquetInputFile→com.onthegomap.planetiler.geo.GeometryType
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
28→17 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.config✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.reader.parquet.ColumnMetadata→com.onthegomap.planetiler.config.Boundscom.onthegomap.planetiler.reader.parquet.ParquetInputFile→com.onthegomap.planetiler.config.Boundscom.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
28→19 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.collection✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.collection.FeatureGroupcom.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.collection.SortableFeature
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.collection.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
28→21 com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.reader.parquet uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.reader.parquet.ParquetInputFile→com.onthegomap.planetiler.Profilecom.onthegomap.planetiler.reader.parquet.ParquetReader→com.onthegomap.planetiler.Profile
- Direction
- com.onthegomap.planetiler.reader.parquet uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.reader.parquet, while a change to com.onthegomap.planetiler.reader.parquet can't break com.onthegomap.planetiler.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.parquet uses a module listed above it, which is the healthy direction.
29→10 com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler.stats✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.shapefile uses a type in com.onthegomap.planetiler.stats.
- The types involved
com.onthegomap.planetiler.reader.shapefile.ShapefileReader→com.onthegomap.planetiler.stats.Stats
- Direction
- com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler.stats, so a change to com.onthegomap.planetiler.stats can break com.onthegomap.planetiler.reader.shapefile, while a change to com.onthegomap.planetiler.reader.shapefile can't break com.onthegomap.planetiler.stats.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.shapefile uses a module listed above it, which is the healthy direction.
29→13 com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler.reader✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.reader.shapefile uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.reader.shapefile.ShapefileFeature→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.reader.shapefile.ShapefileReader→com.onthegomap.planetiler.reader.ShapefileOptionscom.onthegomap.planetiler.reader.shapefile.ShapefileReader→com.onthegomap.planetiler.reader.SimpleReader
- Direction
- com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler.reader.shapefile, while a change to com.onthegomap.planetiler.reader.shapefile can't break com.onthegomap.planetiler.reader.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.shapefile uses a module listed above it, which is the healthy direction.
29→17 com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler.config✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.reader.shapefile uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.reader.shapefile.ShapefileReader→com.onthegomap.planetiler.config.Boundscom.onthegomap.planetiler.reader.shapefile.ShapefileReader→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.reader.shapefile, while a change to com.onthegomap.planetiler.reader.shapefile can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.shapefile uses a module listed above it, which is the healthy direction.
29→19 com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler.collection✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.shapefile uses a type in com.onthegomap.planetiler.collection.
- The types involved
com.onthegomap.planetiler.reader.shapefile.ShapefileReader→com.onthegomap.planetiler.collection.FeatureGroup
- Direction
- com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler.collection, so a change to com.onthegomap.planetiler.collection can break com.onthegomap.planetiler.reader.shapefile, while a change to com.onthegomap.planetiler.reader.shapefile can't break com.onthegomap.planetiler.collection.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.shapefile uses a module listed above it, which is the healthy direction.
29→21 com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.reader.shapefile uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.reader.shapefile.ShapefileReader→com.onthegomap.planetiler.Profile
- Direction
- com.onthegomap.planetiler.reader.shapefile uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.reader.shapefile, while a change to com.onthegomap.planetiler.reader.shapefile can't break com.onthegomap.planetiler.
- Position
- Below the diagonal: com.onthegomap.planetiler.reader.shapefile uses a module listed above it, which is the healthy direction.
30→7 com.onthegomap.planetiler.validator uses com.onthegomap.planetiler.util✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.validator uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.validator.ExampleResult→com.onthegomap.planetiler.util.Try
- Direction
- com.onthegomap.planetiler.validator uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.validator, while a change to com.onthegomap.planetiler.validator can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.validator uses a module listed above it, which is the healthy direction.
30→16 com.onthegomap.planetiler.validator uses com.onthegomap.planetiler.geo✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.validator uses a type in com.onthegomap.planetiler.geo.
- The types involved
com.onthegomap.planetiler.validator.OutputFeature→com.onthegomap.planetiler.geo.GeometryType
- Direction
- com.onthegomap.planetiler.validator uses com.onthegomap.planetiler.geo, so a change to com.onthegomap.planetiler.geo can break com.onthegomap.planetiler.validator, while a change to com.onthegomap.planetiler.validator can't break com.onthegomap.planetiler.geo.
- Position
- Below the diagonal: com.onthegomap.planetiler.validator uses a module listed above it, which is the healthy direction.
30→17 com.onthegomap.planetiler.validator uses com.onthegomap.planetiler.config✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.validator uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.validator.BaseSchemaValidator→com.onthegomap.planetiler.config.Argumentscom.onthegomap.planetiler.validator.BaseSchemaValidator→com.onthegomap.planetiler.config.PlanetilerConfigcom.onthegomap.planetiler.validator.JavaProfileValidator→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.validator uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.validator, while a change to com.onthegomap.planetiler.validator can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.validator uses a module listed above it, which is the healthy direction.
30→21 com.onthegomap.planetiler.validator uses com.onthegomap.planetiler✕
- Connections
- 4 pairs of types, where a type in com.onthegomap.planetiler.validator uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.validator.BaseSchemaValidator→com.onthegomap.planetiler.Profilecom.onthegomap.planetiler.validator.FeatureWithOverrides→com.onthegomap.planetiler.Featurecom.onthegomap.planetiler.validator.FeatureWithOverrides→com.onthegomap.planetiler.RangeWithTagscom.onthegomap.planetiler.validator.JavaProfileValidator→com.onthegomap.planetiler.Profile
- Direction
- com.onthegomap.planetiler.validator uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.validator, while a change to com.onthegomap.planetiler.validator can't break com.onthegomap.planetiler.
- Position
- Below the diagonal: com.onthegomap.planetiler.validator uses a module listed above it, which is the healthy direction.
31→7 com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.util✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.custommap uses a type in com.onthegomap.planetiler.util.
- The types involved
com.onthegomap.planetiler.custommap.ConfigExpressionParser→com.onthegomap.planetiler.util.Memoizedcom.onthegomap.planetiler.custommap.ConfigExpressionParser→com.onthegomap.planetiler.util.Try
- Direction
- com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.util, so a change to com.onthegomap.planetiler.util can break com.onthegomap.planetiler.custommap, while a change to com.onthegomap.planetiler.custommap can't break com.onthegomap.planetiler.util.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap uses a module listed above it, which is the healthy direction.
31→12 com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.reader.osm✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.custommap uses a type in com.onthegomap.planetiler.reader.osm.
- The types involved
com.onthegomap.planetiler.custommap.ConfiguredProfile→com.onthegomap.planetiler.reader.osm.Waycom.onthegomap.planetiler.custommap.TestForSplitFeature→com.onthegomap.planetiler.reader.osm.OsmSourceFeaturecom.onthegomap.planetiler.custommap.TestForSplitFeature→com.onthegomap.planetiler.reader.osm.Way
- Direction
- com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.reader.osm, so a change to com.onthegomap.planetiler.reader.osm can break com.onthegomap.planetiler.custommap, while a change to com.onthegomap.planetiler.custommap can't break com.onthegomap.planetiler.reader.osm.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap uses a module listed above it, which is the healthy direction.
31→13 com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.reader✕
- Connections
- 11 pairs of types, where a type in com.onthegomap.planetiler.custommap uses a type in com.onthegomap.planetiler.reader.
- The types involved
com.onthegomap.planetiler.custommap.ConfiguredFeature→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.custommap.ConfiguredProfile→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.custommap.FeatureContext→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.custommap.FeatureContext→com.onthegomap.planetiler.reader.WithGeometryTypecom.onthegomap.planetiler.custommap.FeatureContext→com.onthegomap.planetiler.reader.WithSourcecom.onthegomap.planetiler.custommap.FeatureContext→com.onthegomap.planetiler.reader.WithSourceLayercom.onthegomap.planetiler.custommap.FeatureContext→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.custommap.ProcessFeature→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.custommap.Root→com.onthegomap.planetiler.reader.SourceFeaturecom.onthegomap.planetiler.custommap.TagValueProducer→com.onthegomap.planetiler.reader.WithTagscom.onthegomap.planetiler.custommap.TestForSplitFeature→com.onthegomap.planetiler.reader.SourceFeature
- Direction
- com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.reader, so a change to com.onthegomap.planetiler.reader can break com.onthegomap.planetiler.custommap, while a change to com.onthegomap.planetiler.custommap can't break com.onthegomap.planetiler.reader.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap uses a module listed above it, which is the healthy direction.
31→14 com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.expression✕
- Connections
- 4 pairs of types, where a type in com.onthegomap.planetiler.custommap uses a type in com.onthegomap.planetiler.expression.
- The types involved
com.onthegomap.planetiler.custommap.BooleanExpressionParser→com.onthegomap.planetiler.expression.Expressioncom.onthegomap.planetiler.custommap.ConfiguredFeature→com.onthegomap.planetiler.expression.Expressioncom.onthegomap.planetiler.custommap.ConfiguredProfile→com.onthegomap.planetiler.expression.Expressioncom.onthegomap.planetiler.custommap.TagValueProducer→com.onthegomap.planetiler.expression.TypedGetter
- Direction
- com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.expression, so a change to com.onthegomap.planetiler.expression can break com.onthegomap.planetiler.custommap, while a change to com.onthegomap.planetiler.custommap can't break com.onthegomap.planetiler.expression.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap uses a module listed above it, which is the healthy direction.
31→15 com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.custommap.expression✕
- Connections
- 13 pairs of types, where a type in com.onthegomap.planetiler.custommap uses a type in com.onthegomap.planetiler.custommap.expression.
- The types involved
com.onthegomap.planetiler.custommap.BooleanExpressionParser→com.onthegomap.planetiler.custommap.expression.ScriptEnvironmentcom.onthegomap.planetiler.custommap.ConfigExpressionParser→com.onthegomap.planetiler.custommap.expression.ConfigExpressioncom.onthegomap.planetiler.custommap.ConfigExpressionParser→com.onthegomap.planetiler.custommap.expression.Matchcom.onthegomap.planetiler.custommap.ConfigExpressionParser→com.onthegomap.planetiler.custommap.expression.ScriptEnvironmentcom.onthegomap.planetiler.custommap.ConfigExpressionParser→com.onthegomap.planetiler.custommap.expression.Signaturecom.onthegomap.planetiler.custommap.ConfiguredFeature→com.onthegomap.planetiler.custommap.expression.ScriptEnvironmentcom.onthegomap.planetiler.custommap.FeatureAttribute→com.onthegomap.planetiler.custommap.expression.ScriptEnvironmentcom.onthegomap.planetiler.custommap.FeatureContext→com.onthegomap.planetiler.custommap.expression.ScriptContextcom.onthegomap.planetiler.custommap.FeaturePostMatch→com.onthegomap.planetiler.custommap.expression.ScriptEnvironmentcom.onthegomap.planetiler.custommap.NestedContext→com.onthegomap.planetiler.custommap.expression.ScriptContextcom.onthegomap.planetiler.custommap.ProcessFeature→com.onthegomap.planetiler.custommap.expression.ScriptEnvironmentcom.onthegomap.planetiler.custommap.Root→com.onthegomap.planetiler.custommap.expression.ScriptContextcom.onthegomap.planetiler.custommap.Root→com.onthegomap.planetiler.custommap.expression.ScriptEnvironment
- Direction
- com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.custommap.expression, so a change to com.onthegomap.planetiler.custommap.expression can break com.onthegomap.planetiler.custommap, while a change to com.onthegomap.planetiler.custommap can't break com.onthegomap.planetiler.custommap.expression.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap uses a module listed above it, which is the healthy direction.
31→17 com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.config✕
- Connections
- 3 pairs of types, where a type in com.onthegomap.planetiler.custommap uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.custommap.Contexts→com.onthegomap.planetiler.config.Argumentscom.onthegomap.planetiler.custommap.Root→com.onthegomap.planetiler.config.Argumentscom.onthegomap.planetiler.custommap.Root→com.onthegomap.planetiler.config.PlanetilerConfig
- Direction
- com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.custommap, while a change to com.onthegomap.planetiler.custommap can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap uses a module listed above it, which is the healthy direction.
31→21 com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler✕
- Connections
- 5 pairs of types, where a type in com.onthegomap.planetiler.custommap uses a type in com.onthegomap.planetiler.
- The types involved
com.onthegomap.planetiler.custommap.ConfiguredFeature→com.onthegomap.planetiler.FeatureCollectorcom.onthegomap.planetiler.custommap.ConfiguredMapMain→com.onthegomap.planetiler.Planetilercom.onthegomap.planetiler.custommap.ConfiguredProfile→com.onthegomap.planetiler.Featurecom.onthegomap.planetiler.custommap.ConfiguredProfile→com.onthegomap.planetiler.FeatureCollectorcom.onthegomap.planetiler.custommap.ConfiguredProfile→com.onthegomap.planetiler.Profile
- Direction
- com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler, so a change to com.onthegomap.planetiler can break com.onthegomap.planetiler.custommap, while a change to com.onthegomap.planetiler.custommap can't break com.onthegomap.planetiler.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap uses a module listed above it, which is the healthy direction.
31→25 com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.custommap.configschema✕
- Connections
- 6 pairs of types, where a type in com.onthegomap.planetiler.custommap uses a type in com.onthegomap.planetiler.custommap.configschema.
- The types involved
com.onthegomap.planetiler.custommap.ConfiguredFeature→com.onthegomap.planetiler.custommap.configschema.AttributeDefinitioncom.onthegomap.planetiler.custommap.ConfiguredFeature→com.onthegomap.planetiler.custommap.configschema.FeatureItemcom.onthegomap.planetiler.custommap.ConfiguredFeature→com.onthegomap.planetiler.custommap.configschema.FeatureLayercom.onthegomap.planetiler.custommap.ConfiguredProfile→com.onthegomap.planetiler.custommap.configschema.FeatureLayercom.onthegomap.planetiler.custommap.ConfiguredProfile→com.onthegomap.planetiler.custommap.configschema.SchemaConfigcom.onthegomap.planetiler.custommap.Source→com.onthegomap.planetiler.custommap.configschema.DataSourceType
- Direction
- com.onthegomap.planetiler.custommap uses com.onthegomap.planetiler.custommap.configschema, so a change to com.onthegomap.planetiler.custommap.configschema can break com.onthegomap.planetiler.custommap, while a change to com.onthegomap.planetiler.custommap can't break com.onthegomap.planetiler.custommap.configschema.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap uses a module listed above it, which is the healthy direction.
32→17 com.onthegomap.planetiler.custommap.validator uses com.onthegomap.planetiler.config✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.custommap.validator uses a type in com.onthegomap.planetiler.config.
- The types involved
com.onthegomap.planetiler.custommap.validator.SchemaValidator→com.onthegomap.planetiler.config.Arguments
- Direction
- com.onthegomap.planetiler.custommap.validator uses com.onthegomap.planetiler.config, so a change to com.onthegomap.planetiler.config can break com.onthegomap.planetiler.custommap.validator, while a change to com.onthegomap.planetiler.custommap.validator can't break com.onthegomap.planetiler.config.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.validator uses a module listed above it, which is the healthy direction.
32→25 com.onthegomap.planetiler.custommap.validator uses com.onthegomap.planetiler.custommap.configschema✕
- Connections
- 1 pair of types, where a type in com.onthegomap.planetiler.custommap.validator uses a type in com.onthegomap.planetiler.custommap.configschema.
- The types involved
com.onthegomap.planetiler.custommap.validator.SchemaValidator→com.onthegomap.planetiler.custommap.configschema.SchemaConfig
- Direction
- com.onthegomap.planetiler.custommap.validator uses com.onthegomap.planetiler.custommap.configschema, so a change to com.onthegomap.planetiler.custommap.configschema can break com.onthegomap.planetiler.custommap.validator, while a change to com.onthegomap.planetiler.custommap.validator can't break com.onthegomap.planetiler.custommap.configschema.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.validator uses a module listed above it, which is the healthy direction.
32→30 com.onthegomap.planetiler.custommap.validator uses com.onthegomap.planetiler.validator✕
- Connections
- 2 pairs of types, where a type in com.onthegomap.planetiler.custommap.validator uses a type in com.onthegomap.planetiler.validator.
- The types involved
com.onthegomap.planetiler.custommap.validator.SchemaValidator→com.onthegomap.planetiler.validator.BaseSchemaValidatorcom.onthegomap.planetiler.custommap.validator.SchemaValidator→com.onthegomap.planetiler.validator.SchemaSpecification
- Direction
- com.onthegomap.planetiler.custommap.validator uses com.onthegomap.planetiler.validator, so a change to com.onthegomap.planetiler.validator can break com.onthegomap.planetiler.custommap.validator, while a change to com.onthegomap.planetiler.custommap.validator can't break com.onthegomap.planetiler.validator.
- Position
- Below the diagonal: com.onthegomap.planetiler.custommap.validator uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 64 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
| A07:2025 — Authentication Failures | 7 | High / Critical |
Roadmap
Top priorities: Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor); Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED; Interpolated log message defeats structured logging.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +3.0 pts | Low | Supply-chain Provenance & Signing |
| Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor). | +3.8 pts | Medium | Nullable reference types |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in REDACTED Scanning — start with REDACTED. | +1.6 pts | Low | REDACTED Scanning |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +1.6 pts | Low | REDACTED Scanning |
| Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. | +1.6 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 48 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +1.6 pts | Low | Static Analysis (SAST) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +1.6 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Secrets (history): REDACTED: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileArchiveWriter.java | 5.9 | Mixed | Cyclomatic Complexity: TileArchiveWriter.encodeTiles (cyclomatic 18) |
| planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureMerge.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/validator/BaseSchemaValidator.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/expression/Expression.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/util/Downloader.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| planetiler-core/src/main/java/com/onthegomap/planetiler/reader/parquet/ParquetRecordConverter.java | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 54 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 54 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 342 of 353 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (JaCoCo's report goal in REDACTED) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 27 dependency(ies) and leaving 30 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. A language sidecar this run needed FAILED, so the code model the non-MSBuild public-API collector reads was never built — this is a DEGRADED run, not a settled gap, and the surface may well be collectable on a re-run: The Go sidecar exited 0 and produced a model, but its own source census reports it opened ZERO Go files — while the engine's presence probe found Go source in this tree. The model is therefore empty for a reason on OUR side, not the repository's, and Go is recorded as unread rather than as clean.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java`, `planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java`, `planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileEncoder.java`, `planetiler-core/src/main/java/com/onthegomap/planetiler/collection/FeatureGroup.java`, `planetiler-core/src/main/java/com/onthegomap/planetiler/expression/DataType.java`, … (+14 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 85 commits in the last 90 days, yet 147 of 183 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
16 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Planetiler.run at 59. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ParquetPrimitiveConverter.of at 22 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: planetiler-core/src/main/java/com/onthegomap/planetiler/reader/parquet/ParquetPrimitiveConverter.java (ParquetPrimitiveConverter.of at 22), planetiler-core/src/main/java/com/onthegomap/planetiler/reader/Struct.java (Struct.of at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with Planetiler.run (cyclomatic 59), TiledGeometry.sliceY (cyclomatic 50). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.3 to about 8.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
64 method(s) exceeded the cognitive complexity threshold of 15; the worst was TiledGeometry.sliceY at 151.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with TiledGeometry.sliceY (cognitive 151), Planetiler.run (cognitive 80), OsmReader.processPass1Blocks (cognitive 64). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
26 god class(es) detected.
What to do
- Resolve the 9 TooManyMethods finding(s) in God Classes — start with Planetiler.java, FeatureCollector.java, GeoUtils.java. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 8 ClassTooLong finding(s) in God Classes — start with VectorTile.java, Planetiler.java, OsmReader.java. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with PlanetilerConfig.java, Planetiler.java, PlanetilerStdLib.java. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
24 duplicated block group(s) detected. 2.8 % of the production lines (1,282 of 45,265) are in a reported copy. A further 38 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 62 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 6 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with GeoJsonFeatureIterator.java, AppendStoreRam.java, ParquetRecordConverter.java. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ArrayDoubleMinHeap.java, Mbtiles.java, ParquetRecordConverter.java. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with SortKey.java, PointIndex.java, TiledGeometry.java. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
6 production modules (Maven+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 5 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 158 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with FeatureCollector.java. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
0 skipped, 35 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1524 tests.
What to do
- Resolve the 35 No assertions finding(s) in Test Quality — start with OsmMultipolygonTest.java (11), VWSimplifierTest.java (5), FeatureRendererTest.java (3). — One of this dimension's main actionable groups (35 warning-level).
D13 · REDACTED Scanning
1 secret(s) detected. 1 AWS access key ID(s) with no secret access key beside them are listed to check and are not counted as leaked: the key ID alone signs nothing.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D14 · License Compliance
0 of 25 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 8 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 30 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. 1 of them resolve to no licence at all on Central, even through their parent POMs; that is missing data, not a violation, and none of them is charged. A further 2 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java (9×59=531)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with Planetiler.java. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
15 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is planetiler-core/src/main/java/com/onthegomap/planetiler/util/Downloader.java. Counted over 183 of the 304 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
27 deducted task-comment markers across 45265 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 27 TodoComment finding(s) in Explicit Debt — start with FeatureCollector.java (3), OsmReader.java (3), BaseSchemaValidator.java (2). — One of this dimension's main actionable groups (27 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 6 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 6 build units (Maven) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
55 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
4 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
64 finding(s): 0 critical, 61 high, 3 medium, 0 low. 48 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 22 file(s) — `mvnw` (lines 220–221), `planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java` (line 1022, line 1023, line 1166, …), `planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java` (line 605, line 606, line 607, …), `planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileEncoder.java` (line 32), `planetiler-core/src/main/java/com/onthegomap/planetiler/collection/FeatureGroup.java` (line 295, line 296, line 297, …), … (+17 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 48 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (49 issue-level, 1 of them charged here).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 1 high, 1 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D35 · Change Coupling
Strongest change-coupling: TileArchiveWriter.java↔Mbtiles.java 54%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with TileArchiveWriter.java. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 28 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
- `tags` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. — planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/expression/ScriptContext.java:17
What to do
- Finish or delete the methods that still throw "not implemented" or return a placeholder under a TODO, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 5/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `launcher`, `planetiler-dist`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gomod`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:5
What to do
- Dependabot is configured but does not watch `gomod`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X13 · Undrained process stream
X15 · Unvalidated length from an untrusted reader
- `length` is read from the bytes being parsed at line 688 (`getInt`), then used to size a `new byte[]` at line 689 — and nowhere in its scope is `length` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). Whoever wrote those bytes therefore chooses the allocation directly: a 32-bit length asks for up to 2 GiB before a single byte of the payload is known to exist, which either exhausts the heap with an `OutOfMemoryError` or, negative, throws `NegativeArraySizeException` out of a parser whose failure path was written for malformed input, not for hostile input. Bound `length` against the bytes actually remaining and a maximum the format allows before allocating. — planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ExternalMergeSort.java:689
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 1257 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:1257
- `error` at line 57 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/FileUtils.java:57
- `error` at line 155 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/FileUtils.java:155
- `error` at line 168 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/FileUtils.java:168
- `warn` at line 131 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:131
- `warn` at line 139 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:139
- `warn` at line 141 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:141
- `info` at line 144 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:144
- `info` at line 146 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:146
- `debug` at line 149 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:149
- `debug` at line 151 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:151
- `info` at line 32 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/stats/Timers.java:32
- `info` at line 35 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/stats/Timers.java:35
- `error` at line 136 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/reader/SourceFeatureProcessor.java:136
- `info` at line 75 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmPhaser.java:75
- `debug` at line 100 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmPhaser.java:100
- `debug` at line 101 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmPhaser.java:101
- `debug` at line 102 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmPhaser.java:102
- `debug` at line 238 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:238
- `debug` at line 420 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:420
- `error` at line 521 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:521
- `error` at line 805 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java:805
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/33 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61.2 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95.6 | Exemplary | Strongest area. |
| Maturity | 79.6 | Strong | Solid. |
| Readiness | 70.3 | Strong | Solid. |
| Security | 51.0 | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 27 dependency(ies) and leaving 30 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, .java, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 19 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (167 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Go, JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 66 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 246 finding(s)
- No assertions: testKeepAPoint planetiler-core/src/test/java/com/onthegomap/planetiler/geo/VWSimplifierTest.java:56
- No assertions: testLine planetiler-core/src/test/java/com/onthegomap/planetiler/geo/VWSimplifierTest.java:93
- No assertions: testRemoveAPoint planetiler-core/src/test/java/com/onthegomap/planetiler/geo/VWSimplifierTest.java:44
- No assertions: testSimplify2Points planetiler-core/src/test/java/com/onthegomap/planetiler/geo/VWSimplifierTest.java:33
- No assertions: testSimplifyPoint planetiler-core/src/test/java/com/onthegomap/planetiler/geo/VWSimplifierTest.java:28
- No assertions: testFullMetadataJson planetiler-core/src/test/java/com/onthegomap/planetiler/mbtiles/MbtilesTest.java:266
- No assertions: testMetadataJsonNoLayers planetiler-core/src/test/java/com/onthegomap/planetiler/mbtiles/MbtilesTest.java:257
- No assertions: testBrokenPolygonSelfIntersect1 planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:298
- No assertions: testBrokenPolygonSelfIntersect2 planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:335
- No assertions: testBrokenPolygonSelfIntersectTriangleLargeOverlap planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:405
- No assertions: testBrokenPolygonSelfIntersectTriangleSmallOverlap planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:376
- No assertions: testConnectAlmostClosed planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:147
- No assertions: testConnectSimplePolygon planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:127
- No assertions: testIgnoreSingleNotClosed planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:194
- No assertions: testMultiPolygonWithNestedHoles planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:250
- No assertions: testSimplePolygonWithHole planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:212
- No assertions: testSimplePolygonWithMultipleHoles planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:226
- No assertions: testTouchingPolygonsWithHole planetiler-core/src/test/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygonTest.java:278
- No assertions: testBackAndForthsOutsideTile planetiler-core/src/test/java/com/onthegomap/planetiler/render/FeatureRendererTest.java:1389
- No assertions: testReplayEdgesInnerPoly planetiler-core/src/test/java/com/onthegomap/planetiler/render/FeatureRendererTest.java:1421
- No assertions: testReplayEdgesOuterPoly planetiler-core/src/test/java/com/onthegomap/planetiler/render/FeatureRendererTest.java:1405
- No assertions: testFreeDirectByteBuffer planetiler-core/src/test/java/com/onthegomap/planetiler/util/ByteBufferUtilTest.java:50
- No assertions: testFreeHeapByteBuffer planetiler-core/src/test/java/com/onthegomap/planetiler/util/ByteBufferUtilTest.java:55
- No assertions: testEmpty planetiler-core/src/test/java/com/onthegomap/planetiler/util/ResourceUsageTest.java:11
- No assertions: issue1470_computeMltFastPforStats planetiler-core/src/test/java/com/onthegomap/planetiler/util/TileSizeStatsTest.java:171
- TodoComment planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/ConfiguredFeature.java:168
- TodoComment planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/expression/ScriptContext.java:18
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java:79
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java:546
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java:915
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureMerge.java:350
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/ForwardingProfile.java:268
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:217
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/Profile.java:37
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:92
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/validator/BaseSchemaValidator.java:182
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/validator/BaseSchemaValidator.java:265
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/util/Downloader.java:614
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/reader/SourceFeature.java:91
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/reader/shapefile/DbfReader.java:170
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/reader/shapefile/ShpGeometryReader.java:51
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/reader/parquet/GeoParquetMetadata.java:127
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/reader/parquet/ParquetRecordConverter.java:124
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:269
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:294
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:307
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java:383
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/geo/VWSimplifier.java:90
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/geo/VWSimplifier.java:114
- TodoComment planetiler-core/src/main/java/com/onthegomap/planetiler/expression/Expression.java:33
- TooManyMethods: Planetiler planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:100
- TooManyMethods: Feature planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java:520
- TooManyMethods: GeoUtils planetiler-core/src/main/java/com/onthegomap/planetiler/geo/GeoUtils.java:49
- TooManyMethods: Arguments planetiler-core/src/main/java/com/onthegomap/planetiler/config/Arguments.java:44
- TooManyMethods: Mbtiles planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java:48
- TooManyMethods: ProgressLoggers planetiler-core/src/main/java/com/onthegomap/planetiler/stats/ProgressLoggers.java:45
- TooManyMethods: CachedRangeFile planetiler-core/src/main/java/com/onthegomap/planetiler/reader/remote/CachedRangeFile.java:39
- TooManyMethods: Downloader planetiler-core/src/main/java/com/onthegomap/planetiler/util/Downloader.java:83
- TooManyMethods: FeatureGroup planetiler-core/src/main/java/com/onthegomap/planetiler/collection/FeatureGroup.java:55
- ClassTooLong: VectorTile planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:79
- ClassTooLong: Planetiler planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:100
- ClassTooLong: OsmReader planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:67
- ClassTooLong: Mbtiles planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java:48
- ClassTooLong: FeatureCollector planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java:48
- ClassTooLong: Downloader planetiler-core/src/main/java/com/onthegomap/planetiler/util/Downloader.java:83
- ClassTooLong: ExternalMergeSort planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ExternalMergeSort.java:62
- ClassTooLong: TiledGeometry planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:71
- Edited copy of a member (9 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/geojson/GeoJsonFeatureIterator.java:235
- Edited copy of a member (9 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/AppendStoreRam.java:76
- Edited copy of a member (9 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/parquet/ParquetRecordConverter.java:199
- Edited copy of a member (9 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/TileCoord.java:128
- Edited copy of a member (9 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Verify.java:117
- Edited copy of a member (9 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/shapefile/ShapefileReader.java:415
- Duplicated block (8 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:153
- Duplicated block (8 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java:659
- Duplicated block (8 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/parquet/ParquetRecordConverter.java:200
- Duplicated block (8 lines × 2) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/expression/stdlib/PlanetilerStdLib.java:163
- Duplicated block (8 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/DouglasPeuckerSimplifier.java:229
- Duplicated block (8 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/LongLongMap.java:160
- MethodTooLong: PlanetilerConfig.from planetiler-core/src/main/java/com/onthegomap/planetiler/config/PlanetilerConfig.java:133
- MethodTooLong: Planetiler.run planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:977
- MethodTooLong: PlanetilerStdLib.<init> planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/expression/stdlib/PlanetilerStdLib.java:36
- MethodTooLong: TiledGeometry.sliceY planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:502
- MethodTooLong: CompareArchives.getResult planetiler-core/src/main/java/com/onthegomap/planetiler/util/CompareArchives.java:123
- FileTooLong: planetiler/VectorTile.java planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java
- FileTooLong: planetiler/Planetiler.java planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java
- FileTooLong: osm/OsmReader.java planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java
- FileTooLong: mbtiles/Mbtiles.java planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (12 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/util/SortKey.java:134
- Edited copy of a member (12 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/PointIndex.java:92
- Edited copy of a member (12 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:701
- Edited copy of a member (12 corresponding lines) planetiler-benchmarks/src/main/java/com/onthegomap/planetiler/collection/BenchmarkKWayMerge.java:81
- Edited copy of a member (8 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/worker/WorkerPipeline.java:175
- Edited copy of a member (8 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/GeoUtils.java:76
- Edited copy of a member (8 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/AppendStoreMmap.java:123
- Edited copy of a member (10 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/PolygonIndex.java:67
- Edited copy of a member (10 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:36
- Edited copy of a member (10 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/expression/Expression.java:326
- Duplicated block (10 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/validator/JavaProfileValidator.java:49
- Duplicated block (10 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:123
- Duplicated block (10 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/PointIndex.java:36
- Duplicated block (6 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/AppendStoreRam.java:77
- Duplicated block (6 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:135
- Duplicated block (6 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/MutableCoordinateSequence.java:73
- REDACTED
- REDACTED
- Edited copy of a member (19 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/stats/ProgressLoggers.java:75
- Edited copy of a member (19 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmInputFile.java:150
- Edited copy of a member (20 corresponding lines) planetiler-benchmarks/src/main/java/com/onthegomap/planetiler/collection/BenchmarkKWayMerge.java:50
- Edited copy of a member (20 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/PointIndex.java:48
- Edited copy of a member (13 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java:657
- Edited copy of a member (13 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java:125
- Edited copy of a member (6 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/TileCoord.java:77
- Edited copy of a member (6 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileCompression.java:37
- Duplicated block (7 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:413
- Duplicated block (7 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/util/Hilbert.java:90
- Duplicated block (5 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:162
- Duplicated block (5 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileCompression.java:31
- Planetiler.run (cyclomatic 59) planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:977
- TiledGeometry.sliceY (cyclomatic 50) planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:502
- VectorTile.decodeCommands (cyclomatic 30) planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:208
- CompareArchives.getResult (cyclomatic 26) planetiler-core/src/main/java/com/onthegomap/planetiler/util/CompareArchives.java:123
- PlanetilerStdLib.<init> (cyclomatic 22) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/expression/stdlib/PlanetilerStdLib.java:36
- ProcessFeature.apply (cyclomatic 21) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/Contexts.java:392
- GeoJsonFeatureIterator.advance (cyclomatic 20) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/geojson/GeoJsonFeatureIterator.java:86
- OsmReader.processPass1Blocks (cyclomatic 20) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:245
- TiledGeometry.sliceX (cyclomatic 20) planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:406
- GeoPackageReader.readFeatures (cyclomatic 19) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/GeoPackageReader.java:137
- TileArchiveWriter.encodeTiles (cyclomatic 18) planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileArchiveWriter.java:268
- Parse.bandwidth (cyclomatic 18) planetiler-core/src/main/java/com/onthegomap/planetiler/util/Parse.java:223
- FeatureMerge.mergeNearbyPolygons (cyclomatic 18) planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureMerge.java:323
- BooleanExpressionParser.tagCriterionToExpression (cyclomatic 18) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/BooleanExpressionParser.java:105
- GeoUtils.isConvex (cyclomatic 17) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/GeoUtils.java:497
- OsmMultipolygon.connectPolygonSegments (cyclomatic 16) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygon.java:317
- Hotspot: planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:977
- TiledGeometry.sliceY (cognitive 151) planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:502
- Planetiler.run (cognitive 80) planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:977
- OsmReader.processPass1Blocks (cognitive 64) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:245
- VectorTile.decodeCommands (cognitive 53) planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:208
- FeatureMerge.mergeNearbyPolygons (cognitive 52) planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureMerge.java:323
- VarInt.getVarLong (cognitive 45) planetiler-core/src/main/java/com/onthegomap/planetiler/util/VarInt.java:41
- GeoPackageReader.readFeatures (cognitive 42) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/GeoPackageReader.java:137
- TiledGeometry.sliceX (cognitive 42) planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:406
- TileArchiveWriter.encodeTiles (cognitive 38) planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileArchiveWriter.java:268
- GeoJsonFeatureIterator.advance (cognitive 36) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/geojson/GeoJsonFeatureIterator.java:86
- OsmMultipolygon.connectPolygonSegments (cognitive 34) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygon.java:317
- CompareArchives.getResult (cognitive 34) planetiler-core/src/main/java/com/onthegomap/planetiler/util/CompareArchives.java:123
- ResourceUsage.checkAgainstLimits (cognitive 34) planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:120
- TiledGeometry.sliceWorldCopy (cognitive 32) planetiler-core/src/main/java/com/onthegomap/planetiler/render/TiledGeometry.java:332
- VectorGeometry.isFillOrEdge (cognitive 32) planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:943
- BooleanExpressionParser.tagCriterionToExpression (cognitive 31) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/BooleanExpressionParser.java:105
- StringColumns.find (cognitive 30) planetiler-core/src/main/java/com/onthegomap/planetiler/archive/JavaMltTileEncoder.java:130
- LoopLineMerger.removeShortStubEdges (cognitive 30) planetiler-core/src/main/java/com/onthegomap/planetiler/util/LoopLineMerger.java:293
- FeatureRenderer.accept (cognitive 29) planetiler-core/src/main/java/com/onthegomap/planetiler/render/FeatureRenderer.java:63
- FeatureMerge.mergeLineStrings (cognitive 29) planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureMerge.java:178
- VectorGeometry.filterPointsOutsideBuffer (cognitive 29) planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:1023
- LoopLineMerger.breakLoops (cognitive 27) planetiler-core/src/main/java/com/onthegomap/planetiler/util/LoopLineMerger.java:231
- VectorTile.unscale (cognitive 27) planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:109
- WeightedHandoffQueue.get (cognitive 26) planetiler-core/src/main/java/com/onthegomap/planetiler/worker/WeightedHandoffQueue.java:81
- ConfigExpressionParser.parseMatch (cognitive 26) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/ConfigExpressionParser.java:118
- OsmMultipolygon.groupParentChildShells (cognitive 25) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygon.java:230
- BaseSchemaValidator.validate (cognitive 25) planetiler-core/src/main/java/com/onthegomap/planetiler/validator/BaseSchemaValidator.java:155
- Contexts.buildRootContext (cognitive 25) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/Contexts.java:65
- GeoUtils.isConvex (cognitive 24) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/GeoUtils.java:497
- NaturalEarthReader.readFeatures (cognitive 24) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/NaturalEarthReader.java:154
- FeatureMerge.extractPolygons (cognitive 24) planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureMerge.java:532
- DualMidpointSmoother.squashVertex (cognitive 23) planetiler-core/src/main/java/com/onthegomap/planetiler/geo/DualMidpointSmoother.java:170
- LoopLineMerger.strokeMerge (cognitive 23) planetiler-core/src/main/java/com/onthegomap/planetiler/util/LoopLineMerger.java:201
- PlanetilerStdLib.<init> (cognitive 23) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/expression/stdlib/PlanetilerStdLib.java:36
- ConfigExpressionParser.parse (cognitive 23) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/ConfigExpressionParser.java:68
- MatchAny.evaluate (cognitive 22) planetiler-core/src/main/java/com/onthegomap/planetiler/expression/Expression.java:483
- Parse.meters (cognitive 22) planetiler-core/src/main/java/com/onthegomap/planetiler/util/Parse.java:180
- BaseSchemaValidator.validateFromCli (cognitive 22) planetiler-core/src/main/java/com/onthegomap/planetiler/validator/BaseSchemaValidator.java:75
- CommandEncoder.encode (cognitive 22) planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:1261
- ArrayDoubleMinHeap.percolateDown (cognitive 21) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:168
- Writer.advanceTo (cognitive 21) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayLongLongMapMmap.java:320
- ArrayLongMinHeap.percolateDown (cognitive 21) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayLongMinHeap.java:190
- ThreeWayMerge.next (cognitive 21) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/LongMerger.java:127
- LoopLineMerger.nodeLines (cognitive 21) planetiler-core/src/main/java/com/onthegomap/planetiler/util/LoopLineMerger.java:473
- ReaderForThread.get (cognitive 21) planetiler-core/src/main/java/com/onthegomap/planetiler/worker/WorkQueue.java:228
- ProcessFeature.apply (cognitive 21) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/Contexts.java:392
- BenchmarkMbtilesWriter.writeTiles (cognitive 20) REDACTED:95
- PolyFileReader.parsePolyFile (cognitive 20) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/PolyFileReader.java:49
- FileUtils.unzip (cognitive 20) planetiler-core/src/main/java/com/onthegomap/planetiler/util/FileUtils.java:299
- DenseNodeIterator.next (cognitive 19) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/PbfDecoder.java:355
- ParquetInputFile.<init> (cognitive 19) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/parquet/ParquetInputFile.java:104
- VectorTile.decode (cognitive 19) planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:361
- TileArchiveWriter.tileWriter (cognitive 18) planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileArchiveWriter.java:356
- LoopLineMerger.shortestDistanceAStar (cognitive 18) planetiler-core/src/main/java/com/onthegomap/planetiler/util/LoopLineMerger.java:261
- TopOsmTiles.readFile (cognitive 18) planetiler-core/src/main/java/com/onthegomap/planetiler/util/TopOsmTiles.java:126
- ShpGeometryReader.multiPolygon (cognitive 17) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/shapefile/ShpGeometryReader.java:66
- ConfiguredFeature.attributeProcessor (cognitive 17) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/ConfiguredFeature.java:305
- PlanetilerConfig.<init> (cognitive 16) planetiler-core/src/main/java/com/onthegomap/planetiler/config/PlanetilerConfig.java:91
- DeduplicatingTileWriter.write (cognitive 16) planetiler-core/src/main/java/com/onthegomap/planetiler/pmtiles/WriteablePmtiles.java:301
- ByteBufferUtil.mapFile (cognitive 16) planetiler-core/src/main/java/com/onthegomap/planetiler/util/ByteBufferUtil.java:97
- FileUtils.createParentDirectories (cognitive 16) planetiler-core/src/main/java/com/onthegomap/planetiler/util/FileUtils.java:229
- TileSizeStats.main (cognitive 16) planetiler-core/src/main/java/com/onthegomap/planetiler/util/TileSizeStats.java:85
- Translations.addTranslations (cognitive 16) planetiler-core/src/main/java/com/onthegomap/planetiler/util/Translations.java:101
- Wikidata.filter (cognitive 16) planetiler-core/src/main/java/com/onthegomap/planetiler/util/Wikidata.java:260
- REDACTED
- REDACTED
- Change coupling: TileArchiveWriter.java ↔ Mbtiles.java planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileArchiveWriter.java:1
- REDACTED
- REDACTED
- Edited copy of a member (42 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:168
- Edited copy of a member (31 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/worker/WeightedHandoffQueue.java:81
- Edited copy of a member (18 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:142
- Edited copy of a member (17 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/expression/Expression.java:289
- Edited copy of a member (16 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:89
- Edited copy of a member (15 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java:895
- Edited copy of a member (11 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/render/GeometryCoordinateSequences.java:101
- Edited copy of a member (7 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmMultipolygon.java:300
- Edited copy of a member (5 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:282
- Edited copies of one member (4 members, 10+ corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayLongLongMapMmap.java:234
- Edited copies of one member (3 members, 7+ corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileEncodingResult.java:26
- Edited copy of a member (4 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/parquet/RangeInputFile.java:57
- Edited copy of a member (3 corresponding lines) planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileCompression.java:44
- Duplicated block (28 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:182
- Duplicated block (14–15 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/LongMerger.java:78
- Duplicated block (14 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ArrayDoubleMinHeap.java:67
- Duplicated block (13 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/stats/ProgressLoggers.java:76
- Duplicated block (11 lines × 2) planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/expression/stdlib/PlanetilerStdLib.java:120
- Duplicated block (9 lines × 2) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/SourceFeatureProcessor.java:155
- Duplicated block (1–6 lines × 3) planetiler-core/src/main/java/com/onthegomap/planetiler/util/Hilbert.java:99
- Duplicated block (10 lines × 3) planetiler-core/src/main/java/com/onthegomap/planetiler/reader/SourceFeatureProcessor.java:185
- Edited copies of one member (7 members, 8+ corresponding lines) planetiler-examples/src/main/java/com/onthegomap/planetiler/examples/AdminBordersOverlay.java:146
- Off the main sequence: planetiler-core
- Low cohesion: Feature (LCOM4 5) planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java:520
- Unfinished stub — returns a placeholder under a TODO marker planetiler-custommap/src/main/java/com/onthegomap/planetiler/custommap/expression/ScriptContext.java:17
- Length read from the parsed input is spent without ever being bounded planetiler-core/src/main/java/com/onthegomap/planetiler/collection/ExternalMergeSort.java:689
Minor — 41 finding(s)
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/Planetiler.java:1257
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/FileUtils.java:57
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/FileUtils.java:155
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/FileUtils.java:168
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:131
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:139
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:141
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:144
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:146
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:149
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/util/ResourceUsage.java:151
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/stats/Timers.java:32
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/stats/Timers.java:35
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/reader/SourceFeatureProcessor.java:136
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmPhaser.java:75
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmPhaser.java:100
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmPhaser.java:101
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmPhaser.java:102
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:238
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:420
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/reader/osm/OsmReader.java:521
- Interpolated log message defeats structured logging planetiler-core/src/main/java/com/onthegomap/planetiler/mbtiles/Mbtiles.java:805
- Duplicated predicate planetiler-core/src/main/java/com/onthegomap/planetiler/validator/JavaProfileValidator.java:48
- Duplicated predicate planetiler-core/src/main/java/com/onthegomap/planetiler/worker/WeightedHandoffQueue.java:84
- Duplicated predicate planetiler-core/src/main/java/com/onthegomap/planetiler/expression/Expression.java:330
- Duplicated predicate planetiler-core/src/main/java/com/onthegomap/planetiler/geo/DouglasPeuckerSimplifier.java:232
- Duplicated predicate planetiler-core/src/main/java/com/onthegomap/planetiler/worker/WeightedHandoffQueue.java:66
- REDACTED
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found REDACTED:345
- Projects may be oversized for their cohesion REDACTED:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- Dependabot does not watch gomod/gitsubmodule REDACTED:5
- No changelog
- Java packages are not null-marked everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-03200e8e77eb4c2fb4ac3a03b3c7e099/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-03200e8e77eb4c2fb4ac3a03b3c7e099/history-1.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=488" --report-format json --report-path /tmp/watchdog-gitleaks-03200e8e77eb4c2fb4ac3a03b3c7e099/history-2.json --exit-code 0 --source . | 5 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-03200e8e77eb4c2fb4ac3a03b3c7e099/tree.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 64 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-bbc44501ec804224b8ec5ccdb3c1dd38 | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 19 file(s) — `planetiler-core/src/main/java/com/onthegomap/planetiler/FeatureCollector.java`, `planetiler-core/src/main/java/com/onthegomap/planetiler/VectorTile.java`, `planetiler-core/src/main/java/com/onthegomap/planetiler/archive/TileEncoder.java`, `planetiler-core/src/main/java/com/onthegomap/planetiler/collection/FeatureGroup.java`, `planetiler-core/src/main/java/com/onthegomap/planetiler/expression/DataType.java`, … (+14 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-bbc44501ec804224b8ec5ccdb3c1dd38 | 0 | artifacts/raw/osv-scanner.json |