|
POST
|
If you have google earth, take the kml into google earth, make a new folder in google earth called plowref, then within that, open all the subfolders of your original kmz, and find your kmls, and move the kmls over you need(also you can make subfolders as needed), and change the names accordingly. Once done, have it export the plowref folder as a kmz, then load into arcgis online(there could be a way in AGOL, but I don't know what it is.)
... View more
08-07-2014
02:09 PM
|
0
|
0
|
744
|
|
POST
|
Another reason to use variables more effectively. If you had used your variable in ever place you spelled out its value, I bet it would have been caught a little sooner, since it would have been more apparent ot the eye that you were using the same string for each. Glad you got it working properly.
... View more
08-07-2014
01:20 PM
|
0
|
0
|
528
|
|
POST
|
yea, you are missing an 0 index on a listlayers by check 3 arcpy.AddMessage("check 3") #upLyr = arcpy.mapping.ListLayers(self.mxd, "Dimensions", dFrame)[0] upLyr = arcpy.mapping.ListLayers(self.mxd, "Dimensions", dFrame)
... View more
08-07-2014
12:11 PM
|
0
|
3
|
1377
|
|
POST
|
Both your original feature layer you create and your feature class have the same name, pointname ( or "route_one_point" + str(i)). I'm assuming you want to use your feature class you created, so perhaps give your feature class a different name than your feature layer and run again(say pointname + "fc"). It might be trying to run the tool off feature layer you made first, instead of the feature class with only one point. Also, since you already made a variable for pointname = "route_one_point" + str(i), hardcoding in "route_one_point" + str(i) again and again is a bit wasteful.
... View more
08-07-2014
10:17 AM
|
2
|
1
|
528
|
|
POST
|
Probably this should go in the python space. Python Timothy Hales, can you get this moved? Xander Bakker, you mind taking a look at this code?
... View more
08-07-2014
09:31 AM
|
0
|
11
|
1795
|
|
POST
|
Some layers only show at certain zooms, so I would check to see if your roads show at all zooms or between a minimum/maximum range. One easy way to see the extent of a layer(and make sure its visible), is to right click on it in the table of contents and select either zoom to make visible(if it only displays at certain ranges), or zoom to layer(if you get zoomed way out, use the horizontal arrows for previous/next extent to get back to your old zoom and extent). What is your source for your road data?
... View more
08-05-2014
02:52 PM
|
0
|
3
|
1561
|
|
POST
|
Ah, now this is where Dan gets to say I told you so. To be able to change your units with kernal density, I believe your data would have to be in the same projection as your data frame, otherwise it can't convert the units correctly(grayed out for me picking a layer using a different projection that dataframe, Timothy Hales you should have someone mention that in the help for that tool if it is true). Try using the project tool to put your data into NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet, and it should let you pick units. Oddly it worked out just making a new map document was the simpler option once you knew that you shouldn't use define projection in that manner, since that way the dataframe and layer had same projection. Please let me know if that works for you
... View more
08-05-2014
12:28 PM
|
0
|
6
|
1561
|
|
POST
|
Did you define projection of your data back to your original projection of GCS_North_American_1983 CRS, then change the dataframe projection to NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet? The reason what you did worked is after you projected the data into a new projection and added it to a new map document, the map document automatically set to that coordinate system and projection, which happened to have a units of feet, which is what you needed. Being within a geodatabase should have had nothing to do with it.
... View more
08-05-2014
11:50 AM
|
0
|
8
|
1561
|
|
POST
|
Hi Mike, It sounds like you need to change the projection of your dataframe or your data frame units, not that of your data. If you shapefile comes projected, then define projection would mess up its location and scale, define projection is only to be used when you have you have an unknown or incorrect coordinate system defined. If you need to project your data in a new projection, use the Project Tool. Your dataframe coordinate system and map units are defined by the first layer you add to your map, in this case GCS_North_American_1983 CRS from your shapefile, which the GCS_North_American_1983 GCS using degrees as its angular unit, hence your map unit being degrees. Try changing your dataframe coordinate system to one that uses feet as a unit., by going to View > Dataframe Properties> Coordinate Systems, Maryland state plane does use feet so that should work fine. You can check your map units under Data frame Properties > General tab, and can also change what the map display shows for units there. I would use define projection to put your data back in the correct projection, then change your dataframe coordinate system to Maryland State PLane. THere is no need to reproject the data into Maryland State Plane unless you want to, since ArcGIS projects data in a different coordinate system than that of the data frame on the fly, so it does it for you for display purposes. I hope this helps Dan Patterson, Melita Kennedy, got any other good advice for Mike here?
... View more
08-05-2014
10:09 AM
|
1
|
10
|
1561
|
|
POST
|
Hi J I would check out: Mosaic tool, ArcGIS Help (10.2, 10.2.1, and 10.2.2) Mosaic to New Raster ArcGIS Help 10.2 - Mosaic To New Raster (Data Management) Mosaic Datasets ArcGIS Help (10.2, 10.2.1, and 10.2.2) See which of those options would work best for you.
... View more
08-04-2014
08:50 AM
|
0
|
2
|
1569
|
|
POST
|
Also Matt, please be careful where you are posting questions, you posted this in the Australia GIS User Group, if you had posted more in the general GIS space it would be easier for you post to be found and answered.
... View more
08-04-2014
07:46 AM
|
0
|
1
|
1177
|
|
POST
|
Have you looked at using the Merge Geoprocessing tool? ArcGIS Help 10.2 - Merge (Data Management)
... View more
08-04-2014
07:29 AM
|
0
|
0
|
1177
|
|
POST
|
I mean subsequently its worked fine plenty of times, but that error was really weird. Found a few other comments about similar problems, not sure what would cause it though.
... View more
08-01-2014
03:52 PM
|
0
|
4
|
824
|
|
POST
|
I've always found Flow Direction to be a bit of a finnicky tool, sometimes it outputs the flow direction raster just fine with the correct values, others it makes w/b range symbology with values 0 - 230. Happened once during an exam, I was the only one who got the tool to have the right output, everyone else got the w/b symbology. I even re-did my exam after the fact, during the exam period and got the same w/b symbology as everyone else. Professor couldn't figure it out either, so he had to scratch that part of the exam.
... View more
08-01-2014
03:32 PM
|
2
|
6
|
2312
|
|
POST
|
You can use the Raster to Other Format tool to convert it to a GRID
... View more
08-01-2014
02:55 PM
|
0
|
0
|
2312
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-22-2017 08:58 AM | |
| 1 | 10-05-2015 05:43 AM | |
| 1 | 05-08-2015 07:03 AM | |
| 1 | 10-20-2015 02:20 PM | |
| 1 | 10-05-2015 05:46 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:23 AM
|