I don't want to combine the 50 states into a single GDB, since the vendor sends regular updates to the data and I don't want to combine each time an update is sent.
Can you provide some more detail on what you are trying to accomplish? How are you looking to access the data, and what operations/anaylsis will you be performing once you do?
We would like to access the data with a rest endpoint. We are a waste company and have, for example 2000 residential cans in an HOA, however the HOA is billed to a single account/customer, so our account/customer master only has the single customer. We plan to view the 2000 residents using an off the shelf product that includes every parcel and point in th U.S. We already have the HOA polygons, so if a parcel/point is inside that polygon they are serviced by us ( a customer). The customer calls us directly with any issues, e.g. missed pickup, so we want that parcel to show as a current customer. Today that customer is not visible in our system. We don't want to add the customers to our account/customer master since they are not billed. The off the shelf data will be regularly updated, and it comes as GDBs by state, we don't want to create a maintenance nightmare, by having to consolidate the GDBs after every update. Besides consolidating the GDBs takes forever :-(
I'd like to have the updates unzipped as 50 states/gdbs and access the data as a single rest endpoint, NOT 50 rest endpoints. Any thoughts on how to do this is appreciated.
You can have a single service with 50 individual layers, but each layer will be referenced with an index. Ex:
If you're looking to have all of the data referenced through a single index (i.e. /0), the only way you can accomplish this that I know of is to merge all the data to a single feature class.
Retrieving data ...