POST
|
If I have a map that is vertically small ("short"), the popup from clicking on a point feature goes above the feature for many extents, as if it's trying its hardest to not cover the feature. This results in the title and most of the popup info flowing out of the top of the map window (see screenshot). The alternate behavior, letting the bottom of the popup flow out the bottom of the map window, does not appear to occur. It would be much more user friendly for the second behavior to occur, having it flow out the bottom so that title and top of the popup (with the most important info) is always visible. Steps to reproduce: Create a point layer in a map with a moderately sized popup, including a title Add that map to an Experience Resize the browser window to be short Click a feature and pan up and down to observe when the popup switches from above the feature to below the feature
... View more
11-28-2023
08:23 AM
|
0
|
0
|
135
|
POST
|
We were running into this problem as well when trying to append a spatially-enabled dataframe to an existing layer in a feature service. I don't know if this will help Joe, but I figured I'd put it here for anyone else who gets here from Google. Our workflow involved getting the live data from the feature service as a dataframe, inserting new rows, truncating the existing data from the feature service, and then using .append to write the new, enlarged dataframe to the feature service using the following code. We kept hitting the "Object reference not set..." error (which, digging through the API source, is coming from the method that keeps checking the status of the operation). geojson = dataframe.spatial.to_featureset().to_geojson
result, messages = target_featurelayer.append(
upload_format='geojson',
edits=geojson,
upsert=False,
return_messages=True,
rollback=True
) My coworker had the thought of checking for and removing all Nulls/NaNs in the dataframe, and this seems to have solved the problem. Any numeric columns with np.nan were set to 0 (which makes sense in this one use case; in the future, I may use -999 or something like that) and any text values were set to empty strings. His dataset is now uploading as it ought to, so it may be that somewhere in the featureset/geojson/append pipeline it really doesn't like null values.
... View more
10-06-2022
09:11 AM
|
1
|
0
|
1600
|
IDEA
|
When working with time-enabled data, ArcGIS Pro allows you to choose time steps based on the unique set of times found in the data. This allows you to step through irregularly-changing data one event at a time, which helps visualize historic data like boundary changes. However, this same functionality doesn't appear to exist in either the classic or new Map Viewer time sliders (unless I missed it somewhere). They only allow you to specify steps by a standard interval (10 years) or dividing the total time into a specified number of equal length intervals (150 years / 10 steps = 15-year intervals). It would be very useful for Map Viewer to have Pro's ability to set the time steps based on the unique times found in the data, as it would allow analysis and visualization of these types of time-enabled datasets without the need for desktop software.
... View more
05-13-2021
08:40 AM
|
7
|
1
|
639
|
POST
|
I was using memory to avoid having to clean up a bunch of intermediate files, but I've built a workaround with a temporary GDB that I can nuke when I'm finished. I'll stick with that until I have time to troubleshoot more. Thanks for the suggestions!
... View more
02-25-2021
02:21 PM
|
0
|
0
|
543
|
POST
|
Good catch on the slash, and that is how I understood "memory" to work- pretty much a drop-in replacement for on-disk datasets (but with some limitations as noted in the docs). However, SummarizeWithin() is still failing on me with "memory" output feature classes. It works with on-disk or memory source points but fails if I use a memory destination. I've been testing in a stand-alone script and also in iPython, both in a conda environment created via miniconda and arcpy installed via conda install arcpy -c esri.
... View more
02-25-2021
10:29 AM
|
0
|
0
|
560
|
POST
|
I have a script that runs SummarizeWithin() as a step in the analysis process. If I pass it paths to feature classes within an on-disk gdb for the input and output data it runs fine, but if I try to use "memory" datasets ("memory/in_points" and "memory/out_hexes"), it fails with "ERROR 000187: Only supports Geodatabase tables and feature classes". Does SummarizeWithin() not work with "memory" datasets?
... View more
02-25-2021
08:52 AM
|
0
|
4
|
580
|
POST
|
Everything looks back to normal from a cursory glance, and we're hearing the same from our users. Thanks for getting this fixed.
... View more
10-01-2020
07:14 AM
|
1
|
0
|
1401
|
POST
|
Woke up this morning to discover the WMTS-backed basemaps (http://utah.maps.arcgis.com/home/item.html?id=38a765a1306e4ba3804c0faaeede95e0) we share out to the entire state are blank. It looks like adding WMTS services in classic ArcGIS Online web maps just results in a blank layer. WMS services work fine. WMTS services work fine in Map Viewer Beta and ArcGIS Pro. Is this related to the September AGOL update?
... View more
09-30-2020
07:40 AM
|
1
|
3
|
1598
|
POST
|
D'oh, yeah, you're right on the range of valid lat/longs. My example point definitely wasn't in the range. While changing that, I realized I had my latitude and longitude reversed in my script, so all the points were not valid UTM points. Garbage in, garbage out. Everything worked as expected once I fixed that. Lessons learned: check your inputs, and if you .buffer() a PointGeometry object with NaN x/y values, you get back a _passthrough object instead of a Polygon object, and no error is raised.
... View more
11-01-2019
11:03 AM
|
1
|
1
|
951
|
POST
|
I'm trying to read in a CSV with point data in lat/long, reproject the points to UTM with .projectAs(), and then create a buffer around each point using .buffer(). I'm using the geometry objects rather than operating on feature classes as mentioned in the Discussion section of the PointGeometry documentation. When I try this procedure and then insert the resulting geometry into a feature class using an insert cursor, it fails with SystemError: <built-in method insertRow of da.InsertCursor object at 0x000001BACC5F1B70> returned NULL without setting an error. Digging further reveals that the buffer() operation returns an arcpy.arcobjects.mixins.GeometrySpecializationMixin._passthrough object instead of an arcpy.arcobjects.geometries.Polygon object. If I don't project a lat/long point but instead just buffer it directly, buffer() returns the Polygon object as expected (see example code below) and inserts just fine. If I create a very small buffer on the lat/long point (point.buffer(0.000001)), project the resulting polygon to UTM, and then buffer the UTM polygon it returns a Polygon as expected as well. Am I using .projectAs() on the lat/long points wrong? In [1]: import arcpy
In [2]: wgs84 = arcpy.SpatialReference(4326)
In [3]: utm = arcpy.SpatialReference(26912)
In [4]: p = arcpy.Point(10, 10)
In [5]: point = arcpy.PointGeometry(p, wgs84)
In [6]: type(point)
Out[6]: arcpy.arcobjects.geometries.PointGeometry
In [7]: utm_point = point.projectAs(utm)
In [8]: type(utm_point)
Out[8]: arcpy.arcobjects.geometries.PointGeometry
In [9]: point_buffer = point.buffer(10)
In [10]: type(point_buffer)
Out[10]: arcpy.arcobjects.geometries.Polygon
In [11]: utm_buffer = utm_point.buffer(10)
In [12]: type(utm_buffer)
Out[12]: arcpy.arcobjects.mixins.GeometrySpecializationMixin._passthrough
... View more
10-31-2019
09:47 AM
|
0
|
3
|
1088
|
Title | Kudos | Posted |
---|---|---|
1 | 10-06-2022 09:11 AM | |
7 | 05-13-2021 08:40 AM | |
1 | 11-01-2019 11:03 AM | |
1 | 10-01-2020 07:14 AM | |
1 | 09-30-2020 07:40 AM |
Online Status |
Offline
|
Date Last Visited |
03-07-2024
04:05 PM
|