Latest Contributions by TedKowal

‎04-19-2018

You got me there, I never took #### as an error, the fix still is to widen the cell column or heighten the row -- or shorten the value by rounding or formating ... etc. Live and Learn!

‎04-18-2018

As Joe stated, MSAccess cannot be versioned naively. Howeever, almost full version control can be achieved by using the access MSSCCI extensions and MS Access Developer Tools. Now you can map one to one the files in MS Access source control with all the objects within the actual database. Now you can rebuild the MS Access database from any version. Yes there are some limitations but versioning can be done. For more information you can go here: So You Want to Version Your Access Database - Simon Online

‎04-18-2018

Like Dan I did not understand the question.... is the excel file corrupted and you cannot open it? If that is the case, How to recover unsaved Excel files | Excel Exposure Repairing a corrupted workbook - Excel Is the error when you are trying to open the workbook, or does the workbook open and you see "#####" in a cell or cells? If you see "#####" in cells then simply make the column wider or row taller...if the workbook will not open or opens with an error --- in order to help we would need the error code being given like Error 1004 .....

‎04-13-2018

Also vote here for MS Access support in Pro .. Enable ArcGIS Pro to access ESRI Personal Geodatabases

‎04-12-2018

This is the direction how the lines are drawn on your center line segments. All the segments should be drawn in the same direction. From this layer you build you routes or LRS. The LRS generally calculates "measures" increasing in value along the road. If you have a segment that is drawn in the wrong direction that portion would "Decrease" in value.

‎04-11-2018

Sorry, as I stated before this is not a quick solution, but one that sets you up with tools for great future benefits and time saving. You can get started by using the help and tutorial from ESRI What is linear referencing?—Help | ArcGIS Desktop Other youtube videos:Linear Referencing Using ArcGIS - YouTube , How to Create a Event Layer in ArcGIS - YouTube Can provide some assistance in insights to what you can do with your Routes when you have them built. I and I am sure other folks will be happy to assist you through any specific problem you run into while developing your LRS and performing event overlays.

‎04-10-2018

Joe I do not believe there are any better ways, only different flavors. In my shop, not dealing with streams but road I have similar situations and some difficult (political) when dealing with LRS... My ramps and connecting roads are like your tributaries and the mainline analogous to the main river... I have to use two options.... For the Main line since it is political and funding is derived from mileage, I use calibration points to create dynamic segmentation... for the ramps like your tributaries I simply use the length along option starting at 0 and make sure all the road segments are drawn in the proper direction (orientation)... The only times I had issues with coordinate priority is if I had the line segments that I building the LRS from accidentally drawn in the wrong directions or had small gaps in between.

‎04-10-2018

