ritterim / atlas Goto Github PK

View Code? Open in Web Editor NEW

7.0 7.0 6.0 2.52 MB

A library that contains geographical data about states, counties, and zip codes.

License: MIT License

C# 63.55% Batchfile 0.17% PowerShell 36.29%

atlas's People

Contributors

Stargazers

Watchers

Forkers

kendaleiv scottschwalm khalidabuhakmeh lightyeare calebjenkins dustinh

atlas's Issues

Will a license be designated for the project?

Choosing a license.

Although, I suppose a license is not required.

Update data

We have data for March 2015.

Counties
CountyZipCode
States
ZipCodes

hmmm...not sure if i created these links right

Missing zip codes - 75033 and 21764

@JCarver27 commented on Tue Nov 02 2021

🐛 Bug Report

We're missing a zip code in Tide....75033.

To Reproduce

Steps to reproduce the behavior:

Go to https://tide.rimdev.io/lead-workflow/new?callDirection=Inbound&stepId=InboundPreLandingViewModel
Fill in first, last, and phone number. I recommend something ridiculous, because why not.
Enter 75033 as the zip on the next screen
See error

Expected behavior

75033 is a valid zip in TX.

Screenshots and/or request snippets

Estimates

@JCarver27 commented on Tue Nov 02 2021

21764 is also showing an error.

@lightyeare commented on Tue Nov 02 2021

Uses Ritter.Atlas, which hasn't been updated in a while.

@bwarner22 commented on Wed Nov 03 2021

Ritter.Atlas ???? didn't know we had such a thing!

Additional Information To Add to Csv Data

Atlas is missing:

Elevation
Primary City (which I think is the largest city in the zip code)
ScfCode

However, ScfCode can be easily derived from the zip code. The ScfCode is the first three digits of the zip code.

Atlas includes the AnsiCodes for County and State.

Converting lat./long. datatype to double for higher precision

atlas/src/Atlas/ZipCode.cs

Line 11 in d8013a1

public float Latitude { get; set; }

uses float based on existing coord.-data (https://github.com/ritterim/atlas/blob/d8013a18f528f1e7b58efb60d1c154814b56c69d/common/ZipCodes.csv), but double would afford more precision if this data gets updated in the future without causing child-apps. to be updated.

Please note, however, the distance-differences would be under one-hundred feet for both lat. and long.
Given a second of lat. (1" = 1/3600 = 0.000277778) is constant at roughly one-hundred feet (http://nationalatlas.gov/articles/mapping/a_latlong.html) and any precision gains for lat. would be to the right of a float's max. precision:

12.345678f = 12.34568
12.345674f = 12.34567

12.34568 - 12.34567 = 0.00001 // 0.036 lat. sec. ~ 3.6 ft.

Long. secs. are not constant (are dependent on lat. position), but empirical data (based on PA-lat.) shows similar distances between secs. and again would only have maximum impact if mid-west and westward U.S. zip-codes are used (since mid-west long. have triple-digit degrees).