Latest Contributions by MarcWouters

Hello Joshua, Sorry for the late reply (I'm leaving my current position, and have lots of things to wrap up). Thanks for the code snippet.  I've implemented your proposal (with a few modifications), and it works OK.  Unfortunately I cannot avoid temporary layers. It's quite time consuming (a query for every single point), but I cannot do it with the complete table, because the Intersect tool doesn't keep my features in the same order, and this is something I MUST have. Thanks again. ... View more

I don't clearly understand the difference between ArcPy and ArcGIS API for Python. Aren't they both using Python functions to get things automated which you can do manually in ArcGIS Pro ? ... View more

Hi Lucas, I've checked again to be sure : field name and alias are both 'Name'. I've checked both for the layer and the mapView that isLabelsEnabled() return true. I've ran the code without the attached renderer. I've changed the parent for the LabelDefinition to this (was empty) and the parent for the layer also to this (was the map). Nothing. The only difference I can see now is that my FeatureLayer is based on a GeodatabaseFeatureTable, while you use a ServiceFeatureTable in your sample code.  Could this be the reason why I don't see labels ? Looking further in the reference I noticed a class LabelingInfo. But I cannot find how to connect this to the layer of the mapView. Could this help ? Thanks for looking into this further. Marc ... View more

I have looked at the sample code, but there is one (probably important) difference : instead of a ServiceFeatureTable, we are using a GeodatabaseFeatureTable - all operations are done off-line. This also means that there is no applyEdits() method to invoke.  Updating attributes works fine, by the way, but updating geometry is causing me headaches.... ... View more

Hi Eric, I am in contact with Belux technical support, they will know how to handle this. ... View more

Eric, I've looked at the sample, but I think this is not relevant for my problem. I don't need to display my data in 3D (but I need them for calculations), therefor I don't use SurfacePlacement. The problem occurs already before I can show them on the MapView : when downloading a copy (to make a runtime .geodatabase) the features with ShapeLength 0 are skipped. Any other suggestions ? ... View more

I have nu idea ! First time to see about this class Where do I need to set this SurfacePlacement ?   When creating my features, when sharing my data to the service, when downloading it into a runtime geodatabase ? Is there a default setting ? Please teach me about this. ... View more

Luke, (First of all : how do you add a code snippet with line numbers, like you did above ? Can't find it) I've modified a code sample I've found somewhere on one of the many ArcGIS webpages  From the featureServiceInfo(), I can obtain layerInfos() and tableInfos(), which have ID numbers. Here I can see that lower ID numbers are assigned to the spatial layers, followed by the non-spatial tables. I cannot assign layerOptions here yet, because my parameters are not generated yet. I cannot add an extra parameter in the generate(params) method, because of the lambda syntax (I'm not so familiar with this construct, but it works) => global parameter m_numLayersInService. Like this it works, although I will not win any beauty contest with this  Marc void myClass::downloadCopy()  {    GeodatabaseSyncTask* task = new GeodatabaseSyncTask(QUrl("url_of_service"));    connect(task, &GeodatabaseSyncTask::doneLoading, this, [this](Error error) {       if (!error.isEmpty()) {          qDebug() << "Error loading GeodatabaseSyncTask:" << error.message()        }       else {          ArcGISFeatureServiceInfo featureServiceInfo = task->featureServiceInfo();          QList<IdInfo> layerInfo = featureServiceInfo.layerInfos();          m_numLayersInService = layerInfo.size();          QList<IdInfo> tableInfo = featureServiceInfo.tableInfos();          for (int i = 0; i < layerInfo.size(); ++i) {             qDebug() << "Layer" << layerInfo.name() << "ID" << layerInfo.infoId();          }          for (int i = 0; i < tabelInfo.size(); ++i) {             qDebug() << "Table" << tableInfo.name() << "ID" << tableInfo.infoId();          }          Envelope area(-20e6, -7e6, 20e6, 15e6, featureServiceInfo.spatialReference());          task->createDefaultGenerateGeodatabaseParameters(area);       }    });    // Default parameters generated ? => generate the offline geodatabase    connect(task, &GeodatabaseSyncTask::defaultGenerateGeodatabaseParametersCompleted,          this, [this](QUuid, GenerateGeodatabaseParameters parameters) {       generate(parameters);      });    task->load(); } void myClass::generate(GenerateGeodatabaseParameters params) {    params.setSyncModel(SyncModel::Layer);    QList<GenerateLayerOption> glo = params.layerOptions();    for (int i = m_numLayersInService; i < glo.size(); ++i) {       glo.setUseGeometry(false);       glo.setWhereClause("1=1");    }    params.setLayerOptions(glo); } ... View more

Hi Luke, I am stupid. Of course it works, because you actually set the LayerOptions in the params (line 13 in your code snippet) In my code, I only changed a copy, but didn't assign them back to the actual parameters. Now it works as documented. Just one small thing : is there a way to identify the layers in GenerateLayerOption list by name or so? From the GeodatabaseSyncTask::featureServiceInfo(), I can get the layernames (spatial) and the tablenames (non-spatial). This allows me to calculate the number of the layer in the GenerateLayerOption list with the 1st non-spatial table. There should be an easier way to find this. ... View more

Hi Luke, I've tried that already, without success. Perhaps my whereClause is not valid ? (but I've successfully used this in other queries). params.setSyncModel(SyncModel::Layer); QList<GenerateLayerOption> glo = params.layerOptions(); for (int i = 0; i < glo.size(); ++i) {    glo.setQueryOption(GenerateLayerQueryOption::All);    if (i > 10) {      // the first layers do have geometry       glo.setUseGeometry(false);       glo.setWhereClause("1=1");    } } Do I need to change something else ? ... View more

Thanks for the update !!! ... View more