Latest Contributions by forestknutsen1

Are you working in a file geodatabase or sde? ... View more

Pandas might be for you. https://pandas.pydata.org/ http://geospatialtraining.com/tutorial-creating-a-pandas-dataframe-from-a-shapefile/ https://datatofish.com/export-dataframe-to-csv/ https://towardsdatascience.com/why-and-how-to-use-pandas-with-large-data-9594dda2ea4c I only have a ~140,000 rows to work within my test... but I think you could scale stuff up. https://stackoverflow.com/questions/14525344/whats-the-maximum-size-of-a-numpy-array import pandas import arcpy arcpy.env.workspace = connection source = 'coninfo' field_names = arcpy.ListFields(source) field_names = [x.name for x in field_names] field_names = field_names[:1] ar = arcpy.da.TableToNumPyArray(source, field_names) df = pandas.DataFrame(ar) df.to_csv('test.csv') ... View more

hahaha. Only 7 years? That fast??? I would think 10 or 15 would be more realistic... But, seriously, we did find the problem with ours. We were adding the service from a server without going through the portal web adaptor that has the server certificate. So, once we changed to go through the web adaptor the errors stopped. ... View more

Hi Eduardo, This was quite some time ago. But as I recall I did end up using Simplify Polygons in the Cartography toolbox Then I erased the original FC with the new output. I think there was a hand full of polygons that I had to go back and edit by hand. But overall it worked well. I was working with PLSS sections. They are basically square shapes with no gaps or overlaps. My data was not in a formal esri topology.  Section (United States land surveying) - Wikipedia  Okay, I hope that helps a little bit. Good luck! ... View more

Great! Thanks for clearing this up for me! ... View more

Okay, I tested this in the dev environment and as expected all rows now join to a version. We can see this in our user complaints as well. After each compress, the custom code would start to work again. And I could go in and see the that the offending "A" rows that did not join to a version had been removed by the compress operation. So, all working as expected with the compress.  Is there a way to get the version of the rows that don't join with the above sql before they are compressed away? Or is this something that sde just does not support? ... View more

Thanks Biraja The screen grab is the results of the sql query. And yes your understanding is correct. Is there a way to trace back the states/lineage to find what version the edit was made in for the rows that don't join with the above sql? Or maybe this is just how sde versioning works and there is no way back? This came up for us because we had some custom code looking at all of the values in the "A" table of a feature class and then blowing up on a bad value (yes the code is of poor quality and should be fixed). So, I wanted to find out the version the bad edit was made in. But I was unable to join it to a version with the above sql as the state/lineage of the version had moved on from the "A" row state/lineage... in the end I was able to track down the version by talking to users.  ... View more

Thanks for the feedback Biraja. So, if I am understanding you correctly your are suggesting something like this: with lina as (select a.objectid, s.lineage_name, s.state_id from a293 a join sde.states s on s.state_id = a.sde_state_id), linver as (select s.state_id, s.lineage_name, v.name from sde.versions v join sde.states s on v.state_id = s.state_id) select * from lina full outer join linver on lina.lineage_name = linver.lineage_name‍‍‍‍‍‍‍‍‍‍‍‍ But what about the rows in the "A" table that do not join to a current version lineage? How do I understand what version they were part of? ... View more

You can move freely between json and a python dict. Converting Dictionary to JSON in python - Stack Overflow  ... View more

I too have noticed this. Anyone have any suggestions? ... View more