-
Notifications
You must be signed in to change notification settings - Fork 18
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
Reverse country GeoCoder has some flaws near 'Monaco' #593
Comments
Thanks @GGGuerin for your report. This flag is the Monaco one ;) (yes it looks like Polish, but in reverse). I'll keep this issue open to not forget that. (BTW Welcome on GitHub!!!) |
Remark : These three caches are more than 200km far away from Monaco. I have got some caches which are in the area of Monaco (but in France) and are well situated in France. |
To be noted reverse country geocoder methods are completly different in both GK implementation GKv1 ( GKv1:
GKv2:
This issue has been opened targeted to Here is the result: https://geo.geokrety.org/api/getCountry?lat=43.74667&lon=5.20602 On GKv2, problem does not exists in normal use case: I'll check what's the problem with Edit: During daily imports, triggers are disabled to prevent foreign key errors :/
|
Not really related to the issue itself, but could you please provide some insights, what was the data source here (I don't believe you handcrafter coordinates->countries mapping yourself), is this part reusable (read as "we're in Geocaching.su would be interested in using some smartness based on coordinates") and so on and so forth? |
Great ! |
Here some insight about Gis features General
Altitude profiles
geokrety-website/website/db/dumps/20_geokrety-schema.sql Lines 1005 to 1008 in 8d8cffb
reverse country geocoder
geokrety-website/website/db/dumps/20_geokrety-schema.sql Lines 998 to 1001 in 8d8cffb
timezones
|
Hello,
As you can see, I have three visits for this GK which are located in France. However, the site displays an other flag (polish one I suppose)
https://geokrety.org/konkret.php?id=78523&page=3
The text was updated successfully, but these errors were encountered: