Hot answers tagged migration
GeoChalkboard can give you a good overview of the changes! Here's the list, but check it out for more detail: Replace the import statement Replace all gp. with arcpy. Check your capitalization. The result tool is different. Replace any del gp statements. The overwrite tool is different. Import the env module from arcpy. List item
According to Paul Ramsey: First, for patch version increases (e.g. X.Y.Z -> X.Y.(Z+1)) in PostgreSQL and PostGIS you do not need to do anything at all other than install the new software. The data can remain in place and everything will Just Work. For minor version increases in PostgreSQL (e.g. X.Y.Z -> X.(Y+1).Z) you need to dump and ...
Take a look at the following: Esri Migration doc Specifically Reference ESRI.ArcGIS.ADF.Local assembly Set ESRI assemblies Specific Version property Platform CPU target changes
It appears you have a setup project that is part of your solution. You might try having it run EsriRegasm, as described in Chris Garrard's blog post. When you build your project you'll also need to call EsriRegasm, as described here. <Target Name="BeforeClean"> <Exec WorkingDirectory="$(CommonProgramFiles)\ArcGIS\bin" ...
In addition to @jmhauck answer; because the application framework has changed in version 10 you might also consider just to build a new extension using the ArcGIS 10 SDK using one of the "Extending ArcObjects" templates and copy your functions and procedures from your legacy extension. More info on extending ArcObjects here
Styles: Your personal style is the default location where new symbols and style elements are saved. It is empty to begin with but can be used to organize your style contents. It will always be referenced by ArcMap. On Windows XP, it is located at install drive:\Documents and Settings\\Application Data\ESRI\Desktop10.1\ArcMap. On Windows Vista and ...
So here is how I successfully solved the issue -- although I did go through every one of the settings for the x86 again -- I removed EVERY reference to the ArcObject interfaces and re-added them to the project. I also, removed and re-added my Unit Test project. In doing this, I was able to catch one of the x86 references that I could have missed the ...
When I formated my PC and reinstall Windows and QGIS I had the same message Exception: bad allocation, After some time I realised the reason for this is that the project I was trying to open contained a google physical map and I hadn't install the open layers plugin. So maybe if this happens is because a missing plugin. Diego.
Create a new simple project, load a shape from the server, save it, and compare the .qgs-Files with the old ones with a good text editor, e.g. notepad++. If you found the difference in < datasource >, you can edit the qgs-files with notepad++. It can open several files at once, and do search&replace on all opened files.
Check usual tables and "tables with geometry", then use (at shell/UNIX terminal) pg_dump for export the usual tables (import with psql) pgsql2shp to export the geo tables, and shp2pgsql to import. The last one (pgsql2shp) is for the "bug" of pg_dump when exporting "old to new PostGIS data" versions. Of course, if no bugs, you need only pg_dump. Check ...
I've converted this to AMD below. Specific things to point out: use require() to load modules instead of dojo.require() no longer use any esri.whatever globals no longer use any dojo.whatever globals dojo/domReady (or dojo/ready) replaces dojo.addOnLoad or dojo.ready use object.on to listen to events, this replaces dojo.connect (example is map.on(), this ...
Depending on your time-frame, you might look at this as an excellent opportunity for you to dive into Python scripting, as it would be very appropriate for this task. First, you could use ArcPy to make a GIS inventory. You could load the results of your inventory into your favorite database, where you could set up columns for old pathnames vs new ...
See this link: Updating and fixing data sources with arcpy.mapping You will need to determine the old/new paths of your data and create a program using these examples. In the future establish procedures and policies for your users so that this does not happen again. Keep your data organized.
We run two Geoserver instances sharing one database. One instance for Development, Testing, then one instance for Production. Each Geoserver Instance is on a seperate machine, as is the database. We backup our database regularly, and load the data into the tables. Once loaded, the tables almost never have to be touched, hence why we share the database ...
Looking through your your steps it looks like you mostly have it covered. To ensure the lease amount of problems try to install on the same drive and directory on the production server as you have on your test server. There is also a number of settings that you will want to make sure are compatible with you new server ect After you have copied over you ...
This is a link to the same question with it's corresponding answer on stackoverflow: Postgis reorder mixed up linestring chunks / max_segment_length(linestring) So if someone gets here, there is the answer.
Only top voted, non community-wiki answers of a minimum length are eligible