Breaking Into Regions or States?

[ssokol]

Hi Brian,

Any thoughts on the best way to break up the database into regions? The full US data set (zoom levels 0 - 12) comes in at about 5.9 GB. One of my use cases is an iOS app, and I would prefer to give my users the option of downloading only those areas in which they fly rather than making them pull the full 5.9 GB each month. (It would save me a bit on bandwidth fees as well.)

Thanks,

Steve

[jamez70]

Maybe you could have it select the sectional charts that they want, sort of like what Avare for Android did? Jim

…

On Wed, Aug 7, 2024 at 1:40 PM Steven Sokol ***@***.***> wrote: Hi Brian, Any thoughts on the best way to break up the database into regions? The full US data set (zoom levels 0 - 12) comes in at about 5.9 GB. One of my use cases is an iOS app, and I would prefer to give my users the option of downloading only those areas in which they fly rather than making them pull the full 5.9 GB each month. (It would save me a bit on bandwidth fees as well.) Thanks, Steve — Reply to this email directly, view it on GitHub <#4>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIVBU4XIPXTAFSBLQO7YRTZQJSZJAVCNFSM6AAAAABME66WWOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TIMJQGEYTKNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ssokol]

Right now the vector map engine I'm using on my iOS app (a commercial library from a 3rd party vendor) makes everything available on an ala carte basis: select the countries and regions (states / provinces / oblasts / etc.) that you want. The library downloads a map data file for each selected region and the engine handles determining which files contain which data. I was planning on using essentially the same approach, creating individual mbtiles files for each state. My question is really how to go about it. Is this something that's worth building into chartmaker or is it best done as a separate project?

…

On Wed, Aug 7, 2024 at 1:44 PM jamez70 ***@***.***> wrote: Maybe you could have it select the sectional charts that they want, sort of like what Avare for Android did? Jim On Wed, Aug 7, 2024 at 1:40 PM Steven Sokol ***@***.***> wrote: > Hi Brian, > > Any thoughts on the best way to break up the database into regions? The > full US data set (zoom levels 0 - 12) comes in at about 5.9 GB. One of my > use cases is an iOS app, and I would prefer to give my users the option of > downloading only those areas in which they fly rather than making them pull > the full 5.9 GB each month. (It would save me a bit on bandwidth fees as > well.) > > Thanks, > > Steve > > — > Reply to this email directly, view it on GitHub > <#4>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAIVBU4XIPXTAFSBLQO7YRTZQJSZJAVCNFSM6AAAAABME66WWOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TIMJQGEYTKNQ> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACVQPGYO4SZEC6J565EM6LZQJTJTAVCNFSM6AAAAABME66WWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZUGEYTMOJRGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *Steven Sokol* * <https://www.falkenavionics.com/>* *Falken Avionics, LLC <https://www.falkenavionics.com/>* Makers of FlightView <https://www.falkenavionics.com/flightview/> EFIS Cedar Park, Texas

[N129BZ]

The "easiest" solution would be to allow selection of the 53 individual chart areas - which correspond exactly to the printed sectional charts. To my knowledge, FAA does not publish charts by state. It should be fairly straightforward to add a checkbox selection of one or more of the specific 56 charts that you want to process. I would also HIGHLY recommend using WEBP image format. With WEBP the full mbtiles database is less than 3 gb. I will work on getting a checkbox list UI added to the app to make this possible.

[N129BZ]

I have completed and am currently testing the modified app. Rather than a GUI I have implemented a console interface where the app prompts with "Enter 0 to process all charts in the chartprocessindexes array, or 1 to process a single VFR chart: "

When 1 is entered, the console puts out:

Select the chart number you want to process from this list

1 Albuquerque
2 Anchorage
3 Atlanta
4 Bethel
5 Billings
6 Brownsville
7 Cape_Lisburne
8 Charlotte
9 Cheyenne
10 Chicago
11 Cincinnati
12 Cold_Bay
13 Dallas-Ft_Worth
14 Dawson
15 Denver
16 Detroit
17 Dutch_Harbor
18 El_Paso
19 Fairbanks
20 Great_Falls
21 Green_Bay
22 Halifax
23 Hawaiian_Islands
24 Houston
25 Jacksonville
26 Juneau
27 Kansas_City
28 Ketchikan
29 Klamath_Falls
30 Kodiak
31 Lake_Huron
32 Las_Vegas
33 Los_Angeles
34 McGrath
35 Memphis
36 Miami
37 Montreal
38 New_Orleans
39 New_York
40 Nome
41 Omaha
42 Phoenix
43 Point_Barrow
44 Salt_Lake_City
45 San_Antonio
46 San_Francisco
47 Seattle
48 Seward
49 St_Louis
50 Twin_Cities
51 Washington
52 Western_Aleutian_Islands
53 Wichita

Enter a single chart number and the app will produce a single chart mbtiles database, for example, entering 50 will make Twin_Cities.db

Screenshot:

[ssokol]

Excellent! One small tweak, if I might suggest it: a command line option for the chart number. That would make it easy to script the process of generating the 53 separate database files.

[ssokol]

Oh - that last comment was assuming that the "0" option generates a single Sectionals.db file as the app currently does. I guess another option would be to accept "*" or something to create all 53 separate database.

[N129BZ]

I could implement a "*" option to process all 53 as individual db files... I'll do that and test it.

[N129BZ]

Added the "*" option which will process all 53 VFR area charts individually into separate db files

[N129BZ]

Closing this issue