Latest Contributions by VinceAngelo

Please provide an example of the invalid polygon coordinates. ... View more

While latitude has hard limits on values ([-90,90]), longitude does not. pi radians is equivalent in every way to 3pi radians and 2pi, 0, and -2pi are equivalent as well. There may be limitations in storage of coordinate values in SQL Server, which, like Esri's ST_Geometry, uses integer internal representation, but values between -360 degrees and +360 degrees ought to be safe. STDistance(), if done correctly for geodesic values, should not find any distance at all between 278.440065912902 and -81.559934087098 with the same latitude. Measuring in Cartesian degrees is of course useless for all purposes. So it seems your problem is not with the longitude values but with distance measurement. You would need to edit or reply to your own post with a more specific description of that issue to get a useful answer. - V ... View more

From my About page: Note: Please do not try to message me directly or tag me in questions; just ask a question in an appropriate community, and if I see it, have something to add, and have the time, I'll respond. Tagging me in questions is more likely to reduce the time I have to answer, and delay whatever response I might have. - V ... View more

Note that you should never store user data in the SDE schema, so the "from sde.fc" part is a problem. Best practice is to create a new login to own spatial data (and a new tablespace to store the data for that login).  Using the SDE login for this is akin to using SYSTEM or DBO for noodling, or web surfing the dark net as administrator -- It's not likely to end well. - V ... View more

There's a whole lot of unclear things here, which is probably why there hasn't been a response. So, please answer the following questions: What version (and service pack level) of ArcMap are you using? What exact version of QGIS are you using? What exact version of PostgreSQL are you using? What exact privileges are bestowing using GRANT wizard ? How is one of the affected tables defined (the complete CREATE TABLE as reported by pgAdmin)? What version of pgAdmin are you using? At what exact version is your geodatabase? What "solutions" have you tried that didn't work? You can either reply below or edit the original question to contain this information. - V ... View more

Four vertices is a triangle, not a square. A square would have five vertices. Edit: I should add that this is pretty much worst practice (aka "antipattern"). Using five vertices to store a pixel could only be made worse by using 9 or 21. On the extremely rare occasions where converting a raster to vector made sense in my own data models, it was only as a point, and only briefly. I'd suggest your colleague review why this is necessary before moving deeper into the process.  - V ... View more

Uh, oh. That's Null Island (wrong coordinate system issue). Have you tried using Check Geometry and/or Repair Geometry on the source layer(s)? - V ... View more

IMHO, copy/paste of each feature class is the road to ruin, because all versions need to be deleted and the entire instance compressed first, or all data in An/Dn tables will be lost. If you move the data in the database using database tools, you move the versioning as well (the backup needs to span the geodatabase tables -- sde.sde/gdb_* and all the schemas which own tables managed in the geodatabase), and you don't need to have a versioning fire sale (Crazy Vince says all data must go!). The single biggest issue here is that you can't change the name of the database after restore (that messes up the registry). If the table schemas have changed in dev, you need a much more detailed migration plan. - V ... View more

Well, I don't know what happened, but Esri uses a third party app for Community, and it's possible something went wonky and a spontaneous rollback happened on the server; I very much doubt someone has maliciously removed content.  I would note that this Community is not Esri Tech Support. If you want help from Esri, you should contact Tech Support according to the terms of your support contract. Community is a user engagement forum, in which some Esri employees also post, as fellow users. Railing against Esri in the forums Esri provides for user interaction is probably not a good way to get help from staff contributors.   I've loaded tens of billions of rows into thousands of PostgreSQL tables in the past decade (a couple hundred million in the past week alone -- dev migration), many of which with plain vanilla ArcPy scripts and Python toolboxes into PostgreSQL databases without enterprise geodatabases enabled. There is a trick to it, though, and without details on the exact database in use, and how you've configured the database, logins, and schemas, and the actual load procedure you used, it's difficult to guess what may have gone wrong. Good luck. - V ... View more

An insanely large objectid (shapefiles can't store 80M features, much less 867+M) wakes me wonder what your exact procedure is. Admin rights is not a particularly good feature for a geodatabase connection. Pro (or ArcMap or ArcCatalog) can create new tables from shapefile or file geodatabase with drag-and-drop, with or without a geodatabase enabled, but the database name and username must be lowercase and the default schema for the login must match (e.g., login 'dataloader', schema 'dataloader'). - V ... View more

Your SQL code would be far more legible if you formatted it in a SQL code block:   SELECT a.OBJECTID, a.PIN, a.Subtype, b.parcel_no, b.siteaddress, b.site_citystzip, b.sw_hauler, b.sw_service_day, b.sw_str_sweep_week, a.GlobalID, a.Shape, b.own1 FROM dbo.parcel_polygon a LEFT OUTER JOIN dbo.ParcelWeb b ON a.pin = b.pin WHERE a.status != 'Retired' and a.status != 'Pending_Retired' and a.status != 'Pending'   From this vantage point, we can see:  You've used "!=" not the ISO standard SQL "not equal" operator "<>" Your WHERE clause is an AND of several NOT EQUAL tests (which can't be effectively searched by as index) So the first question is what are the valid values in a.status?   SELECT DISTINCT a.status FROM dbo.parcel_polygon a    And what are the table counts across the joins?   SELECT (SELECT count(*) FROM dbo.parcel_polygon ) as acount, (SELECT count(*) FROM dbo.ParcelWeb ) as bcount, (SELECT count(*) FROM dbo.parcel_polygon LEFT OUTER JOIN dbo.ParcelWeb b ON b.pin = a.pin) as jcount, (SELECT count(*) FROM dbo.parcel_polygon a WHERE field not in ('Retired','Pending_Retired','Pending')) as qcount   Debugging joins is a stepwise process, stripping out not required components to determine where your logic doesn't align with that of the database. - V ... View more

It's no longer an "SDE" that gets created. The current term of art is "Enterprise Geodatabase", and the command to create one is CreateEnterpriseGeodatabase (or EnableEnterpriseGeodatabase, depending on the context). Both of these commands are available in ArcPy, which is accessible with Enterprise. There is a ".sde" file which can be created, but it is called a "database connection file", and the ArcPy tool for that is CreateDatabaseConnection. Most of the documentation is geared toward using Pro to administer a EGDB, so going without isn't making it easier, but if you can get to the Python instance in your Server install, you can make forward progress. - V ... View more

Placing join tables in the FROM list hasn't been best practice since Oracle 8. I strongly urge you to use JOIN syntax.  And "!=" best written "<>".  The optimizer might prefer placing the point in the first argument, but if Table2 is indexed on t2.field3, and that has higher selectivity, you might want to specify the non-spatial constraints first (though NOT is usually an awful JOIN constraint). - V ... View more

The answer that this quoted was probably a better candidate for "Solution" marking. ... View more

It was right there: (i.e., generate SQL on the fly to execute in the database through a cursor) I also wrote "much more difficult". If you haven't spent the past six months generating `psql` INSERT statements in a Python DA SearchCursor query, it's still "possible", just a heck of a lot of work. Way more work than dragging and dropping a FGDB feature class into a connection file with a Standard or Advanced seat license (against a properly prepared PG database with a lower-case schema that matches the login and has the correct permissions). - V ... View more