Yes, that was when I was simply trying to get GeometryEngine working with online layers. No problem doing that, but I run into difficulty when I try to get my offline data (runtime content) to the same place, where I can run GeometryEngine.within against individual features. (Polygons)
The error that I referenced in my last post was really throwing me, but it sounds like it may be a known bug, and ignorable. (?)
Beyond that, I've tinkered for a while and have the following code loading the geodatabase polygon on my map, no problem.
However, when querying, I never get queryFeaturesStatus to be "Complete". I get a value of 1 from my console.
Loading to the map implies that the data is present, just not sure how to drill down to features, so that I can do my "within" call, like what worked for me, with online resources.
Perhaps there's a better way! Any thoughts? 🙂
FeatureLayer {
id: gdbFeatureLayer
// obtain the feature table from the geodatabase by name
featureTable: gdb.geodatabaseFeatureTablesByTableName["fake_brushview_polygons"]
onLoadStatusChanged: {
map.operationalLayers.append( gdbFeatureLayer );
onQueryFeaturesStatusChanged: {
console.log( "queryFeaturesStatus: ",gdbFeatureLayer.featureTable.queryFeaturesStatus );
if( gdbFeatureLayer.featureTable.queryFeaturesStatus === Enums.TaskStatusCompleted ) {
console.log( "Query Complete!" );
}
}
}
// create the geodatabase
Geodatabase {
id: gdb
path: AppFramework.resolvedPathUrl( outputGeofencing )
}
}