POST
|
We are running 10.2.2 currently, but I massaged the locator to a point where it works for our requirements. When we do upgrade to 10.3+ then I'll respond with detail related to the locator.
... View more
04-17-2017
06:28 AM
|
0
|
0
|
156
|
POST
|
My apologies for not responding sooner. I revisited this project recently and put together a summary of items that this program needs, as well as a few details of how I went about it. Make sure that street names for both address points and street centerlines match as best as can be - this will capture more points to rotate Densify street centerlines - what I did was take our street centerlines (in SDE) and export this feature class to a shapefile as this densifies true curves, etc., then I exported this shapefile to a local FGDB Make sure to check field names in your address point and street centerline files - match them in the script to what you have in your address point and street centerline files The street centerline file had to be densified as the script could not handle true curves/arcs. I essentially dissected the centerlines into feature parts, then to vertex pairs (X,Y) for each part. From this the script calculates the midpoint of each feature part from the centerlines, calculates the distance from each midpoint to the current address point (using a cursor), then calculates the angle of the feature part. "90" was added to the angle calculation to get the address point angle to be perpendicular to the street centerline. (Edit - the reasoning for getting feature part midpoints and comparing them to address points is to find the closest feature part to the address point. Then, once the closest is determined, the angle of the feature part + 90 was transferred to the angle of the address point) Once I wrote the script and made the necessary edits to get it going, then I checked a few areas that I knew would not label like I wanted. Cul-de-sacs are not handled properly so I handled those separately (unless the street centerline was drawn to fit the entire circle of the cul-de-sac - see attached image), and dead ends were manually edited. All in all, I was able to rotate approximately 85% of roughly 50,000 address points we have with this script. Note: Python 2.6 was used within ArcGIS 10.0 SP 4 for this script
... View more
02-26-2015
09:52 AM
|
0
|
0
|
518
|
POST
|
ArcGIS 10.0 SP4 Build 4000 WIndows 7 32bit SP1 Locator and address reference file both stored in FGDB locally ---- I am using the "US Address - Single House with Units" locator (from here: http://forums.arcgis.com/threads/28535-Geocoding-Addresses-with-Apartment-Units) which we modified for our use (removed Street Type aliases when needed), and have come upon a situation that I hope I can find some guidance on. We have some street names (ex. - Parkway Dr) that match a Street Type alias (ex. - "Parkway"), so my initial action was to remove "Parkway" from the Street Type alias in the locator file. This was a temporary fix as a search using "Parkway" as the Street Type comes up empty (ex. - Village Center Parkway) compared to using the abbreviated version of "Parkway" (ex. - Village Center Pkwy) which finds a match. This has recently come up as we are refining our process to provide a more "catch-all" search for our users. Note: this could be done using a Composite Locator but a requirement of this particular project is that one is not used. My question: Is it possible to modify the locator to achieve the goal of having the same Street Name and Street Type within a single locator file? If so, would it be to modify the Street Name aliases or something else?
... View more
04-17-2013
08:14 AM
|
0
|
2
|
701
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|