You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it's a great package. I am trying to use the package for Canadian postal codes.
Regarding the accuracy scale used. I can't find an explanation for each number (3,5 and the blanks). All i found was:
1=estimated,
4=geonameid,
6=centroid of addresses or shape
The text was updated successfully, but these errors were encountered:
For many countries lat/lng are determined with an algorithm that searches the place names in the main geonames database
using administrative divisions and numerical vicinity of the postal codes as factors in the disambiguation of place names.
For postal codes and place name for which no corresponding toponym in the main geonames database could be found an average
lat/lng of 'neighbouring' postal codes is calculated.
it also lists the 3 codes you mentioned. From an earlier forum post,
Accuracy is an integer, the higher the better :
1 : estimated as average from numerically neighboring postal codes
3 : same postal code, other name
4 : place name from geonames db
6 : postal code area centroid
maybe asking on the Geonames mailing list would help getting more information as well.
Accuracy seems to describe where the values have been taken rather than the accuracy of the coordinated for postal code.
Can you @rth please give more details on the same and order according to the more precise and accurate values which can be used for query_postal_code
I think it's a great package. I am trying to use the package for Canadian postal codes.
1=estimated,
4=geonameid,
6=centroid of addresses or shape
The text was updated successfully, but these errors were encountered: