{"action":"created","issue":{"url":"https://api.github.com/repos/georust/rust-geo/issues/137","repository_url":"https://api.github.com/repos/georust/rust-geo","labels_url":"https://api.github.com/repos/georust/rust-geo/issues/137/labels{/name}","comments_url":"https://api.github.com/repos/georust/rust-geo/issues/137/comments","events_url":"https://api.github.com/repos/georust/rust-geo/issues/137/events","html_url":"https://github.com/georust/rust-geo/issues/137","id":249158610,"number":137,"title":"Coordinates are stored as Floats. Could they also be integers?","user":{"login":"rory","id":1547,"avatar_url":"https://avatars2.githubusercontent.com/u/1547?v=4","gravatar_id":"","url":"https://api.github.com/users/rory","html_url":"https://github.com/rory","followers_url":"https://api.github.com/users/rory/followers","following_url":"https://api.github.com/users/rory/following{/other_user}","gists_url":"https://api.github.com/users/rory/gists{/gist_id}","starred_url":"https://api.github.com/users/rory/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rory/subscriptions","organizations_url":"https://api.github.com/users/rory/orgs","repos_url":"https://api.github.com/users/rory/repos","events_url":"https://api.github.com/users/rory/events{/privacy}","received_events_url":"https://api.github.com/users/rory/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2017-08-09T20:55:18Z","updated_at":"2018-03-01T14:12:09Z","closed_at":null,"author_association":"MEMBER","body":"Currently, the fundamental \"unit\" is `num_traits::Float`, i.e. all x/ys (or lat/longs) are represented as `Float`. And I wonder if this needs to be? I have a project which does things and eventually projects/rasterises geometry to a integer grid, and there's no 100% easy way to store this. Yes I can use Floats, and then truncate at the very end, but that seems subpar. I'm not suggesting removing `Float`, but *expanding* what can be stored in/as a Geometry/etc.\r\n\r\nObviously some algorithms wouldn't work on integers (e.g. `Area` calculation), and the Area trait would still use `T: Float`. \r\n\r\nI have a branch locally which does this, and it's that much of a change to support `PrimInt` and `Float`.\r\n\r\nWhat do yous think?"},"comment":{"url":"https://api.github.com/repos/georust/rust-geo/issues/comments/369603373","html_url":"https://github.com/georust/rust-geo/issues/137#issuecomment-369603373","issue_url":"https://api.github.com/repos/georust/rust-geo/issues/137","id":369603373,"user":{"login":"urschrei","id":131862,"avatar_url":"https://avatars0.githubusercontent.com/u/131862?v=4","gravatar_id":"","url":"https://api.github.com/users/urschrei","html_url":"https://github.com/urschrei","followers_url":"https://api.github.com/users/urschrei/followers","following_url":"https://api.github.com/users/urschrei/following{/other_user}","gists_url":"https://api.github.com/users/urschrei/gists{/gist_id}","starred_url":"https://api.github.com/users/urschrei/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/urschrei/subscriptions","organizations_url":"https://api.github.com/users/urschrei/orgs","repos_url":"https://api.github.com/users/urschrei/repos","events_url":"https://api.github.com/users/urschrei/events{/privacy}","received_events_url":"https://api.github.com/users/urschrei/received_events","type":"User","site_admin":false},"created_at":"2018-03-01T14:12:09Z","updated_at":"2018-03-01T14:12:09Z","author_association":"MEMBER","body":"I don't do much raster stuff atm so I'm not really qualified, but it definitely _seems_ like a good idea. We should definitely explain what's going on in the docs, point out caveats etc. when this turns into a PR, though."}}
{"actor":{"display_login":"urschrei"}}