0.30000000000000004
s2geometry
| 0.30000000000000004 | s2geometry | |
|---|---|---|
| 250 | 31 | |
| 1,465 | 2,411 | |
| 0.8% | 1.2% | |
| 2.0 | 6.9 | |
| 12 months ago | 21 days ago | |
| CSS | C++ | |
| GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
0.30000000000000004
-
How to detect and fix flaky tests in Pytest
This is due to the way floating point numbers are represented in memory, certain numbers like 0.3 are stored as a number very close to the original value (0.30000000000000004), but not the exact same. This problem also exists in other languages like JavaScript and C++, but is much more likely to cause problems in common applications of Python like machine learning and data science.
- Floating Point Math
- 0.1 and 0.2 = 0.30000000000000004
- 0.30000000000000004
-
What even is a JSON number?
https://0.30000000000000004.com/
Although it would be good to move in the direction of using a BigDecimal equivalent by default when ingesting unknown data.
-
Working with Numpy floats and Forex financial instruments
There's no such thing as precision for floats. Floating-point calculations are always inaccurate: read this: https://0.30000000000000004.com/
- Just learned the difference between decimal and float
-
how do i make the decimals not fucked up
Edit: This specific example even has its own website: https://0.30000000000000004.com/
s2geometry
- S2 Geometry
-
H3: For indexing geographies into a hexagonal grid, by Uber
I'm not sure either. http://s2geometry.io/ works well and you only have to really worry about 4 points to draw the circle.
- Introducing S2
-
Geospatial Indexing Sampler
I took a quick tour of the three most popular ways to index spatial data : Geohash, H3, and S2.
-
Hexagons and Hilbert Curves – The Horrors of Distributed Spatial Indices
I experimented with geospatial Hilbert Curves as a Postgres extension [0] for PostGIS using the S2 [1] spherical geometry library. S2 uses a scale free cell coverage pattern that is numbered using six interlocking space filling Hilbert Curves [2].
By having both high level (cell) and low level (cell id) geometries it was a very powerful library which allowed projection from the hilbert space into a Postgres spatial index (spgist) including various trees, like noted in this article. It appears to be still quite active in development.
[0] https://github.com/michelp/pgs2
[1] https://s2geometry.io/
[2] https://s2geometry.io/devguide/s2cell_hierarchy
- Show HN: TG – Fast geometry library in C
- Unum: Vector Search engine in a single file
-
Understanding Geohashes
If you check the h3geo comparison page, you should see plenty of alternatives to geohash, such as s2 or even h3 itself.
- Evaluation of Location Encoding Systems
-
Inscribed angle theorem in 3D/higher dimension
See some discussion I started at https://github.com/google/s2geometry/issues/190
What are some alternatives?
glibc - Unofficial mirror of sourceware glibc repository. Updated daily.
h3 - Hexagonal hierarchical geospatial indexing system
proposal-decimal - Built-in exact decimal numbers for JavaScript
open-location-code - Open Location Code is a library to generate short codes, called "plus codes", that can be used as digital addresses where street addresses don't exist.
gcc
protoc-gen-star - protoc plugin library for efficient proto-based code generation