Since things have been pretty quiet lately, how about opening a discussion on the storage of the calculated/compiled data?
Some items that might be contained in the calculated data file are:
- date "compiled";
- application used to "compile";
- source file name (CaveXML data file).
COMPASS has an interesting manner to store the data. Larry uses Move and Draw commands to note the lines. This
allows for the drawing of Polylines which are quicker - in most cases - than drawing a series of two point lines. (I don't know
if this is also true under Java... yet.) If something similar was taken into CaveXML, it could look something like this:
<Line Color="Blue" Size="1">
<Station ID="000001" X="0.0" Y="0.0" Z="0.0"/>
<Station ID="000002" X="1.5" Y="3.3" Z="-100"/>
...
</Line>
or in a DTD:
<!ELEMENT Line (Station, Station+)>
<!ATTLIST Line
Color CDATA #IMPLIED
Size CDATA #IMPLIED>
<!-- Station can either be included from a DTD fragment or re-defined. A station can have either an ID or IDREF -->
<!ELEMENT Station EMPTY>
<!ATTLIST Station
GUID ID #IMPLIED
GUIDREF IDREF #IMPLIED
Easting CDATA #IMPLIED
Northing CDATA #IMPLIED
Elevation CDATA #IMPLIED>
(Note: DTD fragment has not been validated)
The first Station would be assumed (valid?) to be similar to a move command with all following points/stations draw
commands. The ID would tied the station to the CaveXML data file. More data could be copied - station name, etc - or it
could be left as a look-up to tie the rest back in. (We have a need to know info about the survey when viewing the map but
is it worthwhile to copy all that info into the calcalated data file?)
Another thing to consider is a view. Again, COMPASS does something similar to this. However, it would also be nice to
have the ability to store labels for rooms, passages, and such with the view. At a minimum, the view might contain:
- the souce file name(s) (CaveXML data file);
- the calculated file name(s) (CaveXML calculated data file);
- the view's azimuth, inclination, and dip;
- legend text, text style, attributes (scale displayed, north arrow displayed, etc), and location;
- label text, text style, and location;
- included surveys (allows some survey to be excluded or only specific surveys to be be shown)
On the last item, would it be useful to have surveys in the CaveXML data file identified with an ID as well as the stations?
Instead of just having a name for a survey, it could be:
<Survey ID/GUID="SRV000001" Name="A">
</Survey>
or
<!ELEMENT Survey (Data)>
<!ATTLIST Survey
GUID ID #REQUIRED
Designation CDATA #IMPLIED
xml:lang NMTOKEN #IMPLIED>
?
- Richard Knapp
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Fri Jun 01 2001 - 12:00:00 CEST