Same data attributes for different provider in chain providers

Open
#1,080 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
api, backend

Research direction

Start by locating the chain provider’s reverse-geocoding option handling and comparing it with the Mapbox and Google Maps provider behavior. Clarify whether provider-specific location_type values should be filtered, translated, or passed separately; done requires an agreed behavior for mixed-provider queries and corresponding coverage.

Written by the indexing model from the issue text.

Description

question

Hello,

I'm not sure if anyone have encountered this. If I want to use the chain provider with Mapbox and Google Maps provider to do reverse geocode, I can't specify location_type data attributes with the query because it will mean differently to each provider (ie. valid location_type for Mapbox is poi, place, locality etc. but for Google Maps valid values were eg. ROOFTOP, RANGE_INTERPOLATED etc.

We can call each provider individually to work around this, but I'm wondering if there's built-in handler within the chain provider itself?

Thanks!

Dominant language
PHP
Stars
4k
Forks
525
Avg merge
8m
Merged PRs (30d)
1

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 geocoder-php/Geocoder

All issues in geocoder-php/Geocoder

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.