Question : Is it possible to create a table in QGIS that will be a dynamic reference for geographical data entries?
As I'm sure this will sound very general and unclear, here's the actual situation I would like to address :
- let's say I have a vector (points) map of trees on a site.
- Each tree is identified by a unique number, and is further identified by a code which indicates its species (to the cultivar level).
- Each species has their own characteristics, such as environmental preferences (soil, sun, climate, etc.), pests, uses (fruits, timber, wildlife habitat, etc.) behavior (size, root system, blooming time, etc.), and much more
-> My goal : create a table which lists all these characteristics by species, so that when I add a tree on my vector layer, I only enter the unique number (or let QGIS do it for me), and the species code, and it dynamically retrieves all the info from the species list, and includes it in the vector layer's attributes for that tree. Of course, I'd use the same field names and type in both tables. And in reverse, let's say I modify some characteristics for a species, and it automatically updates all the unique trees in my vector layer.
I've experimented with many things in QGIS, and one thing that bugs me is that nothing seems to "stay" or be dynamic. For instance, to make QGIS calculate a polygone surface for an 'Area' field, I need to redo the formula every time I add new entities. Can't it be dynamic?
I'm laying out the needs and solutions to map a future farm on QGIS. Not just trees but shrubs, perennials, annual crops, animals, and much more...
I have a moderate (fortunately fruitful) experience with mapping with QGIS, but it has been 100% self-taught and I'm limited by the database aspect of it, now that I want to push it further. The last time I really dealt with databases was on Access at university, about 10 years ago, and it wasn't super deep.
I just downloaded DB Browser for SQLite (I'm on OS X), which gives me the pleasant ability to do simple edits that QGIS won't let me, such as changing the order of fields. It also seems to give me the ability to quickly mess up my data, which is why I decided to join Stackexchange and go beyond self-learning. I'm having a tough time analyzing what is feasible in QGIS itself or requires external handling of the DB.