|
POST
|
I don't know the difference between a direct connection and a ArcSDE connection. I'm just trying to get Desktop 10.2.2 ArcCatalog >Database Connections>Add Database Connection to make a connection to Server 10.3.1. Which is that? Direct Connection?
... View more
11-20-2015
03:30 PM
|
0
|
3
|
1457
|
|
POST
|
In that first link, if I go down to client 10.2 and slide left to Enterprise geodatabase using an ArcGIS service connection, I don't see geodatabase 10.3.1. Just up to 10.2.2.
... View more
11-20-2015
01:38 PM
|
0
|
12
|
1457
|
|
POST
|
After a long and painful process of upgrading from Server 9.3.1 to Server 10.3.1 https://community.esri.com/thread/161853 because our Desktop 10.2.2 users could not connect to Server 9.3.1 https://community.esri.com/thread/165892, now I can't figure out a way to make a database connection from Desktop 10.2.2 to Server 10.3.1. Are my 10.2.2 users stuck between server versions?
... View more
11-20-2015
11:01 AM
|
0
|
14
|
5959
|
|
POST
|
Still adjusting to ArcServer 10.3.1 from ArcServer 9.3. In the dark old days, I just put my selected LIDAR multipoints, and breaklines in SDE geodatabase feature datasets and produced several kinds of terrains for the users. But now in this 10.x plus era, users can generate different kinds of views directly from the LAS points. Although it seems like I could create mosaic datasets in my new enterprise geodatabase, I'm wondering if there is a role for the enterprise geodatabase for the LAS points and the LAS datasets. What are best practices for allowing my power users access to the LAS point data, while allowing read only access to my occasional users? Just keep the LAS points in folders, and regulate access by Windows user accounts? Is there any role for also storing LAS data as multipoint feature classes? Is terrain generation still needed?
... View more
11-16-2015
03:08 PM
|
0
|
0
|
3463
|
|
POST
|
It works! We just had to go back one step: took the SQL 2008 backup and restored to a SQL 2013 geodatabase I had already created named lidar09. Now all my data is moved off the old server and is safely on the new server. And the real work of re-organizing and publishing services begins. Asrujit was really on the right path when he suggested the database name was wrong.
... View more
11-05-2015
02:03 PM
|
2
|
0
|
572
|
|
POST
|
Thanks. Now I won't have to keep beating my head against this wall. Above, Asrujit SenGupta suggested I try the Export/Import XML Workspace Document tool for my remaining troublesome geodatabase. The route from Enterprise 9.3 to Enterprise 10.3.1 that worked best for me was backup and restore to SQL 2008 at another agency's SQL 2008 instance, then bring the backup home and restore to SQL 2012. But for just this one geodatabase, someone in the chain of custody seems to have changed the database name from lidar09 to lidar. I'm going to have to ask the DBAs involved to repeat the process or track down where the name change occurred.
... View more
11-05-2015
09:24 AM
|
0
|
1
|
572
|
|
POST
|
The troublesome geodatabase, the one that didn't work when I did the two step backup/restore, created a 26 gb xml file. Now that that import xml workspace document option has been shown not to work for 9.3 to 10.3.1, I'll have to go back and repeat the two step process or track down where the DBAs inadvertently changed the database name.
... View more
11-05-2015
09:09 AM
|
0
|
1
|
1927
|
|
POST
|
I have been trying to import a xml file made with export xml workspace document from a 9.3 enterprise geodatabase, SQL server, to a 10.3.1 enterprise geodatabase, SQL server. Trying the whole geodatabase, importing to a new empty geodatabase, I got "999999 : Error executing function" and "The application is not licensed to create or modify schema for this type of data." and "The operation was attempted on an empty geometry" and "Failed to execute (ImportXMLWorkspaceDocument)." I then tried a smaller piece of the old geodatabase, just a single feature dataset. Tried importing to a different non empty geodatabase. Tried remaking the xml file from the old geodatabase. Always get the same error messages.
... View more
11-04-2015
11:45 AM
|
0
|
1
|
4194
|
|
POST
|
I wonder why Import XML Workspace Document tool gave me a crash of Desktop 10.3.1 to the "Serious Problem. Tell ESRI what you were doing" window. I'll try exporting just a feature dataset to xml next.
... View more
11-03-2015
03:43 PM
|
0
|
3
|
1369
|
|
POST
|
Thanks, that was easy. I thought I was losing it. I remember the import button looking like the image at the end of this thread. https://community.esri.com/message/77856#77856 Also, 10.2.2 Help doesn't mention a pulldown, it just says "Alternatively, click Import and navigate to the feature class or feature dataset that uses the spatial reference you want to use as a template. "
... View more
10-30-2015
09:32 AM
|
0
|
0
|
1006
|
|
POST
|
I am trying to create some new feature datasets for lidar terrains in an SQL enterprise geodatabase in ArcCatalog 10.3.1. However, when I right click in 10.3.1 ArcCatalog or ArcMap Catalog Window > New > Feature Dataset, after naming the new feature dataset, the next window wants me to define the xy coordinate system. In my experience, and in the 10.3.1 and 10.2.2 help files, there is supposed to be an Import button on this window that allows me to get the coordinate system from an existing feature class. (as in the link above to another thread) I don't understand why it seems to be missing in both Desktop 10.3.1 for enterprise geodatabases and with Desktop 10.2.2 using file geodatabases. (see image below) Is there an option in Desktop that I need to set? Some discussions here indicate that when I import a feature class into a feature dataset, the coordinate system will be converted to match the coordinate system of the receiving feature dataset. I just get "the spatial references do not match" message. I've tried to set the xy and z coordinate systems of a new feature dataset carefully to match the feature classes that are going into it, but I still get a "the spatial references do not match" message when I try to move a feature class into the new feature dataset. The Create Feature Dataset (Data Management) tool looks like it still has the option of getting spatial reference " By referencing a feature class or feature dataset whose spatial reference you want to apply, such as C:/workspace/myproject.gdb/landuse/grassland. " so I could try this in a python window. But what happened to my import button?
... View more
10-30-2015
09:15 AM
|
0
|
2
|
2987
|
|
POST
|
When I tried copy/paste in 10.3.1 ArcCatalog, the paste failed with "Failed to paste lidar09.DBO.LD2011SwaleGrnd The application is not licensed to create or modify schema for this type of data"
... View more
10-28-2015
02:39 PM
|
0
|
0
|
1369
|
|
POST
|
Trying now to create new feature datasets to replace the terrain feature datasets on my 9.3 server. However, when I right click in 10.3.1 ArcCatalog or ArcMap Catalog Window > New > Feature Dataset, after naming the new feature dataset, the next window wants me to define the xy coordinate system. In my experience, and in the 10.3.1 and 10.2.2 help files, there is supposed to be an Import button on this window that allows me to get the coordinate system from an existing feature class. (as in the link above to another thread) I don't understand why it seems to be missing in both 10.3.1 enterprise geodatabases and with 10.2.2 file geodatabases. (see above image) Is there an option in Desktop that I need to set? I've tried to set the xy and z coordinate systems of a new feature dataset carefully to match the feature classes that are going into it, but I still get a "the spatial references do not match" message when I try to move a feature class into the new feature dataset. The Create Feature Dataset (Data Management) tool looks like it still has the option of getting spatial reference " By referencing a feature class or feature dataset whose spatial reference you want to apply, such as C:/workspace/myproject.gdb/landuse/grassland. " so I could try this in a python window. If this gets any more tricky, I'll have to go bug my DBA to backtrack and see if he can figure out where he changed the database name in the two step restore process
... View more
10-28-2015
01:43 PM
|
0
|
0
|
1369
|
|
POST
|
Although I was able to move a batch of Lidar data from my 9.3 SDE host over my network with the SDE file connection, feature datasets aren't coming across with right click imports or exports as intact feature datasets, just the feature classes within the feature datasets. So terrains will have to be recreated. I've been trying to move the feature classes into new feature datasets on the 10.3.1 side, but having trouble getting the spatial references to match. This is strange. When I try to create a new feature dataset in the 10.3.1 enterprise goedatabase, there is no import button for the coordinate system to bring it in from one of the feature classes like I am used to, and like appears in the 10.3.1 help files, and this thread https://community.esri.com/message/77856#77856
... View more
10-28-2015
10:47 AM
|
0
|
7
|
1369
|
|
POST
|
It looks like the name on the old server is lidar09, while the name in the restored file list is lidar. The other thing that is different about this geodatabase is that in the 9.3 version, it was one of the two that I somehow made the transactional version dbo.Default rather than the standard sde.Default. I'm going to try to import the database features classes one by one from an SDE file connection. This seems to be moving, except I didn't find a way to create a new feature dataset on the new geodatabase.
... View more
10-26-2015
03:32 PM
|
0
|
9
|
1369
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 11-28-2018 04:57 PM | |
| 3 | 09-20-2017 02:37 PM | |
| 1 | 09-20-2017 02:21 PM | |
| 1 | 03-09-2018 03:25 PM | |
| 1 | 03-12-2015 02:06 PM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:23 AM
|