|
POST
|
The Points to Line (Data Management) tool will work for what you want if you can come up with a field in the point attribute table that distinguishes which point belongs to which line. If there's not already a field that contains that differentiation, you can create a new field and populate it with two different values. Then start Editing and then select all the points that need to become your first line. Use Field Calculator to give them all the same value. Then select all the points that will form your second line. Use Field calculator to give them all the same value, which needs to be different than what you used for your first line. For example, in the image I had posted in an earlier reply I created a "LineID" field and populated it with "A", "B", and "C". Then run the Points to Line tool, being sure in the Line Field (optional) part to click on the pulldown arrow on the right and choose the field that you just added the differentiating values to. Chris Donohue, GISP
... View more
07-29-2016
07:51 AM
|
1
|
0
|
1991
|
|
POST
|
Let me add in a group of people who work with this sort of data alot and probably have run into similar issues: Addressing Also, I almost wonder if there is not already an ESRI LGIM addressing tool/function available that detects for these sort of gaps in address ranges. Chris Donohue, GISP
... View more
07-28-2016
07:55 PM
|
0
|
0
|
1098
|
|
POST
|
Another workflow - if the intent is to create linework and then split it at existing points, and you have available an ArcGIS Advanced/ArcInfo license, you can do this: Create the line(s) with Points to Lines (Data Management) with the default settings. Don't use the Line Field at all. In your point feature class, select only those points that are the break-points for the lines. Export this query result to a new feature class. Use Split Line at Points (Data Management) to break the line(s) you created in step 1. Split Lines at Points - ArcGIS Help (10.2, 10.2.1, and 10.2.2) Chris Donohue, GISP
... View more
07-28-2016
03:25 PM
|
0
|
0
|
1991
|
|
POST
|
Can you elaborate what you mean by "in the middle of the points"? More specifically, do you need the constructed line to break at an existing point, or at a position between points? If it is the former, you may want to look into populating your points with an attribute you can then use as your "Line Field" when running Points to Line. For example, all the points that make up the first line can be given a value of 1, all the points for the second line a value of 2. Note - if the new lines should touch, you will need to duplicate any point at the junction where lines start/end so they get created and give it the appropriate line attribute. Otherwise, there will be a gap as no line will be created (see image below where this was the case). Points to Line - ArcGIS Help (10.2, 10.2.1, and 10.2.2) If it is the latter, can you elaborate on what basis will be needed to decide where to break the line? Chris Donohue, GISP
... View more
07-28-2016
02:30 PM
|
1
|
2
|
1991
|
|
POST
|
Another item to help in troubleshooting - check the Properties of the Data Frame to see what it is using. It may be that the Data Frame is set to an inappropriate coordinate reference system. Keep in mind the Data Frame "inherits" its coordinate reference system from the first layer loaded into ArcMap (and if the first layer loaded in had an Undefined reference system, the Data Frame will be Undefined). Chris Donohue, GISP
... View more
07-28-2016
09:26 AM
|
0
|
0
|
3324
|
|
POST
|
Just a thought - this is almost like creating a TIN (triangulated irregular network), but without the vertical dimension. Maybe someone can run with this - I'm can't quite figure out the rest (not enough caffeine yet ) - would it be possible to go from a TIN to polygons then to lines? Chris Donohue, GISP
... View more
07-26-2016
08:48 AM
|
0
|
0
|
3780
|
|
POST
|
If you have access to an Advanced ArcGIS license and ET GeoWizards, here is a vector workflow that could be of use: If your data is raster, convert to vector. For your pasture polygons, create a new field in the attribute table for use as a unique ID. Populate it with unique ID's (Calculate equal to the FID field is the easiest Next, we will use the river lines to split the pasture polygons. Use ET Geowizards (third-party ArcGIS add-on) Split Polygons by Lines function. You can download their software and try it out - it is a free function. However, there may be a limit on how many features you can do. ArcGIS tools add-ons and extensions from ET SpatialTechniques Now that you have a split polygon result, run a Frequency based on the Unique ID field you created back in step #2. Frequency - ArcGIS Help (10.2, 10.2.1, and 10.2.2) Now do a query on all the Frequency count that are greater than one. These are the resulting polygons by Unique ID that have river on both sides. If there are only a few, you can manually correlate them to the pasture polygons you made. Otherwise, move on to the next step. One can do an Attribute Join to join of the Frequency result back to the pasture polygons feature class to then be able to query the result (Frequency Count greater than 1) and have the actual polygons select. Edits - cleaned up the process order Chris Donohue, GISP
... View more
07-26-2016
07:53 AM
|
1
|
1
|
2316
|
|
POST
|
If you have access to an Advanced ArcGIS License, one possibility is: Split Line at Point—Data Management toolbox | ArcGIS for Desktop Chris Donohue, GISP
... View more
07-22-2016
09:18 AM
|
1
|
1
|
1488
|
|
POST
|
Some ideas: Has topology been run on the Zoning and Parcels to ensure they are coincident? Viewing linework at a viewing scale of less than 1:1 will show apparent offsets that are not real - i.e. they are not really what is going on. The polygons could be totally coincident, but below 1:1 look off. So some visually-seen disconcerting gaps/overlaps are actually not issues. Here's ESRI Supports explanation: As per our phone interaction, a map scale past 1:1 is a known limitation of our software because at a scale of 1:1, the screen display is equal to the actual distance of objects on the earth's surface (i.e. an inch on your screen is equal to an inch on the ground). When you go past that scale, it may appear that features are overlapping (when in reality) what you are seeing is the actual software resolution tolerance pushed past it's maximum threshold. In essence, the entire screen is only one point (at a map scale of 1:0), which is why your work flow is producing inaccurate results. Strangeness - gaps unintentionally created while editing Chris Donohue, GISP
... View more
07-22-2016
09:07 AM
|
2
|
0
|
3284
|
|
POST
|
I'm not saying it's super-long to set up, but instead that since there are more available options in a geodatabase one usually does take longer to do so. For example, since one has topology as an option compared to shapefiles, one will be setting up a Feature Dataset in a File Geodatabase to house it and its related feature classes. For it to be realistic, the set up of the Feature Dataset will need to include a coordinate reference system. If other feature classes are a component of your topological check, you will need to load them into that Feature Dataset. Then there are Domains, Relationship Classes, etc. That's not to say this is an onerous task; but it does take a bit of time to do compared to a shapefile where one just in ArcCatalog right-clicks and picks New, then Shapefile, and is done outside of assigning a coordinate system (which is optional). FGDB are awesome, but they do take a bit of effort on the front-end to effectively harness that power. Chris Donohue, GISP
... View more
07-21-2016
04:05 PM
|
0
|
0
|
4239
|
|
POST
|
Part of what makes GIS interesting is the divergence between classroom theory and the pragmatic reality. Welcome to the working world of GIS! Domains are a way to constrain your data in a field to only contain a limited set of values - your "valid inputs". Say your organization maps water supply pipes. Say the only material used for the pipes is either copper or PVC. A Domain could be created for the Material field that only allows the entry of copper or PVC. This helps maintain data integrity. A quick tour of attribute domains - ArcGIS Help (10.2, 10.2.1, and 10.2.2) Chris Donohue, GISP
... View more
07-19-2016
12:56 PM
|
1
|
0
|
7883
|
|
POST
|
Merge (Data Management) would be the way to go. Note when you run Merge the Field Map control, which allows you ways to affect how the fields of each feature class get mapped into the combined feature class. Note that the Field Map control interface is not totally intuitive at first, so play around with a bit to get a handle on what it does. Merge - ArcGIS Help (10.2, 10.2.1, and 10.2.2) Field Map Control - ArcGIS Help (10.2, 10.2.1, and 10.2.2) Chris Donohue, GISP
... View more
07-19-2016
11:50 AM
|
1
|
0
|
7883
|
|
POST
|
I haven't used it myself, but it looks interesting. On the product page they offer a free 60 day trial and also a contact for additional information. If no posts a reply to your question, I would try the information contact: ArcGIS for Aviation: Charting is bundled with components for data quality control, cartographic product generation, and workflow management for AIM users. It also includes a complete workflow tutorial and a sample database. Optional services are available that can be customized to your organization's needs. For more information contact [email protected]. Source: ArcGIS for Aviation: Charting| Technical Information Chris Donohue, GISP
... View more
07-19-2016
09:41 AM
|
1
|
0
|
1562
|
|
POST
|
If you have access to the Spatial Analyst Extension, one option is to use Map Algebra: A quick tour of using Map Algebra—ArcGIS Help | ArcGIS for Desktop One workflow would use SetNull to Null out all the values of cells that match your "Erase" raster. Note that you may have to do a processing step first to set up your Erase raster to give it distinct values so the SetNull can work as desired. This can be done with Con or Reclassify. Set Null—Help | ArcGIS for Desktop Con—Help | ArcGIS for Desktop Reclassify—Help | ArcGIS for Desktop Chris Donohue, GISP
... View more
07-19-2016
08:00 AM
|
1
|
0
|
3146
|
|
POST
|
I second what Joseph Segretto suggested - at first glance this looks like a Datum shift. While I'm not familiar with North Carolina data, we have a similar shift here in California when data is in CA State Plane NAD 27 vs. CA State Plane NAD 83. I'd verify the coordinate reference system applied to the data to ensure it is the correct one, and that the correct Datum Transformation was applied if the data does not share the same coordinate reference system. Chris Donohue, GISP
... View more
07-19-2016
07:35 AM
|
2
|
0
|
2109
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-18-2015 12:04 PM | |
| 1 | 09-29-2015 12:41 PM | |
| 1 | 11-29-2018 07:51 AM | |
| 1 | 05-08-2018 02:07 PM | |
| 1 | 07-26-2016 07:53 AM |
| Online Status |
Offline
|
| Date Last Visited |
08-03-2022
01:39 PM
|