From my previous experience with web maps, longitude normally precedes latitude, which makes geographical coordinates similar to x/y on a Cartesian plane. It's good that the <Map /> component has coordorder prop, but this still leaves a couple of issues.
The values of coordorder refer to longitude as long rather than lon as this is done is markers, which results in some kind of inconsistency. I would expect lonlat / latlon here or <Marker long=? lat=?>.
When coordorder="longlat", markers flip despite that they explicitly use lon and lat props. Here are the the Moscow ones from the example:
Removing coordorder="longlat" brings them back.
If Yandex maps API uses lat/lon instead of lot/lan by default, I assume it is for a good reason. However, the React component could probably have a different default behaviour here, just to be more consistent with other mapping / data vis tools and formats (e.g. Mapbox GL JS and GeoJSON).
From my previous experience with web maps, longitude normally precedes latitude, which makes geographical coordinates similar to x/y on a Cartesian plane. It's good that the
<Map />component hascoordorderprop, but this still leaves a couple of issues.coordorderrefer to longitude aslongrather thanlonas this is done is markers, which results in some kind of inconsistency. I would expectlonlat/latlonhere or<Marker long=? lat=?>.coordorder="longlat", markers flip despite that they explicitly uselonandlatprops. Here are the the Moscow ones from the example:coordorder="longlat"brings them back.If Yandex maps API uses lat/lon instead of lot/lan by default, I assume it is for a good reason. However, the React component could probably have a different default behaviour here, just to be more consistent with other mapping / data vis tools and formats (e.g. Mapbox GL JS and GeoJSON).