|
POST
|
Understanding the issue I think there are several solutions buts worth understanding why things are what they are. When you create a Feature Class you typically need to set a coordinate system as that's how the GIS knows where your data is. Don't set a coordinate system then your data could just a easily be on the moon. That's a "sphere" just like Earth... If you read the help file for the tool I link to above the coordinate system parameter tells you that you can set xy domain via the environment settings of the tool. But all that glitters is not gold... Go to the help page for xy domain environment and it states "...geodatabases automatically calculate a valid x,y domain based on the coordinate system". SO.. tools force a xy domain based upon the coordinate system of the data. That makes sense, as you create your features they need to exist somewhere and that is your coordinate system. Possible solution #1 But! You can create a Feature Class without a coordinate system (you simply don't provide one for that parameter) and ONLY THEN can you set the xy domain. So now you have a dataset that has an unknown coordinate system but an xy domain extent you set. But you can't edit into it! Note if you have a dataset with no coordinate system then ArcPro refuses to allow you to edit it. All a bit chicken 'n' egg. But there is a sort of a legacy tool from the past which is define projection , this allows you to set the coordinate system of a dataset which was unknown. Finally you have a featureclass that has a coordinate system, a user define xy domain extent and is editable. But... I can't say with certain, go run one of the many other tools on your data and they simply reset the extent to the domain of the coordinate system. So a complete waste of time... Possible (untested) solution #2 Modern versions of ArcPro have massively expanded the capability of a geodatabase through attribute rules. Arcade code that gets executed when you insert/edit a feature. It would take very little code to query the geometry and ask does it fall within the extent of a predefined area, if not reject the edit. Rules are associated with layers in your project. I would suggest solution #2.
... View more
yesterday
|
0
|
0
|
13
|
|
BLOG
|
This is a tool that will have far reaching impacts for many organisations. Where I work we have many legacy projects that were built using personal geodatabases. I support staff who have a long history of using ArcMap and personal geodatabases. With Universities forced by esri to drop support for ArcMap there are many projects with datasets that are sitting in project folders in these older formats. In true academic style these projects often have a habit of bubbling back to the surface years later, so having a way to transfer them into file geodatabases is critical. Now esri might have said in the past you need to migrate, the rest of the WORLD would responded saying who has time for that! Especially projects that have come to the end of their funding. I feel this new tool is that "get out of jail" card! Use it when we need to. I can already think of several projects I could save from obsolescence! Nice.
... View more
a week ago
|
0
|
0
|
99
|
|
POST
|
Christopher, Perfect! That did the trick, thank you. Now I know what its called I went searching for it in the help file. I even used the document assistant. There appears to be no documentation in the esri arcpro help file on what the chart selection outline is and how to turn it off/on. I would recommend you point this out to the documentation team so they can add it and allow people and no doubt ai to discover what it is and how to turn it off/on.
... View more
a week ago
|
1
|
0
|
260
|
|
IDEA
|
When exporting a chart in arcpro 3.7 which is a set of histograms created using the split by option, ensure the purple border is not included in the export (to clipboard) as it makes that function useless when including the chart in a report as it retains the purple border. I think the copy to clipboard is a great feature as it skips the need to export to a file, but is not useful if it retains the purple selection boundary. A discussion of exactly what I'm talking about is here.
... View more
a week ago
|
0
|
1
|
216
|
|
POST
|
Robert, Unfortunately that idea of clicking onto a different view/pane and even closing down the chart properties pane does not work, the purple border still persists. I have discovered that if I export to a PNG it does lose the purple border, so it is possible to get an image of the chart without the purple border. I'm going to suggest an idea that the copy to clipboard does not retain the annoying purple selection border!
... View more
a week ago
|
1
|
0
|
325
|
|
POST
|
Agree but I don't seem to be able to unselect a histogram? Seems like an obvious thing to do but not possible. Unless there is some secret set of key strokes...?
... View more
a week ago
|
0
|
0
|
357
|
|
POST
|
I have created a simple histogram chart from data in arcpro 3.7 grouped by sediment size. Data is displaying as expected except a purple border around one of the graphs, I show this below. How on Earth do I remove this border? It seems like an unintended bug? I've tried holding down crtl or shift and clicking on graphs but nothing seems to remove it, at best by clicking on the other graph the border swaps over to the other graph. It means I can't copy the chart to clipboard to insert into a report as it retains the irritating purple border. Any advice? Duncan
... View more
a week ago
|
0
|
7
|
400
|
|
POST
|
@HongXu thank you for the answer that is the solution to get to the raw pixels values! I must say "A No-Op Function" statement is not very helpful whilst the Analytical and Cartographic renderers provide informative advice. Please could you feed that back to the ArcPro development team. A simple explanation of what that means would be very useful in that Processing Template dropdown. If I search esri help for "A No-Op Function" it returns nothing, so I have know way of finding out what it is...
... View more
4 weeks ago
|
0
|
0
|
195
|
|
POST
|
Hi Jeff, Thanks for pointing me to the sentinel 2 imagery layer. This is indeed giving me that much needed acquisition date. It's a shame that the wayback data does not seem to keep that, as the quality of those images are very good. May be moving forward, future versions of the wayback metadata could provide such information? I can only but hope! Duncan
... View more
04-20-2026
08:44 AM
|
0
|
0
|
1054
|
|
POST
|
Hi Jeff, Thanks for finding time to help me understand the data. So using my example in the original question, am I correct in saying that the way back images were archived in 2019 and that knowing from the glacier dataset I have it was showing a 2003 image when it was archived. But since then the tile layer has been rebuilt and has overwritten (?) the original source image date with 2024 date? Would that mean as a user I can never truly know what the source image date is as the metadata is reporting the built date of the tile layer? Or have I got the wrong end of the stick?
... View more
04-18-2026
09:54 AM
|
0
|
2
|
1124
|
|
POST
|
For the metadata the url was - https://metadata.maptiles.arcgis.com/arcgis/services For the imagery the url was - https://wayback.maptiles.arcgis.com/arcgis/rest/services/World_Imagery/MapServer
... View more
04-15-2026
07:35 AM
|
1
|
0
|
1202
|
|
POST
|
Just thinking out aloud, when you extended the line have you mistakenly created a multi-part feature? Just go into edit mode and use the vertices tool and in the panel you'll see it list the vertices and if it has grouped them into parts that may be the source of your issue?
... View more
04-15-2026
03:17 AM
|
0
|
1
|
342
|
|
IDEA
|
I like the idea of it duplicating the last clause but would find it highly irritating if it did it automatically! I would say the opposite to you I don't always add a near identical line to the next clause statement. I think the interface needs to be tweaked and some sort of button on the far right (next to the red cross) that duplicates the last clause would be my preferred solution.
... View more
04-14-2026
04:02 PM
|
0
|
0
|
379
|
|
POST
|
Hi Jon, Thanks for the pointer to the website, I explored this and the info box that pops up provides even less detail than the metadata layer when loaded in ArcPro. So it does not resolve my query. Useful website for quickly checking imagery. Duncan
... View more
04-14-2026
06:38 AM
|
1
|
2
|
1245
|
|
POST
|
I'm accessing wayback imagery to update a dataset of glacial fronts on South Georgia. ArcPro and the wayback imagery offer a convenient dataset to digitise against, but ONLY if you know the date of the image. Hence I also access the equivalent wayback metadata for the same release of the imagery. Now I know and expect some imagery I see is actually from a few years earlier and that world imagery has yet to update with new imagery, this make sense and I think something acceptable. It's when it some how reports the future that I am highly suspicious! It undermines the confidence of what I am actually viewing. Can someone from the esri imagery team explain why I am seeing what I see below? I have the 2019 (r00) turned on along with its equivalent 2019_r00 metadata. I have the historic glacial front dataset showing part of a 2003 edge selected. The 2003 data was captured using landsat 7. Note that the 2003 edge aligns wonderfully with the wayback imagery of 2019. Now my small brain is telling me that the world imagery of 2019 had not updated and therefore is showing 2003 images. That would make logical sense, except if you look at the pop-up on the right the metadata is reporting a 2024 image, 5 years into the future?
... View more
04-14-2026
04:16 AM
|
1
|
10
|
1441
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 1 | a week ago | |
| 1 | 04-15-2026 07:35 AM | |
| 1 | 04-14-2026 06:38 AM | |
| 1 | 04-14-2026 04:16 AM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|