Ok.. i think you want to have such a constraint implemented in OpenJUMP.
The point is, that the designers thought to make Jump like a easy to us
drawing program.
- It is possible to store mixed geometries with jml/gml files
- Larry has added to SkyJump a tool that disaggregates all-in-one layers
to single point/poly/lines layers when storing as shape file.
actually there is no real argument to prefer mixed geometry layers over
separeted layers.. but also for the other way around. A mix may
facilitate to group logical (i.e. we dont care if the water body is a
lake or a river) while a separation facilitates easier geometric
analysis (a lake has an area while a river only a length).
mhm.. but to come back to your question. What happens if you decide for
yourself to store only lines in one layer and write this layer to PostGIS?
btw. Uwe will be in holiday until the end of the month.
stefan
Giuseppe Falcone schrieb:
Hi.
First of all, thanks for the response.
In Open JUMP I can create a new layer and the I can put on him features of any
type (line, polygon,...). But if I want to save this layer on a postGIS table
I obtain an error. On a postGIS table exists some constraint on the field
that contains the geometry (type of geometry and its dimension) and I can
write geometries of a single kind.
But hte problem doesn't is only postgis: if I want to save the new layer on a
ESRI shapefile I obtain also an error because also in the shape I can write
geometries of a single kind!
I find strange that I can put on a layer features of any type (on Intergraph
Geomedia, on ESRI ArcView, on QGIS when I create a new layer I specifiy also
the kind of features that contains).
I have partially read the german postgis manual with the help of a friend that
knows german, but there's no help about my question.
Any ideas about this?
Thanks for the help.
Giuseppe
Hei,
a couple of comments and questions below:
I have noticed some strange things about OpenJUMP:
1: When I create a new layer, i couldn't specify the
geometry type of the
feature (MULTILINESTRING, POINT, ...)
do you mean you want to specify the geom type for a new layer in
OpenJUMP or when writing to the database?
2: When I save this data on a new PostGIS table, the
table created doesn't
have any constraint about geometry types and this
table doesn't have the gid
field and doesn't appeare in geometry_columns table
mhm .. one can only save with the plugin by Uwe. He is currently in
holidays. Do you think you can re-send this problem in 3 weeks.
3: If I add a new feature on a layer loaded from an
existing PostGIS table and
then I try to save this layer overwriting the table,
I obtain an error
because the gid value of the new feature isn't
defined (the gid data type is
serial NOT NULL)
see comment above. i am not sure how Uwe uses the PostGIS writing. I
think he deletes the old table before. But 2 further comments on that:
- we/I did not yet found the time to translate his german PostGIs manual
to english.. or put it on the wiki
- If you know somebodoy, who needs the write/update feature and can add
or finance this functionality to the plugin - then we would be very
happy. Companies are around that provide commercial suppport.
sorry for this probably not satifying answers, but we are glad that you
pointed out the problem.
stefan
Someone could help me?
Thanks a lot.
Bye.
Giuseppe
_______________________________________________
jump-users mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jump-users
___________________________________
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail:
http://it.docs.yahoo.com/nowyoucan.html
_______________________________________________
jump-users mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jump-users
_______________________________________________
jump-users mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jump-users
_______________________________________________
jump-users mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jump-users
