whosonfirst / go-whosonfirst-spatial Goto Github PK

https://marianogappa.github.io/software/2020/04/01/webassembly-tinygo-cheesse/

https://github.com/whosonfirst/go-whosonfirst-spatial/blob/master/static/javascript/whosonfirst.spatial.pip.init.js

Probably a custom Coord struct not that the universe needs one but it would be one less package to import.

Pass a Feature or an ID or ... ?

https://github.com/whosonfirst/go-whosonfirst-spatial-rtree

For example only "reversegeo" geometries. Uncertain at this time where these hooks should be added or how they filter down to specific implementations (rtree, sqlite, etc.)

Related:

• whosonfirst-data/whosonfirst-data#367
• whosonfirst-data/whosonfirst-data#1793

https://github.com/engelsjk/rtyq

Something like:

IsAlt(flags.ExistentialFlag) bool

But that begs the question of how you filter on a specific alternate geometry or geometries. If we did something like we did for placetypes:

HasPlacetypes(flags.PlacetypeFlag) bool
HasAlternates(flags.AlternateFlag) bool

We will need to change the go-whosonfirst-spr interface.

https://github.com/iwpnd/piper

https://github.com/akhenakh/insidetree

https://github.com/tidwall/geometry

Cache properties body using whosonfirst/go-cache on ingest?

Instead of whosonfirst/go-cache

https://github.com/rowanwins/point-in-polygon-hao

Thanks for README. I understand it's for structural reorganization.

go-whosonfirst-pip-v2 consumes days for Indexing. Is it possible to speed up indexing? hopefully ten or hundred times.

Another concern is memory usage. I'm not sure that memory thrashing is the main cause of the slow indexing or not. Of course we could use a larger machine, but we have some restriction.

Pass it down to the templates and assign to a data attribute in inc_head.html

https://github.com/whosonfirst/go-whosonfirst-spatial/blob/master/static/javascript/whosonfirst.spatial.init.js

https://github.com/whosonfirst/go-whosonfirst-spatial/blob/master/templates/html/inc_head.html

https://github.com/whosonfirst/go-whosonfirst-spatial/blob/master/http/www/pip.go

Blocked on #4

https://github.com/tidwall/buntdb

Principally for use with the SQLite-related package where the assumption is the -spatial-database-uri flag may reference a database that has already been indexed.

At present the work-around is do this:

go run -mod vendor cmd/server/main.go -... -mode directory://

Where we set the -mode flag but don't pass any files to index.

Make sure issue #24 works first.

https://github.com/whosonfirst/go-whosonfirst-browser#select

At a minimum provide an example. Silencing the placetype=alt warnings (for alternate geometries) would be a good example.

It is causing things to be slow, as documented here:

• whosonfirst/go-whosonfirst-spatial-sqlite#2

The reasons are outlined here:

• https://github.com/whosonfirst/go-whosonfirst-geojson-v2/blob/master/geometry/polygon.go

This points to a wholesale refactoring of how geometries are handled in go-whosonfirst-geojson-v2 but in the meantime we should just update the caching layer, here, to be more efficient. If that work is successful perhaps it can be applied to the geojson package.

Specifically: https://github.com/whosonfirst/py-mapzen-whosonfirst-hierarchy/blob/master/mapzen/whosonfirst/hierarchy/__init__.py

https://github.com/akhenakh/regionagogo

So that the spatial database itself can be used for reading stuff.

https://github.com/engelsjk/polygol

• https://medium.com/@tidwall/faster-geospatial-queries-in-tile38-f771e2f6b1bd
• https://github.com/tidwall/rtree