Moritz Lennert wrote:
I don't have a copy of grass64 on my machine at the moment.
Could someone merge this into 64 for me ?
fyi in SVN you can not checkout a single file from the repo to
update (like you can in CVS), but you can check out a single
directory non-recursively then edit the file.
I have updated the vectorintro (vector/vectorintro.html) in grass64,
grass65 and grass7. Attribute management has been changed to Vector
object categories and attribute management.
Please check for and report any errors/inconsistencies or if the changed
description is incomprehensible.
On 10/03/09 12:57, Markus Metz wrote:
I have updated the vectorintro (vector/vectorintro.html) in grass64,
grass65 and grass7. Attribute management has been changed to Vector
object categories and attribute management.
Please check for and report any errors/inconsistencies or if the changed
Moritz Lennert wrote:
On 10/03/09 12:57, Markus Metz wrote:
I have updated the vectorintro (vector/vectorintro.html) in grass64,
grass65 and grass7. Attribute management has been changed to
Vector object categories and attribute management.
Please check for and report any
Normalization of data and GIS is a difficult topic. I tend to seperate
geometry and data into different tables and join them together by need. This
makes it easier to modify the geometry without touching the data or even use
different representation forms, e.g. point sizes vs. choroplethe maps.
On 09/03/09 00:00, Benjamin Ducke wrote:
Dear all,
I keep getting into situations where mapping 1:n and m:n relationships
in relational DBMS to GIS vector models becomes a problem.
The toughest restrictions of course are the 1:1 relation between map
features and attribute table records
Where
Dear all,
I keep getting into situations where mapping 1:n and m:n relationships
in relational DBMS to GIS vector models becomes a problem.
The toughest restrictions of course are the 1:1 relation between map
features and attribute table records and the fact that GIS relates
data by spatial
