Latest Contributions by JohnMDye

‎07-16-2019

Generally, I like the idea but I would have some concerns on how this works. It seems to me you could easily get into a situation where there's just a whole bunch of buttons on the side. Maybe a dropdown-style button where all of your custom buttons could be hosted, similar to the way the 'Open in ArcGIS Desktop' button works. Also Would you propose doing this at the individual item level or generally, like add this button to all 'Hosted Feature Layers', or perhaps both. Then there's the question of what that button should do and how it does it. Are you proposing just a simple URL call or would you want to be able to write some JS functions that will be called when the button is clicked? I highly doubt Esri would give us the latter and honestly, I'd be surprised if they gave us the former.

‎07-16-2019

Generally, I like the idea but I would have some concerns on how this works. It seems to me you could easily get into a situation where there's just a whole bunch of buttons on the side. Maybe a dropdown-style button where all of your custom buttons could be hosted, similar to the way the 'Open in ArcGIS Desktop' button works. Also Would you propose doing this at the individual item level or generally, like add this button to all 'Hosted Feature Layers', or perhaps both. Then there's the question of what that button should do and how it does it. Are you proposing just a simple URL call or would you want to be able to write some JS functions that will be called when the button is clicked? I highly doubt Esri would give us the latter and honestly, I'd be surprised if they gave us the former.

‎07-16-2019

So, Tracker is currently only available for ArcGIS Enterprise, so definitely you need that component. You also need the ArcGIS Spatio-Temporal Big Datastore. That's a free component, but it does require additional infrastructure deployments on your part. Now for the mobile component, Tracker is a field app and as such, it requires the ability to "write" its tracks to the Spatio-Temporal Big Datastore. So, your Account Manager is correct. My previous comment that Tracker is licensed at the Viewer level is not accurate. It would be impossible for a Viewer to use Tracker as Viewers do not have permission to write features. Rather, the Tracker has to be licensed with one of the User Types that includes the Field Apps bundle (Creator, Field Worker, GIS Professional). Alternatively, the Editor User Type is likely to have Tracker as a compatible Add-on App as well in the same way that it has Collector, Workforce, Survey123, Navigator and QuickCapture as compatible add-on apps. There is no mention of Tracker in the User Types page or anywhere else and I expect that is because the app is relatively new and the documentation hasn't been updated yet. Nonetheless, I would expect its licensing to align with that of the other Field Apps.

‎07-15-2019

Ugh, what an oversight. With internal stylesheets please! There's no reason I should have to use inline styling on every element and write the exact same style 100 times.

‎07-15-2019

Tracker for ArcGIS is a very simple, easy to use application. One of the best features is that you can schedule it to automagically start tracking on a schedule, which is pretty cool. As an Enterprise Administrator though, sometimes a Field Worker might need to be tracked out-of-schedule. This is especially true if they are leveraging one of the field apps that has also been deployed alongside tracker via our MDM with AppConfig. It would be great to be able to specify an AppConfig parameter on Collector, Workforce, Surve123, Business Analyst and the other mobile apps, so that when they are initialized they automatically call Tracker and tell it to start tracking. When the application shuts down, it also calls to Tracker and tells it to knock it off. It's not that scheduling isn't useful. It definitely is. However, sometimes users work out of schedule and if Tracker is not capturing that ad-hoc work that is being done, well that's portion of the work becomes unverifiable in terms of location tracking.

‎07-15-2019

Tracker for ArcGIS is a very simple, easy to use application. One of the best features is that you can schedule it to automagically start tracking on a schedule, which is pretty cool. As an Enterprise Administrator though, sometimes a Field Worker might need to be tracked out-of-schedule. This is especially true if they are leveraging one of the field apps that has also been deployed alongside tracker via our MDM with AppConfig. It would be great to be able to specify an AppConfig parameter on Collector, Workforce, Surve123, Business Analyst and the other mobile apps, so that when they are initialized they automatically call Tracker and tell it to start tracking. When the application shuts down, it also calls to Tracker and tells it to knock it off. It's not that scheduling isn't useful. It definitely is. However, sometimes users work out of schedule and if Tracker is not capturing that ad-hoc work that is being done, well that's portion of the work becomes unverifiable in terms of location tracking.

‎07-15-2019

