Latest Contributions by MelitaKennedy

I should have asked this already--can you post the extents of one of these CAD files? I have heard about DGN files having a scaling factor. I don't remember off-hand what it's called. But maybe I can at least identify what's happening when I see the extent values. Thanks, Melita ... View more

Does the CAD data show up with a defined coordinate system? Or is it listed as unknown? If it's known, try redefining it to the other unit. Melita ... View more

So Johnson County? The control points are in US survey feet then. 50 miles southwest makes me think the rest of the data is in meters instead. Anyway, that there's some feet/meters issue occurring. Melita ... View more

Looking for a smallish dataset, I downloaded the Badajoz one. There's something in the WKT of the coordinate reference system that we're having trouble understanding, so it comes in with an unknown coordinate system. Use the define projection tool, or the data's property page in ArcCatalog to change it to projected coordinate systems, continental, europe, ETRS 1989 LAEA. Then you should be able to reproject it with the Project tool or on the fly in ArcMap. (no time to check what's the problem right now; will try tomorrow) Melita ... View more

Hi, That dataset was originally built in ArcInfo Workstation where the FIPS code was the way to specify a state plane zone. It hasn't been updated to include any well-known IDs, for instance. I'm attaching a list of all state plane zones on all supported geographic coordinate systems and units (meters, US survey feet, Int'l feet) with their well-known IDs. Melita ... View more

I have a project that gave me a table of xy values in NAD27, Pennsylvania State Plane (Foot). They would like the coordinates converted to NAD83, PA State Plane (Foot). I need some one to check this for the correct steps. This is the process that I did: Open an MXD file and set the projection to NAD27, PA State plane (foot) Bring in the table from Catalog Right click on the table, then Display XY data, and set the the appropriate x and y fields. Export the data to change it from and event to a shapefile/feature class in NAD27 Open an MXD file that is set to NAD83, PA State plane (foot) Import the previously created shapefile. Export the shapefile ensuring that the projection for the export is the same as the data frame (NAD83) and NOT the source (NAD27). Create two fields in the attribute table for new x and y values Calculate the geometry of these field using the appropriate data. These values are now in the NAD83, PA state plane (foot) but they are slightly different than another check that I have (from the client). Can anyone point me in a different direction or confirm my method? Thanks I think this thread should be moved to the general Desktop queue because you're not using ArcObjects. If you agree, I'll move it. Anyway, the order looks good although I have two comments. Make sure that the geographic (datum) transformation is set to convert between NAD 1927 and NAD 1983. Open data frame properties, Coordinate System tab, and click the Transformations button. In the top box, make sure NAD 1927 is selected. The middle pull-down should list NAD 1983. The transformation pull-down should have NAD_1927_To_NAD_1983_NADCON. If the values are still off (how much?), ask the client if they really want a more recent re-adjustment than NAD 1983 (1986 aka the original). It's possible they want something like NAD 1983 HARN, or later. The 2nd comment is that you don't need to use two documents. Once you have the shapefile/feature class, change the data frame's coordinate system to the coordinate system you want to use and export the data the same way. Melita ... View more

Very rough guess/estimate based on the image. false easting: -36000 meters false northing: -71000 meters ... View more

The transformation parameter is 'optional' because it is unnecessary when the input and output geographic coordinate reference systems are the same. When they are different, the parameter becomes mandatory in the Project Tool. If the output coordinate system is WGS 84 (latitude-longitude), you don't need to project it. If the needs to have a different version of WGS 1984 (name is different), use the Define Projection tool instead. That will update the 'metadata' and not change the coordinate values. Another method is add the data to ArcMap. Set the data frame's coordinate system to what you want to use. Right-click the layer in the table of contents and select data, export data. In the dialog, choose to use the data frame's coordinate system. Melita ... View more

Hi, The laszip.exe file is having problems with the spaces and possibly the parentheses in the path to your input file. Try moving the file to someplace like c:\temp (may have to create it) and try the tool again.  Melita ... View more

I often have that problem too--a link to a blog entry goes to the main page instead. A second try will often work. Leo's link works for me. The blog post was on February 11th, and is now on page two if you go to the main page. Anyhow, the only possibly relevant thing I see in the post is this: Custom Roles The existing organizational roles of Administrator, Publisher, and User are being complemented by the addition of custom roles. Custom roles provide a more granular way to control member privileges, enabling you to tailor unique roles to suit your needs. Leo, is that what you were talking about? I haven't used AGOL beyond pulling public content into a map, so I can't help on the problem. ... View more

Very true. I'm not sure I can figure this out late on a Friday afternoon. Possibly a central meridian/longitude of origin that's at 180? But misread as 0? I see references to ground track Mercator "projection", but it looks like this data has already been converted from that. Melita ... View more

I'm not sure what to do about it, but I've seen other data from NGS (part of NOAA) that uses positive west longitude values. That would fit with this data. Does the data look flipped too? (I know it's probably hard to tell). Melita ... View more