3 ms·
As a geographer turned DS it is my duty to remind CS people that all geo methods are compromises. No system, s2, h3, mgrs, even lat lon are perfect for every pr
by PLenz 5y ago
As a geographer turned DS it is my duty to remind CS people that all geo methods are compromises. No system, s2, h3, mgrs, even lat lon are perfect for every project and you must think carefully about what you are doing and pick your geo representation based on your givens and druthers.
- deleted 5y ago[deleted]
- monkeybutton 5y agoIf you had to represent arbitrary plots of land as fixed sized vectors for a ML model, what would you use?
- PLenz 5y agoDepends on where the land is and size and shape of the polygons are
- monkeybutton 5y agoLet's say the land is confined to north America, the size can vary from an entire state to a single zip code (I know zips are logical addressing, not geological, but I have what I have), and the shape is unrestricted so it could be non-convex. I suppose one could convert various kinds of areas (states, cities, boroughs, ...) to lists of zipcodes contained within and OHE them but I feel like that would be the _worst_ solution.
- PLenz 5y agoI would probably use h3 for this which each polygon being reduced to a list of hex ids.
- s2mcallis 5y agoS2 wouldn't be a bad choice, it lets you compute "coverings" of arbitrary regions as S2 cells, with variable resolution. Fixed size is trickier but is probably doable, especially if you're allowed to null out unused cells. Check out https://s2.sidewalklabs.com/regioncoverer/ https://s2.sidewalklabs.com/regioncoverer/
- deleted 5y ago[deleted]