11/27/2024 4:23:44 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
State Splitting
Posted: 12 Feb 07 9:56 AM
|
fiogf49gjkf0d We have field agents that work in regions, for instance region 5 is TX, LA, NM, AZ. We have two regions that split CA, north and south. Can you give suggestions on how to split these in the system for grouping/quering? We where thinking of zip codes but that may cause frequent updates for the zip code ranges. Anyway, any ideas you can give me to explore? |
|
|
|
Re: State Splitting
Posted: 13 Feb 07 6:18 AM
|
fiogf49gjkf0d We were faced with similar issues for North and South New Jersey. Zip codes are just too numerous and extremely hard to manage. What we found to be the best way was to split by county.
I know the next question - how do you figure out the county? Well, we have a process that goes through the address table every Saturday that updates the county field for every record. How do we figure out what the county is? We use a 3rd party database and control that does it for us. We just pass the address as its stored in the database to the control and it passes back the full, correct address along with a lot of other info - including longitude, latitude, USPS route codes, what type of building it is, etc. The software we use is also CASS compliant meaning its certified by the USPS and enables us to get discounted bulk mail rates.
The software comes from Melissa Data and is called Data Quality Tools Suite, It is subscription based. We get an updated database via priority mail every month. The database does expire so there is no one time fee. Addresses, localities, etc are in constant flux.
John G. |
|
|
|
Re: State Splitting
Posted: 13 Feb 07 7:36 AM
|
fiogf49gjkf0d Another approach might be to use data from the census bureau zip code tabulation area table. http://www.census.gov/geo/ZCTA/zcta.html You could set a assign everything south of the designated latitude to one rep and everything north to someone else.
We use this data to locate pharmacists near a requested zip code.
This data has not been updated since 2000, so the Melissa data would be a more up to date source.
Craig
|
|
|
|
Re: State Splitting
Posted: 13 Feb 07 9:41 AM
|
fiogf49gjkf0d Hmmm... ZCTA looks like a good solution as well. Will still need to identify where an entity is located - eg. what is their latitude? I've never worked with ZCTA and am not familiar with how it would be programmed to retrieve latitude information.
As you stated, the Melissa Data is very up-to-date vs. the ZCTA data (plus I like all the other data cleansing Melissa Data does), but for the cost and probably minor differences in terms of entities on the latitude border it would be worth looking into ZCTA.
Thanks,
John G. |
|
|
|
Re: State Splitting
Posted: 13 Feb 07 9:58 AM
|
fiogf49gjkf0d ZCTA provides a table of states and postal codes with the corresponding lat./lon. You could look up the account's zip, use the ZCTA to get the lat. and then compare to the lat. split value for the state.
Thanks,
Craig |
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|