Tag Info

New answers tagged

1

Instead of: for fields in arcpy.Listfields(Feature): print fields try: for field in arcpy.Listfields(Feature): print field.name My changing of fields to field is not important but I think it makes the code read better. However, what is important is that ListFields returns a list of field objects and so you need to examine the name property of each ...


1

Thanks to the comment from Hornbydd, I tried using the Geoprocessor to remove the join and the lock file did disappear (see RemoveJoins3). I would still like to understand why the lock file isn't being released using the other methods (and get some input from Kirk Kuykendall on why his method I linked to doesn't work for me). I would also like a solution ...


0

From your question I infer that you have added the dbf file to map as a standalone table. When you access the dbf file for joining it to a feautrelayer, arcobject automatically creates a shared lock for the dbf file. When you remove the join, and you remove the dbf layer in TOC (StandaloneTable), the shared lock must be automatically removed. I suggest to ...


2

I think your code doesn't work because MakeFeatureLayer_management() creates a layer (in memory) , not a layer file (.lyr). Just replace your TablesView variable, e.g. TablesView = "TablesView" and you shouldn't get that error anymore.


0

Could you use the "Create Feature Class from XY table" instead? This can be done with a right click on the table in the Catalog window in ArcMap or Catalog.


2

If i got you,you have common field among tables so better to use Join command and export the result to get a combined feature(composite). This will not add geometry to the composite but only features' attributes only. N.B.If you are working with lot of data then take different approach, i mean you need to use RDBMS where you will link both table using ...


0

Using Near obtain the FID/OBJECTID of the closest road segment. Use an attribute join between the points and road segments; at this stage check the matching road names vs the names on the points to ensure you're getting the right one... some manual work may be required. After you've validated the ids then join lines to points (1:1) and then either field ...


2

Sorry. Wildcards are for use in strings, and unfortunately the double quotes around a column name don't mean that it's a string. Column names are "identifiers", which I think are basically object names, but I'm no expert. That doesn't mean that there is no way to do what you're asking, but it won't be happening in field calculator.


1

I had the same problem and figured out a solution with the 'processing modeler' from QGIS 2.6. Weird enough: in the resulting shapefile, the original columnnames from the .dbf are kept! How to use the processing modeler? With the processing modeler you can automate whatever geoprocessing, analysis, datamanagement, etc you do within the usual QGIS ...


2

When to use join: When there is a one to one relationship between two distinct tables or geometrics (based on join field or spatial relation) Used to append new field/columns to table (result = table has same number of rows, and more columns) http://resources.arcgis.com/en/help/main/10.2/index.html#//005s0000002q000000 When to use merge: To combine ...


0

The tool Copy Features honours the qualified field names environment setting. So Use that tool to make a copy of the dataset with the join and work with that.


0

when you join a table, the names of the fields to be used in ArcGIS becomes a concatenation of the name of the table and the name of the field. So you should try with fields = ["Potash_Rates.Potash","pt_tst.LB_P_SQM"] also there is a small typo in your raster name, but probably not in your original one cursor = arcpy.UpdateCursor("pt_tst_lyr") should be ...


1

I just realized that one of my column headers was solely a number -- which I thought I'd fixed. Sorry about that! If you're ever having this problem, please make sure none of your column headers are numbers; it makes QGIS assume it's a value instead of a header.


1

Use the Add Delimited Text Layer add option. It has much better handling of CSV then what OGR has via the Add Vector Layer add option.


2

As @MichaelMiles-Stimson already mentioned, there doesn't seem to be a way to symbolise NULL features. However, there is an alternative whereby you create a filter to force QGIS to treat NULL values as an integer such as 0. I've included an example where I created 3 simple polygons each with a certain value: Here is the Graduated Symbology I used with ...



Top 50 recent answers are included