POST
|
There isn't a work-around in the core template. However...we are looking at putting this splice point into the template sometime in the near future, but I just can't guarantee when or if it will happen at all. It will also end up being based off the xml builder. So there will be an external component that will understand how to get the 'internal' data and send it to schematics where the algorithm will be applied.
... View more
09-28-2012
02:08 PM
|
0
|
0
|
1286
|
POST
|
That is a custom algorithm that is only exposed to customers via our partners (Telcordia (Eriksson) and Telvent (Schneider)) at the moment. We are just now deciding if this will be something we put into the core or provide on the side that will work with our Esri Telco data model. If you have an xml file (following our xsd) that describes one of your splice points, I might be able to run it through the algorithm and show you the results.
... View more
09-21-2012
09:45 AM
|
0
|
0
|
1286
|
POST
|
I will need to see exactly what is happening to help much more here. Send me an e-mail to jetta01@hotmail.com with your contact info and I will get in touch.
... View more
09-11-2012
02:09 AM
|
0
|
0
|
420
|
POST
|
Did you follow those quick start steps exactly? Usually the only way to end up with missing lines is that one of the point features in the geometric network is missing from the configuration. Schematics needs to have configuration information for every class that is in the geometric network in order to keep proper connectivity. A link can't exist without both end nodes. So if one of those end node classes hasn't been configured, it won't work. If you haven't followed those steps exactly, give it a quick try with a file gdb or personal gdb and see if that resolves it, only takes a minute or 2 to test it. If that still doesn't fix it, let me know and we can try to setup a web meeting so I can see what is happening. Also include the service pack you are running in the next response please.
... View more
08-31-2012
07:51 AM
|
0
|
0
|
420
|
POST
|
Not very much info to go on here... Have you followed the quick start guidelines? http://forums.arcgis.com/threads/1079-Beta-10-Schematics-Quick-Start-for-Utilities?highlight=schematic Have you watched and followed the resource center videos? http://resources.arcgis.com/en/communities/schematics/01n600000012000000.htm What version are you on? Do you have a geometric network?
... View more
08-30-2012
12:03 PM
|
0
|
0
|
420
|
POST
|
You must be doing it wrong, our software never crashes 😄 What version of ArcGIS are you on and what does the 'entire schematic' really mean? How many nodes, links etc...? If the crash is reproducible, can you watch the memory on your machine and see what happens when you run this to see if it is a memory limitation? This algorithm is pretty memory intensive as it has a lot of calculations to figure out especially if you are doing this on a large diagram. How much RAM is on this machine?
... View more
08-28-2012
02:33 PM
|
0
|
0
|
836
|
POST
|
No limitation that I can think of. Usually if it doesn't separate anything, means it didn't find a conflict. So that first property setting 'BufferWidth' is very important. That is what it uses to find a conflict and then it uses the next value 'offset' for the new spacing. ***Remember that these settings are interpreted in map units. So if your map units are decimal degrees and your conflict setting is 1...well, it will be a bit strange. So make sure to either have more realistic map units, or to set the property value to something that makes sense based on those units '.00005' for example. If you still can't get it to work, if possible, export your diagram as XML, clean up any critical information as needed, and get it to me so we can take a look.
... View more
08-24-2012
06:49 AM
|
0
|
0
|
836
|
POST
|
http://resources.arcgis.com/en/help/arcobjects-net/componenthelp/#/DisplayDiagram_Method/003t0000001s000000/ You should use the ISchematicDisplayDiagramHelper. You need first to have a handle to the ISchematicDataset, then you get the desired diagram class (the old diagram type). From the class, you get the diagram and finally use the diagram helper to 'display' the diagram. Dim pSchematicDiagramClass As ISchematicDiagramClass Dim pDiagramClassContainer As ISchematicDiagramClassContainer pDiagramClassContainer = m_pSchematicDataset pSchematicDiagramClass = pDiagramClassContainer.GetSchematicDiagramClass("INTERNAL_DIAGRAM") Dim pDiagram As ISchematicDiagram pDiagram = pSchematicDiagramClass.SchematicDiagramByName(plant_name) ... m_pDispDiagramHelper.DisplayDiagram(pDiagram, Nothing) More information about migrating code: http://resources.arcgis.com/en/help/arcobjects-net/conceptualhelp/index.html#/d/000100000m29000000.htm
... View more
08-24-2012
06:40 AM
|
0
|
0
|
324
|
POST
|
Hi Srikanth, Schematics supports the 'container' concept. When you create the schematic feature class in configuration, set it as a Point type but with polyline geometry. So you have a node feature with an "ExternalUniqueID" that is going to end up drawing as a polyline geometry. Now any feature that goes inside it (node or link etc...), you just set its xml for "RelatedContainerID" = to the "ExternalUniqueID" of that node 'container' feature. The attached example of a telco splice point internal shows this concept. The Buffer Tubes are containers around the actual fiber nodes. You can also search the schematic help system for 'container' to find out more information. Rick
... View more
08-20-2012
11:46 AM
|
0
|
0
|
1286
|
POST
|
Hi Srikanth, First of all, the xml capabilities and SOE capabilities are completely different concepts. There is desktop capability and there is server capability (SOE). In either case, there is an XML Builder that can be used to pass the desired data to schematics. The main reason to use an XML Builder would be that the data is not in a standard geometric network or network dataset, which those cases have specific Builders to deal with those networks. After you get the data to schematics (xml builder, standard builder, network dataset builder or Custom Query), then you have to deal with the physical layout (layout algorithm) on the screen. The core product only has generic layout algorithms and tools that would allow you to do this manually. If you want it automated, then you will also need to create a custom layout algorithm that does exactly what you need. Start on the desktop and get it working, then transition the builder and layout algo to the server. So it is possible, but will likely require at least a custom layout. I would suggest you spend some time watching the videos available on the resource center which explain the basics of schematics and go through the various builders. Once you have a better handle on that, then look at the sample for creating a custom layout algorithm. There is also a sample for an xml builder. After all that, see what questions you still have. Thanks, Rick
... View more
08-16-2012
08:36 AM
|
0
|
0
|
1286
|
POST
|
I guess I should note that if you are only 'selecting' elements, you can use the core Select Features tool from the main toolbar. The schematic tool does do selection, but also allows for moving things.
... View more
08-10-2012
06:33 AM
|
0
|
0
|
303
|
POST
|
That is a standard tool on the toolbar, so if it is missing, I would question the installation or the map doc template that you are using. You might want to delete the normal.mxt file your user settings so that it 'resets' to default. Other than that, all of the tools on the toolbar are available in the customize dialog. So you can Customize on the toolbar and then choose the Customize Mode. Go to the Commands tab on the Customize dialog. Scroll down and select schematics from the categories list and then find the Edit/Move Schematic Features tool in the commands list. Now you can drag/drop that onto a toolbar.
... View more
08-10-2012
06:30 AM
|
0
|
0
|
303
|
POST
|
The schematics api is just another part of ArcObjects. So you definitely can edit the real features/objects from a diagram, but we don't allow that out of the box. Out of the box, a diagram is just a view of the real data. Depending on how your diagrams templates are configured and the type of underlying data, schematics keeps track of the 'real' classid, objectid and subid as well as the datasource from which it came. So it is pretty easy to use that to get back to the source feature and make changes. In the 10.1 desktop SDK, there is a digitizing sample that shows how you can digitize directly on a schematic diagram, so that will help you get a feel for various parts of the api. Since standard features and schematic features are in different edit sessions, if you want to take what was digitized on the diagram and push it to the 'real' feature class, you will have to get that workspace, start editing and create the 'real' feature record based on what was digitized on the schematic. You should also take a look at the ISchematicFeatureLinker as it can help you retrieve objects (again depending on how the schematic dataset is configured). This would be very useful if you want to update the 'real' feature attributes based on a change done in the schematic diagram. http://resources.arcgis.com/en/help/arcobjects-net/componenthelp/#/FindObjectsFromSchematicFeature_Method/003s000001n3000000/
... View more
08-02-2012
08:45 AM
|
0
|
0
|
295
|
POST
|
We have seen this a couple of times but can't reproduce it here. In those other cases, re-installing has fixed it, so it seems like something is not getting registered correctly during the installation.
... View more
07-13-2012
07:54 AM
|
0
|
0
|
224
|
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
|