Tracker for ArcGIS is a very simple, easy to use application. One of the best features is that you can schedule it to automagically start tracking on a schedule, which is pretty cool. As an Enterprise Administrator though, sometimes a Field Worker might need to be tracked out-of-schedule. This is especially true if they are leveraging one of the field apps that has also been deployed alongside tracker via our MDM with AppConfig. It would be great to be able to specify an AppConfig parameter on Collector, Workforce, Surve123, Business Analyst and the other mobile apps, so that when they are initialized they automatically call Tracker and tell it to start tracking. When the application shuts down, it also calls to Tracker and tells it to knock it off. It's not that scheduling isn't useful. It definitely is. However, sometimes users work out of schedule and if Tracker is not capturing that ad-hoc work that is being done, well that's portion of the work becomes unverifiable in terms of location tracking.

‎07-15-2019

Tracker for ArcGIS is a very simple, easy to use application. One of the best features is that you can schedule it to automagically start tracking on a schedule, which is pretty cool. As an Enterprise Administrator though, sometimes a Field Worker might need to be tracked out-of-schedule. This is especially true if they are leveraging one of the field apps that has also been deployed alongside tracker via our MDM with AppConfig. It would be great to be able to specify an AppConfig parameter on Collector, Workforce, Surve123, Business Analyst and the other mobile apps, so that when they are initialized they automatically call Tracker and tell it to start tracking. When the application shuts down, it also calls to Tracker and tells it to knock it off. It's not that scheduling isn't useful. It definitely is. However, sometimes users work out of schedule and if Tracker is not capturing that ad-hoc work that is being done, well that's portion of the work becomes unverifiable in terms of location tracking.

‎07-15-2019

Tracker for ArcGIS is a very simple, easy to use application. One of the best features is that you can schedule it to automagically start tracking on a schedule, which is pretty cool. As an Enterprise Administrator though, sometimes a Field Worker might need to be tracked out-of-schedule. This is especially true if they are leveraging one of the field apps that has also been deployed alongside tracker via our MDM with AppConfig. It would be great to be able to specify an AppConfig parameter on Collector, Workforce, Surve123, Business Analyst and the other mobile apps, so that when they are initialized they automatically call Tracker and tell it to start tracking. When the application shuts down, it also calls to Tracker and tells it to knock it off. It's not that scheduling isn't useful. It definitely is. However, sometimes users work out of schedule and if Tracker is not capturing that ad-hoc work that is being done, well that's portion of the work becomes unverifiable in terms of location tracking.

‎07-15-2019

Tracker for ArcGIS is a very simple, easy to use application. One of the best features is that you can schedule it to automagically start tracking on a schedule, which is pretty cool. As an Enterprise Administrator though, sometimes a Field Worker might need to be tracked out-of-schedule. This is especially true if they are leveraging one of the field apps that has also been deployed alongside tracker via our MDM with AppConfig. It would be great to be able to specify an AppConfig parameter on Collector, Workforce, Surve123, Business Analyst and the other mobile apps, so that when they are initialized they automatically call Tracker and tell it to start tracking. When the application shuts down, it also calls to Tracker and tells it to knock it off. It's not that scheduling isn't useful. It definitely is. However, sometimes users work out of schedule and if Tracker is not capturing that ad-hoc work that is being done, well that's portion of the work becomes unverifiable in terms of location tracking.

‎07-15-2019

Tracker for ArcGIS is a very simple, easy to use application. One of the best features is that you can schedule it to automagically start tracking on a schedule, which is pretty cool. As an Enterprise Administrator though, sometimes a Field Worker might need to be tracked out-of-schedule. This is especially true if they are leveraging one of the field apps that has also been deployed alongside tracker via our MDM with AppConfig. It would be great to be able to specify an AppConfig parameter on Collector, Workforce, Surve123, Business Analyst and the other mobile apps, so that when they are initialized they automatically call Tracker and tell it to start tracking. When the application shuts down, it also calls to Tracker and tells it to knock it off. It's not that scheduling isn't useful. It definitely is. However, sometimes users work out of schedule and if Tracker is not capturing that ad-hoc work that is being done, well that's portion of the work becomes unverifiable in terms of location tracking.

‎07-15-2019

