The ArcGIS Pro Roadmap is now being maintained as a GeoNet Document. Please go here: https://go.esri.com/ProRoadMap
Just read that in the post.
Scene Layer Editing - The ability to edit or delete feature-centric I3S layers, including 3D Object and 3D Point layers. This will include attribute edits, attribute table edits, symbology, and geometry edits. Great!
What does "Editing Scene Layer" imply (I see it in the "Near-term" implementations)? Would it be possible to (e.g.) add a Hosted Scene Layer to ArcGIS Pro, and edit it in a scene view? I opened a thread on this, will update there or here if I receive a feedback. Thanks.
If this is a question, please post as a question in https://community.esri.com/community/gis/applications/arcgis-pro?sr=search&searchId=b4aa02a5-ba56-4d2f-9111-968d4d9727e6&searchIndex=1
If it is an idea, please submit to https://community.esri.com/community/arcgis-ideas?sr=search&searchId=c15d61ca-afb3-473d-a101-962d2819fda8&searchIndex=0
Need to be able to customize a grid in layout to include Township Range.
Thank you Dan.
I will update now!
According to this... http://pro.arcgis.com/en/pro-app/get-started/release-notes.htm
This bug was fixed at... Issues Addressed at ArcGIS Pro 2.1.2
BUG-000111919
ECW files cannot be read in ArcGIS Pro.
Does 2.1 support ECW format files yet?
I updated to 2.1 a while ago but had to roll-back to 2.0 due to ECW files no longer being supported in 2.1.
Cheers,
It just means the training folks have something new to peddle...
t
The Borg!!!!
Resistance is Futile
Steady Joshua
No joke, but they only sent it to our "leaders," which likely don't bother to read e-mail from Esri anyways.
Seriously? That's a real email? That's as bad as Romney's "The other 46%" speech....
You just missed the memo (e-mail received by one of my co-workers from Esri):
As a leader at an organization with an Esri Enterprise Agreement, you understand the transformational and strategic business impacts of GIS technology. To achieve enterprise-wide benefits from your ArcGIS platform, your workforce must be willing to discard legacy workflows. Human resistance to change is a powerful force.
It is simple, just disregard those "legacy workflows" and change to whatever Esri is selling this year.
"Shape overrides are something we're still evaluating." Why isn't that "In the Product Plan"? I'm curious as to why Representation, and all of its features and workflows, isn't included in Pro. Were customers demanding that it be unsupported? I'm looking for that idea, do you have a link to it? It's pretty frustrating to have spent years on our most popular map series built with Representation, only to learn that we're going to have to start from scratch with the replacement software if we wish to continue producing and editing those maps.
A large number of representation capabilities have existed in ArcGIS Pro since version 1.0 for standard feature layers. For instance, the symbol model incorporates geometric effects and marker placements and has a similar structure to representations. Field based overrides are available and have extended capabilities with expressions (see Attribute-driven symbology—ArcGIS Pro | ArcGIS Desktop for more info). Our approach moving forward will be to add capabilities to feature layers rather than continuing with the representation model. We plan to improve the migration from representations in a future release. So what's missing?: Primarily some editing tool capabilities, marker editing, and shape overrides. Editing tool enhancements are in the product plan. For marker editing, we've gone down the path of promoting import of graphics from SVG and modifying (e.g. color / rotation) after import. Shape overrides are something we're still evaluating.
My recommendation, from early 2017, was to have the RoadMap as a GeoNet document and not a blog post. GeoNet documents are more robust than blogs when it comes to content that changes over time. Sadly, we are stuck with the blog post still.
I understand the desire for that but its incredibly confusing. I'd suggest having a new post for every new version but reference the previous ones.
More than likely the "original" post was updated and the "Created date" went to the last date modified.
I think of it as living document.
This thread is really hard to follow. The post says it was created on February 2, 2018 but there are comments from 2017 on here. I can't figure out what comments are based on the new information without reading the dates. I'm not sure using the typical thread format for this is working very well.
https://community.esri.com/groups/esri-deutschland-partner-community?sr=search&searchId=ff6b76cc-0a3f-4003-b0ed-0b1f85b6535a&searchIndex=0
Disappointing to not see https://community.esri.com/ideas/12258 on the road map. For many, that's a fish or cut bait barrier to adopting Pro.
We are not planning for spell check within attribute tables at this time. Our initial focus will be on text items within the layout.
Are you planning for the Spell Check component to have functionality to spell check within attribute tables? Or just map elements (i.e. labels, titles, etc)?
The COGO functionality in Pro (Traverse tool) is available in every license level. The type of geodatabase (file, enterprise) is one of the key factors to determine the needed license level.
The ground to grid corrections functionality is also planned to available for all license levels and is key when precise measurements are used from ground values.
The ground to grid correction used to be available as one of editing option without having to use any of ESRI’s parcel management tools. This made doing basic cogo possible with just a basic license. It was part of the core editing functionality. Please make the editing tools equivalent to what was in ArcGIS Desktop.
Wesley Keller
GIS Analyst
City of Universal City
210-659-0333 x722
Wesley, see this thread that gives more details about timelines: https://community.esri.com/ideas/13861
Amir,
In ArcGIS Desktop in the editing options there used to be tools that would allow the user to choose bearing/azimuth and distance units. There also used to be a place where you could choose a ground-to-grid correction: both a bearing adjustment and a scale factor. These were available under the default editing tools and were separate from the COGO tools. This gave me the ability to create GIS data from survey descriptions and plats with only a basic license. This will seriously affect by ability to to completely adopt ArcGIS Pro.
Hi WiscRapids I did some research and saw a case that was logged against ArcGIS Pro 1.3.1 crashing. It looks like there was room for quite a bit more troubleshooting for that particular issue. Is your comment referencing that case from last year?
Are you currently working in ArcGIS Pro 2.0.1? Are you experiencing the same issue with crashing?
Is it a particular Project where this occurs, a particular process or workflow that causes the crash, or importing a certain MXD?
Please let me know if you're still experiencing crashes. We'd like to help.
Thank you.
!!!!
I put in a ticket for Pro crashing on import. The outcome was that I was told to rebuild the map in Pro.
Thanks Thomas. We recently setup Portal and Federated so we are able to follow you workflow. It works as expected and we are able to start transitioning over to ArcGIS Pro. Next we'll likely transition from AGOL to Portal.
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Nový zde? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
