Latest Contributions by PeteJordan

@Bud, yes I often am getting corrdinates from places like Google so haveing to re-arrage them was always a pain to do with the extra steps to make it work in the Go To XY tool. I also like how it just makes another pane on the side of Arc that I don't have to search for. If I have my Attribute Editor up in the bottom as I often do, I have to move that, to move the Go To XY tool to a visible space on the map. So it's now I don't have any use for that tool anymore since the Locate tool does everything better and much more efficiently...

@silverberrysea I have actually been using the Locate now for quite some time as I find it doing exactly what I need and much easier to use. I've actually unbound my GoTo XY and just use Locate now...

Thanks, I couldn't remember if I had done it or not, but I couldn't figure out how to remove it at all if it was me (which I guess it was)...

At the time George_Thompson suggested it was our version of SQL that was causing the issue amd we needed to upgrade and then move to PostGreSQL. At the time, it was marked as the solution (forgot if it was by me or George_Thompson. Since then, there was a work around @MartinWong1 explained involving enabling the enable/disable editing as ArcMap had which solved the issue for many of us until the issue got fixed in later updates. @joonpark also submitted a bug ticket on this as well from this thread since I hadn't done that at the time. After that, it seems a lot more people are not even able to work even with the work around that was proposed, but since it was marked as "solved" I'm not sure I can un-solve it if I was the one that did that. Either way, @George_Thompson might be able to Unsolve it on ESRI's end to keep this a current issue...

‎02-29-2024

With the errors popping up, that's kind of the only draw back with the work around for me. I've now kind of trained myself to ignore the little error warnings in the bottom and/or top and sometimes if doing processes with the SDE data, I forget that valid errors might also show up in the Notifications. So I just had to kind of train myself to only ignore them when editing the SDE data and not while doing any analysis on the data...

‎01-11-2024

Thanks for that. Our GIS admin was thinking they might contact ESRI as well, but I figured it's just all related to the same bug that was introduced in 3.2. It just seems like a caching problem of some sort, but now after discovering the error occuring overnight at some point, makes me wonder if there is just some weird disconect with the SDE server and Pro or something?

‎01-11-2024

Oh there isn't a new error. I just meant last night I left work and everything seemed ok and the data was showing, this morning the data vanished again and a new error popped up in the error window just saying it's that same STATE_ID=0 and that was it...

‎01-11-2024

Hey @George_Thompson, so we finally merged our data this week and tested it out on PostgreSQL (up to date) and after testing several things such as copying the old database to PostgreSQL, recreating a new table and appending it to PostgreSQL, I'm still getting this error. In testing though it seemed to be fine initially before I created templates for the feature class I am actively editing, but that could have just been a coincidence. I haven't tested it for any great length of time to see if that is for sure part of the problem or not though. Currently the only solution is what @MartinWong1 suggested and that's enabling editing and having it set to "single workspave edit session", which is what I had to use previously before we merged the data to PostgreSQL this week... Error code given ArcGIS Pro with the versioned data now in PostgreSQL: Note: Last night before I left work, things were working fine without the Enable Editing checked off. I left it over night and this morning is where I saw the error. So it seemed to occur even without me present overnight, if that is a clue or anything?

‎12-21-2023

Well ArcGIS Pro does have the ability as it does update properly if I switch the Cache mode. That refresh that is used when switching modes just needs to be made avaliable as an option to keybind and that would solve the issue, similar to using the standard <F5> to refresh. And yes this is done using the old ArcMap system where tables were edited directly to change measures. We have since obtained a licence for Roads & Highways, it's just we will need to spend some time to convert our existing LRS into the new schema for it to properly work with the new tools I would assume. So in the mean time, the quick fix would be just having access to that redraw/refresh process that happens when switching Cache methods. And yes I agree in the future we hope to use the new LRS funtionality in ArcGIS Pro...

‎12-20-2023

First we have an LRS table in SDE and instead of using SQL Manager Studios to update the LRS data, we have linked the table to Access to make it much easier. In old ArcMap, there were 2 registry files that could be used to toggle Caching to allow LRS updates to display the new measures graphically on the fly when changed. This was for all data on ArcMap regardless of project as it affected it as a whole and worked great. In ArcGIS Pro, it seems we have the Cache options on a layer by layer basis. With that, though, I have run into an issue. Issue It seems when updating an LRS measure in the database table in SDE, the data change will show in the attributes in ArcGIS Pro just fine, but Refreshing usually doesn't update the graphical part. The only way I've consistantly found to actually do this is to do the following: i) Original data (Step1 - Show original measures.jpg) a) Make the change in the database table (Step2 - Change a Measure.jpg) Test b) In ArcGIS Pro, Refresh (sometimes a few times) until I see the change in the attributes for that feature (Step3 - Change is shown in Attributes but no change in graphics.jpg) c) Go into the layer's Properties --> Cache and then change it from "Keep the cache between sessions. Automatically clear the cache every x mins" to "Clear cache when the session ends" or visa-versa. (Step4 - Cache showing current Method.jpg & Step5 - Change Cache Method.jpg) d) Press OK and this then redraws the features and displays the correct LRS extents for that feature. (Step6 - Update Now Reflects new LRS Measure Change.jpg) Edit: for some reason I can't put the image here in a spoiler or remove the extra duplicate one. I was hoping that the features would automatically update when there was a change to an LRS measure, but none of the options in the Cache pane does this. I have also tried to find the ESRI tool or code for the type of Refresh/redraw that occurs when I swtich between the two Cache methods above, but I am unable to find the one that those use to redraw the feature to the new measures (LRS - Refresh.jpg). Any ideas on why the Cache isn't working or if not, how I can keybind the Refresh/Redraw that occurs after you switch a Cache method? Unsure if this should be a bug or not? Thanks

‎12-07-2023

I have tested this myself and it does work. I do still get the errors showing up below, but it doesn't affect the drawing updates which is good. The only thing is I just have to remember to activate the editing session as I used to do in ArcMap with this method as each time you close out of the project and reopen ArcGIS Pro you have to enable the Editing again or else the attribute data is greyed out, but that only needs to be done only one time when you open the project. This has sped things up on my end a lot and very happy you found this...

‎12-06-2023

For those using versioned editing. My work around is to Reconcile, Post, Reconcile and that updates all my edits. It's annoying, but at least I don't have to exit and go back into the project each time it happens...

‎12-06-2023

@TanuHoque Though in some cases like mine where IT needs to either upgrade to SQL Server or move to something like PostGres then, rolling back would sovle the issue as it would in my case. The only reason I'm having to use a annoying work-around right now is because I'm enjoying testing out the new Customization feature in 3.2. So I think in some people's cases rolling back may solve the issue if it's like mine with versioned editing on an older SQL Server...

‎12-01-2023

Thanks for the document update @KoryKramer ...

‎11-20-2023

Yes, this might be an issue that will get us to push the move to PostGreSQL sooner then...

Online Status	Online
Date Last Visited	6 hours ago

My Ideas

Latest Contributions by PeteJordan

Re: Go To XY Lat-Lon Pair Input Box

Re: Go To XY Lat-Lon Pair Input Box

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: Cache Issue When Updating an LRS Measure on SDE via SQL Server

Cache Issue When Updating an LRS Measure on SDE via SQL Server

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro Keybind (Accelerator) Customization

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning STATE_ID Error when editing Polylines

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning ST...

Local Server Taken Offline - Issue with Pro Projec...

Changing Symbology for Selected Values Only

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning ST...

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning ST...