You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently outputting both feature.coordinates and feature.geometry.coordinates. The former is the result of layer.feature(i).loadGeometry(); which is a custom structure of x,y in tile coordinates. The latter is geojson coordinates. I think we should output only the latter by removing this line:
@@ -69,7 +78,6 @@ function readTile(args, buffer, callback) {
var layer = tile.layers[layerID];
for (var i = 0; i < layer.length; i++) {
var feature = layer.feature(i).toGeoJSON(args.x, args.y, args.z);
- feature.coordinates = layer.feature(i).loadGeometry();
collection.features.push(feature);
}
});
/cc @jfirebaugh who might remember if there was a reason for feature.coordinates = layer.feature(i).loadGeometry();.
The text was updated successfully, but these errors were encountered:
We are currently outputting both
feature.coordinates
andfeature.geometry.coordinates
. The former is the result oflayer.feature(i).loadGeometry();
which is a custom structure of x,y in tile coordinates. The latter is geojson coordinates. I think we should output only the latter by removing this line:/cc @jfirebaugh who might remember if there was a reason for
feature.coordinates = layer.feature(i).loadGeometry();
.The text was updated successfully, but these errors were encountered: