[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.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
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.
Description
Please check the following before submitting a new issue.
- I have searched the existing issues.
- I have carefully read the documentation and verified I have added the required platform specific configuration.
Please select affected platform(s)
- Android
- 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<geocoding.Placemark> 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
- Dominant language
- Dart
- Stars
- 153
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Baseflow/flutter-geocoding
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Baseflow/flutter-geocoding#311 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Baseflow/flutter-geocoding#309 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Baseflow/flutter-geocoding#287 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Baseflow/flutter-geocoding#286 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Baseflow/flutter-geocoding#247 · 1 comment · 1 reaction ·
All issues in Baseflow/flutter-geocoding
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
code quality good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Suwayomi/Suwayomi-Tsumiru#479 ·
-
Build Failure: agora_rtc_engine compiled against android-31 while dependencies require android-34+ Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
conceptadev/noir#95 ·