BLOG
|
We're pleased to introduce for the first time the ArcGIS Runtime SDK Sample Viewer! This application is a great tool for demonstrating the new and powerful capabilities in ArcGIS Runtime SDK 100.3 for Android. Install it for free today! ArcGIS Runtime SDK Sample Viewer - Apps on Google Play You'll also find the .apk on arcgis.com, publicly available today. Enjoy!
... View more
07-19-2018
09:28 AM
|
0
|
0
|
475
|
POST
|
Hi Onur, Geometric network tracing functionality is not supported yet in Runtime Core. It can be done using a geoprocessing package in Local Server, but that doesn't work on mobile devices. While we are aware of this functional gap, we are going to be working on support for Utility Networks sometime next year, where this may come up. It's hard to tell at this stage.
... View more
07-18-2018
08:05 AM
|
2
|
1
|
413
|
POST
|
Hi Daniel. String ldString = featureLayer.getLabelDefinitions().get(0).toJson(); if 'featureLayer' has at least 1 labelDefinition, calling toJson() will give you the serialized representation of that. In that string, you'll see the "Expression" value of where the text for that label comes from. Is this what you're looking for? Also see Show Labels on Layer—ArcGIS Runtime SDK for Android | ArcGIS for Developers .
... View more
07-08-2018
09:57 PM
|
0
|
1
|
282
|
BLOG
|
Today, we are happy to announce the release of ArcGIS Runtime SDK 100.3 (Update 3)! Please have a look at all that is new across all of the SDKs, as well as the specific items in the release notes for Java. We are looking to release another update in Fall 2018, Update 4, that will focus on another small collection of enhancements, most notably support for reading KML. Notice that we are announcing the deprecation of Java 8 support after Update 3 (Update 3 is supported through July 2022), and will stop supporting it in Runtime in a near future release. We want your feedback on this plan. Java 8's commercial end of life is January 2019, and so our focus will soon be on supporting the next LTS version of Java, Java 11. If you'd like to comment, please drop us a line here on GeoNet. Sincerely, The ArcGIS Runtime SDK for Java Team
... View more
07-05-2018
10:41 AM
|
0
|
0
|
429
|
BLOG
|
It's Update 3 release time! On top of the many exciting new features that are supported across the Runtime SDKs (web scenes, 3D distance measurement analysis, identifying and selecting web scene features, new WMS capibilities, etc), the Qt team has been hard at work adding some new features unique to this SDK for 100.3. Here are some of the highlights... Runtime API Transactional edit support. This allows the developer to commit or rollback a set of edits as one transaction. Other APIs introduced this at Update 2, and Qt now supports this feature with Update 3. Pagination of query results. This allows developers to set a result offset in the QueryParameters so that results can easily be paginated. Other APIs introduced this at Update 2, and Qt now supports this feature with Update 3. Time aware layers. The TimeAware interface was added and implemented by FeatureLayer, RasterLayer, ArcGISMapImageLayer, and WmsLayer. The new API allows you to set a time extent on the GeoView, and all layers participating will be filtered by the time extent. Other APIs introduced this at Update 2, and Qt now supports this feature with Update 3. The Runtime Error object is now creatable. This means that you can create custom Errors throughout your application and utilize the same error handling logic throughout your application, as well as provide additional details for any known issues. Support for OpenGL rendering on Windows. Qt has two different rendering engines for the Windows platform : OpenGL and DirectX via ANGLE. By default, Qt will try and render using OpenGL and if the proper drivers are not available, it will fall back to using ANGLE. Previous releases of ArcGIS Runtime only supported ANGLE. Update 3 fully supports both OpenGL and ANGLE so that you can fully utilize either rendering engine and Qt's fallback mechanism for when OpenGL cannot be utilized on a given system. For more information on this, please see Qt's documenation - https://wiki.qt.io/Qt_5_on_Windows_ANGLE_and_OpenGL Ability to get size and ID properties as either a string or int type in QML. Previously, these properties always returned as strings due to a limitation of the QML integer type being a 32-bit integer as opposed to 64-bit. You can now request the property as an int and get an actual QML int back. Toolkit API TimeSlider toolkit component. Coinciding with our new TimeAware support is a ready-to-use Toolkit component that allows you easily filter data based on time. The TimeSlider also allows you to play and pause an animation of your spatiotemporal data. CoordinateConversion toolkit component. An easy-to-use UI component is now available to help you convert a given coordinate to one or more different formats. For example, you could convert from Decimal Degrees to MGRS with this tool. This tool has a slick new UI making use of the modern Qt Quick Controls 2 module. SDK improvements Improved API documentation details added, as well as additional code snippets added throughout the documentation. Dozens of new samples have been added, with an extra emphasis placed on providing more fundamental samples, such as Geometry and GeometryEngine samples, as opposed to only new features. We are looking forward to hearing about your experience with this exciting release. Happy coding! - The Qt SDK Development Team
... View more
07-05-2018
01:09 AM
|
0
|
1
|
593
|
POST
|
You can first open the mobile map package to get the map(s) containing your vector (feature) layers that contain the polygons you want to get. // create a map view mapView = new MapView(); //load a mobile map package final String mmpkPath = new File("./samples-data/mmpk/Yellowstone.mmpk").getAbsolutePath(); MobileMapPackage mobileMapPackage = new MobileMapPackage(mmpkPath); mobileMapPackage.loadAsync();mobileMapPackage.addDoneLoadingListener(() -> { if (mobileMapPackage.getLoadStatus() == LoadStatus.LOADED && mobileMapPackage.getMaps().size() > 0) { //add the map from the mobile map package to the map view mapView.setMap(mobileMapPackage.getMaps().get(0)); } else { Alert alert = new Alert(Alert.AlertType.ERROR, "Failed to load the mobile map package"); alert.show(); } }); You will now have access to the map's operational layers, and you can find the one you need from that list. Just like any other feature layer from any other data source, you can query for Segids and Pages, using FeatureLayer.selectFeaturesAsync. The FeatureQueryResult will give you access to the number of selected segids and pages. You can iterate through each feature in the result, collect the geometry extent for each polygon, merge them using GeometryEngine, then zoom to the merged geometries using MapView.setViewpointGeometryAsync() - MapView| arcgis-android I think some good examples to look at are: Open Mobile Map Package—ArcGIS Runtime SDK for Android | ArcGIS for Developers Feature Layer Query—ArcGIS Runtime SDK for Android | ArcGIS for Developers
... View more
06-30-2018
02:38 PM
|
2
|
1
|
1196
|
POST
|
Hi Norbert! Technical Support should be able to provide the answers to you on this.
... View more
06-29-2018
01:49 PM
|
2
|
10
|
2051
|
POST
|
Hi Nathan. Thanks for reporting this. I assume you see this behavior with 100.2.1? We'll take a look. Has this been reported to Esri Support by chance?
... View more
06-15-2018
10:19 AM
|
0
|
1
|
743
|
POST
|
You can use the VS compiler, but if you are going to put that app that you compile into 'production', you need to buy a Qt commercial developer license. You can purchase these at a discount from Esri as well.
... View more
06-15-2018
10:13 AM
|
1
|
0
|
720
|
POST
|
Hi Charles, Have you tried the GeometryEngine "within" static method? GeometryEngine| arcgis-android . Let us know if this doesn't work for you.
... View more
06-15-2018
10:10 AM
|
1
|
0
|
571
|
POST
|
Hi Nathan, Yeah, I don't think App Logins is the answer for your use case. In your scenario, the users of your system need to have Named User accounts, it sounds like.
... View more
06-15-2018
09:06 AM
|
0
|
0
|
2613
|
POST
|
Hi Matus, You will need a Qt Commercial license if you plan to use their local compilers that come with the Qt SDK (from The Qt Company) to compile your application, regardless of whether you used AppStudio or just the ArcGIS Runtime SDK to build it. You will need to Commercial version, not the open source version. I hope this helps?
... View more
06-12-2018
01:57 PM
|
1
|
2
|
720
|
POST
|
class EasyAuthenticationHandler implements Authentication Handler { final string USERNAME = "GeorgeJetson"; final string USERPASSWORD = " ..... "; As long as GeorgeJetson is not allowing the app to present PRIVATE resources (requiring token authentication) to any of the app's end users. Then all of the people using the app would have access to all resources that have been shared with my organization. And this would work if 1000 users are logged in as GeogeJetson at the same time? No. With App Login, you can only share PUBLIC information shared with Everyone (well, technically, you CAN give access to your organization's private data....the software will not prevent this.... But that violates the ArcGIS Online terms of use). If your app shares any PRIVATE services, you would have to show the authentication dialog. Bottom line is, the "App Login" approach cannot be used to give access to things that end users would normally need a Named User subscription for. See what I mean?
... View more
06-07-2018
04:34 PM
|
0
|
2
|
2613
|
POST
|
Right. I apologize, Nathan. This example was not the correct one. You are asking the right questions. Let me try again and see if I can help. You don't want your users to see the OAUth dialog. You want them to access the things they need to without being asked to log in again. Correct? So in your app, you authenticate on their behalf, unseen to the user...using your named user credentials. Correct? This is all ok. As long as those services that your users ("unknown to the ArcGIS Platform") are accessing are not "private" services (need authentication). App Logins cannot be used for accessing protected/private services that need organizational Named User authentication. You may ask..."What? If everything is supposed to be public in app login scenarios, why use app logins at all?" Because you, as the app developer, may be paying for credit-burning services that are public. For example, the World Geocoding Service. These are public, but require a token, and they burn credits that need to be paid for. You, as the developer of the app, want to foot the bill for these services and therefore login via the app to use the credits and access the tokens on the user's behalf. Does this make sense? Let me know. Eric
... View more
06-07-2018
09:00 AM
|
0
|
0
|
2613
|
Title | Kudos | Posted |
---|---|---|
1 | 03-29-2016 11:51 AM | |
1 | 04-26-2015 09:53 AM | |
1 | 12-28-2016 03:30 PM | |
1 | 06-12-2018 01:57 PM | |
1 | 06-15-2018 10:13 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:22 AM
|