POST
|
There is no limitation for building locators with feature classes that reside within a feature dataset. Can you post your data and I can take a look? Brad
... View more
11-18-2010
07:45 AM
|
0
|
0
|
349
|
POST
|
That is a bug but we have fixed it locally already and plan on getting it into SP2. Brad
... View more
11-18-2010
07:30 AM
|
0
|
0
|
680
|
POST
|
Try creating the composite locator in a file folder instead. Brad
... View more
11-17-2010
07:06 AM
|
0
|
0
|
680
|
POST
|
Can you supply me with some data? I can take a look at it. Brad
... View more
11-09-2010
08:26 AM
|
0
|
0
|
398
|
POST
|
I guess you have a few options when it comes to getting the X, Y values from the geocoding service and each one has its pros and cons: 1. Use GP Geocode Addresses Tool within a model and post-process the geocoded featureClass to extract the X and Y values. Within the model you can make the output geocoded featureClass an "Intermediate" or even "In Memory" output so that it does not stay around after. 2. Use SOAP and the GeocodeAddresses method to get back a recordSet that will need to be post-processed to extract the X and Y values. You will need to pass WriteXYCoordFields with a value of "true" in the PropMods PropertySet that you pass in GeocodeAddresses. 3. Use SOAP and GeocodeAddress method to get back a PropertySet that contains the Geocoded Result of a single address and post-process the result to extract the X and Y values. You would also need to have WriteXYCoordFields in the PropMods PropertySet as in option 2. 4. Use REST and FindAddressCandidates method to geocode a single address and get multiple candidates that you will need to post-process and to find the best candidate and get the X and Y values from it. As you can see, there are many options but I am not 100% sure what your requirements and your workflow look like. I can give further direction if you can clarify your requirements and perferred workflow. Brad
... View more
10-28-2010
07:51 AM
|
0
|
0
|
814
|
POST
|
You are correct. You would need to use REST or SOAP and then you could process the result to get just the X and Y values. Why are you looking for just X and Y and what format would you like the result to be?
... View more
10-25-2010
08:33 AM
|
0
|
0
|
814
|
POST
|
You can get just x and y back if you use ArcGIS Online via REST. Brad
... View more
10-22-2010
08:26 AM
|
0
|
0
|
814
|
POST
|
Are you using IE8 to download the zip file? If so, do you have another web browser like Firefox or Chrome? There seems to be an issue with zip files and downloading from IE8. I can email it to you if you would like. Brad
... View more
10-12-2010
12:15 PM
|
0
|
0
|
595
|
POST
|
Would you be willing to share your data? I could take a look and see why it is failing.
... View more
10-11-2010
10:38 AM
|
0
|
0
|
680
|
POST
|
Try unzipping this locator xml file and replacing the one with the same name (make a copy of the original first though). This should solve your problem. Brad
... View more
10-08-2010
02:02 PM
|
0
|
0
|
595
|
POST
|
This is a bug. I can update the locator xml file and give you a new one so that it will work. I will post it when I am finished. Brad
... View more
10-08-2010
12:10 PM
|
0
|
0
|
595
|
POST
|
Tom, We had a few issues with projected data at 10 that are fixed in SP1. Brad
... View more
10-08-2010
11:39 AM
|
0
|
0
|
680
|
POST
|
Was your data projected? If so, there was an issue that is resolved for 10 SP1 with regards to projected data and side offset. As for storing a locator in SDE, it is not recommended because locators that are stored in a file folder are much faster because the locator is not slowed down by the database and SDE overhead. In previous releases, SDE was suggested because it was a "Server Side" geocoding process. This would help with performance compared to Desktop geocoding but there is no longer SDE server side geocoding. We now suggest ArcGIS Server for server side geocoding but it is still recommended to store the locator in a file folder even when hosted by ArcGIS Server. Brad
... View more
10-08-2010
11:28 AM
|
0
|
0
|
472
|
POST
|
Unfortunately no. Reverse geocode just returns the closest address to the point. Is the reverse geocoded intersection on the wrong side of the segment? If so, you could try this: 1. Geocode the address 2. Get the "From" and "To" values from that geocoded address 3. Geocode the "From" address and the "To" address 4. Reverse geocode the result of each. I.E. Address is: 101 S. Main St From is: 100 To is: 200 Geocode 100 S. Main St. and 200 S. Main St. Reverse geocode the results and one of the two will be the intersection that you want. You could even use the percent along to determine if the original geocoded address is closer to the "To" or the "From" address. In this case you would just need to reverse geocode just one of the two. Brad
... View more
07-28-2010
02:36 PM
|
0
|
0
|
324
|
Title | Kudos | Posted |
---|---|---|
1 | 07-15-2022 02:04 PM | |
1 | 09-24-2021 03:08 PM | |
1 | 06-07-2021 10:02 AM | |
1 | 05-19-2021 11:17 AM | |
1 | 04-19-2021 03:28 PM |
Online Status |
Offline
|
Date Last Visited |
05-30-2024
01:08 AM
|