Select to view content in your preferred language

Summarizing Data - Approach. Currently manually entering into excel.

236
5
Jump to solution
03-21-2025 07:08 AM
Labels (3)
sdavidson
Emerging Contributor

Hello Friends,

Hoping for some direction on tools or methods to improve my workflow to summarize data. The main issue is that I am manually entering data into a table rather than calculating it. Indeed, I am literally running a query on the attribute table in Arc Pro and manually filling in the resulting count of features into excel - this feels horribly inefficient, and needs to be completely re-done if any of the attributes change.

I am working with a pavement marking dataset. Essentially, it is two featureclasses, lines and points, showing where pavement markings are throughout the city. Some attributes: paint type, colour, ownership, who maintains it (contractor or city staff), etc. Fairly self-explanatory, lines are things like centrelines or stop bars, points are things like turn arrows or bicycle lane symbols.

The method that I would normally use to somewhat-automate the process is to copy the table into excel and then write a formula for each cell in my table. Essentially, a long countifs function in each cell. However, if anything changes in the ArcPro table it would need to be copied into excel again. That's not too bad. However, if the structure of the table changes (different count of columns) then each countifs function would need to be adjusted. I'm fairly confident the tools are available in ArcPro to accomplish the same thing. How can I use ArcPro to do a similar summarizing process?

Description of the summary table in excel I have been manually entering information into:

  • The rows in the excel table are the different marking types. For example, crosswalks, stop bars, centrelines, etc.
  • The columns are setup to first double check that the data makes sense - and I am correcting the dataset as I go - and then to give an idea of numbers for each year of a 3 year plan to refresh markings. For example, we will be re-painting stop bars on higher traffic roads more frequently than lower traffic roads.
  • Column examples:
    • Total Count = Count of features of this type.
    • Owned by city = Count of features of this type owned by the city.
    • Owned by other = Count of features of this type not owned by the city.
    • Owned by City and on road = Count of features of this type owned by the city and is on road (the dataset also contains pavement markings on pathways, but these are not needed for my analysis)
    • Contractor = Count of features to be maintained by contractor
    • Planned Thermal = Count of features on the docket to be painted with a more durable material. These are all still being considered by our team.
    • Annual = Number of features of this type that will be re-painted annually, on average

I look forward to reading your suggestions.

0 Kudos
1 Solution

Accepted Solutions
BobBooth1
Esri Regular Contributor
5 Replies
AlfredBaldenweck
MVP Regular Contributor

Check out charts and Data engineering.

sdavidson
Emerging Contributor

Thank you for the suggestion, Alfred. I did some exploration with Data Engineering. It seems to give the summary information I am looking for, but doesn't put it into a table like I described. It seems like another method to query the data, but I'm still extracting the result and manually putting it into my table.

0 Kudos
BobBooth1
Esri Regular Contributor
sdavidson
Emerging Contributor

The model builder seems to be doing the trick. It took some time to get my head around some of the problems (for example, using variables in SQL queries when iterating), but I think this will be a useful tool now that it has been put together.

Appreciate the suggestion.

 

sdavidson_0-1743010742082.png

 

0 Kudos
BobBooth1
Esri Regular Contributor

Nice!

0 Kudos