|
POST
|
I am still having issues. I am trying to geocode five years worth of data with roughly 20K records in each year, working for ArcGIS Desktop 10 Service Pack 5 (ArcInfo license). I have tried the 10.0 North America Geocode Service and 10.0 US Streets Geocode Service. When I try to geocode from the csv file I get the message "There was an error trying to process this table" with no further information. When I try to geocode from after converting to a geodatabase table I get a variety of different error messages, including "Attempted to read or write protected memory. This is often an indication that other memory is corrupt" or "No resource could be found at that address" But I don't understand because I got two years of data to work. There is nothing different about the remaining three. Any chance you can provide one of the csv's that bail out?
... View more
08-08-2013
12:37 PM
|
0
|
0
|
4618
|
|
POST
|
And you the actual routes or you're going to model them? Sorry to keep asking questions. If you know the routes, like 125 people go north on a street, then east on b street, south c street and west on d street you could assign some kind of values to those streets. Modeling would require network analyst, and a good set of roads.
... View more
08-07-2013
02:59 PM
|
0
|
0
|
2183
|
|
POST
|
What is it you want to map and/or analyze? Is it traffic volume? Is it bike routes? Is it the traffic volume on bike routes? Is it the number of the 1,000 bikers that take the same route? Or some combination of all?
... View more
08-07-2013
01:08 PM
|
0
|
0
|
2183
|
|
POST
|
I think your problem lies in the fact that E is often considered as a suffix direction and you are getting dinged for not having E in the suffix_direction field in your street data; the locator is looking for it but since it's not there it does not match. Try this: try to geocode that address without the E on end of it. My guess is you'll get a partial match on all the streets including the problem child.
... View more
08-07-2013
08:47 AM
|
0
|
0
|
1882
|
|
POST
|
Does this mean that all other mappers that are still using 9.2 will lose the ability to connect to the database because it will be upgraded to 10.0? In a word, yes.
... View more
08-02-2013
12:17 PM
|
0
|
0
|
552
|
|
POST
|
Perhaps you could also provide the version of software you are using and service pack level. I found a something similar with a google search. You might want to take a look at this.
... View more
07-30-2013
11:04 AM
|
0
|
0
|
2205
|
|
POST
|
Interesting. Where might I find said "ArcSDE for Microsoft SQL Server Express Wizard"? I downloaded SQL Server Express myself through Microsoft so I never used any wizard from ESRI. Should be on your desktop install disc....
... View more
07-30-2013
10:58 AM
|
0
|
0
|
894
|
|
POST
|
My suggestion is you start with the basics: work through the geocoding tutorial and develop a good understanding of the available locators and then consider your customization ideas.
... View more
07-25-2013
06:50 AM
|
0
|
0
|
694
|
|
POST
|
Are you suggesting converting an excel spreadsheet into a coverage? I'm a little confused by that if you are. I routinely geocode hundreds of thousands of addresses without any bail outs, seizures, or other malfunctions. I'm sticking with my story; excel is a great spreadsheet. I use it all the time to bill my clients and pay my taxes. When it comes to actually making my living, I use data bases. Back in the day Info ruled as a data base; that was then this is now.
... View more
07-24-2013
05:58 AM
|
0
|
0
|
4618
|
|
POST
|
I have a dataset of about 32000 addresses I have been trying to geocode. Time after time I keep getting the same error message, the one in the title of this thread. I have changed names of columns, tried making it a dbf, tried removing everything but the address information, splitting the data in half to make it smaller. Regardless of what I do i get anywhere from 1%-5% done and I get the error. Any ideas? Thanks. As long as you've made all the field names one word with no special characters, you should be good there. (Typically it'll bail out right at the get-go if thats the problem.) My guess is somewhere you've got a <null> value in on of your address records. Personally, I'd make sure the address table is within some flavor of geodatabase. That way all your data and results can be in the same place.
... View more
07-18-2013
11:36 AM
|
0
|
0
|
4618
|
|
POST
|
This has worked for me. It creates a a new table by selecting from one table INTO another. It's the between statement you want. Your mileage may vary and sorry, no tech support is available... SELECT Field1, Field2 Field3, Field_ETC_ETC INTO db.dbowner.tablename2 FROM db.dbowner.tablename1 WHERE (YourDateField BETWEEN '2013/03/19 00:00' AND '2013/06/10 00:00') ORDER BY YourDateField Here is a great site for learning sql expressions
... View more
07-17-2013
07:10 AM
|
0
|
0
|
1093
|
|
POST
|
Curious that this is posted in the Search and Rescue forum; I'm glad when I broke my leg in a back country ski accident that my political affiliation didn't come into play for my rescue!
... View more
07-15-2013
08:06 AM
|
0
|
0
|
2735
|
|
POST
|
Not gonna happen. You can't traverse what doesn't exist.
... View more
07-15-2013
04:33 AM
|
0
|
0
|
1574
|
|
POST
|
Here's a little tidbit that came my way. If you try this, be sure to follow the line that mentions backing up your original file... Copy your file C:\Program Files (x86)\ArcGIS\Desktop10.2\Locators\USAddress.lot.xml to a backup copy. Start editing it with an XML editor. Look for lines in the grammar section having this element (below), you are looking for entries in the multiline_grammar section under the supportsIntersections alternate and further down under the FullIntersection element. <elt ref="intConnector" weight="40"/> Replace these two entries with this: <elt ref="intConnector" weight="40" pre_separator="optional" post_separator="optional"/> Create new locators using the modified style. Hold your breath hoping it works. If not revert the changes out;don't expect miracles.
... View more
07-12-2013
12:30 PM
|
0
|
0
|
695
|
|
POST
|
Bridged intersections... Sort of an oxymoron don't you think? An over-pass or under-pass isn't an in intersection; at least, I wouldn't want to model my data as such. For example: Main St doesn't Intersect I-80, the on/off ramps do. Main St intersects the on/off ramps and passes over I-80, right? What if you create a point feature class of your over/underpasses and create a naming convention for your users to follow? Be careful about how many different aliases you create. That will become a data maintenance night mare for you. (I like to call it this, but he likes to call it that, and so & so likes it called something else, and oh yeah, Billy Bobs great grandfather used to call it this...) I go two deep; tops. You fail mention software version, but I've always indexed the join item in both the feature class AND alternative name table.
... View more
07-11-2013
03:41 AM
|
0
|
0
|
695
|
| 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
|