Tag Info

Hot answers tagged

7

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


6

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 ...


6

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


5

I don't see any obstacles for you to use QGIS instead of OCAD. Editing works pretty much the same way you do. QGIS has a CAD Tools plugin for those who prefer CAD-like techniques. You will benefit from the ability to load other data and maps in the background to check your data visually, without the need to do a complete re-import.


5

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" ...


5

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


4

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 ...


3

This is fairly simple to do and there's little risk. But be sure to have a backup of your production data directory anyway. Just copy the following directories/files: /workspaces/YOUR_WORKSPACE_NAME/ The workspace directory that you copy over actually contains the store and layer declarations as well as the workspace itself. Ideally in your setup you'll ...


3

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 ...


2

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.


2

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.


2

Have you looked at any other spatial ETL solutions? There are some open source solutions like GeoKettle and Spatial Data Integrator.


2

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 ...


2

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 ...


2

I have with success migrated companies from CAD (and commercial GIS) software to QGIS. The main challenge is having people understand the database behind a GIS instead of (just) a CAD drawing. Usually DXF is no problem opening in QGIS.


2

You may have hit a data corruption issue as detailed in Esri technical article 41119. The error message matches. A file geodatabase may become corrupted that is on a remote Win7 or certain Windows Server boxes. The problem is caused by one of several Microsoft updates and has a patch. Excerpted from the article: The update for KB 2732673 has been ...


1

The following steps works in nearly every case for this procedure. It may be a good idea to repair geometry if you find this process is not producing your desired results. There is the condition of truncated field names should they be greater than a certain length. Generally this is not as severe a problem as the actual transfer, though. Open ArcGIS. ...


1

SDO_GEOMETRY doesn't appear in the source code (github.com/darold/ora2pg) so I'd say you'll need to add support for it yourself, or manually fix up the SDO_GEOMETRY columns using a second pass over your code with awk / sed / whatever. ora2pg is written in Perl and looks fairly sane, so I suggest adding SDO_GEOMETRY support and sending a pull request on ...


1

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 ...


1

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 ...


1

I would actually first try to just move the data directory. Back it up, of course, or run on a test machine first. But if you're migrating forward then GeoServer is designed to just automatically add the new files you need. Going backwards in versions with a newer data directory is much less supported, and that's why the data directory documentation page ...


1

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 ...


1

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.


1

I agree with the other answers and have used the pg_dump method. One additional advantage is that you can compress the dump to a zip or tar for example and move it to another server if you need to.


1

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