|
POST
|
The 2048? That's the number of records that show up when the data is pasted into an Excel spreadsheet. Or did you mean something different? Thanks, Tycho Tycho Granville, GISP | GIS Coordinator INFORMATION SERVICES tychog@co.wasco.or.us | www.co.wasco.or.us 541-506–2658 | Fax 541-506-2641 2705 E. 2nd St. | The Dalles, OR 97058
... View more
03-09-2017
11:48 AM
|
0
|
7
|
2542
|
|
POST
|
I am working with ESRI tech support on this, I thought I would check with the community simultaneously. This is a known (and open) bug in desktop from 10.1 on. This just started happening to us (we first noticed it this morning), none of our data structures or procedures have changed in some time. The FC's are in a File GeoDB. This happens on multiple machines using both 10.5 and 10.2 (we have one user with a 32 bit machine so they won't be able to upgrade for a while). Basically, copy–paste a selected set from the table view to Excel does not select all the records. For example: Select more than 2048 features in FC (does not matter if it has joined or related tables or not) --> copy selected features in table view --> paste into Excel. Result: 2048 records pasted into the spreadsheet (always returns 2048 if any number greater then that selected) These permutations work – Select > 2048 features in FC (does not matter if it has joined or related tables or not) --> copy selected features in table view --> sort (by any field) --> paste into Excel. Result: all records pasted into spreadsheet Select > 2048 features in FC (does not matter if it has joined or related tables or not) --> export from table view to DBF --> open in Excel. Result: all records pasted into spreadsheet Selecting and copy/pasting from a shapefile works correctly. Not all of my staff are (necessarily) sophisticated enough to figure out/consistently use the workarounds, and we are not going back to shape files. Has anyone else experienced this, and did you have any luck fixing it? Thanks, Tycho
... View more
03-08-2017
12:17 PM
|
0
|
12
|
4703
|
|
POST
|
Yes, it's a horrible practice. Creating a dummy point was a workaround we had to come up with fairly quickly as the sub- addressed points were creating issues with real calls. As soon as the dispatch software can deal with sub-addresses I will remove the dummy points from our database (and archive them elsewhere).
... View more
11-07-2016
01:51 PM
|
0
|
0
|
552
|
|
POST
|
Our dispatch can't (currently) use sub- addresses. We just add a dummy point in the middle of the tax lot with the main address on it, and let the vendor strip out all the real ones. We have the dummy point flagged so it does not appear to our internal users (we have custom layer files set up for regular staff, they are not allowed to access to any of the raw data because of things like this).
... View more
11-07-2016
11:44 AM
|
0
|
4
|
1136
|
|
POST
|
So, I sat in on the meeting with our vendor. The CAD will pull up the correct address point but there is no way (nor will there be) a way to have to the software figure out automatic routing to that point. The dispatcher will just have to look at the display and find the best route manually then pass it on to the first responders. Currently there is a memo or flag field with problem address points - I don't know what it looks like onscreen or how the dispatchers deal with it. It would appear that NexGen may not have that as a field in their specification. Some of the other counties are doing (pilot?) projects where they are adding an "access point" at the beginning of a driveway to work around this. I believe those projects are just starting, and I'm not sure how they will integrate into Next Gen. That type of data creation is not covered under the standard contracts - it looks like one may be able to get some funding for it from the State to help with the cost. Our vendor's main suggestion was to have landowners change their house addresses so they will fit into the 911 system. Not sure how far that would fly with our public (actually, I do have a pretty good idea...). Tycho
... View more
11-04-2016
02:44 PM
|
0
|
4
|
1136
|
|
POST
|
I'm not seeing any extra points on our centerline layer (the version our vendor sends to us; we wouldn't need anything like that for in-house use). Let me check with the PSAP and our vendor to see what they are doing about that. I already have a meeting set up with both them for next Friday, so I will get back to you after that. I know there have been some issues when a house has been much closer to a road that has a different name than the assigned address.
... View more
10-27-2016
03:01 PM
|
0
|
0
|
1136
|
|
POST
|
Hi Chris, Interacting with the E-911 system is a very small part of my job, but here are some thoughts anyway – I work for a rural County with 24,000 people spread over 2400 square miles. We have agreements (some formal, others just hand-shake) with the towns to maintain road and address (among other) data for them. We also work closely with our PSAP. The 911 data is maintained by a combination of in-house staff and vendors. We are using both centerlines and point addresses. Once per month we send the vendor any changes to either of those 2 layers. They merge these updates into their versions of the data (E-911 uses a lot of fields we don't care about in our internal business process... and since we eat costs (see below) we don't spend the time to fill in additional data). We also assist with maintaining ESN and ASA polygons. We typically spend 2 to 3 hours per month modifying the data for the vendor's use. It can be considerably more if we have to do additional research. Oregon 911 is already using point addresses. The CAD system looks for the points first, then if it can't find those looks to the road centerline for an approximate location. Since driveways can easily be 1/4 to 1 mile long (and have multiple tracks heading off of them to other houses) an approximate location near the road is not ideal. Funding from the State has gone (as far as I know) to vendors only. The County is not reimbursed for our staff time. The only real insight I have is to thoroughly document everything (there's a surprise ) ! We have had instances of vendors asking the same questions about the same addresses months later. It's much easier if you can just look at your notes and say "we told you about this 6 months ago" instead of vaguely remembering that you did research on it "a while back". Good Luck! Tycho
... View more
10-27-2016
11:48 AM
|
0
|
1
|
1136
|
|
POST
|
My above comment about the workspace path needing to exist was incorrect. All you need to do is set the validation flag to False. For example, findAndReplaceWorkspacePath(r"\\WC-HOMERB\Shared\GIS\GeoDatabase", r"E:\GISData103\Data",False)
... View more
10-14-2016
02:07 PM
|
1
|
0
|
1590
|
|
POST
|
Yep, that did the trick. Also, for anyone who looks this up in the future, it looks like the target workspace path needs to already exist. (In my case there is no E:\ drive in our network – I was trying to preconfigure the files on my machine so I could simply copy and paste them to the other one. It is a production machine, so I try to refrain from mucking about on it very much) Thanks, Tycho
... View more
10-13-2016
01:49 PM
|
1
|
1
|
1590
|
|
POST
|
I am sure I am missing something simple (I usually just steal code snippets and try to string them together). I want to change the data source path in a bunch of layer files (I will add in a for… loop once I get this to work). This is a simple layer file, I will also need to update Group layer files def main(): pass if __name__ == '__main__': main() #Modules import arcpy #import string #Environments arcpy.env.qualifiedFieldNames = False # Allow unqualified field names arcpy.env.overwriteOutput lyr = arcpy.mapping.Layer(r"\\WC-HOMERB\Shared\GIS\Scratch\LayersForWilbur \LegalParcelData.lyr") lyr.findAndReplaceWorkspacePaths(r"\\WC-HOMERB\Shared\GIS\GeoDatabase", r"E: \GISData103\Data") lyr.save() and I get this error message: Help…
... View more
10-13-2016
12:52 PM
|
0
|
3
|
2523
|
|
POST
|
Embarrassing but apparently I can't remember my words this morning... I have a roads layer (routed) and a point that I need to show a 30 mile distance from. Damned if I can remember the name of the tool to do that. Anyone?
... View more
10-03-2016
11:09 AM
|
0
|
2
|
1124
|
|
POST
|
I talked to some reps here at the conference, the pointer not being updated when the layers are moved around/added/removed is considered a known bug and has been for a while. It is rated as "Medium" severity (though close to fatal for me). Sigh... Tycho
... View more
06-30-2016
10:05 AM
|
1
|
0
|
2055
|
|
POST
|
Thanks, Kelly I will look at editing the JSON with the tool you linked. There are 3 entries for my map, presumably the AGOL map, mobile version, and web app version. Do I need to edit all 3 files? Also, will I need to do the edits again any time I republish/overwrite the service or only if I add/remove layers? I can't really just add layers to the bottom of the list (at least on this map) as that breaks the groupings I want in the table of contents. Re-configuring the pop-ups every time does not really work either. They took a considerable amount of time to create, I can't set that much aside every time I update the map. (And thanks for the compliment, Adrian ) Tycho
... View more
06-20-2016
02:09 PM
|
0
|
1
|
2055
|
|
POST
|
The map is here, though I had to revert back to the version that was working before (it is a public facing map, and people get upset when I leave it broken for very long...). But, before I canceled my changes… Open up the layer list, and expand Boundaries. I inserted a layer (Parks and Rec) between Fire Districts and School Districts. I turned off all the layers except School Districts. I zoomed into the map until the School Districts layer is visible then click on it. The pop-up lists the information from the Voting Precincts layer, not the schools. Everything in the table of contents from Fire Districts on up is correct, everything from School Districts to the bottom is “offset”.
... View more
06-17-2016
03:13 PM
|
0
|
3
|
2055
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-03-2025 09:05 AM | |
| 1 | 04-17-2024 02:44 PM | |
| 1 | 02-09-2024 10:28 AM | |
| 1 | 05-02-2023 11:53 AM | |
| 1 | 07-26-2023 09:00 AM |
| Online Status |
Offline
|
| Date Last Visited |
12-03-2025
11:15 AM
|