Timeline for AutoCAD Map3D New feature from geometry fails on PostGIS
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 30 at 3:47 | history | edited | PolyGeo♦ | CC BY-SA 4.0 |
added 3 characters in body
|
S Mar 19 at 11:04 | history | bounty ended | CommunityBot | ||
S Mar 19 at 11:04 | history | notice removed | CommunityBot | ||
S Mar 11 at 10:01 | history | bounty started | crafter6029 | ||
S Mar 11 at 10:01 | history | notice added | crafter6029 | Draw attention | |
Mar 6 at 13:53 | comment | added | crafter6029 | @Mapperz The postgres table in question has a defined MultiPolygon geometry type. The problem, however, is not postgres not accepting the feature; but Map3D not producing a feature which postgres could accept. | |
Mar 6 at 13:44 | comment | added | Mapperz♦ | If postgres has no geometry defined it should accept all types gis.stackexchange.com/questions/89200/… (we tend to use FME to do this ETL load from dwg to postgres/postgis) | |
Mar 6 at 12:41 | history | edited | crafter6029 | CC BY-SA 4.0 |
Added results from further testing of the issue in question.
|
Mar 6 at 11:49 | comment | added | crafter6029 | No, the "New feaure from geometry" command doesn't simply try to save whatever I select to the database, it creates a new entity based on the vector layer (=DB table) selected; and even asks whether to delete the original drawing entity. So it should make the proper conversion internally and automatically, and apparently it does, the new, yet-uncommitted feature appears on the map with the proper vector layer style. But I'll do some more testing and update the Q as neccessary. | |
Mar 6 at 10:49 | comment | added | J.R | Just to be sure this is related to a AutoCAD Map3D bug and not an actual case of trying to save the wrong geometry type (like trying to save a polyline in a polygon feature class) ? | |
Mar 6 at 9:24 | history | asked | crafter6029 | CC BY-SA 4.0 |