POST
|
No idea. Looks like a bug in the ADF, not specific to schematics.
... View more
09-21-2011
09:01 AM
|
0
|
0
|
562
|
POST
|
This "most of the time diagram not displaying properly" needs some further explanation please. Is there anything in particular that is different about diagrams that do display vs. diagrams that don't display? Do the diagrams that don't display work fine if you go to a full extent (i.e. is it just a problem of initial extent)? We think the problem is just that the published map didn't have a large enough extent to cover the future diagrams. The extent of the original published map is the 'full extent' on server. So if you later generate new diagrams that are beyond this initial extent, then they will not be visible or may only partially be visible. If you re-open the published map, click full extent and re-publish, these diagrams should all be visible. If that is the case, then the issue you have is just making sure to make the initial extent of the published map much larger.
... View more
09-08-2011
08:13 AM
|
0
|
0
|
562
|
POST
|
It was just a prototype and the decision was to not continue with it. For large scale social network analysis, we have a business partner, I2, that builds software specific to SNA. Everything that was shown in the video was build on top of the public api and can be reproduced. Starting at version 10, there is a SchematicsDigitizingTool sample in the desktop developer kit. That will allow you to do custom digitizing directly on a diagram very similar to what was done in the video. If you already have the data in a tabular format with some concept of connectivity (from/to information) and geographic position (x,y), then you can simply use our custom query capability to have schematics draw this data. Initially using the correct x,y given in the table, but then using the other out of the box algorithms for alternate visualizations. The basics of this concept is covered in the help system as well as in a white paper (Using Schematics for Inside Plant Representation) that can be found on the website: http://www.esri.com/software/arcgis/extensions/schematics/brochures-whitepapers.html
... View more
08-31-2011
10:18 AM
|
0
|
0
|
1058
|
POST
|
Did you get this working? You either need to compile the dll that contains this class on the server, or register it on the server with the command line registration commands from Microsoft.
... View more
08-11-2011
08:59 AM
|
0
|
0
|
562
|
POST
|
Again this depends on what you need to do. Make sure to read and understand the document that edga6340 left a link to in his post. Schematics has always had 2 levels basically. Prior to 10, there was 'Schematic' and 'Ng'. Ng was just a prefix but it was dealing with things once they are 'in-memory'. So in 10, that was cleaned up with proper naming. So, for the most part things that used to be Ng..., are now just SchematicInMemory...
... View more
07-27-2011
06:56 AM
|
0
|
0
|
527
|
POST
|
You just really don't need NgProject anymore. The only place it really looks like this code was using it was Set ngDiagramFromSchDiagram = ngProjectFromSchDataset(schDataset).GetDiagramType(pObjectClass.AliasName).GetDiagram(schDiagram.Name) Now you just get the schematic dataset, then get a diagramclasscontainer and set it to the schematic dataset. Once you have the diagramclasscontainer, you get the specific diagram class (used to be called diagram type) and from there get your diagram. If your schematicdataset variable is named m_pSDS, then the code would look like this: ISchematicDiagramClassContainer pDCC = (ISchematicDiagramClassContainer)m_pSDS; ISchematicDiagramClass pDC = PDCC.GetSchematicDiagramClass(somename); ISchematicDiagram pDiagram = pDC.SchematicDiagramByName(somename);
... View more
07-26-2011
06:45 AM
|
0
|
0
|
527
|
POST
|
So first of all, everyone must realize that VBA is dead... So if you are migrating code to 10, I would strongly suggest that you don't do it to just VBA. Follow the new Add-In paradigm that uses .NET or you will end up migrating again when VBA is completely pulled out of ArcGIS. Secondly, there are a lot of schematic samples available in the desktop developer kit that show how to work with the api. So just saying you need NgProject isn't descriptive enough, we need to know what you are actually trying to accomplish. At 10, you can do most everything from the diagramclass or elementclass, but again, depends on what you are trying to accomplish. So let us know what you are doing and I will try to help you through it.
... View more
07-22-2011
08:30 AM
|
0
|
0
|
527
|
POST
|
For ArcGIS 10 and below, the convert is the best thing to do, then you have another service that is publishing the converted features. Remember that you can convert multiple diagrams into the same set of converted feature classes. Then when you want to display one of those diagrams, you just need to apply a definition query on the published layers (diagramobjectid=?). At 10.1, a schematic diagram is fully recognized on server, and is a REST endpoint. There is also a Schematic Server Object Extension. So you have a map service published and you have a schematic service published. When you generate a diagram, a new end point is available on the schematic service. Now you can pop-up viewers etc... basically a map and tell it to display a particular diagram with something like this: http://schematics64:6080/arcgis/rest/services/Westerville/MapServer/exts/SchematicsServer/diagrams/0-6
... View more
06-22-2011
02:17 PM
|
0
|
0
|
257
|
POST
|
Chris, I don't have an answer for your problem, but am interested in this scenario (diagram). Wondering if you can share some information about it. If so, send me an e-mail please. randerson@esri.com
... View more
06-14-2011
01:02 PM
|
0
|
0
|
477
|
POST
|
From one of the developers here: The builder context is a remote object that is created on the server : pSchStandardBuilderCtxt = pServerContext.CreateObject("esriSchematic.SchematicStandardBuilderContext") Then, in this remote object, they try to put a local object from a local class (EnumObjectConverter) : EnumObjectConverter eocon = new EnumObjectConverter(pEnumFeature); pSchStandardBuilderCtxt.InitialObjects = eocon as IEnumObject; But their EnumObjectConverter class is not known on the server I think this class should be registered on the server and they should instantiate their �??eocon�?� object as a remote object too.
... View more
06-07-2011
06:31 AM
|
0
|
0
|
562
|
POST
|
Don't thank us yet until your sure it works 😄 Let me know if there is something else I can help you with. randerson@esri.com
... View more
06-03-2011
06:30 AM
|
0
|
0
|
582
|
POST
|
Is this a blank (empty) map document? Is there a selection in the map? Are you using the standard builder and working with a geometric network? Lot's of questions before we can help. Take a look at this post to see if it helps find the issue.
... View more
06-02-2011
11:33 AM
|
0
|
0
|
582
|
POST
|
Symbols are static in nature. In Schematics, you can configure a rotation attribute that will rotate based on a database field. You can also use the Geo-Rotate Nodes Along Links algorithm that will do this without being field driven. Sometimes you need to change the initial orientation of the symbol itself from Top-Bottom to Left-Right so that it draws better after using the algorithm. This happens with switch symbols in many cases.
... View more
05-27-2011
08:10 AM
|
0
|
0
|
314
|
POST
|
Take a look at ArcGIS Schematics. We have several large partners (Telvent Miner & Miner and Telcordia) that use ArcGIS Schematics for this. You can link a GIS object to a 'diagram' and have it pop-up. The diagrams themselves are data driven, so changes in the real data are often automatically reflected in the diagram. So no static 'dummy' diagrams, they are live. Send me an e-mail and we can setup a time to learn more about what you are doing and how ArcGIS Schematics might be able to help. randerson@esri.com
... View more
05-27-2011
08:07 AM
|
0
|
0
|
159
|
POST
|
If this is for viewing only, you have one free option available for server. You can run the schematics gp tool to convert diagrams to features and just convert all your diagrams into features. This results in a feature dataset for the diagram template and then a feature class for each schematic feature class. Then all the diagrams are just individual records in the dataset/feature classes. You can then just put those into a map and publish with nothing more to do with Schematics. The trick is that on the web client side, you will need to provide a way for the user to pick which diagram they want to view and then you just dynamically apply a definition query to the layers DiagramObjectID=?. At 10.1, the diagram layer itself is recognized by the server publishing mechanism, so you don't have to convert to features first.
... View more
04-29-2011
08:23 AM
|
0
|
0
|
268
|
Title | Kudos | Posted |
---|---|---|
1 | 12-16-2013 10:41 AM | |
1 | 08-22-2014 09:04 AM | |
1 | 01-09-2017 07:52 AM | |
1 | 01-09-2017 08:59 AM | |
1 | 04-11-2014 10:02 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:22 AM
|