Re:Why Are Geospatial Databases So Hard to Build?
by sopooneo on Sunday March 15, 2015 @08:44PM
(#9208955)
Here's one I think is probably 101 level for others here, but what is the difference between a multidimensional scalar and a vector? I'll gratefully read through any reference you can link to.
[ Parent
| on HN ]
Re:Why Are Geospatial Databases So Hard to Build?
by nkurz on Sunday March 15, 2015 @09:14PM
(#9209104)
Whether something is 101-level or a difficult thesis topic often depends on your point of view. Different fields seem to define scalars differently, with the physicists sometimes arguing that the mathematicians have got it all wrong: http://imechanica.org/node/15857
On a related note, I was tremendously impressed with the quality of discussion at imechanica.org. At a glance, it may be the best example of a well-functioning online community that I've ever seen.
Re:Why Are Geospatial Databases So Hard to Build?
by Potando on Monday March 16, 2015 @12:42AM
(#9209909)
Great part:
"They should not call the elements in the number field F scalars. These elements already have names: they are called numbers. And we physicists and engineers need the word scalar to name some other objects. Mathematicians, like physicians, should at least learn to do no harm. "
Re:Why Are Geospatial Databases So Hard to Build?
by GFK_of_xmaspast on Sunday March 15, 2015 @10:17PM
(#9209374)
It looks like he's fumbling towards replacing the field with a (graded?) ring and therefore replacing vector spaces with modules.
Re:Why Are Geospatial Databases So Hard to Build?
by fizx on Sunday March 15, 2015 @09:49PM
(#9209254)
A vector belongs to a vector space, which implies certain algebraic rules relating it to other vectors in the space (http://en.wikipedia.org/wiki/Vector_space is probably enough reference). A multidimensional scalar is a more general data type, as any or all of the vector axioms can be relaxed or eliminated.