Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Estuaries in Coastline Data (e.g., Amazon Estuary) #31

Open
fbriol opened this issue Sep 22, 2024 · 1 comment
Open

Missing Estuaries in Coastline Data (e.g., Amazon Estuary) #31

fbriol opened this issue Sep 22, 2024 · 1 comment

Comments

@fbriol
Copy link

fbriol commented Sep 22, 2024

Hello,

We are working on building a high-resolution land/sea/ocean mask using shapefiles from osmdata. The data has been incredibly useful; however, we’ve noticed that estuaries are missing from the coastline data—for example, the Amazon estuary.

This omission affects the accuracy of our project, as estuaries are significant geographical features that should be included in the coastline. Is it possible to include estuaries in the coastline data provided by osmdata? We are willing to assist by modifying the coastline generation process to incorporate these areas if needed.

For reference, here’s an Overpass API query that illustrates the issue in the Amazon estuary region:

// Fetch all natural water bodies within the bounding box
[out:xml][timeout:25];
(
  way
    ["maritime"="yes"]
    ["natural"="water"]
    (-2.5,-52.0,0.5,-48.0);
  relation
    ["maritime"="yes"]
    ["natural"="water"]
    (-2.5,-52.0,0.5,-48.0);
);
out body;
>;
out skel qt;

We believe that including estuaries would enhance the dataset’s completeness and utility for many users.

Thank you for your time and consideration. We look forward to your response and are ready to collaborate on this.

Best regards,

Frederic.

@joto
Copy link
Collaborator

joto commented Sep 23, 2024

The coastlines as they are processed here don't take anything into account but the ways tagged as natural=coastline in OSM. That is on purpose. This data needs special processing and that's what we are doing here.

This data should include the estuaries but unfortunately more and more people mess up the OSM data and pretend the estuaries and bays are "inland water" when they are clearly not. Misusing the tags for inland water and then adding a maritime=yes to it is still, in my opinion, wrong tagging. That data should be fixed in OSM and then this processing will work as intended. Unfortunately this seems to be an uphill battle.

Anyway: The long and short of it is that the goal for this data is to do the special processing for the natural=coastline ways only. We don't have the resources to do any other kind of processing or provide and maintain the services for it. Feel free to set up your own processing using the coastline processing tools plus any other stuff you want to do and offer that to the public.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants