tile38/vendor/github.com/mmcloughlin/geohash/.appveyor.yml

version: "{build}"

clone_folder: c:\gopath\src\github.com\mmcloughlin\geohash

environment:
  GOPATH: c:\gopath

install:
  - echo %PATH%
  - echo %GOPATH%
  - go version
  - go env

build_script:
  - go test -v
Faster point in polygon / GeoJSON updates The big change is that the GeoJSON package has been completely rewritten to fix a few of geometry calculation bugs, increase performance, and to better follow the GeoJSON spec RFC 7946. GeoJSON updates - A LineString now requires at least two points. - All json members, even foreign, now persist with the object. - The bbox member persists too but is no longer used for geometry calculations. This is change in behavior. Previously Tile38 would treat the bbox as the object's physical rectangle. - Corrections to geometry intersects and within calculations. Faster spatial queries - The performance of Point-in-polygon and object intersect operations are greatly improved for complex polygons and line strings. It went from O(n) to roughly O(log n). - The same for all collection types with many children, including FeatureCollection, GeometryCollection, MultiPoint, MultiLineString, and MultiPolygon. Codebase changes - The pkg directory has been renamed to internal - The GeoJSON internal package has been moved to a seperate repo at https://github.com/tidwall/geojson. It's now vendored. Please look out for higher memory usage for datasets using complex shapes. A complex shape is one that has 64 or more points. For these shapes it's expected that there will be increase of least 54 bytes per point. 2018-10-11 00:25:40 +03:00			`version: "{build}"`

			`clone_folder: c:\gopath\src\github.com\mmcloughlin\geohash`

			`environment:`
			`GOPATH: c:\gopath`

			`install:`
			`- echo %PATH%`
			`- echo %GOPATH%`
			`- go version`
			`- go env`

			`build_script:`
			`- go test -v`