|
POST
|
Hi See if you can use this: http://www.arcgis.com/home/item.html?id=9398bd2232cb4c8490b0b05015364d28 Regards
... View more
02-14-2013
06:05 AM
|
0
|
0
|
2577
|
|
POST
|
Hi NormalAddress is under the Top level Elements section. Regards
... View more
02-07-2013
06:08 AM
|
0
|
0
|
1152
|
|
POST
|
Hi Try this: Look for the NormalAddress element, this is under the Top level elements. Add an alt like this: <alt> <elt ref="FullStreetName" weight="60" separator_list=".,;-"/> <elt ref="House" weight="50" pre_separator="required"/> <elt ref="OptionalUnit" weight="0"/> </alt> Regards
... View more
02-05-2013
06:24 AM
|
0
|
0
|
1152
|
|
POST
|
Hi This will take some unravelling; as we don't have ArcGIS 9.x installed here I'll need to rely on you to examine your own files. If you open your USAddress.lot file in Wordpad and scroll down to the line that looks something like this: IntFileSTN = us_intsc.stn Open the .stn file in Wordpad and see what the line starting STANDARDIZE has as the argument. I'll say it has "us_intsc" as the argument. It may be different on your system. This means a file named "us_intsc.cls" is the classification file used as the single view of the world of intersection address tokens. Open the .cls file in Wordpad and look for lines ending in a letter "D". These are the street direction tokens. Whichever file you are using will have an entry for East that looks like this (spaces are not important): EAST E D This means that any time an East token is found by the parser it always outputs it a a single letter E. If you edit the line to be like this: EAST EAST D Then the word EAST will be output by the parser. Make this edit and rebuild your locator and see how it goes. Regards
... View more
01-30-2013
06:14 AM
|
0
|
0
|
1828
|
|
POST
|
Hello Jamal Try the US One Range style for your purposes. Developing a new address style is a very challenging task, if you can use an existing style it will save a lot of work. Regards
... View more
01-28-2013
07:50 AM
|
0
|
0
|
3326
|
|
POST
|
Hi All When looking at these GML issues we find that many files are not valid GML. There can be many reasons, for example: http://fmepedia.safe.com/articles/Error_Unexpected_Behavior/GML-geometries-not-read You can test any GML/XML with the XMLValidator. You can test GML using the schemas that come with Data Interop in: C:\Program Files (x86)\Esri\Data Interoperability (x86)\xml\schemas\schemas.zip\gml If you want to test the validity of your files please open a support incident and we'll take a look. Regards
... View more
01-25-2013
01:16 PM
|
0
|
0
|
2348
|
|
POST
|
Hi NZTM uses GRS80 datum, the XYZ transformation between that and WGS84 is 0,0,0, so null. There must be some other issue here, maybe a support call is in order. Regards
... View more
01-22-2013
06:48 AM
|
0
|
0
|
3247
|
|
POST
|
Hello Tristanto You could export the model to Python and hard code all the parameters you require. ModelBuilder does not have a locking mechanism. Regards
... View more
01-14-2013
01:18 PM
|
0
|
0
|
677
|
|
POST
|
Hello Use the Data Interoperability extension, create a new Spatial ETL tool with a GPX writer as output and connect your field of interest to the Waypoint name attribute. Regards
... View more
01-14-2013
01:13 PM
|
0
|
0
|
682
|
|
POST
|
Hello J Yes, if you write a standalone Python script that imports arcpy and the Data Interoperability extension and imports/adds your toolbox, you can execute the tool from a command shell. This is the same workflow as any other geoprocessing functionality called from a command line. Regards
... View more
01-14-2013
01:01 PM
|
0
|
0
|
626
|
|
POST
|
Hello Derek In your ArcMap session, set the Geoprocessing Options menu option to overwrite the outputs of GP operations to true. Regards
... View more
01-14-2013
12:59 PM
|
0
|
0
|
741
|
|
POST
|
Hello Chris If you want to preserve your attribute schema within a KML file, use the Data Interoperability extension to export to KML (the Quick Export tool will do it). The core tool Layer to KML will output a single description field with HTML, which cannot be imported back into ArcGIS with any schema. Regards
... View more
01-14-2013
12:55 PM
|
0
|
0
|
566
|
|
POST
|
Hello Adam There is a known limitation when running Quick Import as a background process; it cannot be the first tool run in background for your current session. Regards
... View more
01-14-2013
12:46 PM
|
0
|
0
|
984
|
|
POST
|
Hi ArcPy recordsets (and featuresets) can be converted to and from JSON using the .JSON and .AsShape methods, so that part is easy, within a script or model embedding a script. You can geocode a recordset (treat it like a table in other words) or load it into an in_memory table to geocode it. If you are using ArcGIS Online there is a REST endpoint for batch geocoding, but don't go down that track unless you need to. http://resources.arcgis.com/en/help/arcgis-online-geocoding-rest-api/ Regards
... View more
01-08-2013
06:54 AM
|
0
|
0
|
1626
|
|
POST
|
Hi Scripts running out of process in ArcGIS that call the Data Interoperability extension must check the extension out: arcpy.CheckOutExtension('DataInteroperability') Regards
... View more
01-07-2013
06:45 AM
|
0
|
0
|
1033
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 8 hours ago | |
| 1 | 8 hours ago | |
| 1 | yesterday | |
| 4 | 05-28-2026 05:58 AM | |
| 1 | 05-15-2026 06:54 AM |
| Online Status |
Online
|
| Date Last Visited |
5 hours ago
|