Database Edit

Menu appears when "EDIT" button is pressed on database table form.  You must enable edits by checking the "EDIT" box on the right of the row of buttons, since all changes are permanent (save a copy of the database if you are concerned about editing mistakes).

Choices available will depend on the type of database open.
  • Color_db_recs
  • Date/TIME
  • Icons
  • Font
  • Map coordinates
  • Fill viewshed fields

  • Graphically move points: drag points to a new location.
  • Graphical pick and edit record: pick a record by clicking on it on the map, and then edit the record.
  • Graphically delete
    • Single points:  double click to delete; confirm if you want to keep deleting
    • All points in box: outline box to delete.  Right click and abort current operation when done.
  • Graphically insert point: copies the current record to the bottom of the database, and gives it the location when you double click on the map.  The you can edit the record.  You must change any fields that do not apply to the new location, or that might be duplicated by the record this was copied from and are not allowed to be duplications.
  • Insert record--add a new record at the bottom of the table.
  • Insert record from clipboard
  • Merge point databases 
  • Edit records in grid--type directly in the grid to change values.  For the last change to take, you must click inside another cell.
  • Delete all records--useful after filter, for point databases only.  You can get the same result by reversing the filter, and then saving that as a new DBF file on the Report menu.
  • Thin database: select thinning factor.  A "USE" field will be added to the database, the first record will be marked "Y", and the next (thinning factor minus one) records will be marked "N".  You can then filter based on this field, and save as a new database.  This only makes senses in certain cases, such as points selected along a line, for instance a least cost path or a digitized path, when such selective thinning produces a reasonable subset of the data, or when you have points very densely but randomly located.
  • Mask--based on geometry
  • Flag--based on data characteristics
    • Add Y/N  from substring.  Because you cannot filter with an initial wild card, this enables you to create a new field, and fill it with a "Y" for every records that contains a specified substring. 
    • Add count from substring: adds a new field with the number of times a specfied substring occurs in the field
  • Create grid
    • Point density (match map area)
    • Point density (match grid area)
  • Shift point records
  • Evaluate XY profiles
  • DEM
    • Add interpolated elevation from DEM: put elevation for each lat/long point in the database, placing it in field "ELEVATION"
    • Add nearest elevation from DEM:
    • Add slope/aspect from DEM: put slope in percent for each lat/long point in the database, placing it in field "SLOPE_PC"
    • Add elevation difference from DEM: 
    • Add elevation from DEM series
    • Find records on DEM
    • Pick grid and add nearest value
    • Place values in DEM
    • Compute intervisibility from point: enter a location, and the height of the observer.  The program will compute the aziumuth and pitch to each record in the database, and show them as either visible for masked by intermediate terrain.
  • Satellite, add DN: add the reflectance value for each band in fields BAND_1 to BAND_N.  If one of the bands (e.g. ETM pan) has different spacing, the values for it will not be correct.
  • Stream network topology/Strahler order
    • Open shapefile with the river segments.
    • Filter  shapefile to have a single basin, so the segments must be assigned to basins.
  • Fill in drainage basin
    • Must open grid with the drainage directions, following ArcGIS flow directions conventions. An example of this would be the HydroSHEDS  data.
    • Must open rivers shapefile, which must have the orders for the subbasins fields set.
  • Navigation
  • Add NLCD category
  • Find neighbors in second database: both databases must have point geometry, and you will select a box interval (distance out from point in all direction), and the program will find the number of points in the second database.  For large databases this will be very slow, and you should consider the raster option to get Point Density.

  • Check joined database
  • Fill fields from joined table: select fields from the joined table.  They will be copied to the table into a field with the same name.  If the field already existed, you choose whether or not to overwrite records which already have a value for the field.
  • Add fields from open data base: this will insert the value from the closest record in the other open database.
  • Geocode address to lat/long: compute LAT/LONG from ADDRESS field. 
  • Geocode lat/long to address:  point databases only.

  • Insert new fields
  • String field operations--change the string in the existing field.  To be safe, you might want to create a duplicate field first.
  • Field arithmetic
  • Field geometry
  • Rename fields from reference table
  • Fill field for all records
  • Use field
    • Mark all "Y"
    • Mark all "N"
    • Toggle records--change "Y" to "N", and "N" to "Y"
    • Current filter "Y", rest "N"--everything in the current filter will be "Y", and everything else "N"
  • Change fields used

 

Rename individual fields by clicking on field name for the field.


Last revision 12/17/2017