【20090713-01】AE中Uid

常见GIS图层接口GUID
最新推荐文章于 2022-03-29 13:41:29 发布
转载 最新推荐文章于 2022-03-29 13:41:29 发布 · 182 阅读 · 0 ·
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/willwayer/archive/2009/07/13/1522558.html
文章标签：

#php

本文列举了地理信息系统（GIS）中常见的图层接口及其GUID，包括IDataLayer、IFeatureLayer等，并展示了如何通过设置UID来获取指定类型的图层。

 

 

Here are the GUIDs for some of the common intefaces searched for:
{6CA416B1-E160-11D2-9F4E-00C04F6BC78E} IDataLayer
{40A9E885-5533-11d0-98BE-00805F7CED21} IFeatureLayer
{E156D7E5-22AF-11D3-9F99-00C04F6BC78E} IGeoFeatureLayer
{34B2EF81-F4AC-11D1-A245-080009B6F22B} IGraphicsLayer
{5CEAE408-4C0A-437F-9DB3-054D83919850} IFDOGraphicsLayer
{0C22A4C7-DAFD-11D2-9F46-00C04F6BC78E} ICoverageAnnotationLayer
{EDAD6644-1810-11D1-86AE-0000F8751720} IGroupLayer

 

 

IRasterLayer rl = new RasterLayerClass();
            Guid puid = (typeof(esriGlobeLayerType)).GUID;

 

获得指定类型的图层

UID puid = new UID();
  puid.Value = "{40A9E885-5533-11d0-98BE-00805F7CED21}"; //FeatureLayer的UID;

 

http://bbs.esrichina-bj.cn/ESRI/viewthread.php?tid=28565&highlight=uid

转载于:https://www.cnblogs.com/willwayer/archive/2009/07/13/1522558.html