Tracker for ArcGIS is a very simple, easy to use application. One of the best features is that you can schedule it to automagically start tracking on a schedule, which is pretty cool. As an Enterprise Administrator though, sometimes a Field Worker might need to be tracked out-of-schedule. This is especially true if they are leveraging one of the field apps that has also been deployed alongside tracker via our MDM with AppConfig. It would be great to be able to specify an AppConfig parameter on Collector, Workforce, Surve123, Business Analyst and the other mobile apps, so that when they are initialized they automatically call Tracker and tell it to start tracking. When the application shuts down, it also calls to Tracker and tells it to knock it off. It's not that scheduling isn't useful. It definitely is. However, sometimes users work out of schedule and if Tracker is not capturing that ad-hoc work that is being done, well that's portion of the work becomes unverifiable in terms of location tracking.

‎07-15-2019

Was toying with Tracker while at UC (sorry I couldn't track you down Jeff Shaner, but I did successfully make Craig Gillgrass cringe with a poorly thought out Workforce integration) and Aaron showed me that to connect tracks and create path, you basically have to leverage GeoAnalytics - which is obv. not available in AGOL and I know you guys are working on figuring out how to bring it to AGOL. All this to say, I get it. You collect a bajillion breadcrumbs and then you want to connect the dots to visualize the linear path of those tracks after the fact. That's going to take some horsepower, hence GeoAnalytics. But, I just wondered why Tracker is not just connecting the dots on the fly and producing a path layer as it goes along. Similar to the way many Esri apps rely on and manage multiple layers, it seems to me that Tracker should automagically be producing a 'Tracks' and 'Paths' layer, extending the path as new 'Tracks' are added. The only reason I could see not to do this if you wanted to have the option to also ensure that the paths generated by connecting the dots also align with a road network, in which case that is certainly some heavier processing. This didn't occur to me until later so I didn't get to ask anyone.

‎07-05-2019

Since more modern cars are coming with CarPlay and Android Auto support, I think it would be great to be able to get CarPlay/Android Auto integrations for the runtime apps. At a minimum, I would think Navigator and Tracker would be prime candidates for this. I'm actually surprised that Navigator doesn't already have this feature. I could see Workforce benefiting from it as well. Collector would be great too, but I can see all kinds of problems with that in terms of "distracted driver" issues. Even so, I could see it being very useful for digitizing service roads or new streets, off road trails and such. Just set collector to some sort of 'stream collection' mode, tell it your speed and drive the route at that speed. If even a halfway solution could be figured out, a CarPlay/Android Auto solution would be a lot better than what is probably already happening in scenarios where someone is driving and using one of these apps at the same time.

‎07-05-2019

Since more modern cars are coming with CarPlay and Android Auto support, I think it would be great to be able to get CarPlay/Android Auto integrations for the runtime apps. At a minimum, I would think Navigator and Tracker would be prime candidates for this. I'm actually surprised that Navigator doesn't already have this feature. I could see Workforce benefiting from it as well. Collector would be great too, but I can see all kinds of problems with that in terms of "distracted driver" issues. Even so, I could see it being very useful for digitizing service roads or new streets, off road trails and such. Just set collector to some sort of 'stream collection' mode, tell it your speed and drive the route at that speed. If even a halfway solution could be figured out, a CarPlay/Android Auto solution would be a lot better than what is probably already happening in scenarios where someone is driving and using one of these apps at the same time.

Online Status	Offline
Date Last Visited	‎05-19-2023 08:06 PM

My Ideas

Latest Contributions by JohnMDye

Re: Allow us to customize ArcGIS Online Item Buttons

Re: Allow us to customize ArcGIS Online Item Buttons

Re: Bring back location tracking in Collector

Re: Popup windows support standard HTML tags for formatting

AppConfig on Mobile Apps for initializing Tracker

AppConfig on Mobile Apps for initializing Tracker

AppConfig on Mobile Apps for initializing Tracker

AppConfig on Mobile Apps for initializing Tracker

AppConfig on Mobile Apps for initializing Tracker

AppConfig on Mobile Apps for initializing Tracker

AppConfig on Mobile Apps for initializing Tracker

AppConfig on Mobile Apps for initializing Tracker

Re: Bring back location tracking in Collector

CarPlay/Android Auto integrations for Runtime Apps

CarPlay/Android Auto integrations for Runtime Apps

Enable Editing & Editor Tracking via Python API

Date-Range Domains - what gives

App Studio for iPad

Is it possible to set the field length when publis...

Re: How do you edit a hosted feature service in Ar...