Baseflow / Baseflow/flutter-geocoding
[Bug]: Wrong pincode at first index of array. There is no types parameter with key postal_code just like google provides in its reversegeocoding API.
- Dominant language
- Dart
- Stars
- 153
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
### Please check the following before submitting a new issue.
- [X] I have searched the [existing issues](https://github.com/baseflow/flutter-geocoding/issues).
- [X] I have carefully [read the documentation](https://github.com/Baseflow/flutter-geocoding/blob/main/geocoding/README.md) and verified I have added the required platform specific configuration.
### Please select affected platform(s)
- [X] Android
- [X] iOS
### Steps to reproduce
Hi,
Facing issue of having wrong pincode based on provided devices latitude and longitude. Example, If I am passing device latitude longitude, the accurate postal code should get visible.
Result
Expected Output : 24.8234664, 75.0307014 => 458226
### Expected results
If I pass latlong : 24.8234664, 75.0307014 it should get pincode as 458226
### Actual results
When passing latlong : 24.8234664, 75.0307014 getting pincode 454226
### Code sample
List placemarks = await geocoding.placemarkFromCoordinates(loc.latitude, loc.longitude);
Using dart, I should get types as postal-code and basis of that I should get the actual pincode of that location.
### Screenshots or video
_No response_
### Version
3.0.0
### Flutter Doctor output
Have done all the things and upgraded the flutter version with all other dependencies
Contributor guide
Research direction
Start by reproducing the reported coordinates through the Dart placemarkFromCoordinates call on both Android and iOS, using version 3.0.0 and comparing the returned postal-code data. Trace how the plugin exposes the platform geocoder result and determine whether the requested postal-code selection is supported. Done means the reported coordinates return the expected pincode or the limitation is documented with a verified result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100