Closed gabegm closed 3 years ago
could you provide the expected unique h3 indexes?
I test it with https://github.com/uber/h3-py
it also get the same 8452c89ffffffff
.
import h3
resolution = 3
print("resolution3: ", h3.geo_to_h3(11.474228, 48.144711, resolution),
h3.geo_to_h3(11.666443, 48.138521, resolution))
resolution = 4
print("resolution4: ", h3.geo_to_h3(11.474228, 48.144711, resolution),
h3.geo_to_h3(11.666443, 48.138521, resolution))
resolution = 5
print("resolution5: ", h3.geo_to_h3(11.474228, 48.144711, resolution),
h3.geo_to_h3(11.666443, 48.138521, resolution))
resolution3: 8352c8fffffffff 8352ccfffffffff
resolution4: 8452c89ffffffff 8452c89ffffffff
resolution5: 8552c887fffffff 8552cc2ffffffff
Thanks for the speedy reply!
Maybe I have this wrong, but shouldn't I be getting two unique H3 keys for both coordinates as per the two examples in the screenshots above?
Could this be an incorrect projection?
Hey guys just took a quick look, I think you have the co-ordinates in backwards
julia> gd = [
(48.144711, 11.474228), # west (lat, lon)
(48.138521, 11.666443) # east
]
2-element Vector{Tuple{Float64, Float64}}:
(48.144711, 11.474228)
(48.138521, 11.666443)
julia> [geoToH3(GeoCoord(deg2rad.(location)...), 4) for location in gd]
2-element Vector{UInt64}:
0x0841f8d5ffffffff
0x0841f8d7ffffffff
this worked for me!
Many thanks @spcogg!!
Hi there, not sure if this is a bug or some wrong doing of mine, my apologies if it's the latter, although I have cross checked the results with H3 viz web apps and am not getting the same results.
Problem description
Environment information
Details
First Point
Second Point
H3 Visualiser 1st example
H3 Visualiser 2nd example