BLOG
|
Further to my earlier messages, it wont be a configuration app from Trimble, but a firmware update for the hardware, and an update Survey123. The update for Survey123 is planned in 3.9 and I will advise on this post when the Trimble firmware update is available.
... View more
01-16-2020
06:42 PM
|
0
|
0
|
20971
|
BLOG
|
Thanks for picking up this omission, we have updated the topic re Geode in prep for next release.
... View more
12-17-2019
06:44 PM
|
0
|
0
|
20971
|
BLOG
|
No word as yet. Still awaiting Trimble app update that will enable Survey123 support on iOS.
... View more
11-20-2019
06:11 PM
|
0
|
0
|
20971
|
BLOG
|
To be specific, Trimble R1 works as expected on Android and Windows. For iOS we are awaiting a configuration app from Trimble themselves.
... View more
10-29-2019
05:20 PM
|
0
|
0
|
20971
|
POST
|
I have just successfully observed my bookmarks come across to ArcPad from ArcMap after check out. Am using ArcPad 10.2.5 and ArcMap 10.7. See screenshot with the two bookmarks in each. You also mention form management in ArcPad Studio. What changes are you making in ArcPad Studio? Bookmarks are saved in the APM. Do you see the bookmarks there?
... View more
09-24-2019
10:44 PM
|
0
|
0
|
701
|
POST
|
ArcPad doesnt read the file geodatabase directly, but you check out a portion of the file geodatabase using the ArcPad Data Manager in ArcGIS Desktop to take all that data (layers, related tables, domains, subtypes) into an AXF file. this file maintains the rules of your file geodatabase. After you edit the data in ArcPad you can check in the edits back to your file geodatabase. For more information see ArcPad Help .
... View more
09-24-2019
03:06 PM
|
1
|
0
|
545
|
POST
|
Yes. In fact we are wrapping up work on 10.2.6 at the moment. New releases are focused specifically on customer needs and discrete requirements or issues. If you have a issue or request please be sure to work with our Tech Support team to determine what is required. In fact, with ArcPads extensible design it might mean we can help you without needing a new release of the product.
... View more
09-24-2019
03:02 PM
|
2
|
1
|
862
|
BLOG
|
Have you made a great app for outdoor use, that would benefit from high accuracy location? Do your users want to improve the location that they capture or report in your app, by using an external receiver? Do you want to report a location in your app that is being fed from a receiver that is remote to you but available over a network? In each of these cases, you will want to add the ability to search for, and connect to, an external GNSS receiver in your app. We have recently added this ability to a number of our apps – Trek2There, Survey123, QuickCapture – and now we have made that work available to you, as a small collection of custom components, so you can drop them into your own app. There are a few considerations you need to evaluate before adding GNSS device discovery to your app – what hardware are you intending your app to be used on, what receivers you want to support – jump to the end of this post to explore those. For now, I want to show you the mechanics of making this work. The code that you can add to your app is available as an AppStudio sample called GNSS Discover. You can download this directly to your computer and copy and paste contents of it to your app. The following steps will demonstrate how to add GNSS device discovery to the Hello World (Runtime) starter app. I’ve deliberately chosen this lightweight app so you can see the few steps that it takes to add this complex functionality. Launch and sign in to AppStudio Desktop Edition. Search for and download, the GNSS Discover sample app. Click New App, choose Hello World (Runtime) and click Create. Select the app you just created in the AppStudio gallery, and from the side menu choose Files. This will launch a file browser showing you the files created for your new app. In the AppStudio gallery, select the GNSS Discover app that you downloaded already, and from the side menu choose Files. This will launch another file browser showing you the files of the sample app. Copy the subfolder called GNSSPlugin, from the sample app to the folder of your new app. Close both file browsers. In the AppStudio gallery, select your new app (created from the Hello World starter app) and from the side menu select Edit. Your app will now launch in your default code editor. You will make edits to the MyApp.qml file only. After the existing import statements at the top of the file, add the following reference for your app to be able to use the contents of the folder that you just copied to your project: import "./GNSSPlugin" Scroll to the bottom of the MyApp.qml file. Before the last curly brace, you need to add the following code. This code is also in the GNSSDiscover.qml of the GNSS Discover sample app. You can open this file and copy and paste from there if you prefer. // Manage connections to GNSS providers GNSSManager { id: gnssManager gnssSettingsPages: gnssSettingsPages } // GNSS settings UI GNSSSettingsPages { id: gnssSettingsPages gnssManager: gnssManager } // GNSS status UI GNSSStatusPages { id: gnssStatusPages gnssManager: gnssManager gnssSettingsPages: gnssSettingsPages } The GNSSManager that you have just added provides a new position source that will communicate with both your internal position source and any configured external position source. To use this, change the positionSource of the existing locationDisplay component, to be gnssManager. It should look like this: locationDisplay { positionSource: gnssManager } Save your work. If you choose to run your app at this stage (Alt+Shift+R), you will see the map launch and it will have two buttons, a home and location button. Click the location button and see that the map will center on your current location. By default, the app is using your devices internal position source. To be able to use an external receiver, you need to be able to select one. We will next add a settings button , so you have somewhere to select a new receiver. Copy the existing locationButton component and paste a copy of it immediately below the original one. Change the id of the copied component to be settingsButton. Change the source to be "./GNSSPlugin/images/round_settings_white_24dp.png" Change the name of the parameters in the onHoveredChanged event of this button to be settingsButton Remove the contents of the onClicked event and replace with gnssSettingsPages.showLocationSettings() Run your app. See that there is now an additional button with the settings icon. Click on this button and see the settings page. On this page you can choose to connect to a GNSS receiver that is connected to your device. As an optional bonus – would you like to make the color of the settings button match the others? You can do this with a color overlay.Start by adding the Qt Graphic Effects plugin so you can use the color overlay component. At the top of the file where the other import statements are, add the following: import QtGraphicalEffects 1.12 Add an id of settingsButtonImage to your button image component. Add the following code immediately after your button image component: ColorOverlay { anchors.fill: settingsButtonImage source: settingsButtonImage color: "black" } Ensure that the name for anchors.fill and source is the same as the name that your gave your settings button image in the previous step. Save your work and run your app. See that the settings button is now the same color as the other buttons. Instead of cloning and modifying an existing button, there is a settings button component in the GNSS Discover sample that you also could have used. Steps 12-17 show how you add new functionality to your app whilst maintaining the existing presentation of tools. Also included in the GNSS Discover sample is a status button that indicates when the position source is connected, and when clicked, displays information coming from that position source. In the next step, we will add this button as is. After the last button in your app, paste the following (this code is also in the GNSS Discover sample) GNSSStatusButton { gnssStatusPages: gnssStatusPages } Save your work and run your app. The status button is only visible when the location is active, so first click the location button for the status button to appear. See that the status button has different styling to your other buttons. You can choose to style it as you wish. Click on the status button to see information coming from the position source. You can add the components from the GNSS Discover sample to any other app in a similar way. Just include the GNSSPlugin folder in your app and reference the GNSS Manager, GNSS Settings and GNSS Status pages in your app. You can choose how to launch the settings and status pages to suit your needs. For alternative examples on how to launch those pages, take a look at the code for the GNSS Discover sample itself. This sample shows buttons for the status and settings pages, that appear on the toolbar of the sample app. Things to consider An app that needs to communicate with external GNSS hardware needs the high accuracy location and Bluetooth capabilities to be set. Also, to be able to work on iOS devices, the receiver must be part of the MFi program as well as support the output of NMEA sentences. Whilst building your app, we recommend you test in AppStudio Player. Player already has many GNSS receivers whitelisted so you can test your app on iOS before whitelisting your own app. To learn more about using GNSS receivers with your apps see https://doc.arcgis.com/en/appstudio/api-guide/apihighaccuracygps.htm
... View more
09-03-2019
11:09 PM
|
4
|
0
|
2909
|
BLOG
|
We are still working with Trimble on the support of the R1 on iOS. We have made some good progress since my last message, bu not enough to be able to give release date.
... View more
08-15-2019
03:10 PM
|
0
|
0
|
20971
|
BLOG
|
The Garmin Glo 2 will be supported on iOS in the next release of Survey123 (no, I cant give an exact date).
... View more
07-22-2019
04:07 PM
|
0
|
0
|
20971
|
POST
|
The 'While Using the App' and 'Always' options in the Location Services setting for Survey123 do the same thing - and in fact we have removed the 'Always' option from the next version of Survey123 (because it does nothing). So it wont matter which one you choose. From what you describe - I'm not sure it will work for you regardless of the Survey123 connection setting. When Collector goes into background I would expect it would continue to capture the line, hence the position source wouldn't be available for Survey123 to use. I would suggest you capture the line and points in one app. Perhaps you could try Survey123 beta on the Early Adopter Community - you can now create a survey that captures lines and points.
... View more
07-01-2019
06:09 PM
|
0
|
2
|
1288
|
POST
|
Are you still having this issue Sasha? You mention that you have Survey123 set to always stay connected - let me check - is this the connection mode of the location provider? I've been experimenting with a variety of devices and receivers and I've seen that I can successfully switch back and forth between Collector and Survey123 only when I set the connection mode to 'As needed' (in Survey123). This was the default behaviour pre Survey123 3.3, but we changed the default to improve the time to get a fix within the app. If your workflow is to switch back and forth between apps, then you should change the connection model to 'As needed'. This is not unique to the Arrow receiver, it is the same with others. Note to all curious GNSS users - the connection mode setting is not visible by default. To enable it, browse to the information page of your location provider and tap and hold on the title (in the green bar) A new setting called Connection Mode will appear. The default value is 'When the app is open'. If you need to switch back and forth between apps, change this to 'As needed'. Note that it may take a moment to get a fix next time you need to capture a location in Survey123. This is similar to the searching behaviour you will also see in Collector when you switch to that.
... View more
06-30-2019
06:59 PM
|
0
|
4
|
1288
|
POST
|
To change the list to arabic, ensure the label column title includes the arabic language code ar. for more information on multiple language support see Multiple language support—Survey123 for ArcGIS | ArcGIS . Saying that, i did a little more experimentation and I can now amend my earlier response, you can actually use HTML formatting inside a list also. In the following xlsform example, you can see the arabic list label, but also another list that has english labels, that have HTML formatting. Both will work. Here is the resultant form for the two select one cases:
... View more
04-17-2019
12:00 AM
|
2
|
0
|
3980
|
BLOG
|
Aha - thank you for pointing me to that statement in the tlsproducts summary page, but its wrong. It should read: Syncing feature services and upload/download ArcPad packages requires TLS 1.2 support provided by the OEM. I will get that statement fixed. Your paragraph after the screenshot might be a little muddled - are you still asking about windows mobile there? If you windows mobile device has windows ce version 6.5 or earlier, yes, there's no way to upgrade it. if it has windows ce 7, then it can be upgraded by the manufacturer. Bu yes, you can still use check out/in on windows mobile devices that do not have TLS 1.2.
... View more
04-07-2019
09:47 PM
|
0
|
0
|
968
|
BLOG
|
As a reminder / prompt - this change is happening on the 16th April 2019 - see the Technical Support information page for more info.
... View more
04-01-2019
04:13 PM
|
0
|
0
|
968
|
Title | Kudos | Posted |
---|---|---|
7 | 07-01-2025 04:21 PM | |
5 | 07-01-2025 04:21 PM | |
3 | 11-12-2024 09:15 PM | |
1 | 08-20-2024 04:58 PM | |
2 | 08-20-2024 03:39 PM |
Online Status |
Offline
|
Date Last Visited |
Monday
|