About this skill

Problem

AMap JSAPI 2.0 spreads map development across initialization, overlays, layers, events, and LBS services. The v2.0 securityJsCode requirement adds loader order and proxy concerns, which can cause quick demos to fail in subtle ways. This skill is for engineers who need practical frontend map code examples rather than a full product SDK.

How It Works And Limits

It organizes guidance around AMapLoader.load(), new AMap.Map(), Marker, Polyline, Polygon, InfoWindow, Layer, Geocoder, and PlaceSearch. Start from a scenario example, then verify the API reference before generating code. It is useful for map init, markers, route rendering, area drawing, custom layers, geocoding, POI search, and event handling. It also emphasizes v2.0 key configuration, proxying serviceHost in production, declaring only needed plugins, and calling map.destroy() to release the WebGL context. It is best suited for common AMap JSAPI 2.0 frontend tasks, not for backend key-proxy implementation, production GIS architecture, or custom service design.

Screenshots

Use Cases

Frontend needs to quickly build a map homepage demo with zoom, pan, and rotation controls.
Need to mark store locations with info windows, context menus, and mass marker avoidance.
When building a logistics trajectory page, draw route polylines, area polygons, and connect routing services.
When building a location search box, call POI search, input suggestions, and geocoding/reverse geocoding.

Best For

Frontend engineers who need to integrate AMap into a homepage and quickly deliver an interactive map demo.
Web developers building store, logistics, or mobility pages who need overlays, routing, and POI search.
Integration engineers who need to follow AMap JSAPI v2.0 security-key, proxy, and resource-release patterns.
Tech leads working on LBS apps who need to verify geocoding, routing, and POI search API usage.