Talk:LIMTYP

raphael 22:15, 7 August 2009 (UTC) :

A new attribute Limitation Type is proposed. This attribute is intended to expand the expressiveness of CHALIM by allowing a more precise machine-readable specification of what is meant when a CHALIM is associated with some other object, for example 'negative limitations'. For example, to encode a limitation that applies only to vessels of draught greater than 12m, use LIMTYP=10 (included), MAXDRF=12; to encode a limitation that does not apply to vessels of draft greater than 12m, use LIMTYP=11 (excepted), MAXDRF=12. To encode a limitation that applies only at night, use LIMTYP=14 (new code meaning "applicable at night").

Concerning the enumeration: The first 4 (prohibited, required, permitted, recommended) are intended for use when CHALIM is attached to a facility to capture the fact that it is intended for use by vessels meeting certain limitations. The other two (included, excepted) are intended for use with regulations, etc.

jens 16:49, 14 September 2009 (UTC)

Make sence so far. Do we need to think about a better name widen up the meaning of those adjectives?

raphael 20:30, 14 September 2009 (UTC): Suggestions welcome, also descriptions of problems that arise using the current definitions.

jens 13:04, 24 October 2009 (UTC)

See, for example prohibited: to model anchorage prohibited for all vessels one can model now

• RESARE/RESTRN(1) or
• ACHARE/RESTRN(1) or
• ACHARE/CHALIM/LIMTYP(1).

The second construction is against the ProdSpec (A.51 9.2.3) of S57.

However, it shows that ""prohibited" in combination with something" is more or less occupied by RESTRN.

"Recommended" is being used by STATUS. STATUS is being used in many many other features.

Perhaps we can use "condition" or "stipulation" as attribute name. It would allow a wide use of that attribute as well. That looks fine to my German English, native speakers might see that different. Come on guys, it is your language.