|
POST
|
Nope just the beep. when I first open an ArcMap session Single Line Input shows up but goes away and hovering over it brings it back. I guess I will report it to Esri support. This is such a bizarre error I don't know what else to do.
... View more
08-14-2014
06:17 AM
|
0
|
0
|
3346
|
|
POST
|
That seems to work. As long as I make only one of the operational layers and one basemap layer visible="true" it seems to work. That is until I tried the Identify widget which doesn't seem to recognize the operational layer anymore. The other layers that have different labels still work just fine. Is this the issue that would require source code changes? I guess I could have another layer for those layers that has no symbology but that stinks if that is what I have to do. Seemed like such a good idea at the time.
... View more
08-13-2014
02:26 PM
|
0
|
2
|
1348
|
|
POST
|
Well, that method might work for me. I'll try it out and see what happens.
... View more
08-13-2014
02:12 PM
|
0
|
0
|
1348
|
|
POST
|
I'm frustrated that I cannot use a different operational layer over different basemaps. The Imagery webmaps require relatively vivid colors for overlaying layers. The Streets (General Purpose) basemap looks better with duller colors. I've created a perfect overlay operational layer for the Streets basemap but don't understand how to change which layers are visible for each basemap. My only other option would be to create separate webmaps for each basemap which is a horrible workaround. Am I missing something?
... View more
08-13-2014
01:40 PM
|
0
|
5
|
1917
|
|
POST
|
The attachment is there Capture.JPG. This forum thread was brought from the old forums into Geonet so it looks a little funny. By the way, it doesn't matter which locator I use, I tried the World Geocode Service and came up with the same problem.
... View more
08-08-2014
06:47 AM
|
0
|
4
|
4251
|
|
POST
|
That's not bad. Might want to reconsider the basemap though, when you zoom in it is too pixelated. For mine I used the imagery when zoomed out but changed to a streetmap style as it was zoomed in.
... View more
08-08-2014
06:14 AM
|
0
|
1
|
4308
|
|
POST
|
I assume by your second message that you saw that I posted that in the original post? It is my own locator service.
... View more
08-07-2014
01:40 PM
|
0
|
0
|
4251
|
|
POST
|
Yeah, the tooltip that is displayed is the one that tells you what to enter and Single Line input comes up too and like I said the address inspector works just fine and all other uses of this locator display just fine. I just get the warning sound that I am trying to do something even though an invisible dialog box is open. The sound I am describing is the same one you get when you try to close out of an application without saving and the message comes up asking if you want to save. I removed the Address Management Add-in and nothing changes.
... View more
08-07-2014
11:47 AM
|
0
|
2
|
4251
|
|
POST
|
Unfortunately, it doesn't change the extent. I even removed the spatial index and added a new one but it just returned to the original extent.
... View more
08-06-2014
12:46 PM
|
0
|
1
|
6216
|
|
POST
|
I had a layer that initially had a very large extent (moved from one of the Local Government templates) and even though the extent of all of the features is much smaller now, when you select zoom to layer in the Table of Contents, it zooms to the that massive extent still. All of the existing features are within the smaller extent. When you select all features and click Zoom To Selected the smaller extent also applies. Is there a way to adjust the extent of a feature to match the extent of the features? Under the Source tab the larger extent is also present. Should be closer to:
... View more
08-06-2014
11:49 AM
|
0
|
4
|
10854
|
|
POST
|
Is there really ever any cause to worry about just disabling the schema locking on all services. Anytime a feature class is removed, the service should be restarted anyways so I don't see what the issue is.
Esri help:
"When schema locking is disabled, it is recommended that you only update your source dataset schemas when the service is idle. If you update the dataset schema when the service is under load, users of your map service may experience unexpected behavior such as layers and fields missing, queries failing, and service unavailability. Changes to the schema of the dataset need to be carefully planned; permanently removing datasets may leave your map services in an inconsistent state."
I don't ever have a large load and can usually recover quickly with a quick refresh of a service. I do know approximately when my peak usage is so I can avoid that. Best time for me will be at the end of the day.
... View more
08-06-2014
11:15 AM
|
0
|
0
|
4361
|
|
POST
|
Gary, I will try to only disable my one main base service that locks almost all of the feature datasets. It is the main layer that probably receives the least edits but is needed in virtually every webmap (parcels, addresses, etc). I will leave my utility layers alone so as to avoid problems, thanks for your help.
... View more
08-06-2014
10:01 AM
|
0
|
1
|
4361
|
|
POST
|
Sounds like a good workaround but wow is that a lot of extra steps to do.
... View more
08-06-2014
08:54 AM
|
0
|
0
|
4361
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-29-2024 02:00 PM | |
| 1 | 06-06-2014 01:54 PM | |
| 1 | 08-14-2014 07:03 AM | |
| 4 | 06-10-2025 12:49 PM | |
| 1 | 09-23-2020 07:48 AM |
| Online Status |
Offline
|
| Date Last Visited |
01-07-2026
12:11 PM
|