|
POST
|
If you have the stop signs in the form of a point feature class, could you use them as an added cost barrier? I agree, creating turns for that many potential stop signs would be a maintenance nightmare! Hope this helps.
... View more
04-10-2012
12:23 PM
|
0
|
0
|
604
|
|
POST
|
Hi all, I have a book "GISTUTORIAL1 Basic Workbook for ArcGIS 10" by W.L. Gorr & K. S. Kurland. I am working on Chapter 7 Geocoding and I am doing Tutorial 7-4 Correct street reference layer addresses =>Create an address locator for CBD Streets (on Page 248), Geocode clients' addresses to CBD Streets (on Pages 248-249), Identify a problem street segment record using Review/Remartch Addresses (on Pages 249-250), Edit a street record (on Pages 250-251), and Rebuild a street locator (on Page 251) - Step 3: right-click PghCBDStreets and click Rebuild. I got the following error: Rebuild Address Locator - Can't rebuild address locator (see the attched file). Please kindly help and tell me where I can find the root of the problem and how to solve this problem. Thanks, Scott Chang Just a guess, but you may have to either quit ArcMap or ArcCatalog and rebuild in what ever you leave open. To be sure, close everything, open ArcCatalog and rebuild there.
... View more
04-10-2012
07:47 AM
|
0
|
0
|
760
|
|
POST
|
I've always found sdemon -o kill -t <pid> to be my friend when it comes to users who can't remember when its mainantence time... :cool:
... View more
03-29-2012
07:44 AM
|
0
|
0
|
2285
|
|
POST
|
Any idea why this doesn't seem to work with the Spatial Join tool in the toolbox? I'd like to script this, but can't seem to figure it out. Basically, I have a bunch of points and a few polygons. I just want to assign a value to a field in the point feature class based on the polygon the point happens to be within. Spatial join appears to only join each target feature once? Oddly, the JOIN_FID field is correct for all of the points, but I get no metadata from the polygon?!? (I just get a bunch of nulls) Not sure what you're after here. I just joined a county wide feature class of mile markers (target) to a county wide feature class of city polygons (join features) and got my desired/expected results; a point feature class of all 231 mile marker locations,each with the appropriate city information attached to them. (Along with the attributes from the original point feature class.) Also, what do you mean about 'metadata from the polygon'?
... View more
03-29-2012
07:39 AM
|
0
|
0
|
3915
|
|
POST
|
I'm not familiar with geodatabases and feature classes yet. I have worked almost exclusively in shapefiles. I see a tool for featureclass to shapefile, but not the other way around. I opened the centerlines shapefile dbf table and added the JOINID field. I was not working with just a dbf of street names, if that matters. I felt like I was following all the steps, but when it tries to build the locator, it would fail with a very general error. Chris- I had responded earlier this morning, but apparently didn't click the 'post' button.... Your original post mentioned a 'centerlines file' which I took literally. To get a shapefile into a geodatabase is pretty easy. Take a look here to start. That said, you can use shapefiles, I just prefer geodatabases. Without taking a look at your data, I really can't comment on what the problem is that tosses the error. If you can post some of your data here, I'd be happy to give it a go, or you can contact me via pm and we can take this off-forum if you prefer.
... View more
03-22-2012
07:33 AM
|
0
|
0
|
1680
|
|
POST
|
WOW! We GOT IT! After 2 days and 7 hours of phone support it ended up being an issue with the public rolls. As each new users is added they get defaulted as public. Well all the indexes, tables etc... had no permissions under public so we had to grant all that under public manually (long process). How this happened they don't know. This issue does come up in Oracle (Allot) but this is the first time in SQL. Just a thought; could this have been avoided using database authentication? For SDE, I'm not a big fan of windows authentication which is why I ask. I've always used database authentication.
... View more
03-20-2012
01:50 PM
|
0
|
0
|
2768
|
|
POST
|
Thanks for the offers of help. I did attempt to create an altname table and I thought I had it figured out to some extent, but it fails when it tries to create the locator. I have a centerlines file with a streets with many segments. I created a JOINID field on each segment. For example, segment JOINID 36 is called FAYETTEVILLE RD, but it's also known as US 401 HWY. So I have a matching ALTNAME table with JOINID 36 and it's street name is US 401. STREET_ID DIR_PRE STNAME STYPE DIR_SUF joinid 465 US 401 HWY 36 The ALTNAMES table I'm creating is a DBF file. The centerlines file table I used was also a DBF table. Is that what I should be doing? Your streets need to be in the form of a feature class, not a file. When you geocode, you are turning an address that you and I recognize into a pair of X,Y coordinates that the GIS recognizes; the coordinate system of your street feature class is the basis of those x-y pairs. I'm a big fan of personal geodatabases since I'm a big fan of access, so I'll store both my streets feature class as well as my alt-names table there. I like to keep the addresses in there too, and write my geocoded output there as well. However, I write my locators to a directory, typically the one that holds the pgdb. Take a look here; it may help you out a bit.
... View more
03-20-2012
11:09 AM
|
0
|
0
|
1680
|
|
POST
|
Chris- the key to alt names is a join item. Here is how I've done it: All the streets I have are either alpha or numeric in name. Every alpha street has a numeric value that I use for an alias. The numeric value of each alpha street is stored as an attribute in the original feature class. I also add a unique identifier other than the OID or GUID. To make an alias table I simply select those streets where alias_field is not null or <> ' ', and write the records to a stand alone table. The join item goes with them, so you are good to go. If you don't have your centerlines set up as I do, you can start from scratch; just be sure to add an item to the original street feature class that you can join to. Develop your table in such a manner that it has the proper fields you'll need like Pre Dir, Suf Dir, Type etc. The address ranges will be taken care of in the original data. Michelle- you are much nicer than me when it comes to aliases. I'll go two, maybe three deep, but 26!? Your dispatchers had better treat you like a saint! Hope this helps-
... View more
03-16-2012
03:21 PM
|
0
|
0
|
1680
|
|
POST
|
Take a look here for the 9.3.x description of Network Analyst algorithms. And here for 10.x tutorial. Specifically page 30. After you get a good understanding of the software, you can take a look at the developers pages and get into the gory details of ArcObjects.
... View more
03-16-2012
06:49 AM
|
0
|
0
|
2625
|
|
POST
|
Let's see if I can shed some light by asking a few questions as well as a couple of suggestions.... Obviously, you should begin by filtering streets that are missing data: No Street Name? No Address Ranges? Flag them some how; add an attribute called 'Suspect' or 'ByeBye' or 'Exclude' or something along those lines. Type it short integer, and calc them to 0 (zero). As you perform your filtering, those that are Suspect, or should go ByeBye or should be Excluded should be calced to 1 (one). Ones and zero; pretty easy right? That way you can symbolize them and see where the problems are. You get more creative too; 1 = missing name, 2 = missing ranges, 3 = missing ranges right side, etc, etc. Compare them spatially with what you want to replace them with: are you going to gain any additional useable data? No sense replacing lousy data with the same, right? Maybe you have data that has better attributes, but lousy geometry or the other way around. You can use the Spatial Adjustment tool bar to transfer attribute values and/or geometry. Seems like I've responded to your public safety forum posts; does you cad vender provide you any tools to check overlapping ranges, missing ranges, mixed parity, gaps,etc? I know that Spillman and Versaterm both do; I use them both and they work really well. Once you have your address attributes taken care of you can start looking at connectivity. Build a network and start running some routes or service areas. Your disconnects will show up in a hurry. Be especially careful of freeway over and under passes; legacy coverage data will have your responders making 40 foot jumps to and from bridges! Hope this helps...
... View more
03-16-2012
06:26 AM
|
0
|
0
|
745
|
|
POST
|
Good catch Jake; I should have included that; I use sdemon...
... View more
03-15-2012
10:12 AM
|
0
|
0
|
1234
|
|
POST
|
I have a feature class with the name GIS_POLYGON_TEST. Versions: sde.default sde.Test After opening ArcMap and adding the FeatureClass I want to work, I'm following the steps bellow: -> create version -> start editing -> add a polygon -> reconcile and post version -> save and stop edition -> delete the test version -> run compress Table 'A' of GIS_POLYGON_TEST is not cleared. *The dataset is versioned. what's the problem? I'm not sure what the problem is but I'll make a suggestion on your work flow: Create your 'edit version' first in ArcCatalog Create a database connection to the sde instance and make the 'edit version' you default Open ArcMap and add the 'edit version' feature class (the edit version will be the default from above) Make your edits Save your edits Stop editing Start editing Reconcile and post your edit version to sde.default Stop editing Change versions to sde.default to make sure the changes you made have been posted I don't know why you want to delete youre edit version, but that's your call. I would do that in an ArcCatalog session though. Depending on the permissions you have set to sde.default, you may or may not have compress priveldges. Hope this helps-
... View more
03-14-2012
09:10 AM
|
0
|
0
|
1234
|
|
POST
|
A shape file is made up of a minimum of three seperate files: <name>.shp, <name>.shx, <name>.dbf. It's always nice to have the <name>.prj as well. Yes, <name>.shp holds the geometry, and <name>.dbf is the feature attribute table; <name>.shx is the go-between-guy that indexes or links the proper geometric feature with the correct row in the .dbf. Finally, the <name>.prj holds the projection definition for the shape file. If you don't get the .prj file, you'll need to ask the data provider what the spatial reference is and run the define projection tool on the shape file. Personally, I think the best way to transfer all the components of a shapefile is to put them into a directory and add the directory to it's own zip file. If you got some of the component files but not all, contact who ever the data provider is and ask that they send everything.
... View more
03-13-2012
12:31 PM
|
0
|
0
|
7247
|
|
POST
|
An international standard? Wow. That's a good one....
... View more
03-12-2012
12:08 PM
|
0
|
0
|
2184
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-11-2018 07:12 AM | |
| 1 | 05-17-2021 11:18 AM | |
| 1 | 06-29-2021 11:42 AM | |
| 1 | 07-05-2012 07:49 AM | |
| 1 | 09-03-2016 06:16 AM |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|