We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Geographic + vector data structures already handle coordinate values as double.
Geographic
Change also other key classes handling geographic and projected coordinate data to use double type instead of num. The aim is to simplify class APIs.
The text was updated successfully, but these errors were encountered:
refactor(geobase): change num to double in for coordinate values in v…
c6d011a
…arious classes like Position, Box, Projected and ProjBox, many other refactorings too #186 BREAKING CHANGE: the API of Position and Box changed
refactor(geobase): PositionData with coordinate value type generics a…
8396be3
…s always double #186
refactor(geobase): num to double changes on web mercator converter #186
26fdf54
docs(geobase): update diagram about Position and Box #186
6129a87
docs(geobase): about double and int types in position, bounding box a…
b494061
…nd scalable coordinates #186 #183
Implemented in geobase 0.5.0
Sorry, something went wrong.
No branches or pull requests
Geographic
+ vector data structures already handle coordinate values as double.Change also other key classes handling geographic and projected coordinate data to use double type instead of num. The aim is to simplify class APIs.
The text was updated successfully, but these errors were encountered: