Re: TNTmips GIS gets SVG

I expect you'll get a few responses to your question with more depth than 
my response, but in case no one else says anything...

SVG has a <metadata> element that can be a child of nearly any element in 
an SVG document. Document level metadata can be put in the <metadata> 
element that is a child of the outermost <svg> element. Metadata associated 
with particular fragment of the document can certainly be put in the 
<metadata> element that is a child of top-level element for that fragment, 
or could also be put other places, such as the <metadata> element that is 
the child of the outermost <svg> element. Whatever is convenient and makes 
sense for your application.

SVG 1.1 defines some specific guidelines for geographic projection 
metadata. I have lost track of the details. I'm hoping someone else will 
help you with specifics.

Beyond putting things in <metadata> elements, remember that the underlying 
technology is eXtensible Markup Language, and that one part of the 
underlying technology is XML namespaces. It is also possible to define a 
custom XML namespace for your application and scatter elements and 
attributes from your namespace around the SVG document. The SVG 
specification says that viewers should ignore elements and attributes from 
non-SVG namespaces for viewing purposes, but this information is available 
via the DOM.

Jon Ferraiolo
SVG 1.0 Editor
Adobe Systems Incorporated

At 10:58 AM 3/22/2002 -0600, Lance Dyas wrote:
>Well  I had mentioned it as a possible now its becoming a definite, I am
>writing the code that will include direct
>export from TNTmips, MicroImages GIS software to SVG format.  Also on the
>todo list is import SVG.
>What does anyone suggest as a method for encoding the projection information
>and metadata associated with groups and objects?
>Lance Dyas
>programmer, web application developer, web tech, DHTML wizard and graphic
>MicroImages, Inc.

Received on Friday, 22 March 2002 12:40:20 UTC