I would recommend using LRS (Linear Referencing System) especially if you are going to manage the signs along your road system. Quickly looking at your data, your signs do not have a relationship to the road they are on and must be blindly snapped to the closet line which is not always correct... I can give an outline on how I would address your situation... (there is no quick easy way about it). First I would create a LRS on your roads layer, perhaps using the the nombre field as your "Route." Having a LRS will allow your to "Event Map" without resorting to breaking up your roads into 5m segments.... You could create a table/dbf/excel that will event map your sign points to the road at whatever interval you want... When building your LRS you must determine the inventory route directions for road... I use the following rules N/S roads would have a direction S to N E/W roads would have a direction W to E Single Direction roads would be the direction of travel When building your LRS all your road segments beg/end parts of the segments must be following your direction rules Next you will have to add a Route field to your signs and populate the field with the corresponding route the sign is on. (This will allow you to event map your signs and get its corresponding Milepoint (reference distance along the line). Some other fields to incorporate to make your management easier: Add Route field and populate it Add a Sign facing field example ( 1 - Direction of travel, 2 - Opposite Direction of travel) Populate this field... this will allow you to orientate and offset the sign for those signs on roads that have two way traffic Now you can event map and overlay over your new LRS your speed limits along your road... the overlay will divide out your roads into segments relating to speed limits. You can use the offset to position the signs (right side of road for direction of travel, left side of road for opposite direction of travel).... Information from the road and or signs can be handles by simple SQL queries and joins. Yes this is a bit of work...but not much more than using the near/split and other routines and still have to manually find and fix exceptions that will occur (namely that you must snap a sign to the closest road...this can lead to many incorrect associations because the physical sign may be closer to another unrelated road...) Finally you will enjoy the functionality of your new LRS for other projects... What is linear referencing?—Help | ArcGIS for Desktop to get you started.. Este es mi dos centavos1

‎04-09-2018

I believe Vince Angelo answered this completely and Dale_Brooks-esristaff gave an excellent word warning! Currently, I am using coding to access Stored Procedures, my case it is VB.Net wrapped up around various custom commands that I have created to work within ArcMap. These, by nature, are very specific to your individual working environment. Since I am not fully versed in the geometry stuff, I do not touch any esri specific fields but only use store procedures with the attributes... for example, in my shop we use LRS (Linear Referencing System). Most of our new roads are being constructed at the beginnings of the route thereby constantly changing the beginning mile point. So store procedures in my case allow me to trigger an event that changes all the assets that are collected in reference to Mileposts downstream of the change.

‎03-21-2018

We don't have much to work on with your description? There could be a lot of reasons why joins are not matching...Data Types, Punctuation, Null values, Case Sensitivity... Typically I do not even attempt to join from a text file because of its many nuances. Give this try: Import your text file into MS Access Database as a table. After which make sure you County field is the same Data Type as the field you are trying to join to. Bring in this table into Arc Map then try your join again. Possibly when going through this exercise you may discover what is preventing the join. PS.... Realized that you are joining to a shape file... make sure your field names are less than 8 characters....

‎03-16-2018

I do not believe it is unreasonable to expect a consistent "Definition" of a FeatureSet and all language abide by that consistent definition. An apple may be an apple in VB.net but you have to treat it like an Orange in Python...... In all other areas in the programming world I FULLY expect an object or class to return a a class/object that could be used in the same manner in any language or package. That is a reasonable expectation!

‎03-13-2018

I don't use the attachment table... reason why I name the attachments something like FeatureID-X.png; the -X is for when I have multiple images for one feature eg Sign Post and its related Sign Panels(Multiple) and the -X is the placement order. So in my case I don't have to make a walk through making a comprehensive data store, I simply only have to create a query/view and Word uses that view as my single source..... reason why I put smarts in my image naming.... Select SignID.Signs, SignType, Config, (SR & "\\" & SignID.Signs & - & Config) & ".png") as Filename from Signs, SignPanels where SignID = ParentID; Signs are a Feature Class and SignPanels is an attribute table. My panel images are stored under each respective SR (State Route) they are assign to. There I have my single datastore with no extra work except for the query development. In my case, no coding since I am using Access other than the macro in Word. Most of my use of attachments come outside of GIS in my case, so the attachment table and its funky relationships are not needed since I don't really put them on maps and my online stuff is Google/Bing Maps over which I overlay the attachments with a similar query and using Lat/Long for placement. Good luck! Maybe someone who has knowledge of the Attachment Table can provide more assistance!

‎03-13-2018

