-
Notifications
You must be signed in to change notification settings - Fork 61
Description
I discovered two entries with errors that need correcting:
| id | postcode | locality | state | lat | long | Lat_precise | Long_precise |
|---|---|---|---|---|---|---|---|
| 7987 | 4120 | LORETO HILL | QLD | -27.5087 | 153.0442 | -26.0118 | 111.348 |
ID 7987: Lat_precise & Long_precise are WAY off. The locality does not actually come up in Google Maps. I think the lat and long are correct and should be copied over to the precise fields. This also matches Geonames and the surrounding localities.
| id | postcode | locality | state | lat | long | Lat_precise | Long_precise |
|---|---|---|---|---|---|---|---|
| 8086 | 4171 | BALMORAL | QLD | -27.456 | 153.0604 | -27.4539 | 153.0669 |
| 8087 | 4171 | BULIMBA | QLD | -27.456 | 153.0604 | -27.45 | 153.058 |
| 8089 | 4171 | HAWTHORNE | QLD | -27.456 | 153.0604 | -27.467 | 153.058 |
| 8088 | 4171 | GALLOWAYS HILL | QLD | -10.7833 | 142.417 | -10.7833 | 142.417 |
ID 8088: You'll notice Galloways Hill's location is grossly different to the surrounding localities in this postcode, and is clearly incorrect. Google Maps identifies a mountain peak in far north Queensland as Galloways Hill, but with a very different postcode (4876). The lat/long and Precise_lat/Precise_long in your list seem to incorrectly point to this north QLD place, far from the localities in 4171 which are in Brisbane. I would suggest using -27.475, 153.064 for both sets of fields, from Geonames, which matches closely with the surrounds.
If it's helpful to make a pull request with the updates, I can do so.