Latest Contributions by JasonJordan00

Using the FeatureLayerCollection method got it to return a token error message that pointed me to a step that slipped my mind. Our portal is behind a firewall so nothing is able to go public, but I forgot to share the layer publicly anyway so it doesn't look for a token (which our authorization methods doesn't easily generate through Python). That's what I've had to do for all other feature services I've used the API on, just plumb forgot to do it this time.

I've done this successfully on a dozen different scripts with other feature layers however this one is causing me issues. After logging into portal with the Python API, I get the item I am working with. port_item = gis.content.get('#############') That returns the appropriate item. Then I will grab the point layer. item_layers = port_item.layers That, however, returns 'None'. I've compared with other feature layers that it has worked fine on and I can't find any differences that would cause it to fail. Everything is a hosted feature service, everything is either points or polygons, and just switching out the itemID will successfully return other layers so I know there's not a typo or portal issue.

I've had this happen on some past projects. It's some sort of corruption or confliction issue with the new form package it downloaded. Sometimes clearing Survey123's cache and data from my phone settings would solve it, otherwise people had to uninstall and reinstall it. Either way they were good to go afterward.

You might try exporting lidar out at a 3D Scene Object .slpk file then uploading it straight into portal from your contents page. If the option to publish the slpk doesn't appear then it would be an issue with your data store as Calvin mentions.

In Catalog view, you can right click on folder or GDB locations and say 'Add to new projects' or 'Add to favorites'. This would at least let you shortcut to commonly used folders.

If you enable time settings on the feature layer's item content page, it will appear in the configuration options for the time slider widget is WAB. The time slider should interact with all layers that have time enabled. It's not as intuitive though, once the slider is turned on, you have to mouse hover over the date display to show the slider bar.

Several test mosaics I've run through have come out pretty crisp, however the color balancing is non-existent and the result looks horrible. Much better results with Pro's ortho maker or Drone2Map.

Yes, Portal and server are both operating normally. Again, this began happening immediately after upgrading to Pro 2.7.

The most consistent trend I've noticed is if I rapidly tap twice. Either by quickly jumping from point to point, double tapping a point, or jumping from a point to a menu.

I have pretty constant crashes in Field Maps too even without Arcade expressions in the layers on my Android. It's definitely still an infant app that could have stayed in Beta a little longer.

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by JasonJordan00

Re: 'None' returned from .layers with API

'None' returned from .layers with API

Re: Updating Public Survey Causes Unpacking Failure

Re: How to configure Portal to publish LiDAR Data?

Re: Can ArcGIS Pro remember window sizes and folders last visited?

Re: Using time series in Web AppBuilder with Time Slider

Re: ortho maker

Re: JSONDecodeError after updating to Pro 2.7

Re: Field maps crashing when selecting feature layer. Android

Re: Field maps crashing when selecting feature layer. Android