|
POST
|
Amy, Here is my original forum post by which I learned what was necessary: Publishing a feature service using a versioned feature class
... View more
07-17-2015
10:05 AM
|
1
|
4
|
2458
|
|
POST
|
Amy, Create a connection to your database specifically for your transactional version. If you use Direct Connects, use the ArcToolbox tool: "Create Database Connection" (in the Data Management-->Workspace toolbox), otherwise use "Create ArcSDE Connection File" (same location) if using the ArcSDE Service. The important step with either is to specify the version to be used. With "Create Database Connection" you need to expand the Geodatabase Connection Properties section to get at the version drop-down. Once you have that connection, register it with Server. Connect to your data with the new connection and add your versioned data to your .mxd. If you have other data as part of this same service, add it by using a connection to the default database. For Feature Services with versioned data, I tend to not have extraneous data added alongside the versioned data in the same map service. But that's just the way I do things and I don't know if that's a "best practice" or not.
... View more
07-17-2015
09:59 AM
|
1
|
1
|
2458
|
|
POST
|
John, This is a situation where you may not necessarily be able to have your cake and eat it, too. It depends on how your are currently operating. If you publish all of your map services in the UTM coordinate system, the coordinates reported will be in UTM. But that basically precludes you from using any of ESRI's basemaps. So, if you like and use ESRI's basemaps this may not be an option. I have the other side of the issue--I publish everything in our State Plane coordinate system, including our own basemaps. My users want to see the "mouse-following" lat/long display but the coordinates are State Plane. As a compromise, my users use Robert Scheitlin's Enhanced Draw and Measure widget to get at coordinates. The coordinate text persists, so it makes it easier for them to transfer that value rather than attempting to keep the mouse still enough so the value doesn't shift on them. But now that the Flex Viewer is "dead", I am shifting over to HTML5 using the Geocortex Essentials product. It allows me to still use my AGS map services directly without resorting to AGOL or Portal and ESRI's overpriced named user model. I'm also exploring--a bit more than casually--the open source offerings on everything in the GIS stack because I see the day coming when ESRI forces us all into the named user model (with ArcGIS Pro) and prices us completely out of continuing to use ESRI products. And I'm fairly certain my organization isn't the only one that will be in this situation. Brian
... View more
05-27-2015
08:03 AM
|
2
|
0
|
475
|
|
POST
|
Steven, By "multiple ArcGIS Server sites" do you mean viewers/apps? If so, the answer is yes. Those can go on any webserver and are not constrained to being on the same machine as your ArcGIS Server instance. If you mean multiple ArcGIS Server instances, I am fairly certain the answer is no. Your license is for a single instance. But this question is probably better answered by your account representative. I suppose that you could have two 2 core servers (for a total of 4 cores--your license), but your question specifically says "same machine" and from a performance standpoint I am not sure how much that would gain you. Admittedly, I may be misinterpreting what you are truly asking. Brian
... View more
03-17-2015
09:46 AM
|
1
|
1
|
1110
|
|
POST
|
Jon, I hope others take the time to offer additional ideas. Admittedly, shifting features around from one version to another is a hackish workaround. I'd like to think someone else has approached this from a slightly different angle that is more efficient! But maybe that's just wishful thinking... Brian
... View more
03-13-2015
01:38 PM
|
1
|
0
|
1307
|
|
POST
|
Jon, The situation where this arises for us is with addressing. I am sometimes asked to calculate house numbers and then there is some sort of delay necessary before making them official. We are usually not incredibly busy from an addressing standpoint so most of the time I can simply delay the post to default. There have been a few times that in the interim another address assignment or two has come up that needs to be posted right away. At that point, we discuss and make one of two decisions: - Post everything but delay the official announcement. Not ideal if I get a data request for our site address layer before everything is official! - Move the unofficial addresses to a separate layer and delete them from the primary layer so that posting can commence. The danger is that I might forget to add them back when they get officially announced. I've contemplated the idea of creating a separate version for every address assignment or group of addresses (i.e. all of the newly assigned addresses for a subdivision), but the number of times this issue occurs doesn't seem to warrant adding that extra layer of complexity. That might be different if there were more than one editor for this data. I may be reading too much into your initial post, but are you saying that for a particular unit of work (i.e. the PDF or CAD dataset) only a portion of the features might be desired to be posted? Or are you saying that you may only want to post the edit for one dataset even though you have a requirement to enter all of the datasets? I know some organizations use versions to capture working alternatives and some of those never become the end result but are still used in the analysis/review stages of their project. Multiple versions would work for the latter scenario but not for the former. And I suspect that you've already evaluated that workflow. A thought that just popped into my head is: Are you able to evaluate beforehand which features should be posted and which should not? If so, maybe splitting the work into different versions could work. We don't know enough specific info about what you are dealing with to really say if that is viable or not, but you can evaluate that idea for appropriateness. I don't know, either, if that may create feature conflicts where the conflict resolution process is invoked. Brian
... View more
03-13-2015
01:01 PM
|
1
|
2
|
1307
|
|
POST
|
Jon, I don't think you can pick and choose which changes get posted versus not. All of the changes are saved into the delta tables, and a reconcile/post process simply operates on all of the outstanding changes, pushing them to default. Occasionally I have a similar need, typically related to the timing of when the changes are made official, so I am interested in also finding out if there is a way to do this. But I suspect such a process would be a bit convoluted to pull off. Brian
... View more
03-13-2015
12:11 PM
|
0
|
4
|
1307
|
|
POST
|
Tim, Interesting comment regarding the "dummy layer". It turns out that I have our city limit boundary added to the map, but turned off, so I never came across the issue. I remember intentionally adding the layer so that ArcMap would have our projection "locked in" to the map document to prevent any re-projection-on-the-fly issues. "Rinse and Repeat" sums the process up beautifully! Glad you found some/all of my advice helpful. Brian
... View more
10-10-2014
12:28 PM
|
0
|
0
|
2062
|
|
POST
|
Jared, With the definition query in place, there are 66 features, so well under the 1000 record default limit. But just in case ArcGIS was applying the def. query somehow after I think it logically should, I bumped the record limit to 20000--that, too, is well beyond even the total number of parcels in the dataset. After re-publishing I still get the odd behavior of dropped features. Brian
... View more
10-06-2014
12:51 PM
|
0
|
0
|
1364
|
|
POST
|
Running version 10.2 of Server. Created .mxd of desired data. See the "ArcMap" image attached. Published as a "regular" map service (not a Feature Service). When I preview the published service in ArcCatalog (see the "ArcCatalog" image attached), a number of my features are missing. The attached image has red circles surrounding a few of the areas where this is occurring. Joins are involved with this map service, but wouldn't all of the features fail to display if the join was at issue? The display in ArcMap is the result of a query definition where a particular field of the joined table is not NULL. I've looked at the data in the features that are not showing up in the published service and compared it to the data in the features that do show up and cannot see anything unusual. Has anyone seen this behavior before? Any ideas on how best to troubleshoot? Thanks in advance, Brian
... View more
10-06-2014
11:45 AM
|
0
|
4
|
3794
|
|
POST
|
Matt, Aren't all of the responses to this thread the "feedback"? To be sure, it isn't a nice, tidy list but all of the requests are there. At the very least, I see the common thread of "all of the widgets Robert produced for the Flex Viewer" with some additions.
... View more
09-29-2014
08:10 AM
|
0
|
0
|
1523
|
|
POST
|
Robert, 1. enhanced search 2. identify 3. basemap fader/switcher 4. draw/measure 5. related records 6. street view Like others, I would be consuming REST services directly from my own server and not via AGOL webmap/Portal. For the basemap switcher I need it to recognize my cached map services that are in our State Plane projection. The AGOL basemap switcher doesn't seem to recognize my published basemap services as basemaps. But maybe I am missing something simple regarding that.
... View more
08-26-2014
03:28 PM
|
0
|
3
|
1523
|
|
POST
|
Dan, The formula syntax to use depends on your source data. See this blog post and the user comments for more info: http://mappingcenter.esri.com/index.cfm?fa=ask.answers&q=533 I don't recall if the contour layer in the LGIM has fields set up for coding index contours, but if not, create fields of short integer type based upon the index intervals you want to use. Then use the formula in the link above to select those contours that fit that interval, then code the index field with a value of "1" to indicate the particular contour line is an index contour. Otherwise the field has a value of "0". For example, I have fields set up in our 2 ft. contour layer for 50 ft. and 100 ft. index contours. If I want to show 50 ft. index contours, I copy/paste the contour layer and write a definition query where Index50 = 1 (Index50 is my field name), then symbolize it as an index contour and label that layer only.
... View more
08-07-2014
11:38 AM
|
0
|
0
|
686
|
|
POST
|
Kathleen, I would subscribe to an "add to the model only" method and not delete anything--at least until you become familiar with the various applications and what fields they are using. Your concern is valid and you don't want to paint yourself into a corner unnecessarily! You can hide fields by unchecking them in the layer properties within ArcMap. That may or may not have consequences with the apps you want to use, however.
... View more
08-07-2014
11:00 AM
|
0
|
0
|
474
|
|
POST
|
Josh, Looking at your attached graphic, that toolbar is the "standard" geocoding toolbar included in ArcMap. Right-click on a blank area of the toolbar/menu and you can turn on/off various toolbars, including 'Geocoding'. You can also access the same list via the Customize-->Toolbars menu. That said, your original issue is that nothing is found when you type in an address. The toolbar defaults to the World Geocode Service (ArcGIS Online). Is it possible that this address is not captured by the data that locator is built from? I ignore that locator and instead use the locators built against our data. You can drop down the left-most list in the toolbar and select "<Manage Address Locators...>" and select your own locator(s) to choose from. After another look at your graphic it appears that you are pointing it to a different locator than the default, so maybe what I wrote above is info you are well-informed about. When was the last time that locator got rebuilt? If the address shown in the graphic is a new addition to your streets data, a match may not be found until you rebuild the locator's indexes. Also, is the locator set up to need a city/state/zipcode? That may be another reason for no results being found. As for the Windows sound, I've never come across that. If the locator doesn't find a match it simply indicates that in a tooltip--at least in my experience. I don't have the Address Management add-in installed. Since you mentioned that you do have it installed, maybe there is some conflict between the add-in and the "regular" geocoding toolbar (i.e. either a bug or by design).
... View more
08-07-2014
10:42 AM
|
1
|
3
|
2462
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 09-10-2024 12:21 PM | |
| 4 | 07-18-2023 08:22 AM | |
| 2 | 11-09-2021 05:42 PM | |
| 1 | 01-21-2020 02:00 PM | |
| 5 | 08-01-2022 09:07 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-24-2025
02:17 PM
|