Jak upravíte desetinná místa pro hodnoty M v nástroji Identify v ArcPro? V ArcMap často používáme Identify Route Locations a hledáme stejnou/nebo podobnou funkčnost v Pro. Používání RH nástrojů dostupných v Pro vyžaduje licenci RH, což není realistické pro všechny naše uživatele.<\/P>
Byl jsem zde<\/A>, ale myslím, že to je pouze pro skutečný nástroj measure (vzdálenost).<\/P><\/span><\/P> <\/P><\/span><\/P><\/P><\/span><\/P><\/P><\/P>
<\/span><\/P> <\/P><\/span><\/P><\/P><\/span><\/P><\/P><\/P>
Can you please change the default radio button to the units you've adjusted the decimal precision for. It seems in the screenshot you are still using two decimals:
-amit@esri
Talking with @Amit with esri last night. Identify and that link is the poor man's version of the tool without R&H in Pro. Please mention if that doesn't work as that is our planned workaround.
Hope that helps.
Brian,
As you noted, the Explore/Identify tool does display the M-value at the point clicked. The way to get more decimal places in the M display is:
First: Project tab > Options > Select "Units" > expand the "Distance Units" section
Then: See which unit is the Default. Double-click on the Format for this unit > Numeric Format opens up > Adjust the Decimal places to a higher number
Finish: Hit OK, OK, (arrow back to project)
Now you should see more decimals of precision for the M value when you use the Explore/Identify tool.
Regards,
Forgot to credit Clive with that help as well.
I tried that before posting. Tried it again and it doesn't change. I modified both the 'miles' and the 'meters' since it is UTM Zone 14N and the measures are in miles. I closed and re-opened the Project, still no luck.
Am I missing something simple?
I am at Pro 2.7.1.
@AmitHazra we had the same issue as Brian and your response fixed it. Thanks.
Brian, look for which is the Default unit. In your first screen shot, I think I am seeing Foot as the default unit in your project.
Adjust that unit's decimal precision up.
This was counterintuitive to me when I first encountered it, because like you, the dataset I was working with was also in meters, the measures were calibrated to miles, but the default display unit was Foot.
P.S. I tested switching my default units to Miles, and the Explore/Identify started using that decimal precision for distances.
We have a winner. I get the joke now, I was thinking measures was in miles so that is where I adjusted the decimals. Thanks @AmitHazra , @CliveReece and @RyanKoschatzky
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
