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

add support for EPSG:4326 WMS layers #4858

Merged
merged 1 commit into from
Mar 8, 2018
Merged

add support for EPSG:4326 WMS layers #4858

merged 1 commit into from
Mar 8, 2018

Conversation

tyrasd
Copy link
Member

@tyrasd tyrasd commented Mar 7, 2018

See #4843, follows #4814 – adds support for WMS'es supporting EPSG:4326 (WGS 84).

Are there any alternative codes for this projection around? I've seen CRS:84 in some places (examle), but I'm not actually sure where that one actually originates from…

Also, it would be nice to do a similar analysis as in osmlab/editor-layer-index#425 for EPSG:4326 as well.

@tyrasd tyrasd changed the title add support for 4326 WMS layers add support for EPSG:4326 WMS layers Mar 7, 2018
y: lat * 180 / Math.PI
};
default: // EPSG:3857 and synonyms
var mercCoords = d3_geoMercatorRaw(lon, lat);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice - this is much simpler 👍

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh wait nevermind, it's just moved

@bhousel
Copy link
Member

bhousel commented Mar 8, 2018

Are there any alternative codes for this projection around? I've seen CRS:84 in some places (examle), but I'm not actually sure where that one actually originates from…

Interesting - that source also supports EPSG:4326. It looks like it's the same as CRS:84 but with x and y switched 🤔

@bhousel
Copy link
Member

bhousel commented Mar 8, 2018

Also, it would be nice to do a similar analysis as in osmlab/editor-layer-index#425 for EPSG:4326 as well.

Sounds good to me! I don't see a need to wait for that, so I'm just going to merge it as is. Thanks for the PR 😃

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

Successfully merging this pull request may close these issues.

2 participants