Author Topic: UML Profile for Simple Features Access for SQL  (Read 433 times)

JPHespanha

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
  • et pluribus unum
    • View Profile
UML Profile for Simple Features Access for SQL
« on: November 08, 2007, 09:58:29 am »
Hello all!

As part of my current PhD research, I am trying to specify a new UML Profile to apply to UML Class diagrams representing spatial features, that is, using geometry types.

I am using PostgreSQL's PostGIS extension as reference for the actual geometry types, but I think it could be applied to any spatial database system which complies to the Simple Features Access for SQL specification.

Currently, also geometry types from SQL/MM ISO/IEC standard are also being supported by such databases, and at least some will be added to the Profile.

I would like to receive any suggestions this forum members might have, but I can not attach the EAP file itself, so I will just insert pictures with the Class (Domain) diagrams from EA.

If somebody has any suggestion on other way to interact, with or without EA software, ideas are also most welcome.

Looking forward to hear from you,
Joao Paulo Hespanha
PhD Student, OTB Research Institute,
TUDelft
The Netherlands
Joao Paulo Hespanha
OTB Research Institute
Technical University Delft

Gary W.

  • EA User
  • **
  • Posts: 139
  • Karma: +0/-0
    • View Profile
Re: UML Profile for Simple Features Access for SQL
« Reply #1 on: November 08, 2007, 02:29:13 pm »
Joao
Quote
If somebody has any suggestion on other way to interact, with or without EA software, ideas are also most welcome.
Creating a UML Profile is a great idea.  *We* cheated by duplicating Simple Features Specification for SQL (Revision 1.1) in our EA Model, and then specialising our modelled observations from these classes.  Technically, you are correct to treat them as meta-classes rather than classes.

However, by creating such a "Simple Geometry" package to hold Point, Curve, Surface, etc., we were able to easily associate Geometry to our implementation-specific SpatialReferenceSystem (i.e. Oracle Spatial's MDSYS.CS_SRS table).

Also, we were able to simply model multi-dimensional data, in the form of the two classes FeaturePointMD and FeatureLineMD.

Our focus was on modeling a specific implementation of Simple Features to meet specific requirements (e.g. specific kinds of spatial data such as roads, jurisdictional bounds, waterways, catchment basins, etc.  

Now... if you ever finish your UML Profile and choose to publish it, we would be VERY interested  ;D

Gary