Found some more notes on Single Directory vs path to image: If you can be sure the pictures will always be in the same folder as the mailmerge main document, you can incorporate a FILENAME field thus: {IF{INCLUDEPICTURE {IF TRUE "{FILENAME \p}\..\{MERGEFIELD Image}"} \d} {INCLUDEPICTURE {IF TRUE "{FILENAME \p}\..\{MERGEFIELD Image}"} \d}} or: {IF{INCLUDEPICTURE {IF TRUE "{FILENAME \p}\..\«Image»"} \d} {INCLUDEPICTURE {IF TRUE "{FILENAME \p}\..\«Image»"} \d}} If the path data are included with in the image field, you can use: {IF{INCLUDEPICTURE {IF TRUE «Image»} \d} {INCLUDEPICTURE {IF TRUE «Image»} \d}} or: {IF{INCLUDEPICTURE {IF TRUE {MERGEFIELD Image}} \d} {INCLUDEPICTURE {IF TRUE {MERGEFIELD Image}} \d}} For what it's worth, *provided* the path has the separators expressed as '\\' or '/', you can retain the links by omitting the all-encompassing IF test and the images will display correctly without the need to refresh the fields after completing the merge. For example: {INCLUDEPICTURE {IF TRUE "C:\\Users\\My Document Path\\Pictures\\«Image»"} \d}

‎03-13-2018

Given that ESRI will be dropping MS Access, I do not recommend that...but this type of thing is easy peasy using Access. In my shop, speed is related to functionality (geoprocessing is only one part of the equation). Back to your issue .. Since you are using variable picture/images, are your path names separated by "\\" double slashes, I use vb script so I do not know if py handles this .... but that was my issue when I first started using mail merge and including images. For my images, I use a standard name scheme so I generally can skip the joins since my image names are data in-it-self (Yes, I know this is not best practice...but it works). But for what it is worth here are some of my notes that help me .... To insert variable images in a mailmerge, you need to embed the relevant mailmerge field in a INCLUDEPICTURE field. However, there are some issues with this that make the process less straightforward. For example, when embedding a mailmerge field in an INCLUDEPICTURE field for the purpose of merging graphics: 1. the file paths to the fields need to have the separators expressed as '\\' or '/' instead of the usual '\'; 2. the pictures usually won't show until you refresh the fields (eg Ctrl-A, then F9) in the output document after completing the merge; and 3. even after updating the images, they remain linked to the image files, which can be an issue if you later delete the image or you need to send the merged output to someone else. {IF{INCLUDEPICTURE {IF TRUE "{MERGEFIELD FilePath}\{MERGEFIELD Image}"} \d} {INCLUDEPICTURE {IF TRUE "{MERGEFIELD FilePath}\{MERGEFIELD Image}"} \d}} The Braced pair help handle the refresh or re-linking issues....Note cannot add the brace programically need to do this in Word!

‎03-13-2018

.... again if the feature class was stored in a PGDB (MS Access ) you can create your excel spreadsheet based upon a view/query that linked the records together and that would be update-able from within excel .... another one of my reason for wanting ESRI to keep the MS Access format! .... we have plenty of excel spreadsheets that update upon opening that are linked to our PGDB's ...... Enable ArcGIS Pro to access ESRI Personal Geodatabases

Online Status	Offline
Date Last Visited	‎10-18-2023 06:40 PM

My Ideas

Latest Contributions by TedKowal

Re: Excel ###### error

Re: Personal Database; Versioned or Standalone?

Re: Excel ###### error

Re: MS Access 32 bit via ArcPro

Re: Create points on line between speed limit signs near the road in ArcGIS 10.4

Re: Create points on line between speed limit signs near the road in ArcGIS 10.4

Re: Creating a Route on a Stream System

Re: Create points on line between speed limit signs near the road in ArcGIS 10.4

Re: How to call an SQL Server stored procedure from ArcMAP

Re: Joining data does not work unless I retype the data in Excel

Re: arcgis...FeatureSet != arcpy...FeatureSet

Re: FGDB Source for MS Word Doc Mail Merge

Re: FGDB Source for MS Word Doc Mail Merge

Re: FGDB Source for MS Word Doc Mail Merge

Re: Feature class to Excel?

Re: Overpass and Underpass detection for intersect...

Re: Import of Objects (word-documents, pdf, ...) i...

Re: ArcGIS Pro (.mdb)?

Re: I am trying to calculate a field where i want ...

Re: Date (date field - mm/dd/yyyy) to String (stri...

Cartography and Maps