Latest Contributions by NateArnold

+1 on this 🙂 Referencing data already on our web server would be great, since we're not using AGO for data hosting.  We already have our own open data catalog in place, but it lacks the multiple format download options of open data.  I'm actually working on a rolling 180 day crime export right now (csv with lat/long), and it would be great to upload this to our web server and have it published to open data.  I imagine for others direct upload of csv (with an associated tool/arcpy element) to hosted AGO would be useful, plus as you mentioned upload from ESRI Maps for Office. Nate ... View more

The 'sdelayer -o register' command is used to register tables or views in native storage (or ST_GEOMETRY, where available) with ArcSDE Thanks for that.  Bummer more command line. Nate ... View more

Also, one other problem we had when coming from 9.3 to 10.1 was that we changed from the default LONGRAW storage in Oracle to Geometry in SQL Server.  Changing data sources in our AGS mxd's to the new gdb resulted in problems with the shape area and length fields.  ArcMap did not properly interpret the change in fields, and the publisher/analyzer did not catch the problem, which resulted in AGS map service errors.  I'm not sure if any of the newer builds have caught this though.  Nate ... View more

They certainly can be registered with an enterprise geodatabase, if you a) have an enterprise geodatabase, and b) choose to do so. Please explain how to do this.  I've created a view using CreateDatabaseView_management, in a SQL Server gdb, using an owner account, on a feature class owned by that account.  After creating the view, right-click context menu --> Regsiter with geodatabase is greyed out.  When I run RegisterWithGeodatabase_management against it, I receive ERROR 001399: Views are not supported. Query Layers are a way of accessing spatial databases without ArcSDE.. This is an interesting point.  True, CreateDatabaseView_management can be used for non-spatial table views too, but if it's used against feature classes that are already in ArcSDE, I think the tooling should be able to take advantage of registering the view instead of leaving it as a query layer. It's not just spatial views, it's all tables which involve GEOMETRY/GEOGRAPHY objects, but these are an aspect of Microsoft's database implementation (and the difficulty of tuning it), not anything Esri has control over. That's fine, just as an FYI to the original poster.  We found for best performance with our data, load datasets into ArcSDE with the SDEBINARY keyword, then build the registered spatial view with command line tools.  Of course, you should try it with one of the other storage types and compare 🙂 Nate ... View more

Vince, From an end user perspective, I think ESRI has done a terrible job of clarifying differences between spatial views and query layers:  When you use SSMS to make a "view that includes a spatial column", why would it not be interpreted as a "spatial view" (confusion in terms)?  When the CreateDatabaseView_management tool was introduced, why would an end user not think "I can use this tool to make a spatial view", when it actually gets interpreted in ArcGIS as a query layer?  Why can views created using SSMS or CreateDatabaseView_management not be registered with the GDB (and hence store feature type, extents, description/metadata, etc.)? ArcGIS 10.1+ has seen much of the command line tools become GP/GUI tasks, but creating actual spatial views is one are where ESRI needs to focus.  Since there is indeed a speed difference between spatial views and query layers, but views are much easier to manage using SSMS, our approach has been to make a "dummy" spatial view using command line, then modify the view definition in SSMS.  We've also seen a speed difference between spatial views built on feature classes stored in the default Geometry spatial type (slower) versus SDEBINARY (faster).  Nate ... View more

Paul, Thanks for posting your solution - I needed pip and poster, which required setuptools.  Your workaround helped me get everything working. Nate ... View more

Hi Jeff: Thanks for the response.  The help link you provided is specifically for publishing Image services, which I am not doing.  I'm trying to publish a map service based on an mxd that has a mosaic dataset in it.  This is the point of my question - why is the extension required for map services? ... View more

Thanks, Bubba Hey!  This solution worked for me as well - I didn't realize the SP was the full installer. Nate ... View more

I just wanted to revive this topic, as I've run into this again using 10.1 SP1 which I'd hoped handled this differently.  When copy/pasting between geodatabases, an archive-enabled feature class loses its history table.  This seems counter to the concept of archiving - what are the chances that nothing will ever go wrong with your enterprise GDB?  Or, in our case, when migrating to a new RDBMS platform?  Or, what if you want to serve archive-enabled data via file GDB?  Feature attachments go along with the feature class with copy/paste operations, so why not archive classes too?  Or, at the very least why doesn't an option exist toreuse existing _H tables when enabling archiving, instead of ignoring it and making a bunch of _H1 tables?  Is ESRI's workaround that you should just load up all the records from your original _H tables into the new _H1 tables?  Seems like there should be a better way (and if there is, please let me know!). Nate ... View more

If you're not running the application server, then command line tools are still useful for working with dbtune.  However, all that stuff can be edited in the config tables directly, so if you're using all direct connect then the service really isn't required.  Do your RAM a favor and don't install it 🙂 Nate ... View more