Latest Contributions by ToddFagin

We have an organizational AGOL account with more than sufficient credits. In AGOL, in the Geocoding section of Utility services, it shows the ArcGIS World Geocoding Service. However, when we go to geocode in ArcGIS Pro, the only Input Locator available is the Esri World Geocoder. If we use it, we get zero matches. If we try to rematch, we get a "Geocoding result not stored. Ensure you are signed in to ArcGIS Online and have geocoding privilege." After much tinkering, ArcGIS World Geocoding Service now shows, but it still does not work. This is preventing us from doing a very basic task. Interestingly, I have access to other organizational accounts and have not encountered any problems there (and this is not a problem that existed prior). NOTE: As working through this, I tried it on another computer with a different Pro version and it worked. I think it may be a 3.5.1 issue. I am still checking, but I would appreciate any feedback in the meantime. Second Edit: While it works on 3.4.2, it is not solely a 3.5.1 issue on second though because when I log into a different organization, it works on 3.5.1.       ... View more

Several years ago, I (with help from this fine community) developed a simple app that, when a user searched for a location (address, XY, etc.) using the search widget, a featurelayer was also queried and a pop-up would provide information from that feature layer. Example: an individual would enter an address and the search widget would query a state house district layer, resulting in a pop-up with info. about the district in which the address occurs (code snippet below to show what was done).     searchWidget.on('select-result', function(evt){ let query = hsb.createQuery(); query.geometry = evt.result.feature.geometry; query.spatialRelationship = 'within'; query.outFields = ['*']; query.returnGeometry = true; query.outSpatialReference = view.spatialReference; query.maxAllowableOffset = 0; hsb.queryFeatures(query).then(function(result){ view.popup.open({ features: result.features, location: result.features[0].geometry.centroid }); }); });     We now have a need to do this for taxable jurisdictions. However, a single location can fall within multiple taxable jurisdictions (e.g. county, municipality, etc.), necessitating querying multiple layers and, ideally, returning a single pop-up. The quickest, easiest solution would be to union the various layers and then query against it, but these data are dynamic, so being able to query each layer individually and returning the results at once is a better solution. Anyone have any examples of something comparable I could use as a potential guide? ... View more

We recently updated our GIS stacks which necessitated upgrading the Postgres versions, as well. We followed the guidelines to do a pg_dump and pg_restore and read the documentation that stated that OIDs are not supported with newer versions of Postgres. However, when we try to do anything in the database, we are unable to. For instance, if we try to add a new feature class, we receive a an ERROR 160332: The table does not have an OID Field. Well, we know this. It also prohibits us from taking maps that use the database as a datastore offline and so on and so forth. Is there a fix to this? ... View more