|
POST
|
When geocoding against a line, the process simply interpolates the location (x,y) of the given address based on the range of addresses for a given street and the length of the street. As a very simple example, suppose you have a street called Main St and the 100 block is address ranged 101-199 on the odd side and 100-198 on the even side. This section of Main ST is 300 meters long. The address of 150 Main ST should fall on the even side of the street, at just about the middle of the block (approximately 150 meters from the intersections). Could be that the house is actually on the odd side of the street and at the far end of the block. This can lead into a discussion of accuracy and precision; locating 150 Main St at the half way point is accurate; if you use GPS'd address points, they would much more precise as you would have occupied the driveway at 150 Main ST and recorded the actual x,y. You have to decide how precise your data needs to be and the associated costs with that level of precision....
... View more
06-10-2013
12:25 PM
|
0
|
0
|
1452
|
|
POST
|
very interesting. but how do you actually use that attribute when building the network? The docs say that One Way restrictions have to be attributes/expressions that evaluate to Boolean. I thought that meant a road was either one way or two way. Unless you are using this in some other way like Connectivity maybe? See attached jpeg....
... View more
06-05-2013
11:28 AM
|
0
|
0
|
1547
|
|
POST
|
I use an attribute called.... Oneway. (short integer, nulls not allowed) It has three values: 0 (zero) which means there is no travel restriction (two way traffic flow); 1 (one) which means traffic restriction to the same direction of the polyline; and 2(two) which means travel restriction to the opposite direction of the polyline. In my geodatabase, the default value is 0 since the majority of new roads are two way.
... View more
06-04-2013
06:13 PM
|
0
|
0
|
1548
|
|
POST
|
You could also create a topology and check for dangles. You get a lot of 'false positives' with dead end streets, but depending on your data, it can be a first start. Using network analyst, you can create service areas and look for disconnects there as well.
... View more
06-04-2013
03:29 AM
|
0
|
0
|
2061
|
|
POST
|
You might want to run a quick search in the geocoding forum using 'CANADA' as a key word. There have been several discussions on this subject in the past.
... View more
05-27-2013
03:09 PM
|
0
|
0
|
1273
|
|
POST
|
Or use the caveman simple approach and select <your_field> is null. Then use the field calculator on the selected set such that <your_field> = Your_Specified_Value.
... View more
05-23-2013
07:01 AM
|
0
|
0
|
1877
|
|
POST
|
You've got to ask yourself the question: Which 85 is this tool supposed to carve out? I suggest you build yourself a polygon feature class based on a sub-area of your study plot. Edit it until you get the 85 acres you want and use it to erase or union with the original.
... View more
05-16-2013
09:17 AM
|
0
|
0
|
623
|
|
POST
|
Perhaps Jay, Patrick or one of the other ESRI NA guys can weigh in here....
... View more
05-15-2013
11:10 AM
|
0
|
0
|
3253
|
|
POST
|
That being the case, the only significant difference I notice is to the lower right side of you image. Can that be explained with the cut off time?
... View more
05-15-2013
09:44 AM
|
0
|
0
|
3253
|
|
POST
|
The illustration provided only shows one; where is the difference?
... View more
05-15-2013
08:53 AM
|
0
|
0
|
3253
|
|
POST
|
I think you'll want to use a relate or relationship class as a 1(polygon) to Many (crime incidents). First and foremost I reccomend getting the data out of a spreadsheet and into a geodatabase table. Spreadsheets are okay.... If you are doing your taxes... As long as your city codes have a consistent value [that is, spelled the same way] between the polygons and incident data, use it with which to create the relationship. You can use a Many to One join; but that may be a little cumbersome if you are planning to map the data.
... View more
05-14-2013
07:09 AM
|
0
|
0
|
1278
|
|
POST
|
I have a shapefile of LA county with a single polygon for each city. I also have a table with x,y data that has been represented and the city names for each event match with the city names for the polygons. So how can I combine the point data to the polygons to do polygon analysis? Trying to join doesn't work since there are several events for each city and only one input for each city Are you trying a tabular join or a spatial join? Your post is a bit confusing. Try these steps: add your xy data as an event export the event data to a point feature class be sure to add the newly created feature class ( you may want to remove the event) right click on your polygon feature class and select join you are given several options of what you want to track in the resulting polygons What exactly is the polygon analysis you are trying to accomplish?
... View more
05-14-2013
03:44 AM
|
0
|
0
|
1278
|
|
POST
|
From the 9.3 help pages: 000042: Failed to create the address locator. Description: The address locator cannot be created. Solution: Check that you have Permission to write to the disk or database Enough disk space for the address locator you tried to create Valid network or database connection Valid geocoding rule files Valid address locator style You might want to avoid placing the locator in the geodatabase; it's recommended practice to just keep it in a regular directory. Permissions can always goof on you: make sure you have what you need (Read/Write).
... View more
05-12-2013
04:50 PM
|
0
|
0
|
1082
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-11-2018 07:12 AM | |
| 1 | 05-17-2021 11:18 AM | |
| 1 | 06-29-2021 11:42 AM | |
| 1 | 07-05-2012 07:49 AM | |
| 1 | 09-03-2016 06:16 AM |
| Online Status |
Offline
|
| Date Last Visited |
05-19-2026
11:56 AM
|