Delta CLT

Your New Favorite Change Template

Remember the good old days when people either wildly speculated about neighborhood change? What a simpler time. But to quote my dad's favorite Bob Dylan song:

Times they are a'changin'

But even now, during the buzzword-frenzied time of 'data-driven' everything, it somehow seems even harder to get information you trust, can understand and that you really care about. As much fun as reading a hundred page thesis on the distribution of gentrification and demographic shifts, I don't have time for that (I have to catch up on Brooklyn-99) and I doubt you do either (Game of Thrones or This is Us?).

This application does one thing: Shows you how housing and land-values have changed over time in the area you specify.

It addresses a simple question with equal simplicity and clarity, but if you want it to do more, have a ball!

Oh, and the data I used is a mock-sample. The service's data is incomplete / not processed fully yet... so don't write a story about Charlotte based on this info (cough cough Charlotte Agenda cough cough

Here's How It Works

The web-application has a few moving parts that were kept in isolation so that folks can easily modify and deploy this application for their area. The application uses:

• The Esri JS API (4.9);
• The Esri Calcite-Maps Library;
• The Esri Calcite-Bootstrap Library; and
• Hosted ArcGIS Online Feature Layers

How To Make it Work For You

I get it. Clone or download my repo and never tell me. So typical. Just kidding, let's go!

Here are the moving parts you need to update in order to deploy this application yourself:

1. Review Esri's Service for leveraging their API which can be found here
2. Open the index.html document and make the following modifications (where appropriate):

• Change the tags in the html header. If this will be public facing, having proper SEO is important. However, remember to give yours truely credit :)
• Publish a FeatureLayer to ArcGIS Online that has the locations, their current values and their historical values (I detail how I chose to organize my service later in this file).
• Change the title of the application (but I'd really like if we kept the whole Delta () structure... We could eventually make a composite tool if you do so and let me know!

3. Review the code under the comment. I get pretty detailed about what's going on in there. You'll ultimately make the following changes (If I was to guess):

• Change the 'center' and 'zoom' properties of the mapView to be centered and appropriately zoomed on the area you care about;
• Change the popup properties in the popTemplate variable (const) to correspond with the schema of your published service;
• Change the URL of the taxHistoryFeatureLayer to point to the service you published;
• Change the properties of the elements contained within the statDefinition array to correspond with the fields you care about on your published service; and
• Change the properties of the tvChart and pvChart variables to properly work with your service and accurately represent the data you're exploring. For instance, I used a mock-dataset for the years 2015,2016 and 2017 for my 'labels.' If your data has a differen't period, you'll need to update that fella.

And you should be good to go! I also tried to be a thorough as possible and not re-use names or name variables the same as their keys (i.e. I named the map view (mapView) so that when we set our map view, we don't need to write (view: view) which always confuses me :).

You can also create new graphs and do whatever else you'd like to extend this template!

Coming Soon:

Modal Support so that the 'About,' 'Help,' 'Learn More,' and 'AndrewBuiltThis' dropdowns actually do something

Enhanced CSS & Formatting (i.e. beter centering classes, more intuitive breakpoints, better symbols

Feature Aggregation to both improve performance and provide a better UX

Feel free to reach out for help or question!

Cheers, A