Tag Info

New answers tagged

0

You should be able to use this option: http://resources.arcgis.com/en/help/main/10.1/index.html#//001w00000008000000 I am sure you can get there with field mappings if that doesn't work, but it would likely be a lot more lines of code than what youd expect. https://geonet.esri.com/thread/30539


0

Just an idea but if your output was a GeoDatabase Featureclass rather than a Shapefile you could use the Alter Field tool to rename it back as part of the work flow of the model?


1

It's not so much a bug as something which just wasn't implemented yet. The good news is that this has been implemented in QGIS 2.10, so filtering joined layers will be possible when 2.10 is released.


1

I've had issues with ArcMap not recognizing the full data set when the number of records in a single table is very large. I manually "force" ArcMap to recognize the size of the data set I want to join to by opening the table and clicking on the Move to end of table button. See this graphic: As you can see I was working with nearly half a million ...


1

So... this is how I have done it. For large number of entries, it works. I created drop-down menus in excel , then concatenate in excel: concatenate(a1;b1) then concatenate same fields in the shapefile using FIELD CALCULATOR : concat(field1,field2) Then Join both and that.s it. For few registries, I think you can enter data manually on a new column ...


2

The key here is to make two fields into one. Like lot and plan becomes lotplan (eg. Lot 10 on SP1234 -> 10/SP1234) in BOTH tables.. then join as normal. This is easy in Excel by adding a new header cell and use the function =A1 & "\" & B1 (or whatever you cells are) and then use field calc in QGIS. – Michael Miles-Stimson


1

It's currently not possible to do an inner join in one step but you can afterwards filter out those features which were not joined based on the resulting NULL values.


1

It may crash because you are joining directly excel table. These datatypes don't have an OID or Index. You must first work with table in geodatabase using Copy Row or Table to Table geoprocessing. Then it should work


0

MUKEY is your join column. Use a dominant component sql on the Soil Data Access site select m.mukey, hydgrp from legend l inner join mapunit m on l.lkey=m.lkey and areasymbol like 'PA%' inner join component c on m.mukey=c.mukey and c.cokey = (SELECT TOP 1 component.cokey FROM component WHERE component.mukey=m.mukey ORDER BY component.comppct_r DESC) ORDER ...


1

It is probably possible with GDAL but not extremely easy. Everything that can be done with SQL in SpatiaLite can also be done with GDAL http://www.gdal.org/ogr_sql_sqlite.html and this query could be used as starting point: ogrinfo -dialect sqlite test.shp -sql "select attr, st_union(geometry) from test group by attr" However, the query creates one ...


0

If I am understanding your question correctly, I would recommend creating a point feature class using the begin and end point coordinates of each pipe, and then constructing a line from those points. You should then be able to use your line to create a route if you wish. As a side note: The Create Routes tool only prepares an already created line for use ...


1

I see what you are asking for. Unfortunately the MapInfo SQL syntax doesn't support "tableA.*". You can only select all columns from both tables or specific columns. I see three workarounds Select all columns and then modify the table structure afterwards where you can remove the extra columns you don't want If your table structure is somewhat static, you ...


0

There are a number of functions that don't work with joined fields. Hyperlinks (at least with the Hyperlink tool) were and I believe still are one of them. See Esri KB article http://support.esri.com/en/knowledgebase/techarticles/detail/17493 for more detail. You would need to permanently add that field to your table for the Hyperlink tool to work. ...


2

Seeing as though you have no matching attributes to join you will need to perform a spatial join. This is under Vector>Data Management Tools>Join Attributes by Location


2

Create a new ASCII raster from your table. To do this, first save your table as a space-delimited file. Open the file in a text editor and add an ASCII raster header, like this: NCOLS 480 NROWS 450 XLLCORNER 378922 YLLCORNER 4072345 CELLSIZE 30 NODATA_VALUE -32768 43 2 45 7 3 56 2 5 23 65 34 6 32 54 57 34 35 45 65 34 2 6 78 4 2 6 89 3 2 7 45 23 5 ... You ...


0

I have ended up using a solution outside of the Arc software: The first step was to intersect the pipe layer with the bursts to get sections of pipes recording all of the individual burst properties. A unique ID was then added to identify each of these parts. In excel a pivot table was created listing all of the pipe ID's along with the maximum P value. A ...


0

In addition to the One to One Spatial Join that you have done, I would also do a One To Many Spatial Join with the Segments as the Target to create all of the links of segments to your polygons. Then use my tool to convert a Multiple Field Key to a Single Field key with the summary Spatial Join as the Primary table and the One to Many Spatial Join as the ...



Top 50 recent answers are included