Latest Contributions by MartinAmeskamp

Hi, we've been trying to identify some line features with duplicate vertices recently (this is ArcGIS 10.2.1 with ST_GEOMETRY on Oracle 11.2), and one obvious way seemed to be to output the geometry as OGC WKT using the ST_GEOMETRY function ST_ASTEXT. I noticed, however, that line features are always output as LINESTRING, i.e. with straight line segments, even though the real geometry (as seen in the edit vertices window in ArcMap) has circular segments as well. Also, my duplicate vertices don't show up in the WKT LINESTRING either Is there a way of exporting the "real" geometry as text, especially the location of all vertices? Thanks, Martin PS We're using Data Reviewer 10.3 right now, but installing that at a customer site otherwise running 10.2.1 is a bit of a hassle... ... View more

Hi, we have a geometric network where a large number (too many for interactive editing) of complex edges have duplicate vertices (these are really duplicate, i.e. two subsequent vertices have excatly the same coordinates). How can we get rid of these duplicate vertices, preferrably without touching the geometric network? Versions and platforms: This is ArcGIS 10.2.1 on Oracle 11.2.0.4, using ST_GEOMETRY. Thanks very much, Martin PS It looks like the duplicate vertices where generated by data migration; they seem occur mainly in places where a straight line segment is followed by a circular arc segment. ... View more

Hi, we have a customer with around 50 concurrent editors on ArcGIS 10.0 SP5 (yes, I know), and Oracle 11.2.04. Editing is done using work order versions, and the number of versions is near the number of users. The typical versions lives a couple of hours: gets created off DEFAULT, edited, passed on to a QC person, and then gets reconciled, posted, and deleted by a dedicated service (ArcGIS Server + Java ArcObjects API). A (reasonably) full compress is done every night after shutting down various services, and this typically gets the number of states very close to the number of open versions. We keep seeing the effect, though, that a large number of version have a very long state lineage (hundreds), and the state tree (viewed with GDBT) looks a bit like a palm tree: A long (hundreds) linear chain of states with no versions pointing to them. After looking into the situation, I found that there seem to be a large number of exclusive state locks:In one specific instance, most users have few shared state locks, but some users have 20 to 30 exclusive state locks each. I assume that these exclusive locks have something to do with the long uncopmpressed chains of states, and the question is. Where do they come from? What can I do with ArcMap to generate 20 exclusive state locks?? This seems to be a recurring problem, so I'm interested in finding out how it comes about. As night, when theer are no users, the database behaves as expected and compresses quite nicely... Thanks, Martin ... View more

Hi, we have some problems with the GDB_ITEMS SRID (master and user GDB) when upgrading (Oracle) enterprise geodatabases, e.g. from 10.0 to 10.2.2, so naturally, we're familiar with the spatial reference consistency patch. This doesn't seem to address all problems in this area, however, and in trying to figure out whether the upgraded database is "clean" or not, we came across the following question: When a database that was created at or before 10.0 (i.e. with SRID 0 for GDB_ITEMS) has been treated with the spatial reference consistency patch and the corresponding upgrades, what state should it be in to be safe for use with ArcGIS 10.2.2 or later: All SRIDs in all GDB_ITEMS (SDE and user schema) MUST use SRID 4326  OR The GDB_ITEMS SRID may either be 0 or 4326, and the (patched) software will keep things safe and consistentent either way? Thanks very much, Martin ... View more