[Geodata] Relevance and usage of OGC compliant geometries for custom-created geometries?

Navin Ipe navin.pro at gmail.com
Wed Mar 20 20:52:09 PDT 2013


I had created a software where I stored 2D geometry attributes in a C++
class and when a user drew geometries, these attributes were saved to a
file.
I'm looking to store these attributes in a PostGis database now, so that it
would be OGC compliant and so that even if I create a web-browser
application, it should be able to take the geometries from this database,
and anybody else who makes an OGC compliant software should be able to
recognize these geometries and use them.

I'm using this pdf<http://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CDYQFjAA&url=http%3A%2F%2Fportal.opengeospatial.org%2Ffiles%2F%3Fartifact_id%3D829&ei=J39KUbiQA4rprQeZk4HgCg&usg=AFQjCNF80iZuzG81OmbhRAUqwqzaoBk_mA&sig2=Vqm1V0AvL6EFXDezMKMrDg&bvm=bv.44158598,d.bmk>as
a reference, and as per page 2-20, it appears like I can represent any
kind of geometry using GEOMETRY_COLUMNS, SPATIAL_REFERENCE_SYSTEMS,
FeatureTables and GEOMETRY_COLUMNS. But a lot of the geometries I have are
custom created - like thick curved arrows with control points to allow a
user to adjust the curvature of the arrow, and a text label at the center
of the arrow, polygons with an X mark at the center of every edge and
control points at certain points of the polygon to allow the user to resize
it etc.

1. For geometries that are meant to be dynamically modified (shape, color,
style and size) by the user, is it right-to/meant-to-be stored it in a
generic OGC compliant database table?
2. How can such custom geometries be made OGC compliant? I've considered
storing the control points as a separate column in the table.
3. Is it better to store the ordinary geometries in an OGC-style table and
create separate tables for the custom geometries (where each table is meant
for a unique geometry and its properties)?

Primary objective is to have OGC compliant geometries and features stored
in a database instead of in C++ classes, so that even other softwares will
be able to recognize these geometries and display them.

-- 
Regards,
Navin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geodata/attachments/20130321/8c7b7fbf/attachment.html>


More information about the Geodata mailing list