POST
|
The stand-alone arcgis schematics extension is not available for Pro. The new version of schematics, called Network Diagrams, is available in pro though and won't be available in ArcMap. Network Diagrams are built in as a core capability inside the new Utility Network, which is the next generation Geometric Network. It is no longer an extension, it is just part of the Utility Network. Pro doc for network diagrams: http://pro.arcgis.com/en/pro-app/help/data/utility-network/about-network-diagrams.htm
... View more
03-27-2018
07:36 AM
|
3
|
1
|
942
|
POST
|
Actually, instead of running the Separate Overlapping Links algorithm, you really should be running the Geo-Partial Overlapping Links algorithm. Separate only works on lines that are completely overlapping, i.e. they have the same end points. The partial overlapping algo just looks for any overlapping segment. POLA algorithm
... View more
01-09-2017
08:59 AM
|
1
|
0
|
645
|
POST
|
Looks like you need to play with the order of the tasks a bit. Separate overlapping links would solve your 1a/b issues. However, immediately after you are running that algo, you then run square links which then perfectly squares things again causing the overlap. So just flipping 4 and 5 should clarify the overlaps. For items 2 and 3, you can manually adjust afterwards. The algorithms will normally only get you 80 to 90 percent of the way, then manual white space management is needed for the final 10 to 20 percent. A combination of algorithms that works perfectly for 1 sample area of data may not work well for the next sample area. White space management is tricky. The only way you would get 100% is to write a custom algorithm that does everything for you and rechecks several times to make sure it doesn't violate the desired results.
... View more
01-09-2017
07:52 AM
|
1
|
0
|
645
|
POST
|
Not sure what version you are using, but there is a bug in the system dealing with this. It looks like it will be resolved in the upcoming 10.2.1 general utility patch 2 and also in 10.3.1.
... View more
02-19-2015
02:02 PM
|
0
|
0
|
323
|
POST
|
It sounds like maybe you posted this same question elsewhere at the same time because the network analyst team already claimed they answered this question but I don't see any info here. Anyway, apparently 750 is what they consider the 'useful' limit for the treeview. After that, if you need to see it you can use the table window to view everything. Hope that helps. This thread has become pretty bloated, so I am going to stop watching it as I have resolved the main issues. Thanks!
... View more
02-09-2015
01:54 PM
|
0
|
1
|
1207
|
POST
|
Not really any tips...62 routes is a lot of overlapping possibilities. Work the the Partial Overlapping Links algorithm. Hopefully that will get you 80+% or so there and then you will have to use the various manual tools to finish up. I have seen folks use the schematics side to get the overlapping taken care of and then exporting that as standard features to do other cartographic finishing on top. All depends on how much overlapping there is and what you are trying to achieve with the final output.
... View more
02-04-2015
02:11 PM
|
1
|
3
|
1207
|
POST
|
Excellent! Glad we were able to get you up and running again.
... View more
02-03-2015
03:40 PM
|
1
|
5
|
1207
|
POST
|
Are you automatically (or manually) applying a layout algorithm to the entire diagram? Wondering if the parameters being used are causing the issue. Can you just export the schematic dataset (no diagrams) to a FGDB and provide it so we can look at the configuration?
... View more
02-03-2015
02:51 PM
|
0
|
0
|
641
|
POST
|
What version of software are you using? Sounds like maybe an issue with spatial index due to the node reduction happening. In Catalog, right click the Schematics schematic dataset in your database Click Show/Hide Schematic Classes option Expand the tree so you can see the schematic feature classes that are now exposed. For each line schematic feature class, right click and choose properties, then do the following 2 steps Click the Indexes tab and click the Delete button at bottom in the spatial index area Click Apply After this, see if generating/updating is any better. If not, I would need to get a copy of the dataset so we can dig into it more.
... View more
02-03-2015
02:46 PM
|
0
|
2
|
641
|
POST
|
I had a chat with one of the network analyst gurus and showed them the error and table pictures you included. Below are the comments: The user has a network cost attribute with spaces in the name. Since we use this name to create additional fields on some of the analysis classes (like stops), users can run into problems where the system thinks there are invalid field names since typically field names can’t include spaces. We did some work in 10.3 (or 10.3.1) to handle invalid field names a little better. But really, it’s best to tell the user to not have network cost attributes with spaces in the names. So, it seems that there was some configuration done for this network cost attribute that is causing this downstream issue on the diagram side and the diagram side is trying to actually create table fields to keep this data and it is failing because of the spaces.
... View more
02-02-2015
04:53 PM
|
0
|
9
|
1048
|
POST
|
Let me see if I can find a 10.2 / 10.2.1 machine and try to reproduce it. Are you just using a file gdb?
... View more
02-02-2015
02:24 PM
|
0
|
11
|
1048
|
POST
|
Hmmm, not sure. Always recommended to be on the latest and greatest, which is 10.3.1, but even within a specific major release (10.2), you should try to be on the latest minor release (10.2.1). Not saying that solves the issue though. Did you add those filed names to your network dataset, or is that just how they were named out of the box? Those are definitely not very good naming as it would cause issues in many different database formats.
... View more
02-02-2015
02:16 PM
|
0
|
13
|
1048
|
POST
|
The error is on the internal schematic tables it looks like. If you create a brand new fgdb with a schematic dataset and 1 diagram template configured for the network dataset builder and then try this again, is it OK? Make sure the builder is network dataset. Here is a link to the tutorial showing this.
... View more
02-02-2015
01:53 PM
|
1
|
15
|
1048
|
POST
|
Is your geometric network functioning properly? For example, if you try to just run a find connected trace with 1 starting flag, how long does it take and are you seeing strange results from that operation? If you create a new fgdb, with a schematic dataset and just basic config (no rules etc...) does the same problem happen? A schematic diagram is just reflecting what is currently in the underlying network index for a geometric network.
... View more
02-02-2015
01:10 PM
|
0
|
4
|
641
|
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
|