Latest Contributions by DavidSolari

Branch versioned data only uses a single table so Compress has no effect, although if there's also traditionally versioned data in the same database it might improve overall performance. ... View more

By default Pro maps will reproject all data into the coordinate system of the map, which includes any necessary datum transformations. Geoprocessing tools will also try to reproject and transform input data into the target format, but you either have to set these values on the "Environments" tab of the tool if it creates a new feature class, or hope it uses the correct transformation when you add data to an existing feature class. When in doubt, use the Project tool to get all your input data into the correct coordinate system (or the correct datum at the very least) before processing to ensure errors are minimized. Datum transformations aren't always lossless -- and I'm pretty sure NAD27 to NAD83 is a bit lossy -- but the error is often well within the tolerance of your task. ... View more

The tool has the option to return all results within an area. You'd have to do some more processing to remove duplicate street names, avoid extra intersecting streets etc. etc. but it's doable. ... View more

You can run Generate Near Table and then do a pair of joins to skip the polygons and find the closest street to each sign. If you must use the intersection polygons, do a 1-M Spatial Join from the polygons to the streets, then use Summary Statistics with the "Concatenate" mode on the street names to smush them into a single intersection, then do a 1-1 spatial join from the signs to the enriched polygons. ... View more

If you're in ArcGIS Online (or if you're using Enterprise with hosted data) look into Hosted Feature Layer Views, this allows you to lock down what your public users can access vs. your internal staff. If you're using referenced data in Enterprise you'll have to publish two sets of service, one for public use and one for private use. Don't try to be fancy with, say, map-level editing permissions and filters, anyone can take a look at the network traffic and bypass those restrictions to access your private data. ... View more

This would be a fantastic addition to both Online & Enterprise, my team always has to check this info during maintenance and few of us know the API well enough to avoid cracking maps open and enumerating the layers by hand. ... View more

Does Upgrade Attachments not add the right columns and fix the issue? I have branch versioned datasets in my 11.1 setup and running that tool gets things working perfectly. That said, if the latest version of EGDBs don't create attachment tables with those 2 attributes under all cases I'd say that's a deficiency, it's a trivial thing that would save everyone a ton of time. ... View more

One thing you can try is publishing a big rectangular polygon as a vector tile service, then using that as your basemap, that should make the downloads much smaller. Would be nice if that came with Enterprise deployments like the sample world cities do. ... View more

This is partially correct. You can't use cursors on direct database connections, but you can use them on feature service layers without bringing in the Python API. Obviously there's performance implications with this but it's possible. ... View more

That looks like a great tool, thanks Scott! That said, if I have several dozen tiny gaps to clean up, it'd be a bit faster to use something like my proposal from the Error Inspector pane as opposed to jumping to an area and switching tools each time. ... View more

Oddly enough this workflow is still in Pro, but it's part of the topology workflow actions. Having this as a choice for regular merges would be useful. ... View more

As mentioned in the docs, if you ask for an intersecting polygon using pulldata it'll grab whatever comes back first. If you want to ensure you only get one possible choice back you'll have to keep your polygons nice and tidy. ... View more

Security-wise, branch versioning hoists the main barrier to access from the database to ArcGIS Server and by extension your Enterprise setup. You publish the services out using database connections that use the data owner's authentication and then your portal's sharing options handles the rest. This is either a trivial change or a massive headache depending on how heavily your org uses Enterprise but as you've implied, ESRI is trying to make Enterprise the central hub for all remote GIS access so the sooner you bite the bullet the better. Performance is where it gets tricky. Edits to branch versioned data are supposed to be more database friendly in the long term due to only having one table that doesn't need compression, although I haven't benchmarked anything myself. You also get an archive built up of edits to DEFAULT which has none of the headaches of doing versioning + archiving in the old model. The catch is all edits have to be made through a feature service, so your overall performance drops compared to direct connection edits unless you run your servers on some very powerful hardware. The one escape hatch is if you're the "owner" of the data, you can make direct connection edits using the append, calculate field & delete features/records tools; there might be others but this is your minimum CRUD set. I say "owner" because I can never tell if you need the database owner or if your Portal authentication plays a part somehow but either way you have an avenue for doing large updates without bogging down the servers. I can't speak to DB replication, hopefully someone else can step in here. ... View more