Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to specify a customizable buffer size to all results #3642

Closed
juburr opened this issue Jan 24, 2025 · 1 comment
Closed

Ability to specify a customizable buffer size to all results #3642

juburr opened this issue Jan 24, 2025 · 1 comment

Comments

@juburr
Copy link

juburr commented Jan 24, 2025

Is your feature request related to a problem? Please describe.
I'd like to add a buffer to all search results. e.g., instead of returning a polygon for North Carolina, I want the ability to return a polygon representing the border plus a customizable buffer, like 20 miles.

Describe the solution you'd like
Make it an API parameter that can be used to transform all search results. Defaults to 0 (unused) if not supplied.

Describe alternatives you've considered

  • Do it in my own source code afterwards (depending on the programming language, it was more painful than what PostGIS can do natively it seemed).
  • Reach into the Nominatim database and query it out myself. i.e., something like this: SELECT ST_Buffer(ST_Transform(geometry, 3857), buffer_distance) FROM placex WHERE osm_id = in_osm_id;.

Additional context
None

@lonvia
Copy link
Member

lonvia commented Jan 31, 2025

This is a rather specific request. Libraries for buffering are widely available, thus making it fairly easy to do on the client side. In addition there is no real upside like saving bandwidth when doing on the server side. The obvious downside is the introduction of a new API parameter that needs to be maintained for many versions to come. So, I'm sorry to say that the downside outweighs the upside here.

Closing as "won't be implemented".

@lonvia lonvia closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2025
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

No branches or pull requests

2 participants