Hot answers tagged editing
It's not strictly read-only access. You can load data via copy/paste and import into a SQLite or SpatiaLite database. Tables and feature classes can be appended to using append or Load Data. You can edit the SQLite/SpatiaLite data via code as Insert/Update/Delete are supported. What you can't do is open an edit session in ArcMap.
Updating the map view whenever an attribute value is changed in the attribute table could impact the performance in a very negative way. A workaround - if you want to see changes immediately - could be to edit not in the attribute table but in the feature attribute form which opens when you click on a feature with the Identify tool ("auto open form" needs ...
It is indeed not possible to edit data from a joined table. The easiest workaround is right clicking the layer name -> Data -> Export Data... and save it as a new shapefile. This new shapefile will then include all data from your joined table, and can be edited freely.
If you are using File Geodatabase, the only option to track feature editions is Editor Tracking (@John Comment). It added 4 fields to each table namely: Creator,CreatedDate, Editor, EditedAt If you are using Enterprise geodatabase then you can take advantage of versioning. You can create a version for each user and manage their editions, deletions, ...
I think what you want - assuming you're using ArcMap - is the 'classic snapping' tool, which would give you the ability to set which layers you're snapping to, so you can turn off snapping to the grid you're running into.
As you cited, the lasheight tool from LASTools can do the trick (used from ArcGIS). The READ ME text from lasheight says: .... Another alternative is to use the computed height to eliminate points with a particular ground height above or below a threshold with the options ... or '-drop_above 6.8'. .... Example: lasheight -i *.las -odix ...
Only top voted, non community-wiki answers of a minimum length are eligible