|
POST
|
Sorry to hear that. Honest, this does work. Here's a useful step by step: Problem: XY points from a CSV file display incorrectly in ArcMap https://support.esri.com/en/technical-article/000012576 It is very important not to try to convert any coordinate systems until you have the points plotting in map projection, projecting on the fly (for example, to state plane) on the data frame. If you have that working, then you can save the events to a point feature class either using Data > Export (set output CS same as data frame) or using the Project tool.
... View more
07-15-2019
11:02 AM
|
2
|
0
|
4254
|
|
POST
|
I am wondering if full item/description metadata is supported, as the Pro help says that only the summary and tags are prompted for when you share these items. So I don't know, I maybe a call to tech support is warranted as no one else has chimed in. If you find out, please update this thread.
... View more
07-15-2019
10:50 AM
|
0
|
0
|
1271
|
|
POST
|
I am assuming you are using ArcMap. This is a common issue folks run into. The coordinate system you specify in the add xy to map dialog must be the one of the xy coordinates in the table -- NOT the data frame coordinate system (Ohio State Plane) - which unfortunately is the default that comes up. So you should change the coordinate system to one that matches your data table location values (a geographic -- lat/long -- not projected -- coordinate system, for example WGS84 or NAD83). If you do that your points should plot in your data frame in the correct place, regardless of the data frame coordinate system setting (state plane, utm, etc). Hope this helps!
... View more
07-15-2019
10:04 AM
|
0
|
2
|
4254
|
|
POST
|
You can access raster fields using the Lookup tool. Not so sure you can apply Raster Calculator on text values however.
... View more
07-10-2019
09:47 PM
|
1
|
3
|
2175
|
|
BLOG
|
From the https://community.esri.com/community/events/user-conference/blog/2019/06/26/2019-uc-qa?sr=search&searchId=f9a45665-026b-4fd1-8049-de5968239a1c&searchIndex=3 - reposting here for wider distribution Standards-compliant metadata is already supported for items throughout the ArcGIS platform for viewing and editing in ArcMap, ArcGIS Pro, ArcGIS Online, and ArcGIS Enterprise. Support for more recent updates to the ISO 19115 standard (-1/2/3) are under development. ArcGIS Online and ArcGIS Enterprise now allow users to view layer-level metadata for hosted feature layers from the layer's item page. The metadata is displayed in the style configured by the organization. Additionally, when exporting hosted feature layers to a file geodatabase or to shapefiles, layer-level metadata is included in the exported feature classes. At present, the layer-level metadata is read-only; it will be editable in the future. In ArcGIS Pro 2.1, we introduced the ability for map layers either to reference a read-only version of their source data's metadata (the default), or to have their own metadata independent of the source data’s metadata. With the release of ArcGIS Pro 2.2, users are able to import metadata to an item, save a copy of ArcGIS metadata to a file on disk, and export an item’s metadata to a standard-format XML file. Users are also able to upgrade metadata created in ArcGIS Desktop 9.x (for example) to the ArcGIS metadata format so it can be viewed and managed in ArcGIS Pro. When publishing a map from ArcGIS Pro, the map’s full ArcGIS metadata will be published with the data and transferred to the portal item. Using ArcGIS Pro’s metadata import capabilities full metadata can be transferred from local maps to the portal items that were published with earlier versions of ArcGIS Pro. When ArcGIS Pro 2.2 is used together with ArcGIS Enterprise the process of updating metadata for published content will be more streamlined than ever. If you publish a map service where layers reference data in an enterprise geodatabase that is registered as a data store item, and the map layers reference the data source’s metadata—updates to the feature class metadata are instantly available in the portal when someone views metadata for the service’s layers. With the Pro 2.3 release (Jan ‘19), you can create Metadata for a Project and extend Pro with the Pro Metadata Toolkit (https://github.com/Esri/arcgis-pro-metadata-toolkit). The ArcGIS Pro Metadata Toolkit provides resources to create an Add-In that allows you to customize the pages that appear in the ArcGIS Pro metadata editor to suit your organizational, community, or regional requirements. For the upcoming Pro 2.4 release, Esri will begin a phased approach for supporting the newer ISO 19115-1 and the 19115-3 specifications by first allowing import of an ISO 19115-3 metadata file; however, this file will lose any new attributes not supported by old standard upon import. Full support for ISO 19115-1/2/3 is planned for a Pro 2.5 release.
... View more
07-05-2019
03:08 PM
|
1
|
0
|
1128
|
|
BLOG
|
This is breakthrough stuff! Fantastic!! Definitely will add this capability to my analysis class in the fall.
... View more
07-05-2019
02:46 PM
|
1
|
0
|
656
|
|
POST
|
Oh, your new code makes it more clear to me what you are trying to do. Here are some expressions that should work. expression = '!ValveID!.replace("SV","").replace("HV","").replace("SR","").replace("ZB","")'
# or simply remove the first two characters:
expression = '!ValveID![2:]'
... View more
07-05-2019
02:27 PM
|
2
|
0
|
2618
|
|
IDEA
|
Still miss RESELECT KEYFILE in ArcPlot which would do a similar thing. Select records in table 1 and migrate that selection to another table through a pair of key files in the source and destination table, regardless of 1-M,M-1,or M-N cardinality. Workflows exist in geoprocessing but most are clunky. Implementing this with relates would be very consistent and elegant and also allow the use of stored relationship classes and on the fly relationships created with Add Relate in Pro.
... View more
07-05-2019
02:18 PM
|
2
|
0
|
5685
|
|
POST
|
Reclassify won't work for this as it reclassifies the data in a single value field. I agree with Lauren that working with Calculate Field in the raster table may be (much) more efficient, but I'm wondering how you got such a "fat" raster table. If the fat table was output from the Combine tool, you may want to skip the Combine tool and do this instead using the five input rasters: Con("RasterA" > 50, "RasterA",
Con("RasterB" > 50, "RasterB",
Con("RasterC" > 50, "RasterC",
Con("RasterD" > 50, "RasterD",
"RasterE"))))
... View more
07-05-2019
02:04 PM
|
0
|
0
|
13964
|
|
POST
|
I agree I do not believe relates are supported in geoprocessing. The best way to do one to many relates is either to build a long query expression as Duncan suggests using arcpy, or, add a join from the 'many' table to the 'one' table and use a sql expression use a query find the records that match in an unambiguous many to one join. For example, run this select on manytable with the active join to onetable: onetable.OBJECT IS NOT NULL and onetable.RECTYPE = 'BEST'
... View more
07-05-2019
01:45 PM
|
1
|
0
|
3564
|
|
POST
|
Everyone be sure and check out the enhancements to Model Builder added at Pro 2.4! I love the new ability to see a python version of an existing model and the returned (from ArcMap) ability to export to Python script -- a great learning tool! Hope to meet you next week Shitij Mehta! https://community.esri.com/community/arcgis-ideas/blog/2019/07/02/ideas-in-arcgis-pro-24?sr=search&searchId=986e501c-2f01-4c79-995a-ab158ae1f53f&searchIndex=0
... View more
07-05-2019
01:37 PM
|
0
|
1
|
1175
|
|
POST
|
Normally field names cannot be changed but there is a geoprocessing tool for that: Alter Field (only supported in ArcGIS Pro). In ArcMap you need to create a new field, copy the data over using Calculate Field (as Dan suggests) and delete the old field once you have verified the data have been successfully copied. I should warn you that field names starting with a number can cause you major problems down the road https://community.esri.com/people/curtvprice/blog/2016/05/07/how-to-name-things-in-arcgis?sr=search&searchId=2e41b637-a244-44e9-84ad-8888868bbd37&searchIndex=0
... View more
07-05-2019
01:31 PM
|
0
|
0
|
2618
|
|
IDEA
|
This is implemented now implemented using the Calculate Geometry tool in ArcMap and Pro.
... View more
07-05-2019
01:21 PM
|
0
|
0
|
465
|
|
IDEA
|
Still want it. Maybe add "FIRST" and "LAST" to Cell Statistics? This is an alternate workflow to the Mosaic tools, which are limited in their support of the GP environment settings.
... View more
07-05-2019
01:19 PM
|
0
|
0
|
1617
|
|
POST
|
You can probably make progress with this using the Add Join tool in the other direction. Relates are not supported in Model Builder. See Select Related Data in Model Builder
... View more
07-05-2019
12:14 PM
|
1
|
2
|
3851
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-11-2021 01:26 PM | |
| 5 | 12-10-2021 04:58 PM | |
| 1 | 02-27-2017 09:30 AM | |
| 2 | 12-04-2023 01:05 PM | |
| 1 | 04-12-2016 10:17 AM |
| Online Status |
Offline
|
| Date Last Visited |
06-19-2024
12:10 AM
|