You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My abilities are somewhat limited here as far as a "quick fix" for Launch goes. To create the downloadable areas of the map, I have to go through a process that looks at the raw OSM data and extracts what I want to use. Since OSM data isn't so well organized, improvements here will need to be be iterative, over time.
Separately, there's coding up the app to display the extracted data. That adds more challenges. I'm able to do it; I added walking paths, for instance. But it's probably beyond the scope of Launch at this point unless it's something really important.
Also note that display data and search data are separate. You may find something you can search for doesn't display, or vise versa. Search data turns out to be easier for me to improve.
So with that in mind, feel free to comment here with your suggestions. I'll see if there's something quick I can do. I plan to re-generate the data within a week or two (#50), so we can get some more stuff in there. (The process takes about 2.5 days so it's something to plan ahead for).
In the specific case of playgrounds, which was suggested: I just checked and found one that showed up as a generic POI, probably because it has a name. Perhaps I can extract the data such that un-named playground shows up with the name "playground", but that might be too risky for launch.
The text was updated successfully, but these errors were encountered:
Suggested by @Ryuno-Ki
My abilities are somewhat limited here as far as a "quick fix" for Launch goes. To create the downloadable areas of the map, I have to go through a process that looks at the raw OSM data and extracts what I want to use. Since OSM data isn't so well organized, improvements here will need to be be iterative, over time.
Separately, there's coding up the app to display the extracted data. That adds more challenges. I'm able to do it; I added walking paths, for instance. But it's probably beyond the scope of Launch at this point unless it's something really important.
Also note that display data and search data are separate. You may find something you can search for doesn't display, or vise versa. Search data turns out to be easier for me to improve.
So with that in mind, feel free to comment here with your suggestions. I'll see if there's something quick I can do. I plan to re-generate the data within a week or two (#50), so we can get some more stuff in there. (The process takes about 2.5 days so it's something to plan ahead for).
In the specific case of playgrounds, which was suggested: I just checked and found one that showed up as a generic POI, probably because it has a name. Perhaps I can extract the data such that un-named playground shows up with the name "playground", but that might be too risky for launch.
The text was updated successfully, but these errors were encountered: