Latest Contributions by VinceAngelo

Best practice is to give each user their own login, and use roles to manage access (create roles, grant table access to roles, grant roles to users). I always use SDE-based (vice DBO) geodatabases, with one or more "headless" logins mapped to a user (and schema) with the same name to own tables.  If there's a web mapping application, I'll create a login for that as well.  Creating logins to match the users of user-schema GDBs wouldn't be a bad plan Your old edit environment wasn't as isolated as it seemed, since the tables all lived in the same space.  You can isolate editing frameworks in separate databases, but doing so makes it nearly impossible to have the tables of different databases interact at the SQL level (cross-database queries are a violation of best practice, and not easily possible with ArcGIS). Keep in mind that "SDE" no longer exists.  The current term of art is "enterprise geodatabase".  They can only be created by ArcGIS Desktop or Server. - V ... View more

The biggest differences you will encounter are: Oracle is the only RDBMS where user-schema databases are possible, so you'll need to choose between a different user or a different database for editing. In Oracle, the default geometry is SDE.ST_Geometry, but an Esri type is not possible in SQL-Server, so the default geometry is Microsoft's Geometry type.  It has a very different spatial indexing protocol, so you'll need to learn the new options. SQL-Server allows for very-long names, but conforming to the Oracle 30-character column name limit will save you pain in the transition process, since names are still restricted to 31 characters by ArcGIS. - V ... View more

Unedited shapefiles are corrupted over time by filesystem integrity issues, not anything directly due to ArcGIS (or any other GIS software for that matter). If the disk has failed (subtly, at the block level), there really isn't anything you can do (short of going to an archive from before the corruption).  This same issue will corrupt all local filesystem objects, so using file geodatabase is not a solution to this problem. - V ... View more

Yeah, that bit of lore has been repeated long after the original mistaken assertion was made.  It sounds good, but it isn't true. No biggie. - V ... View more

No, the .shx only provides direct read references into the .shp file.  It's a naming convention adopted from the PRIMOS operating system (for the Prime minicomputers on which Arc/Info was originally developed) which provided a shadow fixed-width file for offsets to direct access of the variable record width files. All the *x files of ArcGIS are indexes into the similarly named variable-width files. The dBase file has a fixed table header and N fixed field headers, that define the start and width of the fixed records.  The only link between .shp and .dbf is record number.  You can usually regenerate the .shx if it is lost, since the .shp has internal offsets as well, but if the .shp or .dbf is lost, the geometry or attributes are gone. - V ... View more

Employee feedback is different than corporate feedback. Asking for an "Esri" response in a place where those with authority to respond on behalf of Esri do not participate does not increase the response rate.  If the issue is a known bug without a resolution, there isn't much response that is possible. GeoNet is not intended to be a replacement for Tech Support. If you contact Tech Support, Esri has a better idea of the number of folks with a problem, and can notify you directly if/when a hot-fix or other resolution is found.  If the bugfix does not resolve all issues, then this is something which should be caught earlier than later, and not participating in the process extends the time to response.  Using GeoNet as a supplement to bug reports is one of the main reasons that GeoNet exists. - V ... View more

If you want to hear from Esri on a topic, you should create a Tech Support incident.  Second choice (but not nearly as effective) is to try to contact your local marketing rep, who has access to techincal resources for ad-hoc queries. While plenty of Esri staff participate in GeoNet, very few are authorized to speak for Esri, so the moment you write "Would love to hear from Esri on this" you discourage any further participation from Esri staff (which probably wasn't your intent). - V ... View more

You don't need to parse WKT before making a shape from it (though it will actually work): COORDREF_XY     -400,-400,1000000 COORDSYS        GCS_WGS_1984 EFLAGS          "na+" DELIMITERS      "\t" SKIP            1 COLUMNS OBJECTID        Int32               -    10 N # $WKT          String              - 32767 N # Shape         AsShape($WKT,WKT)   -    32 Y SHAPE           WKTShape            -  1000 Y END Assmptions: 1) You are using a 10.x ArcGIS install (or at least something after 9.1, so that HIGH precision coordinate references are in use) 2) You have a tab between the objectid and well-known text (the default delimiters set includes a comma, which messes up WKT).  There are other ways to parse the line if the objectid is space delimited from WKT. 3) The geometry doesn't exceed 1000 kilobytes (1024000 bytes) -- the maximum is 32767k (all BLOB, CLOB, XML, and Shape columns are in kilobyte units) ... View more

Never ever drop database tables registered with ArcGIS with ordinary database tools.  This corrupts the geodatabase registry.  The safest way to set things right is to re-DROP the table within Catalog, then recreate/re-register the table. Please clarify what you mean by "we use C API".  This seems like a second/different issue. - V ... View more

The fact that they were in different servers wasn't explicitly set forth until just now.  Conversion is going on, just not in a way over which you have control.  It might be instructive to generate a hexadecimal dump of the UTF-8 representation from each table, to see if any escape codes have hidden in the strings. - V ... View more

The problem statement is still far from clear. Please provide the exact version of the database software. Are you using a string conversion function to make sure the UTF-8 and UTF-16 strings are really compatible? Why not create a view? - V ... View more

Don't forget about the 4000 byte record limit.  You could store all the fields if the mean field width is less than 16.  Other products may enforce the 100 field limit of dBase, in which case the "140-150" field count would still fail (just later in the conversion process). - V ... View more

What is the datatype of the join column? Using ODBC to join spatial and non-spatial data in databases is the long way to implement a view. - V ... View more

While 250+ fields is an ugly database design, the error message is actually based on the 4000 byte record width limitation of dBase, which can be reached in as few as sixteen 254-character string fields.  The dBase III specification also has a 100 field limit, which ArcGIS ignores, but it does honor the hard limit of 255 fields (field count is a single byte in the dBase header). File geodatabase does not have the 4K buffer limitation, and supports 64K columns (which is far greater than the database limitations of 256 or 512, depending on ArcGIS version). So your options are to slice the the table width to something that dBase can support or to use a format other than shapefile. - V ... View more

You really don't want my solution to this question (because I don't have one).  Instead, you want to edit the question to contain all the information which would be needed by an API for JavaScript expert (and/or a Python GP Service guru), with a complete description of the platforms, versions of software involved, data, and an exact description of what "intersect polygon details with angles" means (with a sketch or other graphic to explain). - V ... View more