New answers tagged features
GRASS GIS is not QGIS and it is not very difficult to find documentation: v.edit: it for editing a GRASS vector map and not a QGIS vector map, so you don't need this command: it does not exist in the Processing Toolbox, nor in the GRASS Tools of the GRASS plugin. v.edit in GRASS GIS: v.distance: it is to find the nearest element in GRASS vector map ...
Here I found my question! I found the way to fix my problem, so this question is answered! (Vector -> ResearchTools -> Random Points)
Having your data stored in a Postgres\postgis database, you can use QGIS DBManager to create a versioning system on your tables. Open DBManager and open you postgis database connection. Then go to Table > Versioning. This dialog will show: Select the schema and table (That must be empty!) and press Ok This tool will create new fields, a view ...
Assuming you are using PostGIS, you may want to look into implementing your own edit tracking system in postgres. A great tutorial can be found at this blog. The general idea is that after each edit/delete a table is updated to store details of any changes made along with user and time (all done using triggers). This system will also allow you to roll back ...
Here are a couple of suggestions: You could maybe store your data in a database and use versioning. PostGIS announced a plugin for this (pgVersion) - though I must admit I've not used it. Alternatively, you could server your data via GeoServer with appropriate accounts and permissions set for your team and use GeoServer's versioning capabilities.
It does sounds like you have changed the CRS half through adding the features. You can re-project those points by selecting them, then right click on the shapefile layer in the table of contents and select 'Save selection as'. You can then choose to re-project those features to 'Selected CRS' and choose the appropriate CRS from the list. Finally you ...
Top 50 recent answers are included