Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About CraigCarsley
CraigCarsley
Frequent Contributor
since
07-04-2014
3 weeks ago
92
Posts created
31
Kudos given
1
Solutions
47
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(3 Idea Submissions)Latest Contributions by CraigCarsley
|
IDEA
|
-->
As it is now.... When Zoom to Selected Features is used for a single, point feature, the zoom scale is calculated as 1/20 the overall spatial extent of the layer. In cases where the feature class has hundreds of thousands of features (e.g. Address Points), this zoom function loses all of its value. I would like to see an option for a default, or maximum zoom extent setting in cases where I want to zoom to a single, selected, point feature.
... View more
05-05-2014
07:38 AM
|
19
|
6
|
4870
|
|
POST
|
I'm building a Streets Network Dataset, nearly identical to one that existed previously. Every time I try to build the dataset, I receive this error: [ATTACH=CONFIG]32267[/ATTACH] All of the Parameters and Evaluators for my Attributes are the same as the pre-existing Network Dataset. Is there anything else I could look at that this error might be referring to? Any input appreciated.. thanks!
... View more
03-18-2014
05:38 AM
|
1
|
0
|
4565
|
|
POST
|
Thanks for the response, Joe! I spent a bit more time looking at my roundabouts yesterday, and I think the solution is actually much simpler. I realized that my streets were intersecting at as endpoint and vertex point, rather than endpoint and endpoint. I made some changes, and have yet to actually test this solution, but I'm fairly confident this was my problem. It seems obvious, in hindsight, but sometimes the simple fix is the most elusive!
... View more
03-13-2014
10:26 AM
|
0
|
0
|
928
|
|
POST
|
I'm having a problem geocoding roundabout intersections in my Streets dataset. I think the reason could be that the two roads actually intersect twice because of the way the roundabout is drawn. Has anyone come into contact with this? Is there a better way to portray a roundabout intersection that will allow a geolocator to find it? [ATTACH=CONFIG]32157[/ATTACH]
... View more
03-12-2014
12:27 PM
|
0
|
2
|
1052
|
|
POST
|
I think I've figured this out... I've included the MUNICIPALITY field in my Validate_Attribute_Lookup method. It seems that the Attribute Assistant will add a trailing space to a Street Name when the MUNICIPALITY field value is blank. So, in cases where the MUNICIPALITY was not calculated prior to the method running, I see the white space. To resolve this, I set a higher-priority, Intersecting_Feature method to confirm the MUNICIPALITY directly prior to running the Validate_Attribute_Lookup. It has been working fine, ever since.
... View more
03-10-2014
05:47 AM
|
0
|
0
|
574
|
|
POST
|
Has anyone noticed that the Validate_Attribute_Lookup method seems to add a space to the end of an attribute value? When I use it to validate a street name from the MasterStreetName table, it adds a trailing space to the value. I don't believe this was happening before I started incorporating the MUNICIPALITY field as part of the same method. I've eliminated the possibility that the space exists in the MasterStreetName table. Anyone have any thoughts on this?
... View more
02-21-2014
10:28 AM
|
0
|
1
|
828
|