It is the S-52 specification that details the S-57 colours & symbolization -
specifically S-52 Appendix 2. The specification states what colours should
be used for different ambient lighting and also makes suggestions regarding
what you should wear:
"The face of the CRT acts as a mirror to white shirts, sometimes seriously
obscuring the chart display. Wearing a "watch coat" of black Egyptian cotton
will greatly improve viewing on a sunlit bridge. "
This looks like a good site to get started:
http://www.iho.shom.fr/ECDIS/s52intro.htm
Mark
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mark Stoakes
Safe Software Inc. Professional Services
[EMAIL PROTECTED] +1 (604) 501-9985 ext. 211
=========================================================
-----Original Message-----
From: Mark Ireland [mailto:[EMAIL PROTECTED]
Sent: March 14, 2005 11:44 AM
To: [email protected]
Subject: RE: [fme] s57 feature colors
Hi,
Attached below is an extract from a set of FAQs I am writing. They concern
converting S57 to MapInfo.
Basically you need to set the Format Attributes that relate to your
destination format symbology, for example mif_symbol_size or
mapinfo_pen_color
The FME Readers and Writers Manual (in the online help or available at
www.safe.com/download) will give you the full list of Format Attributes for
any format.
You can set these by exposing them in your destination Feature Type and
setting with a constant, or by creating them with an AttributeCreator
transformer.
Hope this is useful,
Regards,
Mark
Mark Ireland, Product Support Engineer
Safe Software Inc. Surrey, BC, CANADA
[EMAIL PROTECTED] http://www.safe.com
Solutions for Spatial Data Translation, Distribution and Access
------------------------------------------------------------------------
-----
When I convert my S57 data none of the correct symbols or colors come
through. Why?
According to the official S57 specification document...
"The model... does not contain any rules for the presentation or display of
information... Therefore the presentation of information is considered to be
independent of its storage. Different applications must provide their own
specific presentation model"
In other words if you open the S57 data in an S57 viewing application then
you will see symbols and colours not because the S57 data holds this
information, but because the viewing application is automatically
symbolising the data according to its own set of rules (its "presentation
model").
If you convert the data from S57 to, say, MapInfo using FME all of the
available information is carried across. You will not see the same display
in MapInfo as in the S57 viewing application because MapInfo is not
automatically symbolising the data (NB neither will the FME Universal
Viewer).
Your options are to either use FME to set MapInfo format attributes to
simulate the S57 viewer display, or by applying these properties within the
MapInfo environment.
------------------------------------------------------------------------
-----
When I convert my S57 data to MIF/MID the soundings do not have an attribute
for depth. Why?
As with symbology (see above) the only reason you are seeing numbers
representing a sounding in your S57 data is that your S57 viewing
application is automatically converting the Z value of the each sounding
feature into an item of text annotation.
If you convert the data from S57 to another format, FME does not create an
attribute to hold sounding depth because there is no such attribute in S57.
Each sounding feature will be in 3D with the Z coordinate representing
depth.
Because MapInfo Interchange Format (MIF) does not support 3 dimensions the Z
coordinate is being lost. Therefore you are getting neither an attribute or
a 3d feature.
The extremely simple solution to this is to add a CoordinateFetcher
transformer in your workspace, just after the soundings Feature Type. A
CoordinateFetcher will retrieve the Z value of every sounding feature and
place that value into an attribute of your own creation.
------------------------------------------------------------------------
-----
When I convert S57 to MapInfo I get the message "MapInfo file 'myfile.tab'
could not be opened" or "unable to create new table" when I convert or open
the TAB file in MapInfo. Why?
The issue is that the S57 schema has character fields that are 254
characters in size and therefore too long for MapInfo to handle correctly.
Because this is a limitation of MapInfo it is something that cannot be
easily resolved by FME.
The solution is to modify the output schema in Workbench to make destination
fields have fewer characters. To preserve attributes that are 254 characters
long you'll need to split them into sections and write each section to a
separate MapInfo attribute.
------------------------------------------------------------------------
-----
> -----Original Message-----
> From: Shamim [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 10, 2005 8:25 PM
> To: [email protected]
> Subject: [fme] s57 feature colors
>
>
>
> Hi
>
> I would like to know how to extract the s57 chart feature colors into
> other format , for example mapinfo ?.
>
> Thanks.
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/
>
>
>
>
>
> Get the maximum benefit from your FME, FME Objects, or SpatialDirect
> via our Professional Services team. Visit www.safe.com/services for
> details.
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our
Professional Services team. Visit www.safe.com/services for details.
Yahoo! Groups Links
Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our
Professional Services team. Visit www.safe.com/services for details.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/fme/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