AE中通过UID使用getLayer
asynx
10-09 1229
UID的官方解释是  COM interfaces and coclasses are identified by a globally unique identifier (GUID). The GUID for an interface is called an interface ID (IID). The GUID for a coclass is called class ID
在AxTOCControl控件中组织AxMapControl控件中的图层
u012488787的专栏
09-03 5613
一、环境ArcGIS10.2、VS2010 、win7 32位 二、读取Person GeoDatabase中要素集下的所有要素类，并添加到AxMapControl控件中。 这步完成，在AxTOCControl控件中显示的图层是自动的，如下图： 由于图层太多，可能有超过40个要素图层，就考虑对图层进行组织。   三、根据一定的规则（如：同一个管种有：点要素图层、线要素图层、面要素图层
mapcontrol 遍历所有图层方法
weixin_33790053的博客
06-03 570
通过IMap中的get_layers()可以遍历MapControl中当前的图层。此方法可以通过指定UID对图层进行过滤或者分类。 1. 遍历矢量图层 public IEnumLayer GetFeatureLayers() { UID uid = new UIDClass(); uid.Value =...
ArcEngine中getLayer方法的UID参数的详解
zy332719794的专栏
04-17 3923
UID中value的几种值以及表示的意思： {6CA416B1-E160-11D2-9F4E-00C04F6BC78E} IDataLayer {40A9E885-5533-11d0-98BE-00805F7CED21} IFeatureLayer {E156D7E5-22AF-11D3-9F99-00C04F6BC78E} IGeoFeatureLayer {34B2EF81-F4AC-
ArcGIS UID的用法
Prince的博客
06-22 1039
{6CA416B1-E160-11D2-9F4E-00C04F6BC78E} IDataLayer {40A9E885-5533-11d0-98BE-00805F7CED21} IFeatureLayer {E156D7E5-22AF-11D3-9F99-00C04F6BC78E} IGeoFeatureLayer {34B2EF81-F4AC-11D1-A245-080009B6F22B} IGraphicsLayer {5CEAE408-4C0A-437F-9DB3-054D83919850} IFDO
遍历MapControl中的图层方法
沙漠之花的博客
11-10 951
通过IMap中的get_layers()可以遍历MapControl中当前的图层。此方法可以通过指定UID对图层进行过滤或者分类。  1. 遍历矢量图层  public IEnumLayer GetFeatureLayers() { UID uid = new UIDClass(); uid.Value = "{40A9E885-5533-11d0-98BE-00805...
错误码 IllegalParam.AcceptingVpcId 请求 ID 28CB982E-B552-58DF-9BEE-90AE5A2454E6
04-21
提供请求ID `28CB982E-B552-58DF-9BEE-90AE5A2454E6`，可快速定位具体错误日志。 --- ### 常见错误场景示例 | 错误场景 | 解决方法 | |--------------------------|--------------------------------------| | ...
01-01 00:13:46.024 2141 2141 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 01-01 00:13:46.024 2141 2141 F DEBUG : Build fingerprint: &#39;realme/RMP2502IN/RE6453L1:15/UKQ1.231108.001/V.R4T1.50f6fcd-329ace1:user/release-keys&#39; 01-01 00:13:46.024 2141 2141 F DEBUG : Revision: &#39;0&#39; 01-01 00:13:46.024 2141 2141 F DEBUG : ABI: &#39;arm64&#39; 01-01 00:13:46.024 2141 2141 F DEBUG : Timestamp: 2025-01-01 00:13:45.939000309-0500 01-01 00:13:46.024 2141 2141 F DEBUG : Process uptime: 1s 01-01 00:13:46.025 2141 2141 F DEBUG : Cmdline: /odm/bin/hw/subsys_daemon -l /odm/lib64/lib-virtual-modem-radio-aidl.so -i 0 01-01 00:13:46.025 2141 2141 F DEBUG : pid: 2129, tid: 2129, name: Binder:subsys_d >>> /odm/bin/hw/subsys_daemon <<< 01-01 00:13:46.025 2141 2141 F DEBUG : uid: 1001 01-01 00:13:46.025 2141 2141 F DEBUG : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE) 01-01 00:13:46.025 2141 2141 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 01-01 00:13:46.025 2141 2141 F DEBUG : Abort message: &#39;Pointer tag for 0x7e1a931148 was truncated, see &#39;https://source.android.com/devices/tech/debug/tagged-pointers&#39;.&#39; 01-01 00:13:46.025 2141 2141 F DEBUG : x0 0000000000000000 x1 0000000000000851 x2 0000000000000006 x3 0000007ffcfe9560 01-01 00:13:46.025 2141 2141 F DEBUG : x4 7260761f37333030 x5 7260761f37333030 x6 7260761f37333030 x7 7f7f7f7f7f7f7f7f 01-01 00:13:46.025 2141 2141 F DEBUG : x8 00000000000000f0 x9 0000007e9f6f1608 x10 0000000000000001 x11 0000007e9f77aa50 01-01 00:13:46.025 2141 2141 F DEBUG : x12 000000006774cf09 x13 000000007fffffff x14 00000000000046b2 x15 000000002887433f 01-01 00:13:46.025 2141 2141 F DEBUG : x16 0000007e9f7e6f00 x17 0000007e9f7cf990 x18 0000007ea0ad0000 x19 0000000000000851 01-01 00:13:46.025 2141 2141 F DEBUG : x20 0000000000000851 x21 00000000ffffffff x22 0000007ffcfe96f1 x23 b400007e9ab482d0 01-01 00:13:46.025 2141 2141 F DEBUG : x24 0000007ea0354000 x25 000000000000002f x26 0000000000000000 x27 0000000000000000 01-01 00:13:46.025 2141 2141 F DEBUG : x28 0000000000000000 x29 0000007ffcfe95e0 01-01 00:13:46.025 2141 2141 F DEBUG : lr 0000007e9f762d58 sp 0000007ffcfe9540 pc 0000007e9f762d88 pst 0000000000001000 01-01 00:13:46.025 2141 2141 F DEBUG : 12 total frames 01-01 00:13:46.025 2141 2141 F DEBUG : backtrace: 01-01 00:13:46.025 2141 2141 F DEBUG : #00 pc 0000000000097d88 /apex/com.android.runtime/lib64/bionic/libc.so (abort+168) (BuildId: c23c39d0e7aacb7c4fb733dcd0e3cb19) 01-01 00:13:46.025 2141 2141 F DEBUG : #01 pc 00000000000515a8 /apex/com.android.runtime/lib64/bionic/libc.so (free+120) (BuildId: c23c39d0e7aacb7c4fb733dcd0e3cb19) 01-01 00:13:46.025 2141 2141 F DEBUG : #02 pc 0000000000023318 /odm/lib64/android.hardware.radio.voice-V1-ndk.so (ndk::ICInterface::ICInterfaceData::onDestroy(void*)+56) (BuildId: 34939db762097ad95945235c0867116b) 01-01 00:13:46.025 2141 2141 F DEBUG : #03 pc 0000000000014b28 /system/lib64/libbinder_ndk.so (ABBinder::~ABBinder()+72) (BuildId: 032745f0978de18ef9c83c1aa861b553) 01-01 00:13:46.026 2141 2141 F DEBUG : #04 pc 0000000000010c40 /system/lib64/libutils.so (android::RefBase::decStrong(void const*) const+160) (BuildId: e335e75b9933dbd38e10c5e8d7994c7e) 01-01 00:13:46.026 2141 2141 F DEBUG : #05 pc 0000000000048588 /odm/lib64/lib-virtual-modem-radio-aidl.so (RadioVoiceImpl::init(int, PlatformType)+472) (BuildId: c07f7ab3a500dda751ae00a36df388cf) 01-01 00:13:46.026 2141 2141 F DEBUG : #06 pc 000000000002b510 /odm/lib64/lib-virtual-modem-radio-aidl.so (PadRadioService::init()+176) (BuildId: c07f7ab3a500dda751ae00a36df388cf) 01-01 00:13:46.026 2141 2141 F DEBUG : #07 pc 000000000002b844 /odm/lib64/lib-virtual-modem-radio-aidl.so (onLoad+244) (BuildId: c07f7ab3a500dda751ae00a36df388cf) 01-01 00:13:46.026 2141 2141 F DEBUG : #08 pc 000000000000a3c4 /odm/bin/hw/subsys_daemon (DaemonApp::onCreate(int, char**)+820) (BuildId: cb91cf2af2c33f45fe0290d22e5b85e4) 01-01 00:13:46.026 2141 2141 F DEBUG : #09 pc 000000000000222c /odm/lib64/libmindroid-app.so (MainThread::main(int, char**)+156) (BuildId: 5971af6c09bfbd6373fefc3044d07b6f) 01-01 00:13:46.026 2141 2141 F DEBUG : #10 pc 0000000000002178 /odm/lib64/libmindroid-app.so (main+8) (BuildId: 5971af6c09bfbd6373fefc3044d07b6f) 01-01 00:13:46.026 2141 2141 F DEBUG : #11 pc 0000000000091524 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+116) (BuildId: c23c39d0e7aacb7c4fb733dcd0e3cb19) 01-01 00:13:46.099 2147 2147 F DEBUG : Process name is /odm/bin/hw/subsys_daemon -l /odm/lib64/lib-virtual-modem-radio-aidl.so -i 1, uid is 1001, not key_process 01-01 00:13:46.100 2147 2147 F DEBUG : keyProcess: 0
06-25
我们面对的是一个Android系统级崩溃问题，发生在`subsys_daemon`进程中，由指针标签截断（Pointertagtruncation）引发SIGABRT信号。根据日志，崩溃点位于`lib-virtual-modem-radio-aidl.so`库的`RadioVoiceImpl::...
MS51FB9AE_MS51XB9AE_MS51XB9BE_SC_Rev1.04技术手册中文版.pdf
04-11
文档中介绍了MS51FB9AE、MS51XB9AE、MS51XB9BE的引脚配置，包括TSSOP20脚封装和QFN20脚封装的引脚信息。每种封装类型的引脚排列和功能定义都有详细的描述，确保了用户可以正确地连接和配置微控制器。 5. 功能框图 ...
08-14 15:59:14.843 01224 01224 I libimsma_adapt: mtk-brm-commit-id:8783a29bae0ae84a456239f3212f27bdafa94c91 08-14 15:59:14.843 01224 01224 I libimsma_adapt: mtk-brm-change-id:Iee598bb542f5de895a4b71649fbc79b2d93bc3de 08-14 15:59:14.843 01224 01224 I libimsma_adapt: mtk-brm-merge-id:none 08-14 15:59:14.924 01273 01273 I emdlogger: mtk-brm-commit-id:04ab5bd912477cf2320dee54df9ac8b535476f2d 08-14 15:59:14.925 01273 01273 I emdlogger: mtk-brm-change-id:Ib405363e450403587f3a66bbe5b353966c086aba 08-14 15:59:14.925 01273 01273 I emdlogger: mtk-brm-merge-id:none 01-01 13:34:06.294 15692 17547 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 17547 (POSIX timer 9), pid 15692 (om.oplus.camera) 01-01 13:34:17.558 18178 18178 F DEBUG : Process name is com.oplus.camera, uid is 10167, not key_process 01-01 13:34:17.560 18178 18178 F DEBUG : keyProcess: 0 01-01 13:34:17.560 18178 18178 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 01-01 13:34:17.560 18178 18178 F DEBUG : Build fingerprint: &#39;realme/RMX5253/RE644C:15/AP3A.240617.008/V.R4T2.175910c_7d6745_7d139e:user/release-keys&#39; 01-01 13:34:17.561 18178 18178 F DEBUG : Revision: &#39;0&#39; 01-01 13:34:17.561 18178 18178 F DEBUG : ABI: &#39;arm64&#39; 01-01 13:34:17.561 18178 18178 F DEBUG : Timestamp: 2025-01-01 13:34:06.761352475+0800 01-01 13:34:17.561 18178 18178 F DEBUG : Process uptime: 69s 01-01 13:34:17.561 18178 18178 F DEBUG : Cmdline: com.oplus.camera 01-01 13:34:17.561 18178 18178 F DEBUG : pid: 15692, tid: 17547, name: POSIX timer 9 >>> com.oplus.camera <<< 01-01 13:34:17.561 18178 18178 F DEBUG : uid: 10167 01-01 13:34:17.561 18178 18178 F DEBUG : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE) 01-01 13:34:17.561 18178 18178 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 01-01 13:34:17.561 18178 18178 F DEBUG : x0 0000000000000000 x1 000000000000448b x2 0000000000000006 x3 000000000005b22e 01-01 13:34:17.561 18178 18178 F DEBUG : x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0080808000000000 01-01 13:34:17.561 18178 18178 F DEBUG : x8 0000000000000083 x9 160829885e63c0f0 x10 0000000000000083 x11 fffffffffffffffd 01-01 13:34:17.561 18178 18178 F DEBUG : x12 0000007993b3fda0 x13 0000000000000079 x14 0000007993b41138 x15 000000063a0d6e47 01-01 13:34:17.561 18178 18178 F DEBUG : x16 0000007bd5728598 x17 0000007bd570fbd0 x18 0000007906e20000 x19 0000000000000060 01-01 13:34:17.561 18178 18178 F DEBUG : x20 00000079d4b94d4b x21 00000079d4bb63e3 x22 00000079d4b7fa8e x23 00000079d4b7e2c0 01-01 13:34:17.561 18178 18178 F DEBUG : x24 00000079d4b94d82 x25 00000079d50088a8 x26 0000007993b41579 x27 00000079d532b840 01-01 13:34:17.561 18178 18178 F DEBUG : x28 00000000000fc000 x29 0000007993b415c0 01-01 13:34:17.561 18178 18178 F DEBUG : lr 00000079d4db3c54 sp 0000007993b41570 pc 0000007bd570fbd8 pst 0000000000001000 01-01 13:34:17.561 18178 18178 F DEBUG : 5 total frames 01-01 13:34:17.561 18178 18178 F DEBUG : backtrace: 01-01 13:34:17.561 18178 18178 F DEBUG : #00 pc 00000000000ffbd8 /apex/com.android.runtime/lib64/bionic/libc.so (tgkill+8) (BuildId: b963824e1119e1e9ec07440f1ee81f14) 01-01 13:34:17.561 18178 18178 F DEBUG : #01 pc 00000000002c8c50 /odm/lib64/libAlgoProcess.so (android::AlgoInterface::thirdPartyAlgoTimerFunc(sigval)+512) (BuildId: 113a6f60b430f0175d2f605dfee9702c) 01-01 13:34:17.562 18178 18178 F DEBUG : #02 pc 00000000000a4a44 /apex/com.android.runtime/lib64/bionic/libc.so (__timer_thread_start(void*)+196) (BuildId: b963824e1119e1e9ec07440f1ee81f14) 01-01 13:34:17.562 18178 18178 F DEBUG : #03 pc 00000000000a67a4 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+196) (BuildId: b963824e1119e1e9ec07440f1ee81f14) 01-01 13:34:17.562 18178 18178 F DEBUG : #04 pc 0000000000097b20 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: b963824e1119e1e9ec07440f1ee81f14)
最新发布
09-03
- **断言失败**：代码中使用了断言（assert）来确保某些条件为真。当断言条件不满足时，程序会触发 `SIGABRT` 信号终止。比如，在相机初始化过程中，某些关键参数未正确设置，断言检查失败，从而引发错误。 - **异常...
CE8AFADE8A880E7BC96E8AF91E599A8_1011_32bit-221961-o_1fi1h7ubp25i1vj7182btvg1s5er-uid-2523814.apk
11-03
CE8AFADE8A880E7BC96E8AF91E599A8_1011_32bit-221961-o_1fi1h7ubp25i1vj7182btvg1s5er-uid-2523814.apk
ArcEngine中UID使用资料收集
weixin_34237596的博客
07-02 273
ArcEngine中getLayer方法的UID参数的详解 UID中value的几种值以及表示的意思： {6CA416B1-E160-11D2-9F4E-00C04F6BC78E} IDataLayer {40A9E885-5533-11d0-98BE-00805F7CED21} IFeatureLayer {E156D7E5-...
ArcGIS UID的用法
kone666
09-15 1762
{6CA416B1-E160-11D2-9F4E-00C04F6BC78E} IDataLayer {40A9E885-5533-11d0-98BE-00805F7CED21} IFeatureLayer {E156D7E5-22AF-11D3-9F99-00C04F6BC78E} IGeoFeatureLayer {34B2EF81-F4AC-11D1-A245-080009B6F22B} I...
获取所有图层
qq_29768651的博客
03-29 550
/// <summary> /// 获取所有图层 /// </summary> /// <param name="map">地图对象</param> /// <returns>图层对象集合</returns> public static List<ILayer> GetLayers(IMap map) { .
MXD文档操作（一）-获取所有图层数据源信息
csu2015的专栏
08-17 5853
打开mxd文档 1 在后台打开 2 在arcgis中打开 获取mxd文档中所有图层的数据源信息 1 根据类型获取Layer 2 IFeatureLayer 3 IRasterLayer 4 IGroupLayer
Arcgis Engine获取IMap所有图层方式
GISningchong的博客
06-13 2208
1、获得要素图层通过UID获取       /// &lt;summary&gt;        /// 获得要素图层UID获取(第一种方法)        /// &lt;/summary&gt;        /// &lt;param name="pMap"&gt;IMap对象&lt;/param&gt;        /// &lt;returns&gt;&lt;/returns&gt
ArcGIS的UID
weixin_33859844的博客
03-24 228
關于什么是GUID，ProgID ，CLSID和UID，在ESRI的Document Library能夠找到下面的描述. COM interfaces and coclasses are identified by a globally unique identifier (GUID). The GUID for an interface is called an interface ...
ArcGIS Engine遍历图层，获取指定的图层
shenzhenzhao的博客
11-05 4453
遍历图层主要使用ICompositeLayer 类，可以理解为图层集合。主要思想就是获取当前地图的最上层图层列表，循环判断是图层集合还是图层，若是图层集合则继续向下遍历，若是图层则判断图层名称，直到找到指定的图层。 同理可以根据其他条件获取指定的图层，此处名称只是一个例子。 private ILayer relayer;//存储最终获取的图层 //根据图层...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值