Latest Contributions by NeilAyres

"BTW, Jason S. no longer works here" That's a shame.... ... View more

You could try the Pivot Table tool in Data Management / Table ... View more

But looking into the geographic_transformations pdf I see this. WGS_1984_(ITRF00)_To_NAD_1983 108190 CF 0.9956 -1.9013 -0.5215 0.025915 0.009426 0.011599 0.00062 WGS_1984_(ITRF00)_To_NAD_1983_2011 108354 CF 0.9956 -1.9013 -0.5215 0.025915 0.009426 0.011599 0.00062 WGS_1984_(ITRF00)_To_NAD_1983_CORS96 108151 CF 0.9956 -1.9013 -0.5215 0.025915 0.009426 0.011599 0.00062 WGS_1984_(ITRF00)_To_NAD_1983_HAR 108282 CF 0.9956 -1.9013 -0.5215 0.025915 0.009426 0.011599 0.00062 These are all the same thing. So now I am not so sure ... View more

The factoryCode for NAD83 (1986) is 4269. And WGS_1984 is 4326. So to list the available transformations I did this sr1 = arcpy.SpatialReference(4269) >>> sr1.name u'GCS_North_American_1983' >>> sr2 = arcpy.SpatialReference(4326) >>> sr2.name u'GCS_WGS_1984' >>> trans = arcpy.ListTransformations(sr1, sr2) >>> len(trans) 298 But a great deal of those 298 are composite transformations and I treat those with deep suspicion. So listing out only those without "+" in the name gives me : >>> for tr in trans: ...     if "+" not in tr: ...         print tr ...         WGS_1984_(ITRF00)_To_NAD_1983 NAD_1983_To_WGS_1984_5 NAD_1983_To_WGS_1984_1 NAD_1983_To_WGS_1984_4 NAD_1983_To_WGS_1984_3 NAD_1983_To_WGS_1984_2 So that first one might do want you need to do. ... View more

Well in ArcScene, you could extrude each polygon using the floor ht and the cumulative floor ht of those below it as the base level. Might be a little tricky to set up but certainly doable. ... View more

I agree with you Dan. Excel is widely used and misused. In the last 10 years as a private consultant, I have lost count of the number of times I have been given someone's "database", only to be confronted with a pile of spreadsheets! Perhaps I am getting a little old and tired now.... But the best way to handle these is to import into access with all the columns as correctly defined types. Then if necessary, go back and fix the spreadsheet input. ... View more

So do I.... ... View more

Are you saying that Copy Features doesn't work for you? As far as I am concerned a feature class in the "in_memory" workspace is still a feature class. Should copy out the disk easily. ... View more

Hmmm. Here we go again... "specifications of the database which is stored in Excel file". I know things are getting easier and easier, and I have seen the esri demo's of just "dragging your excel sheet on to the map" and magically all the data appears but.... Excel is an excellent bi tool and millions use it everyday. But it is not a database. ... View more

Well, in a 2d environment, there is no easy way round this other than to have specific layers representing to different levels of the data. Essentially you have multiple overlapping polygons covering the same 2d space. ... View more

I agree with Dan & Chris. Try to fix the spreadsheet first. But this does highlight the potential issues of using spreadsheets as a form of data input . You could also create a personal geodatabase (access) and use its excel import tools to bring in the data. There you can specify each columns data type. Anything not matching that will be converted to Null. ... View more

I have certainly seen in the past, people with a French set up, have difficulty opening csv's. All the decimal separators "." get replaced with ",". Which causes chaos in a csv. ... View more

Post the csv file here. I am sure someone will be able to identify the problem. ... View more

I though that in the US they use month/day/year... Always confuses me ... View more