POST
|
Hi Jennifer, I did somewhat, but it's not that straightforward, I had to export from AGO the feature layer that contained the points that had photo attachments as a file geodatabase, then using an export attachments tool (developed in-house) export the attachments as photographs and these photos had EXIF data, I verified this by generating points by using the 'Geotagged Photos to Points' tool.
... View more
08-30-2016
01:38 PM
|
0
|
1
|
699
|
POST
|
What is the purpose of having 600 copies of a point feature, sounds very inefficient?
... View more
07-21-2016
11:49 AM
|
0
|
0
|
170
|
POST
|
The latest release of Collector on iOS promises this feature, but when I tested it on a project (project was uploaded to AGO prior to the app update) no EXIF data is recorded. Is there anything I have to do in AGO or Collector to have this feature enabled? Thanks, Brian
... View more
07-21-2016
11:47 AM
|
0
|
5
|
2460
|
IDEA
|
This falls under the category of many features that should be available with at most a Pro license. GIS is all about data after all and to be hamstrung with a static table is ridiculous.
... View more
06-08-2016
08:11 AM
|
0
|
0
|
661
|
POST
|
I have a mapbook (Data Driven pages) derived from a strip map for a pipeline project. As it's a strip map the rotation of each page varies depending on the orientation of the pipeline feature, for each page I have a feature class of lines indicating linear intersections (roads, rail, etc.). These lines appear vertical in each rotated page and have an associated horizontal Maplex label that is set to offset to the right or left of the line, along with an associated callout arrow and line. In ArcGIS 10.2 this setting displayed as expected, but in 10.3.1 the vast majority of labels are not offset and are placed horizontally on the mid point of the line. The offending labels also don't stack even if that setting is checked. I initially thought I may have missed a setting in my current mxd project file, but when I open an older mxd, with identical labeling, that too has the same issue and leads me to believe the issue is related to 10.3.1. Anyone else have this issue and have any workarounds? How the labels used to display (10.2): How they display now (10.3): Thanks, Brian
... View more
02-02-2016
11:40 AM
|
0
|
0
|
1943
|
POST
|
I experienced a rather worrying crash upon opening an MXD that had data driven pages setup. The MXD had a layer driving the mapbook that had a definition query to filter only certain pages and also had page definition queries set up for several layers to display only matching records of a different unique ID field. Turned out I had opened a different MXD that used the same data driven setup, same Layer and same unique field, but had changed the unique field contents from a simple ‘yes’ to ‘priority site’. When I opened the other MXD it crashed automatically, presumably because its definition query and/or page definition queries were looking for records in the mapbook layer that contained the value ‘yes’ and could find none. To solve the issue I had to copy the mxd to a subfolder in Windows Explorer, which broke the relative path links, remove the definition query on the mapbook layer, relink all the data sources and update the definition query to find the ‘priority site’ records. I’m not sure if this is a repeatable crash, but be wary of changing definition query values that may impact other MXDs. Anyone else experience this issue?
... View more
05-11-2015
08:12 AM
|
0
|
0
|
2805
|
POST
|
Another option: for features with elevation data (ZM) you can use the Geometry Calculator to fill in a field with the elevation values.
... View more
03-23-2015
12:35 PM
|
0
|
0
|
1236
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|