Latest Contributions by LucasDanzinger

Perhaps you could create a topology on that line feature with a Must Not Intersect rule. This rule "Requires that line features from the same feature class (or subtype) not cross or overlap each other." Validate the topology, then add it to ArcMap, and it should highlight all of the locations where the line is intersecting itself. ... View more

This is a tough one, because it is hard to determine how the employee numbers are distributed throughout the grid polygon (i.e. are they spread equally across the polygon, are should some areas of the polygon be weighted differently than others?). Off the top of my head, the only thing that comes to mind is creating a custom BDS layer in the Business Analyst Desktop extension. You would use the Custom Data Setup Tool and select the proper apportionment method. You could then create your trade areas of 1 mile buffers around your cities and use the Spatial Overlay (Append) tool to grab the values from the Grid. Then, depending on what apportionment settings you have set up in BA, you should see different numbers. The Advanced Apportionment Settings article discusses the different styles available. Unfortunately, all of this will only be doable with Business Analyst desktop. That's not to say there may not be some other way to get a similar result using ArcGIS without any extensions... ... View more

Hi Mike, It's hard to say what is going on without looking at your data, but perhaps the wrong coordinate system is defined. This would mean it is set as a certain coordinate system in the properties, but it really isn't that coordinate system. For example, you could have data gathered in WGS 1984 and then go in and Define the Projection as NAD 1983 UTM Zone 15N. That doesn't mean that the data are actually NAD 1983 UTM Zone 15N, rather it means that you simply gave your data that label. You only want to use the Define Projection tool when either your data do not have a coordinate system defined (gathered the data in WGS 1984 and it says Undefined in the Source Tab) OR if someone defined it incorrectly (defined it as NAD 1983 UTM Zone 15N when it is WGS 1984). The Project tool will actually physically reproject the data from one coordinate system to another (and not just change the label as Define Projection does). For example, you could use it to project your data from WGS 1984 to NAD 1983 UTM Zone 15N. As far as why your data aren't lining up, it might be that the incorrect coordinate system is defined. This would be my best guess, being that you said the GCS and PCS are listed as the same. You could either try to gather the correct information from the data source, or read through the "Identify the spatial reference, projection, or coordinate system of data" KB article. An important thing to check (which is highlighted in the article) is how many digits are to the left of the decimal place for the extent in the Source tab. ... View more

I'm not sure why the v button is not working, but you can either double click the feature with the Edit tool or click the feature once with the Edit tool, then click the Edit Vertices button on the Editor Toolbar. ... View more

Hi Tim, Just wanted to add that it really doesn't matter if you set the format as numbers in Excel. ArcMap disregards this and scans the first 8 rows to determine field type. The 5th bullet point in the Understanding how to use Microsoft Excel files in ArcGIS article explains this: "Excel does not enforce field types for values during data entry like standard databases do. Therefore, the field type specified in Excel is not used in determining the field type exposed in ArcGIS. Instead, field type in ArcGIS is determined by a scan of the values in the first eight rows for that field. If the scan finds mixed data types in a single field, that field will be returned as a string field, and the values will be converted to strings." In your case, the issue is field headers, but another common issue with displaying XY data is that ArcMap is setting the field type as String because of mixed data types. ... View more

Google Earth and ArcGIS Explorer use WGS 1984, so it is a good idea to reproject your data to WGS 1984, being sure to use the proper geographic transformation. It's hard to say why it lined up correctly in ArcMap originally, but it depends on what reference data you were using (and what coordinate system it was in) as well as what you had the data frame coordinate system set to. To keep things simple, if you want to display the data in Explorer or Google Earth, you might want to think about reprojecting to WGS 1984. ... View more

I don't think this is possible, but I can't find any documentation that specifically says that it cannot do this. This thread discusses this and it seems like the general consensus is that you can't do this in Explorer Desktop, as it is just a free application. However, as Cody suggests at the end, you might be able to use the ArcGIS Explorer SDK to make some tools that would do this. ... View more

Hi James, Interesting find. I logged the following bug for this behavior: NIM081730 ArcGIS Explorer Online color ramps duplicate colors with groups of 6 or more The workaround for now is to go to the details of the duplicated colors and modify them to be darker or lighter there. Luke ... View more

You're definitely going to want to get the coordinate systems defined. If no one in your organization knows what they are in, you can work through the following knowledge base article: Identify the spatial reference, projection, or coordinate system of data. If you plan on just working with what you have, you can just merge these features together in Editor. 1. Start Editing 2. Use the Edit tool to select all of the grids you want to merge (7E1, 7E2, 7E3, 7E4). You can either drag a box or click each and hold shift. 3. Click the Editor drop down and select Merge. 4. Select the feature that you want the merged output to inherit the attributes from Either that, or if there is a common attribute between 7E1, 7E2, 7E3, 7E4, you could use the Dissolve tool. ... View more

Just to be certain, they aren't just pasting on top of each other, are they? That's what happens for me and then I need to manually move them in order to see that there is a new copy. It might worth a try adding it to a new MXD and test it there. MXDs can become corrupt from time to time. ... View more

Just like MXDs, you are going to want to stay current on the version of PMFs you are using. I suppose you could get Publisher 9.3 (as suggested above), but being that ArcReader is free, I would just download version 10 of ArcReader, and continue working with ArcPublisher 10 on ArcGIS 10. ... View more

As Michael is suggesting, if you have a polygon shapefile/fc of Greenland, you can use the Feature Vertices to Points tool. If you do not have a Greenland polygon, try searching through ArcGIS Online for administrative boundaries, select only Greenland, and export it out to an individual shapefile for you to run the tool with. You will, however, need ArcInfo to use the tool. ... View more

If you follow the workflow of: Make Feature Layer > Select layer by Attribute > Delete Features, it should work. All the make feature layer is doing is making a temporary object for model builder to use. It is then performing a select by attribute to the layer (which is your original data) and deleting all selected features. ... View more