Skip to content

Add park and dog park POI categories - #7

Merged
tldev merged 2 commits into
mainfrom
feature/park-poi-categories
Mar 31, 2026
Merged

tldev merged 2 commits into
mainfrom
feature/park-poi-categories

Conversation

@tldev

@tldev tldev commented Mar 31, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add park (leisure=park) and dogPark (leisure=dog_park) categories to the POI pipeline
  • Use 1600m radius for park/dogPark exit candidates (vs 800m for other categories)
  • Add park/dogPark to name-filter exception list (unnamed parks aren't dropped)

Test plan

  • Run import + derive and check counts: SELECT category, COUNT(*) FROM exit_poi_candidates WHERE category IN ('park','dogPark') GROUP BY category;
  • Verify parks appear in API responses for exits near known parks

🤖 Generated with Claude Code

tldev and others added 2 commits March 31, 2026 14:13
Classify leisure=park and leisure=dog_park from OSM tags as new POI
categories. Use a 1600m search radius (vs 800m standard) for these
categories since parks tend to be larger and further from exit nodes.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The expanded 0.024° envelope was applying to all categories, widening
the initial candidate set unnecessarily. Now uses a CASE expression
matching the ST_DWithin radius: 0.024° for park/dogPark, 0.012° for
everything else.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@tldev
tldev merged commit d229109 into main Mar 31, 2026
3 checks passed
tldev added a commit that referenced this pull request Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant