Polygon support for addressSearch

Open
#747 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend, search

Research direction

Start by locating the addressSearch implementation and its Nominatim provider, then trace how returned points determine the map view and zoom. Define the provider configuration and polygon handling from the issue requirements, and verify that polygon results choose a zoom level showing the whole area.

Written by the indexing model from the issue text.

Description

enhancement

The addressSearch should (additionally) support working with polygons instead of points.

If a service is able to return a polygon, this should be preferred over points (or at least, it should be configurable).

Having the polygon allows for determining the adequate zoom level for the feature. The adequate zoom level should at least show the whole area of the polygon.

This issue is meant to be resolved when the following is implemented:

  • addressSearch supports providers that return polygons.
  • The nominatim addressSearch provider can be configured to use polygons.
  • If polygons are used, the adequate zoom level is dynamically determined.
Dominant language
TypeScript
Stars
50
Forks
8
Avg merge
18h 24m
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Dataport/polar

All issues in Dataport/polar

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.