1

Closed

[MapWindow] Join tables functionality is troublesome

description

Part of the SSURGO soils preparation requires two MS Access tables to be joined to the "soilmu_a_XXXXX.shp" file. I tried doing this with Meem's Tools, but was not successful. Is there a better way to join tables in MapWindow? Or does this functionality need to be built?
Closed Jan 23, 2013 at 1:03 PM by DEslinger
Found work around for 4.8.6 (documentation being posted at csc.noaa.gov/nspect, then on the Support tab), and MapWindow has join capability in 4.8.7, which is now out for beta testing. The new Attribute Table editor allows joining and works very well!

comments

allen_anselmo wrote Dec 29, 2010 at 3:29 AM

Could you explain further where this fits in the process? is it something you do manually before feeding the data to the new soils form or is it something in the automatic process which is failing? What did you use of Meem's Tool that failed and how did it fail? I've honestly never tried doing a join in MW, so if it's a purely manual thing, it may require coding, but I'd have to look into it further. For now though, let me know more about what this needs to do.

carterhj wrote Dec 30, 2010 at 6:12 PM

This step is required to prepare the SSURGO soils for ingestion in the new soils form. The SSURGO data come as a set of shapefiles and tables. Two tables have to be joined to one of the shapefiles in order for the correct fields to be available for processing into rasters via the code you have implemented. I tried using Meem's "Manage External Data Sources" tool to link the tables to the shapefile. I don't know if this was the appropriate use of that tool, but it was the closest thing I could find. I think a simple tool to join tables based on similar attributes in specified fields would be a very valuable tool, and I'd be surprised if it doesn't already exist.

wrote Feb 3, 2011 at 4:52 PM

carterhj wrote Feb 16, 2011 at 1:19 AM

I attempted to join these required tables in MS Access so that the polygon shapefile had the correct fields associated with the features. I was able to join the tables and generate an updated .dbf file to replace the original .dbf file. However, I ran into a problem where there were more records in the new .dbf file than there were in the original file due to the one-to-many join operation. I don't know how to effectively and accurately remove the extra records without harming the quality of the data. Furthermore, the process was long, convoluted, and extremely inefficient. I hardly expect anyone else to follow these steps if we're trying to keep the user skill level at the intermediate level.

mudnug wrote May 9, 2011 at 6:31 PM

This is a missing feature in MapWindow

wrote Jun 2, 2011 at 5:26 PM

wrote Jan 23, 2013 at 1:03 PM

wrote Feb 13, 2013 at 7:11 PM

wrote May 16, 2013 at 3:14 AM