mirror
/
tile38
mirror of https://github.com/tidwall/tile38.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
tile38/vendor/github.com/tidwall/geojson/linestring_test.go

75 lines
3.1 KiB
Go
Raw Normal View History

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
package geojson
import "testing"
func TestLineStringParse(t *testing.T) {
expectJSON(t, `{"type":"LineString","coordinates":[[1,2,3]]}`, errCoordinatesInvalid)
expectJSON(t, `{"type":"LineString","coordinates":[[1,null]]}`, errCoordinatesInvalid)
expectJSON(t, `{"type":"LineString","coordinates":[[1,2]],"bbox":null}`, errCoordinatesInvalid)
expectJSON(t, `{"type":"LineString"}`, errCoordinatesMissing)
expectJSON(t, `{"type":"LineString","coordinates":null}`, errCoordinatesInvalid)
expectJSON(t, `{"type":"LineString","coordinates":[[null]]}`, errCoordinatesInvalid)
expectJSON(t, `{"type":"LineString","coordinates":[null]}`, errCoordinatesInvalid)
expectJSON(t, `{"type":"LineString","coordinates":[[1,2,3,4,5]]}`, errCoordinatesInvalid)
expectJSON(t, `{"type":"LineString","coordinates":[[1]]}`, errCoordinatesInvalid)
g := expectJSON(t, `{"type":"LineString","coordinates":[[3,4],[1,2]]}`, nil)
expect(t, g.Rect() == R(1, 2, 3, 4))
expectJSON(t, `{"type":"LineString","coordinates":[[3,4],[1,2]],"bbox":null}`, nil)
expectJSON(t, `{"type":"LineString","coordinates":[[3,4],[1,2]],"bbox":[1,2,3,4]}`, nil)
}
Update geojson dependency
2019-01-10 19:37:20 +03:00
func TestLineStringParseValid(t *testing.T) {
json := `{"type":"LineString","coordinates":[[1,2],[-12,-190]]}`
expectJSON(t, json, nil)
expectJSONOpts(t, json, errDataInvalid, &ParseOptions{RequireValid: true})
}
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
func TestLineStringVarious(t *testing.T) {
var g = expectJSON(t, `{"type":"LineString","coordinates":[[3,4],[1,2]]}`, nil)
expect(t, string(g.AppendJSON(nil)) == `{"type":"LineString","coordinates":[[3,4],[1,2]]}`)
expect(t, g.Rect() == R(1, 2, 3, 4))
expect(t, g.Center() == P(2, 3))
expect(t, !g.Empty())
g = expectJSON(t, `{"type":"LineString","coordinates":[[3,4],[1,2]],"bbox":[1,2,3,4]}`, nil)
expect(t, !g.Empty())
expect(t, g.Rect() == R(1, 2, 3, 4))
expect(t, g.Center() == R(1, 2, 3, 4).Center())
}
Update geojson dependency
2019-01-10 19:37:20 +03:00
func TestLineStringValid(t *testing.T) {
var g = expectJSON(t, `{"type":"LineString","coordinates":[[3,4],[1,2]]}`, nil)
expect(t, g.Valid())
}
func TestLineStringInvalid(t *testing.T) {
var g = expectJSON(t, `{"type":"LineString","coordinates":[[3,4],[1,2],[0, 190]]}`, nil)
expect(t, !g.Valid())
}
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
// func TestLineStringPoly(t *testing.T) {
// ls := expectJSON(t, `{"type":"LineString","coordinates":[
// [10,10],[20,20],[20,10]
// ]}`, nil)
// expect(t, ls.(*LineString).Contains(ls))
// expect(t, ls.Contains(PO(10, 10)))
// expect(t, ls.Contains(PO(15, 15)))
// expect(t, ls.Contains(PO(20, 20)))
// expect(t, ls.Contains(PO(20, 15)))
// expect(t, !ls.Contains(PO(12, 13)))
// expect(t, !ls.Contains(RO(10, 10, 20, 20)))
// expect(t, ls.Intersects(PO(10, 10)))
// expect(t, ls.Intersects(PO(15, 15)))
// expect(t, ls.Intersects(PO(20, 20)))
// expect(t, !ls.Intersects(PO(12, 13)))
// expect(t, ls.Intersects(RO(10, 10, 20, 20)))
// expect(t, ls.Intersects(
// expectJSON(t, `{"type":"Point","coordinates":[15,15,0]}`, nil),
// ))
// expect(t, ls.Intersects(ls))
// lsb := expectJSON(t, `{"type":"LineString","coordinates":[
// [10,10],[20,20],[20,10]
// ],"bbox":[10,10,20,20]}`, nil)
// expect(t, lsb.Contains(PO(12, 13)))
// expect(t, ls.Contains(PO(20, 20)))
// }